Search Results project_relationship_m




Overview
Explore in AI Chat

Overview

APPS.PA_CUSTOMER_RELATIONSHIPS_V is a supplementary Oracle EBS view owned by the APPS schema and registered under FND Design Data as PA.PA_CUSTOMER_RELATIONSHIPS_V. In Oracle EBS 12.1.1 and 12.2.2, it belongs to the Projects (PA) module and exposes the set of customer relationship codes and their translated meanings that govern how a customer is associated with a project. The view is a lookup-backed reference view: it presents a denormalized, form-friendly list of project relationship codes, their display meanings, descriptions, and effective date ranges.

Its documented role in Oracle EBS is as a supplementary view used to simplify forms coding. Oracle explicitly cautions that this view is not intended for direct querying or data manipulation by customers and that its structure may change dramatically in subsequent minor or major releases. Consequently, it should be treated as a reference and reading aid rather than as a stable integration interface. For reporting purposes it is best used to resolve relationship codes to their meanings when analyzing project-customer assignment data, or as a template for identifying the authoritative lookup source.

Underlying Base Objects

The only documented referenced base object is PA_LOOKUPS, itself a view. PA_LOOKUPS resolves the PA lookup types that define project relationship semantics, supplying the relationship code, the meaning, the description, and the active date range. The view therefore functions as a filtered, presentation-oriented projection over the project relationship lookup type rather than over a transactional table.

Within the dependency graph, APPS.PA_CUSTOMER_RELATIONSHIPS_V is referenced by APPS.OKE_PROJECT_CUSTOMERS_V and APPS.PA_PROJECT_CUSTOMERS_V. This means the customer relationship view feeds the customer-facing project views used in project customer setup and in Oracle Contracts (OKE) project customer integration. Any change to the lookup definitions underlying this view propagates into those dependent views, so lookup maintenance affects project-customer reporting downstream.

Key Columns

  • PROJECT_RELATIONSHIP_CODE (VARCHAR2, 30) — The stored lookup code representing a customer's relationship to a project (for example, a bill-to or ship-to style relationship). This is the join key used against project customer assignment data.
  • PROJECT_RELATIONSHIP_M (VARCHAR2, 80) — The translated meaning of the lookup code, suitable for display in reports, forms, and LOVs. The trailing "_M" convention indicates a meaning column.
  • DESCRIPTION (VARCHAR2, 240) — The longer description maintained against the lookup entry, providing additional explanatory text.
  • START_DATE_ACTIVE (DATE) — The date from which the relationship code becomes active.
  • END_DATE_ACTIVE (DATE) — The date on which the relationship code ceases to be active; a null value generally denotes an open-ended, currently effective entry.

Common Use Cases and Queries

Typical usage includes resolving relationship codes to meanings in project customer reports, populating selection lists for project relationship filters, and validating the code values returned by PA_PROJECT_CUSTOMERS_V and OKE_PROJECT_CUSTOMERS_V. A simple and safe reproduction of the view definition is:

SELECT PROJECT_RELATIONSHIP_CODE,
       PROJECT_RELATIONSHIP_M,
       DESCRIPTION,
       START_DATE_ACTIVE,
       END_DATE_ACTIVE
FROM APPS.PA_CUSTOMER_RELATIONSHIPS_V;

To list only currently effective relationship codes, add a date filter such as WHERE TRUNC(SYSDATE) BETWEEN NVL(START_DATE_ACTIVE, TRUNC(SYSDATE)) AND NVL(END_DATE_ACTIVE, TRUNC(SYSDATE)). Because Oracle warns against customer reliance on this view, production reports should generally query the underlying lookup tables directly or use the view only for reference during development and diagnostics. When integrating, prefer the documented PA lookup definitions and standard project customer APIs rather than this supplementary view.