cancel
Showing results for 
Search instead for 
Did you mean: 

Automatic negative delivery costs in PO

former_member368750
Participant
0 Kudos

Our customer is creating imports Purchase Order and maintaining different conditions to capture planned delivery costs at document header level

The PO is saved and invoice receipt is done for the planned delivery costs .Now on the same Purchase Order when two new line items are being added, the system is automatically making a specific condition value as negative.

Thus, the system is prompting an error message “Negative delivery costs not allowed” Message no. 06259” and not letting to proceed further.

We intend to find out the specific reason behind the automatic occurrence of negative value against a specific condition type.

Our customer would not be able to reverse subsequent documents because payment, LC and other documents are already released to the vendor with respect to this PO.

Accepted Solutions (0)

Answers (6)

Answers (6)

JL23
Active Contributor

In general SAP allows to add new items to a PO at any time.

However it is not really logical to go back to an old PO which is completely fulfilled to add new items.

Since the only thing in common is the same vendor, but it is a totally different business case, hence you should create new documents instead of reopening old documents.

Over some time your POs just get bigger and bigger and navigation within the PO becomes more complicated, not to speak about the performance and the time needed to open the PO, to post an invoice to POs with a large history. It makes root cause analysis in case of problems more difficult.

It is just good practice to create new POs for new business cases, you wont find a single OSS note telling you that, but when you search for performance notes for MIRO then you certainly find the hints about the large PO history.

Beside of that, since it is in general allowed to add new items to an old PO it must not result in such error that you current have.

So you can in general avoid this error by just following good practice and creating new POs instead of necromancing old POs.

But currently you have this error, and if you want solve it, then you need to describe it in much more details, e.g. explaining the setup of this specific condition, together with providing screenshots, and also showing what history you already have in your PO which could potentially cause this side effect to new items.

mohsinabbasi007
Active Contributor
0 Kudos

Dear Rameesa Shabbir,

Just found today an SAP Note regarding your concern negative Delivery cost i.e. 87983 - Negative delivery costs after goods receipt, 133329 - Negative delivery costs in purchase order. I think by applying these notes you will get your issue resolved.

Best Regards

Mohsin Abbasi

former_member511707
Participant
0 Kudos

Quote: "We intend to find out the specific reason behind the automatic occurrence of negative value against a specific condition type."

=> it is because your condition type "control data" has a negative control type(Plus/minus) in IMG configuration. and your condition type has a "condition category" of delivery cost.

mohsinabbasi007
Active Contributor
0 Kudos

Dear Rameesa,

Could you elaborate, why your business process required 2 new line items to be added, after once the PO is saved and definitely you company do have a release strategy as well.

We also have import process but we never ever came in such situation in which we needs to add line item once even invoice has been done regardless of GR, yes there might be a change in quantity, as it is import. So LC has also been opened on performs invoice, upon which you have to create PO in SAP as well to make payment in advance w.r.t PO.

What i am presuming is the problem of business process more then SAP.

Best Regards

Mohsin Abbasi

0 Kudos

I agree with you that this should not be the SOP... Can you share any SAP Note on this? Where SAP prohibits the addition of line items after once IR and / or GR has been posted.

If anyone can share some relevant documentation on this, it will be great and we will refer the same to the customer.

Regards,

M. Tuaha Mustafeez

mohsinabbasi007
Active Contributor
0 Kudos

Dear Tuaha,

It is just like that if we have standard document type of i.e. NB for the Purchase Order in SAP, we can create service PO as well from this Document Type, the question is why we normally created other document types as per business like for Services PO's, subcontracting PO's, Imports etc. Just to map business process properly and to remove complexity for the Users. So likewise you should not be allowed to change PO once either GR has been done or invoice has been done in general until and unless you do reverse process. e.g. A+b+c are the step to reach invoice, then if you are to make changes on 1st step then you have to go reverse i.e. C-B-A. Although there is option to reverse in SAP directly i.e. Reversal of GR Despite invoice. but we normally recommend it as per client requirement.
Just Cut long story into Short, to avoid complexity you have to develop SOP, and i still very much confuse why you need to change PO in-case of import as already you mentioned that Payment Method is also LC, in which we have to submit Performa invoice as well with bank, if there is a change in Performa invoice then LC should also be amended, and accordingly you have to change PO, but at this point of stage there is no concepts of Goods or invoice other then Bank.

I think jrgen.lins has explained you question in very comprehensive manner. I hope it is cleared now.

Best Regards

Mohsin Abbasi

former_member183424
Active Contributor
0 Kudos

New line item has a new conditions, it is nothing to do with existing line item, so it is not required to reverse subsequent documents for existing line item. Did you check the analysis button to check from where the condition value is getting picked?

JL23
Active Contributor
0 Kudos

Are you certain you have no own coding which could cause this trouble? Transaction ANST can be used to analyze the behavior, to find OSS notes and also point you to own coding. PANKS functionality can be used from the error message itself to check for OSS notes.