SAP ABAP Data Element UG_MD_TR_SYNCH_MASTERDATA (Replicate Master Data 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_MASTERDATA
Short Description Replicate Master Data 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 MasterData 
Medium 15 Master Data 
Long 20 Master Data 
Heading 2 MD 
Documentation

Definition

Use

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

When master data is imported by the transport tool of the application, this data is initially only written to the tables of the application. This system behavior contrasts to that of online maintenance in which the master data is 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 master data 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 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 master data in the BW System. Then you can use this option to modify system behavior so that imports write the master data to both the application tables as well as the BW tables.

You can choose one of two procedures:

  • Overwrite only writes new values to the BW system and updates modified values. This option does not delete any values in BW.
  • Delete All also deletes all values in the BW system that no longer exist in the application tables. However, it is possible to not delete values that are used elsewhere in the BW system, for example in InfoCubes.

Regardless of which option you choose, it does not matter which values the transport request contains. If the request contains entries for a characteristic, the system replicates the entire list of values from the application table into the BW system. The Overwrite option can be recommended particularly if you also maintain values for an InfoObject from outside the workbench, for example by means of an extractor. Otherwise, you should use 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 master data 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 master data of the characteristic to be replicated.
  • The application is responsible for the master data with regards to the respective InfoObject. When a master data item for the characteristic is imported, the system always copies all master data of the characteristic from the application tables to the BW System and thereby deletes any additional values in the BW System.

    Thus, if the application only deals with a portion of the data that has been created in the BW System, or if the application normally maintains the data 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 data after transports take place using the synchronization programs of master data services.

Dependencies

Example

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