Configuring SAP Global Trade Services – GTS200 — Lesson 2: Legal Regulations, Embargo Checks, Sanctioned-Party Screening, Legal Control, and Licenses

Learning Objectives

• Explain the SAP structures, data, settings, roles, and dependencies governing legal-regulation activation and screening.
• Perform and validate embargo, partner, and license controls using reviewable system evidence.
• Evaluate the condition where a shipment is blocked because embargo screening, sanctioned-party results, license determination, and customs-document status do not agree and select proportionate corrective action.

Detailed Topics

• Legal Regulations applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• Embargo Checks applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• Sanctioned-Party Screening applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• Legal Control applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• and Licenses applied to the course scenario, expected SAP behavior, dependencies, and evidence.

Instructor Demonstration

The instructor traces a global trade team standardizing import and export controls across multiple company codes, customs offices, and legal regulations. The walkthrough connects navigation, configuration or process logic, system messages, and evidence captured in the GTS200 compliance, customs, and legal-control configuration workbook. It also tests the exception where a shipment is blocked because embargo screening, sanctioned-party results, license determination, and customs-document status do not agree.

Hands-On Exercise

Complete a controlled SAP exercise covering Legal Regulations, Embargo Checks, Sanctioned-Party Screening, Legal Control, and Licenses and preserve the verified result in the GTS200 compliance, customs, and legal-control configuration workbook.

1. Confirm scope, prerequisites, master data, roles, dependencies, and acceptance criteria.
2. Execute the workflow while recording settings, transactions, outputs, and system messages.
3. Test normal behavior, one boundary condition, and the stated exception.
4. Document corrections, evidence, ownership, retest criteria, and handover actions.

Scenario Analysis

• Identify which object, rule, setting, or process step most strongly influences legal-regulation activation and screening.
• Compare two defensible responses and explain business, technical, control, and support trade-offs.
• Determine how the GTS200 compliance, customs, and legal-control configuration workbook should be approved, retained, retested, and updated.

Troubleshooting Guidance

Start where expected SAP behavior first differs from the observed result. Check master data, configuration sequence, authorization, integration, status, and transaction evidence separately. Treat “a shipment is blocked because embargo screening, sanctioned-party results, license determination, and customs-document status do not agree” as a hypothesis until system settings, logs, documents, and outcomes confirm the cause.

Validation Checklist

• Required SAP structures, master data, roles, settings, and dependencies are present.
• The GTS200 compliance, customs, and legal-control configuration workbook connects each conclusion to objective, reviewable evidence.
• Normal processing, the boundary condition, integration behavior, and exception were tested.
• Corrections, ownership, retest criteria, documentation, and operational handover are complete.

Lesson Outcome

Learners can apply Legal Regulations, Embargo Checks, Sanctioned-Party Screening, Legal Control, and Licenses, explain the resulting SAP behavior, and defend the outcome through the GTS200 compliance, customs, and legal-control configuration workbook.