Search Results ntf_only

Overview

GCS_ENG_CP_UTILITY_PKG is a consolidation engine utility package owned by APPS in the Oracle E-Business Suite Financial Consolidation Hub (GCS) module. The package provides the technical bridge between the consolidation engine's business processing logic and the concurrent manager framework that produces output artifacts — specifically extensible markup language (XML) documents and workflow notifications. In the context of the search term "cons_process", the package is most directly associated with the CONS_PROCESS execution type, one of three supported execution modes the package recognizes alongside IMPACT_ENGINE and NTF_ONLY. When the consolidation process completes its balance translation, elimination, and aggregation phases, this package is responsible for generating the resulting XML output and the notifications that inform consolidation managers and entity-level users of the outcome. The package was last revised under version 120.1 in October 2005 and retains the "noship" designation in its header, indicating it is a supporting internal utility rather than an end-user-facing API. It is classified in the ETRM repository as an OTHER API type, reflecting its role as an internal engine component invoked programmatically rather than as a documented public interface.

Key Procedures and Functions

The package exposes two documented procedures:

• GENERATE_XML_AND_NTFS — The core implementation procedure. It serves as the concurrent program entry point responsible for generating the XML payload and the associated notifications for a given consolidation execution. Its execution is parameterized by an execution type (CONS_PROCESS, IMPACT_ENGINE, or NTF_ONLY), a run name acting as the process identifier, the consolidation entity, category code, and child entity, together with optional run detail, entry, and load identifiers that scope the generation to a specific unit of work. As a standard concurrent program it also returns the conventional error buffer and return code outputs.
• SUBMIT_XML_NTF_PROGRAM — The submission API. Rather than performing generation inline, this procedure enqueues a concurrent request to run the XML and notification generation logic asynchronously. It accepts the same execution type and identifier parameters (with the entity, run detail, entry, and load arguments defaulted to NULL), making it suitable for callers that need to trigger output generation without blocking the calling session.

Tables Accessed

The documented table reference is GCS_CONS_ENG_RUN_DTLS, the consolidation engine run details table, accessed through an APPS synonym. This table stores the granular run-level records produced during a consolidation execution, and the utility package reads it to resolve the run name, run detail identifiers, and entity context required to assemble the correct XML output and to determine the notification recipients and content. The optional run detail, entry, and load identifier parameters correlate directly to key columns in this table, allowing the generation logic to be narrowed to a single run detail record or broadened across an entire consolidation run. No other table references are documented.

Usage Notes

This package is invoked within the Financial Consolidation Hub consolidation workflow rather than from standard Oracle Forms. Typical invocation paths include:

• Concurrent program submission — The consolidation engine submits the generate_xml_and_ntfs procedure as a concurrent program as part of the consolidation run sequence, using the CONS_PROCESS execution type to drive full XML and notification generation after consolidation processing completes.
• Programmatic submission — Other consolidation engine packages call submit_xml_ntf_program to enqueue output generation; the ETRM metadata records that this package is referenced by two other packages, confirming its role as a shared utility.
• Targeted re-runs — The IMPACT_ENGINE and NTF_ONLY execution types support narrower scenarios, such as regenerating notifications only without rebuilding XML, or regenerating output for a specific run detail, entry, or load.

Because the package is marked "noship" and classified as OTHER, it should be treated as an internal engine component. Customizations that call it directly must supply a valid execution type and a consistent set of identifier parameters, and should account for the asynchronous behavior of submit_xml_ntf_program when sequencing downstream steps.