In previous chapters SAP Landscape Transformation (SLT)
, we explained basic feature and functionalities of SLT. We also learnt how to replicate data from SAP Source to HANA using SLT
In this article we will explain major jobs involved in the SLT replication process.
Master Job (Monitoring Job)
There is only one master job which handles all active configurations (a configuration is active if flag is set on IUUC_REPL_HDR).
An additional master job is started for system event SAP_SYSTEM_START which ensures that the master job is started automatically after a restart of the SLT system.
The decrease and increase of initial load and data transfer jobs is controlled by the composite master job.
Every 5 seconds, the monitoring job checks in the SAP HANA system whether there are new tasks and, if so, triggers the master control jobs. It also deletes the processed entries (tasks) from table RS_ORDER and writes statistics entries into table RS_STATUS (in the relevant schema in the SAP HANA system).
Master Controller Job
This job is scheduled on demand and is responsible for:
- Creating database triggers and logging table in the source system
- Creating synonyms
- Writing new entries in admin tables in SLT server when a new table is loaded/replicated
Data Load Job
This job should always be active. If the job does not complete successfully, the master controller job restarts it.
This job is responsible for:
- Loading data (load)
- Replicating data (replication)
- Changing status flag for entries in control tables in the SAP LT Replication Server
Migration Object Definition Job
This job defines the migration object of a specific table (that you choose to load/replicate), which is the fundamental object for LT replication. The migration object definition should normally be quite fast for all tables.
Access Plan Calculation Job
This job calculates the access plan of a specific table (that you choose to load/replicate), and the access plan is used for data load or replication. The access plan is also a fundamental object for the replication. For a normal sized table, access plan calculation should finish quite quickly (less than 1 minute) while large tables might take up to several hours to finish