AR_DISP_FLU_VW (SQL View)	Index Back
Dispute Tile View View for dispute resolution

AR_DISP_FLU_VW

(SQL View)

Dispute Tile View

View for dispute resolution

SELECT DISTINCT S.OPRID , V.BUSINESS_UNIT , V.CUST_ID , V.ITEM , V.ITEM_LINE , M.SETID , CASE S.RESP_PART_OPT WHEN 'A' THEN V.AR_SPECIALIST WHEN 'B' THEN V.BROKER_ID WHEN 'R' THEN V.CR_ANALYST WHEN 'S' THEN V.SALES_PERSON ELSE V.COLLECTOR END , V.SUBCUST_QUAL1 , V.SUBCUST_QUAL2 , V.DISPUTE_STATUS , V.BAL_CURRENCY , V.ORIG_ITEM_AMT , V2.DISPUTE_AMOUNT , V.DISPUTE_DT , V.DUE_DT , %DateDiff(V.DUE_DT, W.CURRENT_DATE1) , V1.DISP_RESOLUTION_DT , %DateDiff(V2.DISPUTE_DT, V1.DISP_RESOLUTION_DT) , V.BAL_AMT_BASE , V.CURRENCY_CD , V.CONVERS_EXISTS , V.PYMNT_TERMS_CD , V.ENTRY_TYPE , V.ENTRY_REASON , V.COLLECTOR , V.SALES_PERSON , V.CR_ANALYST , V.AR_SPECIALIST , V.BROKER_ID FROM PS_ITEM_BASE_MVW V , PS_ITEM_ACT_MV_VW1 V1 , PS_ITEM_DISP_VW1 V2 , PS_OPI_SYSCFG_TBL1 W , PS_ARFO_PRF_DISP S , PS_AR_BUSET_MVW M WHERE M.SETCNTRLVALUE = V.BUSINESS_UNIT AND V.BUSINESS_UNIT = V1.BUSINESS_UNIT AND V.CUST_ID = V1.CUST_ID AND V.ITEM = V1.ITEM AND V.ITEM_LINE = V1.ITEM_LINE AND V.BUSINESS_UNIT = V2.BUSINESS_UNIT AND V.CUST_ID = V2.CUST_ID AND V.ITEM = V2.ITEM AND V.ITEM_LINE = V2.ITEM_LINE AND V1.BUSINESS_UNIT = V2.BUSINESS_UNIT AND V1.CUST_ID = V2.CUST_ID AND V1.ITEM = V2.ITEM AND V1.ITEM_LINE = V2.ITEM_LINE AND V.ITEM_STATUS = 'C' AND V.DISPUTE_DT IS NULL AND W.PRODUCT_OE = 'ALL' AND V1.DISP_RESOLUTION_DT BETWEEN S.DATE_FROM AND S.DATE_TO AND M.RECNAME IN ('AR_SPECIALIST','CR_ANALYST_TBL','TEAM_MEMBER_VW','COLLECTOR_TBL')

# PeopleSoft Field Name PeopleSoft Field Type Database Column Type Description

1 OPRID Character(30) VARCHAR2(30) NOT NULL A user's ID (see PSOPRDEFN).

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

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 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 SETID Character(5) VARCHAR2(5) NOT NULL SetID

7 RESP_PART Character(15) VARCHAR2(15) NOT NULL Responsible Party

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

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

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 BAL_CURRENCY Character(3) VARCHAR2(3) NOT NULL Currency Code - Bal Amount

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

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

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

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

16 DAYS_LATE Signed Number(7,0) DECIMAL(6) NOT NULL Days Late

17 DISP_RESOLUTION_DT Date(10) DATE Resolution Date

18 DISP_RESOLVE_DAYS Number(8,0) INTEGER NOT NULL Dispute resolution days

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

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

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

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

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

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

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

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

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

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

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

#	PeopleSoft Field Name	PeopleSoft Field Type	Database Column Type	Description
1	OPRID	Character(30)	VARCHAR2(30) NOT NULL	A user's ID (see PSOPRDEFN).
2	BUSINESS_UNIT	Character(5)	VARCHAR2(5) NOT NULL	Business Unit Prompt Table: SP_BUARDS_NONVW
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	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	SETID	Character(5)	VARCHAR2(5) NOT NULL	SetID
7	RESP_PART	Character(15)	VARCHAR2(15) NOT NULL	Responsible Party
8	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.
9	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.
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	BAL_CURRENCY	Character(3)	VARCHAR2(3) NOT NULL	Currency Code - Bal Amount
12	ORIG_ITEM_AMT	Signed Number(28,3)	DECIMAL(26,3) NOT NULL	Original Item Amount
13	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.
14	DISPUTE_DT	Date(10)	DATE	Specifies the date that an item was placed in dispute status.
15	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.
16	DAYS_LATE	Signed Number(7,0)	DECIMAL(6) NOT NULL	Days Late
17	DISP_RESOLUTION_DT	Date(10)	DATE	Resolution Date
18	DISP_RESOLVE_DAYS	Number(8,0)	INTEGER NOT NULL	Dispute resolution days
19	BAL_AMT_BASE	Signed Number(28,3)	DECIMAL(26,3) NOT NULL	Balance - Base Currency
20	CURRENCY_CD	Character(3)	VARCHAR2(3) NOT NULL	Currency Code
21	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 ."
22	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.
23	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.
24	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""."
25	COLLECTOR	Character(8)	VARCHAR2(8) NOT NULL	Specifies the personnel code for the person who works with a customer to collect overdue payments.
26	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.
27	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.
28	AR_SPECIALIST	Character(8)	VARCHAR2(8) NOT NULL	Accounts Recievable Specialist - person responsible for an action on an item.
29	BROKER_ID	Character(15)	VARCHAR2(15) NOT NULL	Broker ID