cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

New ODO or WT not getting created when BIDF exception code is used for short pick

0 Likes
5,045

HI All,

We have configured an exception code in our EWM system to cater the needs of pick denial.

So, whenever the physical stock in bin is say less than the required quantity, then system should pick the available bin quantity and create an additional warehouse task for picking the remaining quantity.

I have activated Bin Denial at warehouse level.

At WPT, I have maintained the bin denial related two configs.

Trying this short pick in RF.

I expect a new task created from another bin to complete pick. But thats not happening. Rest working fine i.e. Physical Inventory doc is created and source bin in blocked for inventory.

Accepted Solutions (1)

Accepted Solutions (1)

Ajit_Routray
Active Contributor
0 Likes

Hi SAYAN PAL,

Do you use Wave Management/Templete ? If yes, I guess you might miss this below settings for pick Denial.

Please let me know if you have further queries on this.

Kind Regards,

Ajit

Answers (4)

Answers (4)

0 Likes

Hi Juergen,

I dont want to create new ODO. But I found the below in SAP help ( F1 on Action on Pick Denial ). So I thought new ODO will be created. But happy if we get a new WT from new bin where stock available.

Kindly advise.

snipimage.jpg

0 Likes

hi Juergen,

Thanks for your response. I am describing the requirement below.

The requirement is like below

1. Picking WT is created with 10 qty. Picking is done via RF.

2. When picking, I am using external exception ZIDF or ZIDP ( mapped to internal code BIDF and BIDP respectively ) to short pick. For example when I using ZIDF, I am doing a full short pick with 0 qty.

3. A physical inventory document is gets created and an email is triggered - This is working fine

4. The source bin is inventory blocked - This is working fine

5. In ODO, the qty is getting reduced to 0 - This working fine.

6. The last requirement is that system should automatically create a second pick ODO/WT from another bin where stock is available.

Please note : Picking Strategy should be able to identify the alternative bin.

I have tried both ZIDF and ZIDP. But its not working for me. When I check SLG1 log, I cannot find the log where system is trying to create a new ODO/Wave/WO/WT. So I am not sure even if the workflow to create alternative WT is at all getting triggered.

Can you please suggest.

This is same problem I am facing which is described in the below link. But I am not sure how it was resolved.

https://answers.sap.com/questions/12011461/pick-denial-process-with-proposal-new-bin.html

JuergenPitz
Product and Topic Expert
Product and Topic Expert
0 Likes

Hi,

ok, just for my understanding: why do you want to create a new ODO - when at the same time you want the system to create a new WT from an alternative bin? Why that additional hassle?

Brgds

Juergen

JuergenPitz
Product and Topic Expert
Product and Topic Expert
0 Likes

Hi,

"Trying this short pick in RF."

That means you enter the bin denial during picking?

Then these two settings:

"I have activated Bin Denial at warehouse level.

At WPT, I have maintained the bin denial related two configs."

have nothing to do with that. These trigger an internal exception code when you create a WT and the system can not determine enough stock. This internal exception code (WR02) then must be connected to an external exception code (in the standard we delivery PD02) - but that means that it is a totally different process.

For what you want (if I understand that correctly, but what you write: "So, whenever the physical stock in bin is say less than the required quantity, then system should pick the available bin quantity and create an additional warehouse task for picking the remaining quantity.") you need to assign the internal process code "BIDP" to your exception code.

Brgds

Juergen

---
Want to learn EWM?
Check for EWM courses @ https://training.sap.com/trainingpath/Applications-Logistics+Execution+%26+Warehouse+Management-SAP+...
Get a SAP Learning Hub Subscription: https://training.sap.com/shop/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!

0 Likes

HI Ajit,

Thanks for your response. I tried this option but the result is same. Can you please tell me how can I see the log for this new WT creation. I am not sure even if the system tried creating new WT on exception code ZIDF/ZIDP.

I have maintained the attached config.

Can you please let me know what is expected a new ODO or only new WO/WT.

Ajit_Routray
Active Contributor
0 Likes

Hi SAYAN PAL,

Could you check the FM-/SCWM/TO_CREATE_BIN_DENIAL ? Specially the below line (Queue,AA,WOCR)..Not Sure. Please check in debug.

Kind Regards,

Ajit

Ajit_Routray
Active Contributor
0 Likes

Hi SAYAN PAL,

The above is for WT checking.

For New ODO Generation: Could you please try in your exception code ? Process Code should be O002

Kind Regards,

Ajit

0 Likes

Hi Ajit,

At last I am able to run the scenario and a big thanks to you.

Right now new ODO is getting created on bin denial and a wave. But wave is not getting released automatically. I have to manually release it to get new WT from alternative BIN.

I have maintained the wave template configuration as mentioned by you and changed to option "B" i.e. create WT with an alternative Bin immediately". But still wave is not getting released immediately.

Any clue on this ?

Regards
Sayan

Ajit_Routray
Active Contributor

Hi SAYAN PAL,

"Right now new ODO is getting created on bin denial and a wave. But wave is not getting released automatically. I have to manually release it to get new WT from alternative BIN."-> It can not release again automatic once it released. Please configure PPF for auto create WT/WO using condition if possible.

"I have maintained the wave template configuration as mentioned by you and changed to option "B" i.e. create WT with an alternative Bin immediately". But still wave is not getting released immediately." -> This is applicable to same activity area where user can pick the stock.

Kind Regards,

Ajit

0 Likes

Thanks Ajit,

"Right now new ODO is getting created on bin denial and a wave. But wave is not getting released automatically. I have to manually release it to get new WT from alternative BIN."-> It can not release again automatic once it released. Please configure PPF for auto create WT/WO using condition if possible. -> Yeah this is clear. But I dont want to manually release the wave. I want it to be automated.

Btw one last doubt. I have configured the follow on work flow to crate Inv doc and its working fine.

But physical Inventory document is not getting created for the bins if there is any open WT already existing on that bin. Is there a way we can get all other open WT cancelled automatically and new WT getting created for those task from alternative bins if stock exists. ( same as first WT which was cancelled/partial picked using exp code BIDF or BIDP) As a result, Inv doc also gets created on the bin.