Search Results pa_customer_relationships_v




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PA_CUSTOMER_RELATIONSHIPS_V is an Oracle E-Business Suite (EBS) view owned by the APPS schema within the Projects (PA) product family. It is documented in ETRM as a VALID database object and is explicitly flagged with the description "10SC Only." This designation indicates that the object originated in the legacy Oracle Projects 10SC code line and is not intended for general functional use in a standard 12.1.1 or 12.2.2 implementation. Its role is that of a lookup-driven reference view: rather than presenting transactional customer-to-project relationship data, it exposes the seeded or user-defined values that define the allowed customer project relationship types. Because of the "10SC Only" restriction, it should be treated as a legacy compatibility artifact, retained to preserve backward compatibility for dependent customizations or upgrade scripts, not as a mainstream reporting surface. The view carries no joins to transactional tables and performs no data manipulation; it is a filtered projection of the PA_LOOKUPS view constrained to a single lookup type, making it inexpensive to query and safe to access in read-only contexts.

Underlying Base Objects

The view is defined over a single documented base object: PA_LOOKUPS, itself a view in the APPS schema. The defining query selects from PA_LOOKUPS using the alias L and filters on the condition that LOOKUP_TYPE equals 'CUSTOMER PROJECT RELATIONSHIP'. There are no additional joins, unions, or aggregations. Consequently, every row returned by PA_CUSTOMER_RELATIONSHIPS_V corresponds one-to-one with a row in PA_LOOKUPS whose lookup type is the customer project relationship set. Any maintenance performed on those lookup codes through the standard Oracle Projects lookup maintenance forms is immediately reflected when the view is queried. Because PA_LOOKUPS is the sole dependency, the view inherits its security posture, synonym resolution, and any grants applied to that underlying object within the APPS schema.

Key Columns

The view projects five columns drawn from PA_LOOKUPS. Each plays a distinct role in interpreting a relationship type:

  • PROJECT_RELATIONSHIP_CODE — the underlying lookup code, serving as the unique identifier for a customer project relationship type.
  • PROJECT_RELATIONSHIP_M — the user-facing meaning or display name associated with the code.
  • DESCRIPTION — additional descriptive text qualifying the relationship type.
  • START_DATE_ACTIVE — the date from which the lookup value becomes effective.
  • END_DATE_ACTIVE — the date on which the lookup value ceases to be effective.

Typical filtering applies the start and end dates against the current date to return only currently active relationship types.

Common Use Cases and Queries

Given the "10SC Only" limitation, the primary use cases are audit, migration verification, and validation of relationship lookup values before or after an upgrade. A common query retrieves all currently active relationship types:

  • SELECT project_relationship_code, project_relationship_m, description FROM pa_customer_relationships_v WHERE TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, TRUNC(SYSDATE));
  • SELECT project_relationship_code, project_relationship_m, start_date_active, end_date_active FROM pa_customer_relationships_v ORDER BY project_relationship_code;

These queries are useful when validating that a required relationship type exists and is effective, or when comparing lookup content between source and target environments. Because the view resolves entirely against lookup data, it should not be used to derive actual customer-to-project assignments; those are held in the Projects transactional model. Implementations should confirm the "10SC Only" flag against their release before relying on this view in new development.