Search Results c_created_error

Overview

APPS.FA_XLA_CMP_LOCK_PKG is a private Oracle Assets (Fixed Assets) package that belongs to the FA_XLA component of the Subledger Accounting (XLA) architecture. Its documented purpose is to create locking for each extract type processed by the FA XLA extract engine. In Oracle EBS releases 12.1.1 and 12.2.2, Subledger Accounting extracts accounting events from Oracle Assets and transforms them into journal entries. Because multiple extract processes can run concurrently, the extract infrastructure requires a serialization mechanism to prevent two concurrent runs from claiming the same set of accounting event data. FA_XLA_CMP_LOCK_PKG provides that mechanism.

The package header carries the source control identifier $Header: faxlackb.pls 120.1 2006/08/24 14:23:53 bridgway noship $, indicating it is a seed (non-shippable object) created by the development team. It is classified under the ETRM API classification OTHER and is owned by APPS.

Key Procedures and Functions

The ETRM repository documents a single public procedure for this package: GENERATELOCKINGEXTRACT. This routine generates the locking constructs required for each extract type handled by the FA XLA extract process. It is the sole externally visible entry point in the package.

Internally, the body embeds private PL/SQL blocks as string constants (for example C_PRIVATE_API_1 and C_PRIVATE_API_2) that are assembled and executed dynamically. The source excerpt shows that these embedded blocks declare the private procedure Lock_Data, which accepts no parameters and operates on a PL/SQL associative array of type number_tbl_type (a table of NUMBER indexed by BINARY_INTEGER). The dynamic construction supports the FND_LOG diagnostic framework: the embedded code checks the runtime logging level using G_LEVEL_PROCEDURE and G_CURRENT_RUNTIME_LEVEL and emits begin and end trace messages through fnd_log.string, with an exception handler keyed on WHEN others and G_LEVEL_UNEXPECTED.

The package does not expose any documented functions; GENERATELOCKINGEXTRACT is the only procedure recorded in the metadata.

Tables Accessed

The only database object recorded in the ETRM dependency metadata for this package is DBMS_SQL. DBMS_SQL is the Oracle-supplied dynamic SQL package rather than an application table, and its presence confirms the pattern visible in the source: SQL statements and anonymous PL/SQL blocks are parsed, bound, and executed at runtime rather than being compiled statically. The locking statements issued against the FA XLA extract structures are therefore constructed dynamically by GENERATELOCKINGEXTRACT.

No FA base tables (such as FA_ADDITIONS, FA_BOOKS, or FA_DEPRN_SUMMARY) and no XLA interface or extract tables are documented as direct references. Because the dynamic SQL text is assembled at runtime, the actual tables acted upon are not resolved from the package's static dependency list and must be identified from the generated statement text when troubleshooting.

Usage Notes

FA_XLA_CMP_LOCK_PKG is invoked programmatically by the Oracle Assets Subledger Accounting extract flow rather than from a user-facing form. The ETRM metadata records that the package is referenced by one other package, indicating that it is called by a companion FA XLA extract or compare driver rather than being scheduled independently as a concurrent program.

Because the package is a private FA implementation object, it should not be called directly from custom code. Customers extending or debugging FA XLA extraction should invoke the supported extract concurrent programs and rely on the accounting event and extract log tables for diagnostics. When the ETRM search term "c_created_error" appears in the context of this object, it relates to the error-state columns populated in the FA XLA extract interface structures that the dynamic locking logic traverses before the extract proceeds.

The embedded FND_LOG calls provide the primary diagnostic surface: setting the FND logging level to PROCEDURE or UNEXPECTED captures the begin and end markers for Lock_Data and any unexpected exceptions raised during locking, which is the recommended first step when an FA XLA extract terminates without processing records.