Search Results pa_proj_retn_bill_rules




Overview
Explore in AI Chat

Overview

The PA_PROJ_RETN_BILL_RULES table is a core data object within the Oracle E-Business Suite (EBS) Projects (PA) module, specifically for versions 12.1.1 and 12.2.2. It serves as the central repository for defining and storing retention billing rules at the project or task level. Retention billing is a critical financial practice in project-centric industries, where a percentage of an invoice is withheld by the customer until project milestones or contractual obligations are met. This table enables the systematic configuration of how these retention amounts are calculated, tracked, and eventually released for billing, forming an essential link between project execution, revenue recognition, and accounts receivable processes.

Key Information Stored

The table stores configuration rules that dictate retention billing behavior. While the full column list is not provided in the metadata, the documented foreign key relationships indicate the presence of critical columns that define the rule's scope and parameters. The PROJECT_ID and optional TASK_ID columns anchor the rule to a specific project or sub-task within the PA_PROJECTS_ALL and PA_TASKS tables, respectively. The CUSTOMER_ID links the rule to a specific customer account in HZ_CUST_ACCOUNTS, allowing for customer-specific retention terms. The RETN_BILLING_CYCLE_ID foreign key references PA_BILLING_CYCLES, defining the schedule or event that triggers the release of retained amounts. Other typical columns in such a table would include retention percentage rates, calculation bases (e.g., on revenue, invoice amount), retention ceilings, and effective date ranges.

Common Use Cases and Queries

Primary use cases involve configuring retention terms during project setup and generating reports for project financial analysis. Administrators use this data to ensure billing complies with contractual retention clauses. Common SQL queries include retrieving all retention rules for a specific project to review terms, or joining with customer and project tables for a consolidated view. A typical reporting query might be:

  • SELECT p.segment1 project_number, hca.account_number, prbr.* FROM pa_proj_retn_bill_rules prbr, pa_projects_all p, hz_cust_accounts hca WHERE prbr.project_id = p.project_id AND prbr.customer_id = hca.cust_account_id AND p.project_id = :p_project_id;

This data is also critical for the invoice generation engine within Projects Billing, which references these rules to calculate the correct billable and retainable amounts for each transaction.

Related Objects

The PA_PROJ_RETN_BILL_RULES table maintains defined foreign key relationships with several key EBS tables, as documented in the metadata:

  • PA_PROJECTS_ALL: Links via PA_PROJ_RETN_BILL_RULES.PROJECT_ID. This is the master table for all projects.
  • PA_TASKS: Links via PA_PROJ_RETN_BILL_RULES.TASK_ID. Allows retention rules to be defined at a granular task level within a project.
  • PA_BILLING_CYCLES: Links via PA_PROJ_RETN_BILL_RULES.RETN_BILLING_CYCLE_ID. Defines the cycle (e.g., monthly, upon completion) for releasing retained funds.
  • HZ_CUST_ACCOUNTS: Links via PA_PROJ_RETN_BILL_RULES.CUSTOMER_ID. References the Trading Community Architecture (TCA) customer master.

These relationships ensure data integrity and enable comprehensive joins for reporting and process execution within the integrated EBS framework.