Splitting WO for PI-RF count

[m_vandenbiggelaar]

As a PI-area can only be assigned to one AA, I followed SAP and created 0001 as the activty area where all stockholding storage types (involved in the PI-count) are to be linked to.

So I created a sorting sequence via /scwm/V_TAAREAS (for activity INVE and activtyarea 0001 ) and /V_TAAREAD (for activityarea 0001) so that all countable bins do appear in the proper sequence in /scwm/SBST, for activity INVE/activity area 0001.

You might consider this overdone at first hand, but we intend to provide a WO-print (with limited info) to the RF operator so he can scan his own WO during the anual PI count. Therefore we do require multiple WO's, so that each RF-user can select his own task by simply scanning the submitted document. Differentiation in Queue assignment is therefore not meaning full. Having thus no further option to splitt the WO; I introduced a consolidation group representing a group of bins which one RF-operator can sequentially count. (done via /scwm/V_TAAREAD)

Accordingly I created a limit-rule where I specified that only 1 Consolidation group was allowed by WO. This limit rule was applied in a WOCR which is nicely applied during WO creation during creation/saving of the PI document.

However it still gives me only one WO instead of multiple WO's as per the different consolidation groups all belonging to activity area 0001.

Although SAP SPRO helps indicates that this should be possible; I fear this only works during picking (where the source and destination bin are different). Am I here on the correct path? Does anybody recognize this issue and may be somebody found a solution around this? Any suggestion is appreciated.

Best regards

Maarten

[former_member209095 · Accepted solution]

Hi,

I followed SAP and created 0001 as the activty area where all stockholding storage types (involved in the PI-count) are to be linked to.

This is a suggestion, not a restriction. You can multiply physical inventory area depending on activity area. Just sayin..

I introduced a consolidation group representing a group of bins which one RF-operator can sequentially count.

So you want to create WHO depending on a number of bins? If this bin number is standard for all users, you can create a copy from limit MX01 or maybe use MX10? If this does not fit, then you can use one of the BAdI's.

Best regards

Serhan

[m_vandenbiggelaar · Accepted solution]

Indeed; I thought of one PI-area being the warehouse (where all the same rules applies), but indeed it compromise a number of locations. So I will create several PI-areas and assign those to AAs used for INVE. This should work as now I can have different AA's which should give me different WO's per AA. Thanks!

[Ajit_Routray]

Hi Maarten,

Addition to above.

consolidation group wont work in PI.

Checking Warehouse Order Creation Rules - SAP Documentation

SAP Library - Supply Chain: Business Process Configuration

In WOCR Limit, You  can only use two parameters

Min.Items/WO

Max. Itm per WO

As suggested by Serhan , you can create multiple PI Area assign to AAs.

Please let us know if you have any other alternatives.

Thanks,

Ajit

[JuergenPitz]

Hi,

"I introduced a consolidation group representing a group of bins which one RF-operator can sequentially count (done via /scwm/V_TAAREAD)."

So where you assign the bins to the activity area you entered a consolidation group? That is actually a "deconsolidation" group, so AFAIK this only works for putaway.

Well, what is the limit you want to have for one user?

Brgds

Juergen

[m_vandenbiggelaar]

Hi Juergen;based on the help of /scwm/V_TAAREAD-DSTGRP I was indeed afraid that this consolidation group would only be relevant for putaway/picking-packing. As I did not immediately recognize why this restriction would apply; I thought it was worthwhile to try and ask the experts for their opinion as my result was inline with fear.  Thanks!

The limit is basically 1 WO by user; the PIPA sorting applied in /scwm/sbst for activity INVE, allows me to state that once the /scwm/lagp-aisle is changing of the listed bin; it should create a new WO.

As the aisles do contain always the same number of stacks, there is no opportunity to use the bin-count as a limit value.