GTS · Global Trade Services
Präferenzkalkulation SAP S/4HANA training
Training for preference determination, aggregation, threshold comparison and eligibility interpretation.
Prozess?berblick und Gesch?ftskontext
Preference calculation determines whether a product qualifies for preferential customs treatment under an agreement. It uses supplier declarations, BOM or procurement context, agreement rules, product data and value thresholds.
Learners can explain how determination consumes evidence, why products become eligible or ineligible and how to troubleshoot threshold and aggregation issues.
End-to-End-Ablauf
- 1
Collect evidence
FioriFiori-App: Supplier Declarations
ACDOCA-Auswirkung: No posting; provides proof.
- 2
Run aggregation
Fiori / jobFiori-App: Preference Determination - Aggregation
ACDOCA-Auswirkung: Prepares product-level data.
- 3
Run determination
FioriFiori-App: Preference Determination
ACDOCA-Auswirkung: Calculates eligibility.
- 4
Review result
FioriFiori-App: Preference Statements
ACDOCA-Auswirkung: Explains eligible or not eligible status.
- 5
Archive result
Fiori / backgroundFiori-App: Preference result archive
ACDOCA-Auswirkung: Supports audit and monitoring.
Wichtige Tabellen
| Table | Erkl?rung |
|---|---|
| Preference determination results | Eligibility, statement and reason information. |
| Supplier declaration evidence | Released LTSD and validity data used by calculation. |
| Product BOM / procurement data | Input for determining origin or eligibility of produced/procured products. |
| Agreement rules | Thresholds, validity and legal preference rules. |
| Business document values | Order or billing values used in comparison. |
Schritt-f?r-Schritt-Anleitung
Confirm agreement scope
Check agreement, country, product and validity.
Achten Sie auf: Wrong agreement context creates misleading results.
Validate evidence
Ensure LTSD and procurement data are valid and released.
Achten Sie auf: Invalid evidence is as bad as missing evidence.
Run calculation
Execute aggregation and determination.
Achten Sie auf: Run sequence matters when data changed.
Explain status
Use result reasons to explain why a product is eligible or not.
Achten Sie auf: Do not override preference results without evidence.
H?ufige Fehler und Fehlerbehebung
No preference result
Wahrscheinliche Ursache: Aggregation or determination was not run after data changes.
L?sungsweg: Schedule/run jobs and review selection criteria.
Result not eligible
Wahrscheinliche Ursache: Threshold failed or evidence is invalid.
L?sungsweg: Check threshold, ex works price and LTSD validity.
Unexpected eligible result
Wahrscheinliche Ursache: Agreement or source data does not match business expectation.
L?sungsweg: Trace rule, product, source category and values.
ECC zu S/4HANA Unterschiede
S/4HANA integration improves visibility into business-document values, but GTS preference logic still depends on correctly maintained agreement and evidence data.
Glossar
- 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.
- Aggregation
- Process that combines relevant product and evidence data for determination.
- Threshold value
- Agreement rule value compared with product or document values.
- Preference statement
- Result indicating whether preferential treatment can be claimed.
Wissenstest
Schließen Sie den Test mit mindestens 70 % ab, um das Zertifikat freizuschalten.
Generator starten