Do you have any question about this error?
Message type: E = Error
Message class: IL - PM: ILOM - Functional Locations
Message number: 813
Message text: A hierarchy level must be under the last character of a block
You have either
not entered a hierarchy level under the last edit character of a block
of edit characters surrounded by two separators
or
not completed the entry of the hierarchy levels with a character flush
with the last block of the edit mask.
INCLUDE 'KEINE-VERARBEITUNG' OBJECT DOKU ID TX LANGUAGE E
Correct the entry of the hierarchy levels:
Ensure that every block consisting of edit characters that is
surrounded by two separators ends with a hierachy level under the last
edit character.
Complete the entry of the hierarchy levels with a hierarchy level that
is flush with the last block in the edit mask.
Error message extract from SAP system. Copyright SAP SE.
IL813
- A hierarchy level must be under the last character of a block ?The SAP error message IL813, which states "A hierarchy level must be under the last character of a block," typically occurs in the context of creating or modifying a hierarchy in the SAP system, particularly in the area of logistics or master data management.
Cause:
This error usually arises when there is an issue with the structure of the hierarchy you are trying to create or modify. Specifically, it indicates that the hierarchy level you are trying to define is not correctly positioned under the last character of a block. This can happen due to:
- Incorrect Hierarchy Structure: The hierarchy levels may not be properly aligned or defined according to the expected structure.
- Missing Parent Node: The level you are trying to create may not have a valid parent node, or the parent node may not be defined correctly.
- Improper Level Definition: The level you are trying to add may not be defined as a child of the correct parent level.
Solution:
To resolve the IL813 error, you can take the following steps:
Check Hierarchy Structure: Review the hierarchy structure you are trying to create. Ensure that each level is correctly defined and positioned under its respective parent node.
Verify Parent Nodes: Make sure that the parent nodes for the levels you are trying to create exist and are correctly defined. Each child level must have a valid parent.
Adjust Level Definitions: If you are trying to add a new level, ensure that it is correctly defined as a child of the last character of the block. You may need to adjust the level definitions to ensure they follow the correct hierarchy.
Use Transaction Codes: If you are using specific transaction codes (like IL01, IL02, IL03 for creating, changing, or displaying hierarchies), ensure that you are following the correct steps and guidelines for those transactions.
Consult Documentation: Refer to SAP documentation or help resources for guidance on creating and managing hierarchies. This can provide insights into the expected structure and any specific requirements.
Testing: After making adjustments, try to save or execute the hierarchy creation/modification again to see if the error persists.
Related Information:
By following these steps, you should be able to identify the cause of the IL813 error and implement a solution to resolve it.
Get instant SAP help. Start your 7-day free trial now.
IL812
There are levels outside the area of the edit mask
What causes this issue? The number of hierarchy levels entered is longer than the edit mask.System Response INCLUDE 'KEINE-VERARBEITUNG' O...
IL811
The numbering of the hierarchy levels is incorrect
What causes this issue? The numbering of the hierarchy levels in your edit mask is incorrect.System Response INCLUDE 'KEINE-VERARBEITUNG' ...
IL814
A hierarchy level must not end with a separator
What causes this issue? You have entered a hierararchy level with a separator at the end.System Response INCLUDE 'KEINE-VERARBEITUNG' OBJE...
IL815
The entered level &1 is greater than the highest hierarchy level &2
What causes this issue? You want to define hierarchy level &V1& as the identifying level of the functional location. However, the structure o...
Click on this link to search all SAP messages.