3806182 - SupplierInvoiceCollaborationNotification_Out WSDL definition issue: SupplierInvoiceItem cardinality mismatch - SAP S/4HANA

When using the outbound service SupplierInvoiceCollaborationNotification_Out, the generated WSDL defines node SupplierInvoiceItem with a minimum occurrence of 1 (1..n).

However, in certain scenarios, SAP S/4HANA generates and sends an outbound notification without a SupplierInvoiceItem element. This can occur, for example, when the supplier invoice contains G/L account items and has no purchase order reference.

As a result, a receiver application that validates the received SOAP payload strictly against the SAP-generated WSDL may reject the message because the payload does not fulfill the WSDL cardinality requirement.

The following behavior can be observed:

• The outbound service SupplierInvoiceCollaborationNotification_Out is triggered.
• The outbound message is generated in SAP.
• The payload does not contain SupplierInvoiceItem entries.
• The service definition/WSDL specifies SupplierInvoiceItem with minOccurs="1".
• The receiver system rejects or cannot process the payload due to the mandatory item-node definition.

• Materials Management (MM)
• SAP enhancement package for SAP ERP, version for SAP HANA
• SAP S/4HANA Cloud Private Edition - All Versions
• Enterprise Services in Invoice Verification

SupplierInvoiceCollaborationNotification_Out, WSDL, SupplierInvoiceItem, cardinality, minOccurs, 1..n, SOAP, outbound API, SPROXY, SRT_MONI, payload missing items, invoice without items, purchase order, integration, enterprise services , KBA , MM-IV-GF-ES , Enterprise Services in Invoice Verification , Problem