How To Fix /SAPAPO/SOR091 - Retention date could not be determined

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPAPO/SOR -

• Message number: 091

• Message text: Retention date could not be determined

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/SOR091 - Retention date could not be determined ?

  The SAP error message /SAPAPO/SOR091 indicates that the retention date for a specific object could not be determined in the SAP Advanced Planning and Optimization (APO) system. This error typically arises in the context of supply chain planning, where the system needs to calculate or retrieve a retention date for certain materials or products.
  Causes:
  
  
  Missing Master Data: The retention date may not be defined in the master data for the material or product in question. This could include missing information in the material master or other related master data.
  
  
  Configuration Issues: There may be configuration settings in the APO system that are not set up correctly, leading to the inability to determine the retention date.
  
  
  Data Inconsistencies: Inconsistencies in the data between the APO and the ERP system can lead to this error. For example, if the data in the ERP system is not synchronized with the APO system.
  
  
  Planning Version Issues: The planning version being used may not have the necessary data or settings to determine the retention date.
  
  
  Time Period Settings: The time period settings for the planning horizon may not be correctly defined, which can affect the calculation of retention dates.
  
  
  Solutions:
  
  
  Check Master Data: Verify that the master data for the material or product includes all necessary information, including retention dates. Ensure that the material master is correctly maintained in both the ERP and APO systems.
  
  
  Review Configuration: Check the configuration settings in the APO system related to retention dates. Ensure that all necessary settings are correctly defined.
  
  
  Data Synchronization: Ensure that the data between the ERP and APO systems is synchronized. You may need to run data transfer jobs or check for any errors in the data transfer process.
  
  
  Planning Version Review: Make sure that the planning version being used has the correct settings and data. You may need to switch to a different planning version or update the current one.
  
  
  Check Time Period Settings: Review the time period settings in the planning area to ensure they are correctly defined and that the planning horizon is appropriate.
  
  
  Consult Documentation: Refer to SAP documentation or notes related to this error message for any specific guidance or updates that may be relevant.
  
  
  Related Information:
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions to common problems.
  
  
  Transaction Codes: Use transaction codes like /SAPAPO/SDP94 (for planning book) or /SAPAPO/MC62 (for master data) to investigate the relevant data.
  
  
  Support: If the issue persists after checking the above points, consider reaching out to SAP support for further assistance, providing them with detailed information about the error and the context in which it occurs.
  
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.