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.

[colm_boyle]

Hi Laura,

we received your SAP Support Message and have sent it back requesting remote access for analysis. Hopefully we can get this issue sorted a lot quicker now 😉

Thanks,

Colm

[colm_boyle]

HI Laura,

can you copy a screenshot of the 'Longtext' of the error into this message, including the diagnosis, the procedure etc.

It seems the spelling is strange, i.e..... data packat '0'

-> would usually be "datapacket" and  '1' or more.  If I can see the error in full in a picture i may be able to advise further.

Were there any SM12 locks, or updates to further targets, a screenshot of the process chain may help with this also,

thanks,

Colm

[Former Member]

Hi Colm

This is exactly the error message. I noticed that misspelling and the word chopped off too but this is the long text.

There were no locks in SM12.  Here is the chain that is failing at Update from PSA step.

Thanks for your advice.

[RamanKorrapati]

hi laura,

Seems like you missed error message details.

You need to select failed process chain step--> right click--> display message, there you can see error message.

or

Go to your DSO--> right click--> manage--> activate icon--> on next pop screen, there you cans ee activation jobl ogs, choose date wise which you had failed one.

Thanks

[former_member182470]

15 Million is massive amount of records. You should not try to activate such a big request. Break this data load into multiple smaller requests. Then try to activate them. This will certainly activate all your 15 million data.

Settings to be done in BGDs as 10 and above. If you are not reporting on this DSO, just switch off SID generation.

RSODSO_SETTINGS t-code. Increase all parameters here.

[Former Member]

Thanks for your reply Suman.  Unfortunately data is already extracted and I am trying to avoid re-loading it.  I was not aware that a large retro pay was processed or I would have done that for sure.  Is there anyway to do that on BI side ?

What is BGDs ? Where do I turn off SID generation ?  Is the parallel process parameter in RSDDSO_SETTINGS ?

Thanks again Laura

[former_member182470]

Hi,

In your DSo Activation window, you can find Activate in parallel button. Hit it and increase BGDs number here and save it.

SID generation settings is there in DSO definition. If it is a first load data to this DSO, then delete this Req from DSo and reload from PSA.

Try to get the access for the mentioned t-code and change the parameters to process such a massive volume.

[colm_boyle]

HI laura,

when you say you are getting the error when activating DSO, do you just mean you are getting the error when running the request? Is there any 'activation' error as such, or simply a failed request?

Also, on a seperate subject, are you familiar with the following note...

892513  Consulting: Performance: Loading data, no of pkg,req siz.

Please make sure your datapackets are below 50,000 records and you load no more than 10million per request.

If all the records have been extracted and the issue occurs on the activation step, then check the following note and change the activation parameters for 0PY_PP_C1 in transaction RSODSO_SETTINGS, depending on the number of parallel activation processes you have in your chain...

1392715 DSO req. activation:collective perf. problem note

1118205 RSODSO_SETTINGS Maintain runtime parameter of DataS

Are there any other logs, SM21, SLG1, ST22, SM37, etc.?

Thanks,Colm

[Former Member]

Hi Colm

Thanks for your reply.  The error is happening in "update from PSA' step of Process chain.(This is 3.5 DS to a 3.5 DSO - not migrated). Data packets are ~23,000 res each.  The request turns RED but not error message on DSO log, nothing in ST22, SM37,SM21 - I checked all that.

I have asked for auth. access to RSODSO_SETTINGS.  Can I change these setting with data in the DSO already ?

[RamanKorrapati]

Hi Laura,

Is this req was there at DSO level - 322.811?

If not then deletion may be happens partially. you may need to delete above request from base tables.

Careful, Just check below tables. whether above req exist or not

Tables - RSICCONT, RSMONICDP, RSODSACTUPDTYPE

and RSODSACTREQ

Thanks

[Former Member]

Thanks for your suggestion, I have checked all the tables and that request does not exist in any of them.

[RamanKorrapati]

Hi,

please check oss notes which are shared by mates. if not helped then search at sap market place you may get relevant note.

Thanks