MXTMPLEFDT – Attr Template Effective Date

System
General Ledger Setup (IF)
Prefix
MTE
Primary key
OBJ-TYPE, TEMPLATE-NAME, MATRIX-CAT, EFFECTIVE-DATE
Fields
5
Updated by
2 programs
Referenced by
45 programs

MXTMPLEFDT is the Attr Template Effective Date table in Lawson General Ledger Setup (prefix MTE). It is indexed by OBJ-TYPE, TEMPLATE-NAME, MATRIX-CAT, EFFECTIVE-DATE (MTESET1); alternate indexes: MTESET3. It is related 1:1 to MXCATDEF and MXTMPLHEDT and 1:M to MXTPEFDTAU. It is updated by MX06.1 and MX06.2 and referenced by AC13.1, AC13.7, AC14.1, AC14.6, AC16.1, AC16.2, AC16.7, GL14.1 and 37 more. The table has 5 fields, 2 indexes and 3 documented relations.

About MXTMPLEFDT

This file stores the detail records for the attribute value effective date attribute templates. The file is updated by Attribute Value Effective Date Template (MX06.1).

Fields (5)

Column = COBOL field name without the MTE- 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
#MTE-OBJ-TYPE PK
OBJ_TYPE		Alpha 5Ths file determine the attribute object type. For this fype of template, the object type is always ACCTU.MX06.1
#MTE-TEMPLATE-NAME PK
TEMPLATE_NAME		Alpha 12This is the name of the template.MX06.1
#MTE-MATRIX-CAT PK
MATRIX_CAT		Alpha 12This is an accounting unit attribute to which to template assigns a value.MX06.1
#MTE-MX-VALUE
MX_VALUE		Alpha 32This is the value assigned to the accounting unit attribute by the template.MX06.1
#MTE-EFFECTIVE-DATE PK
EFFECTIVE_DATE		Numeric 8 (yyyymmdd)This is the effective date for the value.MX06.1

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
MTESET1
  1. OBJ-TYPE
  2. TEMPLATE-NAME
  3. MATRIX-CAT
  4. EFFECTIVE-DATE
PrimaryAC13.1, AC13.7, AC14.1, AC14.6, AC16.1, AC16.2, AC16.7, GL146 +22 more (list truncated in source)
MTESET3
  1. OBJ-TYPE
  2. MATRIX-CAT
  3. EFFECTIVE-DATE
  4. TEMPLATE-NAME
—

Relations

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

One to one (2) — lookups and parents

RelationTableRulesConditionField map
Matrix CatMXCATDEFRequired
MTE-MATRIX-CAT→MXC-MATRIX-CAT (MXCSET1)
MxtmplhedtMXTMPLHEDTRequired
MTE-OBJ-TYPE→MTI-OBJ-TYPE
MTE-TEMPLATE-NAME→MTI-TEMPLATE-NAME

One to many (1) — child tables

RelationTableRulesConditionField map
MxtpefdtauMXTPEFDTAU
MTE-OBJ-TYPE→TEU-OBJ-TYPE
MTE-TEMPLATE-NAME→TEU-TEMPLATE-NAME
MTE-MATRIX-CAT→TEU-MATRIX-CAT
MTE-EFFECTIVE-DATE→TEU-EFFECTIVE-DATE
—→TEU-ACTION
—→TEU-DATE
—→TEU-TIME
—→TEU-UNIQUE-I-D

Programs

Updated by (2)

Referenced by (45)