Search Results project_relationship_code

Overview

OKE_PROJECT_CUSTOMERS_V is a valid, APPS-owned database view in the OKE – Project Contracts module of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. It is documented in ETRM as the "View for table PA_PROJECT_CUSTOMERS," meaning its primary role is to expose customer-to-project relationships maintained by Oracle Projects and Project Contracts in a denormalized, report-ready form. While the underlying PA_PROJECT_CUSTOMERS table stores only identifiers and relationship codes, this view enriches each row with descriptive customer attributes and a decoded relationship meaning, making it directly usable in reporting, concurrent programs, and integration extracts without additional joins. Its most significant exposed attribute is CUSTOMER_BILL_SPLIT, which identifies the billing split configured for the customer on a given project — the field directly associated with the user search term "customer_bill_split."

Underlying Base Objects

Per the ETRM metadata, the view is defined over three referenced objects:

• PA_PROJECT_CUSTOMERS (referenced in ETRM 12.2.2 as a synonym) — the driving table, holding PROJECT_ID, CUSTOMER_ID, PROJECT_RELATIONSHIP_CODE, and CUSTOMER_BILL_SPLIT.
• PA_CUSTOMER_RELATIONSHIPS_V (VIEW) — aliased CR, supplying PROJECT_RELATIONSHIP_CODE and the decoded PROJECT_RELATIONSHIP_M (relationship meaning).
• RA_CUSTOMERS (aliased C; noted alongside PA_CUSTOMERS_V in the documented metadata) — supplying CUSTOMER_NAME, CUSTOMER_NUMBER, STATUS, and PARTY_ID.

The view text joins PA_PROJECT_CUSTOMERS to RA_CUSTOMERS on CUSTOMER_ID and to PA_CUSTOMER_RELATIONSHIPS_V on PROJECT_RELATIONSHIP_CODE. It also selects PC.ROWID as ROW_ID, a common Oracle Forms/BC4J pattern that supports updatable-view behavior. Because two of the three base objects are themselves views, the definition is layered: changes to PA_CUSTOMER_RELATIONSHIPS_V or PA_CUSTOMERS_V propagate directly into this view's output.

Key Columns

• ROW_ID — the ROWID of the PA_PROJECT_CUSTOMERS row; used for row identification and update targeting.
• PROJECT_ID — the project to which the customer relationship applies.
• CUSTOMER_ID — the RA_CUSTOMERS identifier of the related customer.
• CUSTOMER_NAME / CUSTOMER_NUMBER — descriptive customer attributes sourced from RA_CUSTOMERS.
• CUSTOMER_STATUS — status of the customer record (exposed from RA_CUSTOMERS.STATUS).
• PARTY_ID — the TCA party identifier for the customer, enabling joins to party-level data.
• PROJECT_RELATIONSHIP_CODE — the relationship role code (for example, bill-to or ship-to style roles) linking the customer to the project.
• PROJECT_RELATIONSHIP_M — the decoded meaning of the relationship code from PA_CUSTOMER_RELATIONSHIPS_V.
• CUSTOMER_BILL_SPLIT — the billing split value assigned for this customer on this project; relevant to revenue and billing allocation logic.

Common Use Cases and Queries

Typical uses include reporting on customers associated with projects, validating bill-split configuration, and feeding downstream billing or integration processes.

List all customers for a project:

SELECT project_id, customer_id, customer_name,
       project_relationship_m, customer_bill_split
FROM   apps.oke_project_customers_v
WHERE  project_id = :p_project_id;

Find customers with a non-null bill split:

SELECT project_id, customer_name, customer_number,
       project_relationship_code, customer_bill_split
FROM   apps.oke_project_customers_v
WHERE  customer_bill_split IS NOT NULL;

Retrieve the bill-to relationship for a project:

SELECT customer_name, party_id, customer_bill_split
FROM   apps.oke_project_customers_v
WHERE  project_id = :p_project_id
AND    project_relationship_code = :p_rel_code;

In each case, the view eliminates manual joins to RA_CUSTOMERS and the relationship view, providing a single, AMS-conformant source for project customer and bill-split reporting.