Performance OSS Note for PMR Processing
From this Blog post you can learn about one relatively fresh OSS Note, which from my point of view important for and System Performance in operations related to the Production Material Request (PMR).
This is only relevant for EWM with Advanced Production integration. and System Versions SCMEWM 950 or S4CORE from 101 to 106.
It took some time till we are figured out why do we have some performance issues in our system. (SAP Support knows how to platy Ping Pong) And there are some preconditions which makes described performance problem relevant for your processes.
- You use PMRs in the Production staging process.
- Your PMR documents are relatively big (in our case it is 1000+ items)
- You use order-based staging, or you write GI document reference in the PMR document
Here some signs which could help to understand if you have similar issues:
- For Warehouse task creation, confirmation, cancellation with relation to PMR takes long time (longer than expected, in our case it took more than 1 Second (up to 4 seconds for one operation)
- You cannot post GI with outbound delivery because of PMR validation error message, message could be from another, not related to GI Item. (e.g. /SCWM/PWR030 Goods movement bin &1 must be same as bin &2 for PSA &3)
Issue with error /SCWM/PWR030 could be theoretically solved with 3101708, but this is kind of “dirty fix” because system should not validate all the items during update of one item in PMR.
And so, we are coming to the main issue, during update of one single item system validates complete PMR. It happens because of the wrong BOPF Customizing, during call of the SAVE method Validation method HDR_CHECK_AUTHORITY requires reading of all items. You can check and correct it with following steps (as well described in OSS Note 3146978
- Start transaction /BOPF/CONF_UI, press Open and select /SCWM/PWR
- Switch to the edit mode (sure if you want to change, if you want only to check you can skip this step)
- Right-click on Business Object Element Assignments -> Component Assignment to Validations -> HDR_CHECK_AUTHORITY
- Uncheck /SCWM/PWR_ITM in nodes ‘Request Nodes for Validation’ and ‘Read Nodes for Validation’
- Save it (This is a correction of the system object)
- Since BOPF customizing is buffered via Shared memory next steps should be done in every system.
- Invalidate and Propagate area /BOPF/CL_CONF_SHARED (pay attention it is /BOPF/CL_CONF_SHARED and /BOBF/CL_CONF_SHARED, we need the first one)
After you should have performance improvements, which are noticeable for example in the RF picking, especially if you use exception codes (BIDU, BIDP) since they cause cancellation and recreation of the warehouse task. Or with standard /SCWM/STAGE if you create order-based WTs. Or as well if you post consumption.
Here are some results for similar to /scwm/stage report which creates warehouse tasks to PMR items.
Charts are aligned with time, upper chart shows execution time of the WT creation process (Scale 0 – 120 Seconds), and second chart showing number of created WTs (scale 0 – 1600), horizontal scale is from 8:00 day 1 till 13:00 day 2.
It is easy to see that maximal execution time was reduced. For this application it was not so important for the process (is still important for Carbon footprint reduce #clean-IT). And in the RF area with a single WT confirmation/cancellation performance improvement is up to 10 times.
For sure one can find this OSS Note by himself, but unfortunately it is not very well described in the OSS note (I assume because this OSS was just copied from similar OSS note for PDI/PDO 2747733)
And wrapping it up, if you use PMRs in your EWM System, check tcode /n/BOPF/CONF_UI for the object /SCWM/PMR, if for HDR_CHECK_AUTHORITY component has nodes /SCWM/PWR_ITM are selected for Read & Request they should be deactivated. After Shared memory cache should be rebuild for the area /BOPF/CL_CONF_SHARED. This disables unneeded validation of all PMR items during partial update of the PMR. Depends on the number of PMR items it could improve performance of the small operation up to 10+ times.
I hope this was interestig to read. And if you have questions feel free to ask in comments, or in Q&A section
You can find more EWM Blogs hier