How To Fix /PLMI/PPEENG104 - Creation of &1 &2 to &3 &4 not allowed

SAP Error Message - Details

• Message type: E = Error

• Message class: /PLMI/PPEENG -

• Message number: 104

• Message text: Creation of &1 &2 to &3 &4 not allowed

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 /PLMI/PPEENG104 - Creation of &1 &2 to &3 &4 not allowed ?

  The SAP error message /PLMI/PPEENG104 Creation of &1 &2 to &3 &4 not allowed typically occurs in the context of the SAP Production Planning and Control (PP) module, particularly when dealing with the creation of production orders, process orders, or similar objects. The placeholders &1, &2, &3, and &4 in the error message will be replaced with specific values that indicate the type of object and the reason for the restriction.
  Cause:
  The error message generally indicates that there is a restriction or a configuration setting that prevents the creation of a specific object. Common causes include:
  
  Status Restrictions: The object you are trying to create may be in a status that does not allow further processing or creation of related objects.
  Configuration Settings: Certain configuration settings in the system may restrict the creation of specific types of orders or objects based on business rules.
  Missing Authorizations: The user may not have the necessary authorizations to create the specified object.
  Dependencies: There may be dependencies or prerequisites that have not been met, such as missing master data or incomplete previous processes.
  
  Solution:
  To resolve the error, consider the following steps:
  
  Check Object Status: Review the status of the object you are trying to create. Ensure that it is not in a status that prohibits creation.
  Review Configuration: Check the configuration settings in the relevant customizing transactions (e.g., OPL1 for production order types) to see if there are any restrictions in place.
  User Authorizations: Verify that the user has the necessary authorizations to create the object. This can be checked in transaction SU53 or by consulting with your security team.
  Check Dependencies: Ensure that all prerequisites for creating the object are met. This may include checking for required master data, such as material master records or routing information.
  Consult Documentation: Look into SAP documentation or notes related to the specific error message for additional insights or known issues.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as CO01 (Create Production Order), CO02 (Change Production Order), and CO03 (Display Production Order).
  SAP Notes: Search for SAP Notes related to the error message for any patches or updates that may address the issue.
  Support: If the issue persists, consider reaching out to SAP support or your internal SAP support team for further assistance.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.