Skip to Content
Technical Articles

Central Finance: Performance optimization via parallel loads in SLT


SLT is an integral part of S4 Central Finance implementation. While, most of its core functionality remains the same, yet there is a slight variation in some part like the concept of migration template aka predefined filters and its transport mechanism.

This blog would shed some light on some of the aspects as below:

  • How to performance tune via parallel load jobs with migration template.
  • Transport of the migration template to the different landscape- Test, Quality and Production
  • Retrigger reports


With the concept of application-based replication, SLT has come up migration template which comes with predefined filters for Central Finance. You can easily access it by downloading the latest content from SAP note- 2154420 and using transaction code MWB – Project REPL_CFIN and Subproject REPL_CFIN.

Part 1: Parallel load job in SLT (for Central Finance):

To optimize the initial load, we tend to either put filters to limit the volume or have parallel jobs running in the system. Refer blog – for setting parallel jobs in a table based replication.

For application-based replication, all the stuff remains the same, apart from how we set the reading type 5 parameter. In table-based replication, we can just simply put the reading type 5 in transaction code LTRS – advanced settings. However, when you do the same setting in application-based replication for Central Finance, the settings get overwritten with what is maintained in the migration template REPL_CFIN. Therefore, we need to maintain the reading type directly in the template.

Steps to maintain Reading Type 5 as below:

Step 1: Open the migration template linked with the active mass transfer id with transaction code MWB or by going through LTRC->Selecting Mass transfer id -> Processing Steps-> Create Predefined Load and Replication Objects. Select the Subproject with suffix ‘Template’ such as ‘ZIUUC_<mt_id_Template>’

Step 2: On the next screen DMC: Display subproject, select the load object in the conversion objects table. In our case, we are going to select ‘Z_AUFKL_00K’.

Step 3: Next we are going to select ‘Sender Range: Edit structure and field’ as we are making the change on the sender side.

Step 4: Now, we just need to select the ‘Access option’ and change the reading type to 5. As you will notice, by default it is set to Reading Type 1 – Range calculation and hence, the reason LTRSsettings are overwritten.
Note- to make the change, you will need to go in change mode.

Now that we have the made the reading type to 5 which is a prerequisite to start the parallel jobs. Other steps remain the same as that with table-based replication like maintaining the NUMREC in the table IUUC_PRECALC_OBJ (Table data will be divided into separate access plans by record count (NUMREC in IUUC_PRECALC_OBJ) and assigning adequate jobs in both source and SLT system.

Mode: P(Parallel) and Reading Type 5

Part 2: Transporting the migration template

In table-based replication, it is simple to import and export of filters from LTRS. But, in application-based replication, we got two options, either transport management system can be disconnected for the migration workbench objects or create Z* project and sub-project and use them in the step “Predefined Load and Replication object”.

For the first option, you will just need to set parameter NO_CTS_CONNECTION = ‘X’ in table DMC_RT_PARAMS.

For the second option “create Z* project and sub-project”, you can follow the document “Applying Modified Migration Workbench Content to Configurations” provided in the SAP note 2154420.


Part 3: Retrigger reports:

As per my experience in SLT with central finance, it is too common that we need to resend some documents again to the central finance system, which could be due to many reasons such as missed data, incorrect/incomplete data or we mistakenly cancelled/deleted the entry in AIF.
Normally, our option is to create a new mass transfer id and do a partial load by setting particular filters in LTRS or Migration template.
But, now we have an easier way of doing it by simply running the retrigger reports listed below, for each of the Central Finance interfaces.


Interface Report Name Present in System
FI Document (AC_DOC) FIN_CFIN_SLT_ADD_LOGTAB Source system
CO Document (CO_DOC) FINS_CFIN_REPL_CO_DOC Central System
Cost Object (CO_OBJ) FINS_CFIN_REPL_CO_OBJ Central System


Note: For FI document, the report might not be available in the source system depending on the Support pack level, to get this report, you might need to implement Source Note 2648321 – Central Finance: Retrigger Replication to reprocess postings from the source system and its prerequisite.

For instance, FI replication.

Step 1: Execute the report ‘FINS_CFIN_SLT_ADD_LOGTAB’ in the source system.

Step 2: Pass on the document which needs to be retriggered – you can choose the document based on different selection-option.

Step 3: Verify the document, then select the document and click on ‘Post’.

In conclusion, setting parallel jobs via SLTfor central finance is same just with the minute difference of settings in Migration workbench.


Priya K Asphlani

Be the first to leave a comment
You must be Logged on to comment or reply to a post.