Object documentationDerivation Hierarchy

 

Hierarchy of object types that need to be reorganized entirely. This hierarchy shows the dependencies of these object types in terms of their content: It describes how the profit center is determined when an object of an object type is created.

 

On the basis of the object types, transactions in General Ledger Accounting are posted to the profit centers that need to be corrected by the reorganization.

Structure

Hierarchy Levels in the Derivation Hierarchy

The derivation hierarchy can be displayed as a tree structure with different hierarchy levels. There are objects on the first level of the derivation hierarchy and objects on its lower levels:

  • For objects on the first level of the derivation hierarchy, the user enters the profit center directly; the profit center is therefore not inherited from another object.

  • When objects from the lower levels of the derivation hierarchy are created, they inherit the profit center from a different object.

This is demonstrated in the following examples.

Example Example

When creating a material, you specify the profit center directly in the material master record (the assignment is therefore independent of other object types). The object type Material is therefore located on the first level of the derivation hierarchy.

When an unassigned purchase order item is created, it obtains the profit center from the ordered material. Consequently, the object type Purchase Order (Unassigned) is found in the derivation hierarchy beneath the object type Material.

This is portrayed in the following graphic:

End of the example.

Example Example

When a sales order item is created, the profit center is proposed from the material master of the ordered material.

In the tree structure, there is therefore the node Sales Order Item beneath the node Material because the profit center is inherited, and the sales order item needs to receive in this case the same new profit center as the material during reorganization.

On the other hand, you can manually overwrite the proposed value for the profit center when you create the sales order item. This case is also portrayed in the derivation hierarchy: There is also the node Sales Order Item on the first level of the hierarchy.

End of the example.
Versions

The reorganization works with one version of a derivation hierarchy (called the hierarchy version). SAP delivers a standard version (version 001) that you cannot modify. You can display this standard version in Customizing for General Ledger Accounting (New) under Start of the navigation path Reorganization Next navigation step Basic Settings Next navigation step Remove Object Types from Derivation Hierarchy End of the navigation path.

You have the following options for creating your own derivation hierarchy versions:

  • You can make small adjustments to the standard version of the derivation hierarchy. For this, you create a copy of the standard version and remove from this copy any object types that you do not need (in Customizing for the Reorganization under Start of the navigation path Basic Settings Next navigation step Remove Object Types from Derivation Hierarchy End of the navigation path).

  • You can define a totally different derivation hierarchy version that can contain its own object types or use different hierarchical relationships between the object types.

    You define such hierarchy versions in Customizing for the Reorganization under Start of the navigation path Basic Settings Next navigation step Settings for Experts Next navigation step Define Own Version of Derivation Hierarchy End of the navigation path.

    You define your own reorganization object types in Customizing for the Reorganization under Start of the navigation path Basic Settings Next navigation step Settings for Experts Next navigation step BAdI: Enhancement of Reorganization Object Types End of the navigation path (BAdI FAGL_R_OBJ_TYPE_BADI).

You can activate or deactivate any version of the derivation hierarchy, as required.

Integration

The following applies during the creation of a reorganization plan:

  • If there is only one active version of the derivation hierarchy, the system automatically uses this version.

  • If there is more than one active version of the derivation hierarchy, you have to specify the version that is used.