Data Locking in Parallel Batch Jobs

[jeff_dillon]

Hello all:

We have a problem with a DP process chain that we cannot figure out.  We are running seven DP Background Processing jobs at the same time, using seven distinct selection profiles (Characteristic A = "1", Characteristics A = "2", etc).  When we run all the jobs together, we frequently receive error SDP222, telling us that the batch user is locking one or more CVCs in one or more of the jobs.

Because Characteristic A can only be one thing for any given CVC, we are sure we are not overlapping our selection profiles.  But we do not know why this is happening.  Any ideas?

Thanks in advance,

Jeff

[rajkj · Accepted solution]

Hi Jeff,

It depends on the locking logic you maintained for your DP planning area (t.code /SAPAPO/MSDP_ADMIN , tab locking logic). Please check the following link for SAP documentation on locking logic  http://help.sap.com/saphelp_SCM700_ehp02/helpdata/en/77/d4103d2669752de10000000a114084/content.htm.

You can also display the locks when your process chain is being executed using t.code SM12.  Probably your BASIS admin or an ABAPer can help you to identify the issue. One reason could be the session id (SIMSESSION) that can be analyzed by your ABAP expert.

Thanks,

Rajesh

[jeff_dillon · Accepted solution]

Thanks Rajesh.

After taking a more careful look at the MPOS, I realized that the "characteristic" we are selecting on is actually a Nav Att.  I believe that is the problem.

No parallel batch jobs for us.  We will run everything sequentially to avoid conflicts.

Jeff

[former_member209769 · Accepted solution]

Hi Jeff,

Using navigational attribute as selection shouldn't be an issue. They are meant for this very same purpose of allowing selections.

Either locking logic is not maintained properly for your requirements as Rajesh suggested above, or may be there is some other understanding issue or bug.

What DP process are you working on in your jobs? (e.g. macros, forecasting, etc)

Could you please share screenshot of the locking logic maintained for your planning area?

Also, if you could share some of the selection IDs (showing details of how they have been maintained), that would be helpful in suggesting a solution.

Thanks - Pawan

[jeff_dillon · Accepted solution]

OK, we took a more careful look at these.

We are using Nav Atts, which we could not do the last time I personally built a DP Planning Area (APO 3.0), but that does work now.  Our locking logic matches the logic of another DP system we have in the same box.  (We currently have 4 live DP systems.)  But the system we based this one off of only uses one characteristic in the selection profiles.  Because the new system has two selection profiles that use two characteristics, we need to use the Detailed locking option.

Rajesh and Pawan, you are correct.  Thanks for yor help.

Jeff

[Former Member]

Hi Jeff,

my assumption is that you are using aggregates in your POS.

Normally you get this message when usinge aggregates and parallel processing in SCM 5.0.

In SCM 7.0 there is a release restriction that it isn't possible to use aggregates and parallel processing.

Robert