REFERENCED BY
AP20.1 | AP20.2 | AP20.3 | AP20.4 | AP20.5 | AP20.7 |
AP21.1 | AP23.1 | MA41.1 | MA41.2 | MA41.4 | MA41.7 |
MA42.2 | MA43.2 | MA44.1 | MA44.2 |
FIELD NAME | DESCRIPTION/VALID VALUES | UPDATED BY | |
---|---|---|---|
IEX-COMPANY Element: Company | 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-VENDOR Element: Vendor | Alpha 9 (Right Justified) The vendor's identification code. |
|
|
IEX-VENDOR-VNAME Element: Name | Alpha 30 (Lower Case) Displays the company description. |
|
|
IEX-INVOICE Element: Invoice | Alpha 22 Used to identify the invoice. |
|
|
IEX-SUFFIX Element: Suffix | Numeric 3 This is the suffix for the invoice. |
|
|
IEX-CANCEL-SEQ Element: Seq Nbr | Numeric 4 An automatically assigned sequence number. |
|
|
IEX-INV-TYPE Element: Invoice 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-STATUS Element: Rec Status | Numeric 1 The record status. |
|
|
IEX-OBJ-ID Element: 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-PO-NUMBER Element: Po Number | Alpha 14 (Right Justified) This field contains the number representing the purchase order. |
|
|
IEX-PO-RELEASE Element: Po Release | Numeric 4 Used to identify a purchase order release (created from a Blanket or Standing order). |
|
|
IEX-PO-CODE Element: Po Code | Alpha 4 This is the purchase order code. |
|
|
IEX-LOCATION Element: Location | Alpha 5 This field contains a valid stocking location within the company inventory. |
|
|
IEX-TRAN-INV-AMT Element: Intl Amt | Signed 18.2 |
|
|
IEX-BASE-INV-AMT Element: Intl Amt | Signed 18.2 |
|
|
IEX-RETAIL-AMT Element: Intl Amt | Signed 18.2 |
|
|
IEX-INVOICE-DTE Element: Invoice Dte | Numeric 8 (yyyymmdd) |
|
|
IEX-CREATE-DATE Element: Create Date | Numeric 8 (yyyymmdd) The creation date. |
|
|
IEX-HANDLING-CODE Element: Handling Code | Alpha 4 |
|
|
IEX-MATCH-FL Element: Match Fl | Alpha 1 This field determines whether a transaction is considered to be a match transaction. |
|
|
IEX-MATCH-STATUS Element: Match Status | Numeric 1 |
|
|
IEX-MATCH-DATE Element: Date | Numeric 8 (yyyymmdd) This field displays the system date when this was created. |
|
|
IEX-MATCH-OBJ-ID Element: 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-FL Element: All Flag | Alpha 1 |
|
|
IEX-CANCELLED-FL Element: All Flag | Alpha 1 |
|
|
IEX-DIST-CODE Element: Dist 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-1 Element: User Field1 | 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-2 Element: User Field2 | 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-3 Element: User Field3 | 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. |
|
NAME | KEY FIELDS | DESCRIPTION / SUBSET CONDITION | USED IN | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
IEXSET1 |
COMPANY OBJ-ID |
|
|
All trademarks and registered trademarks are the property of their
respective owners.