APUAVAL – No description in the Lawson data dictionary

System
Accounts Payable (AP)
Prefix
UAV
Primary key
SEG-TYPE, API-OBJ-ID, DIST-SEQ-NBR
Fields
4
Updated by
55 programs
Referenced by
199 programs

APUAVAL is a Lawson Accounts Payable table (prefix UAV); no description in the lawson data dictionary. It is indexed by SEG-TYPE, API-OBJ-ID, DIST-SEQ-NBR (UAVSET1). It is updated by AP125, AP126, AP170, AP180, AP181, AP190, AP193, AP198 and 47 more and referenced by AM19.1, AM19.2, AM19.4, AP115, AP131, AP175, AP220, AP305 and 191 more. The table has 4 fields, 1 index and 0 documented relations.

About APUAVAL

No description in the Lawson data dictionary.

Fields (4)

Column = COBOL field name without the UAV- prefix, hyphens → underscores. Derived fields are computed by the application and are not stored.

Field / columnTypeDescription & valuesUpdated by
UAV-SEG-TYPE PK
SEG_TYPE		Alpha 1This 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.AP125, AP126, AP170, AP180, AP181, AP190, AP20.1, AP20.2 +41 more
UAV-API-OBJ-ID PK
API_OBJ_ID		Numeric 12This 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.AP125, AP126, AP170, AP180, AP181, AP190, AP193, AP20.1 +44 more
UAV-DIST-SEQ-NBR PK
DIST_SEQ_NBR		Numeric 6A unique sequence number.AP125, AP126, AP170, AP180, AP181, AP190, AP20.1, AP20.2 +44 more
UAV-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.AP125, AP126, AP180, AP181, AP190, AP20.1, AP20.2, AP20.3 +40 more

Indexes (1)

Keys marked * are descending. Every documented Lawson index is unique unless flagged Duplicates; Subset indexes carry a Where condition.

IndexKeysFlagsConditionUsed in
UAVSET1SEG-TYPE, API-OBJ-ID, DIST-SEQ-NBRPrimaryAM19.1, AM19.2, AM19.4, AP115, AP125, AP126, AP131, AP170 +22 more (list truncated in source)

Programs

Updated by (55)

Referenced by (199)