How To Fix /ACCGO/CAS_CALLOFF088 - PO not created; UoM changed during PO creation

SAP Error Message - Details

• Message type: E = Error

• Message class: /ACCGO/CAS_CALLOFF -

• Message number: 088

• Message text: PO not created; UoM changed during PO creation

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message /ACCGO/CAS_CALLOFF088 - PO not created; UoM changed during PO creation ?

  The SAP error message /ACCGO/CAS_CALLOFF088 PO not created; UoM changed during PO creation typically occurs in the context of creating a Purchase Order (PO) in the SAP system, particularly when dealing with the Advanced Compliance Solutions (ACS) module. This error indicates that there was a change in the Unit of Measure (UoM) during the PO creation process, which is not allowed under certain conditions.
  Cause:
  
  
  Unit of Measure Change: The most common cause of this error is that the UoM for the material being ordered has been changed in the system after the initial setup or during the PO creation process. This can happen if:
  
  The material master data was modified.
  The UoM in the purchase requisition or previous documents does not match the UoM in the material master.
  
  
  
  Configuration Settings: There may be specific configuration settings in the SAP system that prevent the creation of POs when there is a discrepancy in UoM.
  
  
  Data Inconsistency: There might be inconsistencies in the data between the material master, the purchase requisition, and the PO.
  
  
  Solution:
  
  
  Check Material Master: Verify the UoM settings in the material master record. Ensure that the UoM is correctly defined and matches the expected UoM for the purchase.
  
  
  Review Purchase Requisition: If the PO is being created from a purchase requisition, check the UoM in the requisition. Ensure it matches the UoM in the material master.
  
  
  Correct UoM: If there is a mismatch, correct the UoM in the relevant document (material master or purchase requisition) before attempting to create the PO again.
  
  
  Consult Configuration: If the issue persists, consult with your SAP configuration team to review the settings related to UoM handling in the purchasing module. They may need to adjust settings to allow for UoM changes under certain conditions.
  
  
  Error Logs: Check the error logs for more detailed information about the error. This can provide insights into what specifically triggered the error.
  
  
  Testing: After making the necessary corrections, test the PO creation process again to ensure that the issue has been resolved.
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance on handling UoM changes.
  Documentation: Review SAP documentation related to purchasing and material management for best practices on managing UoM.
  User Training: Ensure that users involved in the procurement process are trained on the importance of UoM consistency and how to handle changes in the system.
  
  By following these steps, you should be able to resolve the error and successfully create the Purchase Order.