Structure of Subobject Hierarchy for Target Agreements 

Use

During the additional commission case run, the system generates a commission case for target agreements. The commission case is calculated for a specific period, as well as all complex target types of an individual contract, for the commission case trigger. However the structure of the hierarchy for subobjects and activities is not created before the commission case, as is the case for additional cases, but during the commission case process. This means that if the structure of the hierarchy has been incorrectly created, you have the opportunity of correcting it with minimum amount of manual processing.

Integration

The structure of the hierarchy for subobjects and activities is created in the commission case with program DETERMIN_OBJECTS in the new process step of the subobject enrichment, in function module <APPL>_CASE_VERS_CREATE. The subobject hierarchy is stored in the internal table META_OBJECTDATA during runtime. Activities receive the same structure as subobjects, and it is made up of a combination of participation and newly determined subobjects.

Schematic Display of Calling Sequence

With program DETERMIN_OBJECTS the system checks if the structure of the subobject hierarchy is already created, in other words if table META_OBJECTDATA is already filled. If this is not the case, the structure of the subobject hierarchy is created and the subobjects are filled with values. Then the structure of activities is created out of a combination of participation and subobjects.

This process is handled by a logical service (OTC 33 and methods 01 Enhance Object Data & 02 Enhance Activities); the tool is assigned to the processed business object category. The logical service is encapsulated with the following programs and function modules:

●     ENRICH_COMMISSION_CASE

●     <APPL>_CASE_ENRICH_SUBOBJECTS

●     <APPL>_CASE_ENRICH_ACTIVITIES

For target agreements, the standard delivery includes sample Customizing with business object category 830 and assigned tool TARGET AGREEMENT CASE (OTC 33), with function 20 Enhancement of Commission Case with Subobjects and function module CACS26_TGT_CASE_ENHANCE_OBJECT as well as method 21 Enhancement of Commission Case With Activities and function module CACS26_TGT_CASE_ENHANCE_ACTIV.

Structure of Subobject Hierarchy for Target Agreements in Subobject Enrichment

Two-level or three-level subobject hierarchies can be created and filled for target agreements as in the following examples:

●     Variant 1:

○     Subobject type (SO type) 82000 is assigned to business object category 830 (target agreements).

○     Business object category 830 is assigned to commission case trigger type YEAR for target agreements.

○     Subobject type 82001 (complex target type) is subordinate to subobject type 82000.

○     Subobject type 82001 (elementary target type) is subordinate to subobject type 82000.

○     Subobject type 82001 and trigger type YEAR are assigned to complex target types 0001 and 0002.

○     The subobject hierarchy in the commission case has three levels:

●     Variant 2:

○     Subobject type 82000 is assigned to business object category 830 (target agreements).

○     Subobject type 8200 is also assigned to the complex target type.

○     Business object category 830 is assigned to commission case trigger type YEAR for target agreements.

○     Subobject type 82002 (elementary target type) is subordinate to subobject type 82000.

○     Subobject type 82000 and trigger type YEAR are assigned to complex target types 0001 and 0002.

○     The subobject hierarchy in the commission case has two levels: