Symptom
- The External Billing Document Request (EBDR) is successfully created but does not reference the original SAP Sales Order, causing the EBDR and follow-up billing documents to be missing from the Sales Order document flow.
- The Sales Order remains in "Not Invoiced" status despite the creation of the EBDR and billing document.
- The document flow of the Sales Order does not display the EBDR or the associated billing document.
Environment
SAP S/4HANA Cloud Public Edition
Reproducing the Issue
- Create a Sales Order with document type "OR" and item categories "TAD" or "TAN".
- Use the EBDR spreadsheet import functionality to create an External Billing Document Request by referencing the Sales Order.
- Observe that the EBDR and follow-up billing document are created successfully.
- Check the document flow of the Sales Order and note that the EBDR and billing document are not displayed.
Cause
- The EBDR spreadsheet import process does not create a system-level reference to internal SAP Sales Orders.
- Even when fields like ‘Preceding Document Type’ and ‘Preceding Document Item Category’ are filled (e.g., with values like OR and TAN), the system treats the EBDR as a standalone external transaction, not linked to internal SD documents.
- As a result, no integration occurs with the Sales Order’s document flow (VBFA), and status fields (e.g., invoice status) in the Sales Order remain unchanged.
- This is standard behaviour, EBDRs are intended for billing data from external sources, such as third-party systems or manually uploaded spreadsheets, and not for internal billing references.
Resolution
- Clarify the intent:
- EBDRs are designed for external billing data and do not update the document flow or billing status of internal SAP Sales Orders.
- To invoice a Sales Order directly (while preserving document flow and billing status), use one of the following:
- The standard SD billing process via the Create Billing Documents app.
- Sales Billing APIs such as: SAP API for Billing Document Creation
- For solution-centric scenarios
- Combining internal and external sources, leverage Omnichannel Convergent Billing, ensuring only true external data is funneled via EBDRs:
- Omnichannel Convergent Billing – SAP Help Portal
See Also
Keywords
EBDR, external billing document request, sales order, document flow, SAP S/4HANA Cloud, billing document, spreadsheet import, not invoiced, OR document type, TAN item category, TAD item category, external transaction, billing integration, SAP API, Omnichannel Convergent Billing. , KBA , SD-BIL-BDR-2CL , Billing Document Request , Problem
Product
SAP S/4HANA Cloud Public Edition all versions
SAP Knowledge Base Article - Public