Tolerance check for Overpick in O2C cycle

[Former Member]

Hello

I was working on the normal O2C cycle. SO>>Delivery is created in ECC, Over/Under delivery tolerance is 0%, unlimited delivery check is inactive. Same is replicated to EWM as well (no tolerance).

Yet, during picking, if I try to pick extra qty using exception code OVER. Pick task is confirmed with this exception code & the warehouse request is adjusted using process code O001. Same is communicated to ECC after PGI & it went through.

I also tried restricting the use of exception code OVER for business context TPI, step 02, 05 & 06, no luck here as well.

Same is true for underpick as well, using the same exception code OVER.

Researched SCN, market place, QnA...everywhere, tolerance for purchase cycle is elaborated. Wondering if this basic functionality is even available for O2C cycle.

Any input is truly appreciated, thanks in advance.

[Former Member]

I tried switching the Round up at storage type level & tried creating a pick task. System threw an error saying ODO must not be overpicked. The inference is the system by default honours the ECC delivery tolerance check & doesn't allow Over / Short pick until we use a process code in Delivery.

What's also interesting is, there is no way to have the "Unlimited delivery' check in ECC for STO deliveries or have Overdelviery tolerance check (Note 548914) which is kind of a bummer.

[Ajit_Routray]

Hi Girish Nataraj,

As per my understanding, it is not used as a filter for Delivery Type. Please read documentation.

For your requirement- Could you please remove the Process code Profile from Delivery(ODO) Item type Configuration and check the system behavior?

OR BADI-/SCWM/EX_EXCP_EXC_FLT

Kind Regards,

Ajit

[Former Member]

Hi Ajit, Thanks for suggesting the BADI. Our scenario goes this way - We have to overpick for STO's, never for customer orders. We have a single Doc type & multiple item types, which are determined based on the business process.

If I remove the Process code, it won't work for STO's. Wondering if there is no sort of tolerance check at all in the O2C cycle?

Ultimately we may have to look at the BADI if is nothing is available in the standard.

[Ajit_Routray]

Hi Girish Nataraj,

"I also tried restricting the use of exception code OVER for business context TPI, step 02, 05 & 06, no luck here as well."- > I guess exception code OVER is custom (Not Standard so config has no impact) ? Please check.

https://help.sap.com/viewer/9832125c23154a179bfa1784cdc9577a/1809.000/en-US/c5cbcb53ad377114e1000000...

Kind Regards,

Ajit

[Former Member]

Hi Ajit

That is correct, we configured this code, forgot to mention that. The point is, there is this filter in the configuration of exception code on Item type. I have maintained this on only the item types for which over pick is applicable. Still, the system ignores this setting for the item types which arent configured here.