Search Results write_text

Overview

APPS.GL_DRM_INTEGRATION_PKG is an Oracle E-Business Suite PL/SQL package that brokers integration between the General Ledger chart of accounts and Oracle Data Relationship Management (DRM). DRM serves as the master data management hub for enterprise hierarchies; this package translates the GL representation of flex values and normalized hierarchies into the DRM interface tables and, in the reverse direction, consumes values and relationship data supplied by DRM so that GL accounts can be created and validated consistently.

The package body carries the header identifier gldrmpkb.pls 120.9, last modified in 2011, and is therefore present in both 12.1.1 and 12.2.2 environments. It is classified as an "OTHER" API rather than a public interface, indicating it supports the underlying integration flow rather than being a formally supported extension point. The body maintains global state for the integration run, including a boolean debug flag and holders for the value set name and identifier, and declares PL/SQL collection types used to stage flex values and normalized hierarchy rows before handing them to the GL chart-of-accounts segment value import API (GL_COA_SEG_VAL_IMP_PUB).

A distinguishing feature of the package is its XML-oriented design. The body defines numeric constants for opening and closing tags, yes/no text values, and named constants for a DRM loader document root plus elements such as loadDone, numOfValImported, numOfRelImported, relationValidation, loadError, errorMsg, relInError, parent, child, valuesValidation, and description. Private helper routines, among them write_xml_tag, write_xml_element, and write_text, emit this markup. The requested search term "write_text" refers precisely to that private helper, which writes character content into the generated XML output stream.

Key Procedures and Functions

• GL_DRM_IMPORT_PROCESS — Drives the inbound direction of the integration, reading DRM-supplied values and relationships from the interface tables, validating them against flex value and hierarchy definitions, and returning the outcome counts and per-row errors reflected in the XML payload.
• GL_DRM_EXPORT_PROCESS — Drives the outbound direction, extracting GL flex values, hierarchies, and validation qualifiers and packaging them for consumption by DRM or by the intermediate staging tables.
• GET_MESSAGE_TEXT — Retrieves the translatable message string for a given message name, allowing error and status text produced during integration to be presented in the user's language.
• GET_PROFILE_NAME — Resolves and returns the profile option value needed by the integration, typically to determine user-facing configuration such as language or processing behavior.
• GET_VALUE_ATTRIBUTE — Returns an attribute of a key flexfield value, supplying descriptive or qualifier information for individual segment values during export.

Tables Accessed

• FND_FLEX_VALUES, FND_FLEX_VALUES_TL — Read for value definitions and their translated descriptions during export and validation.
• FND_FLEX_VALUE_SETS — Identifies the value set and its identifier used to scope the integration run.
• FND_FLEX_HIERARCHIES — Source of existing hierarchy definitions compared against DRM data.
• FND_FLEX_VALUE_NORM_HIERARCHY — Supplies parent-child normalized hierarchy relationships for export and validation.
• FND_FLEX_VALIDATION_QUALIFIERS — Read to build the qualifier collection used when validating attributes; the body declares a row type and collection indexed by binary integer for this purpose.
• GL_DRM_HIERARCHY_INTERFACE, GL_DRM_SEGVALUES_INTERFACE — The principal staging tables through which DRM hierarchy and segment value data enter or leave the GL application.
• FND_LANGUAGES, FND_NEW_MESSAGES, FND_PROFILE_OPTIONS_TL, PLITBLM — Support language resolution, message lookup, profile option text, and PL/SQL error stack formatting.

Usage Notes

The package is normally invoked indirectly. In a standard configuration, concurrent programs submit the DRM import and export processes, which populate the interface tables and then call GL_DRM_IMPORT_PROCESS or GL_DRM_EXPORT_PROCESS. Because the documented package is referenced by no other package according to the ETRM metadata, callers are expected to be concurrent program definitions, Oracle Forms events, or bespoke code rather than dependent PL/SQL units.

Custom code that invokes these routines directly should treat the API as "OTHER" — usable but not a published extension point — and should therefore expect limited backward-compatibility guarantees across patches and upgrades. Implementations running on 12.1.1 or 12.2.2 may review the XML output produced by the write_text and related helpers when diagnosing integration failures, since the markup carries the imported value and relationship counts together with per-row validation errors.