cancel
Showing results for 
Search instead for 
Did you mean: 

Overdelivery tolerance - extended classic

Former Member
0 Kudos

Hi all,

We have extended classic scenario, and would like to have overdelivery tolerance. I've created a tolerance group in SRM, and assigned tol keys CF, DA and DQ.

I've also maintained a Purchasing Value Key in ECC via OMQW (SPRO --> MM --> Purchasing --> Material Master --> Entry Aids for Items Without a Material Master)

When I post the confirmation in SRM I get the appropriate error message (so if I try to post 106 for a PO with 100 qty, I get the error message, 105 is OK).

However, the IDoc goes into error in the backend, as the qty is exceeded. Error message: "PU Ordered quantity exceeded by 5 EA : <PLANTCODE>"

When I look at the PO inside SRM, in the item detail the overdelivery tolerance is 0%, and the ECC copy also has 0%. I would have expected them both to show 5% (and for this to copy-into the PO)?

If I create a new 'spot PO' directly in ECC (ME21N) with all the same detail, the 5% tolerance is coming through automatically from the OMQW setup.

Do you have any ideas how to get the overdelivery tolerance into the SRM PO, so that the copy in the backend would also show it (so IDOC will post successfully)?

Thanks in advance,

J

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

When I look at the PO inside SRM, in the item detail the overdelivery tolerance is 0%, and the ECC copy also has 0%. I would have expected them both to show 5% (and for this to copy-into the PO)?

But this has to be the cause of your confirmation error in ECC. Your PO has to show the tolerance in percentage and/or absolute value. Just a note, if you have defined both percentage and absolute values in tolerance, the absolute value takes priority, meaning if the confirmation is over the absolute tolerance value, but not the percentage value, an error would still occur.

If you think the PO process seems to be correct, you can take a look at this note and see if it applies to your case.

Note 1522984 - Tolerance from contract not set correctly back to PO items

Former Member
0 Kudos

Hi Jay,

Indeed I think this is the problem - the PO does not show any tolerance - it shows 0%.

In SRM I am able to successfully create confirmation with overdelivery, but because the PO shows 0% (and therefore ECC copy of PO also shows 0%) the iDOC goes into error.

For more info - We have ECC 6 EhP 4 and SRM 7.0 SP 9.

Any ideas how to get the PO to show the tolerance?

Many thanks,

J

Former Member
0 Kudos

I think you have to define the tolerance in PO to be 5, manually. Try that and see if it works out.

Former Member
0 Kudos

Hi Jay,

I am able to enter the tolerance manually in the PO, but we want the tolerance to go automatically into the Purchase Order.

I would have expected that because the tol group is assigned on the org structure, that it comes in automatically?

J.

Former Member
0 Kudos

I don't think the value in IMG would be defaulted in PO process for tolerance. You can try to implement BBP_DOC_CHANGE_BADI for BBP_PD_PO method to make the value as a default if you want to.

Former Member
0 Kudos

Hi,

I have a similar problem.

I have assigne a tolerance group in ppoma_bbp, but the purchasing group is not defaulted into the PO,

Therefore the % on the PO is 0, which leads to an error message when i hit check on the confirmations in SRM, even if I am within the tolerance limit.

Also when i try to search for the tolerance group on the PO it won't display.

If I update the tolerances the manually ont he PO the i am able to create an overdelivery.

We are on the same release ECC 6 EhP 4 and SRM 7.0 SP 9, extended classic.

Could you please update how you solved the issue?

Cheers

Ulrike

Former Member
0 Kudos

Have you assigned the tolerance group to the TOG attribute of the user (via PPOMA_BBP)?

Former Member
0 Kudos

Hi Jay,

Yes the tolerance group is assigned to the highest level node in the org structure for my user, and also on the vendor via ppomv_bbp

Any other ideas?

Many thanks,

J