SD / O2Cintermediate

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

Key takeaway

Follow trade data through order, delivery and billing: proposal and changes, copy control of export data, pro forma invoices for customs, billing as basis for statistical declarations, handling incomplete or wrong trade data, and corrections after goods left.

Explanation

📌 KEY POINTS
✅ Export data is proposed in the order, copied to delivery and billing; changes must stay consistent.
✅ Pro forma invoices (e.g. F8 from delivery) support customs clearance before the commercial invoice.
✅ Billing documents are the main source for statistical declarations.
✅ Incomplete trade data should block delivery or billing, not be fixed after declarations.
⚠️ Correcting trade data after declarations requires correction declarations — avoid it with upfront completeness.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 2 configured data and compliance. Now the lifecycle.

━━━━━━━━━━━━━━━━━━━━
▶ 1. ORDER

Proposal of trade data; compliance check.

━━━━━━━━━━━━━━━━━━━━
▶ 2. DELIVERY

Export data copied; customs documents and pro forma invoice.
Compliance recheck before goods issue.

━━━━━━━━━━━━━━━━━━━━
▶ 3. BILLING

Commercial invoice with trade data.
Declaration selection from billing documents.

━━━━━━━━━━━━━━━━━━━━
▶ 4. DECLARATIONS

Intrastat/Extrastat runs; error lists for missing data.

━━━━━━━━━━━━━━━━━━━━
▶ 5. CORRECTIONS

Fix master data at source; correction declarations if already reported.

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

Create export order → delivery → pro forma → invoice.
Check trade data at each step.
Run declaration selection and check errors.

✅ CHECKPOINT: declarations run without manual corrections.

Code example

ABAP Code

===== STEP 1: documents =====Order (trade data proposal) → delivery (export data, pro forma F8) → PGI → invoice F2 (trade data) → declaration ===== STEP 2: controls =====Incompletion for export data before delivery/billing | compliance recheck at delivery ===== STEP 3: declarations =====Selection from billing documents → error list (missing commodity code, origin, weights) → correct at source

Real project scenario

Intrastat reports required three days of manual fixes each month because invoices lacked net weights and origins. Making these fields mandatory via incompletion before billing and cleaning product master data reduced monthly corrections to a few cases.

Common mistakes

Fixing data in declaration tools instead of source.
No pro forma for customs.
Missing weights/origins.
No compliance recheck at delivery.
Manual declaration corrections as routine.

Best practices

Enforce completeness before billing.
Use pro forma invoices for customs.
Fix data at master level.
Recheck compliance before goods issue.
Monitor declaration errors monthly.

Interview angle

Questions: "How does trade data flow from order to billing?", "What is a pro forma invoice used for?", "How do you avoid declaration corrections?"
Strong answer: proposal in order, copy to delivery and billing, pro forma for customs, billing as declaration source, incompletion and compliance rechecks, source data fixes.

Practice this lesson

Quick check

1. Which document is typically used to support customs clearance before the commercial invoice?

2. Within SD order processing for export business, what is the main purpose of monitoring a Letter of Credit (L/C) against a sales order?

3. In SAP SD, foreign trade export data such as commodity code and country of origin is typically maintained in which material master view?

Interview questions

1. How would you apply Foreign Trade in a real SAP project? Walk through the design or implementation approach.

Answer it in your own words first, then compare.

2. A production issue is reported in Foreign Trade. What would you check first, and how would you troubleshoot it systematically?