SD Foreign Trade Part 2: Configuring Foreign Trade Data and Legal Control Integration
Set up foreign trade data: commodity code classification of products, country of origin, default business transaction types and export procedures, incompletion for export data, proposals from master data, and integration points for legal control and sanctioned party screening (built-in or SAP GTS).
Explanation
📌 KEY POINTS
✅ Products need commodity codes and origin; in S/4HANA classification is maintained via product classification functions.
✅ Default business transaction types and export procedures are proposed into documents.
✅ Incompletion procedures can make export data mandatory for cross-border documents.
✅ Legal control/SPL screening blocks orders or deliveries until compliance releases them (often via GTS).
⚠️ Screening only at order entry misses partner changes before delivery.
━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 1 explained why foreign trade matters. Now setup.
━━━━━━━━━━━━━━━━━━━━
▶ 1. PRODUCT CLASSIFICATION
- Commodity code per country/region, origin.
- Mass classification for large catalogues.
━━━━━━━━━━━━━━━━━━━━
▶ 2. DOCUMENT DEFAULTS
- Business transaction type, export procedure defaults.
- Proposed from master data (plant, customer, product).
━━━━━━━━━━━━━━━━━━━━
▶ 3. INCOMPLETION
- Export data fields in incompletion for export sales areas/document types.
━━━━━━━━━━━━━━━━━━━━
▶ 4. COMPLIANCE INTEGRATION
- Sanctioned party list screening of BPs and documents.
- Export control checks; blocks on order/delivery.
- GTS integration: documents transferred, status returned.
━━━━━━━━━━━━━━━━━━━━
▶ 5. RESPONSIBILITIES
- Trade compliance owns classification and releases.
- SD ensures data flows into documents.
━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP
- Classify products.
- Set defaults and incompletion for export.
- Activate screening/integration.
- Test a blocked export order.
✅ CHECKPOINT: an order for a sanctioned party is blocked, and export orders are incomplete without trade data.
Code example
===== STEP 1: master data =====Product classification: commodity code (e.g. 8471 30 00), country of origin DEPlant/customer data for proposals ===== STEP 2: documents =====Defaults: business transaction type (e.g. 11 sale), export procedureIncompletion: export fields for export document types/sales areas ===== STEP 3: compliance integration =====SPL screening of BP and documents | export control → block order/delivery → release by compliance (GTS status)Real project scenario
An exporter screened partners only at customer creation. A customer later changed ownership to a sanctioned entity; shipments continued. Adding document-level screening at order and delivery (via GTS) with automatic blocks and daily rescreening of partners caught the risk before the next shipment.
Common mistakes
- One-time screening only.
- Missing incompletion for export data.
- No ownership of classification.
- Blocks without release process.
- Manual defaults per order.
Best practices
- Screen at master data and document level.
- Make export data mandatory where needed.
- Maintain classification centrally.
- Define release responsibilities.
- Automate defaults.
Interview angle
Questions: "How do you configure foreign trade data?", "How is sanctioned party screening integrated?", "How do you ensure export data completeness?"
Strong answer: product classification (commodity code, origin), default business transaction types/procedures, incompletion, SPL/export control with document blocks and GTS integration, ownership.
Practice this lesson
Quick check
1. A customer changed ownership and became a sanctioned party, but shipments continued. What control was missing?
2. What is the primary function of the 'Legal Control' component within SAP Foreign Trade functionality during sales order processing?
3. A boycott list check within Foreign Trade functionality is used to identify which situation?
Interview questions
1. What are the most important design decisions, trade-offs, and best practices in Foreign Trade?
Answer it in your own words first, then compare.
2. Suppose you inherit an existing Foreign Trade solution. How would you review it before making a change?
Answer it in your own words first, then compare.
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.