Search Results bill_address4




Overview
Explore in AI Chat

Overview

PA_TASK_CUSTOMERS_V is a Projects (PA) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It provides a denormalized, reporting-friendly presentation of the relationship between project tasks, their associated customers, and the bill-to and ship-to addresses held in the Oracle Trading Community Architecture (TCA) model. Rather than forcing developers and report authors to join PA_PROJECT_CUSTOMERS, PA_TASKS, and the HZ_* tables themselves, the view encapsulates the required joins and exposes a flat structure of customer, task, and address attributes.

Its practical role is to support customer-facing project reporting — for example, task-level billing detail, customer contact listings, and address verification on project deliverables. Because the address lookups on the bill-to and ship-to paths are implemented as outer joins, the view returns one row per qualifying project/task/customer combination even where address data is incomplete.

Underlying Base Objects

Per the documented metadata, the view is defined over the following synonyms:

The HZ_* tables are joined twice, once on the bill-to path (aliased BA_*) and once on the ship-to path (aliased SA_*), which is why the view exposes parallel BILL_* and SHIP_* address columns. The two address chains are left-joined with the (+) operator, making them optional.

h4>Key Columns

Common Use Cases and Queries

Typical scenarios include task-level customer extracts for project billing, verification of bill-to/ship-to data before invoicing, and integration feeds to external systems requiring a single flat customer/address record.

Sample query retrieving customer and bill-to detail for a project:

  • SELECT project_id, task_id, customer_name, customer_number, bill_address1 FROM pa_task_customers_v WHERE project_id = :project_id;
  • SELECT customer_name, ship_address1, ship_address2 FROM pa_task_customers_v WHERE task_id = :task_id ORDER BY customer_name;

Because the view is read-only and based on TCA synonyms, use it for reporting and integration queries rather than as a DML target. Confirm that the caller has appropriate privileges on the HZ and PA objects before exposing it in custom reporting.