Do you have any question about this error?
Message type: E = Error
Message class: KOSA - Product Cost Collector
Message number: 204
Message text: Costing not possible - routing header unit of measure changed
You are attempting to create a preliminary cost estimate for a product
cost collector of a repetitive manufacturing material. The repetitive
manufacturing profile specifies that reporting point processing is
active.
In preliminary costing, when the routing is changed the reporting point
structure of the associated run schedule headers is converted.
However, the unit of measure in the routing header was changed. This
means it is not possible to convert to the new reporting point
structure.
The system does not execute preliminary costing.
Change the header unit of measure back to what it was. Then perform
preliminary costing again.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
KOSA204
- Costing not possible - routing header unit of measure changed ?The SAP error message KOSA204, which states "Costing not possible - routing header unit of measure changed," typically occurs during the costing process in SAP when there is a mismatch between the unit of measure (UoM) defined in the routing and the unit of measure used in the material master or the production order.
Cause:
- Unit of Measure Mismatch: The routing for the material has a different unit of measure than what is defined in the material master or the production order. For example, if the routing is set up with a unit of measure in pieces (PC) but the material master is set up in kilograms (KG), this discrepancy will trigger the error.
- Changes in Routing: If the routing has been changed after the material was created or after the last costing run, this can lead to inconsistencies.
- Costing Variant Settings: The costing variant may not be configured to handle the unit of measure changes appropriately.
Solution:
Check Routing and Material Master:
- Go to the routing (transaction code CA03) and check the unit of measure used in the routing header.
- Go to the material master (transaction code MM03) and verify the unit of measure defined there.
- Ensure that both the routing and material master are using the same unit of measure.
Adjust Routing or Material Master:
- If there is a mismatch, you may need to adjust either the routing or the material master to ensure they are consistent.
- If the routing needs to be changed, you can do this using transaction code CA02.
Re-run Costing: After making the necessary adjustments, re-run the costing process to see if the error persists.
Check Costing Variant:
- Review the costing variant settings (transaction code OKKN) to ensure that it is set up correctly to handle the units of measure.
Consult Documentation: If the issue persists, consult SAP documentation or reach out to your SAP support team for further assistance.
Related Information:
By following these steps, you should be able to resolve the KOSA204 error and successfully complete the costing process.
Get instant SAP help. Start your 7-day free trial now.
KOSA203
Error creating prelim. cost est. for product cost collector &1
What causes this issue? Errors occurred while the system was creating the preliminary cost estimate for the product cost collector.System Response T...
KOSA202
Preliminary cost estimate for product cost collector &1 created
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
KOSA205
Cost estimate with costing date in the past not allowed
What causes this issue? Preliminary cost estimates for product cost collectors cannot be created for a validity date that is in the past.System Respo...
KOSA206
No product cost collector was costed
What causes this issue? The system could not find a <DS:GLOS.3526B6F2AFAB52B9E10000009B38F974>product cost collector</> that meets the se...
Click on this link to search all SAP messages.