C360_ITACT_VW(SQL View) |
Index Back |
|---|---|
Item Activity |
| SELECT A.cust_id , A.business_unit , A.item , A.item_line , A.item_seq_num , A.post_dt , A.CR_ANALYST , A.COLLECTOR , A.SALES_PERSON , A.ENTRY_TYPE , A.ENTRY_REASON , CASE WHEN A.ENTRY_USE_ID = 'FC-01' THEN A.ENTRY_AMT ELSE 0 END AS OVERDUE_AMT , CASE A.ENTRY_USE_ID WHEN 'WS-09' THEN A.ENTRY_AMT WHEN 'MT-03' THEN A.ENTRY_AMT WHEN 'MT-02' THEN A.ENTRY_AMT ELSE 0 END AS ACV_WRITEOFF , A.ENTRY_CURRENCY , A.ENTRY_USE_ID , A.ENTRY_AMT , A.SUBCUST_QUAL1 , A.SUBCUST_QUAL2 , A.ACCOUNTING_DT , %Sql(EOEW_FUNCLIB_DATE_MONTH_UPD, A.post_dt) , %Sql(EOEW_FUNCLIB_DATE_YEAR_UPD, A.post_dt) , %Sql(C360_FUNCLIB_DATE_YYYYMM, A.post_dt) FROM PS_ITEM_ACTIVITY A |
| # | PeopleSoft Field Name | PeopleSoft Field Type | Database Column Type | Description |
|---|---|---|---|---|
| 1 |  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_SRCH_VW |
| 2 | BUSINESS_UNIT |
Character(5) | VARCHAR2(5) NOT NULL |
Business Unit
Prompt Table: SP_BUARDS_NONVW |
| 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 | POST_DT | Date(10) | DATE | The Date a transaction was Posted. |
| 7 | 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. |
| 8 | COLLECTOR | Character(8) | VARCHAR2(8) NOT NULL | Specifies the personnel code for the person who works with a customer to collect overdue payments. |
| 9 | 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. |
| 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 | OVERDUE_AMT | Signed Number(28,3) | DECIMAL(26,3) NOT NULL | Overdue Amount |
| 13 | ACV_WRITEOFF | Signed Number(28,3) | DECIMAL(26,3) NOT NULL | Write Off |
| 14 | CURRENCY_CD | Character(3) | VARCHAR2(3) NOT NULL | Currency Code |
| 15 | ENTRY_USE_ID | Character(5) | VARCHAR2(5) NOT NULL | Specifies the System Function or type of processing associated with an entry type. |
| 16 | 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. |
| 17 | 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. |
| 18 | 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. |
| 19 | ACCOUNTING_DT | Date(10) | DATE | The accounting entry construction date for a given transaction (a generic field that crosses multiple |
| 20 | C360_POS_MTH | Character(2) | VARCHAR2(2) NOT NULL |
Posted Month
01=01-January 02=02-February 03=03-March 04=04-April 05=05-May 06=06-June 07=07-July 08=08-August 09=09-September 10=10-October 11=11-November 12=12-December |
| 21 | C360_POS_YEAR | Character(4) | VARCHAR2(4) NOT NULL | Posted Year |
| 22 | C360_POS_PERIOD | Character(8) | VARCHAR2(8) NOT NULL | Period |