RSMPC 121

[Former Member]

Hi Gurus

I am getting error RSMPC 121 in application log when activating 3.5 DSO 0PY_PP_C1 from 3.5 data source 0HR_PY_PP1.

The activation of DSO turns red and fails but there is nothing in the activation log for this DSO except to say activation started.

Note 916936 does not apply to us, we are at SAPKW70106.  I am loading a HUGE number of recs 15 million due to retro pay processing.  I have deleted the request and tried to re-load more than once and it is failing at exactly the same number of records added which is ~ 5 million mark. I am using a Process chain as well.

I have started another infopkg with shorter time frame for a data load

Any suggestions appreciated.  Error message is below.

Thanks a bunch !!

Error Occured After Updating Request 322.811(REQU_4VMVYIO5P0P1ZM7O7OQ2YCESP) Into Data Target 0PY_PP_C1

Message no. RSMPC121

Diagnosis

Error text: Activation is still running - data packat '0' stil

[former_member182516 · Accepted solution]

Hi Laura,

Are there any short dumps in ST22 with respect to this DSO activation failure?

We can activate t15M records but proper system setting need to be set and also make sure you have enough system resource to activate such huge volumes of data.

Which system you are trying? if its in DEV or QA system resource are less when compared to PROD. if you are in QA or DEV try to split the data load and activate the DSO requests.

Try to increase the No of parallel processes

TCode: RSODSO_SETTINGS --> enter your DSO object --> Change

Here you can set the max activation wait time and data package size.

Set the data packet size to 10000 and wait time to 600 secs. But this need to be calculated based on the system parameters. check the below link for more details.

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0d82054-f705-2e10-75b8-fc0f428bc...

Next click on "Change Process Parameters" button --> below window will pop up ,here set the no of parallel process and Parallel processing to Background --> save.

Change the priority of the job to 'A".

Regards

KP

[colm_boyle · Accepted solution]

Hi Prashanth and Laura,

Following Prashanths instruction above is perfect.

However, with such a large load it might not be best practice to set the datapacket size to 10,000 because there will be too many datapackets for activation. i.e. 15million / 10,000 = 1500 datapackets, according to the note 892513 you should not have more than 1,000 or the application struggles. Between 20,000 and 40,000 is more advisable, depending on the amount of parallel processes you set to run in the background. The more parallel processes the easier the system can allocate 'Work Processes' for the datapacket activations.

SAP common recommendations:
Batch processes    = (All Processes/2)+1
Wait Time in Sec.  =   3 * rdisp/max_wprun_time
rdisp/max_wprun_time - RZ11  (Note 25528)

Please refer to the Note 1118205 for more detailed info.

p.s. I would recommend reloading with selections, this way you could load 3 x 5million records, and in this case you could follow the 10,000 records per datapacket recommendation. You need to test these parameters based on available background work processes, size of the load, parallel setup of processes in your chain and of course, if this is the actual error. Are there any other details? The only way to make sure if it is the error is to retry the load with smaller selection criteria. If it fails again we can continue with further root-cause-analysis.

Also, do you have a screenshot of the process chain step? How many parallel steps in the activation of this DSO in the Process Chain?

Thanks,

Colm

[Former Member · Accepted solution]

Thanks Colm

I now have access to RSODSO_SETTINGS but I am wondering if these parameters will affect my problem because the step in the chain that is failing is "UPDATE from PSA" which is before the activation step ?

[former_member182470 · Accepted solution]

RSODSO_SETTINGS is only for activation purposes.