Results for “bill_another_project_flag”

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

Overview

PA_PROJECT_CUSTOMERS is a transactional assignment table in the Oracle Projects (PA) module of Oracle E-Business Suite, holding the customer accounts associated with each project. A single project can be billed to or associated with multiple customers, and this table captures that many-to-many relationship together with billing defaults such as bill-to and ship-to addresses, invoice currency, exchange rate attributes, and cross-project billing controls. It is a core enabling object for project billing, invoicing, revenue generation, and customer-facing reporting within Oracle Projects.

Its heuristic Data Vault classification, mined from the foreign key structure, is link. This is a modeling suggestion rather than a physical design fact: the table resolves the relationship between two business entities, projects and customer accounts, and therefore behaves naturally as a link table. Because it also carries descriptive and transactional attributes, portions of the row resemble a satellite, but the primary role is associative.

Key Information Stored

The documented physical schema for 12.2.2 contains 24 columns in the PA schema. The most significant are listed below.

• PROJECT_ID — Identifier of the project; part of the composite primary key PA_PROJECT_CUSTOMERS_PK and the foreign key to PA_PROJECTS_ALL.
• CUSTOMER_ID — Identifier of the customer account; the second component of the composite primary key and the foreign key to HZ_CUST_ACCOUNTS and RA_CUSTOMERS.
• BILL_TO_ADDRESS_ID — Bill-to address for the customer on this project; references HZ_CUST_ACCT_SITES_ALL and RA_ADDRESSES_ALL.
• SHIP_TO_ADDRESS_ID — Ship-to address; references the same address tables as the bill-to column.
• BILL_TO_CUSTOMER_ID and SHIP_TO_CUSTOMER_ID — Customer identifiers used for bill-to and ship-to, allowing invoice and delivery parties to differ from the primary customer.
• PROJECT_RELATIONSHIP_CODE — Classifies the customer relationship to the project, supporting differentiated billing and reporting behavior.
• CUSTOMER_BILL_SPLIT — Controls how billing is split among multiple customers associated with the project.
• INV_CURRENCY_CODE, INV_RATE_TYPE, INV_RATE_DATE, and INV_EXCHANGE_RATE — Invoice currency and the exchange rate attributes used to convert project amounts into the billing currency.
• ALLOW_INV_USER_RATE_TYPE_FLAG — Determines whether the user may override the invoice rate type during invoicing.
• BILL_ANOTHER_PROJECT_FLAG — Indicates that the customer is billed through another project rather than the current one.
• PROJECT_PARTY_ID — Foreign key to PA_PROJECT_PARTIES, tying the customer to the project team or party structure.
• RECEIVER_TASK_ID, DEFAULT_TOP_TASK_CUST_FLAG, and RETENTION_LEVEL_CODE — Task association, default top task behavior for the customer, and retention level applied during billing.
• RECORD_VERSION_NUMBER — Optimistic locking and change-detection column, with the standard WHO audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) also present.

Uniqueness is enforced by the primary key and the unique index PA_PROJECT_CUSTOMERS_U1 on (PROJECT_ID, CUSTOMER_ID), which are the business-key candidates for identifying a row. No separate single-column surrogate key is documented; the composite PROJECT_ID and CUSTOMER_ID pair serves as the business key.

Common Use Cases and Queries

Typical uses include listing all customers for a project, generating billing and invoicing reports, validating that a customer exists before creating a project invoice, and reconciling project customer assignments against the receivables customer master.

A basic join returns the customer accounts for a project:

• SELECT ppc.PROJECT_ID, ppc.CUSTOMER_ID, ppc.PROJECT_RELATIONSHIP_CODE, ppc.INV_CURRENCY_CODE, ppc.BILL_TO_ADDRESS_ID FROM PA.PA_PROJECT_CUSTOMERS ppc WHERE ppc.PROJECT_ID = :project_id;

A reporting query links the project and customer masters:

• SELECT p.PROJECT_NUMBER, h.CUSTOMER_NUMBER, h.CUSTOMER_NAME, ppc.CUSTOMER_BILL_SPLIT, ppc.PROJECT_RELATIONSHIP_CODE FROM PA.PA_PROJECT_CUSTOMERS ppc JOIN PA.PA_PROJECTS_ALL p ON p.PROJECT_ID = ppc.PROJECT_ID JOIN HZ.HZ_CUST_ACCOUNTS h ON h.CUST_ACCOUNT_ID = ppc.CUSTOMER_ID;

Additional scenarios include checking multi-customer billing splits, identifying projects with cross-project billing enabled, and auditing invoice currency and rate settings for a portfolio of projects.

Related Objects

The most significant objects that this table references or depends on are:

• PA_PROJECTS_ALL — joined via PROJECT_ID = PA_PROJECT_CUSTOMERS.PROJECT_ID.
• HZ_CUST_ACCOUNTS — joined via CUSTOMER_ID = PA_PROJECT_CUSTOMERS.CUSTOMER_ID; the primary customer master in Release 12.
• HZ_CUST_ACCT_SITES_ALL — joined via BILL_TO_ADDRESS_ID and SHIP_TO_ADDRESS_ID.
• RA_CUSTOMERS — legacy customer master, joined via CUSTOMER_ID.
• RA_ADDRESSES_ALL — legacy address source, joined via BILL_TO_ADDRESS_ID and SHIP_TO_ADDRESS_ID.
• PA_PROJECT_PARTIES — joined via PROJECT_PARTY_ID = PA_PROJECT_CUSTOMERS.PROJECT_PARTY_ID.

Downstream billing processes and project invoice generation in Oracle Projects consume this table to determine who is billed, in which currency, and to which addresses.