SAP LT Replication Server – Master Job execution with Batch user

[Former Member]

Dear All,

With this blog I would like to share the learning I had with the SLT configuration where in the replication master job was  getting executed with the dialog user, if the dialog user is locked or deactivated  the replication jobs were not restarted  after 24 hrs.

Error Msg : Error while starting the job with the user(user not available or locked)

SLT Replication Server Version details:

SLT NW 731 SP5 – DMIS 2011_731 SP5 on Oracle Database

HANA Revision: 74.04

SAP LT Replication Server – Master Job execution with Batch user

     For SLT Master Job always runs with the dialog user of a person whoever restarts the replication manually, in case if the dialog user id locked the replication will not restart automatically after 24 hrs.

     As master job never exist in release mode it is not possible to run the same with batch user.

     For the work around we can schedule a job which will intron restart all the replication MTIDs (with Master job) using a batch user below are the attributes for scheduling the job.

Step 1: Create a Job in Sm36.

Step 2: Click on Step to provide the below details

Inputs:

User: CT1SLSLTBKGR

ABAP Program name: IUUC_REPL_START_STOP_JOBS

Once the job parameters are defined you can execute this job immediately to start the Replication configuration for all the MT IDs.

Or if the job is already created we can simply execute and get the replication started.

To Stop the Replication we have to use the same old process, of manually stopping the replication for all the MT-IDS

Observation:

This will start the master job with the dedicated batch user. I have this scenario in Dev env once the master job starts with the batch user it will be picked up next time whenever the replication restarts at 12.00AM night as per architecture.

The only concern here would be;

1. In case if anyone restarts the LTRC using his/her own ID the master job will pick up the DIALOG id for starting and stopping next time onwards
2. In case of any downtime we will have to use above process to start and stop the replication.

Please let me know in case if you have any questions or concerns.

Thanks and Regards,

Amar Ghuge