MITPOP
Prefix: MPmasterItem aliases — one row per alias type, qualifier, and alias number, mapping external identities (customer or supplier item numbers, barcodes) to the internal ITNO; the lookup behind alias-based item search
What the badges mean
- Prefix: MM
- Prefix: the table’s 2-character physical-column prefix (e.g.
MMonMITMAS) — every field alias on the table carries it. Join by matching aliases across tables, not full column names (see the quirks guide). - master
- Data class: what the table holds — master data, balances, transaction documents, code/reference tables, or history.
- Shared across companies
- The table carries no
CONO— rows aren’t partitioned per company (see the quirks guide). - Division-level
- The table carries
DIVI— rows are scoped below company to a division, one layer more granular thanCONOalone (see the quirks guide).
Parent & satellites
MITPOP is a satellite of MITMAS — many rows here per MITMAS row; join on ITNO plus the CONO (exact ON clause under Join details below).
Fields
5 fields · 4 key
5 fields.
| Key | Field | Alias | Description | Type | Length | Flags |
|---|---|---|---|---|---|---|
| Key | MPCONO | CONO | Company | numeric | ||
| Key | MPALWT | ALWT | Alias category — what kind of external identity the alias is | numeric | ||
| Key | MPALWQ | ALWQ | Alias qualifier — narrows the category, e.g. to a specific partner | alphanumeric | ||
| Key | MPPOPN | POPN | The alias number itself — the external item identity being mapped | alphanumeric | ||
| MPITNO | ITNO | Internal item number the alias resolves to | alphanumeric |
Field provenance: hand-curated.
Boilerplate SQL
Starting point for reading MITPOP on 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.
3 parameters not filled: <catalog>, <schema>, <company>
-- ============================================================
-- Table : MITPOP — Item aliases — one row per alias type, qualifier, and alias number, mapping external identities (customer or supplier item numbers, barcodes) to the internal ITNO; the lookup behind alias-based item search
-- Purpose: Column-selected read of MITPOP — auto-generated from field metadata
-- Grain : One row per company (CONO) + MPALWT + MPALWQ + MPPOPN
-- Notes : Auto-generated skeleton for a prefixed physical M3 schema or a landing schema normalized to the prefixed names in this catalog. Raw Data Lake property names vary with the published object: map them through Data Catalog before running this SQL. Dates are numeric YYYYMMDD (0 = none, mapped to NULL); all curated status values are decoded inline. Audit columns (RGDT/RGTM/LMDT/CHNO/CHID) omitted — see the quirks guide.
-- ============================================================
SELECT
m.MPCONO AS "Company",
m.MPALWT AS "Alias category — what kind of external identity the alias is",
m.MPALWQ AS "Alias qualifier — narrows the category, e.g. to a specific partner",
m.MPPOPN AS "The alias number itself — the external item identity being mapped",
m.MPITNO AS "Internal item number the alias resolves to"
FROM <catalog>.<schema>.MITPOP m
WHERE
m.MPCONO = <company>
ORDER BY m.MPALWT;Verified September 2026
Relationships
Diagram of 1-hop neighbors — join details below. CSYTAB decode edges are highlighted; they’re the joins newcomers most often get wrong.
Join details
-- Uses this catalog's prefixed M3 column names; map raw Data Lake properties through Data Catalog first. ON MITPOP.MPITNO = MITMAS.MMITNO AND MITPOP.MPCONO = MITMAS.MMCONO
Programs That Use This Table
More Items & Product Data tables
- MITAUNAlternate units of measure — one row per item, unit type, and alternate unit, carrying the conversion factor between the alternate unit and the item's basic unit; the table that answers 'how many eaches in a case'
- MITFACThe item/facility record — one row per item and facility, where costing lives; the approved cost the facility values the item at sits here, between the company-wide item master and the warehouse-level balances
- MITMASThe item master — one row per item per company, carrying the item's identity, status, grouping codes, basic unit of measure, and physical attributes; every balance, order line, and stock movement joins back to it on ITNO