No action because all incoterms are unfree

[former_member1115366]

I have recently configured a new shipment document type for “Collect” orders.  These shipments are not subject to costing, as the receiver of goods pays the shipping.

Every time one of these shipments is edited and saved, the annoying information message number 86312 “No action because all incoterms are unfree” pops up.  It can be entered through and changes are saved on the document.

The incoterms on the underlying deliveries are set up like COL Collect, which I believe to be standard SAP. 

I seek help in suppressing this information message.

Regards,

Ken

[JL23 · Accepted solution]

in what system are you working?

I have neither a message class 86

nor is COL a SAP standard Incoterm

Standard Incoterms can be found here:http://www.pfc-nordic.com/fileadmin/templates/PDF_filer/PFC/Incoterms_2010_UK_PFC.pdf

COL collect is an Americanized term of sale but not an Incoterm

[former_member1115366 · Accepted solution]

The message likely comes from an enhancement to the standard SAP transportation planning system from a partner called GPC. We do not need to use the functionality of GPC for this simple shipment type, but it seems to be getting in the way nonetheless.

I checked our configured incoterms against the link you provided.  The only common one is FOB, which is not suitable for these over-the-road, customer pick-up kind of shipments.  COL has been used for years in deliveries and billing, but never has it been involved in shipments.

It appears I was foolishly optimistic in that this new type would not involve GPC reconfiguration. 

[JuergenPitz · Accepted solution]

Hi,

you should NEVER use anything else as "Incoterm" then the ones officially described here http://www.iccwbo.org/. You will always loose in a court case if you have a transport damage and fight with the customer who will pay...

Brgds

Juergen

[former_member1115366]

Resolution:  debugged to find the line of code that generates the annoying message.  Applied modification to bypass the message when shipment type matches the newly configured one. 

Regards,

Ken