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

Preference Calculation SAP S/4HANA training

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

Process overview and business context

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 flow

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

Key tables

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

Step-by-step walkthrough

Confirm agreement scope

Check agreement, country, product and validity.

Watch out for: Wrong agreement context creates misleading results.

Validate evidence

Ensure LTSD and procurement data are valid and released.

Watch out for: Invalid evidence is as bad as missing evidence.

Run calculation

Execute aggregation and determination.

Watch out for: Run sequence matters when data changed.

Explain status

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

Watch out for: Do not override preference results without evidence.

Common errors and troubleshooting

No preference result

Likely cause: Aggregation or determination was not run after data changes.

Fix path: Schedule/run jobs and review selection criteria.

Result not eligible

Likely cause: Threshold failed or evidence is invalid.

Fix path: Check threshold, ex works price and LTSD validity.

Unexpected eligible result

Likely cause: Agreement or source data does not match business expectation.

Fix path: Trace rule, product, source category and values.

ECC to S/4HANA differences

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

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

Knowledge check

Complete the quiz with at least 70% to unlock the certificate.

Start the generator