Search Results load_entities




Overview
Explore in AI Chat

Overview

GCS_ENTITIES_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that provides the procedural logic supporting Consolidation Hierarchies within the Financial Consolidation module. The $Header annotation in the package specification (gcsentts.pls 120.1, dated 30-Oct-2005) and the creation history entry credited to M Ward in March 2005 identify this as an older, stable component of the General Consolidation System (GCS) codebase. The package occupies a supporting role: it does not expose a public API classification beyond OTHER, and the documented metadata shows it is not referenced by any other package. Instead, it is invoked by the consolidation forms, concurrent programs, and internal loading routines that manage the relationship between consolidation entities and the cost centers or organizations to which they belong. Its central concern is the maintenance of the summary association records that tie an entity to its organization structure, together with the import of entity definitions from XML source files.

Key Procedures and Functions

The package specification documents three procedures, reflecting the limited scope of its responsibilities.

  • ADD_TO_SUMMARY_TABLE — The procedure most directly associated with the search term "add_to_summary_table." It accepts an entity identifier and inserts rows into the GCS_ENTITY_CCTR_ORGS table, populating the summary mapping for that entity. Because it operates on a single entity id, it is typically called iteratively or from a driver routine that iterates across a hierarchy. No output or error buffer parameters are declared for this procedure.
  • LOAD_ENTITIES — Loads the entity records listed in a character large object. It is driven by a file identifier referencing GCS_XML_FILES, and its signature includes the standard concurrent program error buffer and return code out parameters, indicating that it is designed to be called from a concurrent manager context rather than interactively.
  • UPDATE_ENTITY_ORGS — Refreshes the list of organizations associated with all entities. Like LOAD_ENTITIES, it declares the error buffer and return code parameters and therefore follows the concurrent program calling convention. It performs a bulk synchronization of entity-to-organization relationships rather than the single-entity insert performed by ADD_TO_SUMMARY_TABLE.

Tables Accessed

The accessed tables fall into three functional groups. The summary and mapping tables are GCS_ENTITY_CCTR_ORGS (the insert target of ADD_TO_SUMMARY_TABLE), GCS_ENTITY_ORGANIZATIONS, and GCS_ENTITIES_ATTR, which hold the entity-level descriptive and organizational attributes. The loading infrastructure is represented by GCS_XML_FILES, the source of entity definitions consumed by LOAD_ENTITIES, with DBMS_LOB used to read the stored CLOB. The package also consults Financial Consolidation engineering tables — FEM_CCTR_ORGS_ATTR, FEM_DIM_ATTRIBUTES_B, FEM_DIM_ATTR_VERSIONS_B, FEM_ENTITIES_ATTR, and FEM_ENTITIES_B — to resolve dimension and entity attribute values. Supporting lookups include FND_FLEX_VALUES_S for flex value validation, GL_SETS_OF_BOOKS_S for ledger context, GCS_LEX_MAP_RULE_SETS and GCS_ROLE_ENTITY_RELNS for ledger mapping and role assignments, and WF_LOCAL_ROLES for the workflow role repository.

Usage Notes

ADD_TO_SUMMARY_TABLE is normally invoked from consolidation setup forms or from custom PL/SQL when an entity's cost center or organization memberships must be reflected in the summary table. Because it has no error buffer signature, callers must handle exceptions themselves. LOAD_ENTITIES and UPDATE_ENTITY_ORGS, by contrast, carry the standard x_errbuf and x_retcode parameters and are intended to be registered as concurrent programs, allowing an administrator to submit the entity load or organization refresh as a background request. When extending or debugging consolidation behavior in EBS 12.1.1 or 12.2.2, developers should treat this package as a legacy, self-contained utility whose correctness depends on the integrity of the FEM and GCS attribute tables it reads.