Skip to main content

Prerequisite Tasks for Replicating Master Data

Before you install SAP Central Finance Master Data Replication by insightsoftware for SAP S/4HANA for replicating master data, ensure that the following tasks are complete:

  • Review the system requirements, and ensure that your setup meets the minimum requirements.
  • Copy the compressed file Master Data Replication-<VersionNumber> to the computer on which you want to install Master Data Replication.
  • Create the staging database named MAG_SC_STG. The database objects, such as tables, views, and stored procedures are created in the staging database. The required roles are as follows:
    • CONTENT_ADMIN
    • MODELING
    • MONITORING
  • Create a user named MAGS4HDBUSR for the remote SDA connection from the staging database into SAP S/4HANA. The user must have read access to all the SAP S/4HANA tables in SAP S/4HANADB schema/user.

    Note: The name of the SAPHANADB schema may differ for each customer. This is the core schema that contains all the tables and can be found in the System Status window.

  • Assign the SAP GUI user the SAP_BR_EMPLOYEE role and ensure that the user has access to the SAP Fiori query browser and the/MAGSH/RECON_REPORTS role.

Configure a partner profile in SAP S/4HANA to ensure that data load is performed for the cost center and GL account entities using IDocs. Perform the following steps to configure a partner profile:

  1. Open the SAP S/4HANA system as an administrator.
  2. In the WE20 transaction code, create an LS type partner profile for the logical system by setting up the inbound parameters for each IDoc message type as shown in the following table.
    Message Category Process Code

    GLMAST (For GL account)

    GLMA

    COSMA (For cost center)

    COSM
  3. Create a cross-system company code and then assign it to your actual company code using the transaction code SALE.

For more information about creating partner profiles, see SAP Documentation.

Important: We recommend that you do not install more than one instance of Master Data Replication on your computer.

Prerequisite Tasks for Microsoft Dynamics 365 Finance and Operations as Source System

Before performing the prerequisite tasks for setting up Microsoft Dynamics 365 Finance and Operations as your source system, it's important to understand the Data Management Framework or DMF.

The DMF is a standard tool in Microsoft Dynamics 365 Finance and Operations that can be used to import, export, and copy data (setup, configurations, references, master, and document data). You require the DMF to export the Transaction data and Master Data into Azure SQL Database from where the exported data will be loaded into the staging database. The following procedure includes DMF from Step 9 onwards.

  1. Create an LCS project by referring to Start a new LCS project.

  2. If you don't have an Azure subscription, create one, and add it to your LCS project by referring to Add an Azure subscription to an LCS project .
  3. Refer to Deploy and access development environments and deploy cloud hosted environment in the LCS project.
  4. Connect to the RDP environment or VM created by the cloud hosted environment.
  5. Import either the AXPP files placed in the SCT/MSFTD365/custom Entities folder in to a new solution or Microsoft Visual Studio Solution (.sln) as a solution in the Finance and Operations environment in Visual Studio. The custom entities are as follows:
    • ISWAccountingDistribution
    • ISWCompanyInfo
    • ISWCustInvoiceJour
    • ISWCustInvoiceTrans
    • ISWCustPackingSlipJour
    • ISWCustSettlement
    • ISWCustTable
    • ISWCustTrans
    • ISWDimensionAttribute
    • ISWDimensionAttributeValue
    • ISWDimensionFinancialTag
    • ISWDimensionAttributeValueCombination
    • ISWDirPartyPostalAddress
    • ISWDirPartyTable
    • ISWDirPersonName
    • ISWEcoResProduct
    • ISWEcoResProductTranslation
    • ISWFiscalCalenderPeriod
    • ISWFiscalCalenderYear
    • ISWGeneralJournalAccountEntry
    • ISWGeneralJournalEntry
    • ISWHierarchyLinkTable
    • ISWHierarchyTreeTable
    • ISWInventDim
    • ISWInventItemInventSetup
    • ISWInventTable
    • ISWInventTableModule
    • ISWLedger
    • ISWLedgerEntry
    • ISWLedgerEntryJournal
    • ISWLedgerEntryJournalizing
    • ISWLedgerJournalTable
    • ISWLedgerJournalTrans
    • ISWLogisticsElectronicAddress
    • ISWMainAccount
    • ISWMainAccountCategory
    • ISWMarkupTrans
    • ISWProjTable
    • ISWSmmActivities
    • ISWSubledgerJournalAccountEntry
    • ISWSubledgerJournalAccountEntryDistribution
    • ISWSubledgerVoucherGeneralJournalEntry
    • ISWTaxTrans
    • ISWTaxTransGeneralJournalAccountEntry
    • ISWTransactionLog
    • ISWTransactionReversalTrans
    • ISWVendInvoiceJour
    • ISWVendInvoiceTrans
    • ISWVendPackingSlipJour
    • ISWVendSettlement
    • ISWVendtable
    • ISWVendTrans
    • ISWDimensionFocusBalance
  6. Build and synchronize the entire solution.
  7. Refer to Bring your own database (BYOD) to create an Azure SQL database.
  8. Refer to Azure SQL Database and Azure Synapse IP firewall rules and install a firewall.
  9. Go to Framework parameters under Data management in Finance and Operations and set up the required framework options as shown in the following images.


  10. To refresh the selected entities, select Workspaces > System administration> DEV Tools > all DMF data entities, and select the Refresh data entity option.
  11. Go to Configure data source, create a new source data format by entering appropriate details and save the format.
  12. Go to the Configure entity export to database option, double click on the source data format you created, and configure the connection string following the format shown in the screenshot.

  13. To enable the incremental push load, go to Data Entities, select Source name, Entity, select Change Tracking, and update the tracking for entire entity or primary table or use a custom query.

  14. Go to the Configure entity export to database, select Source name, Entity, and then select Publish. The job will go to queue and run. These jobs place these tables in your database, however, no data is added.

  15. Select the Show published only option. The published entities are displayed.
  16. To retrieve data in the published entities, go to Export > Create a new group or select an existing group. In the Add multiple section, change the Target data format to your data source, and your Default refresh type to Full push only. Then, search for the entities you wish to export.
  17. The selected entities will be added. You can either export now or export in the batch job.

Prerequisite Tasks for Microsoft Dynamics 365 Business Central (Cloud) as Source System

Jet Data Manager, powered by TimeXtender, facilitates data extraction from Microsoft Dynamics 365 Business Central (cloud). Perform the following steps:

  1. Locate the Jet Analytics Setup.exe file in the Business Central (cloud) folder within the SourceConnect 8.0 folder of the product package.
  2. Run the setup file and complete the installation process.

    Note: To activate Jet Data Manager, obtain the required keys by contacting insightsoftware.

  3. Open Jet Data Manager.
  4. Import the project (.xml). This file is located in the Business Central (cloud) folder within the SourceConnect 8.0 folder.
  5. Run the Connection Manager.
  6. Edit the staging database settings by clicking the corresponding icon. Provide the necessary details and establish the connection.
  7. Edit the BC 365 Provider settings by clicking the corresponding icon. Provide the necessary details and select Authorize OAuth.
  8. Enter your credentials to connect to the data source.

Click here for more information on installing Jet Data Manager.

Was this article helpful?

We're sorry to hear that.