ACMNTSCHX – Activity Maintenance Sched Dtl

System
AC Billing Revenue (BR)
Prefix
MSD
Primary key
CONTRACT, MAINT-SCHEDULE, OBJ-ID, TRAN-DATE
Fields
11
Updated by
23 programs
Referenced by
0 programs

ACMNTSCHX is the Activity Maintenance Sched Dtl table in Lawson AC Billing Revenue (prefix MSD). It is indexed by CONTRACT, MAINT-SCHEDULE, OBJ-ID, TRAN-DATE (MSDSET1); alternate indexes: MSDSET2 and MSDSET3. It is related 1:1 to ACCNTRACT, ACMNTHDR, ACMNTSCH, ACPRODDTL, ACTRANS and GLTRANS and 1:M to ACPRODUSER. It is updated by BR02.3, BR120, BR121, BR122, BR123, BR140, BR151, BR152 and 15 more. The table has 11 fields, 3 indexes and 7 documented relations.

About ACMNTSCHX

No description in the Lawson data dictionary.

Fields (11)

Column = COBOL field name without the MSD- 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
#MSD-CONTRACT PK
CONTRACT		Alpha 15Activity Management contract.BR51.1, BR52.1, BR52.3, BRIP.1
#MSD-MAINT-SCHEDULE PK
MAINT_SCHEDULE		Alpha 15—BR51.1, BR52.1, BR52.3, BRIP.1
#MSD-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.BR51.1, BR52.1, BR52.3, BRIP.1
#MSD-PRODUCT SET2 SET3
PRODUCT		Alpha 15—BR51.1, BR52.1, BR52.3, BRIP.1
#MSD-PROD-VERSION SET2 SET3
PROD_VERSION		Alpha 10—BR51.1, BR52.1, BR52.3, BRIP.1
#MSD-TRAN-DATE PK
TRAN_DATE		Numeric 8 (yyyymmdd)—BR51.1, BR52.1, BR52.3, BRIP.1
#MSD-GLT-OBJ-ID SET2
GLT_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.BR154, BR51.1, BR52.1, BRIP.1
#MSD-ATN-OBJ-ID SET2
ATN_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.BR154, BR51.1, BR52.1, BRIP.1
#MSD-REVENUE-AMT
REVENUE_AMT		Signed 18.2—BR51.1, BR52.1, BR52.3, BRIP.1
#MSD-STATUS
STATUS		Numeric 1This field displays the status of the transaction.
  • 1 To Process
  • 2 Processed
  • 3 Hold
BR154, BR51.1, BR52.1, BR52.3, BRIP.1
#MSD-SITE-LOCATION
SITE_LOCATION		Numeric 2—BR51.1, BR52.1, BR52.3, BRIP.1

Indexes (3)

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
MSDSET1
  1. CONTRACT
  2. MAINT-SCHEDULE
  3. OBJ-ID
  4. TRAN-DATE
PrimaryBR02.3, BR120, BR121, BR122, BR123, BR140, BR151, BR152 +15 more
MSDSET2
  1. GLT-OBJ-ID
  2. ATN-OBJ-ID
  3. CONTRACT
  4. MAINT-SCHEDULE
  5. PRODUCT
  6. PROD-VERSION
  7. OBJ-ID
  8. TRAN-DATE
KeyChange—
MSDSET3
  1. CONTRACT
  2. MAINT-SCHEDULE
  3. PRODUCT
  4. PROD-VERSION
  5. OBJ-ID
  6. TRAN-DATE
KeyChangeBR154, BR52.3

Relations

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

One to one (6) — lookups and parents

RelationTableRulesConditionField map
AccntractACCNTRACTRequired
MSD-CONTRACT→CNT-CONTRACT
AcmnthdrACMNTHDRRequired
MSD-CONTRACT→MSE-CONTRACT
MSD-MAINT-SCHEDULE→MSE-MAINT-SCHEDULE
AcmntschACMNTSCHRequired
MSD-CONTRACT→MSC-CONTRACT
MSD-MAINT-SCHEDULE→MSC-MAINT-SCHEDULE
MSD-PRODUCT→MSC-PRODUCT
MSD-PROD-VERSION→MSC-PROD-VERSION
MSD-OBJ-ID→MSC-OBJ-ID
AcproddtlACPRODDTLRequired
MSD-CONTRACT→AHD-CONTRACT
MSD-PRODUCT→AHD-PRODUCT
MSD-PROD-VERSION→AHD-PROD-VERSION
MSD-OBJ-ID→AHD-OBJ-ID
ActransACTRANSNot Required
MSD-ATN-OBJ-ID→ATN-OBJ-ID
GltransGLTRANSNot Required
MSD-GLT-OBJ-ID→GLT-OBJ-ID

One to many (1) — child tables

RelationTableRulesConditionField map
AcproduserACPRODUSER
MSE-PRODUCT-LIST→BRU-PRODUCT-LIST
MSD-PRODUCT→BRU-PRODUCT
MSD-PROD-VERSION→BRU-PROD-VERSION
MSC-EFFECTIVE-DT→BRU-EFFECTIVE-DT
—→BRU-RECORD-TYPE
—→BRU-MAX-USERS

Programs

Updated by (23)