SAP ABAP IMG Activity SIMG_CFMENUOKCMOKX0 (Create sender structure for master data hierarchies)

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	SIMG_CFMENUOKCMOKX0	Create sender structure for master data hierarchies
Transaction Code	S_ALR_87000262	IMG Activity: SIMG_CFMENUOKCMOKX0
Created on	19981222
Customizing Attributes	SIMG_CFMENUOKCMOKX0	Create sender structure for master data hierarchies
Customizing Activity	SIMG_CFMENUOKCMOKX0	Create sender structure for master data hierarchies

Document

Document Class	SIMG	Hypertext: Object Class - Class to which a document belongs.
Document Name	SIMG_CFMENUOKCMOKX0

Description

EC-EIS/BP data transfer is record-based, i.e. each record can be checked and updated independently of all others. As hierarchies always indicate links between their records, the records in the hierarchy cannot be updated independently. The whole hierarchy has to be updated at once.

However, in the SAP system, the hierarchy data must be transferred independently. In order to keep the relationship between the records, additional information is required with each record.

Example

The following example illustrates which additional information is required to transfer this hierarchy. The example hierarchy is structured as follows:

A X
_________/ ! \__________ / \
B F J Y Z
/ ! \ / \ !
C D E G H K
/ \
L M

This hierarchy can be displayed as follows:

1. Level numbers: Each level of the hierarchy is assigned a level number. The first number is 1.
   
   Level Char. value
   --------------------
   1 A
   2 B
   3 C
   3 D
   3 E
   2 F
   3 G
   3 H
   2 J
   3 K
   4 L
   4 M
   1 X
   2 Y
   2 Z
   The sequence of the records combined with the level number indicates the exact position within the hierarchy.
2. Reference to the superior node (parent):
   
   Char. value Parent
   --------------------
   A (Parent = blank: i.e. no parent)
   C B
   D B
   E B
   L K
   K J
   X
   Y X
   Z X
   B A
   F A
   J A
   G F
   H F
   M K
   Note that the sequence of the records is insignificant. The hierarchical relationship is determined by the parent. As the sequence of the nodes on any one level is not defined, it is not guaranteed that node B will be positioned left of node C. This does not matter for many hierarchies where the position of the nodes on any one level is unimportant.
3. Reference to the superior node (parent) and previous node on the same level (left brother):
   
   Char. value Parent Left brother
   ------------------------------------
   A (blank: does not exist)
   D B C
   C B
   E B D
   L K
   K J
   X
   Y X
   Z X Y
   B A
   F A B
   J A F
   G F
   H F G
   M K L
   The sequence of the records is insignficant here too because the reference to a left brother ensures that all the hierarchy information is available.

The above display types are supported by SAP data transfer.

Requirements

Each of the transfer formats illustrated in the above examples can be tranferred, however, the relevant additional information must also be available. The following fields are required in the sender structure (i.e. per record):

1. For example 1:
   
   Field Value range
   -------------------------------------------
   Hierarchy level 1 to 999
   Char. value String of length 32
2. For example 2:
   
   Field Value range
   -------------------------------------------
   Char. value String of length 32
   Parent String of length 32
3. For example 3:
   
   Field Value range
   -------------------------------------------
   Char. value String of length 32
   Parent String of length 32
   Left brother String of length 32

You cannot change the transfer format (1, 2 or 3) during the transfer of hierarchy.

Further notes

If non-chargeable nodes are transferred at the same time, it is also possible to transfer the appropriate texts. The following fields are required to do this:

Field Value range
-------------------------------------------
Language 1 character
Short text String of length 20
Long text String of length 40

If these fields are filled for chargeable nodes, they will not be taken into account as the master data texts take priority in this case.

The simultaneous transfer of several hierarchies is not supported.

Activities

Define the format of your sender structure. The individual steps to be performed correspond to those for the sender structure for transaction data. Make sure that all necessary additional information and fields have been defined.

You can choose any sequence of fields and field names in your records.

Further notes Transport of settings

Business Attributes

ASAP Roadmap ID	252	Prepare Data Transfer Fields
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	SIMG_CFMENUOKCMOKX0	0	HLA0009491	Data Collection

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
IMGDUMMY	D - Dummy object	OKX0	9999999999	☐	☐	Maint.sender str.for mast.data hier.

History

Last changed by/on	SAP	19981222
SAP Release Created in