Search Results print_logfile

Overview

XLA_UPDATE_INVAL_CCID is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Subledger Accounting (XLA) product family and is classified under the ETRM taxonomy as OTHER. Its stated purpose, as recorded in the package header comments, is to serve as the server-side implementation for the "Update Invalid CCIDs" program. The package is invoked from the Java layer after a BPEL process completes. When the BPEL flow returns a set of invalid Code Combinations (CCIDs), the Java layer calls this API so that affected accounting entries can be stamped with an invalid status. In practical terms, the package bridges an external BPEL-driven validation service and the Subledger Accounting tables inside EBS, applying the outcome of an external code combination validation back onto accounting event and journal data.

Key Procedures and Functions

ETRM documents a single public entry point for this package body: XLA_UPDATE_INVAL_CCID_API. This procedure encapsulates the update logic for invalid CCIDs. It is the routine the Java caller references when it needs the database to mark accounting entries whose code combinations have failed downstream validation. The package body also contains a private local trace routine named TRACE, which is not part of the documented public interface but is used internally to write diagnostic output through the FND_LOG framework. The trace constants defined in the body (level_statement, level_procedure, level_event, level_exception, level_error, level_unexpected, and a disabled level) show that logging is guarded by a session log level and a log-enabled flag. This private logging infrastructure supports the "print_logfile" style of diagnostics familiar to EBS administrators, since FND log messages surface in the standard EBS log files when logging is enabled for the module XLA.PLSQL.XLA_UPDATE_INVAL_CCID.

Tables Accessed

The package interacts with core Subledger Accounting tables through APPS synonyms. It references XLA_AE_HEADERS and XLA_AE_LINES, the header and line tables holding accounted journal entries, which are the primary targets of the invalid CCID update. It also references XLA_EVENTS, the table that records subledger accounting events, allowing the package to correlate affected accounting entries with their originating events. Finally, it references PLITBLM, a standard EBS PL/SQL table-of-varchar2 storage structure often used to hold lists or arrays in memory, which in this context supports the passing or buffering of invalid CCID values returned from the Java/BPEL layer. No other package in the documented set references this package.

Usage Notes

XLA_UPDATE_INVAL_CCID is not a user-facing utility and is not exposed through a standard EBS form. It is invoked programmatically by the Java layer, typically as the completion step of an integration flow in which BPEL performs code combination validation and returns the offending CCIDs. The Java caller then invokes XLA_UPDATE_INVAL_CCID_API to update the corresponding accounting entries to invalid status. Because tracing is controlled by the FND_LOG mechanism and the module identifier XLA.PLSQL.XLA_UPDATE_INVAL_CCID, support personnel diagnosing the process should enable FND logging at the appropriate level and inspect the resulting log file—this is where the "print_logfile" style diagnostics originate. The source history shows the package was created in April 2008 and last updated in November 2010, indicating a stable, narrowly scoped integration component rather than a general-purpose API. Customers and integrators should not call it directly from custom code unless they are replicating the BPEL integration contract, since the Java layer is the intended and documented caller.