Hierarchy

⤷

⤷

IMG Activity
ID | FAGL_R_DERH | Define Own Version of Derivation Hierarchy |
Transaction Code | S_EB5_05000174 | (empty) |
Created on | 20090226 | |
Customizing Attributes | FAGL_R_DERH | Define Own Version of Derivation Hierarchy |
Customizing Activity | FAGL_R_DERH | Define Own Version of Derivation Hierarchy |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | FAGL_R_DERH_DC |
Use
SAP delivers version 001 of the derivation hierarchy (standard derivation hierarchy version).
In this activity, you can copy standard derivation hierarchy version 001 and then make changes or additions to the copy.
Requirements
The implementation of the Business Add-In BAdI: Enhancement of Reorganization Object Types (FAGL_R_OBJ_TYPE_BADI) must match the structure of the active derivation hierarchies.
All hierarchy versions for which the Version Is Active indicator is set are active.
Standard settings
Standard derivation hierarchy version 001 can be used in the production system. However, we recommend making a copy of the standard derivation hierarchy version and removing from the copy any object types that are not used.
Standard derivation hierarchy version 001 cannot be changed.
Activities
- Copy derivation hierarchy version 001.
- To enable the copy of the derivation hierarchy version to be selected in the reorganization plan, set the Version Is Active indicator for the copy. Deselect this indicator for derivation hierarchy version 001.
We recommend only setting the "Version Is Active" indicator for one hierarchy version. In this way, this hierarchy version is applied automatically when you create a reorganization plan. This makes it easier to maintain a reorganization plan.
- To navigate to the detail window, choose the Hierarchy pushbutton for the copy of the derivation hierarchy version.
- Adjust the hierarchy accordingly. You can remove, move, and rearrange branches and subbranches or create new ones.
Important: Great care needs to be taken when moving branches and subbranches or creating new branches. This is because the system cannot ensure that the hierarchy is semantically correct, nor can it ensure that the hierarchy matches the implementation of the BAdI FAGL_R_OBJ_TYPE_BADI.
- Return to the overview screen.
- Save your changes.
Example
Business Attributes
ASAP Roadmap ID | 203 | Establish Master Data |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 1 | Critical |
Country-Dependency | A | Valid for all countries |
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 |
V_FAGL_R_DERH | V - View | SM30 |
History
Last changed by/on | SAP | 20100311 |
SAP Release Created in | 605 |