How To Fix /CUM/MSG118 - No entry in Customizing table /cum/cunitwerk for plant &

/CUM/MSG118 - Overview

• Message type: E = Error

• Message class: /CUM/MSG -

• Message number: 118

• Message text: No entry in Customizing table /cum/cunitwerk for plant &

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.

/CUM/MSG118 - Details

• The SAP error message /CUM/MSG118 No entry in Customizing table /cum/cunitwerk for plant & typically indicates that there is a missing configuration in the Customizing table related to the specific plant you are trying to work with. This error is often encountered in the context of the SAP Cumulative (CUM) module, which is used for managing various aspects of production and logistics.
  
  Cause:
  
  Missing Configuration: The error suggests that there is no entry in the Customizing table /CUM/CUNITWERK for the specified plant. This means that the system does not have the necessary configuration data for the plant in question.
  Incorrect Plant Code: The plant code you are using may be incorrect or not properly set up in the system.
  Transport Issues: If the configuration was recently transported from another system, it may not have been transported correctly, leading to missing entries.
  
  
  Solution:
  
  
  Check Customizing Table: 
  
  Go to transaction code SE16 or SE11 and check the table