Message type: E = Error
Message class: /SAPAPO/OM_ERROR2 -
Message number: 117
Message text: Creation of persist. pl. version object not possible because client = ' '
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.
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.
/SAPAPO/OM_ERROR2117
- Creation of persist. pl. version object not possible because client = ' ' ?The SAP error message /SAPAPO/OM_ERROR2117 indicates that there is an issue with the creation of a persistent planning version object in SAP Advanced Planning and Optimization (APO). The specific message states that the operation is not possible because the client is not specified or is empty.
Cause: Client Not Specified: The error typically arises when the client information is missing or not properly configured in the system. In SAP, a client is a self-contained unit with separate master records and its own set of tables. Authorization Issues: The user may not have the necessary authorizations to create or modify planning versions in the specified client.
Configuration Issues: There may be configuration issues in the APO system that prevent the creation of the planning version.
Solution: Check Client Configuration: Ensure that the client is correctly specified in the system settings. You can check this in the SAP GUI by navigating to the relevant configuration settings. Verify that the client
Get instant SAP help. Sign up for our Free Essentials Plan.
/SAPAPO/OM_ERROR2116
Error when accessing DLL file information
INCLUDE /SAPAPO/OM_ERROR_GENERAL OBJECT DOKU ID TXError message extract from SAP system. Copyright SAP SE. ...
/SAPAPO/OM_ERROR2115
SessionGlobals not initialized
INCLUDE /SAPAPO/OM_ERROR_GENERAL OBJECT DOKU ID TXError message extract from SAP system. Copyright SAP SE. ...
/SAPAPO/OM_ERROR2118
Key already exists for PlanVersionObject
INCLUDE /SAPAPO/OM_ERROR_GENERAL OBJECT DOKU ID TXError message extract from SAP system. Copyright SAP SE. ...
/SAPAPO/OM_ERROR2119
Mode linkage problem with primary resource
What causes this issue? An application program has called an LCA routine. This led to an error: An order has at least one condition with mode linkage...
Click on this link to search all SAP messages.