Articles and guides on purchase order data extraction, PO-to-Excel conversion, AP three-way matching, ERP import, and procurement automation.
The full AS2 MDN disposition modifier table from RFC 4130, why an HTTP 200 tells you nothing, what really causes a MIC mismatch, and why a processed MDN is not order acceptance.
Read articleThe complete X12 997 error code tables, why an accepted 997 does not mean your order was processed, and how to read AK3, AK4, AK5 and AK9 in the right order.
Read articleThe three tables that store an SAP IDoc, the full inbound and outbound status code list, and the programs that move an IDoc out of status 51, 64 and 30.
Read articleA field level reference for the IIF file format QuickBooks Desktop uses to import purchase orders, including the row structure, the required columns, and the five failures that silently corrupt an import.
Read articleThe four causes behind almost every Integration Manager failure in Dynamics GP, each mapped to its verified Microsoft fix, plus a preflight checklist for purchase order loads.
Read articleME9F processes purchase order output, NACE configures output type NEU under application EF, and the NAST table records what was created, how it should be sent, and whether it worked. A field-level reference plus the usual reasons a PO never reaches the vendor.
Read articleBAPI_PO_CREATE1 creates a purchase order with the same logic as ME21N, but the interface catches people out: POHEADER is an importing parameter, every field needs an X flag, and custom fields only travel through EXTENSIONIN. Here is the whole interface, a working example, and why ME887 happens.
Read articleSAP purchase order pricing sits in four layers: document conditions in KONV or PRCD_ELEMENTS, master records in KONH and KONP, the Annn condition tables, and the RM0000 calculation schema. Here is which table answers which question, and why a contract price beats an info record price.
Read articleSAP has no single PO status table. The header state is EKKO-PROCSTAT, item closure is EKPO-ELIKZ and EREKZ, open quantity comes from EKET, and history from EKBE. The full field map with values and joins.
Read articleT16FS holds the release strategies, T16FC the release codes, and EKKO carries FRGGR, FRGSX, FRGKE and FRGZU on the order itself. The full table map, the CEKKO rule, and the joins.
Read article