Search Results gl_flex_values_obj

Overview

GL_COA_SEG_VAL_IMP_PUB is the public PL/SQL package body in the APPS schema that supports the bulk import of chart of accounts (COA) segment values into Oracle General Ledger. In Oracle EBS 12.1.1 and 12.2.2, key flexfield segment values are validated against value sets defined in the Application Object Library, and this package provides the programmatic entry point through which externally sourced or mass-loaded values are pushed into the GL accounting flexfield. It functions as the public wrapper around the private server-side logic held in GL_COA_SEGMENT_VAL_PVT, exposing a supported interface while delegating validation, key flexfield processing, and error handling to the underlying private package and the FND key flexfield APIs.

The package is classified as a PUB API under the ETRM standard, meaning it is intended for supported external invocation. Its dependency footprint confirms a standard EBS API architecture: FND_API for the returned status/error stack, FND_MSG_PUB and FND_MESSAGE for message resolution, FND_GLOBAL for session context, FND_PROFILE for environment setup, FND_REQUEST for optional concurrent submission, FND_LOG for debug logging, and FND_NEW_MESSAGES for message repository lookups. Utility dependencies include STANDARD (the PL/SQL STANDARD package), PLITBLM, and the GL_FLEX_VALUES_OBJ / GL_FLEX_VALUES_NH_OBJ object types and their corresponding table types, which are used to marshal sets of flex values and normal-hierarchy values into the API.

Key Procedures and Functions

The ETRM metadata documents a single public program unit for this package body:

• COA_SEGMENT_VAL_IMP — the import routine for COA segment values. It accepts a collection of segment value definitions and processes them against the target accounting flexfield, performing validation and inserting or updating the corresponding FND_FLEX_VALUES records. Internally it relies on GL_COA_SEGMENT_VAL_PVT for the substantive validation and DML logic, returning outcome through the FND_API standard status, message, and error-stack conventions.

No additional procedures or functions are documented for this package body, and no parameter lists should be assumed beyond the standard FND_API pattern of p_init_msg_list, x_return_status, x_msg_count, and x_msg_data.

Tables Accessed

Through APPS synonyms, the package and its supporting private code reference the core key flexfield configuration and value tables:

• FND_FLEX_VALUES and FND_FLEX_VALUES_TL — the base and translated tables holding segment values and their descriptions; these are the primary write targets for imported values.
• FND_FLEX_VALUE_SETS — defines the value set controlling validation for each segment.
• FND_FLEX_VALUE_NORM_HIERARCHY and FND_FLEX_HIERARCHIES — support rollup and parent-child hierarchy assignments for normal value sets.
• FND_NEW_MESSAGES — used for message lookup when generating user-facing errors.
• PLITBLM — the standard PL/SQL table utility used for internal collection handling.

Usage Notes

GL_COA_SEG_VAL_IMP_PUB is not referenced by any database object according to the ETRM data, and it is referenced by four other packages, indicating it is a leaf-level API invoked by callers rather than a dependency of EBS forms themselves. It is typically called from custom PL/SQL load routines, conversion programs, or extension code that populates or synchronizes accounting flexfield segment values from external sources. Calls should always check x_return_status and drain the FND_API error stack with FND_MSG_PUB before committing. Because the package writes directly to flexfield value tables, it must be run with the correct GL responsibility and flexfield context, and changes may require concurrent program regeneration for the affected accounting flexfield.