Storage Control in the replenishment

[Atul_Joshi]

Hi All,

I have question regarding the POSC in the replenishment process.

As an requirement we need to map the replenishment using the POSC as repacking needs to be performed as an intermediate steps.

the storage process gets triggered with replenishment and product goes to the intermidate workcenter for repacking. but for the final putaway in the estination bin system does not take into account the bin selected udring the replenishment execution but again determines based on the WPT assinged to the step in the storage control.

Does anyone know what can be done in order to use the bin selected for replenishment as a destination bin.

juergen.pitz Hello Juergen your valuable insight would be very helpful.. Thanks!!

[former_member788724]

Please provide the details about your POSC steps and what you have setup for all POSC steps.

Share the screenshot of storage process please.

[container]

Hi bro!

Can you send screenshot about your customizing?

[JuergenPitz]

OK...

"I put my comments as per SAP note 2807808. "

Well, sometimes what is written in a note is not really correct...

The problem with LOSC is: if you create a WT for a partial quantity and check the WT after saving: yes, no LOSC is used. BUT: if you then process the WT with RF and create a pick-HU in the pick step - the destination bin is dynamically changed and LOSC is triggered.

"Please also let us know the POSC behavior when we have crate part or KANBAN synchronous WT replenishment. "

No idea. The question was about replenishment, so I tested replenishment. I could imagine that create part replenishment does also work, but I would have to test it, and maybe it does not work. These synchronous WT creation things (which are all bad decisions, IMHO), have several limitations, as was discussed in other posts already, so probably that also does not work. But that is more a problem of these WT creation triggers, then POSC or LOSC.

"Yes so the destination bin got determined based on the WPT in the POSC and not the one determined in replenishment transaction"

Again, the problem is the WPT you are using. I used for example the WPT 3060 (one of the old WPTs from early BC sets, which has NO source or destination information) and then it works.

Brgds

Juergen

[JuergenPitz]

Hello atul.diwakar.joshi ,

I had to set this up first to test it. But at least with a replenishment for fixed bins, that worked for me with POSC.

" but again determines based on the WPT assinged to the step in the storage control."

Of course you should NOT use then a WPT with a destination storage type / bin. I entered in the POSC settings a WPT without assignment and just the storage type, the bin was read from the fixed bins assignment. I have not tested with a storage type without fixed bins... wait, that of course also works.

LOSC would not be the good choice when you want to repack. But " If system has picked partial HU then LOSC won't work." - is of course wrong. Also with partial HU picks you can use LOSC, you only need to create a pick HU during the pick step.

Brgds

Juergen

---

All the above is no official SAP statement.

Want to learn EWM?

Check for EWM courses: https://training.sap.com/trainingpath/Applications-Extended+Warehouse+Management-EWM+in+S4HANA

Get a SAP Learning Hub Subscription: https://training.sap.com/learninghub

And it is EWM. NOT eWM - Duh!

And if your question includes the word "transfer order" - do NOT tag the question with Extended Warehouse Management!

[former_member788724]

Hello Juergen

For LOSC:

I put my comments as per SAP note 2807808. as per this note- LOSC can work with partial HU removal only with pick point scenarion. as for as I know, pick WT will be always product WT. Let's know if we can also have pick WT as HU WT . I am particularily talking about OB01 step.

I need to test if LOSC really works if we setup pick HU creation while creating pick WT itself (Here I won't setup pick point).

Regards

ASLAM

[former_member788724]

Hello Juergen

Please also let us know the POSC behavior when we have crate part or KANBAN synchronous WT replenishment. I tested and found that system is not taking the destination bin as maintained in KANBAN CC or /SCWM/PSASTAGE.

I put only storage type in POSC last step OBK3 (Customized one). I checked with both rule based check ON and OFF with only storage type maintained.

[former_member788724]

Hello- more screehshots

[former_member788724]

Screenshots

[Atul_Joshi]

Hello Juergen,

Thanks for reply with analysis.

Yes so the destination bin got determined based on the WPT in the POSC and not the one determined in replenishment transaction. and system does not consider the bin selected during replenishment run.

Yes LOSC didn't help because we need to do repacking.

So this in line with my observation and understanding of the standard behavior.

Thanks again for confirmation.

Regards,

Atul

[shailesh_mishra5]

Hello,

It worked for me in Crate part replenishment process with POSC having OB01( Pick), Pack(OB02)and Stage(OB03) steps. The destination bin in Staging process (OB03)gets determined from /SCWM/PSASTAGE table. The setting which worked for me is keeping “destination storage type PSA 1000, storage section and keeping Bin entry blank in POSC set up. Tried with rule based also but when closing HU at OB02(Packing step), system did not create a follow up WT for OB03 step, a queue was stuck up stating- POSC destination bin could not be determined.

The WPT which I used is standard 3070 which does not contain any destination bin information. Please try it will work. And yes I tested it twice :-).

best regards

Shailesh Mishra

[anilverma02]

Hi Shailesh,

For OB03 WT, we first maintained the default bin in /scwm/psastage and then maintained GM bin determination in /scwm/gmbin_det for the PMR doc type and item type for specific warehouse no. and kept the bin empty. OB03 was successfully created with combination of POSC and LOSC.

Best Regards,

Anil

[former_member788724]

Hello

POSC is not so well designed for internal processes. This is what I have felt out of my experience.

Once you have POSC set for internal processes, system takes the final bin as per bin details maintained in POSC steps. It does not consider the destination bin maintained as per replenishment data or KANBAN CC.

You may explore LOSC - but keep in mind there are some special restrictions using LOSC like if will work perfect when you have to always pick the full HU. If system has picked partial HU then LOSC won't work.

What you can try is to look for BADI where you can influence the destination bin determination for the last put away WT when working with POSC.

Regards- ASLAM

[Atul_Joshi]

Thanks Aslam for your input but I thought there could be some config option which I might be missing otherwise for enhancement we can do the way you said..

[former_member788724]

I could not find and config option.

If you find something with config then please update us as well.

thanks.