Articles and guides on purchase order data extraction, PO-to-Excel conversion, AP three-way matching, ERP import, and procurement automation.
EKKO 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 articleA non-PO invoice arrives with no purchase order to match against, so AP has to code it and hunt down an approver. The difference from a PO invoice, real examples, the journal entry, and the SAP FB60 route.
Read articleA purchase order creates no journal entry. Here are the entries that do post, at goods receipt, invoice, and payment, plus what SAP, Oracle, D365, NetSuite and QuickBooks each call the accounts.
Read articleThe four purchase order types every procurement team uses: standard, planned, blanket, and contract. What each one commits you to, when to use it, and how SAP and Oracle name them.
Read articleEKBE is the purchase order history table in SAP. Here is what it stores, how to read the PO History tab in ME23N, why that tab sometimes disappears, and how change history in CDHDR and CDPOS is a different thing entirely.
Read articleThe purchase order IDoc is message type ORDERS with basic type ORDERS05. Here are the segments, transaction codes, and status errors that matter in practice.
Read article