Impact of removing incoterms

[Former Member]

Hi,

Our client has advised that they are intending to remove the usage of a few incoterms.

What is the best practice to remove incoterms?

Straight-forwardly speaking, it would be to use t-code "spro" and use the Display IMG -> SRM -> SRM Server -> Cross-Application Basic Settings -> Create Incoterms screen. However, would this affect previous documents that have been created using the old incoterms? We only want to prevent users from creating new documents using the incoterms that are planned to be removed, but we do not wish to break any previous documents. Is there a way to mark an incoterm as "inactivated" but allow the record to still remain in BBPC_INCOTERMS?

Thanks in advance for any advice!

[Former Member · Accepted solution]

Hi

Try to implement check / change badi to validate old incoterms

[Former Member]

Hi Santhosh and Govardhan,

Many thanks for your replies.

For implementing checks via badi, it requires some manhours for coding and regression testing, which the customer is reluctant to pay for, and hence we have been asked to explore other options. Otherwise, yes I think this will be the best way to implement the change.

Simply removing the incoterms using IMG will cause errors when we try to save over existing documents that make use of the obsolete incoterms. For example, it is possible that the client wants to modify the price of an item. Saving will then throw an "Incoterm not found" error.

Eventually, we may have to resign to do a simplified (and "crude") way of addressing this issue: by renaming the full descriptions of the obsolete incoterms to mark it as such (users will have to use their own discretion to see), and to caution users against using them.

[Former Member]

Hi Kwong,

There is no impact on old documents once the document has been created and transferred to back end.

You can delete / modify the Inco terms in IMG, under  IMG > SRM > SRM server > Cross app basic settings > Create Incoterms

I had a similar instance and tested this in various scenarios. You can reprocess the previous documents and system doesn't give any error messages even thought the inco term  doesn't exist.

You can test this before moving the change to production.

Regards,
Govardhan