SAP Scheduling Agreement Reconciliation Integration
TransactIG ingests SAP scheduling agreements (document types LP and LPA), inbound IDoc 830 (ORDERS05), inbound 862 (DELFOR01 / DELINS01), ASN dispatches (DELVRY03 / DESADV01), GRN postings, and outbound invoices (INVOIC02). It runs four-way cumulative-quantity reconciliation against OEM-side GRN acknowledgements. No custom ABAP, no Z-tables, no schema changes inside SAP.
Where the gap actually sits
SAP S/4HANA and ECC handle the transactional backbone of an auto-component supplier — scheduling agreement creation, EDI IDoc 830 / 862 / 856 processing, delivery creation through VL10A, GRN posting through MIGO, invoice creation through VF01 with INVOIC02 outbound to the OEM. What SAP does not do in the standard product is reconcile financial settlement back against the delivery schedule: CUM drift between supplier-shipped and OEM-received does not surface as a standing exception, RMPV is not recomputed against commodity indices, debit memos on payment advices are not decomposed by reason code, and Section 143 job-work return windows are not tracked.
Most Tier-1s fill this gap with eight to twelve custom ABAP Z-reports. TransactIG replaces the estate with a configuration layer that reads from documented SAP interfaces and runs the reconciliation outside the SAP release cycle.
SAP inputs we ingest
| Source | SAP-side method | Reconciliation purpose |
|---|---|---|
| Scheduling Agreement Header / Items | ME38 SA Header view extract, EKKO / EKPO tables, or BAPI_SAG_GETLIST | Customer master plant code, ship-to, agreement type (LP / LPA), validity period, payment terms, RMPV clause flag. |
| Inbound 830 (planning forecast) | ORDERS05 IDoc, idoc_input_orders processing | Forecast horizon per part per ship-to. Excluded from invoiceable quantity; tracked separately for capacity planning. |
| Inbound 862 (firm call-off) | DELFOR01 or DELINS01 IDoc, idoc_input_delfor processing | Firm CUM-required per part per ship-to per delivery window. The anchor for the four-way match. |
| ASN dispatch (856) | DELVRY03 / DESADV01 IDoc, VL02N delivery extract, or portal-mirrored 856 file | CUM-shipped per part per ship-to. Persistent state across uploads so missed or duplicate ASNs become standing exceptions. |
| OEM GRN acknowledgement | OEM portal extract (e-Nagare, TML SRM, SupplyOn) of CUM-received | Closes the supplier-side vs OEM-side cumulative gap. |
| Outbound invoice | INVOIC02 IDoc, VF03 billing-document extract, or e-invoice IRN payload | CUM-billed per part per ship-to. Closes the four-way match. |
Ingestion is interface-level — scheduled file drops (SFTP / S3), BAPI calls, or read-only views. No code change on the SAP side.
The reconciliation chain end-to-end
- Scheduling agreement → 830 forecast → 862 firm call-off. Forecast tracked separately for capacity; firm call-off becomes CUM-required per part per ship-to.
- 862 → ASN (856) dispatch. Supplier ships against firm; CUM-shipped persisted across uploads. Missed or duplicate ASN becomes a standing exception with a drift register.
- ASN → GRN posting (MIGO) → OEM GRN acknowledgement. Supplier-side GRN and OEM-side GRN reconciled; drift surfaces immediately rather than at quarter end.
- GRN → invoice (VF01, INVOIC02 outbound, e-invoice IRN). CUM-billed per part per ship-to closes the four-way match. Many-ASN-to-one-invoice and partial-shipment edge cases handled in the engine.
- Invoice → OEM payment advice. Payment decomposed into base invoice plus reason-coded debit memos (FOMP, JIT shortage, quality penalty, line-stop, tooling, transport). Each debit linked back to the originating invoice with Section 34 GST credit-note action queue.
Scope a SAP integration
Share the list of SAP plants, scheduling agreement types, and OEM customers in scope. We will return an interface map and a two-to-four-week implementation plan.
Request scoping