CBMXVALUE is the Cash Code Attribute Value table in Lawson Cash Ledger (prefix CMV). It is indexed by OBJ-ID, MATRIX-CAT (CMVSET1); alternate indexes: CMVSET2. It is related 1:1 to CBCPYCASH, MXOBJCAT and MXCATDEF and 1:M to CBMXVALUE. It is updated by CB01.4, CB01.5, CB162 and MX500 and referenced by AP150, AP155, AP160, AP161, AP265, CB00.3, CB145, CB170 and 15 more. The table has 3 fields, 2 indexes and 4 documented relations.
About CBMXVALUE
No description in the Lawson data dictionary.
Fields (3)
Column = COBOL field name without the CMV- 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.
This 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.
Attribute 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.
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.
Index
Keys
Flags
Condition
Used in
CMVSET1
OBJ-ID
MATRIX-CAT
Primary
AP150, AP155, AP160, AP161, AP265, ZA161, CB00.3, CB01.4 +20 more
CMVSET2
MATRIX-CAT
MX-VALUE
OBJ-ID
KeyChange
AP150, AP155, AP160, AP161, AP265, ZA161, CB01.7, CB145 +14 more
Relations
Relationship map — 1:1 lookups/parents on the left, 1:M children on the right (up to 14 each)
