How To Fix AG858 - TM scheduling: APO release &3 not connected; &1 &2: no date/time consist.

SAP Error Message - Details

• Message type: E = Error

• Message class: AG - Nachrichten ATP-Server

• Message number: 858

• Message text: TM scheduling: APO release &3 not connected; &1 &2: no date/time consist.

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 AG858 - TM scheduling: APO release &3 not connected; &1 &2: no date/time consist. ?

  The SAP error message AG858 typically occurs in the context of Transportation Management (TM) and Advanced Planning and Optimization (APO) when there is a scheduling issue related to the release of a transportation order or shipment. The error indicates that the specified APO release is not connected, and there is a lack of date/time consistency between the involved objects.
  Cause:
  
  Disconnected APO Release: The specified APO release (indicated by &3) is not properly linked to the transportation order or shipment (indicated by &1 &2).
  Date/Time Inconsistency: There may be inconsistencies in the dates or times associated with the transportation order, shipment, or the APO release. This could be due to incorrect planning data, changes in the schedule, or missing data.
  Configuration Issues: There might be configuration issues in the integration between SAP TM and APO, leading to the inability to connect the relevant releases.
  
  Solution:
  
  Check APO Release: Verify that the APO release specified in the error message is valid and correctly configured. Ensure that it is active and connected to the relevant transportation order or shipment.
  Review Dates and Times: Check the dates and times associated with the transportation order and the APO release. Ensure that they are consistent and correctly set. Look for any discrepancies that might cause the inconsistency.
  Integration Settings: Review the integration settings between SAP TM and APO. Ensure that the necessary configurations are in place for proper communication and data exchange.
  Reprocess the Order: If the issue persists, consider reprocessing the transportation order or shipment. This may involve re-triggering the planning process to ensure that all data is up to date.
  Consult Documentation: Refer to SAP documentation or notes related to TM and APO integration for any specific guidelines or troubleshooting steps that may apply to your version of SAP.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as /SAPAPO/SDP94 for planning board or /SAPAPO/OM17 for order management, which may help in diagnosing the issue.
  Support: If the problem cannot be resolved internally, consider reaching out to SAP support for assistance, providing them with the error details and any relevant logs.
  
  By following these steps, you should be able to identify the root cause of the AG858 error and implement a solution to resolve it.