Search Results update_ptd_balances

Overview

GCS_DATASUB_UTILITY_PKG is a data submission utility package in the Oracle E-Business Suite Financial Consolidation Hub (also referred to as Enterprise Performance Foundation / FEM) schema. In Oracle EBS 12.1.1 and 12.2.2, the package supports the loading, transformation, and validation of financial balances during the data submission process. It operates under the FEM data model, where balances are staged in interface tables and combined with dimension member definitions before being moved into the consolidation and analytics balances tables.

The package is classified as an OTHER API and carries the internal API identifier gcs.plsql.GCS_DATASUB_UTILITY_PKG. It provides the procedural logic used to compute and refresh period-to-date (PTD) and year-to-date (YTD) balance columns, and to validate dimension member references prior to committing data. The procedures leverage FND_LOG diagnostic logging (LEVEL_PROCEDURE and LEVEL_STATEMENT) and, in the case of the balance update routines, declare PRAGMA AUTONOMOUS_TRANSACTION so that balance maintenance work commits independently of the calling transaction.

Key Procedures and Functions

The ETRM metadata documents four procedures within the package body:

• UPDATE_YTD_BALANCES — Recalculates and stores year-to-date amounts on the balance interface table gcs_bal_interface_t. The documented source excerpt shows it updating the columns ytd_debit_balance_e, ytd_credit_balance_e, ytd_balance_e, and ytd_balance_f by aggregating source balances. It is an autonomous transaction procedure that accepts identifiers such as the load ID, source system code, dataset code, calendar period, ledger, currency type, and currency code to scope the refresh.
• UPDATE_PTD_BALANCES — Performs the analogous period-to-date refresh, recomputing PTD debit, credit, and net balance amounts for the same scoping parameters. This is the routine a user searching for "update_ptd_balance_sheet" is most likely targeting when PTD period accumulation is required.
• UPDATE_PTD_BALANCE_SHEET — Recalculates period-to-date balances specifically for balance sheet accounts (assets, liabilities, and equity), distinguishing them from the income statement / flow accounts handled by the general PTD procedure. The distinction supports the different accumulation behavior required when prior-period balances must carry forward.
• VALIDATE_DIMENSION_MEMBERS — Verifies that dimension member values submitted in the load map correctly to defined FEM dimension members and hierarchies, ensuring referential integrity before balances are consumed by consolidation and reporting processes.

Tables Accessed

The package reads and writes data defined through APPS synonyms in the FEM schema. Principal among these are FEM_BALANCES, which holds the consolidated balances, and the dimension definition tables used during validation: FEM_DIMENSIONS_TL (dimension translations), FEM_FIN_ELEMS_B (financial elements/accounts), FEM_ENTITIES_ATTR and FEM_CCTR_ORGS_B (entity and cost center organizations), FEM_CHANNELS_B, FEM_CUSTOMERS_B, FEM_PRODUCTS_B, FEM_PROJECTS_B, and FEM_LN_ITEMS_B/ATTR (line items). Attribute tables FEM_EXT_ACCT_TYPES_ATTR, FEM_LEDGERS_ATTR, and FEM_GLOBAL_VS_COMBO_DEFS supply account type, ledger, and combination definitions used to resolve and validate member combinations. The procedures also maintain the balance interface table gcs_bal_interface_t, the staging structure that feeds these definitions.

Usage Notes

GCS_DATASUB_UTILITY_PKG is not an end-user entry point. It is invoked internally by higher-level data submission and consolidation packages; the ETRM metadata indicates it is referenced by one other package. It may also be called by concurrent programs in Financial Consolidation Hub responsible for processing submitted balance data, and by custom PL/SQL extensions that stage data through the FEM interface tables. Because the balance update procedures run as autonomous transactions, calls should be scoped carefully with the load ID, source system, dataset, period, ledger, and currency context so that partial refreshes commit consistently. Diagnostic output is written to the FND_LOG facility, and logging levels should be set appropriately when troubleshooting PTD or YTD balance discrepancies.