Foreign Trade
SD / O2Cbeginner

SD Foreign Trade Part 1: Why Foreign Trade Matters in SD

Key takeaway

What foreign trade adds to cross-border sales: classification of products (commodity codes), export/import data in orders, deliveries and invoices, statistical declarations (Intrastat/Extrastat), export controls and sanctioned party screening, customs documents, and when to use SAP Global Trade Services (GTS) instead of built-in functions.

What this complete series covers

Learn Foreign Trade in a clear, practical sequence — from the basic idea to real project use, troubleshooting, and interview-ready understanding.

Who it is for
Best for SAP consultants, developers, and learners who want a practical understanding of Foreign Trade.
Prerequisites
Basic SAP S/4HANA navigation and an understanding of the business process are helpful. Configuration or transaction steps require suitable access to a practice or project system.
Final outcome
By the end, you should be able to explain Foreign Trade clearly, follow the main end-to-end flow, apply it in a project scenario, and troubleshoot the most common issues.
  1. Part 1: SD Foreign Trade Part 1: Why Foreign Trade Matters in SD

    Introduces the business and legal purpose of Foreign Trade functionality in SAP SD, the data it captures, and where it fits in the order-to-cash process for cross-border transactions.

  2. Part 2: SD Foreign Trade Part 2: Configuring Foreign Trade Data and Legal Control Integration

    Explains how Foreign Trade data is configured and maintained across material, customer, and document levels, how it flows through the order-to-billing cycle, and how legal control

  3. Part 3: SD Foreign Trade Part 3: Foreign Trade Data Through the Order-to-Billing Lifecycle

    Explains how foreign trade data (commodity code, country of origin, legal control results, preference status) is determined, copied, and re-validated as a document moves from sales

System and release assumptions: Examples focus on SAP S/4HANA. Exact apps, transaction codes, configuration paths, and field names can vary by release and deployment model.

Explanation

📌 KEY POINTS
✅ Cross-border sales need trade data: commodity code, country of origin, business transaction type, export procedure, incoterms.

✅ Statistical declarations (e.g. Intrastat within the EU) are built from billing/delivery foreign trade data.

✅ Compliance checks (export control, sanctioned party screening) must happen before goods leave.

✅ Many companies run compliance and customs in SAP GTS (or its successor), integrated with SD documents.

⚠️ Missing commodity codes or origin data block declarations and customs — and can cause fines.

━━━━━━━━━━━━━━━━━━━━
▶ WHAT THIS SERIES COVERS

Part 1: Why foreign trade matters in SD

Part 2: Configuring foreign trade data — master data and legal control integration

Part 3: Foreign trade data through the order-to-billing lifecycle

━━━━━━━━━━━━━━━━━━━━
▶ 1. TRADE DATA

  • Product: commodity code, country/region of origin.
  • Document: business transaction type, export procedure, mode of transport, customs office.

━━━━━━━━━━━━━━━━━━━━
▶ 2. STATISTICS

  • Intrastat (intra-EU), Extrastat/export declarations.
  • Data from billing documents (and deliveries).

━━━━━━━━━━━━━━━━━━━━
▶ 3. COMPLIANCE

  • Export control (license requirements, embargoes).
  • Sanctioned party list screening of partners.
  • Documents blocked until cleared.

━━━━━━━━━━━━━━━━━━━━
▶ 4. CUSTOMS

  • Export declarations, electronic customs filing.
  • Commercial and pro forma invoices for customs.

━━━━━━━━━━━━━━━━━━━━
▶ 5. SAP GTS

  • Central compliance and customs solution integrated with SD.
  • Built-in S/4HANA international trade functions cover classification and Intrastat.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

  1. Maintain commodity code and origin on a product.
  2. Create an export order and check foreign trade data.
  3. Create invoice and check export data.

✅ CHECKPOINT: the invoice carries complete foreign trade data for declaration.

Code example

ABAP Code
===== STEP 1: data elements =====Product: commodity code, country of origin | Customer: country, tax dataDocument: business transaction type, export procedure, incoterms, mode of transport, customs office ===== STEP 2: outputs =====Intrastat/Extrastat declarations from billing | export declaration (customs) | pro forma invoice for customs ===== STEP 3: compliance =====Sanctioned party screening (partners) | export control (licenses, embargoes) → block until released (often in SAP GTS)

Real project scenario

A mid-size industrial equipment exporter maintained commodity codes only for some products. Customs declarations were rejected, shipments sat at the border, and Intrastat reports needed manual corrections every month. Classifying all export products, making foreign trade data mandatory in the export order types and integrating sanctioned party screening before delivery removed delays.

Common mistakes

  • Missing commodity codes.
  • No screening before shipment.
  • Manual Intrastat corrections.
  • Treating pro forma invoices as optional for customs.
  • No ownership for trade data.

Best practices

  • Classify all traded products.
  • Screen partners before delivery.
  • Automate statistical declarations.
  • Assign trade compliance ownership.
  • Evaluate GTS for complex compliance.

Interview angle

Questions: "What foreign trade data is needed?", "What is Intrastat?", "When would you use SAP GTS?"
Strong answer: commodity code, origin, business transaction type, export procedure, incoterms; declarations from billing; export control and SPL screening blocking documents; GTS for compliance and customs.

Practice this lesson

Quick check

1. What is the main business purpose of 'preference determination' in SAP Foreign Trade?

2. What does Sanctioned Party List (SPL) screening within SD Foreign Trade functionality primarily check?

3. Which data element classifies a product for customs and trade statistics?

Interview questions

1. What are the core concepts of Foreign Trade, and how would you explain them clearly in an SAP interview?

Answer it in your own words first, then compare.

2. A mid-size industrial equipment exporter has shipments held at customs and monthly manual Intrastat corrections. How do you improve foreign trade handling?

Answer it in your own words first, then compare.

Practice more with Interview AI →

Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.

More lessons in this topic

Interview questions on this topic

Related SAP topics