Search Results gcs_fem_post

Overview

GCS_DYN_FEM_POSTING_PKG is a PL/SQL package in the APPS schema of Oracle E-Business Suite that supports the consolidation and financial reporting functionality of the General Ledger Consolidation (GCS) module, a component associated with Oracle Financial Consolidation Hub and Enterprise Performance Foundation (formerly Financial Enterprise Management, "FEM"). The package is responsible for dynamically posting consolidation balances from the GCS module into the FEM (Financial Enterprise Management) balances repository. It acts as a bridge between the consolidation engine's transactional data and the analytical balances tables consumed by the Enterprise Performance Foundation and Financial Statement Generator engines.

The package is classified as an internal utility API (API classification: OTHER) rather than a public application programming interface. It carries a VALID status in the ETRM documentation and is referenced by a single additional package, GCS_CONS_ENG_UTILITY_PKG, indicating it operates as a subordinate component of the consolidation engine. Its name — "DYN" for dynamic and "FEM_POSTING" — confirms its role in dynamically generating and executing SQL statements that post combined and consolidated balances based on runtime-defined consolidation hierarchies and accounting flexfield configurations.

Key Procedures and Functions

The ETRM metadata documents two procedures within this package:

• GCS_FEM_POST — Posts consolidated balances to the FEM balances repository. This procedure reads consolidation entry data, resolves the corresponding Entity Performance Foundation entity attributes and hierarchies, and inserts or merges the resulting balances into the FEM_BALANCES structure so they are available for reporting and analysis.
• GCS_FEM_DELETE — Removes previously posted FEM balances and contribution records for a given consolidation run or entity scope. This procedure supports the reversal, re-run, or reconciliation of posting activity, ensuring that stale data does not persist in FEM balance tables after changes to consolidation data.

The package utilizes DBMS_SQL and a PL/SQL index-by table (referenced as PLITBLM) to construct and execute dynamic SQL statements. This dynamic approach is necessary because consolidation hierarchies and account ranges vary by ledger and run. Parameter lists are not exposed in the available documentation; the procedures should be treated as internal and invoked only through the consolidation engine rather than directly by custom code.

Tables Accessed

The package reads and writes several categories of tables via APPS synonyms:

• GCS_ENTRY_HEADERS and GCS_ENTRY_LINES — consolidation entry transaction data, the source of posting amounts.
• GCS_CATEGORIES_B and GCS_HIERARCHIES_B — consolidation category and hierarchy definitions used to resolve the structure of the posting.
• GCS_CONS_ENG_RUN_DTLS — consolidation engine run details, providing the run context for each posting.
• GCS_FEM_POSTING_GT, GCS_FEM_BAL_S, and GCS_FEM_CONTRIBUTIONS_H — staging and work tables that hold balances and contribution history during processing.
• FEM_BALANCES and FEM_ENTITIES_ATTR — the target FEM balances repository and entity attribute definitions.
• DUAL and DBMS_SQL — supporting reads and dynamic SQL execution, with PLITBLM used as the dynamic SQL bind/statement table.

Usage Notes

GCS_DYN_FEM_POSTING_PKG is invoked indirectly by the Oracle Consolidation Engine, most commonly through the GCS_CONS_ENG_UTILITY_PKG package during consolidation posting, revalidation, or reversal concurrent program runs. It is not a form-level or user-facing API and should not be called directly from custom code. Because it is internal, its procedures may change without notice between releases. In a 12.1.1 or 12.2.2 environment, tuning or troubleshooting of consolidation posting performance should focus on FEM_BALANCES indexing and the volume of GCS_ENTRY_LINES data processed per run. GCS_DYN_FEM_POSTING_PKG references the following: SYS, STANDARD. Only documented dependencies should be relied upon when assessing impact of patching or customization.