Search Results submit_xml_ntf_program




Overview
Explore in AI Chat

Overview

APPS.GCS_ENG_CP_UTILITY_PKG is a utility package body within the Oracle E-Business Suite Consolidation (GCS) module, which forms part of the Enterprise Performance Management / Financial Consolidation Hub stack. The package supports the Consolidation Engine by generating XML output and handling notification or submission logic associated with consolidation runs. In Oracle EBS 12.1.1 and 12.2.2, this object is an internal engine utility rather than a public end-user API, and is classified under the "OTHER" API category. Its responsibilities cluster around the consolidation processing cycle, where entity-level and parent-level data must be extracted, formatted as XML, and routed to downstream notification or transformation processes. The package relies on standard EBS concurrent processing and logging infrastructure such as FND_LOG and FND_FILE, indicating that it is designed to execute within the context of a concurrent program request.

Key Procedures and Functions

The package exposes two documented procedures:

  • GENERATE_XML_AND_NTFS — The principal procedure for producing XML output together with related notification actions. Based on the source excerpt, it accepts a set of consolidation-driving identifiers (execution type, run name, consolidation entity, category code, child entity, run detail, entry identifier, and load identifier) and logs each parameter to the concurrent request log before processing. A notable behavioral detail captured in the source is a fix (Bugfix 5288100) that suppresses XML generation when Aggregation is NOT_APPLICABLE, and a further fix (Bugfix 4874306) that eliminated direct calls to the legacy XML generator in favour of data templates. An obsolete branch is retained when the execution type equals CONS_PROCESS.
  • SUBMIT_XML_NTF_PROGRAM — The procedure that submits the XML notification concurrent program. Its presence supports the pattern in which the utility generates or identifies XML content and then launches a separate concurrent program to handle notification delivery. This is the procedure users encounter when searching for "submit_xml_ntf_program," since the search term closely mirrors the internal procedure name that wraps submission of the notification request.

Tables Accessed

The documented package references the APPS synonym GCS_CONS_ENG_RUN_DTLS. This is the Consolidation Engine run-details table, which records the granular execution state of a consolidation run, including run detail identifiers, entity relationships, and processing status. The package reads from or writes to this table to resolve the identifiers passed into GENERATE_XML_AND_NTFS and to determine which run detail records require XML generation or notification. Access occurs through an APPS synonym, so the physical table resides in the GCS schema and is exposed to the consolidation engine's runtime user.

Usage Notes

GCS_ENG_CP_UTILITY_PKG is not intended for direct invocation by end users. It is normally called from within the consolidation engine's concurrent program flow, either as a nested call from other GCS engine packages (the metadata notes it is referenced by two other packages) or as the target of a concurrent program submission. Typical invocation paths include the Consolidation Monitor and the Consolidation Workbench in EBS, which trigger engine programs that in turn call this utility to emit XML and issue notifications. The parameter listing written to FND_FILE indicates the procedure should always run under a concurrent request context so that the log and output files are available for diagnostics. Customizations should avoid calling GENERATE_XML_AND_NTFS outside that context, and should be aware that historical code paths for direct XML generation have been deprecated in favour of data-template-driven extraction; any custom integration should therefore treat the package as a supporting internal utility and rely on the documented consolidation APIs rather than on this package directly.