Setting Up Initial Load

MDG-F supports the option to initially upload accounts, companies, cost centers, cost elements and profit centers from your MDG target systems into your MDG hub system.

The extraction of the master data in the MDG target system is performed by the generic MDM extractor (MDMGX). The upload of the master data in the MDG hub system is performed by the MDG data import framework (DIF). MDG-F provides content for both.

Process

Setting up MDMGX in client systems

MDG-F uses transaction MDMGX for the extraction of master data from SAP MDG target systems. To set up MDMGX, perform the following:

Apply the SAP Notes 1783851, 1880169 and 2134044 in the target systems.
Download the required MDMGX configuration text file from SAP Note 2151430. The note includes a detailed how-to document about MDMGX setup and execution.
Run transaction MDMGX in the client systems.

Choose Define Object Types. Check that the object types in the following table exist in your system. The object types are predefined by SAP. If they do not exist, create the missing entries. Afterwards, navigate back to the main menu of the transaction.

Object Type	Description
Account	Chart of Account & G/L Account
Company	Company
CostCenter	Cost Center
CostElement	Cost Element
GroupAccount	Group Account
ProfitCenter	Profit Center

Choose Define Repositories and FTP Servers. Check if there is an entry with the attribute Log. Repository Name defined as SAP_MDG_TEMPLATE. If it is available, you can use this entry as a template for defining your own repositories. You can use the Copy button to create a new repository from the template. Each master data object that you want to extract requires a specific repository.

If the template does not exist, you can create a new repository. Define the attributes of the new repository according to the master data object that you want to extract. The table below shows the entries for the MDG-F objects. Define attributes Clnt Code and Remote System Type according to your specific systems. Other attributes may use the values as shown in the table. It is absolutely mandatory that the repository name starts with MDG_.

Log. Repository Name	Object Type	Repository Name (Code)
MDG_ACCOUNT	Account	MDG_Account
MDG_COMPANY	Company	MDG_Company
MDG_COSTCENTER	CostElement	MDG_CostElement
MDG_COSTELEMENT	CostCenter	MDG_CostCenter
MDG_GROUPACCOUNT	GroupAccount	MDG_GroupAccount
MDG_PROFITCENTER	ProfitCenter	MDG_ProfitCenter

Choose Upload Ports and Check-Tables. Upload the configuration text file and perform the following:
1. Define the object type as Account.
2. Browse the configuration text file.
3. Select the Remove Header Line checkbox.
4. Execute the upload and go back to the main menu
Define the function modules for the cost elements as follows:
1. Choose Define Function Module Parameters for Exceptional Cases and search without attributes.
2. Choose the Create button, and enter CostElement as the object type and MDM_ERP_CELEM_EXTR as the function module. Do not provide an input parameter.
3. Save your entries.
4. Repeat the procedure for the function module MDM_ERP_CELEM_DESCR_EXTR.
The predefined content of the configuration text file has to be adapted according to the master data that shall be extracted. Refer to the how-to guide of SAP Note 2151430 for details.

Setting up DIF in MDG systems
DIF requires at least two types of file directories on the application server:
- One directory for each object type to store the files to be imported.
- One directory for all object types to store the archived files that have been imported.
Perform the following:
1. Create the physical directories on the application server and map them to logical directories using transaction FILE.
2. Run transaction MDGIMG. Configure the directories in the Customizing activity under Master Data Governance, Central Governance General Settings Data Transfer Define File Source and Archive Directories for Data Transfer .