on 2020 Jul 08 12:50 PM
Dear All,
I have configured LOSC with Pick Point. When I am doing Full Pallet Picking, Full Pallet goes to Pick Point, which is correct as per Configuration.
Then I change the Configuration (Refer attached Screenshot – LOSC) to check other Scenario and have an Issue with Partial Pallet. Scenario is -- > I need Picking for One Full Pallet and one Partial Pallet. When I pick a Full Pallet, it should not move via Pick Point and should directly go to Staging Area, and when a Partial Pallet is required, this should move to the Pick Point and I pick the required quantity and Leftover Quantity is moved back.
With this Configuration, when Task is created both Pallets (Full & Partial) directly goes to Staging Area (Partial Pallet is not going to Pick Point).
During analysis, I found both Tasks are directly going to Staging Area may be because, When Task is getting created, Active Tick Mark is coming by default for Partial Quantity as well, but I am not sure why this is happening.
I am using S4 Hana 1909 Embedded System. Any suggestion how to rectify this Issue.
Regards,
Avdhoot
Help others by sharing your knowledge.
AnswerRequest clarification before answering.
Hi,
question to 56461ebe76024ff482c5fe46aa8c6390 : What does the "K-Punkt" flag do for you?
Because (AFAIK) this flag does nothing at all. Or at least not in a standard storage type environment.
What controls the pick point behaviour, is the storage type role in the interim storage type.
avdhoot : For the full pallet the system creates a HU WT and that's why LOSC immediately is triggered. For the non-full pallet pick LOSC would be triggered when you process the pick with RF and create a pick-HU for the pick quantity in the process.
What is the storage type role of your storage type 0093?
Brgds
Juergen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jürgen,
you are right, I just checked the process again in a sandbox system. Do you have an idea why there is a flag when it does not do anything at all? (Not too sure why we had that setting back then; the screen shot was from a process documentation for a project a couple of years back).
Apart from the flag the settings in the screenshot are what I needed to get the process up and running.
Best regards Andreas
Hi 56461ebe76024ff482c5fe46aa8c6390 ,
I was hoping you could tell me 🙂
I actually believe they are artifacts from development, that there was the idea to use them, but it was never done as originally intended. But I might be wrong. I know the colleagues building MFS implementations are using these flags, but I don't know how this is then being used.
Brgds
Juergen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
WT Screenshot
| User | Count |
|---|---|
| 17 | |
| 16 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.