Skip to content
M3 Reference

MPLINE

Prefix: IBtransaction

The purchase order line — one row per ordered item with quantity, price, planned delivery date, and status; the core buy-side transaction, joined to its header by PUNO

Module: PurchasingCompany-partitioned (CONO)Header: MPHEAD

Header & line

MPLINE lines join back to their header MPHEAD — and the CONO — so a line never fans out across companies.

Fields

10 fields · 4 key

KeyFieldAliasDescriptionTypeLengthFlags
KeyIBCONOCONOCompanynumeric
KeyIBPUNOPUNOPurchase order numberalphanumeric
KeyIBPNLIPNLIPurchase order line numbernumeric
KeyIBPNLSPNLSLine subnumber — subdivides a line across deliveriesnumeric
IBITNOITNOItem orderedalphanumeric
IBPUSTPUSTLine status — the two-char ladder the line walks from entry through confirmation, receipt, and invoice matchingalphanumeric
IBORQAORQAOrdered quantity in the purchase unitnumeric
IBPUPRPUPRPurchase price per price unit on the linenumeric
IBDWDTDWDTPlanned delivery date for the linenumeric
IBWHLOWHLOReceiving warehouse for the linealphanumeric

Field provenance: hand-curated.

Boilerplate SQL

Starting point for reading MPLINEon Databricks — numeric YYYYMMDD dates are wrapped to NULL, verified status ladders are decoded, and the CONO anchor is in place. Set your Unity Catalog location, company, and filter values below; they’re substituted into the SQL and the copy button.

Query parameters
-- ============================================================
-- Table  : MPLINE — The purchase order line — one row per ordered item with quantity, price, planned delivery date, and status; the core buy-side transaction, joined to its header by PUNO
-- Purpose: Column-selected read of MPLINE — auto-generated from field metadata
-- Grain  : One row per company (CONO) + IBPUNO + IBPNLI + IBPNLS
-- Notes  : Auto-generated skeleton for Infor Data Lake-landed M3 data. Dates are numeric YYYYMMDD (0 = none, mapped to NULL); status ladders decoded inline where verified. Audit columns (RGDT/RGTM/LMDT/CHNO/CHID) omitted — see the quirks guide.
-- ============================================================
SELECT
  pl.IBCONO AS "Company",
  pl.IBPUNO AS "Purchase order number",
  pl.IBPNLI AS "Purchase order line number",
  pl.IBPNLS AS "Line subnumber — subdivides a line across deliveries",
  pl.IBITNO AS "Item ordered",
  pl.IBPUST AS "Line status — the two-char ladder the line walks from entry through confirmation, receipt, and invoice matching",  -- status: decode pl.IBPUST against your configuration — see quirks guide #statuses
  pl.IBORQA AS "Ordered quantity in the purchase unit",
  pl.IBPUPR AS "Purchase price per price unit on the line",
  CASE WHEN pl.IBDWDT = 0 THEN NULL ELSE TO_DATE(CAST(CAST(pl.IBDWDT AS BIGINT) AS STRING), 'yyyyMMdd') END AS "Planned delivery date for the line",  -- YYYYMMDD, 0 → NULL
  pl.IBWHLO AS "Receiving warehouse for the line"
FROM <catalog>.<schema>.MPLINE pl
WHERE
  pl.IBCONO = <company>
  -- AND pl.IBPUNO = '<PUNO>'
  -- AND pl.IBDWDT >= <DATE_FROM>  -- yyyyMMdd numeric
  -- AND pl.IBDWDT <= <DATE_TO>  -- yyyyMMdd numeric
ORDER BY pl.IBPUNO;

6 parameters not filled: <catalog>, <schema>, <company>, <PUNO>, <DATE_FROM>, <DATE_TO>

Relationships

1-hop neighbors — click a table to navigate there. CSYTAB decode edges are highlighted; they’re the joins newcomers most often get wrong.

Join details

  • MPHEADMPLINEheader line · 1:N
    ON MPHEAD.IAPUNO = MPLINE.IBPUNO AND MPHEAD.IACONO = MPLINE.IBCONO
  • MPLINEMITMASforeign key · N:1
    ON MPLINE.IBITNO = MITMAS.MMITNO AND MPLINE.IBCONO = MITMAS.MMCONO
  • MPLINEMITWHLforeign key · N:1
    ON MPLINE.IBWHLO = MITWHL.MWWHLO AND MPLINE.IBCONO = MITWHL.MWCONO

Programs That Use This Table

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Work with the practice →

Not affiliated with or endorsed by Infor. Infor, Infor M3, and Infor CloudSuite are trademarks of Infor and/or its affiliates.