How To Fix APPL_MM_IV_MODEL006 - Planned delivery costs are not supported (PO &1 &2)

SAP Error Message - Details

• Message type: E = Error

• Message class: APPL_MM_IV_MODEL -

• Message number: 006

• Message text: Planned delivery costs are not supported (PO &1 &2)

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 APPL_MM_IV_MODEL006 - Planned delivery costs are not supported (PO &1 &2) ?

  The SAP error message APPL_MM_IV_MODEL006, which states "Planned delivery costs are not supported (PO &1 &2)," typically occurs in the context of purchasing and inventory management when there are issues related to planned delivery costs in a purchase order (PO). Here’s a breakdown of the cause, potential solutions, and related information:
  Cause:
  
  
  Planned Delivery Costs Not Supported: The error indicates that the system does not support planned delivery costs for the specific purchase order. This can happen if the configuration settings in the system do not allow for planned delivery costs to be included in the purchase order.
  
  
  PO Type Restrictions: Certain types of purchase orders may not allow for planned delivery costs. For example, standard purchase orders may have different rules compared to subcontracting or stock transport orders.
  
  
  Configuration Issues: The configuration settings in the SAP system related to purchasing and inventory management may not be set up to handle planned delivery costs.
  
  
  Document Type: The document type of the purchase order may not be configured to allow planned delivery costs.
  
  
  Solution:
  
  
  Check PO Configuration: Review the configuration settings for the purchase order type in the SAP system. Ensure that the settings allow for planned delivery costs.
  
  
  Review Document Type Settings: Check the settings for the specific document type of the purchase order. You may need to adjust the settings to enable planned delivery costs.
  
  
  Consult SAP Notes: Look for relevant SAP Notes that may address this specific error. SAP frequently releases notes that provide solutions or workarounds for known issues.
  
  
  Adjust PO: If planned delivery costs are not necessary for the transaction, consider adjusting the purchase order to remove any planned delivery costs.
  
  
  User Authorization: Ensure that the user has the necessary authorizations to create or modify purchase orders with planned delivery costs.
  
  
  Contact SAP Support: If the issue persists after checking the configuration and settings, consider reaching out to SAP support for further assistance.
  
  
  Related Information:
  
  SAP Documentation: Review the SAP Help Portal for documentation related to purchasing and planned delivery costs.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as ME21N (Create Purchase Order), ME22N (Change Purchase Order), and ME23N (Display Purchase Order) to troubleshoot the issue.
  Community Forums: Check SAP Community forums or other user groups for discussions related to this error message, as other users may have encountered and resolved similar issues.
  
  By following these steps, you should be able to identify the cause of the error and implement a suitable solution.