Do you have any question about this error?
Message type: E = Error
Message class: /LIME/CUST -
Message number: 004
Message text: For ROOT, only a location is allowed as a child
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.
/LIME/CUST004
- For ROOT, only a location is allowed as a child ?The SAP error message
/LIME/CUST004: For ROOT, only a location is allowed as a child
typically occurs in the context of SAP's Logistics Information Management Environment (LIME) or similar modules where hierarchical structures are defined, such as locations, plants, or organizational units.Cause:
This error indicates that there is an attempt to add a child node to a ROOT node in a hierarchy that is not a valid location. In SAP, the ROOT node is expected to have only location-type children, and if you try to add a different type of node (like a material, product, or any other entity that is not a location), the system will throw this error.
Solution:
To resolve this error, you should:
Check the Hierarchy Structure: Review the hierarchy you are trying to create or modify. Ensure that any child nodes under the ROOT node are indeed locations.
Correct Node Types: If you have mistakenly added a non-location node as a child of the ROOT node, you will need to either:
- Remove the incorrect child node.
- Replace it with a valid location node.
Review Configuration: If you are unsure about the types of nodes that can be added, refer to the configuration settings in your SAP system. This may involve checking the customizing settings for the specific module you are working with.
Consult Documentation: Refer to SAP documentation or help resources related to the specific module you are using. This can provide insights into the expected structure and types of nodes.
Testing: After making the necessary changes, test the hierarchy again to ensure that the error does not reoccur.
Related Information:
SPRO
for configuration or specific transaction codes related to LIME.If the issue persists after following these steps, consider reaching out to your SAP support team or consulting with an SAP expert who can provide more tailored assistance based on your specific system configuration and requirements.
Get instant SAP help. Start your 7-day free trial now.
/LIME/CUST003
At a location, an HU is not allowed as a parent
What causes this issue? In a <DS:GLOS.35C290B42AE2052AE10000009B38F9B9>location,</> you can only select either one location or the highes...
/LIME/CUST002
Enter missing key fields
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
/LIME/CUST005
Parent index table does not exist
What causes this issue? The entry does not exist in the index table.System Response The system issues an error message and will not allow you to con...
/LIME/CUST006
Child index table does not exist
INCLUDE /LIME/CUST005 OBJECT DOKU ID NAError message extract from SAP system. Copyright SAP SE. ...
Click on this link to search all SAP messages.