ACCATMXVDT – No description in the Lawson data dictionary

System
Activity Management (AC)
Prefix
MXB
Primary key
OBJ-ID, MATRIX-CAT, EFFECTIVE-DATE
Fields
5
Updated by
8 programs
Referenced by
2 programs

ACCATMXVDT is a Lawson Activity Management table (prefix MXB); no description in the lawson data dictionary. It is indexed by OBJ-ID, MATRIX-CAT, EFFECTIVE-DATE (MXBSET1); alternate indexes: MXBSET2, MXBSET3 and MXBSET4. It is related 1:1 to ACCATMXVAL, MXCATDEF and MXOBJCAT and 1:M to ACCATSUM and ACCATSUMX. It is updated by AC08.1, AC08.2, AC08.3, AC08.6, AC16.1, AC16.2, AC16.7 and AC16.8 and referenced by AC135 and MX202. The table has 5 fields, 4 indexes and 5 documented relations.

About ACCATMXVDT

No description in the Lawson data dictionary.

Fields (5)

Column = COBOL field name without the MXB- 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
#MXB-OBJ-ID PK
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.AC16.1, AC16.2, AC16.7, AC16.8
#MXB-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.AC16.1, AC16.2, AC16.7, AC16.8
#MXB-STRUCTURE SET3
STRUCTURE		Alpha 15The name of the category structure.AC16.1, AC16.2, AC16.7, AC16.8
#MXB-MX-VALUE
MX_VALUE		Alpha 32The attribute value.AC16.1, AC16.2, AC16.7, AC16.8
#MXB-EFFECTIVE-DATE PK
EFFECTIVE_DATE		Numeric 8 (yyyymmdd)The date a vendor's prices will be in effect.AC16.1, AC16.2, AC16.7, AC16.8

Indexes (4)

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
MXBSET1
  1. OBJ-ID
  2. MATRIX-CAT
  3. EFFECTIVE-DATE
PrimaryAC08.1, AC08.2, AC08.3, AC08.6, AC16.1, AC16.2, AC16.7, AC16.8 +1 more
MXBSET2
  1. MATRIX-CAT
  2. EFFECTIVE-DATE
  3. OBJ-ID
MX202
MXBSET3
  1. MATRIX-CAT
  2. STRUCTURE
  3. EFFECTIVE-DATE ↓
  4. OBJ-ID
KeyChangeAC16.8
MXBSET4
  1. OBJ-ID
  2. MATRIX-CAT
  3. EFFECTIVE-DATE ↓
AC135

Relations

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

One to one (3) — lookups and parents

RelationTableRulesConditionField map
AccatmxvalACCATMXVALNot Required
MXB-OBJ-ID→AJB-OBJ-ID
MXB-MATRIX-CAT→AJB-MATRIX-CAT
MxcatdefMXCATDEFRequired
MXB-MATRIX-CAT→MXC-MATRIX-CAT
MxobjcatMXOBJCATRequired
"ACCAT"→MOC-OBJ-TYPE
MXB-MATRIX-CAT→MOC-MATRIX-CAT

One to many (2) — child tables

RelationTableRulesConditionField map
AccatsumACCATSUM
MXB-OBJ-ID→SRS-OBJ-ID
—→SRS-STRUCTURE
—→SRS-SUM-ACCT-CAT
AccatsumxACCATSUMX
MXB-OBJ-ID→SRX-OBJ-ID
—→SRX-STRUCTURE
—→SRX-ACCT-CATEGORY

Programs

Updated by (8)

Referenced by (2)