Search Results get_value_attribute




Overview
Explore in AI Chat

Overview

APPS.GL_DRM_INTEGRATION_PKG is a PL/SQL package that provides the integration layer between Oracle General Ledger and Oracle Data Relationship Management (DRM) within Oracle E-Business Suite 12.1.1 and 12.2.2. DRM is Oracle's master data management solution for maintaining chart of accounts hierarchies, value sets, and segment values outside of EBS. The package enables the bidirectional exchange of flexfield value set definitions, segment values, and hierarchy structures between the two systems. It allows Oracle EBS to import hierarchies and segment value definitions that were authored or maintained in DRM, and to export the current EBS value set and hierarchy content so that DRM can consume it as its source of truth.

The package is declared AUTHID CURRENT_USER, meaning that all SQL inside executes under the privileges of the calling user rather than the owner, which is standard practice for EBS integration interfaces that must respect the invoker's security context. The package header carries a "noship" designation, indicating it is an internal integration utility rather than a publicly supported API.

Key Procedures and Functions

  • GL_DRM_IMPORT_PROCESS — Drives the import of value set and hierarchy data originating from DRM into Oracle General Ledger. It accepts the target value set name and returns a return code indicating success or failure. This is the primary inbound routine of the integration.
  • GET_MESSAGE_TEXT — A utility that resolves a message name, with an optional message token, into a fully formatted, language-specific message string. This is the routine associated with the user's search term and is used throughout the package (and by callers) to translate FND_NEW_MESSAGES entries into readable text for logs, concurrent program output, and error handling.
  • GET_PROFILE_NAME — Returns the descriptive profile option name for a given profile option code, allowing the package to present user-friendly names when referencing EBS profile options.
  • GET_VALUE_ATTRIBUTE — A function that extracts a specific attribute from a compiled flexfield value attribute structure, based on the compiled attribute value and a numeric attribute position. It supports parsing of the attribute strings used by the flexfield validation engine.
  • GL_DRM_EXPORT_PROCESS — The outbound counterpart, added under bug fix 11937027 as the executable for "Initialize Segment Values and Hierarchies." It accepts the standard concurrent program errbuf and retcode parameters plus a value set name, and is designed to run as a concurrent program that exports EBS value set and hierarchy content for consumption by DRM.

Tables Accessed

The package operates primarily against the Application Object Library flexfield and message tables through APPS synonyms. FND_FLEX_VALUE_SETS and FND_FLEX_VALUES (with its translation table FND_FLEX_VALUES_TL) supply value set and segment value definitions; FND_FLEX_HIERARCHIES and FND_FLEX_VALUE_NORM_HIERARCHY provide hierarchy and rollup structure; and FND_FLEX_VALIDATION_QUALIFIERS supports validation rule resolution. FND_NEW_MESSAGES backs the GET_MESSAGE_TEXT routine. FND_LANGUAGES and FND_PROFILE_OPTIONS_TL support language and profile option name resolution. Two staging/interface tables, GL_DRM_HIERARCHY_INTERFACE and GL_DRM_SEGVALUES_INTERFACE, hold the inbound DRM payload before it is validated and applied. PLITBLM is the standard PL/SQL message buffer used for message lookups.

Usage Notes

GL_DRM_INTEGRATION_PKG is not a general-purpose API and is referenced by no other documented packages. It is invoked internally by the GL DRM integration concurrent programs: GL_DRM_IMPORT_PROCESS is called during the DRM-to-EBS import, while GL_DRM_EXPORT_PROCESS is registered as the executable for the "Initialize Segment Values and Hierarchies" concurrent program, which initializes DRM's staging area from existing EBS value sets. GET_MESSAGE_TEXT and GET_PROFILE_NAME are helper routines that may be called by custom code when the same message and profile resolution behaviour is required. Because the package is marked noship and AUTHID CURRENT_USER, customizations should call it only through the supported concurrent programs or with careful attention to the invoker's privileges and to value set naming assumptions.