APEXPINV – No description in the Lawson data dictionary
- System
- Accounts Payable (AP)
- Prefix
IEX- Primary key
COMPANY,OBJ-ID- Fields
- 29
- Updated by
- 0 programs
- Referenced by
- 0 programs
APEXPINV is a Lawson Accounts Payable table (prefix IEX); no description in the lawson data dictionary. It is indexed by COMPANY, OBJ-ID (IEXSET1). The table has 29 fields, 1 index and 0 documented relations.
About APEXPINV
No description in the Lawson data dictionary.
Fields (29)
Column = COBOL field name without the IEX- prefix, hyphens → underscores. Derived fields are computed by the application and are not stored.
| Field / column | Type | Description & values | Updated by |
|---|---|---|---|
IEX-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. | — |
IEX-VENDORVENDOR | Alpha 9 (Right Justified) | The vendor's identification code. | — |
IEX-VENDOR-VNAMEVENDOR_VNAME | Alpha 30 (Lower Case) | Displays the company description. | — |
IEX-INVOICEINVOICE | Alpha 22 | Used to identify the invoice. | — |
IEX-SUFFIXSUFFIX | Numeric 3 | This is the suffix for the invoice. | — |
IEX-CANCEL-SEQCANCEL_SEQ | Numeric 4 | An automatically assigned sequence number. | — |
IEX-INV-TYPEINV_TYPE | Alpha 1 | THis field will be filled in from the Invoice based on PO number. This is a carrier for the field. The PORECEIVE file will have to be updated with this field. | — |
IEX-REC-STATUSREC_STATUS | Numeric 1 | The record status. | — |
IEX-OBJ-ID PKOBJ_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. | — |
IEX-PO-NUMBERPO_NUMBER | Alpha 14 (Right Justified) | This field contains the number representing the purchase order. | — |
IEX-PO-RELEASEPO_RELEASE | Numeric 4 | Used to identify a purchase order release (created from a Blanket or Standing order). | — |
IEX-PO-CODEPO_CODE | Alpha 4 | This is the purchase order code. | — |
IEX-LOCATIONLOCATION | Alpha 5 | This field contains a valid stocking location within the company inventory. | — |
IEX-TRAN-INV-AMTTRAN_INV_AMT | Signed 18.2 | — | — |
IEX-BASE-INV-AMTBASE_INV_AMT | Signed 18.2 | — | — |
IEX-RETAIL-AMTRETAIL_AMT | Signed 18.2 | — | — |
IEX-INVOICE-DTEINVOICE_DTE | Numeric 8 (yyyymmdd) | — | — |
IEX-CREATE-DATECREATE_DATE | Numeric 8 (yyyymmdd) | The creation date. | — |
IEX-HANDLING-CODEHANDLING_CODE | Alpha 4 | — | — |
IEX-MATCH-FLMATCH_FL | Alpha 1 | This field determines whether a transaction is considered to be a match transaction. | — |
IEX-MATCH-STATUSMATCH_STATUS | Numeric 1 | — | — |
IEX-MATCH-DATEMATCH_DATE | Numeric 8 (yyyymmdd) | This field displays the system date when this was created. | — |
IEX-MATCH-OBJ-IDMATCH_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. | — |
IEX-EXPORT-FLEXPORT_FL | Alpha 1 | — | — |
IEX-CANCELLED-FLCANCELLED_FL | Alpha 1 | — | — |
IEX-DIST-CODEDIST_CODE | Alpha 9 | A user-defined code used to automatically create expense distributions or expense distribution "shells" for invoices or to split an invoice distribution into multiple distributions. | — |
IEX-USER-FIELD-1USER_FIELD_1 | Alpha 30 | This is the first user definable field. It can be used to capture any data that the user wants. The title of the field is setup in IC00. | — |
IEX-USER-FIELD-2USER_FIELD_2 | Alpha 30 | This is the second user definable field. This field can be used to enter any data that the user wants to capture for this item. The title of the field is setup in IC00. | — |
IEX-USER-FIELD-3USER_FIELD_3 | Alpha 30 | This field is the third user definable field. It can be used to capture any data that the user wants. The name of the field is determined in IC00. | — |
Indexes (1)
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 |
|---|---|---|---|---|
IEXSET1 | COMPANY, OBJ-ID | Primary | AP20.1, AP20.2, AP20.3, AP20.4, AP20.5, AP20.7, AP21.1, AP23.1 +8 more |
Programs
No Lawson programs are documented as updating or referencing this table.