Hierarchy

⤷

⤷

Basic Data
Data Element | IAOM_CONTROLLING_LEVEL |
Short Description | Controlling Level |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | IAOM_AT_LEVEL | |
Data Type | NUMC | Character string with only digits |
Length | 2 | |
Decimal Places | 0 | |
Output Length | 2 | |
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 | Cntrl.Lev. |
Medium | 20 | Controlling Level |
Long | 20 | Controlling Level |
Heading | 20 | Controlling Level |
Documentation
Definition
This determines the Controlling level.
Use
CRM Service:
Here you have the option to choose between the Controlling levels Transaction and Item. For the Controlling type Mass-Object Controlling, the Controlling level is not relevant.
cProjects:
Here you have the option to choose a Controlling level from the interval 1 - 99. For PS projects to be created automatically, the Controlling level specifies the lowest level of the PS project.
Dependencies
CRM Service: Warnung
If you choose Item as the Controlling level, this can lead to performance problems with large volumes of data. We therefore recommend you choose Transaction as the Controlling level.
cProjects:
In cProjects, the Controlling type is derived from the Controlling method.
Example
CRM Service:
For service contracts, Controlling on item level makes sense.
Supplementary Documentation - IAOM_CONTROLLING_LEVEL0000
Use
You use the Controlling level to specify the hierarchy level to which account assignments should be possible. For PSP projects to be created automatically, the Controlling level specifies the lowest level of the PS project. If there are even lower levels in the cProjects project, these are combined for Controlling püurposes on the lowest level of the PS project.
You can choose from the interval 1 - 99. For manual, hierarchical Controlling, you require no Controlling level.
Dependencies
Bei cProjects wird die controlling type aus der controlling method abgeleitet.
Example
Supplementary Documentation - IAOM_CONTROLLING_LEVEL0001
Use
For the Controlling type Mass Controlling, the Controlling level is not relevant.
Dependencies
Warning:
If you choose Item as Controlling level, this can lead to performance problems with large volumes of data. We therefore recommend you use Transaction as the Controlling level.
Example
For service contracts, Controlling on item level makes sense.
History
Last changed by/on | SAP | 20031111 |
SAP Release Created in |