Rounding Profile Issue in Article Master - IS Retail System

[Former Member]

Hi,

We have an Issue with the Rounding Profile in Article Master of IS Retail System.

Rounding Profile (50) Maintained at Purchasing View of Article Master (MM41 & MM42) and the same is getting copied to Logistic DC View and Logistic Stores of Article Master

Scenario: -

DC Rounding Profile is being incorrectly applied to Store to Distibution Ceter STO

Return STO between Stores (xx01 u2013 xx10) and Distribution Center (Site u2013 XXAA and XXBB)

Store is returning the Stock to the Distribution Center. While creation of Return STO, System is taking the Rounding Profile QTY maintained at Purchasing View of Article Master Record.

Configuration Done:

The Rounding Profile Field hide at the Logistic: DC View and Logistic: Store View of Article Master (OMSR  MARC-RDPRF).Hence the Rounding Profile Field at Both Logicstics View got disappeared in Article Master Screens. But still the entries are visible at MARC Table.

Issue:-

The system is picking the Wrong Qty (50) instead of 1 Qty while creation of Return STO between Stores and Distribution Center.The System is prompting the Qty 50 (Which is maintained in Purchasing View of Article Master but No Rounding Profile is maintained at Logistic: DC View and Logistic: Stores View of the same Article).

REQUIREMENT:

While creation of Return STO between the Stores and Distribution Center the Rounding Profile should be inactive.

The system should pick up the Right Qty entered instead of Rounding Profile Qty.

Your valuable suggestions or advises are highly appreciated...

Regards,

Sateesh.Kandula

Edited by: VijayaSateeshKumar Kandula on Nov 8, 2010 11:52 PM

[Former Member]

Hi,

We have resolved this Issue using the Configuration Change in OMSR and programatically.

Thanks

Sateesh.Kandula

[Former Member]

Hi,

Can you please put in some detail how you did it? I am also facing the same issue.

Thanks

Manav

[Former Member]

Hi,

even though this thread is quite old, can someone describe on how to resolve this issue via OMSR?

Thx in andvance.

Sebastian