#LOGGER DDTANK SYSTEM S2 CODE#

And, MT Id will be there in SLT box which was getting used.Дў) There could be situation where refresh-on source or target CFIN system was not connected by SLT system. Hence, we need to start the replication without initial load.ДЎ) 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, there would be data duplication in central finance system. If we will perform вЂњ Start ReplicationвЂќ then all records which have not already been transferred as part of an Initial Load will be resent. Hence, we should not perform вЂњ Start ReplicationвЂќ to enable replication again. Please get proper authorization and roles by security team.ДЄs Initial load was already done and all tables were running into replication mode.

#LOGGER DDTANK SYSTEM S2 CODE#

Pre-requisite: User should have proper authorization in SLT system to perform activity using transaction code LTRC.

Logging Tables deleted in Source System-IUUC_REMOTEДЈ.2: Re-enablement of Ongoing Replication Source Logging table is deleted and below successful message will come. Go to вЂњ Expert FunctionвЂќ tab and click on вЂњ Delete Logging TablesвЂќ button. 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. Since, three triggers were available for AUFK table hence all got deleted successfully.Д¬) Now, we need to delete source logging table in refresh-on source system which got copied from copy-from system. Triggers deleted in Source System-IUUC_REMOTE Triggers will get deleted and below message will come after successful deletion. Hence, it needs to be deleted in the source system.Д¬lick on вЂњ yesвЂќ button. As we copied source system from other environment generated triggers from other environment will get copied which is not relevant for our SLT system. But, we need to perform this activity in source system. Below Pop-up will come where it says that this activity normally to be executed from IUUC central system means SLT system. Go to вЂњ Expert FunctionвЂќ tab and click on вЂњ Delete TriggersвЂќ button.Д®nter the table name for which triggers needs to be deleted in source system. Note: вЂ“ If same table is used for central finance and non-central finance scenario then trigger needs to be deleted.Д«) Now, delete the triggers for the same table. You can find below triggers in copy-from source system which got copied to refresh-on system and needs to be deleted. Below are the list of available triggers ( Insert, Delete and Update). Enter the table name and select radio button вЂњ list only IUUC TriggersвЂќ. List the triggers available in the source system by clicking on вЂњ List TriggersвЂќ button. Because, logging table name and created triggers are specific to system.ДЄ) Go to transaction code IUUC_REMOTE in source system. 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. Please check with security team if user is not authorized for the same.

Pre-requisite: User should have proper authorization in source system to perform activity using transaction code IUUC_REMOTE. This process document will explain the activities to be performed in each corrective step.ДЈ.1: Cleanup of SLT objects in source system We divided corrective action into four parts.Д¬) Reconciliation and Delta Load of Missing Records We need to perform set of activities in source and SLT box. These objects are generated in system on runtime and has association with system id. As these SLT configuration will be no more useful as technical runtime objects or associated triggers will be copied. 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. We will following the set of activities in the given only when below scenario is present.ДЄ) Both the Source ECC/S4HANA and Target S/4 CFIN System were copied.Д«) The Copy Time for both instances was the same, down to the millisecondД) Initial load was finished and replication was running before copy 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.

Logger ddtank system s2