Search Results method_value

Overview

APPS.PA_PROJ_RETN_BILL_VALUES_V is a reporting view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that exposes retention billing rules defined at the project, customer, and task level within Oracle Projects. Retention billing is the practice of withholding a percentage or fixed amount of a contract value until specified completion or acceptance milestones are met. This view consolidates the retention billing method configuration and its associated cycle or amount value into a single readable result set, joining the retention billing rule table to lookup meanings and optional task and billing cycle attributes.

The view is intended primarily for reporting, extracts, and downstream integration scenarios where a denormalized, human-readable representation of retention billing setup is required. Rather than querying PA_PROJ_RETN_BILL_RULES directly and resolving lookup codes manually, consumers can obtain the translated billing method meaning and the resolved method value in one step.

Underlying Base Objects

The view is defined over four documented base objects:

• PA_PROJ_RETN_BILL_RULES (synonym) — the primary transactional table holding retention billing rules, keyed by RETN_BILLING_RULE_ID and carrying PROJECT_ID, CUSTOMER_ID, TASK_ID, BILLING_METHOD_CODE, RETN_BILLING_CYCLE_ID, RETN_BILLING_PERCENTAGE, and RETN_BILLING_AMOUNT.
• PA_LOOKUPS (view) — provides the translated meaning for the RETN_BILLING_METHOD lookup type, matching LOOKUP_CODE to BILLING_METHOD_CODE.
• PA_TASKS (synonym) — supplies the optional TASK_NUMBER and TASK_NAME via an outer join on TASK_ID.
• PA_BILLING_CYCLES (synonym) — supplies BILLING_CYCLE_NAME for rules that reference a retention billing cycle, joined through an outer join on RETN_BILLING_CYCLE_ID.

The view is a UNION of two branches. The first branch addresses rules where RETN_BILLING_CYCLE_ID IS NULL and derives METHOD_VALUE from a DECODE over BILLING_METHOD_CODE (CLIENT_EXTENSION, PERCENT_COMPLETE, or TOTAL_RETENTION_AMOUNT). The second branch addresses rules where RETN_BILLING_CYCLE_ID IS NOT NULL and derives METHOD_VALUE from the billing cycle name.

Key Columns

• RETN_BILLING_RULE_ID — unique identifier of the retention billing rule.
• PROJECT_ID, CUSTOMER_ID, TASK_ID — the project, customer, and optional task context of the rule.
• TASK_NUMBER, TASK_NAME — descriptive task attributes, null when no task is associated.
• BILLING_METHOD_CODE — the raw lookup code for the retention billing method.
• BILLING_METHOD — the translated meaning from PA_LOOKUPS for lookup type RETN_BILLING_METHOD.
• METHOD_VALUE — the resolved rule value: for CLIENT_EXTENSION the client extension flag, for PERCENT_COMPLETE the completed percentage, for TOTAL_RETENTION_AMOUNT the total retention amount, or the billing cycle name when a cycle is referenced.
• RETN_BILLING_PERCENTAGE — the retention percentage applied.
• RETN_BILLING_AMOUNT — the retention amount applied.

Common Use Cases and Queries

Typical uses include retention billing configuration reports, reconciliation of withheld amounts, and integration feeds that must present billing method descriptions rather than codes. Because the view resolves lookup meanings and joins task descriptions, it is well suited to concurrent program extracts and BI Publisher data sources.

A representative query retrieving retention billing rules for a project:

• SELECT project_id, customer_id, task_number, billing_method, method_value, retn_billing_percentage, retn_billing_amount FROM apps.pa_proj_retn_bill_values_v WHERE project_id = :p_project_id;

A query filtering by billing method description:

• SELECT retn_billing_rule_id, billing_method_code, billing_method, method_value FROM apps.pa_proj_retn_bill_values_v WHERE billing_method = 'Percent Complete';

A query isolating rules that reference a billing cycle versus those that use a numeric method value:

• SELECT retn_billing_rule_id, billing_method, method_value FROM apps.pa_proj_retn_bill_values_v WHERE method_value IN (SELECT billing_cycle_name FROM apps.pa_billing_cycles);

Consumers should note the view is read-only and inherits security characteristics from its base objects; access is governed by the APPS schema and standard Oracle Projects security profiles.