How To Fix /ACCGO/UIS_MSG168 - Delivery not found

SAP Error Message - Details

• Message type: E = Error

• Message class: /ACCGO/UIS_MSG -

• Message number: 168

• Message text: Delivery not found

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/UIS_MSG168 - Delivery not found ?

  The SAP error message /ACCGO/UIS_MSG168 Delivery not found typically occurs in the context of the SAP system when a user attempts to access or process a delivery document that does not exist in the system. This can happen for various reasons, including data inconsistencies, incorrect document numbers, or issues with the underlying logistics processes.
  Causes:
  
  Incorrect Delivery Number: The delivery number entered may be incorrect or does not exist in the system.
  Data Deletion: The delivery document may have been deleted or archived, making it unavailable for processing.
  Authorization Issues: The user may not have the necessary authorizations to view or access the delivery document.
  System Configuration Issues: There may be configuration issues in the SAP system that prevent the delivery from being recognized.
  Integration Issues: If the delivery is part of an integrated process (e.g., with EWM or other modules), there may be issues in the integration that prevent the delivery from being found.
  
  Solutions:
  
  Verify Delivery Number: Double-check the delivery number you are trying to access to ensure it is correct.
  Check Document Status: Use transaction codes like VL03N (Display Outbound Delivery) to check if the delivery exists and its status.
  Review Authorizations: Ensure that you have the necessary authorizations to access the delivery document.
  Consult with IT Support: If the delivery should exist but cannot be found, consult with your IT support team to check for any data integrity issues or system errors.
  Check for Archiving: If the delivery has been archived, you may need to retrieve it from the archive or check the archiving settings.
  Review Integration Settings: If the delivery is part of an integrated process, ensure that all related systems are functioning correctly and that there are no errors in the integration.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as VL03N (Display Outbound Delivery), VL02N (Change Outbound Delivery), and VL01N (Create Outbound Delivery).
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Documentation: Review SAP documentation related to logistics and delivery processing for additional context and troubleshooting steps.
  
  If the issue persists after trying the above solutions, it may be necessary to escalate the problem to your SAP support team or consult with SAP directly for further assistance.