Articles and guides on purchase order data extraction, PO-to-Excel conversion, AP three-way matching, ERP import, and procurement automation.
ME9F 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 articleEKKO stores the purchase order header, EKPO the line items. Field lists, how to join them on EBELN, why BSTYP matters, and the child tables that hold the rest of the order.
Read articleF4311 is the JD Edwards purchase order detail file and F4301 is the header. Here is how they join, what the status codes mean, where receipts live, and the Julian date and implied decimal traps that break reports.
Read articlePurchTable holds the purchase order header and PurchLine the lines, joined on PurchId. Nothing moves to history, so the PurchStatus and DocumentState enums do all the work. The join keys, the status codes, and how D365 differs from Business Central and GP.
Read articlePOP10100 holds the purchase order header and POP10110 the lines, until the order closes and moves to POP30100 and POP30110. The join keys, the status codes, and how GP compares to Business Central and D365.
Read articleThe four tables behind an Oracle purchase order, the keys that join them, the columns people actually query, and what changes between EBS R12 and Fusion Cloud.
Read articleChoose your plan