SAP ABAP Data Element RLEVL (Posting level)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM (Application Component) Customer Relationship Management
⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷
GBAS (Package) FI-SL Customizing / integration / Basis
⤷
⤷
⤷
Basic Data
| Data Element | RLEVL |
| Short Description | Posting level |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | RLEVL | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Post.lvl |
| Medium | 15 | Post.level |
| Long | 20 | Posting level |
| Heading | 1 | P |
Documentation
Definition
The system distinguishes between postings according to posting levels.
There are thus four levels of posting:
- Standardizing entries have posting level 1 and are company-specific.
- When a consolidation posting takes place between two affiliate companies, two companies will always be involved in the account assignment transaction. This posting type, also described as <GL: eliminating entry>eliminating entries then has the level 2. This includes, for example, the postings for <GL:elimination of intercomany payables and receivables>eliminating intercompany payables and receivables.
- Posting level 3 is used for postings that are valid only within one subgroup. These are <GL:consolidating entries>consolidating entries affecting one or more of the companies in a subgroup.
- The postings on level 4 are consistent with those at level 3, except for one significant difference: the additional trading partner assignment. These are also consolidating entries, except that the trading partners concerned do not belong to the subgroup. One example would be a reclassification of receivables against affiliates into receivables against third parties. You could thus ensure that only those amounts that are assigned to third parties would be reclassified.
History
| Last changed by/on | SAP | 20100310 |
| SAP Release Created in |