Search Results apply_transformation

Overview

GCS_LEX_MAP_GL_APPLY_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that provides the Lexical Mapping API for the General Ledger interface. Its business purpose is to apply a defined lexical mapping rule set against a target GL Interface table, transforming the descriptive and accounting data of a specified set of interface rows prior to Journal Import. The package is intended to be driven by an SRS (Standard Report Submission, i.e., concurrent program) request rather than interactive forms, and it is declared with AUTHID CURRENT_USER so that execution privileges resolve against the invoking schema. The package header carries the version identifier gcsgllxs.pls 115.5, dated 15-Oct-2003, and the creation history attributes the original implementation to M. Ward on 29-May-03. It contains a single documented procedure, Apply_Transformation. The package is classified as OTHER in the ETRM API classification and is not referenced by any other documented package, confirming that it functions as a top-level entry point invoked directly by a concurrent program or custom code.

Key Procedures and Functions

• Apply_Transformation — The single documented procedure in the package. It applies the lexical mapping identified by a rule set ID to a GL Interface table indicated by the source argument, affecting only those rows that match the supplied Group ID. Following a successful transformation, the procedure can optionally trigger Journal Import automatically, with subordinate options to create summary journals and to import descriptive flexfields during that Journal Import. Its signature follows the standard concurrent program convention, returning an error buffer and a return code to the concurrent manager in addition to the mapping rule set ID, source, group ID, and the automatic Journal Import, summary journal, and descriptive flexfield flags. The documented example invokes the procedure as GCS_LEX_MAP_GL_APPLY_PKG.Apply_Transformation (err_buf, ret_code, 111, 10000, 'Consolidation', 'Y', 'N', 'N'), illustrating a run against a rule set, a source of Consolidation, and a group identifier, with automatic Journal Import enabled and the summary journal and DFF options disabled.

Tables Accessed

The package operates against the following tables through APPS synonyms:

• GL_INTERFACE_CONTROL — Identifies the GL Interface table and group to be processed, supplying the control context that determines which rows the transformation affects.
• GL_JE_SOURCES — Provides journal entry source validation and context for the interface rows being transformed.
• GL_JOURNAL_IMPORT_S — The Journal Import sequence and control table, used when the procedure optionally launches Journal Import after a successful transformation.
• FND_CONCURRENT_REQUESTS — Supports submission and monitoring of the concurrent request, including the automatic Journal Import request when that option is enabled.
• DUAL — Used for single-row PL/SQL expression evaluation and control flow.

Usage Notes

Apply_Transformation is designed to be executed from a concurrent program registered as an SRS request, consistent with its error buffer and return code parameters. The typical operational sequence is to load data into a GL Interface table, register the rows under a group ID in GL_INTERFACE_CONTROL, define the desired lexical mapping rule set, and then submit the request that calls this procedure. Setting the automatic Journal Import flag to Y causes Journal Import to run immediately upon a successful transform, and the summary journal and descriptive flexfield import flags are passed through to that Journal Import invocation. Because the package uses AUTHID CURRENT_USER, the executing user requires direct privileges on the referenced interface and Journal Import objects. There are no documented dependencies from other packages, so the procedure is normally invoked directly by the concurrent program definition or by custom wrapper code, and it should be used whenever standardized value substitution on GL interface data is required before journal creation.