Results for “projfunc_currency_code”

50+ results




Overview
Explore in AI Chat

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

Overview

PA_BILLING_EXTN_PARAMS_V is an APPS-owned runtime view in the Oracle E-Business Suite Projects (PA) module, defined over billing assignment and billing extension data. According to the ETRM metadata, the view presents "events for a MCB for a specific bill assignment id for use with billing extensions." Its full description clarifies that it is "a runtime view for use in billing extensions that shows a single row with all the new conversion attributes." This makes it a specialized, developer-facing construct rather than a general-purpose reporting view. It is intended to be queried from within PL/SQL billing extension logic, where the billing engine has already established the current bill assignment context through PA_BILLING.GETBILLINGASSIGNMENTID. In both Oracle EBS 12.1.1 and 12.2.2 the object remains VALID and is deployed in the APPS schema, and its behavior is unchanged across those releases.

Underlying Base Objects

The documented base objects referenced by this view are the PA_BILLING package, PA_BILLING_ASSIGNMENTS, PA_BILLING_EXTENSIONS, and PA_PROJECTS_ALL. The view text is a three-branch UNION ALL construct. Each branch joins PA_BILLING_ASSIGNMENTS (aliased BE) to PA_BILLING_EXTENSIONS (aliased B) on BILLING_EXTENSION_ID, and each restrictively filters on the runtime value returned by PA_BILLING.GETBILLINGASSIGNMENTID. The first branch filters on BE.PROJECT_ID IS NOT NULL and draws currency, rate type, rate date, and exchange rate values from the assignment. The second branch filters on BE.TOP_TASK_ID IS NOT NULL. The third branch draws its rate and currency attributes from PA_PROJECTS_ALL (aliased P) instead of the assignment. All branches project B.DEFAULT_COST_PLAN_TYPE_ID and B.DEFAULT_REV_PLAN_TYPE_ID from the billing extensions definition. The dependency on PA_BILLING.GETBILLINGASSIGNMENTID means the view is context-sensitive: it returns meaningful data only while executing inside an active billing event.

Key Columns

Common Use Cases and Queries

The primary use case is reading conversion parameters inside a billing extension to determine how amounts should be converted and which revenue or cost plan type applies. A typical pattern selects the columns of interest for the current assignment:

SELECT billing_assignment_id, default_rev_plan_type_id, default_cost_plan_type_id, project_currency_code, project_exchange_rate FROM pa_billing_extn_params_v WHERE billing_assignment_id = :p_assignment_id;

Because the view itself already filters on the runtime assignment through PA_BILLING.GETBILLINGASSIGNMENTID, an explicit predicate is often redundant but is sometimes retained for clarity. Note that this view is not suitable for ad hoc reporting outside the billing engine context, since its WHERE clause depends on package state. For static reporting on billing extensions, query PA_BILLING_EXTENSIONS directly.