This website is not affiliated with, sponsored by, or approved by SAP AG.
Logistics : PM and its sub-modules & SM
6 posts • Page 1 of 1
Due to our business requirement, we have activated the user exit EXIT_SAPLCOZF_002 in anticipation that the valuation price field (EBAN-PREIS) of the purchase requistiion or stock transport requisition line item is determined in accordance with the pre-defined rule. However, the problem was that even if we can manage to populate the new proposed price in accordance with our rule, SAP has always over-write this determined value (from the user exit) with the valuation price from the moving average price/standard price of the material master in the demand plant. Please clarify if this is the standard system behavior and how to correct this problem so that we can apply our customized rule for valuation price determination of our external purchase requisition or stock transport requisition. We are in ECC6.0.
The reason is that we would like to control the planned cost vs actual cost for our PM work order especially in case of stock transport requisition where the material is supplied from the supply plant. We have successfully activated the user exit EXIT_SAPLCK21_002 to pick up the planned cost from the supply plant of the material. It is then our next problem to recognize that when the PM work order release the work order where the planned costs are accepted, the new planned costs (which is defaulted from the MAP of the material in the demand plant) is kicked in automatically when the stock transport requisition is created (upon work order release) and therefore, we think we should use the user exit EXIT_SAPLCOZF_002 to ''over-write'' the MAP of the material at the demand plant. While debugging the program, we, somehow, saw that when the latter user exit is called, the planned costs are correctly determined and defaulted into EBAN-PREIS of the stock requisition line item. It is only after we exit this function module that SAP automatically ''over-write'' it again.
Hopefully, our business requirement is justified.
Did you get any feedback/help on this one?
Ive used the 'PRICING' FM in that user exit and the prices passed to EBAN-PREIS remain the same. Equally, I have even hard-coded prices, just to test, and no change made by SAP.
However, use BAPI_SALESORDER_SIMULATE to generate prices and they do get changes. There seems to be no clear reason for this.
Any feedback would be much appreciated.
6 posts • Page 1 of 1
Who is online
Users browsing this forum: No registered users and 2 guests