AR_DISPUTES_RSP (SQL View)	Index Back
Recent Disputes

AR_DISPUTES_RSP

(SQL View)

Recent Disputes

SELECT S.SETID , I.CUST_ID , I.BUSINESS_UNIT , I.ITEM , I.ITEM_LINE , I.BAL_AMT , I.BAL_CURRENCY , I.ACCOUNTING_DT , I.DUE_DT , I.ENTRY_TYPE , I.ENTRY_REASON , I.ORIG_ITEM_AMT , I.DISPUTE_STATUS , I.DISPUTE_DT , I.DISPUTE_AMOUNT , I.CR_ANALYST , I.COLLECTOR , I.SALES_PERSON , I.AR_SPECIALIST , 0 , %CurrentDateTimeIn , %OperatorId , %CurrentDateTimeIn , %OperatorId , 0 , %CurrentDateTimeIn FROM PS_ITEM I , PS_SET_CNTRL_REC S WHERE S.SETCNTRLVALUE = I.BUSINESS_UNIT AND S.RECNAME = 'CUSTOMER' AND I.ITEM_STATUS = 'O' AND I.DISPUTE_STATUS <> ' '

# PeopleSoft Field Name PeopleSoft Field Type Database Column Type Description

1 SETID Character(5) VARCHAR2(5) NOT NULL SetID

2 BILL_TO_CUST_ID Character(15) VARCHAR2(15) NOT NULL Customer

3 BUSINESS_UNIT Character(5) VARCHAR2(5) NOT NULL Business Unit

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 BAL_AMT Signed Number(28,3) DECIMAL(26,3) NOT NULL Item Balance

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

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

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

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

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

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

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

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

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

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 COLLECTOR Character(8) VARCHAR2(8) NOT NULL Specifies the personnel code for the person who works with a customer to collect overdue payments.

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

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

20 TOTAL_ROW_COUNT Number(8,0) INTEGER NOT NULL Total Row Count

21 ROW_ADDED_DTTM DateTime(26) TIMESTAMP Added Date/Time

22 ROW_ADDED_OPRID Character(30) VARCHAR2(30) NOT NULL Added By

23 ROW_LASTMANT_DTTM DateTime(26) TIMESTAMP Last Modified Date/Time

24 ROW_LASTMANT_OPRID Character(30) VARCHAR2(30) NOT NULL Last Maintained By

25 SYNCID Number(10,0) DECIMAL(10) NOT NULL The Synchronization ID field stores a value generated by the sync processor. The value is used to identify the type of object that the sync processor is about to handle.

26 SYNCDTTM DateTime(26) TIMESTAMP Synchronization Last Update Date Time

#	PeopleSoft Field Name	PeopleSoft Field Type	Database Column Type	Description
1	SETID	Character(5)	VARCHAR2(5) NOT NULL	SetID
2	BILL_TO_CUST_ID	Character(15)	VARCHAR2(15) NOT NULL	Customer
3	BUSINESS_UNIT	Character(5)	VARCHAR2(5) NOT NULL	Business Unit
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	BAL_AMT	Signed Number(28,3)	DECIMAL(26,3) NOT NULL	Item Balance
7	BAL_CURRENCY	Character(3)	VARCHAR2(3) NOT NULL	Currency Code - Bal Amount
8	ACCOUNTING_DT	Date(10)	DATE NOT NULL	The accounting entry construction date for a given transaction (a generic field that crosses multiple
9	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.
10	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.
11	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""."
12	ORIG_ITEM_AMT	Signed Number(28,3)	DECIMAL(26,3) NOT NULL	Original Item Amount
13	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.
14	DISPUTE_DT	Date(10)	DATE	Specifies the date that an item was placed in dispute status.
15	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.
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	COLLECTOR	Character(8)	VARCHAR2(8) NOT NULL	Specifies the personnel code for the person who works with a customer to collect overdue payments.
18	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.
19	AR_SPECIALIST	Character(8)	VARCHAR2(8) NOT NULL	Accounts Recievable Specialist - person responsible for an action on an item.
20	TOTAL_ROW_COUNT	Number(8,0)	INTEGER NOT NULL	Total Row Count
21	ROW_ADDED_DTTM	DateTime(26)	TIMESTAMP	Added Date/Time
22	ROW_ADDED_OPRID	Character(30)	VARCHAR2(30) NOT NULL	Added By
23	ROW_LASTMANT_DTTM	DateTime(26)	TIMESTAMP	Last Modified Date/Time
24	ROW_LASTMANT_OPRID	Character(30)	VARCHAR2(30) NOT NULL	Last Maintained By
25	SYNCID	Number(10,0)	DECIMAL(10) NOT NULL	The Synchronization ID field stores a value generated by the sync processor. The value is used to identify the type of object that the sync processor is about to handle.
26	SYNCDTTM	DateTime(26)	TIMESTAMP	Synchronization Last Update Date Time