How To Fix /SAPAPO/TDL_DAO147 - Inconsistency: purchase requisition w/o corresponding planned ord. in LC

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPAPO/TDL_DAO -

• Message number: 147

• Message text: Inconsistency: purchase requisition w/o corresponding planned ord. in LC

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/TDL_DAO147 - Inconsistency: purchase requisition w/o corresponding planned ord. in LC ?

  The SAP error message /SAPAPO/TDL_DAO147 indicates an inconsistency in the system where a purchase requisition exists without a corresponding planned order in the Logistics Chain (LC). This typically occurs in the context of Advanced Planning and Optimization (APO) when there is a mismatch between the planning data and the procurement data.
  Cause:
  
  Data Inconsistency: The most common cause is that a purchase requisition was created but the corresponding planned order was not generated or has been deleted.
  Master Data Issues: There may be issues with the master data, such as incorrect material master records or vendor information.
  Planning Run Issues: If the planning run did not execute correctly, it may not have generated the planned orders as expected.
  Manual Changes: Manual changes to purchase requisitions or planned orders can lead to inconsistencies if not properly synchronized.
  
  Solution:
  
  Check Purchase Requisition: Verify the purchase requisition in the system to ensure it is valid and has not been deleted or modified incorrectly.
  Check Planned Orders: Look for the corresponding planned order in the system. If it does not exist, you may need to run the planning process again to generate it.
  Run Planning: Execute the planning run in APO to ensure that all planned orders are generated based on the current purchase requisitions.
  Consistency Check: Use transaction codes like /SAPAPO/TSM (Transaction Data Consistency Check) to identify and resolve inconsistencies in the system.
  Review Master Data: Ensure that all relevant master data (material, vendor, etc.) is correctly maintained and up to date.
  Consult Logs: Check the logs for any errors or warnings during the planning run that might indicate why the planned order was not created.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as /SAPAPO/TSM, /SAPAPO/SDP, and /SAPAPO/MC for monitoring and managing planning data.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Documentation: Review SAP documentation on APO and the specific planning processes to understand how purchase requisitions and planned orders are managed.
  Support: If the issue persists, consider reaching out to SAP support or your internal SAP team for further assistance.
  
  By following these steps, you should be able to identify the root cause of the inconsistency and take appropriate actions to resolve the error.