The SAP B1 adaptor is a database 'read' and uses files to write the order
For the reads the system supports both the Oracle and SQL databases.
For the writes the system produces a file (normally xml) that is then imported using the SAP B1iF (Integration Framework). The B1iF task is done by the SAP consultant so please check with them to ensure they are aware of this
An example of B1iF is here https://www.youtube.com/watch?v=laS5gueVtOY
The EDI process involves receiving EDI orders and converting them to a SAP order to be consumed by the SAP B1if (This file can be customised as fits). The system will then analyse SAP periodically and can send back any order changes, ASN's, and Invoices depending on the retailers requirements. The SAP information is sourced using read only queries.
If a 3PL is involved then the system will send a Shipment Order based on a defined field values in SAP (these can be customised). When a Shipment Advice is returned for the 3PL then the system can produce a shipment file to be consumed by SAP B1if (customizable) and the ASN can be sent immediately to the retailer.
The standard order file to be consumed by SAP B1if looks similar to the following (1 file per order)
Also read only database access normally includes these tables
- OCRD - for customers
- OITM - for items
- OBCD - for items
- OVTG - for tax info
- ORDR - for orders
- RDR1 - for orders
- OINV - for invoices
- INV1 - for invoices