To check the SLT generated objects and other issues I have faced
I was planning trying to write a Technical blog which couldn’t happen in these many years but finally got chance today.
As this is my first blog on technical details please let me know if there are any missing screenshots or mistakes.
The blog contains the navigation and important points in SLT as I have came across.(major details are already mentioned in old blogs by scn experts).
I have already worked in SLT but never worked on advanced settings so this blog will have all those details which I came across recently.
- Recently all replications were changed to inactive status due to some issue.
To activate it –
Click On related Configuration Name to go for detail screen. Then go to Administrative Data and click on Button Activate for Configuration Status.
Now if we have no issue then the Configuration Status will be Active
As in above screen shot data replication starts again.
Now we will look at the other Tabs :
2. Checking created FM and all relevant objects of SLT.
Goto Data Transfer Monitor and Double click on our Custom table as highlighted as in below screenshot.
It will take us to the new screen as below.
Click on Button Display.
_017 corresponds to Mass Transfer ID and in Description we can see our Ztable name ZEMPLOYEE_TEST.
Note : All SLT related names of jobs or any objects have *IUUC*.
Function Group has Function Modules and which have code related to SLT.
To check the Target Structure from SLT double click on the short text adjacent to No 3 as highlighted in below screenshot.
Currently Consistency overview is green or good.
We can see the Final structure which is moving from SLT as in above screenshot.
Now go back and click on No 4 to see the source structure/ fields.
Initially we get the screen as below. Then click on drop down adjacent to S_LOGTAB to see source structure S_EMPLOYEE_TEST.
Double click on S_EMPLOYEE_TEST see the fields related to that structure
Go Back and Click on Conversion Logic to see the if any ABAP coding is available.
Then we can see the screen as below.
Processing-Related – Corresponds to the code written at field.
Event-Related – Corresponds to event based code as its self explanatory.
For Testing purpose I gave both to check where this link will be available.
Double click on Processing Related Fields – TEST_FIELD.
Note : Please remember that this will be our Target field name we have used. For understanding purpose I am attaching Target structure once again as below.
Click on button highlighted below as ABAP editor.
The highlighted one in above screenshot is ABAP include where code is written.(As field symbol names are big it didnt fit in 72 char so need to create a new include and write the code in that. ex : <wa_s_zemployee_test>-new_field and other condition). When we write the code in include we need to use other fields as below instead of field symbol.
Go back and click on the parameters Tab and we can see the import and export parameters to be used.
Now Double click on BOR under Event-Related and the ABAP Editor as highlighted to see the ABAP program used.
For our demo purpose I used both field and Event based. I have used only BOR event based to check the replication.
Now go back 4 times to get to the LTRC default screen.
3. Goto Expert Functions and Settings for Notifications – to mention any email ids incase of any issue in SLT replication.
Double Click on Settings for Notifications.
Goto Expert Functions and check Job Health
Remaining all are self explanatory. Will add them once I come across any important point.
Hoping that this will be useful for all who are in SLT.
Please do share your valuable feedback.