| # |
PeopleSoft Field Name |
PeopleSoft Field Type |
Database Column Type |
Description |
| 1 |
 BUSINESS_UNIT |
Character(5) |
VARCHAR2(5) NOT NULL |
Business Unit
|
| 2 |
CUST_ID |
Character(15) |
VARCHAR2(15) NOT NULL |
Uniquely identifies an organizational entity that purchases goods or services from the enterprise. Represents the sold-to customer which is the customer organization that places orders. The CUST_ID may or may not be the same as the identifiers for the bill-to and ship-to locations.
|
| 3 |
ITEM |
Character(30) |
VARCHAR2(30) NOT NULL |
Uniquely identifies an invoice credit memo or debit memo. The item ID is also called the invoice number.
|
| 4 |
ITEM_LINE |
Number(6,0) |
INTEGER NOT NULL |
Item Line
|
| 5 |
ARCHIVE_ID |
Character(8) |
VARCHAR2(8) NOT NULL |
Archive ID
|
| 6 |
ARCHIVE_DT |
Date(10) |
DATE |
Archive Date
|
| 7 |
ACCOUNTING_DT |
Date(10) |
DATE |
The accounting entry construction date for a given transaction (a generic field that crosses multiple
|
| 8 |
OPRID |
Character(30) |
VARCHAR2(30) NOT NULL |
A user's ID (see PSOPRDEFN).
|
| 9 |
RUN_CNTL_ID |
Character(30) |
VARCHAR2(30) NOT NULL |
Run Control ID
|
| 10 |
SUBCUST_QUAL1 |
Character(15) |
VARCHAR2(15) NOT NULL |
Specifies a user-defined grouping of customer receivables activity. A subcustomer qualifier provides the ability to record and report receivables activity across multiple business units and/or multiple customers. For example a subcustomer qualifier could represent a sales region or a geographic area. There are two possible subcustomer qualifiers: SUBCUST_QUAL1 and SUBCUST_QUAL2.
|
| 11 |
SUBCUST_QUAL2 |
Character(15) |
VARCHAR2(15) NOT NULL |
Specifies a user-defined grouping of customer receivables activity. A subcustomer qualifier provides the ability to record and report receivables activity across multiple business units and/or multiple customers. For example a subcustomer qualifier could represent a sales region or a geographic area. There are two possible subcustomer qualifiers: SUBCUST_QUAL1 and SUBCUST_QUAL2.
|
| 12 |
ENTRY_TYPE |
Character(5) |
VARCHAR2(5) NOT NULL |
Specifies the type of transaction associated with a pending item. The entry type remains with the item after it is posted and affects many areas of Receivables processing. Some examples of entry types are Invoices Credit Memo Prepayment and Deduction.
|
| 13 |
ENTRY_REASON |
Character(5) |
VARCHAR2(5) NOT NULL |
"Specifies an entry reason that further qualifies the entry type associated with a pending item. For example an entry reason for a credit memo might be ""Pricing Error"" or ""Shipping Error""."
|
| 14 |
POST_DT |
Date(10) |
DATE |
The Date a transaction was Posted.
|
| 15 |
BAL_CURRENCY |
Character(3) |
VARCHAR2(3) NOT NULL |
Currency Code - Bal Amount
|