SC_CLOS_ITM_TMP

#	PeopleSoft Field Name	PeopleSoft Field Type	Database Column Type	Description
1	PROCESS_INSTANCE	Number(10,0)	DECIMAL(10) NOT NULL	Process Instance
2	BUSINESS_UNIT	Character(5)	VARCHAR2(5) NOT NULL	Business Unit
3	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.
4	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.
5	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.
6	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.
7	ITEM_LINE	Number(6,0)	INTEGER NOT NULL	Item Line
8	ENTRY_AMT	Signed Number(28,3)	DECIMAL(26,3) NOT NULL	Represents the monetary amount of a pending item transaction such as invoice or credit memo.
9	DAYS_LATE	Signed Number(7,0)	DECIMAL(6) NOT NULL	Days Late
10	TERM_DAYS	Signed Number(4,0)	DECIMAL(3) NOT NULL	Terms days
11	DUE_DT	Date(10)	DATE	Specifies the date that a transaction is due. It is a generic field used in multiple PeopleSoft applications including Receivables Payables and Purchasing. For example it represents the date that payment is due for a voucher or the date that a scheduled shipment is due to be received.
12	ACCOUNTING_DT	Date(10)	DATE	The accounting entry construction date for a given transaction (a generic field that crosses multiple
13	ASOF_DT	Date(10)	DATE	As of Date
14	USER_DT1	Date(10)	DATE	Specifies an additional date associated with a pending receivables item. This field is customizable and user-defined and is one of four user date fields (USER_DT1 through USER_DT4).
15	USER_DT2	Date(10)	DATE	Specifies an additional date associated with a pending receivables item. This field is customizable and user-defined and is one of four user date fields (USER_DT1 through USER_DT4).
16	USER_DT3	Date(10)	DATE	Specifies an additional date associated with a pending receivables item. This field is customizable and user-defined and is one of four user date fields (USER_DT1 through USER_DT4).
17	USER_DT4	Date(10)	DATE	Specifies an additional date associated with a pending receivables item. This field is customizable and user-defined and is one of four user date fields (USER_DT1 through USER_DT4).
18	PYMNT_TERMS_DT	Character(1)	VARCHAR2(1) NOT NULL	Payment Terms Basis Date 1=User Date 1 2=User Date 2 A=As of Date I=Accounting Date N=Invoice Date
19	FISCAL_YEAR	Number(4,0)	SMALLINT NOT NULL	Fiscal Year
20	ACCOUNTING_PERIOD	Number(3,0)	SMALLINT NOT NULL	Identifies a time period to which you post transactions. Typically, an accounting period represents a month, but it can also represent a week, a day, or any user-defined interval. An accounting period has a beginning date and an ending date, and is defined in the calendar table.
21	DISPUTE_STATUS	Character(3)	VARCHAR2(3) NOT NULL	Specifies the reason that an item or customer is in dispute. For example the dispute status code might represent pricing error.
22	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.
23	PYMNT_TERMS_CD	Character(5)	VARCHAR2(5) NOT NULL	Specifies how the payment due date and discount due date are calculated. A payment terms code is associated with various business units bill-to customers vendors as well as sales orders purchase orders and vouchers.
24	CURRENCY_CD	Character(3)	VARCHAR2(3) NOT NULL	Currency Code