Search Results bill_address2




Overview
Explore in AI Chat

Overview

APPS.PA_TASK_CUSTOMERS_V is a view in the Oracle E-Business Suite Projects (PA) schema that exposes customer and address information associated with project tasks. It is classified in the ETRM as an internal, unsupported object: Oracle Corporation does not support direct access to application data through this view except from standard Oracle Applications programs. Its FND Design Data identifier is PA.PA_TASK_CUSTOMERS_V, and its status is VALID in both EBS 12.1.1 and 12.2.2.

The defining characteristic of this view is that it denormalizes the relationship between tasks, project customers, and Trading Community Architecture (TCA) address data into a single flat resultset. Each row carries a project identifier, task identifier, customer identifiers, and formatted bill-to and ship-to address lines. The presence of the SHIP_ADDRESS1 through SHIP_ADDRESS4 columns is significant: this view is the principal PA-layer vehicle through which a task's ship-to address is surfaced without requiring the caller to join through HZ_LOCATIONS or HZ_PARTY_SITES directly. That explains why a search such as "ship_address1" resolves to this object.

Underlying Base Objects

ETRM documents the view as referencing the following base objects, all exposed as synonyms owned by APPS:

  • PA_PROJECT_CUSTOMERS — the primary Projects-side table associating customers with projects and supplying bill-to/ship-to customer and address references.
  • PA_TASKS — supplies TASK_ID and the linkage from the project to its tasks.
  • HZ_CUST_ACCOUNTS — customer account definition, providing customer name and number.
  • HZ_CUST_ACCT_SITES — the customer account site assignments used to resolve bill-to and ship-to sites.
  • HZ_PARTY_SITES — the party-site intersection records underlying address assignments.
  • HZ_LOCATIONS — the actual formatted address lines (address1 through address4).
  • HZ_PARTIES — party-level information backing the customer records.

The view is not referenced by any database object, confirming it is a terminal read-only interface intended for consumers rather than for further composition inside the schema.

Key Columns

The view exposes eighteen columns. The structural keys are PROJECT_ID and TASK_ID (both NUMBER(15)), which identify the project and task context for each row. CUSTOMER_ID, BILL_TO_CUSTOMER_ID, and SHIP_TO_CUSTOMER_ID identify the customer party and its bill-to and ship-to variants. CUSTOMER_NAME (VARCHAR2(50)) and CUSTOMER_NUMBER (VARCHAR2(30)) provide human-readable identification.

Address resolution is carried by BILL_TO_ADDRESS_ID and SHIP_TO_ADDRESS_ID, each paired with four descriptive columns. BILL_ADDRESS1 through BILL_ADDRESS3 and SHIP_ADDRESS1 through SHIP_ADDRESS3 are VARCHAR2(240); the fourth line in each group is VARCHAR2(489), reflecting the concatenated city/state/postal/country formatting used by HZ_LOCATIONS. SHIP_ADDRESS1 is the first line of the ship-to address and is the column most commonly targeted by ad hoc lookups.

Common Use Cases and Queries

The typical use case is a reporting or interface requirement to print or export the ship-to address for tasks under a given project without navigating the TCA model. A representative query is:

  • SELECT task_id, customer_name, ship_address1, ship_address2, ship_address3 FROM apps.pa_task_customers_v WHERE project_id = :p_project_id;
  • SELECT task_id, ship_to_customer_id, ship_address1 FROM apps.pa_task_customers_v WHERE ship_address1 IS NOT NULL; — used to find tasks with a populated ship-to line.
  • SELECT project_id, task_id, bill_address1, ship_address1 FROM apps.pa_task_customers_v WHERE customer_id = :p_customer_id ORDER BY project_id, task_id;

Because the object is flagged Oracle Internal Use Only, any use should be confined to controlled reporting contexts, and the supported path remains the standard Oracle Applications programs that consume this view.