ITEM_OP_DUE_VW

(SQL View)
 Index Back

Open Item View that's Overdue


SELECT C.setid , I.business_unit , I.cust_id , I.item , I.item_line , I.subcust_qual1 , I.subcust_qual2 , C.name1 , C.nameshort , I.item_seq_num , I.po_ref , I.document , I.bill_of_lading , I.accounting_dt , I.accounting_dt , I.pymnt_terms_cd , I.due_dt , I.dispute_status , I.dispute_dt , I.bal_amt , I.post_dt , I.asof_dt , I.item_status , I.collection_status , I.collection_dt , I.entry_type , I.entry_reason , I.bal_amt_base , I.bal_currency , I.currency_cd , I.subrog_case_num FROM PS_ITEM I , ps_customer C WHERE c.setid = ( SELECT SETID FROM PS_SET_CNTRL_REC WHERE SETCNTRLVALUE = I.business_unit AND RECNAME = 'CUSTOMER') AND C.cust_id = I.cust_id AND I.item_status = 'O' AND I.due_dt < %CurrentDateIn

# PeopleSoft Field Name PeopleSoft Field Type Database Column Type Description
1 SETID Character(5) VARCHAR2(5) NOT NULL SetID
2 BUSINESS_UNIT Character(5) VARCHAR2(5) NOT NULL Business Unit

Prompt Table: BU_EDIT_VW_AR

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.

Prompt Table: CUST_BI_A2_VW

4 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.
5 ITEM_LINE Number(6,0) INTEGER NOT NULL Item Line
6 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.
7 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.
8 NAME1 Character(40) VARCHAR2(40) NOT NULL Name 1
9 NAMESHORT Character(10) VARCHAR2(10) NOT NULL Short Name
10 ITEM_SEQ_NUM Number(3,0) SMALLINT NOT NULL Item Sequence Number
11 PO_REF Character(30) VARCHAR2(30) NOT NULL Specifies the purchase order number associated with a receivables item.
12 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.
13 BILL_OF_LADING Character(30) VARCHAR2(30) NOT NULL Specifies a bill of lading number associated with a Receivables item.
14 ACCOUNTING_DT Date(10) DATE The accounting entry construction date for a given transaction (a generic field that crosses multiple
15 EFFDT Date(10) DATE Effective Date
16 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.
17 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.
18 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.

Default Value: N

Prompt Table: DISPUTE_TBL

19 DISPUTE_DT Date(10) DATE Specifies the date that an item was placed in dispute status.
20 BAL_AMT Signed Number(28,3) DECIMAL(26,3) NOT NULL Item Balance
21 POST_DT Date(10) DATE The Date a transaction was Posted.
22 ASOF_DT Date(10) DATE As of Date
23 ITEM_STATUS Character(1) VARCHAR2(1) NOT NULL Item Status
C=Closed
O=Open
24 COLLECTION_STATUS Character(3) VARCHAR2(3) NOT NULL Specifies a collection agency or the reason for placing a customer in collection. Collection status indicates that the customer is delinquent in making payments or the invoice is more than 120 days past due.

Prompt Table: COLLECTION_TBL

25 COLLECTION_DT Date(10) DATE Specifies the date that a customer or invoice was put in collection status. Collection status indicates that the customer is delinquent in making payments or the invoice is more than 120 days past due.
26 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.
27 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""."
28 BAL_AMT_BASE Signed Number(28,3) DECIMAL(26,3) NOT NULL Balance - Base Currency
29 BAL_CURRENCY Character(3) VARCHAR2(3) NOT NULL Currency Code - Bal Amount
30 CURRENCY_CD Character(3) VARCHAR2(3) NOT NULL Currency Code
31 SUBROG_CASE_NUM Character(30) VARCHAR2(30) NOT NULL Subrogation case number used for Insurance