MAINVHAND – Invoice Handling Code

System
Matching (MA)
Prefix
MAH
Primary key
HANDLING-CODE
Fields
18
Updated by
3 programs
Referenced by
306 programs

MAINVHAND is the Invoice Handling Code table in Lawson Matching (prefix MAH). It is indexed by HANDLING-CODE (MAHSET1); alternate indexes: MAHSET2 and MAHSET3. It is related 1:1 to SYSTEMCODE and 1:M to APPROCLEV, APVENMAST and MACOMPANY. It is updated by MA01.1, MA05.1 and MA05.6 and referenced by AC160, AC42.1, AM115, AM117, AM15.1, AM15.2, AM15.3, AM15.4 and 298 more. The table has 18 fields, 3 indexes and 4 documented relations.

About MAINVHAND

The Invoice Handling Code file contains an invoice handling code, its description, and the invoice processing rules assigned to the handling code. Invoice handling codes are defined in MA05.1 (Handling Code).

Fields (18)

Column = COBOL field name without the MAH- 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
#MAH-COMPANY SET2 SET3
COMPANY		Numeric 4The company number that the invoice handling code is assigned to.MA05.1, MA05.6
#MAH-HANDLING-CODE PK
HANDLING_CODE		Alpha 4Handling code. Contains processing rules for invoice matching. Handling codes are assigned at the company level.MA05.1, MA05.6
#MAH-VENDOR-GROUP SET3
VENDOR_GROUP		Alpha 4Vendor group. Represents a group of vendors that can be shared by one or more companies.MA05.1, MA05.6
#MAH-DESCRIPTION
DESCRIPTION		Alpha 30 (Lower Case)A description of the invoice handling code.MA05.1, MA05.6
#MAH-MATCH-FL
MATCH_FL		Alpha 1Indicates if invoices assigned this handling code are eligible for matching. Valid values are:
  • N No
  • Y Yes
MA05.1, MA05.6
#MAH-AOC-FL
AOC_FL		Alpha 1Indicates if the invoice assigned this handling code will be defined as an add on cost only invoice. Valid values are:
  • N No
  • Y Yes
MA05.1, MA05.6
#MAH-SERVICE-FL
SERVICE_FL		Alpha 1This field indicates a transaction is a Service only transaction.
  • N No
  • Y Yes
MA05.1, MA05.6
#MAH-USE-PO-AOC
USE_PO_AOC		Alpha 1Indicates if add on cost information from the purchase order will be used. Valid values are:
  • N No
  • Y Yes
MA05.1, MA05.6
#MAH-VOUCHER-REQ
VOUCHER_REQ		Alpha 1Indicates if a voucher number is required. Valid values are:
  • N No
  • Y Yes
MA05.1, MA05.6
#MAH-BYPASS-MATCH
BYPASS_MATCH		Alpha 1—
  • Y Yes
  • N No
MA05.1, MA05.6
#MAH-ACCT-UNIT
ACCT_UNIT		Alpha 15The 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.MA05.1, MA05.6
#MAH-ACCOUNT
ACCOUNT		Numeric 6This field along with the accounting unit and subaccount make up the location (account) where amounts and other account information is stored.MA05.1, MA05.6
#MAH-SUB-ACCT
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.MA05.1, MA05.6
#MAH-SEGMENT-BLOCK
SEGMENT_BLOCK		Alpha 103This field identifies the user analysis values included in the transaction. You can either type up to four values or use Define (F6) to open the User Analysis Entry subform. Use this subform to select the user analysis values you want to include in the transaction. If you choose to type values, use commas to separate them. For example: value1,value2,value3,value4 There are three conditions that affect how you can select user analysis values. See the User Analysis Entry form help or the Strategic Ledger procedures manual for additional information.MA05.1, MA05.6
#MAH-COCO-FL
COCO_FL		Numeric 1This is the flag when added to the handling code denotes that the invoice will be reviewed for match based on header, line, and Cost components (AOC)
  • 0 No
  • 1 Yes
MA05.1
#MAH-RULE-GROUP
RULE_GROUP		Alpha 10—MA05.1
#MAH-MATCH-LEVEL
MATCH_LEVEL		Alpha 3—MA05.1
#MAH-DROPSHIP-FL
DROPSHIP_FL		Alpha 1This flag indicates whether goods being shipped by the vendor directly to a non standard location need to have the receiving process performed.
  • Y Yes
  • N No
MA05.1, MA05.6

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
MAHSET1
  1. HANDLING-CODE
PrimaryAC160, AC42.1, AM115, AM117, AM15.1, AM15.2, AM15.3, AM15.4 +22 more (list truncated in source)
MAHSET2
  1. COMPANY
  2. HANDLING-CODE
KeyChangeAPI5.1, MA01.1, MA05.6, MA205, MA26.1
MAHSET3
  1. VENDOR-GROUP
  2. HANDLING-CODE
  3. COMPANY
KeyChangeAP110, MA205

Relations

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

One to one (1) — lookups and parents

RelationTableRulesConditionField map
SystemcodepmSYSTEMCODERequired
"PM"→SYS-SYSTEM

One to many (3) — child tables

RelationTableRulesConditionField map
ApproclevAPPROCLEV
MAH-HANDLING-CODE→APR-HANDLING-CODE
—→APR-COMPANY
—→APR-PROC-LEVEL
ApvenmastAPVENMAST
MAH-HANDLING-CODE→VEN-HANDLING-CODE
—→VEN-VENDOR-GROUP
—→VEN-VENDOR
MacompanyMACOMPANY
MAH-HANDLING-CODE→MAY-HANDLING-CODE
—→MAY-COMPANY

Programs

Updated by (3)

Referenced by (306)