Search Results bill_postal_code

Overview

PAFV_CUSTOMERS is an APPS-owned, read-only view in the Oracle E-Business Suite Projects (PA) module that presents customer information associated with projects. It is available in both EBS 12.1.1 and 12.2.2 and exposes data drawn from project-customer relationships combined with Oracle Trading Community Architecture (TCA) party and location records. The view is not a transactional entity; rather, it is a denormalized reporting and integration surface that joins a project to its billing customers and resolves both bill-to and ship-to address details into flat, query-friendly columns.

The view carries a status of VALID and is defined WITH READ ONLY, meaning it cannot be used for DML. Its definition also embeds a security predicate (_SEC:PPA.ORG_ID), so access is filtered by the operating unit context of the querying user through Oracle's Multi-Org security. This makes it suitable for secure reporting, concurrent program data sources, and integration extracts across multiple organizations.

Underlying Base Objects

The view is defined over seven documented base objects, all referenced through APPS synonyms:

• PA_PROJECTS_ALL — the project master; supplies PROJECT_ID, NAME (project name), and SEGMENT1 (project number).
• PA_PROJECT_CUSTOMERS — the intersection of projects and customers, holding the customer relationship, bill split, and the bill-to and ship-to address identifiers.
• HZ_CUST_ACCOUNTS — TCA customer accounts; links CUSTOMER_ID to the owning party.
• HZ_PARTIES — the party master; provides the customer/party name.
• HZ_CUST_ACCT_SITES_ALL and HZ_PARTY_SITES — account-site and party-site assignments that bridge account addresses to physical locations.
• HZ_LOCATIONS — the physical address records supplying address lines, city, state, and postal code.

The joins between PA_PROJECT_CUSTOMERS and the TCA site/location tables are outer joins (marked with (+)), so projects or customer relationships lacking a resolvable ship-to or bill-to address are still returned, with address columns null.

Key Columns

• PROJECT_ID, PROJECT_NAME, PROJECT_NUMBER — project identity, sourced from PA_PROJECTS_ALL.
• CUSTOMER_ID, CUSTOMER_NAME — the customer account identifier and the party name.
• SHIP_TO_ADDRESS_ID, SHIP_ADDRESS1–SHIP_ADDRESS4, SHIP_CITY, SHIP_STATE, SHIP_POSTAL_CODE — the ship-to address resolved from HZ_LOCATIONS.
• BILL_TO_ADDRESS_ID, BILL_ADDRESS1–BILL_ADDRESS4, BILL_CITY, BILL_STATE, BILL_POSTAL_CODE — the bill-to address.
• CUSTOMER_BILL_SPLIT — the proportion of billing allocated to the customer.
• Attribute columns — audit fields LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, plus a lookups-based relationship meaning.

The column SHIP_POSTAL_CODE, the focus of the originating search, is the postal code of the customer ship-to address, sourced from HZ_LOCATIONS.POSTAL_CODE via the ship-to site join chain.

Common Use Cases and Queries

Typical uses include project-to-customer reporting, address verification for billing or delivery, and data extracts into external systems. The view is commonly filtered by project number, customer name, or postal code.

• Find customers by ship-to postal code:
  SELECT project_number, project_name, customer_name, ship_city, ship_state, ship_postal_code
FROM apps.pafv_customers
WHERE ship_postal_code = '&postal_code';
• List all ship-to and bill-to addresses for a project:
  SELECT project_number, customer_name, ship_postal_code, bill_postal_code
FROM apps.pafv_customers
WHERE project_number = '&project_number';
• Identify projects missing a ship-to postal code (a common data-cleansing check) by selecting rows where SHIP_POSTAL_CODE IS NULL.

Because the view enforces read-only access and Multi-Org security, queries automatically respect the caller's operating unit context.