AR_SRCH_ACT_VW (SQL View)	Index Back
Customer Item Activity

AR_SRCH_ACT_VW

(SQL View)

Customer Item Activity

SELECT B.SETID , A.BUSINESS_UNIT , A.CUST_ID , C.NAME1 , A.ITEM , A.ITEM_LINE , A.ITEM_SEQ_NUM , A.ENTRY_TYPE , A.ENTRY_REASON , A.ENTRY_AMT , A.ENTRY_EVENT , A.ACCOUNTING_DT , A.ASOF_DT , A.SUBCUST_QUAL1 , A.SUBCUST_QUAL2 , A.ENTRY_CURRENCY , A.ENTRY_AMT_BASE , A.CURRENCY_CD , A.ENTRY_USE_ID , A.CR_ANALYST , A.SALES_PERSON , A.COLLECTOR , I.BAL_CURRENCY , I.BAL_AMT_BASE , I.CURRENCY_CD , I.DISPUTE_STATUS , I.DISPUTE_AMOUNT , (CASE WHEN D.DESCR IS NOT NULL THEN D.DESCR ELSE M.MESSAGE_TEXT END) , I.DUE_DT , I.ITEM_STATUS , C.CUST_STATUS , (CASE WHEN (I.DEDUCTION_STATUS <> ' ' OR A.ENTRY_USE_ID = 'WS-08' OR A.ENTRY_USE_ID = 'DM-06') THEN %Abs(A.ENTRY_AMT_BASE) ELSE 0 END) AS DEDUCT_AMT , (CASE A.ENTRY_USE_ID WHEN 'WS-01' THEN %Abs(A.ENTRY_AMT_BASE) WHEN 'DM-01' THEN %Abs(A.ENTRY_AMT_BASE) ELSE 0 END) AS PAYMENT_BASE_AMT , (CASE A.ENTRY_USE_ID WHEN 'DM-07' THEN %Abs(A.ENTRY_AMT_BASE) WHEN 'DM-08' THEN %Abs(A.ENTRY_AMT_BASE) WHEN 'DM-09' THEN %Abs(A.ENTRY_AMT_BASE) WHEN 'MT-02' THEN %Abs(A.ENTRY_AMT_BASE) WHEN 'MT-03' THEN %Abs(A.ENTRY_AMT_BASE) WHEN 'MT-06' THEN %Abs(A.ENTRY_AMT_BASE) WHEN 'MT-07' THEN %Abs(A.ENTRY_AMT_BASE) WHEN 'WS-09' THEN %Abs(A.ENTRY_AMT_BASE) WHEN 'WS-10' THEN %Abs(A.ENTRY_AMT_BASE) WHEN 'WS-11' THEN %Abs(A.ENTRY_AMT_BASE) ELSE 0 END) AS WO_AMT_BASE , R.RISK_SCORE , (CASE WHEN I.DUE_DT < %CurrentDateIn AND A.ENTRY_USE_ID = 'IT-01' OR A.ENTRY_USE_ID = 'IT-02' THEN I.BAL_AMT_BASE ELSE 0 END) AS OVERDUE_AMT , I.OPRID_LAST_UPDT , I.LAST_UPDATE_DTTM FROM PS_ITEM I LEFT OUTER JOIN PS_AR_DISPDESCR_VW D ON D.DISPUTE_STATUS = I.DISPUTE_STATUS , PS_ITEM_ACTIVITY A , PS_SET_CNTRL_REC B , PS_CUSTOMER C , PS_SET_CNTRL_REC S , PS_CUST_CREDIT R , PSMSGCATDEFN M 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 AND B.SETCNTRLVALUE = I.BUSINESS_UNIT AND B.RECNAME = 'CUSTOMER' AND B.SETID = C.SETID AND I.CUST_ID = C.CUST_ID AND M.MESSAGE_SET_NBR = 18130 AND M.MESSAGE_NBR = 18001 AND S.SETCNTRLVALUE = I.BUSINESS_UNIT AND S.RECNAME = 'CUST_CREDIT' AND S.SETID = R.SETID AND I.CUST_ID = R.CUST_ID

Parent record: ITEM

# 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: BUS_UNIT_TBL_FS

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 NAME1 Character(40) VARCHAR2(40) NOT NULL Name 1

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

6 ITEM_LINE Number(6,0) INTEGER NOT NULL Item Line

7 ITEM_SEQ_NUM Number(3,0) SMALLINT NOT NULL Item Sequence Number

8 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.
Prompt Table: ENTRY_TYPE_TBL

9 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""."
Prompt Table: ENTRY_REASN_TBL

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

11 ENTRY_EVENT Character(10) VARCHAR2(10) NOT NULL Entry Event

12 ACCOUNTING_DT Date(10) DATE NOT NULL 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 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.

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

16 ENTRY_CURRENCY Character(3) VARCHAR2(3) NOT NULL Specifies the currency associated with the monetary amount of a pending item.

17 ENTRY_AMT_BASE Signed Number(28,3) DECIMAL(26,3) NOT NULL Represents the monetary amount of a pending item transaction such as invoice or credit memo in the base currency of the business unit.

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

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

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

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

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

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

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

25 BASE_CURRENCY Character(3) VARCHAR2(3) NOT NULL "Specifies the primary currency for a general ledger business unit, and is sometimes referred to as the ""book"" currency. Each business unit has one base currency. which is usually, but not always, the local currency for the organization. Journal entries are posted to a business unit in its base currency. "

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

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

28 AR_DESCR Character(30) VARCHAR2(30) NOT NULL Description

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

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

31 CUST_STATUS Character(1) VARCHAR2(1) NOT NULL Customer Status
A=Active
I=Inactive
T=Template

32 DEDUCT_AMT Signed Number(28,3) DECIMAL(26,3) NOT NULL Deduct Amount

33 PAYMENT_BASE_AMT Signed Number(28,3) DECIMAL(26,3) NOT NULL Represents the payment amount in the base currency of the business unit.

34 WO_AMT_BASE Signed Number(28,3) DECIMAL(26,3) NOT NULL Write Off Amt Base

35 RISK_SCORE Number(3,0) SMALLINT NOT NULL Risk Score used in Receivables Collections Workbench

36 OVERDUE_AMT Signed Number(28,3) DECIMAL(26,3) NOT NULL Overdue Amount

37 OPRID_LAST_UPDT Character(30) VARCHAR2(30) NOT NULL Last User to Update

38 LAST_UPDATE_DTTM DateTime(26) TIMESTAMP Specifies the date and time of the last update to an entry. This field is maintained by PeopleSoft and is used in a variety of contexts.

#	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: BUS_UNIT_TBL_FS
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	NAME1	Character(40)	VARCHAR2(40) NOT NULL	Name 1
5	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.
6	ITEM_LINE	Number(6,0)	INTEGER NOT NULL	Item Line
7	ITEM_SEQ_NUM	Number(3,0)	SMALLINT NOT NULL	Item Sequence Number
8	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. Prompt Table: ENTRY_TYPE_TBL
9	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""." Prompt Table: ENTRY_REASN_TBL
10	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.
11	ENTRY_EVENT	Character(10)	VARCHAR2(10) NOT NULL	Entry Event
12	ACCOUNTING_DT	Date(10)	DATE NOT NULL	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	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.
15	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.
16	ENTRY_CURRENCY	Character(3)	VARCHAR2(3) NOT NULL	Specifies the currency associated with the monetary amount of a pending item.
17	ENTRY_AMT_BASE	Signed Number(28,3)	DECIMAL(26,3) NOT NULL	Represents the monetary amount of a pending item transaction such as invoice or credit memo in the base currency of the business unit.
18	CURRENCY_CD	Character(3)	VARCHAR2(3) NOT NULL	Currency Code
19	ENTRY_USE_ID	Character(5)	VARCHAR2(5) NOT NULL	Specifies the System Function or type of processing associated with an entry type.
20	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.
21	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.
22	COLLECTOR	Character(8)	VARCHAR2(8) NOT NULL	Specifies the personnel code for the person who works with a customer to collect overdue payments.
23	BAL_CURRENCY	Character(3)	VARCHAR2(3) NOT NULL	Currency Code - Bal Amount
24	BAL_AMT_BASE	Signed Number(28,3)	DECIMAL(26,3) NOT NULL	Balance - Base Currency
25	BASE_CURRENCY	Character(3)	VARCHAR2(3) NOT NULL	"Specifies the primary currency for a general ledger business unit, and is sometimes referred to as the ""book"" currency. Each business unit has one base currency. which is usually, but not always, the local currency for the organization. Journal entries are posted to a business unit in its base currency. "
26	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.
27	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.
28	AR_DESCR	Character(30)	VARCHAR2(30) NOT NULL	Description
29	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.
30	ITEM_STATUS	Character(1)	VARCHAR2(1) NOT NULL	Item Status C=Closed O=Open
31	CUST_STATUS	Character(1)	VARCHAR2(1) NOT NULL	Customer Status A=Active I=Inactive T=Template
32	DEDUCT_AMT	Signed Number(28,3)	DECIMAL(26,3) NOT NULL	Deduct Amount
33	PAYMENT_BASE_AMT	Signed Number(28,3)	DECIMAL(26,3) NOT NULL	Represents the payment amount in the base currency of the business unit.
34	WO_AMT_BASE	Signed Number(28,3)	DECIMAL(26,3) NOT NULL	Write Off Amt Base
35	RISK_SCORE	Number(3,0)	SMALLINT NOT NULL	Risk Score used in Receivables Collections Workbench
36	OVERDUE_AMT	Signed Number(28,3)	DECIMAL(26,3) NOT NULL	Overdue Amount
37	OPRID_LAST_UPDT	Character(30)	VARCHAR2(30) NOT NULL	Last User to Update
38	LAST_UPDATE_DTTM	DateTime(26)	TIMESTAMP	Specifies the date and time of the last update to an entry. This field is maintained by PeopleSoft and is used in a variety of contexts.