GTS · Global Trade Services
Gestion des LTSD de préférence SAP S/4HANA training
Training for inbound and outbound long-term supplier declarations used as preference evidence in SAP GTS.
Vue du processus et contexte m?tier
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.
Flux end-to-end
- 1
Transfer supplier-product data
IntegrationApp Fiori: Preference Management worklists
Impact ACDOCA: No accounting impact.
- 2
Create LTSD request proposals
FioriApp Fiori: Supplier Declarations
Impact ACDOCA: Creates supplier-facing evidence requests.
- 3
Receive and enter declaration
FioriApp Fiori: Inbound Declarations
Impact ACDOCA: Evidence is captured and validated.
- 4
Release LTSD
FioriApp Fiori: Manage Supplier Declarations
Impact ACDOCA: Released evidence can support determination.
- 5
Issue outbound declaration
FioriApp Fiori: Outbound Declarations
Impact ACDOCA: Customer receives preference evidence where eligible.
Tables cl?s
| Table | Explication |
|---|---|
| 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. |
Parcours ?tape par ?tape
Build request worklist
Use supplier-product relationships and business documents to identify missing declarations.
? surveiller: Do not request declarations for irrelevant or obsolete products.
Maintain received evidence
Enter product, supplier, agreement, validity and statement details.
? surveiller: Validity dates drive downstream eligibility.
Release only checked declarations
Use release workflow once evidence is reviewed.
? surveiller: Unreleased declarations should not support preference claims.
Monitor gaps
Track missing, expired and invalid declarations.
? surveiller: Preference status can change when evidence expires.
Erreurs courantes et r?solution
Product not covered by LTSD
Cause probable: Declaration does not include the product or agreement.
Chemin de correction: Correct declaration scope or request new evidence.
Declaration expired
Cause probable: Validity period no longer covers the transaction date.
Chemin de correction: Request updated LTSD and rerun determination.
Outbound proposal missing
Cause probable: Business document or customer-product relationship is not proposal-relevant.
Chemin de correction: Check proposal selection and partner/product master data.
Diff?rences ECC vers S/4HANA
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.
Glossaire
- 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.
Test de connaissances
Obtenez au moins 70 % pour débloquer le certificat.
Lancer le générateur