Symptom
- Error occurs when creating billing document in the Manage Preliminary Billing Documents app with down payment items to be cleared.
- The error message displayed in the app reads "HTTP request failed during the process".
- Further investigation revealed that the root cause of the error was "invoice summary relevancy not possible for posting XXXX".
Environment
SAP S/4HANA Cloud Public Edition
Reproducing the Issue
- Open the Manage Preliminary Billing Documents app.
- Select the preliminary billing document and click "Create Billing Documents".
- Observe the error message: "HTTP request failed".
- After accessing the backend and reviewing the error log, found that the root cause error message is "invoice summary relevancy not possible for posting XXXXX".
Cause
As far as the number of kinds of tax codes in an accounting document (more strictly and technically saying the number of BSET records, which means the number of active condition records in tax code) is up to three because only 3 kinds of fields in the table BSEG are delivered for tax distribution. This is a known limitation in Japan Invoice Summary.
The root cause of this error is that when creating the billing document, the tax line items generated in the journal entry exceeded three.
Resolution
Solution 1:
You can choose to set this posting to be unrelated to the invoice summary.
- SSCUI: Define Line Items for Invoice Summary
This configuration includes document type, posting key and special G/L indicator. If the generated journal entry meets the requirements, it will be included in the check of the invoice summary. - App: Maintain business partner
In this app, you can manage IS-ROLE for each customer. If the IS-role is "Not (Invoice Summary) Relevant", even if the journal entry complies with the configuration specified in the SSCUI 'Define Line Items for Invoice Summary', the subsequent inspection logic will be skipped.
Solution 2:
If this posting needs to be set as related to Invoice Summary, below situation could avoid above error:
One FAZ with full net value (for example, 1 FAZ with net value 600,000).
One FAZ with partial net value, and then create a billing for left value (for example, 1 FAZ with net value 200,000, create a billing for left 400,000).
Two FAZ with partial net value, while their sum equals to full net value (for example, 1 FAZ with net value 200,000, another FAZ with net value 400,000).
Keywords
billing document error, invoice summary relevancy, posting error, HTTP request failed, preliminary billing document, net value mismatch, IS-role configuration, SSCUI define line items for invoice summary, SAP S/4HANA Cloud Public Edition , KBA , FI-LOC-FI-JP-IVS , Invoice Summary , Problem
SAP Knowledge Base Article - Public