Skip to Content
author's profile photo Former Member
Former Member

Foreign trade import configuration for purchasing document



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,


Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Posted on Jan 30, 2018 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.

    Add a comment
    10|10000 characters needed characters exceeded

    • 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.

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.