GTS · Global Trade Services
Transfer Preference Status to S/4HANA Billing SAP S/4HANA training
Training for using GTS preference status in S/4HANA billing and customer-facing documents.
Process overview ?? business context
Preference status must reach the commercial document flow when customers need correct preference statements on invoices or related outputs. This training links GTS determination, sales/billing integration, output relevance and exception handling.
Learners can explain how preference status is determined, transferred, checked in billing and used in invoice output or follow-up documentation.
End-to-end flow
- 1
Determine preference status
FioriFiori app: Preference Determination
ACDOCA impact: No accounting impact.
- 2
Create sales/billing document
VA01 / VF01Fiori app: Create Sales Orders; Create Billing Documents
ACDOCA impact: Billing posts finance in S/4HANA, not in GTS.
- 3
Transfer status
IntegrationFiori app: Preference status integration to billing
ACDOCA impact: Provides invoice-relevant status.
- 4
Render invoice output
FioriFiori app: Manage Billing Documents
ACDOCA impact: Preference statement appears where configured.
- 5
Handle exceptions
Fiori / logsFiori app: Application logs and document checks
ACDOCA impact: Missing status must be corrected before customer output.
Key tables
| Table | Explanation |
|---|---|
| GTS preference result | Eligibility status and statement reason. |
| Sales and billing references | S/4HANA sales order, delivery and billing objects receiving or displaying status. |
| Output determination | Invoice form, text and message data using preference statement. |
| Product and customer master data | Determines relevance and document content. |
| Integration log | Evidence of status transfer and failures. |
Step-by-step walkthrough
Start with current GTS result
Confirm product/customer/agreement status is valid.
????? ???: Old determination results can lead to wrong invoice statements.
Check billing relevance
Confirm sales area, output form and document type expect preference information.
????? ???: Not every invoice should print a preference statement.
Validate transfer
Check integration log and billing document fields/texts.
????? ???: A successful GTS calculation is not useful if the status never reaches billing.
Review customer output
Verify invoice PDF/text before sending.
????? ???: Incorrect preference statements create customs and customer trust risk.
Common errors ?? troubleshooting
Invoice missing preference text
??????? ????: Output configuration or status transfer did not provide statement data.
Fix path: Check GTS result, integration log and billing output form.
Wrong preference status on invoice
??????? ????: Determination is stale or document date/value changed.
Fix path: Rerun determination and rebuild billing/output where needed.
Billing blocked by missing trade data
??????? ????: Required preference or product data is incomplete.
Fix path: Complete product/customer/agreement data and repeat the check.
ECC ?? S/4HANA differences
S/4HANA billing and output management make the status visible in a modern document flow, but the underlying GTS result must be current and correctly integrated.
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.
- Billing document
- S/4HANA document used for invoice output and accounting transfer.
- Preference status
- Eligibility indicator/result from GTS preference determination.
- Output management
- S/4HANA mechanism that renders invoice or declaration text for customers.
Knowledge check
Certificate unlock करने के लिए कम से कम 70% score करें।
जेनरेटर शुरू करें