APUAVHIST – No description in the Lawson data dictionary
- System
- Accounts Payable (AP)
- Prefix
AH5- Primary key
SEG-TYPE,API-OBJ-ID,DIST-SEQ-NBR- Fields
- 4
- Updated by
- 8 programs
- Referenced by
- 0 programs
APUAVHIST is a Lawson Accounts Payable table (prefix AH5); no description in the lawson data dictionary. It is indexed by SEG-TYPE, API-OBJ-ID, DIST-SEQ-NBR (AH5SET1). It is updated by AP180, AP181, AP190, AP198, AP28.1, AP28.2, AP300 and AP45.1. The table has 4 fields, 1 index and 0 documented relations.
About APUAVHIST
No description in the Lawson data dictionary.
Fields (4)
Column = COBOL field name without the AH5- prefix, hyphens → underscores. Derived fields are computed by the application and are not stored.
| Field / column | Type | Description & values | Updated by |
|---|---|---|---|
AH5-SEG-TYPE PKSEG_TYPE | Alpha 1 | This identifies whether the information included in the ledger defined in SL50.1 (Strategic Ledger) General Ledger only information, a user analysis field, or an attribute. | AP198 |
AH5-API-OBJ-ID PKAPI_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. | AP198 |
AH5-DIST-SEQ-NBR PKDIST_SEQ_NBR | Numeric 6 | A unique sequence number. | AP198 |
AH5-SEGMENT-BLOCKSEGMENT_BLOCK | Alpha 103 | This 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. | AP198 |
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 |
|---|---|---|---|---|
AH5SET1 | SEG-TYPE, API-OBJ-ID, DIST-SEQ-NBR | Primary | AP180, AP181, AP190, AP28.1, AP28.2, AP300, AP45.1 |