/ACCGO/PRC_MC013 - Shadow doc. assgn. UoM not same as assgn. UoM in input interface

Start a new search

SAP Error Message - Details

  • Message type: E = Error

  • Message class: /ACCGO/PRC_MC -

  • Message number: 013

  • Message text: Shadow doc. assgn. UoM not same as assgn. UoM in input interface

  • Show details Hide details


  • 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.


AnswerBot

  • What is the cause and solution for SAP error message /ACCGO/PRC_MC013 - Shadow doc. assgn. UoM not same as assgn. UoM in input interface ?

    The SAP error message /ACCGO/PRC_MC013 indicates that there is a mismatch between the unit of measure (UoM) assigned to a shadow document and the unit of measure in the input interface. This error typically occurs in the context of the SAP General Ledger or during the processing of financial documents, particularly when dealing with materials or inventory management.

    Cause:

    1. Unit of Measure Mismatch: The primary cause of this error is that the unit of measure defined in the shadow document (which is often created during the posting process) does not match the unit of measure that is being used in the input interface (e.g., during a goods movement or invoice posting).
    2. Configuration Issues: There may be configuration issues in the material master or in the settings for the specific transaction that is being processed.
    3. Data Entry Errors: Manual data entry errors can lead to discrepancies in the units of measure.
    4. Inconsistent Master Data: If the material master data is not consistent (e.g., different UoMs defined for the same material in different views), it can lead to this error.

    Solution:

    1. Check Unit of Measure: Verify the unit of measure in both the shadow document and the input interface. Ensure that they match. You can do this by checking the material master data and the transaction data.
    2. Review Material Master Data: Go to the material master (transaction code MM03) and check the UoM settings. Ensure that the base unit of measure and any alternative units of measure are correctly defined.
    3. Adjust Input Data: If the input data is incorrect, correct the unit of measure in the input interface to match the shadow document's UoM.
    4. Configuration Review: If the issue persists, review the configuration settings in the SAP system related to the specific transaction or module. This may involve checking the settings in the customizing (SPRO) for materials management or financial accounting.
    5. Consult Documentation: Refer to SAP documentation or notes related to this specific error message for additional guidance or patches that may address the issue.

    Related Information:

    • Transaction Codes: Familiarize yourself with relevant transaction codes such as MM03 (Material Master), MB1A (Goods Withdrawal), and FB60 (Invoice Entry) to navigate and check the relevant data.
    • SAP Notes: Check SAP Notes for any known issues or updates related to this error message. You can search for the error message number in the SAP Support Portal.
    • User Exits and BAdIs: If custom logic is involved, check for any user exits or BAdIs that might be affecting the processing of the documents.

    By following these steps, you should be able to identify and resolve the cause of the error message /ACCGO/PRC_MC013. If the problem persists, consider reaching out to your SAP support team for further assistance.

  • AnswerBot is an artificial intelligence solution provided by tomco.ai.
    Disclaimer

Related SAP Error Messages

Click the links below to see the following related messages:


SAP messages fall into 3 different categories: Error messages (message type = E), Warnings (W) or Informational (I) messages.

An error message will prevent you from continuing your work - it is a hard stop and you need to fix the error before you can proceed. A warning message will stop your work, however, you can then bypass the warning by pressing the Enter key on your keyboard. That said, it is still good practice to investigate the cause of the warning message and address it. An information message will not stop your work and is truly just for informational purposes.

Click on this link to search all SAP messages.