Why is this trained end-to-end?

Because the visible GTS app is usually only the point where master data, feeder document values, legal regulation and status processing meet.

What should users check first when the process fails?

Start with the log, object status, legal regulation, feeder reference and missing master data before changing configuration.

GTS · Global Trade Services

Calcul de préférence SAP S/4HANA training

Training for preference determination, aggregation, threshold comparison and eligibility interpretation.

Vue du processus et contexte m?tier

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.

Flux end-to-end

1
Collect evidence
Fiori
App Fiori: Supplier Declarations
Impact ACDOCA: No posting; provides proof.
2
Run aggregation
Fiori / job
App Fiori: Preference Determination - Aggregation
Impact ACDOCA: Prepares product-level data.
3
Run determination
Fiori
App Fiori: Preference Determination
Impact ACDOCA: Calculates eligibility.
4
Review result
Fiori
App Fiori: Preference Statements
Impact ACDOCA: Explains eligible or not eligible status.
5
Archive result
Fiori / background
App Fiori: Preference result archive
Impact ACDOCA: Supports audit and monitoring.

Tables cl?s

Table	Explication
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.

Parcours ?tape par ?tape

Confirm agreement scope

Check agreement, country, product and validity.

? surveiller: Wrong agreement context creates misleading results.

Validate evidence

Ensure LTSD and procurement data are valid and released.

? surveiller: Invalid evidence is as bad as missing evidence.

Run calculation

Execute aggregation and determination.

? surveiller: Run sequence matters when data changed.

Explain status

Use result reasons to explain why a product is eligible or not.

? surveiller: Do not override preference results without evidence.

Erreurs courantes et r?solution

No preference result

Cause probable: Aggregation or determination was not run after data changes.

Chemin de correction: Schedule/run jobs and review selection criteria.

Result not eligible

Cause probable: Threshold failed or evidence is invalid.

Chemin de correction: Check threshold, ex works price and LTSD validity.

Unexpected eligible result

Cause probable: Agreement or source data does not match business expectation.

Chemin de correction: Trace rule, product, source category and values.

Diff?rences ECC vers S/4HANA

S/4HANA integration improves visibility into business-document values, but GTS preference logic still depends on correctly maintained agreement and evidence data.

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.
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.

Test de connaissances

Obtenez au moins 70 % pour débloquer le certificat.

Lancer le générateur