POMXVAL – Attribute

System
Purchase Order (PO)
Prefix
PMV
Primary key
BUY-OBJ-ID, MATRIX-CAT
Fields
3
Updated by
2 programs
Referenced by
226 programs

POMXVAL is the Attribute table in Lawson Purchase Order (prefix PMV). It is indexed by BUY-OBJ-ID, MATRIX-CAT (PMVSET1); alternate indexes: PMVSET2. It is related 1:1 to BUYER, MXCATDEF and MXOBJCAT. It is updated by MX500 and POBL.3 and referenced by AP125, AP126, AP131, AP20.1, AP20.2, AP20.3, AP20.4, AP20.5 and 218 more. The table has 3 fields, 2 indexes and 3 documented relations.

About POMXVAL

No description in the Lawson data dictionary.

Fields (3)

Column = COBOL field name without the PMV- prefix, hyphens → underscores. Derived fields are computed by the application and are not stored. PK = primary key (present in every index); SETn = leading/alternate key of that index.

Field / columnTypeDescription & valuesUpdated by
#PMV-BUY-OBJ-ID PK
BUY_OBJ_ID
Numeric 12This is the object identifier. It is used to relate commitments or posted transactions back to the originating subsystems. Each subsystem record that is updated as a commitment or posted transaction is assigned an object identifier. The object identifier is maintained in the subsystem files and in the Activity Commitments Detail and Activity Transaction files. The object identifier is a unique key used to drill back from Activity Management to the subsystems.MX500, PO04.6, POBL.3
#PMV-MATRIX-CAT PK
MATRIX_CAT
Alpha 12Attribute name assigned to an object (like accounting unit) to track additional information. Attribute values may then be used in selection and sorting for report and analysis.MX500, PO04.6, POBL.3
#PMV-MX-VALUE SET2
MX_VALUE
Alpha 32The attribute value.MX500, PO04.6, POBL.3

Indexes (2)

Keys are listed in index order; ↓ marks a descending key. Every documented Lawson index is unique unless flagged Duplicates; Subset indexes carry a Where condition.

IndexKeysFlagsConditionUsed in
PMVSET1
  1. BUY-OBJ-ID
  2. MATRIX-CAT
PrimaryAP125, AP126, AP131, AP20.1, AP20.2, AP20.3, AP20.4, AP20.5 +22 more (list truncated in source)
PMVSET2
  1. MATRIX-CAT
  2. MX-VALUE
  3. BUY-OBJ-ID
KeyChangeMX500, POBL.1

Relations

Relationship map — 1:1 lookups/parents on the left, 1:M children on the right (up to 14 each)
BUYERMXCATDEFMXOBJCATPOMXVAL

One to one (3) — lookups and parents

RelationTableRulesConditionField map
BuyerBUYERRequired
PMV-BUY-OBJ-ID→BUY-BUY-OBJ-ID
MxcatdefMXCATDEFRequired
PMV-MATRIX-CAT→MXC-MATRIX-CAT
MxobjcatMXOBJCATRequired
"BUYER"→MOC-OBJ-TYPE
PMV-MATRIX-CAT→MOC-MATRIX-CAT

Programs

Updated by (2)

Referenced by (226)