Results for “post_processing_flag”

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

Overview

PA_BILLING_EXTENSIONS is a reference and configuration table in the Oracle Projects (PA) module of Oracle E-Business Suite 12.1.1 and 12.2.2. It stores implementation-defined billing extension definitions — the registration records that describe custom billing logic invoked by the Oracle Projects billing engine, such as user-named procedures, event triggers, plan defaults, and processing flags. The table lives in the PA schema and is classified as VALID within ETRM documentation.

Billing extensions in Oracle Projects allow organizations to supplement standard invoice generation with bespoke calculations (for example, burdening, discounts, or special revenue recognition rules). Each row in PA_BILLING_EXTENSIONS defines one extension, its associated database package procedure, the circumstances under which it should be invoked, and default planning/event parameters that the billing engine should apply. Given its FK structure — the table references PA_EVENT_TYPES and PA_FIN_PLAN_TYPES_B, and is referenced by PA_BILLING_ASSIGNMENTS_ALL — a Data Vault classification heuristic suggests this is a satellite-leaning object, holding descriptive attributes associated with the billing extension business key rather than acting as a transactional hub or link.

Key Information Stored

The primary key is BILLING_EXTENSION_ID (PA_BILLING_EXTENSIONS_PK), a surrogate identifier. The unique index PA_BILLING_EXTENSIONS_U1 (BILLING_EXTENSION_ID, ZD_EDITION_NAME) supports multi-tenant/edition-aware access patterns in 12.2.2. The most significant columns include:

• NAME and DESCRIPTION — user-facing identification of the extension.
• PROCEDURE_NAME — the PL/SQL program unit invoked by the billing engine.
• CALLING_PROCESS — identifies which billing process calls the extension.
• PRE_PROCESSING_FLAG, POST_PROCESSING_FLAG, CALL_AFTER_REG_FLAG, CALL_AFTER_ADJ_FLAG — timing controls for invocation.
• AMOUNT_REQD_FLAG, PERCENTAGE_REQD_FLAG — indicate whether amount or percentage parameters are mandatory.
• PROJECT_SPECIFIC_FLAG, MARK_EXP_ITEMS_FLAG, TRX_INDEPENDENT_FLAG — behavioral switches.
• PROCESSING_ORDER — sequence in which extensions execute.
• START_DATE_ACTIVE / END_DATE_ACTIVE — effective dating.
• DEFAULT_EVENT_TYPE (FK to PA_EVENT_TYPES), DEFAULT_REV_PLAN_TYPE_ID and DEFAULT_COST_PLAN_TYPE_ID (FKs to PA_FIN_PLAN_TYPES_B) — default reference values.
• Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE) and ATTRIBUTE1–15 for descriptive flexibility.

Common Use Cases and Queries

Typical usages include auditing which billing extensions are active, reviewing invocation order, and tracing assignments between extensions and projects.

• List active extensions in execution sequence:
  SELECT billing_extension_id, name, procedure_name, processing_order FROM pa_billing_extensions WHERE TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, SYSDATE) ORDER BY processing_order;
• Find extensions by trigger behaviour:
  SELECT * FROM pa_billing_extensions WHERE pre_processing_flag = 'Y' AND call_after_reg_flag = 'Y';
• Join to plan types to display defaults:
  SELECT be.name, rpt.name rev_plan, cpt.name cost_plan FROM pa_billing_extensions be, pa_fin_plan_types_b rpt, pa_fin_plan_types_b cpt WHERE be.default_rev_plan_type_id = rpt.plan_type_id(+) AND be.default_cost_plan_type_id = cpt.plan_type_id(+);
• Show which project/billing assignments reference each extension via PA_BILLING_ASSIGNMENTS_ALL.BILLING_EXTENSION_ID.
• Reporting on extensions that require amount or percentage inputs, to validate downstream parameterization.

Related Objects

• PA_BILLING_ASSIGNMENTS_ALL — references PA_BILLING_EXTENSIONS.BILLING_EXTENSION_ID; links extensions to specific projects, tasks, or agreements.
• PA_EVENT_TYPES — source of DEFAULT_EVENT_TYPE values used as the default billing event.
• PA_FIN_PLAN_TYPES_B — referenced twice, supplying DEFAULT_REV_PLAN_TYPE_ID and DEFAULT_COST_PLAN_TYPE_ID defaults.
• PA_BILLING_EXTENSIONS_PK — primary key constraint over BILLING_EXTENSION_ID.
• PA_BILLING_EXTENSIONS_U1 — unique index combining BILLING_EXTENSION_ID and ZD_EDITION_NAME.
• Billing extension PL/SQL packages named in PROCEDURE_NAME — invoked at runtime by the Oracle Projects billing engine.

Together these objects form the integration surface through which custom billing logic is registered, defaulted, and applied during Oracle Projects invoice and revenue processing.