Data Migration: ECC to CFIN via SLT
SLT (SAP Landscape Transformation) Replication Server is a data migration tool, which is used for real time data migration. SLT is the ideal solution for all HANA customers who need real-time (and non-real-time) data replication sourcing from SAP ERP or non-SAP systems into HANA.
There is always an active configuration which is responsible for data migration.
For documents which failed to load in normal replication, SLT also provides manual way to load the same.
This document will help in exploring in depth behavior of SLT. This document is written in context where data is migrating from ECC to CFIN (Central Finance) via SLT.
Exploring SLT behavior
Activating/Deactivating the Configuration/MTID (Mass transfer ID)
Though there are various ways to deactivate the active configuration, when systems are going under maintenance. Below is snap of transaction LTRC where list of configurations can be seen. Here also we get option to activate/deactivate the config/MTID
Select the configuration, which is to be deactivated, now click on deactivate tab -> now select option ‘Selected configuration’ (refer below snap)
So, this is one of the way replication can be deactivated. But it is found some time that deactivating/activating replication using this technique, sometimes can result in inconsistencies as it can affect the status of other configurations.
Below is the most reliable and standard way to achieve the same goal.
Deactivating the Configuration/MTID
- Login to SLT system -> Go to transaction LTRC
Here two configurations are in active state, we will deactivate the 1st one.
Click on 1st configuration PRD010_E1P010(MTID 001) or in Mass Transfer ID section enter 001 and execute, below screen will appear now go to Administration Data tab
Below screen will appear, click on Deactivate tab
Configuration PRD010_E1P010 is deactivated now.
Now, once the systems are up after maintenance, we need to turn the SLT replication ON.
Activating the Configuration/MTID
Follow the same steps as mentioned above for Deactivating the Configuration. Now in Administration Data Tab Click on Activate tab.
Here Configuration/MTID PRD010_E1P010(MTID 001)
Steps to be followed after Activation
- Hit ‘Table Overview’ tab and check for the trigger status (Activated)
- Go to ‘Data Transfer Monitor’ tab and check for ‘Block Processing Step’ to be blank.
- Once above two steps verified, it proves replication started successfully.
Manual Document loading
We perform manual loading of document, when they are missed because of some inconsistencies in our normal replication. Here we are moving document from ECC to CFIN via SLT.
|Source System (ECC)||PRD/ARP|
|Target System (S/4 HANA)||E1P|
|Objects/tables involved in migration||COBK(costing documents), AUFK(orders), CFIN_ACCHD(Accounting documents)|
Manual CFIN Document loading
- Go to table DMC_FM_RESTART in SLT system enter the MTID and TABLE NAME for which load is to be carried out. Number of records should be 0. If not, execute the program DMC_FM_RESTART_COPY_DELETE, this will bring down entries to 0 in the table.
- Go to transaction LTRC
- For Manual document loading select the config which is maintained for manual loading (as there will always be two configurations with same source/target system, one for normal replication and other one for missed documents)
- Here configuration with Suffix UTIL is used for manual loading. As, ARP010_E1P010_UTIL (MTID 003) (loading data from ARP to E1P). PRD010_E1P010_UTIL (MTID 004) (loading data from PRD to E1P).
- Click on Configuration name for which document is to be loaded or enter the corresponding MTID in Mass Transfer ID section and execute. Below screen will appear (you may not find Tables in Table name section, that is ok)
Here e.g., Configuration PRD010_E1P010_UTIL (MTID 004)
- Now, click on Administration Data tab and Activate the Configuration
- Now click on Go to tab and select Advance Replication Settings
- Below screen will appear, click on Performance Option
- If Tables name not appear, Right click on Performance Option and select Add Table
- Double click on the table name for which Document has to be loaded to Target System (here, E1P). Here e.g. AUFK.
List of previously loaded document may appear (as in above snip), they are called Filters. We can edit in the same and provide new document number or can delete these filters and further can create new ones.
- For editing or creating filters click on Edit Push Button in the top left corner of screen.
- For editing the existing document numbers click on ‘Pencil Icon’ and edit the previous number with the new one.
- For deleting all click on Delete icon and then Create New Filters by clicking on Create Icon.
Below screen will appear when we hit create icon, give the technical name of field in Field Name (Here AUFNR) in operator select equal to for one document if more than one range can be selected and later Low Value and High Value can be provided.
Make sure to provide prefix ‘0’ to the document number, same can be referred from Source system. In source system open that table in SE16 enter the document number and execute. Now copy the full document number otherwise document will go into error while loading.
Also don’t provide doc. No. ‘in codes’, system automatically adds that.
- After Providing Filter Conditions Hit OK and then click Save icon in Application Tool bar.
- Once successfully saved, hit back button icon.
- Click on Data Provisioning button present on Function Tool Bar (as highlighted below)
Below dialogue box will appear, just Enter the Table name for Which filters are Set (here AUFK) and execute.
- Do not mark radio buttons, by default Start Load is marked and that only we needed.
- Once Document loading Process starts, same can be checked in Data Transfer Monitor tab.
- Once Loaded field marked as X, means document loaded successfully. Just to check for errors, select the table name and click on View Errors tab.
As status Loaded marked as X. Go to Administration Data tab and Deactivate the configuration. (As these configurations are used for manual loading only, once document loaded, no use of keeping it on). Now to cross check the loaded document go to transaction /AIF/ERR in Target System (E1P) and search for the document number.
Thanks for sharing step by step !!!
I was wondering if Configuration set up as first step required to start with SLT using LTR code to provide Source and Target system with replication options and the last step that after table gets loaded then loaded Data through SLT process will be displayed in Data preview, although very informative blog !!!
Pramod Kumar, yes, an active configuration actually is the first step using TCode LTRC.
First, thank you for sharing the helpful step-wise guide, Ujjwal Singh.
Next my question on the Manual Load scenario: What will happen if no filters are supplied in the Advanced Replication Settings (in other words, this step is skipped)?
My guess: The entire tables for the selected configuration will be replicated, if they were never replicated before. And if replicated before, the already transferred records will be errored out (that will be unnecessary load on the system) and rest of them will be transferred.
As a best practice, we will do only start load by setting LTRS filters in separate MT ID. If we go with start load with out filters, it will create duplicate entries on target and you will see lot of errors in SLT with duplicate key errors. Again you have to follow some manual steps to remove duplicate entries. Now we have easier approach way of doing it by simply running the trigger reports listed below for each CFIN interfaces.
Present in System
FI Document (AC_DOC)
CO Document (CO_DOC)
Cost Object (CO_OBJ)
These reports may not be available based on version, make sure you have to implement respective notes for the report to be available in your system to reprocess postings from source system and its a pre-req. Hope this info helps you.
Thank you for answering, dear Mohan Krishna Perichetla 🙂