Abending batch jobs when Data is locked in DP

[srinivas_krishnamoorthy]

There are couple of jobs like proportional factor calculations or macro jobs in batch that do not stop or abend when any data is locked say by a dialog user. The log does show that data is locked but finishes successfully. This issue then gets ignored by most people. Is there a way of stopping batch jobs if data is locked at all, like how it happens in say /sapapo/rtsoutput job ? What is the configuration around this ?

[Former Member]

Hi Srinivas,

This issue can be tackled by scheduling the first step containing /SAPAPO/TS_LCM_CONS_CHECK within the SAP batch job to run before the other steps (Prop factors, Macro etc.....).

The program /SAPAPO/TS_LCM_CONS_CHECK fails if the user has locked data thus preventing the following steps such as prop fact or macros from running and you will notice that the data is locked by some users.

Hope this helps.

regards,

Srinidhi

[srinivas_krishnamoorthy]

thanks for your reply.

I had tried using the LC Consistency check with the Lock Planning version option as a preceding step to the calculation proportional factor option, but again that preceding step successfully executes with a job log saying the planning version cannot be locked. So the first step goes through successfully without stopping the second step. So when the planning book is in edit mode, and one runs /SAPAPO/TS_LCM_CONS_CHECK in background, the job does NOT fail. Only a log is established.

[Former Member]

Try setting the 'Repair' option and 'Log' option in addition to the 'Lock planning version' checkbox. It should work.

Let me know after you try it out.

regards,

Srinidhi

[srinivas_krishnamoorthy]

Tried all combinations, and it does not work. Guess this may have to be programmatically achieved.