3803929 - Miro freight line shows no GR reference with multiple GR splits, preventing automated mapping — SAP S/4HANA Cloud Public Edition

• In MIRO (Create Supplier Invoice), material lines for a PO item with multiple Goods Receipts (GR) and identical quantity splits can be identified by Material Document/GR reference and item information.
• NB-Freight lines are displayed separately without a visible GR-level reference.
• Automation cannot reliably map freight quantities/values from an external file to the correct freight line when multiple GRs exist for the same PO item.
• No error messages are displayed.

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

1. Create a Purchase Order with a single item and post multiple Goods Receipts for that item with the same quantity splits.
2. Open MIRO (Create Supplier Invoice) for the PO.
3. Observe that material lines show Material Document/GR reference and item information, allowing identification by GR split.
4. Observe that NB-Freight lines are listed separately and do not show a visible GR-level reference, making it impossible to assign a freight line to a specific GR split.

• Delivery costs (freight and other planned costs) are maintained and accumulated at the purchase-order-item and cost-type level, not per individual GR.
• During invoice creation, the system provides one freight line per cost type for the entire PO item without linkage to a specific GR or material document.
• This is standard system behavior; the goods-receipt-based checking option applies to goods lines only and does not create per-delivery freight lines.

1. Post a single freight amount per cost type for each PO item; do not attempt to split freight by GR.
2. Before submitting each invoice, read the current outstanding freight amount for the PO item (for example, from PO history) so the amount reflects what is not yet invoiced.
3. For fixed (flat-fee) freight, avoid distributing the amount across deliveries to prevent the system from proposing the full remaining amount unintentionally.
4. If a bill of lading number is recorded on each GR and manual processing is acceptable, a user can manually select freight against a specific delivery by bill of lading during invoice entry; this is not suited for automation.
5. Verify the exact invoice interface fields for freight/cost-type items in the current release before implementing automation.

• refer to: Note 3679601 - Planned cost line item missing in supplier invoices created using inbound delivery

MIRO, Create Supplier Invoice, planned delivery costs, freight, NB-freight, GR reference, goods receipt based, GR split, multiple GRs, invoice verification, PO item, automation mapping, bill of lading, delivery costs grouping , KBA , MM-FIO-IV-2CL , Fiori UI for Invoice Verification (Public Cloud) , Problem