Search Results gcs_build_fem_posting_pkg

Overview

The APPS.GCS_BUILD_FEM_POSTING_PKG package body is a component of the Oracle E-Business Suite Financial Consolidation Hub (FCH), a module within the ETRM (Enterprise Tax, Risk, and Management) family of applications. Its name reflects its core responsibility: building the posting structures and financial data required to consolidate subsidiary ledger balances into an enterprise-level Financial Enterprise Model (FEM). The package operates within the APPS schema and carries a status of VALID in the documented environment, indicating it compiles cleanly and its dependencies resolve at runtime.

The package forms part of the consolidation data-preparation layer. Before consolidated balances can be reported, posted, or transferred to downstream applications, the underlying accounting data must be gathered, normalized, and packaged into a posting representation. This package orchestrates that preparation logic, leveraging shared utilities rather than duplicating consolidation algorithms. It is tightly coupled to the consolidation framework, as evidenced by its references to GCS_DYNAMIC_UTIL_PKG and GCS_UTILITY_PKG, which supply generic consolidation services, and to FND_GLOBAL and FND_LOG for session context and diagnostic logging. The package is classified as an OTHER API type, meaning it is an internal engine rather than a published integration interface, and it is not referenced by any other database object, confirming its role as a back-end worker in the consolidation process.

Key Procedures and Functions

The documented metadata identifies a single procedural entry point, CREATE_PACKAGE. Within the constraints of the available documentation, only its name and structural placement can be confirmed.

• CREATE_PACKAGE — The sole documented procedure. By convention and naming, it assembles or constructs the posting package (the set of data elements and structures needed for FEM posting) from source consolidation data. It is the entry point through which callers trigger posting-build logic. Parameter lists are not documented in the ETRM metadata and are therefore not reproduced here.

No additional procedures or functions are registered in the documented metadata. Internal logic is expected to be delegated to the referenced utility packages, particularly GCS_DYNAMIC_UTIL_PKG and GCS_UTILITY_PKG, which the body depends upon for reusable consolidation functions. The presence of CREATE_PACKAGE as a public procedure, combined with the AD_DDL reference, suggests the package may support the dynamic creation or materialization of posting artifacts.

Tables Accessed

The package references a single documented table via APPS synonyms:

• AD_DDL — The Applications DDL (Data Definition Language) table from the Application Object Library. Access to this table indicates the package performs or validates dynamic DDL operations, such as creating or altering database objects required for the posting process. This is consistent with the name CREATE_PACKAGE, which may involve constructing dynamic SQL or DDL to build posting structures at runtime.

No other tables are documented as direct references. The broader data interaction is expected to occur indirectly through the utility packages (GCS_DYNAMIC_UTIL_PKG, GCS_UTILITY_PKG), which encapsulate the reads and writes against consolidation and ledger tables.

Usage Notes

GCS_BUILD_FEM_POSTING_PKG is not a public integration API and is not called by other database objects per the documented dependency analysis. It is therefore invoked internally by the Financial Consolidation Hub engine, most likely as part of a concurrent program or a scheduled consolidation process that prepares FEM posting data. Typical invocations occur during the consolidation cycle, after ledger balances are populated and before consolidated results are published or transferred.

Because the package depends on FND_GLOBAL, calls take place within an initialized Oracle Applications session where application ID, user ID, and responsibility context are established. The FND_LOG dependency indicates that runtime diagnostics are written to the FND logging framework, useful when troubleshooting consolidation posting failures. The GCS_BUILD_FEM_POSTING_PKG self-reference in the dependency list is a standard artifact of package body compilation.

In Oracle EBS 12.1.1 and 12.2.2, the package location and behavior are consistent, with the 12.2.x multitenant architecture requiring only that the APPS session context be valid. Custom code should not invoke this package directly; instead, consolidation procedures should be triggered through supported concurrent programs to preserve dependency and transaction integrity.