How To Fix /SAPAPO/TSM779 - Exception created successfully

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPAPO/TSM -

• Message number: 779

• Message text: Exception created successfully

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 /SAPAPO/TSM779 - Exception created successfully ?

  The SAP error message /SAPAPO/TSM779 Exception created successfully is not an error in the traditional sense; rather, it indicates that an exception has been created successfully in the SAP Advanced Planning and Optimization (APO) module. This message typically appears in the context of the Transportation Load Builder (TLB) or similar planning processes where exceptions are generated to handle specific scenarios or issues in the planning process.
  Cause:
  The message indicates that the system has successfully created an exception for a specific planning situation. This could be due to various reasons, such as:
  
  Planning Constraints: The system may have identified constraints in the planning process that require attention.
  Resource Limitations: There may be limitations in resources (e.g., transportation capacity) that necessitate the creation of an exception.
  Demand and Supply Mismatch: The system may have detected a mismatch between demand and supply, prompting the creation of an exception for further analysis.
  
  Solution:
  Since this message indicates successful creation rather than an error, the next steps typically involve:
  
  Reviewing Exceptions: Check the exceptions created in the system to understand the underlying issues. This can be done through the relevant transaction codes or reports in SAP APO.
  Analyzing the Cause: Investigate the specific reasons for the exceptions. This may involve looking at demand forecasts, supply availability, transportation capacities, etc.
  Taking Action: Based on the analysis, take appropriate actions to resolve the issues. This could involve adjusting planning parameters, reallocating resources, or modifying demand/supply plans.
  Monitoring: After addressing the exceptions, continue to monitor the planning process to ensure that similar issues do not arise in the future.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes in SAP APO, such as /SAPAPO/TSM for transportation planning and /SAPAPO/DP for demand planning.
  Documentation: Refer to SAP documentation and help resources for detailed information on exception handling in APO.
  User Exits and BAdIs: If you need to customize the behavior of exception handling, consider exploring user exits or Business Add-Ins (BAdIs) related to transportation planning.
  
  If you encounter further issues or specific scenarios related to this message, it may be beneficial to consult with your SAP support team or refer to SAP Notes for any known issues or updates.