SLT Scenario for SAP Business Warehouse – Setting of PSA
In this blog, we will have a look on how to create the SLT configuration for BW PSA scenario.
Prerequisite:
- DMIS add-on on BW system.
- RFC connection work between SLT system and BW system
Landscape:
Steps :
1. Go to transaction LTRC , create configuration, input configuration name, and descritption 
2. Choose Source System, here we are using the SAP source system.
3. As we will use BW as target system, so here we choose RFC connection and scenario of “Persistent Staging Area (PSA) for SAP BW” . And then input the created RFC connection to BW system. And for Logical System Name, we input the name we want. And note this Logical System name, we will use it later.
4. As we are just testing, so here we set the following parameter
5. Review your settings and create the configuration.
6. Go to BW system， transaction RSA1， click on “Source System” and right click on “Web Service” , and click on “Create”.
7. Create the web Service Source System, For “Logical System Name”, input the name that you defined in step 3. And input your source system name.
8. Then all are prepared, we can start replication of tables.
10. SLT: transaction LTRC -> Table Overview -> Data Provisioning -> Start Load -> Table : ZKLAUS_TEST
11.
12. BW side , when you double click on source system Z07, it will jump to the datasource “Unassigned Nodes” -> “test open sql from sum” . And you can find the datasouce “SLT_ZKLAUS_TEST”, right click -> manage.
13. And you coud find that the table has already been transferred to PSA. 
This is whole steps for creating the configuration for BW PSA scenario.
Nice one Kiaus with complete step by step explanation of scenario.
Hi Kiaus,
i have problem with this scenario.
I'm using it for 6 months now exactly as you wrote(except i use replication mode with delta). After replicating to PSA we create DSO (standard) or ADSO and some HANA optimized transformations and load chains. The problem occurs when non-ABAP table structure changes (1 text field is added to the table). I tried to STOP and RE-ADD the table to replication...didnt help. I figured out that SLT didnt change Data Source/Fields. I had to delete everything under DS(DSO, Transformation, DTP, Chain, Infopacket...) because it didnt alow me to delete only DS. Then STOPPED replication and RE-ADD. When i did that it worked but i had to delete much stuff and rebuild all again.
Is there any bettrer/shorter way that SLT would refresh the sctructure by itself? If my scenario would be more complicateted i would need to work days for each field change.
SLT:
BW:
BR!
Ales Ocvirk