Skip to Content

Foreign trade import configuration for purchasing document

Jan 30 at 08:55 AM


avatar image
Former Member



I need help in case of foreign trade/ customs configuration required for purchase order and scheduling agreement.

My scenario is I have company code with country code as ZA South Africa and my requirement is when a vendor country and purchase order country is different then a foreign trade data should update for PO. Also at time of Inbound delivery a foreign trade data should be automatically get updated in inbound delivery.

I know the steps - 1. Maintain material with Foreign trade import data

2. Create a new pricing schema with conditions - JCDB,JCV1

3. Assign it to vendor in purchasing view

3. Create PO and import tab will available in PO

4. MIRO before MIGO

I am new in case of Tax related configurations. How import po procedure will impact at FI side.

Will you please provide me detail configuration steps and things which i need to consider before doing configuration.

I need to have foreign trade data automatically in Scheduling agreement, PO and inbound delivery.

Many Thanks,


10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Jürgen L
Jan 30 at 09:09 AM

I am rather skeptical that your given steps lead to an import data screen in your purchase order as pricing procedures have nothing to do with import data screens.

The import screen in a PO is controlled from customizing in transaction OLME > Foreign Trade/Customs > Control Foreign Trade Data in MM and SD Documents > Import Screens In Purchasing Document

Kindly search for existing blogs, wikis, discussions on tax related configuration and do not ask different questions in one discussion.

Show 6 Share
10 |10000 characters needed characters left characters exceeded
Former Member

Hello Jugen,

I will take care for single question in single discussion.

@ SPRO path provided it is already enabled as - Call up import data screens for every import.

but i cant see import tab in purchase order.



Then SAP is probably not able to identify an import.

An import is always then when the country of your plant (customizing) is different from the country of your vendor (vendor master)


you are talking about service items (item category D) which are not enabled for import data.

Former Member

hello Jurgen,

Thanks for your info.

An import is always then when the country of your plant (customizing) is different from the country of your vendor (vendor master) - yes its true company code county and vendor county is different still purchase order is not with import view.

Let me know is there something missing from my side to enable import tab in Purchase order.

Many thanks.


Unfortunately there is not more from a MM point of view which has influence other than countries and item category and customizing of import screens, except the right sequence and the release.

If you changed the country in the vendor master or your customizing after the PO was created then such change does not effect the existing PO.

if you are in S/4 HANA then see OSS note 2402490 - Foreign trade / import data missing in S/4HANA release

Former Member

Hello Jurgen,

I observed one strange thing here in Developement system the Import tab is not coming but in case of devlopment test system this tab is present in Purchase order.

I have checked configuration it is same in both system and i have vendor from other country than purchase order.

Can you please comment as per your experiance.



if you have a difference in both system then there is not much that I can do without knowing your system landscape, without being able to look into it.

Of course has a development system developments that are not yet released to production which could effect the behavior. Basis could have applied a hotpackage with thousands of OSS notes which cause a difference. But usually it is just the master data that has not the same quality than in a production system and a Q-system is often a copy of production while development systems data is just rudimentary created from scratch to serve a certain internal test situation.