1. Introduction:
The purpose of this document is to detail the set of activities which must be completed after system copies in order to align the configuration and filters in Source-SLT-CFIN environment, enable ongoing replication in non-production environment and ensure no replication data was lost.
2. Assumptions:
We will following the set of activities in the given only when below scenario is present.
a) Both the Source ECC/S4HANA and Target S/4 CFIN System were copied.
b) The Copy Time for both instances was the same, down to the millisecond
c) The SLT environment was not copied
d) Initial load was finished and replication was running before copy
Pre-requisite:
We should stop the replication in the SLT box connected to refresh-on systems before source system or target system or both system copy starts. As; these SLT configuration will be no more useful as technical runtime objects or associated triggers will be copied. These objects are generated in system on runtime and has association with system id.
We need to perform set of activities in source and SLT box. We divided corrective action into four parts.
a) Cleanup of Source System Objects
b) Re-enablement of Ongoing Replication
c) Reconciliation and Delta Load of Missing Records
This process document will explain the activities to be performed in each corrective step.
3. Corrective Action in Source and SLT
3.1: Cleanup of SLT objects in source system
Pre-requisite: User should have proper authorization in source system to perform activity using transaction code IUUC_REMOTE. Please check with security team if user is not authorized for the same.
Purpose: Suppose source system S1 is copied with source system s2 then we are deleting triggers and logging table of only those tables in source system S1 for which SLT configuration is done in SLT system connected to source system s2. Because, logging table name and created triggers are specific to system.
a) Go to transaction code IUUC_REMOTE in source system.
List the triggers available in the source system by clicking on “List Triggers” button. Enter the table name and select radio button “list only IUUC Triggers”.
Then, Execute. Below are the list of available triggers (Insert, Delete and Update). You can find below triggers in copy-from source system which got copied to refresh-on system and needs to be deleted.
Note: - If same table is used for central finance and non-central finance scenario then trigger needs to be deleted.
b) Now, delete the triggers for the same table. Go to “Expert Function” tab and click on “Delete Triggers” button.
Enter the table name for which triggers needs to be deleted in source system.
Then, Execute. Below Pop-up will come where it says that this activity normally to be executed from IUUC central system means SLT system. But, we need to perform this activity in source system. As we copied source system from other environment; generated triggers from other environment will get copied; which is not relevant for our SLT system. Hence, it needs to be deleted in the source system.
Click on “yes” button. Triggers will get deleted and below message will come after successful deletion.
Since, three triggers were available for AUFK table hence all got deleted successfully.
c) Now, we need to delete source logging table in refresh-on source system which got copied from copy-from system.
Note: - If same table is used for central finance and non-central finance scenario then source logging table would be same and that needs to be deleted.
Go to “Expert Function” tab and click on “Delete Logging Tables” button.
Enter Table Name and then execute.
Source Logging table is deleted and below successful message will come.
3.2: Re-enablement of Ongoing Replication
Pre-requisite: User should have proper authorization in SLT system to perform activity using transaction code LTRC. Please get proper authorization and roles by security team.
As Initial load was already done and all tables were running into replication mode. Hence, we should not perform “Start Replication” to enable replication again. If we will perform “Start Replication” then all records which have not already been transferred as part of an Initial Load will be resent. And, there would be data duplication in central finance system. Hence, we need to start the replication without initial load.
There could be two scenario in SLT box.
1) If replication was already running on SLT box connected to refresh-on system then we will be stopping the replication before source and target CFIN system copy starts. And, MT Id will be there in SLT box which was getting used.
2) There could be situation where refresh-on source or target CFIN system was not connected by SLT system.
In 2nd scenario, we can create new MT Id in SLT box using LTRC transaction code to establish the connection between refresh-on source and target CFIN system.
Check if LTRS filters and related codes are in place for the tables in SLT system.
First, we need to start recording by selecting “Start Recording” radio button for the table. It starts recording changes of a table without an initial load procedure or the replication procedure. It creates triggers on the table in source systems. It also creates a logging table for the recording purpose.
After recording; triggers and source logging table will be created in the source system.
Once recording is completed. Click on Data Provisioning button-> Below Pop-up will open-> Enter the Table Name for which replication needs to be re-enabled (do F4 to validate if table name is correct) -> Select “Start Replication (w/o Load)” radio button. Once, all phases are completed present in the “Data Transfer Monitor” tab and Loaded flag is checked as “X’. Replication will start for the table without any initial load. We can create new master record in source system, same will get replicated into the target system.
3.3: Reconciliation of Missing Records
In Central Finance, there could be scenario where data posted in the source system might not be replicated for any transactions associated with tables i.e. AUFK, CFIN_ACCHD and COBK. These lost records need to be reconciled. There are ways to know to reconcile missing records. ERDAT in AUFK , CPUDT in CFIN_ACCHD and COBK are the creation date of records in source system which can be used as one of filter criteria in addition to other filters based on business requirements. All missed records will be pulled from the source and same can be loaded using filters.
3.4: Delta Load of Missing Records
Once we have the criteria how to load missing records or if we have list of missing records. New Mass Transfer ID needs to be created to load missing records as all missing records need to be pulled using specific filters. Filter can be set either at LTRS or writing MWB filter logic under standard event method of SAP tables AUFK, CFIN_ACCHD, COBK or any as delivered through SLT content by SAP. Once all filters are in place, corresponding table can be loaded to load missing records.
Go to LTRC->Click on new MT ID-> Click on "Data Provisioning" button-> Select "Start Load"-> Enter table name.
Once Load is finished and missing records are loaded into central finance target system. Table can be removed from LTRC. Click on "Data Provisioning" button-> Select "Stop Load"-> Enter Table.
Table will be removed from the MT ID. As Mass Transfer ID is on no use. Either it can be deactivated to reuse it later or it can be deleted from LTRC.
Above explained scenario is the common practice in any central finance project to copy the source and target system of Non-Production Environment to perform Mock Load on most recent production data.
The purpose of this document is to detail the set of activities which must be completed after system copies in order to align the configuration and filters in Source-SLT-CFIN environment, enable ongoing replication in non-production environment and ensure no replication data was lost.
2. Assumptions:
We will following the set of activities in the given only when below scenario is present.
a) Both the Source ECC/S4HANA and Target S/4 CFIN System were copied.
b) The Copy Time for both instances was the same, down to the millisecond
c) The SLT environment was not copied
d) Initial load was finished and replication was running before copy
Pre-requisite:
We should stop the replication in the SLT box connected to refresh-on systems before source system or target system or both system copy starts. As; these SLT configuration will be no more useful as technical runtime objects or associated triggers will be copied. These objects are generated in system on runtime and has association with system id.
We need to perform set of activities in source and SLT box. We divided corrective action into four parts.
a) Cleanup of Source System Objects
b) Re-enablement of Ongoing Replication
c) Reconciliation and Delta Load of Missing Records
This process document will explain the activities to be performed in each corrective step.
3. Corrective Action in Source and SLT
3.1: Cleanup of SLT objects in source system
Pre-requisite: User should have proper authorization in source system to perform activity using transaction code IUUC_REMOTE. Please check with security team if user is not authorized for the same.
Purpose: Suppose source system S1 is copied with source system s2 then we are deleting triggers and logging table of only those tables in source system S1 for which SLT configuration is done in SLT system connected to source system s2. Because, logging table name and created triggers are specific to system.
a) Go to transaction code IUUC_REMOTE in source system.
IUUC_REMOTE
List the triggers available in the source system by clicking on “List Triggers” button. Enter the table name and select radio button “list only IUUC Triggers”.
List Triggers- IUUC_REMOTE
Then, Execute. Below are the list of available triggers (Insert, Delete and Update). You can find below triggers in copy-from source system which got copied to refresh-on system and needs to be deleted.
Note: - If same table is used for central finance and non-central finance scenario then trigger needs to be deleted.
Triggers- Created in Source System
b) Now, delete the triggers for the same table. Go to “Expert Function” tab and click on “Delete Triggers” button.
Delete Triggers 1-IUUC_REMOTE
Enter the table name for which triggers needs to be deleted in source system.
Delete Triggers 2- IUUC_REMOTE
Then, Execute. Below Pop-up will come where it says that this activity normally to be executed from IUUC central system means SLT system. But, we need to perform this activity in source system. As we copied source system from other environment; generated triggers from other environment will get copied; which is not relevant for our SLT system. Hence, it needs to be deleted in the source system.
Delete Triggers Popup- IUUC_REMOTE
Click on “yes” button. Triggers will get deleted and below message will come after successful deletion.
Triggers deleted in Source System-IUUC_REMOTE
Since, three triggers were available for AUFK table hence all got deleted successfully.
c) Now, we need to delete source logging table in refresh-on source system which got copied from copy-from system.
Note: - If same table is used for central finance and non-central finance scenario then source logging table would be same and that needs to be deleted.
Go to “Expert Function” tab and click on “Delete Logging Tables” button.
Delete Logging Tables 1- IUUC_REMOTE
Enter Table Name and then execute.
Delete Logging Table 2- IUUC_REMOTE
Source Logging table is deleted and below successful message will come.
Logging Tables deleted in Source System-IUUC_REMOTE
3.2: Re-enablement of Ongoing Replication
Pre-requisite: User should have proper authorization in SLT system to perform activity using transaction code LTRC. Please get proper authorization and roles by security team.
As Initial load was already done and all tables were running into replication mode. Hence, we should not perform “Start Replication” to enable replication again. If we will perform “Start Replication” then all records which have not already been transferred as part of an Initial Load will be resent. And, there would be data duplication in central finance system. Hence, we need to start the replication without initial load.
There could be two scenario in SLT box.
1) If replication was already running on SLT box connected to refresh-on system then we will be stopping the replication before source and target CFIN system copy starts. And, MT Id will be there in SLT box which was getting used.
2) There could be situation where refresh-on source or target CFIN system was not connected by SLT system.
In 2nd scenario, we can create new MT Id in SLT box using LTRC transaction code to establish the connection between refresh-on source and target CFIN system.
Check if LTRS filters and related codes are in place for the tables in SLT system.
First, we need to start recording by selecting “Start Recording” radio button for the table. It starts recording changes of a table without an initial load procedure or the replication procedure. It creates triggers on the table in source systems. It also creates a logging table for the recording purpose.
Start Recording-LTRC
After recording; triggers and source logging table will be created in the source system.
Once recording is completed. Click on Data Provisioning button-> Below Pop-up will open-> Enter the Table Name for which replication needs to be re-enabled (do F4 to validate if table name is correct) -> Select “Start Replication (w/o Load)” radio button. Once, all phases are completed present in the “Data Transfer Monitor” tab and Loaded flag is checked as “X’. Replication will start for the table without any initial load. We can create new master record in source system, same will get replicated into the target system.
Start Recording without Load-LTRC
Replication Data Transfer Monitor-LTRC
3.3: Reconciliation of Missing Records
In Central Finance, there could be scenario where data posted in the source system might not be replicated for any transactions associated with tables i.e. AUFK, CFIN_ACCHD and COBK. These lost records need to be reconciled. There are ways to know to reconcile missing records. ERDAT in AUFK , CPUDT in CFIN_ACCHD and COBK are the creation date of records in source system which can be used as one of filter criteria in addition to other filters based on business requirements. All missed records will be pulled from the source and same can be loaded using filters.
3.4: Delta Load of Missing Records
Once we have the criteria how to load missing records or if we have list of missing records. New Mass Transfer ID needs to be created to load missing records as all missing records need to be pulled using specific filters. Filter can be set either at LTRS or writing MWB filter logic under standard event method of SAP tables AUFK, CFIN_ACCHD, COBK or any as delivered through SLT content by SAP. Once all filters are in place, corresponding table can be loaded to load missing records.
Go to LTRC->Click on new MT ID-> Click on "Data Provisioning" button-> Select "Start Load"-> Enter table name.
Start Load-LTRC
Once Load is finished and missing records are loaded into central finance target system. Table can be removed from LTRC. Click on "Data Provisioning" button-> Select "Stop Load"-> Enter Table.
Table will be removed from the MT ID. As Mass Transfer ID is on no use. Either it can be deactivated to reuse it later or it can be deleted from LTRC.
Above explained scenario is the common practice in any central finance project to copy the source and target system of Non-Production Environment to perform Mock Load on most recent production data.
- SAP Managed Tags:
2 Comments
