ITEM_BASE_MVW (SQL View)	Index Back
Items view for OE Past Due Itens

ITEM_BASE_MVW

(SQL View)

Items view for OE

Past Due Itens

SELECT I.BUSINESS_UNIT , I.CUST_ID , I.ITEM , I.ITEM_LINE ,A.ITEM_SEQ_NUM ,I.ENTRY_USE_ID ,I.ENTRY_TYPE , I.ORIG_ITEM_AMT , I.DISPUTE_AMOUNT , I.DISPUTE_STATUS , I.ACCOUNTING_DT , I.SUBCUST_QUAL1 , I.SUBCUST_QUAL2 , I.COLLECTOR , I.SALES_PERSON , I.CR_ANALYST , I.AR_SPECIALIST , I.BROKER_ID , I.BAL_CURRENCY , I.BAL_AMT ,I.DUE_DT , I.ITEM_STATUS ,A.POST_DT ,A.DEPOSIT_BU ,A.DEPOSIT_ID ,A.PAYMENT_SEQ_NUM , I.DISPUTE_DT , I.BAL_AMT_BASE , I.CURRENCY_CD , I.CONVERS_EXISTS , I.PYMNT_TERMS_CD ,A.ORIGIN_ID ,I.BUSINESS_UNIT_CA ,I.CONTRACT_NUM ,I.ENTRY_REASON ,I.DOCUMENT ,I.ROWID ROWID1 ,A.ROWID ROWID2 FROM PS_ITEM I ,PS_ITEM_ACTIVITY A WHERE I.BUSINESS_UNIT = A.BUSINESS_UNIT AND I.CUST_ID = A.CUST_ID AND I.ITEM = A.ITEM AND I.ITEM_LINE =A.ITEM_LINE

# PeopleSoft Field Name PeopleSoft Field Type Database Column Type Description

1 BUSINESS_UNIT Character(5) VARCHAR2(5) NOT NULL Business Unit
Prompt Table: SP_BUARDS_NONVW

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 ITEM_SEQ_NUM Number(3,0) SMALLINT NOT NULL Item Sequence Number

6 ENTRY_USE_ID Character(5) VARCHAR2(5) NOT NULL Specifies the System Function or type of processing associated with an entry type.

7 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.

8 ORIG_ITEM_AMT Signed Number(28,3) DECIMAL(26,3) NOT NULL Original Item Amount

9 DISPUTE_AMOUNT Signed Number(28,3) DECIMAL(26,3) NOT NULL Specifies the amount of an item in dispute. This may represent only a portion of the full amount of an item.

10 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.

11 ACCOUNTING_DT Date(10) DATE The accounting entry construction date for a given transaction (a generic field that crosses multiple

12 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.

13 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.

14 COLLECTOR Character(8) VARCHAR2(8) NOT NULL Specifies the personnel code for the person who works with a customer to collect overdue payments.

15 SALES_PERSON Character(8) VARCHAR2(8) NOT NULL Specifies the personnel code for the person who works with a customer as a sales representative. This field is required for a customer that functions as a bill-to customer.

16 CR_ANALYST Character(8) VARCHAR2(8) NOT NULL Specifies the personnel code for the person who works with a customer to establish credit limits and payment terms. This field is required for a bill-to customer.

17 AR_SPECIALIST Character(8) VARCHAR2(8) NOT NULL Accounts Recievable Specialist - person responsible for an action on an item.

18 BROKER_ID Character(15) VARCHAR2(15) NOT NULL Broker ID

19 BAL_CURRENCY Character(3) VARCHAR2(3) NOT NULL Currency Code - Bal Amount

20 BAL_AMT Signed Number(28,3) DECIMAL(26,3) NOT NULL Item Balance

21 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.

22 ITEM_STATUS Character(1) VARCHAR2(1) NOT NULL Item Status
C=Closed
O=Open

23 POST_DT Date(10) DATE The Date a transaction was Posted.

24 DEPOSIT_BU Character(5) VARCHAR2(5) NOT NULL Identifies the business unit to which a deposit is posted.

25 DEPOSIT_ID Character(15) VARCHAR2(15) NOT NULL Uniquely identifies a deposit of customer payments. The deposit ID can be manually assigned or system-generated.

26 PAYMENT_SEQ_NUM Number(6,0) INTEGER NOT NULL Specifies the system-generated sequence number assigned to each payment as it is entered in a deposit.

27 DISPUTE_DT Date(10) DATE Specifies the date that an item was placed in dispute status.

28 BAL_AMT_BASE Signed Number(28,3) DECIMAL(26,3) NOT NULL Balance - Base Currency

29 CURRENCY_CD Character(3) VARCHAR2(3) NOT NULL Currency Code

30 CONVERS_EXISTS Character(1) VARCHAR2(1) NOT NULL "A flag that indicates whether a conversation is associated with a single item or with multiple items ."

31 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.

32 ORIGIN_ID Character(5) VARCHAR2(5) NOT NULL Specifies the source or method of entry for a pending item group.

33 BUSINESS_UNIT_CA Character(5) VARCHAR2(5) NOT NULL Contracts Business Unit

34 CONTRACT_NUM Character(25) VARCHAR2(25) NOT NULL Contract

35 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""."

36 DOCUMENT Character(30) VARCHAR2(30) NOT NULL Specifies a document used as a reference number for a Receivables item. Document ID is used by the Receivables Update program and the Maintenance Worksheet to "match" related invoices debit memos and credit memos.

37 ROWID1 Character(254) VARCHAR2(254) NOT NULL Row ID

38 ROWID2 Character(254) VARCHAR2(254) NOT NULL Row ID

#	PeopleSoft Field Name	PeopleSoft Field Type	Database Column Type	Description
1	BUSINESS_UNIT	Character(5)	VARCHAR2(5) NOT NULL	Business Unit Prompt Table: SP_BUARDS_NONVW
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	ITEM_SEQ_NUM	Number(3,0)	SMALLINT NOT NULL	Item Sequence Number
6	ENTRY_USE_ID	Character(5)	VARCHAR2(5) NOT NULL	Specifies the System Function or type of processing associated with an entry type.
7	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.
8	ORIG_ITEM_AMT	Signed Number(28,3)	DECIMAL(26,3) NOT NULL	Original Item Amount
9	DISPUTE_AMOUNT	Signed Number(28,3)	DECIMAL(26,3) NOT NULL	Specifies the amount of an item in dispute. This may represent only a portion of the full amount of an item.
10	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.
11	ACCOUNTING_DT	Date(10)	DATE	The accounting entry construction date for a given transaction (a generic field that crosses multiple
12	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.
13	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.
14	COLLECTOR	Character(8)	VARCHAR2(8) NOT NULL	Specifies the personnel code for the person who works with a customer to collect overdue payments.
15	SALES_PERSON	Character(8)	VARCHAR2(8) NOT NULL	Specifies the personnel code for the person who works with a customer as a sales representative. This field is required for a customer that functions as a bill-to customer.
16	CR_ANALYST	Character(8)	VARCHAR2(8) NOT NULL	Specifies the personnel code for the person who works with a customer to establish credit limits and payment terms. This field is required for a bill-to customer.
17	AR_SPECIALIST	Character(8)	VARCHAR2(8) NOT NULL	Accounts Recievable Specialist - person responsible for an action on an item.
18	BROKER_ID	Character(15)	VARCHAR2(15) NOT NULL	Broker ID
19	BAL_CURRENCY	Character(3)	VARCHAR2(3) NOT NULL	Currency Code - Bal Amount
20	BAL_AMT	Signed Number(28,3)	DECIMAL(26,3) NOT NULL	Item Balance
21	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.
22	ITEM_STATUS	Character(1)	VARCHAR2(1) NOT NULL	Item Status C=Closed O=Open
23	POST_DT	Date(10)	DATE	The Date a transaction was Posted.
24	DEPOSIT_BU	Character(5)	VARCHAR2(5) NOT NULL	Identifies the business unit to which a deposit is posted.
25	DEPOSIT_ID	Character(15)	VARCHAR2(15) NOT NULL	Uniquely identifies a deposit of customer payments. The deposit ID can be manually assigned or system-generated.
26	PAYMENT_SEQ_NUM	Number(6,0)	INTEGER NOT NULL	Specifies the system-generated sequence number assigned to each payment as it is entered in a deposit.
27	DISPUTE_DT	Date(10)	DATE	Specifies the date that an item was placed in dispute status.
28	BAL_AMT_BASE	Signed Number(28,3)	DECIMAL(26,3) NOT NULL	Balance - Base Currency
29	CURRENCY_CD	Character(3)	VARCHAR2(3) NOT NULL	Currency Code
30	CONVERS_EXISTS	Character(1)	VARCHAR2(1) NOT NULL	"A flag that indicates whether a conversation is associated with a single item or with multiple items ."
31	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.
32	ORIGIN_ID	Character(5)	VARCHAR2(5) NOT NULL	Specifies the source or method of entry for a pending item group.
33	BUSINESS_UNIT_CA	Character(5)	VARCHAR2(5) NOT NULL	Contracts Business Unit
34	CONTRACT_NUM	Character(25)	VARCHAR2(25) NOT NULL	Contract
35	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""."
36	DOCUMENT	Character(30)	VARCHAR2(30) NOT NULL	Specifies a document used as a reference number for a Receivables item. Document ID is used by the Receivables Update program and the Maintenance Worksheet to "match" related invoices debit memos and credit memos.
37	ROWID1	Character(254)	VARCHAR2(254) NOT NULL	Row ID
38	ROWID2	Character(254)	VARCHAR2(254) NOT NULL	Row ID