Search Results p_from_period

Overview

FEM_INTG_BAL_RULE_ENG_PKG is the balances rule processing engine within the Oracle E-Business Suite Financial Enterprise Performance Management (FEM) integration layer, which supports Enterprise Performance Foundation and the transfer of General Ledger balances into the FEM/OGL integration schema. The package encapsulates the runtime logic required to execute a balances rule version, extracting balance data from the source ledger for a specified accounting period range and staging it for downstream processing and analysis.

The header comment identifies the package as the "main routine of the FEM-OGL Integration Balances Rule Processing Engine program." It was created on 11-12-2004 by L. Poon and carries the source control identifier fem_intg_bal_eng.pls 120.0. In EBS 12.1.1 and 12.2.2 the package is owned by APPS and classified as OTHER in the ETRM repository.

Key Procedures and Functions

The package exposes a single documented public procedure, MAIN. It carries no package-level state and is designed to be invoked as the entry point of a concurrent program.

• MAIN — The documented driver routine of the balances rule processing engine. It accepts concurrent manager output parameters (x_errbuf, x_retcode) along with the balances rule version to be executed (p_bal_rule_obj_def_id), the chart of accounts identifier for the ledger (p_coa_id), the first period from which balances will be loaded (p_from_period), the last period from which balances will be loaded (p_to_period), the effective date used to calculate average balances (p_effective_date), and the low and high balancing segment value range (p_bsv_range_low, p_bsv_range_high).

The parameter p_from_period is the opening boundary of the period range requested by the user; together with p_to_period it defines the window of balances selected for loading. Callers submitting the "FEM-OGL Integration Balances Rule Processing Engine" concurrent program supply these values through the concurrent program parameter form; the period values must be expressed in the format expected by the program (typically the period name as defined in the ledger calendar, or its internal numeric representation as accepted by the rule engine).

Tables Accessed

The documented table references, resolved through APPS synonyms, indicate the package both stages data and reads integration configuration and status:

• FEM_BAL_POST_INTERIM_GT — interim global temporary staging table that holds balances prepared for posting by the rule engine during a run.
• FEM_INTG_DELTA_LOADS — tracks delta or incremental load activity for integration processing.
• FEM_INTG_EXEC_PARAMS_GT — global temporary table holding execution parameters for the current run, populated from the concurrent program arguments such as the period range.
• FEM_DATASETS_B / FEM_DATASETS_TL — dataset definition base and translated tables, used to resolve the dataset associated with a balances rule.
• FEM_DIMENSIONS_TL — translated dimension metadata used to resolve dimension members referenced by the rule.
• FND_NEW_MESSAGES — Oracle Application Object Library message table, used to return logged messages and error text to the concurrent manager.
• DUAL and PLITBLM — standard single-row query source and PL/SQL index-by table helper, used internally for utility operations.

Usage Notes

FEM_INTG_BAL_RULE_ENG_PKG.MAIN is normally invoked through the Oracle Concurrent Manager as the executable behind the balances rule processing engine concurrent program; the concurrent program definition supplies values for the rule version, chart of accounts, period range, effective date, and balancing segment range. Direct invocation from custom PL/SQL is possible where a process needs to drive a balances load programmatically, but the caller must honor the concurrent manager output parameter convention and commit or roll back the transaction appropriately.

The metadata records that the package is referenced by one other package, which suggests it may also be called indirectly from a higher-level FEM integration orchestration package rather than solely from the concurrent program form. When diagnosing issues, the p_from_period and p_to_period parameters are the first values to verify: an incorrect or reversed period range will result in no balances being selected, while an overly broad range increases runtime and the volume of rows written to FEM_BAL_POST_INTERIM_GT.