Symptom
No eDocument is created for a billing document, and the document is marked as "Not Relevant" in the eDocument Cockpit.
Environment
SAP S/4HANA Cloud Public Edition
Reproducing the Issue
- Open the eDocument Cockpit application
- Click the Change button
- Locate the affected billing document
- Select the indicators: "With Errors," "Not yet created," and "Not Relevant"
- Click Execution, then you will see the billing document is flagged as irrelevant
Cause
The configuration has been set up incorrectly.
Case 1: The eDocument type has been configured in the incorrect configuration activity Assign eDocument Type to Billing Document Type (SSCUI 102189), instead of the correct configuration: Assign eDocument Type to Accounting Document Type (SSCUI 102188)
Case 2: The Tax code used in the billing document is not configured in the configuration activity Determine Values for Tax Code for South Korea (SSCUI 101881).
Resolution
Configuration Guidelines:
- Assign eDocument Type to Billing Document Type: Use this only for billing types with no journal entry assignment (for example, pro forma invoices)
- Assign eDocument Type to Accounting Document Type: Use this for billing types with journal entry assignments
- Determine Values for Tax Code for South Korea: Configure all tax codes used in billing document
When a billing document is processed:
- The system checks if the billing document type is linked to an accounting document type
- The system also checks whether the tax code used is maintained in Determine Values for Tax Code for South Korea.
If either condition is not configured there, no eDocument will be created, and the document will be marked as "Not Relevant"
See Also
Refer to:
Keywords
eDocument, South Korea, Billing Document, Created, Irrelevant, Not Relevant, Assign eDocument Type to Billing Document Type, SSCUI 102189, Assign eDocument Type to Accounting Document Type, SSCUI 102188, Determine Values for Tax Code for South Korea, SSCUI 101881 , KBA , CA-GTF-CSC-EDO-KR , Document Compliance South Korea , Problem
SAP Knowledge Base Article - Public