Skip to main content

Prerequisites for Transaction Replication

The SourceConnect Management Console requires two categories of prerequisites to function smoothly: those for SAP Central Finance Transaction Replication by insightsoftware for SAP S/4HANA and those specifically for the Management Console itself. This section describes the prerequisites for Transaction Replication.

Before you install SAP Central Finance Transaction Replication by insightsoftware for SAP S/4HANA, you can review the sequence in which you must install the components and the prerequisite tasks that you must perform.

Prerequisite Tasks

Before you install SAP Central Finance Transaction Replication by insightsoftware for SAP S/4HANA, ensure that the following tasks are complete:

  • Review the system requirements in SAP Central Finance Transaction Replication by insightsoftware Release Notes, and ensure that your setup meets the minimum requirements.
  • Copy the setup files for installing and setting up the product to the computer on which you want to install the product.
  • Configure the source enterprise resource planning (ERP) system with the required modules.
  • Ensure that the source database, such as Oracle E-Business Suite or Microsoft Dynamics AX, and target SLT Replication Server database are accessible from the SAP Data Services server. If required, open ports, and add TNS entries.
  • Create an application user who has access to the ACDOCA, BKPF, SKA1, SKAT, T001, and T077Z tables in SAP S/4HANA and share the user credentials with insightsoftware consultants.
  • Set up BryteFlow if you are using BryteFlow for change data capture (CDC). For information about setting up HVR, see the Setting Up BryteFlow.pdf document that is included with the setup files.
  • Configure the SLT Data Migration Server (DMIS).
  • Perform the following steps to download and install the product:
    1. Sign in to https://help.sap.com/ .
    2. Search for SAP Central Finance Transaction Replication by insightsoftware for SAP S/4HANA. The SAP Central Finance Transaction Replication by insightsoftware for SAP S/4HANA product page appears.
    3. Select the SAP Note link. The note number changes for each release. The SAP Note has further instructions to download the media and the required Attribute Change Package (ACP).
  • Implement the following SAP Notes on SLT:
    SAP Note SAP S/4HANA Version

    3340008

    2023

    3169099

    2022

    3155700

    2021 (PLANT is optional)

    3116266

    2021

    3079411

    2021 and higher (This SAP note is applicable only for AVL. If you are not implementing AVL, you can disregard this note.)

    3067156

    2021

    2922300

    2020

    For information about implementing the SAP Notes, contact SAP Support.

  • Create a database user named MAGSLTDBUSR in the SLT Replication Server with read and write access to the following tables. The database owner grants the required access to the user. This user will be used in SAP Data Services to connect to the SLT Replication Server database.

    Note: When setting up a database user, you can provide a username of your choice.

    • /1LT/CF_E_HEADER
    • /1LT/CF_E_ACCT
    • /1LT/CF_E_DEBIT
    • /1LT/CF_E_CREDIT
    • /1LT/CF_E_PRDTAX
    • /1LT/CF_E_WHTAX
    • /1LT/CF_E_COPA
    • /1LT/CF_E_CLRITM
    • /1LT/CF_E_CLRWHT
    • /1LT/CF_E_DOCCHG
    • /1LT/CF_E_EXTENT
    • /1LT/CF_E_EXT_IT
    • /1LT/CF_E_EXTCHG

      • Access to the following tables is required only if you are implementing AVL:

    • /1LT/CF_E_SODOC
    • /1LT/CF_E_SOITEM
    • /1LT/CF_E_SOPART
    • /1LT/CF_E_SOSLN
    • /1LT/CF_E_CIDOC
    • /1LT/CF_E_CIITEM
    • /1LT/CF_E_PODOC
    • /1LT/CF_E_POITEM
    • /1LT/CF_E_POSCH
    • /1LT/CF_E_POACC
    • /1LT/CF_E_PORMD
    • /1LT/CF_E_PORSI
    • /1LT/CF_E_SIDOC
    • /1LT/CF_E_SIITEM
    • /1LT/CF_E_SIACC
    • /1LT/CF_E_SIGLAC
  • Configure and start the replication in SLT Replication Server. Perform the following steps to start the replication:
    1. Create a mass transfer identifier with two RFC connections, one for SLT Replication Server and another for the target SAP S/4HANA system. A sample screenshot is as follows.
    2. Start replication for the mass transfer identifier that is created for the /1LT/CF_E_HEADER table.
    3. Start replication for AVL for the /1LT/CF_E_SODOC, /1LT/CF_E_CIDOC, /1LT/CF_E_PODOC, and /1LT/CF_E_SIDOC tables. This step is required only if you are implementing AVL.
  • Using Multiple Folders for Business Units: This scenario is applicable to customers who deploy Transaction in multiple instances of a source system. You can use different folder paths for files pertaining to each business unit and instance, such as DEV or QA. Transaction has the flexibility to create different system configurations and a substitution variable for each business unit and instance configuration. A screenshot showing the sample system configurations is as follows.

    • 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.

      Note: Refer to the SAP Central Finance Transaction Replication by insightsoftware Administrator Guide for the complete list of the custom entities.

    6. Build and synchronize the entire solution.
    7. Refer to Creating a SQL database 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.