SAP ABAP Data Element UG_MD_TR_SYNCH_HIERARCHY (Replicate Hierarchies During Import)
Hierarchy
☛ FINBASIS (Software Component) Fin. Basis
   ⤷ FIN-FB (Application Component) Financials Basis
     ⤷ UGMD0 (Package) FIN General: Master Data
Basic Data
Data Element UG_MD_TR_SYNCH_HIERARCHY
Short Description Replicate Hierarchies During Import  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type UG_MD_TR_SYNCH_MODE    
Data Type CHAR   Character String 
Length 1    
Decimal Places 0    
Output Length 1    
Value Table      
Further Characteristics
Search Help: Name    
Search Help: Parameters    
Parameter ID   
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 10 Hier. 
Medium 15 Hierarchies 
Long 20 Hierarchies 
Heading 5 Hier. 
Documentation

Definition

Use

Choose this option to replicate the imported hierarchies for a characteristic in the hierarchy storage location of the corresponding InfoObject in the BW System.

When hierarchies are imported by the transport tool of the application, these hierarchies are initially only written to the tables of the application. This system behavior contrasts to that of online maintenance in which the hierarchies are automatically written to the tables of the application as well as the tables of the BW InfoObject. The reason for these differences is that during an import of hierarchies the system is not always sure that the corresponding BW Content is active or that the RFC destination for the BW System has been maintained and functions. This is often NOT the case especially when the system is being initially built.

Before you choose this option, first make sure that all conditions exist for a replication of hierarchies in the BW System. Then you can use this option to modify system behavior so that imports write the hierarchies to both the application tables as well as the BW tables.

You can choose one of two procedures:

  • Overwrite only writes new hierarchy edges to the BW system and updates modified hierarchy edges. This option does not delete any hierarchy edges in BW.
  • Delete All replicates all hierarchies as a whole in the BW system.

Regardless of which option you choose, it does not matter for which hierarchies the transport request contains specific changes. If the request contains entries with hierarchy information for a characteristic, the system replicates all hierarchies of that characteristic from the application table into the BW system. The Overwrite option is useful only in rare circumstances. Typically you would choose the Delete All option.

Before activating this option for a characteristic, make sure that the following has taken place:

  • You have activated the corresponding InfoObject in the BW System.
  • The RFC destination that enables the application to access the BW System is correct and functions. If different RFC destinations are used in the source and target systems of the transport, then the transport may not simultaneously contain the assignment of the RFC destination and the hierarchies of the characteristic to be replicated. Once you have transported the assignment of the RFC destination, in this case you must first adjust the RFC destination. Then you can again import hierarchies of the characteristic to be replicated.
  • The application is responsible for the hierarchies with regards to the respective InfoObject. When a portion of the hierarchy concerning the characteristic is imported, the system always copies all of the hierarchies of the characteristic from the application tables to the BW System and thereby deletes any additional entries in the BW System.

    Thus, if the application only deals with a portion of the hierarchies that have been created in the BW System, or if the application normally maintains the hierarchies in BW and then transfers them into the application tables, then you should not choose this option.

As an alternative to this option, you can manually synchronize the hierarchies after transports take place using the synchronization programs of master data services.

Dependencies

If you replicate the hierarchies in the BW System during an import, you must do the same for the master data of the characteristic as well.

Example

History
Last changed by/on SAP  20041006 
SAP Release Created in 300