Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
KC (Package) Cost Accounting Controlling EIS
IMG Activity
| ID | OKCM_OKX9 | Maintain Hierarchy Directory |
| Transaction Code | S_ALR_87000228 | IMG Activity: OKCM_OKX9 |
| Created on | 19981222 | |
| Customizing Attributes | OKCM_OKX9 | Maintain Hierarchy Directory |
| Customizing Activity | OKCM_OKX9 | Maintain Hierarchy Directory |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OKCM_OKX9 |
In this step you can maintain the display of the master data and reference hierarchies in reporting.
You can recognize the master data hierarchies created in EIS with the hierarchy class EIS. The variant is stored as part of the hierarchy name e.g. COUNTRY1 COUNTRY1 001.
The other hierarchies are standard hierarchies from other applications that can be used for reporting purposes, if you have created a characteristic with the same domain in EIS. Possible reference hierarchies, that you can use in EIS are
Cost center hierarchy (domain KOSTL)
Cost element hierarchy (domain KSTAR)
Profit center hierarchy (domain PRCTR)
Company grouping (domain RCOMP)
Financial statement version (domain ERGSL)
HR Organizational unit (domain ORGEH)
In the field "med-length key" you can enter a text, that is displayed with the selection of the hierarchy in reporting. This is especially important, if several hierarchies or variants exist for the same characteristic.
In the field "H mode" you enter whether is not allowed to be selected (0), can be selected (1 or 2) or must be selected (3) in the maintenance of the report. The last possibility is mainly used with hierarchies in applications, in which a so-called compulsory hierarchy is present.
In the "H. displ." field, you determine with which structure display the hierarchy should be displayed in the report. If you do not make an entry here a linear display will be used as a default.
In the "Level" field you enter to which level should be exploded when executing the report.
Example
Requirements
Standard settings
Recommendation
Activities
Set how the master data and reference hierarchies are to be displayed in reporting.
Further notes
Business Attributes
| ASAP Roadmap ID | 207 | Establish Reporting |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | OKCM_OKX9 | 0 | HLA0009495 O | |
| SIMG | OKCM_OKX9 | 1 | HLA0009493 | Interactive Drilldown Reporting |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| OKX9 | T - Individual transaction object | OKX8 | OKX8 | Display Hierarchy Directory | ||
| OKX9 | T - Individual transaction object | OKX9 | OKX9 | Maintain Hierarchy Directory |
History
| Last changed by/on | SAP | 19981222 |
| SAP Release Created in |
