Search Results hz_c




Overview
Explore in AI Chat

Overview

APPS.PABV_CUSTOMERS is a read-only Oracle EBS view in the Projects (PA) application that exposes the relationship between projects and their associated customers. It is one of several secured views (commonly suffixed with "BV" for "Business View") that Oracle Projects provides for reference and reporting against project customer assignments without exposing the underlying transactional tables directly. The view joins project-level customer records maintained in PA_PROJECT_CUSTOMERS to the Trading Community Architecture (TCA) customer model, resolving the customer account and party identifiers required for meaningful reporting.

The view is defined with a WITH READ ONLY clause, which means DML operations are not permitted against it. It therefore serves strictly as a query interface for reporting, custom concurrent programs, and integration extracts.

Underlying Base Objects

Per the ETRM 12.2.2 metadata, PABV_CUSTOMERS is defined over four referenced base objects, all of which are synonyms resolving to their respective underlying tables:

  • PA_PROJECT_CUSTOMERS — the primary transactional table storing the customer-to-project assignment, including bill split, bill-to and ship-to address references, and audit columns.
  • HZ_CUST_ACCOUNTS — the TCA customer account, joined on hz_c.cust_account_id = ppc.customer_id.
  • HZ_PARTIES — the TCA party master, joined on hz_c.party_id = hz_p.party_id.
  • PA_PROJECTS_ALL — the projects definition table, joined on ppc.project_id = ppa.project_id.

The view enforces a security predicate in its WHERE clause: '_SEC:PPA.ORG_ID' IS NOT NULL. This is a substituted token resolved at runtime by the Oracle Projects security framework to restrict rows to the operating units (org_id) the querying user is authorized to see.

Key Columns

The view exposes the following columns (as documented in the view text):

  • PROJECT_ID — from PA_PROJECTS_ALL; identifies the project to which the customer relationship applies.
  • CUSTOMER_ID — sourced from PA_PROJECT_CUSTOMERS.CUSTOMER_ID and matched to HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID; the TCA customer account identifier.
  • PROJECT_RELATIONSHIP_CODE (lookup display) — returned as the substituted literal '_LA:PROJECT_RELATIONSHIP_CODE:PA_LOOKUPS:CUSTOMER PROJECT RELATIONSHIP:MEANING', which the Oracle Projects framework resolves to the meaning of the project relationship lookup value at runtime.
  • CUSTOMER_BILL_SPLIT — from PA_PROJECT_CUSTOMERS; indicates whether billing is split across multiple customers for the project.
  • BILL_TO_ADDRESS_ID — the bill-to address reference for the customer on the project.
  • SHIP_TO_ADDRESS_ID — the ship-to address reference for the customer on the project.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — standard audit columns carried through from PA_PROJECT_CUSTOMERS.

Common Use Cases and Queries

Typical uses include identifying which customers are assigned to a project, extracting bill-to/ship-to defaults for invoicing integrations, and driving customer-based project reporting. The view is protected by the Projects security framework, so results are filtered automatically by the user's operating unit access.

Example query listing customers per project:

  • SELECT project_id, customer_id, customer_bill_split, bill_to_address_id, ship_to_address_id FROM apps.pabv_customers WHERE project_id = :p_project_id;

Example query joining to project details for reporting:

  • SELECT c.project_id, p.name, c.customer_id, c.customer_bill_split FROM apps.pabv_customers c, apps.pa_projects_all p WHERE c.project_id = p.project_id AND p.org_id = :p_org_id;

Because the view already joins HZ_CUST_ACCOUNTS and HZ_PARTIES, users searching on "hz_p" (HZ_PARTIES) will find the customer/party linkage resolved here, though additional party attributes (such as party name from HZ_PARTIES) are not projected as columns and must be joined explicitly if required.