# Infor Lawson S3 GL and AP Table Reference > Source: https://netray.co/tools/infor-lawson-s3-gl-ap-table-reference > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer The Lawson S3 General Ledger, Accounts Payable and Cash Ledger tables report writers use, with field prefixes, primary index keys and common joins. ## Category other-erp ## Erp Infor Lawson S3 ## Audience - Lawson developer - Report writer - Finance systems analyst - ERP administrator ## Tool **Kind:** worksheet **Mode:** reference **Columns:** #### Table **Key:** table **Type:** text #### System **Key:** system **Type:** text #### Description **Key:** description **Type:** text #### Field prefix **Key:** prefix **Type:** text #### Primary index and keys **Key:** index **Type:** text #### Key reporting columns **Key:** cols **Type:** text #### Common join **Key:** join **Type:** text #### SQL column example **Key:** sql **Type:** text **Rows:** **Table:** GLTRANS **System:** GL **Description:** General Ledger Transactions **Prefix:** GLT- **Index:** GLTSET1: COMPANY, FISCAL-YEAR, ACCT-PERIOD, CONTROL-GROUP, SYSTEM, JE-TYPE, JE-SEQUENCE, LINE-NBR **Cols:** ACCT-UNIT, ACCOUNT, SUB-ACCOUNT, BASE-AMOUNT, POSTING-DATE, STATUS, SOURCE-CODE, DESCRIPTION **Join:** GLCONTROL on COMPANY, FISCAL-YEAR, ACCT-PERIOD, CONTROL-GROUP, SYSTEM, JE-TYPE, JE-SEQUENCE **Sql:** BASE_AMOUNT **Table:** GLAMOUNTS **System:** GL **Description:** General Ledger Amounts (beginning and period balances) **Prefix:** GAM- **Index:** GAMSET1: COMPANY, FISCAL-YEAR, ACCT-UNIT, ACCOUNT, SUB-ACCOUNT **Cols:** DB-BEG-BAL, CR-BEG-BAL, DB-AMOUNT and CR-AMOUNT (occurs 13), CHART-NAME **Join:** GLMASTER on COMPANY, ACCT-UNIT, ACCOUNT, SUB-ACCOUNT **Sql:** DB_AMOUNT_01 .. DB_AMOUNT_13 **Table:** GLUNITS **System:** GL **Description:** General Ledger Units (statistical balances) **Prefix:** GLU- **Index:** GLUSET1: COMPANY, FISCAL-YEAR, ACCT-UNIT, ACCOUNT, SUB-ACCOUNT **Cols:** DB-BEG-BAL, CR-BEG-BAL, DB-UNITS, CR-UNITS **Join:** GLAMOUNTS on the same five keys **Sql:** DB_UNITS_01 **Table:** GLMASTER **System:** GL **Description:** General Ledger Account Master **Prefix:** GLM- **Index:** GLMSET1: COMPANY, ACCOUNT, SUB-ACCOUNT, VAR-LEVELS, ACCT-UNIT **Cols:** ACTIVE-STATUS, POSTING-LEVEL, CHART-NAME, CURRENCY-CODE **Join:** GLNAMES on COMPANY, ACCT-UNIT **Sql:** ACTIVE_STATUS **Table:** GLNAMES **System:** GL **Description:** General Ledger Names (accounting units) **Prefix:** GLN- **Index:** GLNSET1: COMPANY, ACCT-UNIT **Cols:** DESCRIPTION, VAR-LEVELS, LEVEL-DEPTH, POSTING-FLAG, ACTIVE-STATUS **Join:** GLTRANS or GLAMOUNTS on COMPANY, ACCT-UNIT **Sql:** LEVEL_DEPTH **Table:** GLCHARTDTL **System:** GL **Description:** General Ledger Chart Detail (accounts in a chart) **Prefix:** GDT- **Index:** GDTSET1: CHART-NAME, SUMRY-ACCT-ID, ACCOUNT, SUB-ACCOUNT **Cols:** ACCOUNT-DESC, CHART-SECTION, POSTING-LEVEL, ACTIVE-STATUS, ACCT-CATEGORY **Join:** GLSYSTEM.CHART-NAME, then ACCOUNT, SUB-ACCOUNT **Sql:** ACCOUNT_DESC **Table:** GLCHART **System:** GL **Description:** General Ledger Chart **Prefix:** GCH- **Index:** GCHSET1: CHART-NAME **Cols:** DESCRIPTION, RE-ACCOUNT, RE-SUB-ACCT, SEGMENT-GROUP **Join:** GLCHARTDTL on CHART-NAME **Sql:** RE_ACCOUNT **Table:** GLSYSTEM **System:** GL **Description:** General Ledger Company **Prefix:** GLS- **Index:** GLSSET1: COMPANY **Cols:** NAME, CHART-NAME, FISCAL-YEAR, ACCT-PERIOD, NBR-ACCT-PERS, CURRENCY-CODE **Join:** Any GL table on COMPANY **Sql:** NBR_ACCT_PERS **Table:** GLCONTROL **System:** GL **Description:** General Ledger Control (journal entry headers) **Prefix:** GLC- **Index:** GLCSET1: COMPANY, FISCAL-YEAR, ACCT-PERIOD, SYSTEM, JE-TYPE, CONTROL-GROUP, JE-SEQUENCE **Cols:** STATUS, DESCRIPTION, POSTING-DATE, OPERATOR, SOURCE-CODE, REFERENCE **Join:** GLTRANS on the journal keys **Sql:** CONTROL_GROUP **Table:** GLCODES **System:** GL **Description:** General Ledger Codes (system codes, source codes, periods) **Prefix:** GCD- **Index:** GCDSET1: RECORD-TYPE, FOLDER-NAME, PROCESS-GROUP, SYSTEM, COMPANY **Cols:** SOURCE-CODE, DESCRIPTION, OPEN-PERIODS **Join:** GLTRANS on SOURCE-CODE (via GCDSET3) **Sql:** SOURCE_CODE **Table:** GLCGCPY **System:** GL **Description:** Company Group Company **Prefix:** GCC- **Index:** GCCSET1: COMPANY, COMPANY-GROUP **Cols:** COMPANY-GROUP, SEQ-NBR **Join:** GLSYSTEM on COMPANY **Sql:** COMPANY_GROUP **Table:** APVENMAST **System:** AP **Description:** Vendor **Prefix:** VEN- **Index:** VENSET1: VENDOR-GROUP, VENDOR **Cols:** VENDOR-VNAME, VENDOR-SNAME, VEN-CLASS, VENDOR-STATUS, TAX-ID, TERM-CODE **Join:** APINVOICE on VENDOR-GROUP, VENDOR **Sql:** VENDOR_VNAME **Table:** APVENLOC **System:** AP **Description:** Vendor Location **Prefix:** VLO- **Index:** VLOSET1: VENDOR-GROUP, VENDOR, LOCATION-CODE **Cols:** LOC-TYPE, VENDOR-VNAME, E-MAIL-ADDRESS, ACTIVE-STATUS **Join:** APVENMAST on VENDOR-GROUP, VENDOR **Sql:** LOCATION_CODE **Table:** APVENCLASS **System:** AP **Description:** Vendor Class **Prefix:** VCL- **Index:** VCLSET1: VENDOR-GROUP, VEN-CLASS **Cols:** DESCRIPTION, CASH-CODE, REQUIRE-PO **Join:** APVENMAST on VENDOR-GROUP, VEN-CLASS **Sql:** VEN_CLASS **Table:** APCOMPANY **System:** AP **Description:** Accounts Payable Company **Prefix:** CPY- **Index:** CPYSET1: COMPANY **Cols:** NAME, VENDOR-GROUP, PAY-GROUP, BASE-CURRENCY, CASH-CODE **Join:** APINVOICE on COMPANY **Sql:** VENDOR_GROUP **Table:** APINVOICE **System:** AP **Description:** Accounts Payable Invoice **Prefix:** API- **Index:** APISET1: COMPANY, VENDOR, INVOICE, SUFFIX, CANCEL-SEQ **Cols:** INVOICE-DTE, DUE-DATE, PO-NUMBER, BASE-INV-AMT, REC-STATUS, VOUCHER-NBR, OBJ-ID **Join:** APVENMAST on VENDOR-GROUP, VENDOR **Sql:** BASE_INV_AMT **Table:** APDISTRIB **System:** AP **Description:** Invoice Distribution **Prefix:** APD- **Index:** APDSET1: API-OBJ-ID, DIST-SEQ-NBR **Cols:** DIST-COMPANY, DIS-ACCT-UNIT, DIS-ACCOUNT, DIS-SUB-ACCT, ORIG-BASE-AMT, DISTRIB-DATE **Join:** APINVOICE on API-OBJ-ID = API-OBJ-ID, or COMPANY, VENDOR, INVOICE, SUFFIX, CANCEL-SEQ **Sql:** DIS_ACCOUNT **Table:** APPAYMENT **System:** AP **Description:** Invoice Payment **Prefix:** APP- **Index:** APPSET1: COMPANY, VENDOR, INVOICE, SUFFIX, CANCEL-SEQ, SEQ-NBR, VOID-SEQ **Cols:** DUE-DATE, BASE-PMT-AMT, CHECK-DATE, TRANS-NBR, BANK-INST-CODE, CASH-CODE, REC-STATUS **Join:** APINVOICE on COMPANY, VENDOR, INVOICE, SUFFIX, CANCEL-SEQ **Sql:** BASE_PMT_AMT **Table:** CBCHECK **System:** CB **Description:** Accounts Payable Cash Payment (checks and payments) **Prefix:** CHK- **Index:** CHKSET1: CASH-CODE, BANK-INST-CODE, TRANS-IDENT **Cols:** TRANS-NBR, CHECK-DATE, PAID-VENDOR, PAID-NAME, BASE-PMT-AMT, REC-STATUS **Join:** APPAYMENT on CASH-CODE, BANK-INST-CODE, TRANS-IDENT **Sql:** PAID_VENDOR **Table:** MAINVDTL **System:** MA **Description:** Matching Invoice Detail (PO match lines) **Prefix:** MAD- **Index:** MADSET1: COMPANY, VENDOR, INVOICE, SUFFIX, PO-NUMBER, PO-RELEASE, PO-CODE, LINE-NBR, SEQ-NBR **Cols:** ITEM, MATCHED-QTY, MATCH-UNIT-CST, TOT-BASE-AMT, API-OBJ-ID **Join:** APINVOICE on API-OBJ-ID **Sql:** MATCHED_QTY **Notes:** Tables, prefixes and index keys checked against the LawsonGuru data dictionary for Lawson Applications 9.0 (lawsonguru.com/gurucontent/datadict/90). The SQL column example shows the usual database naming: the 4GL prefix is dropped, hyphens become underscores and occurs fields get a _01 to _nn suffix. Confirm names on your own database, because Apps 10 and site changes can add fields. ## Content **Intro:** This is a searchable reference to the Lawson S3 General Ledger, Accounts Payable, Cash Ledger and matching tables that report writers and developers use most, checked against the Lawson Applications 9.0 data dictionary. Each row gives the field prefix, the primary index and its keys, the columns used most in reports and the usual join. **Sections:** #### 4GL names vs database column names **Body:** In Lawson 4GL and the data dictionary, every field carries the table prefix, such as GLT-BASE-AMOUNT in GLTRANS or API-INVOICE-DTE in APINVOICE. In the relational database behind LSF, columns are usually stored without the prefix and with underscores, so GLT-BASE-AMOUNT appears as BASE_AMOUNT. Fields that occur more than once get a numeric suffix, so the 13 GLAMOUNTS period buckets become DB_AMOUNT_01 to DB_AMOUNT_13 and CR_AMOUNT_01 to CR_AMOUNT_13. DME and Transaction calls use the 4GL element names without the prefix. Direct SQL uses the database column names. #### GLTRANS vs GLAMOUNTS for reporting **Body:** Use GLAMOUNTS for balances and trial balances. It holds one row per company, fiscal year, accounting unit, account and subaccount, with beginning balances and 13 period buckets, so a full-year trial balance reads very few rows. Use GLTRANS when you need detail: journal lines, source codes, posting dates, references and descriptions. GLTRANS can be very large, so filter on its indexes. GLTSET1 starts with company, fiscal year and period, and GLTSET2 starts with to-company, fiscal year, period and the account string. Posted totals from GLTRANS for a period should match the GLAMOUNTS buckets for the same accounts. **Bullets:** - Balances: GLAMOUNTS, keyed by GAMSET1 - Journal detail: GLTRANS joined to GLCONTROL - Account descriptions: GLCHARTDTL through the company's CHART-NAME in GLSYSTEM - Accounting unit names: GLNAMES #### Finding the data dictionary and screens **Body:** The full field list for any table is in the Lawson data dictionary. On the server, the dbdef utility shows the definition for your product line, and the LawsonGuru site publishes the 9.0 dictionary by table, with indexes, relations and the programs that read and update each table. Common screens tied to these tables include GL40.1 Journal Entry and GL190 Journal Posting (GLTRANS, GLAMOUNTS), GL90.1 Transaction Analysis, GL10.1 Company (GLSYSTEM), AP10.1 Vendor (APVENMAST), AP20.1 Basic Invoice and AP30.1 Invoice Maintenance (APINVOICE), and AP90.1 Invoice Search by Vendor, Invoice. #### Sign convention and common mistakes **Body:** Lawson normally stores credits as negative amounts, so a period's net activity is the debit bucket plus the credit bucket, not debit minus credit. Before you publish a report, check your result against the GL trial balance or the GL90.1 inquiry for a few accounts. Other common mistakes are forgetting that the account string is accounting unit plus account plus subaccount, joining GLTRANS to accounts without COMPANY, and summing GLTRANS lines whose STATUS shows they are not posted. Several GLTRANS indexes exclude STATUS 8 rows, so check what each status value means on your release before filtering. **Cta:** If you want finance to ask Lawson GL and AP questions in plain English, on your own servers and with the query shown, we can set up a private assistant over these tables. **Faq:** #### What is Lawson S3? **Answer:** Lawson S3 is the Lawson, now Infor, on-premises application suite covering Financials, HR, Payroll and Supply Chain, running on the Lawson Environment or Lawson System Foundation (LSF). Its data lives in tables such as GLTRANS, GLAMOUNTS and APINVOICE, defined in the Lawson data dictionary. #### Which Lawson table holds GL balances? **Answer:** GLAMOUNTS holds GL balances by company, fiscal year, accounting unit, account and subaccount. It has debit and credit beginning balances and 13 period buckets for debits and credits. GLUNITS holds the same structure for statistical units. Use GLTRANS only when you need transaction detail. #### How do I join APINVOICE to APDISTRIB? **Answer:** APDISTRIB's primary index APDSET1 is API-OBJ-ID plus DIST-SEQ-NBR, so the usual join is APINVOICE OBJ-ID to APDISTRIB API-OBJ-ID. APDISTRIB also carries COMPANY, VENDOR, INVOICE, SUFFIX and CANCEL-SEQ, so you can join on the invoice key fields instead. #### Where can I get an Infor Lawson report listing? **Answer:** The data dictionary lists, for each table, the programs that reference and update it, which gives you a report and program listing by table. On your own system, use the Lawson job and program lists and dbdef. LawsonGuru publishes the 9.0 dictionary for tables, elements and programs. ## Search terms infor lawson s3, what is lawson s3, infor lawson report listing, what is infor s3, infor lawson system, lawson gltrans table, lawson glamounts table, lawson apinvoice table --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json