Results for “icx_edm_customer_task_v”
22 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
ICX_EDM_CUSTOMER_TASK_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the ICX (Oracle iProcurement) product family. Its documented purpose is to provide a "Task Information Summary View by Customer," presenting task-level project data joined to the customer or customers associated with the underlying project. The view consolidates task attributes — task number, task name, description, task manager, start and completion dates, carrying-out organization, location, and project identifiers — into a single, denormalized presentation layer.
Because it spans Oracle Projects (PA), Oracle Human Resources (PER/HR), and Oracle Order Management (OE) objects, the view is typically consumed by reporting tools, iProcurement/EDM-related inquiries, and custom integrations that require a customer-centric slice of task information without writing the multi-table join themselves. In EBS 12.1.1 and 12.2.2, the definition is functionally identical; the view remains VALID in the APPS schema.
Underlying Base Objects
The view is a UNION of two SELECT statements built over the following base tables:
- PA_PROJECT_CUSTOMERS — associates customers with projects (first branch, non-outer join).
- PA_PROJECTS_ALL — project master data (project number, name, description).
- PA_TASKS — task master data including task ID, number, name, dates, manager person, and carrying-out organization.
- HR_ORGANIZATION_UNITS — resolves the carrying-out organization name.
- PER_PEOPLE_F — resolves the task manager full name (outer-joined in both branches).
- HR_LOCATIONS — resolves the location code (outer-joined via ORG.LOCATION_ID).
- SO_LINES and SO_HEADERS — order lines and their headers, providing an alternative path to customer and project context (second branch).
- PJM_SEIBAN_NUMBERS — supplies project number and name for the order-driven branch.
The UNION combines Projects-sourced task rows with Order Management-sourced task rows, so tasks may be reached either through the project-customer relationship or through sales order lines linked to a project and task.
Key Columns
The most relevant columns exposed are:
- TASK_ID, TASK_NUMBER, TASK_NAME — the task's primary key and descriptive identifiers.
- TASK_DESCRIPTION — task description text.
- TASK_MANAGER — full name from PER_PEOPLE_F.
- TASK_START_DATE, TASK_END_DATE — task dates (sourced from START_DATE and COMPLETION_DATE).
- TASK_ORGANIZATION — organization name from HR_ORGANIZATION_UNITS.
- TASK_ORGANIZATION_ID — the user-referenced column; maps to TASK.CARRYING_OUT_ORGANIZATION_ID, the organization responsible for carrying out the task.
- TASK_LOCATION, TASK_LOCATION_DESCRIPTION — location code and description.
- PROJECT_ID, PROJECT_NUMBER, PROJECT_NAME, PROJECT_DESCRIPTION — project context.
- CUSTOMER_ID — the customer associated with the project or order.
Common Use Cases and Queries
Typical scenarios include listing all tasks for a customer, identifying the carrying-out organization for a task, and reporting on tasks linked to sales orders. A representative query:
- SELECT task_id, task_number, task_name, task_organization_id, task_organization, project_number, customer_id FROM apps.icx_edm_customer_task_v WHERE task_organization_id = :org_id;
- SELECT customer_id, task_number, task_manager, task_start_date, task_end_date FROM apps.icx_edm_customer_task_v WHERE project_id = :project_id;
Because two branches feed the UNION, duplicate tasks may appear where both a project-customer and an order-line path exist; DISTINCT is applied only in the second branch, so callers should account for possible duplicates. The OUTER joins on PER_PEOPLE_F and HR_LOCATIONS mean manager and location values may be NULL, and consumers should handle that in filters.
-
Task Information Summary View by Customer
APPS.ICX_EDM_CUSTOMER_TASK_V·↳ HR_GENERAL·↳ HR_LOCATIONS·↳ HR_ORGANIZATION_UNITS·Explore ICX module →
-
Task Information Summary View by Customer
Not implemented in this database·Explore ICX module →
-
12.1.1 DBA Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
VIEW: APPS.SO_HEADERS 12.1.1
-
VIEW: APPS.SO_LINES 12.1.1
-
SYNONYM: APPS.PA_TASKS 12.1.1
-
VIEW: APPS.HR_LOCATIONS 12.1.1
-
VIEW: APPS.PER_PEOPLE_F 12.1.1
-
eTRM - OE Tables and Views 12.1.1
Temporary table
-
eTRM - ICX Tables and Views 12.1.1
-
12.1.1 DBA Data 12.1.1
-
eTRM - PER Tables and Views 12.1.1
Table to store NQF Training info for a person
-
eTRM - OE Tables and Views 12.1.1
Temporary table
-
eTRM - ICX Tables and Views 12.1.1
-
eTRM - PER Tables and Views 12.1.1
Table to store NQF Training info for a person