SAP Knowledge Base Article - Public

3754961 - eDocument Taiwan: XML Missing Down Payment Information in Advanced Down Payment Process

Symptom

While testing the Advanced Down Payment Process (scope item 7s7) provided by Process Navigator - SAP for Me, the e-invoice xml generated after submitting the invoice (billing type F2) does not include any down payment information.

Environment

SAP S/4HANA Cloud Public Edition

Reproducing the Issue

  1. Create a sales order using the Advanced Down Payment process.
  2. Create a Down Payment Request with billing type DPR1.
  3. Post the incoming payment and clear the down payment request.
  4. Create an outbound delivery and post goods issue.
  5. Create the Billing Invoice (F2) with reference to the outbound delivery.
  6. Submit the invoice through the eDocument Cockpit.
  7. Download and review the generated e-invoice xml.

Cause

Advanced Down Payment Flow is a new prepayment processing approach introduced by SAP (scope item 7S7, billing type DPR1) that stores prepayment data in a new internal data structure. However, no Taiwan localization enhancements have been developed for this new flow to date, and the Taiwan e-invoice XML mapping logic has not been updated to accommodate this new data structure.

This is recognized as a new product enhancement requirement and is being tracked internally, but no definitive delivery timeline is currently available.

Resolution

SAP evaluated the feasibility of implementing custom XML corrections through system extensions (BAdI) on the existing ADP flow but does not recommend this approach for production environments due to limitations inherent in cloud extension mechanisms.

The traditional FAZ billing type remains the reliable option for Taiwan scenarios. The SAP standard solution handles e-invoice processing correctly for the conventional prepayment flow (FAZ billing type). Until the standard enhancement is released, please revert to the traditional FAZ prepayment billing flow for Taiwan scenarios by switching the billing type from DPR1 back to FAZ in the relevant sales orders/contracts.

This ensures:

  • Prepayment information is correctly read
  • Settlement invoice XML is generated on a net basis

 Once corrected standard product version is released in future. At that point, you can decide whether to migrate back to the ADP flow based on your business requirements.

See Also

refer to: Process Navigator - SAP for Me

Keywords

eDocument, Taiwan, XML, Missing, Down Payment, Advanced Down Payment, ADP, 7S7, DPR1 , KBA , CA-GTF-CSC-EDO-TW , Document Compliance Taiwan , Product Enhancement

Product

SAP S/4HANA Cloud Public Edition all versions