GTS · Global Trade Services
Preference LTSD Management SAP S/4HANA training
Training for inbound and outbound long-term supplier declarations used as preference evidence in SAP GTS.
Process overview and business context
LTSD processing manages evidence from suppliers and declarations to customers. It connects supplier-product relationships, request proposals, received declarations, validity, release and downstream preference determination.
Learners can request, enter, validate, release and monitor LTSD evidence and explain how invalid or missing declarations affect preferential eligibility.
End-to-end flow
- 1
Transfer supplier-product data
IntegrationFiori app: Preference Management worklists
ACDOCA impact: No accounting impact.
- 2
Create LTSD request proposals
FioriFiori app: Supplier Declarations
ACDOCA impact: Creates supplier-facing evidence requests.
- 3
Receive and enter declaration
FioriFiori app: Inbound Declarations
ACDOCA impact: Evidence is captured and validated.
- 4
Release LTSD
FioriFiori app: Manage Supplier Declarations
ACDOCA impact: Released evidence can support determination.
- 5
Issue outbound declaration
FioriFiori app: Outbound Declarations
ACDOCA impact: Customer receives preference evidence where eligible.
Key tables
| Table | Explanation |
|---|---|
| Supplier-product relationship | Basis for proposal creation and evidence management. |
| Inbound LTSD objects | Received declaration, product coverage, validity and release status. |
| Outbound LTSD objects | Customer-facing declaration proposals and issued statements. |
| Agreement data | Preference agreement, validity and rule context. |
| Business document proposals | Purchase and sales history used to propose requests or declarations. |
Step-by-step walkthrough
Build request worklist
Use supplier-product relationships and business documents to identify missing declarations.
Watch out for: Do not request declarations for irrelevant or obsolete products.
Maintain received evidence
Enter product, supplier, agreement, validity and statement details.
Watch out for: Validity dates drive downstream eligibility.
Release only checked declarations
Use release workflow once evidence is reviewed.
Watch out for: Unreleased declarations should not support preference claims.
Monitor gaps
Track missing, expired and invalid declarations.
Watch out for: Preference status can change when evidence expires.
Common errors and troubleshooting
Product not covered by LTSD
Likely cause: Declaration does not include the product or agreement.
Fix path: Correct declaration scope or request new evidence.
Declaration expired
Likely cause: Validity period no longer covers the transaction date.
Fix path: Request updated LTSD and rerun determination.
Outbound proposal missing
Likely cause: Business document or customer-product relationship is not proposal-relevant.
Fix path: Check proposal selection and partner/product master data.
ECC to S/4HANA differences
In S/4HANA landscapes, feeder data and document proposals are easier to integrate, but the same audit discipline around evidence validity and release remains essential.
Glossary
- Legal regulation
- Country or trade-law framework that scopes GTS checks and process rules.
- Feeder document
- S/4HANA or SAP ERP source document transferred or referenced by GTS.
- GTS document
- Local GTS object used for compliance, customs, preference, origin or Intrastat processing.
- Incompletion log
- Application log that explains missing fields, blocks and readiness issues.
- Audit trail
- Traceable evidence of checks, decisions, releases and messages.
- LTSD
- Long-term supplier declaration used as preference evidence.
- Inbound declaration
- Supplier declaration received from a supplier.
- Outbound declaration
- Declaration issued to a customer.
Knowledge check
Complete the quiz with at least 70% to unlock the certificate.
Start the generator