3809049 - No BAdI available to copy PO header custom field to supplier invoice header (SAP S/4HANA Cloud Public Edition)

• A BAdI is required to copy a value from a custom field on the purchase order header to a custom field on the supplier invoice header.
• The Custom Logic app does not show any eligible BAdIs within the Procurement – Supplier Invoice header business context.
• A screenshot is referenced for the specific field.
• No error message or error code is shown.

• SAP S/4HANA Cloud Public Edition
• Fiori UI for Invoice Verification (Public Cloud)

1. Open the Custom Logic app.
2. Open Business Context.
3. Search for “Procurement – Supplier Invoice”.
4. Observe that no eligible supplier invoice header BAdIs are available for copying a PO header custom field to the invoice header.

• The only supplier invoice header BAdI that can set header data runs exclusively for invoices created via the automated inbound integration; it does not run during manual invoice entry, which is why it does not appear in the Custom Logic app for this use case.
• Making a custom field available in multiple business contexts does not enable automatic value flow; PO-to-supplier-invoice automatic copying is not a delivered process chain.
• The field type “Code List Based on CDS View” is not supported on the supplier invoice, preventing the field from being used there as designed.
• The PO reference on a supplier invoice exists at line-item level, so there is no single PO header value to populate on the invoice header.

1. Confirm how supplier invoices are created (manually in the app vs. through the automated inbound integration/service).
2. If invoices are created manually: automatic copying from PO header to invoice header is not available. Either capture the value at line-item level, change the custom field to a supported type on the supplier invoice, or enter the value manually.
3. If invoices are created via the inbound integration: use the supplier invoice header BAdI that defaults header data during inbound processing; verify it can access the desired PO value and consider the field-type limitation.
4. If invoices are posted through an external interface: include the required value in the inbound message payload so it can be set on the invoice.
5. If the custom field currently uses “Code List Based on CDS View”, change it to a field type supported by the supplier invoice before expecting it to appear or be set there.
6. If a delivered automatic PO-to-invoice field copy is required, submit a feature request. Refer to: 2963059 - How to Submit Feature Requests for SAP S/4HANA Cloud Product.

• Refer to: Business Add-Ins (BAdIs) for Invoice Processing
• Refer to: App Extensibility: Manage Supplier Invoices
• Refer to: Process Extensibility for Documents in Procurement
• Refer to: Supplier Invoice - OData V2
• Refer to: Custom Fields and Custom Logic apps
• Refer to: 2963059 - How to Submit Feature Requests for SAP S/4HANA Cloud Product

BAdI, Custom Logic app, supplier invoice header, purchase order header, custom field, value copy, procurement supplier invoice, header BAdI, inbound integration, manual invoice, code list based on CDS view, field not supported, line item reference, extensibility, S/4HANA Cloud Public Edition , KBA , MM-FIO-IV-2CL , Fiori UI for Invoice Verification (Public Cloud) , Problem