Search Results calc_driver_values

Overview

PFT_AR_ENGINE_PVT is a private PL/SQL package owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It forms part of the Profitability Foundation (PFT) engine that underpins Oracle's Enterprise Performance Foundation and related profitability management functionality. Its designation as a "PVT" package indicates that it is an internal, private implementation unit: it is not intended to be called directly by external application code, and its interfaces are expected to change without notice between releases.

The package serves as the accounts receivable (AR) rating engine within the profitability calculation framework. It applies activity rates to AR driver balances, translating source-system financial data into costing and profitability results. The engine builds upon the Foundation Engine Management (FEM) infrastructure, drawing on rule sets, hierarchies, dimension metadata, and object definitions to evaluate driver values and derive rated amounts. Although the documented metadata is limited, the naming convention and referenced objects confirm that PFT_AR_ENGINE_PVT is an execution-time component invoked by the FEM processing layer rather than a user-facing API.

Key Procedures and Functions

The ETRM metadata documents two procedures or functions within this package:

• ACT_RATE_REQUEST — The primary entry point for an accounts receivable rating request. It is responsible for orchestrating the rating run: accepting a request context (typically tied to an execution and rule set) and coordinating the retrieval of AR driver data and the application of activity rates so that driver balances can be converted into rated output. This procedure corresponds to the "act" action that triggers rating activity against the AR data set.
• CALC_DRIVER_VALUES — A supporting routine that calculates driver values, the quantitative measures against which activity rates are applied. It evaluates source data and dimension attributes to produce the driver quantities consumed by the rating process. This procedure ensures that AR balances are expressed in the correct unit of measure and at the correct level of the FEM dimension hierarchy before rates are applied.

No parameter lists are documented in the ETRM record, and none are asserted here. Both routines are treated as internal engine steps rather than published APIs.

Tables Accessed

The package reads and writes a defined set of tables, accessed through APPS synonyms. These fall into three functional groups.

• Profitability (PFT) tables: PFT_ACTIVITY_RATES holds the activity rate definitions applied during rating; PFT_AR_DRIVERS_T stores the AR driver transaction or staging data that the engine consumes and produces.
• Foundation Engine Management (FEM) tables: FEM_BALANCES, FEM_DIM_ATTRIBUTES_B, FEM_DIM_ATTR_VERSIONS_B, FEM_HIERARCHIES, FEM_OBJECT_CATALOG_B, FEM_OBJECT_DEFINITION_B, FEM_RULE_SETS, FEM_RULESET_PROCESS_DATA, FEM_SOURCE_SYSTEMS_B, FEM_DS_INPUT_OUTPUT_DEFS, FEM_PL_OBJECT_EXECUTIONS, and FEM_PL_TEMP_OBJECTS support the surrounding engine framework — dimension metadata, hierarchies, rule set definitions, data source definitions, execution tracking, and temporary working objects.
• Reference data: FND_LOOKUP_VALUES supplies lookup codes used for validation and configuration.

Together these tables allow the package to resolve the structure of the calculation, retrieve the relevant balances and drivers, and persist rated results and execution status.

Usage Notes

PFT_AR_ENGINE_PVT is an internal component. It is referenced by zero other packages according to the ETRM record, and it therefore should not be treated as a stable integration point. In practice, invocation occurs through the FEM profitability processing framework — typically from a concurrent program or an internal engine driver that registers an execution, reads rule set and object definitions, and then calls the AR rating logic. Direct calls from custom code are strongly discouraged: the package name carries the PVT designation precisely to signal that its signature and behavior may change across patches and upgrades. Developers integrating with profitability functionality should use the supported public APIs and concurrent programs instead, treating PFT_AR_ENGINE_PVT solely as a diagnostic and reference object when troubleshooting rating runs in 12.1.1 or 12.2.2.