Search Results new_line

Overview

APPS.GL_CI_PRE_CROSS_PKG is a General Ledger consolidation pre-processing package in Oracle EBS Release 12.1.1 and 12.2.2. Its name reflects its role within the GL Consolidation (CI) framework: it operates as a "pre-cross" utility, executing preparatory work before the cross-instance (intercompany/consolidation transfer) routines run. Consolidation in Oracle GL requires source ledger balances, balancing segment values, and ownership structures to be staged and validated before transfer to the target ledger. This package provides the early-stage plumbing that obtains identifiers and stages transfer data so that the downstream cross-instance programs can execute against consistent, resolved source groups. As a package body declared under the APPS schema with a header dated 2005, it is legacy consolidation infrastructure that remains shipped in the 12.x code line. It is classified in the ETRM repository as OTHER rather than as a public API, indicating it is an internal implementation package invoked by consolidation setup or transfer programs rather than called directly by external integrations.

Key Procedures and Functions

The documented interface of the package exposes two program units:

• GET_SOURCE_GROUP_ID — Resolves and returns the source group identifier used to scope a consolidation pre-transfer operation. Source groups define the set of source ledgers and balancing segment mappings that participate in a consolidation; this routine supplies that key to callers during the pre-run phase.
• PRE_RUN_CI_TRANSFER — Performs the pre-run preparation required before a consolidation (CI) transfer executes. This is the principal entry point of the package, orchestrating the setup work that must precede the actual cross-instance transfer of balances.

The package header additionally defines a diagnostic helper, debug_message, whose body content is documented in the source excerpt. It accepts a message string, a verbose-mode boolean, a line size, and a target file defaulting to FND_FILE.log. Within the loop it declares a local variable, new_line number := 0;, and uses it to locate embedded newline characters via instr(msg_text, fnd_global.local_chr(10)), wrapping output at the configured line size. This explains the relevance of the search term "new_line": it appears as the loop control variable controlling line breaks in diagnostic log output. An exception handler catches SQLCODE = 1, the error raised when FND_FILE is called without proper user, responsibility, and login responsibility initialization (for example, from a bare SQL*Plus session), and redirects output through raise_application_error.

Tables Accessed

No base tables or APPS synonyms are enumerated in the documented metadata for this package. The package body excerpt references only the FND_FILE logging utility and FND_GLOBAL session context, not database tables directly. Any table access performed by GET_SOURCE_GROUP_ID or PRE_RUN_CI_TRANSFER is therefore undocumented in the ETRM extract; based on consolidation design, these routines would resolve ledger and source group identifiers from GL consolidation and ledger setup entities, but no such tables are confirmed by the supplied metadata and none should be assumed.

Usage Notes

The package is not referenced by any other documented package (referenced by 0 other packages), confirming it is invoked at the top of the consolidation call stack rather than as a shared dependency. Typical invocation is from GL Consolidation concurrent programs or consolidation setup flows that must prime source group context before a cross-instance transfer begins. Because the header carries "noship" in its revision string, it is a non-shipped internal build artifact subject to change between releases. Custom code should not call PRE_RUN_CI_TRANSFER or GET_SOURCE_GROUP_ID directly; consolidation should be driven through the supported GL consolidation user interface and standard concurrent requests. When diagnosing consolidation failures during development, the debug_message routine can be leveraged with verbose_mode enabled to emit line-wrapped output to the FND log, though it will raise an exception if executed from SQL*Plus without FND_GLOBAL initialization.