Search Results eliminations_processor




Overview
Explore in AI Chat

Overview

APPS.GCS_CONS_ENG_UTILITY_PKG is the utility layer of the Global Consolidation System (GCS) consolidation engine in Oracle E-Business Suite. Its package body supplies the shared PL/SQL routines that drive consolidation processing: extracting consolidation and operating entity context from Oracle Workflow item attributes, invoking the category balance processor, deciding whether adjustments or translation are required, applying eliminations, testing category availability, and generating initializing journals. The package is classified under the generic (OTHER) API category, meaning it is intended primarily for internal use by the consolidation engine's Workflow-driven concurrent processes rather than as a published, supported integration API.

Because consolidation runs in Oracle EBS are orchestrated through Oracle Workflow, the package opens with get_cons_entity_wf_info, which reads item attributes such as consolidation hierarchy, consolidation entity, run identifier, calendar period, balance type, run detail identifier, process method, category counters, prior run name, translation entry identifier, and concurrent request identifier. This routine establishes the runtime context that every downstream procedure relies upon.

Key Procedures and Functions

  • EXECUTE_MODULE — The primary dispatcher. It selects and invokes the appropriate processing routine for a consolidation module based on the current run context, serving as the entry point referenced by other packages and workflow activities.
  • GET_CONS_ENTITY_WF_INFO — Populates the consolidation entity Workflow information record from item attributes, converting calendar period end dates and numeric attributes as required.
  • GET_OPER_ENTITY_WF_INFO — Equivalent retrieval routine for the operating entity side of a consolidation relationship.
  • BALANCES_PROCESSOR — Executes category balance processing for the entity and period in scope.
  • CHECK_ADJ_REQUIRED — Determines whether adjustment entries are required before a category can be processed or closed.
  • EXTRACT_MANUAL_ADJ — Extracts manual adjustment entries for processing within the consolidation engine.
  • CHECK_TRANSLATION_REQUIRED — Evaluates whether currency translation must run for the entity/category combination.
  • UPDATE_PROCESS_STATUS — Maintains run and run-detail status as processing progresses.
  • EXECUTE_TRANSLATION — Performs or triggers the translation step for the consolidation entity.
  • ELIMINATIONS_PROCESSOR — Applies elimination rules and relationships to produce elimination entries.
  • CATEGORY_EXISTS — Boolean-style test for whether a consolidation category is defined.
  • CHECK_MAX_CATEGORY — Validates category sequence limits during multi-category runs.
  • CREATE_INITIALIZING_JOURNAL — Creates the opening journal that seeds a consolidation category.
  • SUBMIT_XML_NTF_PROGRAM — Submits the XML notification concurrent program for run messaging.

Tables Accessed

The package reads and writes consolidation configuration, run, and results data. GCS_CONS_ENG_RUNS and GCS_CONS_ENG_RUN_DTLS hold run headers and detail rows whose status is maintained by UPDATE_PROCESS_STATUS. GCS_CONS_RELATIONSHIPS, GCS_ENTITY_CONS_ATTRS, GCS_CATEGORIES_B, GCS_DATASET_CODES, and GCS_DATA_TYPE_CODES_B supply hierarchy, entity, category, and dataset definitions. Elimination logic reads GCS_ELIM_RULES_B and GCS_ELIM_RULE_RELS. Journal and entry data flows through GCS_ENTRY_HEADERS and GCS_ENTRY_HEADERS_S, with GCS_AD_TRANSACTIONS carrying adjustment transactions and GCS_CONS_IMPACT_ANALYSES supporting impact evaluation. FEM_ENTITIES_ATTR provides entity attribute metadata, and PLITBLM is the standard PL/SQL integer table type used for bulk processing.

Usage Notes

The package is invoked from Oracle Workflow consolidation activities and from concurrent programs that execute consolidation runs; EXECUTE_MODULE is typically the call reached through this path. It is referenced by one other package within the GCS schema. Direct custom calls are possible for diagnostics, but because the API is not classified as a public interface, customizations should avoid depending on internal routine signatures, which changed as recently as patch level 120.15. Availability applies to both 12.1.1 and 12.2.2, as the consolidation engine architecture is unchanged between these releases.