LMTRANS – Lease Management Transaction
- System
- LM (LM)
- Prefix
LMT- Primary key
COMPANY,LEASE,SEQ-NBR- Fields
- 28
- Updated by
- 1 program
- Referenced by
- 0 programs
LMTRANS is the Lease Management Transaction table in Lawson LM (prefix LMT). It is indexed by COMPANY, LEASE, SEQ-NBR (LMTSET1); alternate indexes: LMTSET2, LMTSET3, LMTSET4 and LMTSET5. It is related 1:1 to GLTRANS, LMINVOICE and LMLEASE. It is updated by AP30.4. The table has 28 fields, 5 indexes and 3 documented relations.
About LMTRANS
No description in the Lawson data dictionary.
Fields (28)
Column = COBOL field name without the LMT- prefix, hyphens → underscores. Derived fields are computed by the application and are not stored.
| Field / column | Type | Description & values | Updated by |
|---|---|---|---|
LMT-COMPANY PKCOMPANY | Numeric 4 | Identifies the AP company if the resource type = V. Identifies the HR company if the resource type = E. It is blank for type A, P or Q resources. | — |
LMT-LEASE PKLEASE | Alpha 19 | — | — |
LMT-SEQ-NBR PKSEQ_NBR | Numeric 4 | An automatically assigned sequence number. | — |
LMT-PT-COMPANYPT_COMPANY | Numeric 4 | Identifies the AP company if the resource type = V. Identifies the HR company if the resource type = E. It is blank for type A, P or Q resources. | — |
LMT-ACCT-UNITACCT_UNIT | Alpha 15 | The accounting unit is a shorthand notation representing the variable level number. When used in the General Ledger Account Master file, the accounting unit must be defined in the General Ledger Names file as a posting accounting unit. | — |
LMT-ACCOUNTACCOUNT | Numeric 6 | This field along with the accounting unit and subaccount make up the location (account) where amounts and other account information is stored. | — |
LMT-SUB-ACCOUNTSUB_ACCOUNT | Numeric 4 | This field contains the subaccount from your general ledger chart of accounts that was charged with the amount carried on this record. | — |
LMT-ACTIVITYACTIVITY | Alpha 15 | Activities are the processes or procedures that produce work. Cost objects (products, services, customers, and so on) are the reasons for performing the activity. | — |
LMT-ACCT-CATEGORYACCT_CATEGORY | Alpha 5 | Account 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 thru | — |
LMT-TRAN-AMTTRAN_AMT | Signed 18.2 | — | — |
LMT-BASE-AMTBASE_AMT | Signed 18.2 | — | — |
LMT-TO-BASE-CURRTO_BASE_CURR | Alpha 5 | — | — |
LMT-TO-BASE-NDTO_BASE_ND | Numeric 1 | The number of decimals assigned to a particular account as determined by the account currency. | — |
LMT-TO-BASE-RATETO_BASE_RATE | Signed 14.7 | The currency rate. | — |
LMT-GLT-OBJ-IDGLT_OBJ_ID | Numeric 12 | 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. | — |
LMT-TRAN-DATETRAN_DATE | Numeric 8 (yyyymmdd) | — | — |
LMT-STATUSSTATUS | Numeric 1 | This field displays the status of the transaction.
| — |
LMT-REFERENCEREFERENCE | Alpha 10 (Lower Case) | The reference number associated with the transaction. | — |
LMT-ALLOC-CDALLOC_CD | Alpha 12 | — | — |
LMT-TYPETYPE | Alpha 3 | —
| — |
LMT-PROCESSPROCESS | Alpha 3 | — | — |
LMT-REVERSEREVERSE | Alpha 1 | — | — |
LMT-PMT-VENDORPMT_VENDOR | Alpha 9 (Right Justified) | The vendor's identification code. | — |
LMT-PMT-NBRPMT_NBR | Numeric 6 | — | — |
LMT-CANCEL-SEQCANCEL_SEQ | Numeric 4 | An automatically assigned sequence number. | AP30.4 |
LMT-CREATION-DATECREATION_DATE | Numeric 8 (yyyymmdd) | This is the date that this line was added to the requisition. | — |
LMT-CREATION-TIMECREATION_TIME | Numeric 6 (hhmmss) | The creation time. | — |
LMT-CREATOR-IDCREATOR_ID | Alpha 10 | This field is used to store the login id of the person who entered the record. | — |
Indexes (5)
Keys marked * are descending. Every documented Lawson index is unique unless flagged Duplicates; Subset indexes carry a Where condition.
| Index | Keys | Flags | Condition | Used in |
|---|---|---|---|---|
LMTSET1 | COMPANY, LEASE, SEQ-NBR | Primary | — | |
LMTSET2 | COMPANY, LEASE, TYPE, PROCESS, STATUS, SEQ-NBR | — | ||
LMTSET3 | COMPANY, LEASE, SEQ-NBR* | — | ||
LMTSET4 | COMPANY, STATUS, LEASE, PMT-NBR, SEQ-NBR | AP30.4 | ||
LMTSET5 | COMPANY, LEASE, PMT-NBR, PMT-VENDOR, CANCEL-SEQ, SEQ-NBR | KeyChange, Subset | Where TYPE = "ACR" | — |
Relations
One to one (3) — lookups and parents
| Relation | Table | Rules | Condition | Field map |
|---|---|---|---|---|
| Gltrans | GLTRANS | Required | LMT-GLT-OBJ-ID → GLT-OBJ-ID (GLTSET7) | |
| Lminvoice | LMINVOICE | Required | LMT-COMPANY → INV-COMPANY, LMT-LEASE → INV-LEASE, LMT-PMT-NBR → INV-PMT-NBR, LMT-PMT-VENDOR → INV-PMT-VENDOR, LMT-CANCEL-SEQ → INV-CANCEL-SEQ | |
| Lmlease | LMLEASE | Required | LMT-COMPANY → LSE-COMPANY, LMT-LEASE → LSE-LEASE |
Programs
Updated by (1)
- AP30.4 Invoice Cancel