Symptom
OrderConfirmationRequest_In Payload is used, Payload error was showing as “Price unit of measure XX not defined- 006(MMPUR_CONF)” and “ Units of measure X XX do not match up”.
Environment
SAP S/4HANA Cloud
Cause
When there is more than one Unit of measure with same ISO code and while sending confirmation, if the Supplier sends a unit of measure which is not marked as “Primary Code” flag this error occurs.
The SSCUI entries content are built in basis system (Y13) where the SAP code/ ISO code mappings are done. Here if there are 2 units of measure with the same ISO code, the setting would be like one of the unit of measure will have the Primary code flag active. Every system receives this information as one source of truth and needs to be followed.
Resolution
The system setting allows you to have same ISO code for two measurement units with the same dimensions. But one of them will mandatorily have the ‘Primary Code’ flag active.
In case you have 2 units with the same ISO code, it is recommended to use Unit of Measurement which is marked as Primary code flag set against the ISO code for posting a confirmation.
Use of the Primary code field is “You can convert several internal units of measure to the same ISO code. For the conversion in the opposite direction, there must be a unique assignment. This assignment is made by flagging a unit of measure as a primary unit for a particular ISO code”
Keywords
MMPUR_CONF006, Price unit of measure, ISO code, Primary code, Unit of measure, OrderConfirmationRequest_In , KBA , MM-PUR-GF-EDI-2CL , Electronic Data Interchange (Public Cloud) , Problem
SAP Knowledge Base Article - Public