ACMNTSCH – Activity Maintenance Schedule

System
AC Billing Revenue (BR)
Prefix
MSC
Primary key
CONTRACT, MAINT-SCHEDULE, OBJ-ID
Fields
43
Updated by
26 programs
Referenced by
3 programs

ACMNTSCH is the Activity Maintenance Schedule table in Lawson AC Billing Revenue (prefix MSC). It is indexed by CONTRACT, MAINT-SCHEDULE, OBJ-ID (MSCSET1); alternate indexes: MSCSET2 and MSCSET3. It is related 1:1 to ACCNTRACT, ACCNTRPCD, ACGLCODE, ACMNTHDR, ACPMHSTHDR, ACPRODDTL, ACPRODHDR, ACPRODLSTX and 1 more and 1:M to ACCNTRCMTX, ACMNTSCHX, ACPRODTAX and ACPRODUSER. It is updated by BR02.3, BR120, BR121, BR122, BR123, BR124, BR140, BR151 and 18 more and referenced by BR10.9, BR252 and BR31.4. The table has 43 fields, 3 indexes and 17 documented relations.

About ACMNTSCH

No description in the Lawson data dictionary.

Fields (43)

Column = COBOL field name without the MSC- 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
#MSC-CONTRACT PK
CONTRACT		Alpha 15Activity Management contract.BR155, BR51.1, BR52.1, BR52.4, BR52.5
#MSC-MAINT-SCHEDULE PK
MAINT_SCHEDULE		Alpha 15—BR155, BR51.1, BR52.1, BR52.4, BR52.5
#MSC-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.BR155, BR51.1, BR52.1, BR52.4, BR52.5
#MSC-PRODUCT SET2 SET3
PRODUCT		Alpha 15—BR155, BR51.1, BR52.1, BR52.4, BR52.5
#MSC-PROD-VERSION SET2 SET3
PROD_VERSION		Alpha 10—BR155, BR51.1, BR52.1, BR52.4, BR52.5
#MSC-BEGIN-DATE
BEGIN_DATE		Numeric 8 (yyyymmdd)The begin date for this effort period.BR155, BR51.1, BR52.1, BR52.4, BR52.5
#MSC-END-DATE
END_DATE		Numeric 8 (yyyymmdd)The end date for this effort period.BR155, BR51.1, BR52.1, BR52.4, BR52.5
#MSC-STATUS
STATUS		Numeric 1This field displays the status of the transaction.
  • 0 Unreleased
  • 1 Pro Forma
  • 2 Accepted
  • 3 Invoiced
  • 4 Free Maintenance
  • 5 Invoice Cancelled
  • 6 Maint Cancelled
BR02.3, BR120, BR121, BR122, BR123, BR140, BR151, BR152 +14 more
#MSC-EFFECTIVE-DT
EFFECTIVE_DT		Numeric 8 (yyyymmdd)The effective date is the date the record is first valid.BR155, BR51.1, BR52.1, BR52.4, BR52.5
#MSC-USERS
USERS		Numeric 12—BR155, BR51.1, BR52.1, BR52.4, BR52.5
#MSC-MAINT-PERCENT
MAINT_PERCENT		Signed 7.3The percentage determines how much retention is held. It can either be a percentage of each invoice, or it can be a percentage of a total.BR155, BR51.1, BR52.1, BR52.4, BR52.5
#MSC-LIST-NET-FLAG
LIST_NET_FLAG		Alpha 1—
  • 1 List
  • 2 Net
BR155, BR51.1, BR52.1, BR52.4, BR52.5
#MSC-PROD-LIST-AMT
PROD_LIST_AMT		Signed 18.2—BR155, BR51.1, BR52.1, BR52.4, BR52.5
#MSC-PROD-NET-AMT
PROD_NET_AMT		Signed 18.2—BR155, BR51.1, BR52.1, BR52.4, BR52.5
#MSC-PROD-MAINT-AMT
PROD_MAINT_AMT		Signed 18.2—BR155, BR51.1, BR52.1, BR52.4, BR52.5
#MSC-INVOICE
INVOICE		Alpha 22Used to identify the invoice.BR52.1, BR52.4, BR52.5
#MSC-PMH-OBJ-ID SET3
PMH_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.—
#MSC-BILL-ACCT-CAT
BILL_ACCT_CAT		Alpha 5Account categories are groupings of costs, revenues, or a combination of both used for reporting and inquiries for activities in the Activity Management system. All transactions are posted to an account category within an activity. You can assign a specific General Ledger account or range of accounts (company, accounting unit, account, and subaccount) that make up the transactions posted to an account category using AC07.1 (Account Assignment). Period-to-date, year-to-date, and life-to-date balances are maintained by account category for activities. Account categories must be assigned to activities before you do any budgeting or transaction processing. Valid account category types are: cost revenue accrual pass thruBR155, BR51.1, BR52.1, BR52.4, BR52.5
#MSC-BILL-GL-CD
BILL_GL_CD		Alpha 4—BR155, BR51.1, BR52.1, BR52.4, BR52.5
#MSC-BILL-ACCOUNT
BILL_ACCOUNT		Numeric 6This field along with the accounting unit and subaccount make up the location (account) where amounts and other account information is stored.BR155, BR51.1, BR52.1, BR52.4, BR52.5
#MSC-BILL-SUB-ACCT
BILL_SUB_ACCT		Numeric 4This field contains the subaccount from your general ledger chart of accounts that was charged with the amount carried on this record.BR155, BR51.1, BR52.1, BR52.4, BR52.5
#MSC-UNBL-ACCT-CAT
UNBL_ACCT_CAT		Alpha 5Account categories are groupings of costs, revenues, or a combination of both used for reporting and inquiries for activities in the Activity Management system. All transactions are posted to an account category within an activity. You can assign a specific General Ledger account or range of accounts (company, accounting unit, account, and subaccount) that make up the transactions posted to an account category using AC07.1 (Account Assignment). Period-to-date, year-to-date, and life-to-date balances are maintained by account category for activities. Account categories must be assigned to activities before you do any budgeting or transaction processing. Valid account category types are: cost revenue accrual pass thruBR155, BR51.1, BR52.1, BR52.4, BR52.5
#MSC-UNBL-GL-CD
UNBL_GL_CD		Alpha 4—BR155, BR51.1, BR52.1, BR52.4, BR52.5
#MSC-UNBL-ACCOUNT
UNBL_ACCOUNT		Numeric 6This field along with the accounting unit and subaccount make up the location (account) where amounts and other account information is stored.BR155, BR51.1, BR52.1, BR52.4, BR52.5
#MSC-UNBL-SUB-ACCT
UNBL_SUB_ACCT		Numeric 4This field contains the subaccount from your general ledger chart of accounts that was charged with the amount carried on this record.BR155, BR51.1, BR52.1, BR52.4, BR52.5
#MSC-REV-ACCT-CAT
REV_ACCT_CAT		Alpha 5Account categories are groupings of costs, revenues, or a combination of both used for reporting and inquiries for activities in the Activity Management system. All transactions are posted to an account category within an activity. You can assign a specific General Ledger account or range of accounts (company, accounting unit, account, and subaccount) that make up the transactions posted to an account category using AC07.1 (Account Assignment). Period-to-date, year-to-date, and life-to-date balances are maintained by account category for activities. Account categories must be assigned to activities before you do any budgeting or transaction processing. Valid account category types are: cost revenue accrual pass thruBR155, BR51.1, BR52.1, BR52.4, BR52.5
#MSC-REV-GL-CD
REV_GL_CD		Alpha 4—BR155, BR51.1, BR52.1, BR52.4, BR52.5
#MSC-REV-ACCOUNT
REV_ACCOUNT		Numeric 6This field along with the accounting unit and subaccount make up the location (account) where amounts and other account information is stored.BR155, BR51.1, BR52.1, BR52.4, BR52.5
#MSC-REV-SUB-ACCT
REV_SUB_ACCT		Numeric 4This field contains the subaccount from your general ledger chart of accounts that was charged with the amount carried on this record.BR155, BR51.1, BR52.1, BR52.4, BR52.5
#MSC-OPERATOR
OPERATOR		Alpha 10This field is used to store the login id of the person who entered the record.BR155, BR51.1, BR52.1, BR52.4, BR52.5
#MSC-DATE-STAMP
DATE_STAMP		Numeric 8 (yyyymmdd)This field contains the server date (month, date, and year) of the last change to this record.BR155, BR51.1, BR52.1, BR52.4, BR52.5
#MSC-TIME-STAMP
TIME_STAMP		Numeric 6 (hhmmss)Contains the server time (hour, minute, and second) when the record was last changed.BR155, BR51.1, BR52.1, BR52.4, BR52.5
#MSC-PROD-USER-AMT
PROD_USER_AMT		Signed 18.2—BR155, BR52.1, BR52.4, BR52.5
#MSC-PROD-BASE-AMT
PROD_BASE_AMT		Signed 18.2—BR155, BR52.1, BR52.4, BR52.5
#MSC-USER-FIELD1
USER_FIELD1		Alpha 15 (Lower Case)—BR155, BR51.1, BR52.1, BR52.4, BR52.5
#MSC-USER-FIELD2
USER_FIELD2		Alpha 15 (Lower Case)—BR155, BR51.1, BR52.1, BR52.4, BR52.5
#MSC-USER-FIELD3
USER_FIELD3		Alpha 15 (Lower Case)—BR155, BR51.1, BR52.1, BR52.4, BR52.5
#MSC-PROFORMA-FL
PROFORMA_FL		Alpha 1—
  • Y Yes
  • N No
BR02.3, BR120, BR121, BR122, BR123, BR140, BR151, BR152 +12 more
#MSC-SITE-LOCATION
SITE_LOCATION		Numeric 2—BR155, BR51.1, BR52.1, BR52.4, BR52.5
#MSC-REASON-CODE
REASON_CODE		Alpha 4This field contains the reason code, which indicates the cause for credit memos.BR155, BR157, BR52.1, BR52.4, BR52.5
#MSC-SUITE
SUITE		Alpha 6—BR155, BR51.1, BR52.1, BR52.4, BR52.5
#MSC-ORIG-CONTRACT
ORIG_CONTRACT		Alpha 15Activity Management contract.BR155, BR51.1, BR52.1, BR52.4, BR52.5
#MSC-DELIV-METHOD
DELIV_METHOD		Alpha 1—
  • S Shipped
  • H Hosted at
  • E Electronic
  • L Loaded
  • 1 Method 1
  • 2 Method 2
  • 3 Method 3
BR155, BR51.1, BR52.1, BR52.4, BR52.5

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
MSCSET1
  1. CONTRACT
  2. MAINT-SCHEDULE
  3. OBJ-ID
PrimaryBR02.3, BR10.9, BR120, BR121, BR122, BR123, BR124, BR140 +21 more
MSCSET2
  1. CONTRACT
  2. MAINT-SCHEDULE
  3. PRODUCT
  4. PROD-VERSION
  5. OBJ-ID
KeyChangeBR02.3, BR120, BR121, BR122, BR123, BR124, BR140, BR151 +15 more
MSCSET3
  1. PMH-OBJ-ID
  2. CONTRACT
  3. MAINT-SCHEDULE
  4. PRODUCT
  5. PROD-VERSION
  6. OBJ-ID
KeyChange—

Relations

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

One to one (13) — lookups and parents

RelationTableRulesConditionField map
AccntractACCNTRACTRequired
MSC-CONTRACT→CNT-CONTRACT (CNTSET1)
Accntract OrigACCNTRACTNot Required
MSC-ORIG-CONTRACT→CNT-CONTRACT
AccntrpcdACCNTRPCDNot Required
MSC-CONTRACT→CNP-CONTRACT
Acglcode BillACGLCODENot Required
MSC-BILL-GL-CD→AGC-AC-GL-CODE
Acglcode RevACGLCODENot Required
MSC-REV-GL-CD→AGC-AC-GL-CODE
Acglcode UnblACGLCODENot Required
MSC-UNBL-GL-CD→AGC-AC-GL-CODE
AcmnthdrACMNTHDRRequired
MSC-CONTRACT→MSE-CONTRACT
MSC-MAINT-SCHEDULE→MSE-MAINT-SCHEDULE
AcpmhsthdrACPMHSTHDRNot Required
MSC-PMH-OBJ-ID→PMH-OBJ-ID
AcproddtlACPRODDTLRequired
MSC-CONTRACT→AHD-CONTRACT
MSC-PRODUCT→AHD-PRODUCT
MSC-PROD-VERSION→AHD-PROD-VERSION
MSC-OBJ-ID→AHD-OBJ-ID
AcprodhdrACPRODHDRNot Required
MSC-CONTRACT→AHR-CONTRACT
Acprodhdr OrigACPRODHDRNot Required
MSC-ORIG-CONTRACT→AHR-CONTRACT
AcprodlstxACPRODLSTXRequired
MSE-PRODUCT-LIST→BRQ-PRODUCT-LIST
MSC-PRODUCT→BRQ-PRODUCT
MSC-PROD-VERSION→BRQ-PROD-VERSION
AcreasoncdACREASONCDNot Required
MSC-REASON-CODE→CDE-REASON-CODE

One to many (4) — child tables

RelationTableRulesConditionField map
AccntrcmtxACCNTRCMTX
MSC-CONTRACT→CXM-CONTRACT
MSC-MAINT-SCHEDULE→CXM-MAINT-SCHEDULE
MSC-PRODUCT→CXM-PRODUCT
MSC-PROD-VERSION→CXM-PROD-VERSION
MSC-OBJ-ID→CXM-OBJ-ID
—→CXM-COMMENT-TYPE
—→CXM-DATE
—→CXM-SEQ-NBR
AcmntschxACMNTSCHX
MSC-CONTRACT→MSD-CONTRACT
MSC-MAINT-SCHEDULE→MSD-MAINT-SCHEDULE
MSC-PRODUCT→MSD-PRODUCT
MSC-PROD-VERSION→MSD-PROD-VERSION
MSC-OBJ-ID→MSD-OBJ-ID
—→MSD-TRAN-DATE
AcprodtaxACPRODTAX
MSC-REV-ACCT-CAT→BTX-TAX-ACCT-CAT
MSC-DELIV-METHOD→BTX-DELIV-METHOD
—→BTX-EFFECTIVE-DATE
AcproduserACPRODUSER
MSE-PRODUCT-LIST→BRU-PRODUCT-LIST
MSC-PRODUCT→BRU-PRODUCT
MSC-PROD-VERSION→BRU-PROD-VERSION
MSC-EFFECTIVE-DT→BRU-EFFECTIVE-DT
—→BRU-RECORD-TYPE
—→BRU-MAX-USERS

Programs

Updated by (26)

Referenced by (3)