Results for “retn_billing_percentage”

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

Overview

PA_PROJ_RETN_BILL_RULES_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2, delivered as part of the PA (Projects) product family. The view exposes retention billing rules maintained for a project or top task. Retention billing represents amounts withheld by a customer from progress or milestone invoices and released later according to an agreed schedule; the rules stored here determine how that retention invoice is generated. Because the view is a thin projection over a single base table and includes the RETN_BILLING_CYCLE_ID column, it is the object most commonly queried when users search for retention billing cycle identifiers, either to validate configuration, to reconcile retention amounts held against a project, or to drive downstream integrations and custom reports.

Underlying Base Objects

The documented definition of the view is a direct SELECT from PA_PROJ_RETN_BILL_RULES, referenced in the ETRM metadata as PA_PROJ_RETN_BILL_RULES (SYNONYM). No joins, unions, or derived expressions are applied; every column exposed by the view maps one-to-one to a column of the base table. This has two practical consequences. First, the view is not an aggregation or denormalization layer, so query performance is effectively that of the underlying table, and filtering on indexed columns such as PROJECT_ID, TASK_ID, or CUSTOMER_ID is passed through directly. Second, the view cannot return rows that do not exist in the base table, and it carries no additional security predicates of its own. Row-level access is therefore governed by the base table's grants and any Oracle Projects security or MOAC (multi-org access control) behavior applied by the calling application rather than by the view definition.

Key Columns

• RETN_BILLING_RULE_ID — Primary identifier for an individual retention billing rule record.
• RETN_BILLING_CYCLE_ID — Identifier of the retention billing cycle associated with the rule; this is the column users search for when tracing which cycle governs release of retained amounts.
• PROJECT_ID, TASK_ID, CUSTOMER_ID — The project, top task, and customer to which the rule applies. Retention rules are captured at project or top task level.
• BILLING_METHOD_CODE — Code indicating the billing method under which the retention rule operates.
• TOTAL_RETENTION_AMOUNT — Total retention amount defined for the project or task.
• RETN_BILLING_PERCENTAGE and RETN_BILLING_AMOUNT — The percentage and corresponding amount used to compute retention billing.
• COMPLETED_PERCENTAGE — Completion percentage threshold relevant to when retention billing is triggered.
• CLIENT_EXTENSION_FLAG — Flag indicating whether the rule was created through client extension processing rather than standard setup.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — Standard audit columns recording who created and last modified each rule.

Common Use Cases and Queries

Typical usage includes confirming retention configuration before generating a retention invoice, reconciling total retention held against retention already billed for a project, and identifying all projects governed by a specific retention billing cycle. A representative query when searching on the billing cycle is:

• SELECT project_id, task_id, customer_id, retn_billing_rule_id, retn_billing_percentage, retn_billing_amount, total_retention_amount FROM apps.pa_proj_retn_bill_rules_v WHERE retn_billing_cycle_id = :p_cycle_id;
• SELECT billing_method_code, retn_billing_percentage, retn_billing_amount, completed_percentage FROM apps.pa_proj_retn_bill_rules_v WHERE project_id = :p_project_id;
• SELECT r.project_id, r.customer_id, r.total_retention_amount, r.last_update_date FROM apps.pa_proj_retn_bill_rules_v r WHERE r.client_extension_flag = 'Y';

Because the view is read-only in practice and mirrors the base table exactly, custom reports and interfaces should select only the columns required, and joins to project, task, and customer views should be performed explicitly on PROJECT_ID, TASK_ID, and CUSTOMER_ID to obtain descriptive names not present here.