Search Results gma_gme_text_tbl_pkg




Overview
Explore in AI Chat

Overview

GMA_GME_TEXT_TBL_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is classified under the ETRM (E-Business Suite Technical Reference Manual) as an "OTHER" API, indicating that it is an internal utility package rather than a public, supported business API. Its primary business function is to manage the storage, retrieval, and multilingual maintenance of process manufacturing text records. In the Oracle Process Manufacturing (OPM) suite, GME text tables provide descriptive or instructional text that is attached to manufacturing entities such as formulas, recipes, quality specifications, and other GME objects. This package encapsulates the database operations required to insert, update, lock, delete, and translate those text records, and it also supports loading records from external or seed data sources. It serves as the persistence layer behind the GME text maintenance forms and the database-level triggers that enforce integrity on the underlying text base and translation tables.

Key Procedures and Functions

The package exposes seven documented procedures that together provide complete CRUD and language-maintenance coverage for text records:

  • INSERT_ROW — Creates a new text record in the base text table, establishing the primary key and initial column values.
  • LOCK_ROW — Acquires a row-level lock on an existing text record to serialize concurrent updates and prevent lost changes.
  • UPDATE_ROW — Modifies the attributes of an existing text record after the row has been locked.
  • DELETE_ROW — Removes a text record, including any dependent translation rows, from the text tables.
  • ADD_LANGUAGE — Inserts a new language-specific translation row for an existing text record, enabling multilingual descriptions.
  • TRANSLATE_ROW — Updates the translated text value for an existing language row, supporting maintenance of multilingual content.
  • LOAD_ROW — Loads a text record, typically used during data seeding, migration, or bulk population of the text tables.

The procedure names follow the standard Oracle Forms-generated table handler convention, in which LOCK_ROW, INSERT_ROW, UPDATE_ROW, and DELETE_ROW are invoked in sequence by the form's transactional logic, while ADD_LANGUAGE, TRANSLATE_ROW, and LOAD_ROW support translation and installation tasks. The package is marked VALID and depends only on the SYS STANDARD package, confirming it is self-contained with no external API prerequisites.

Tables Accessed

According to the documented metadata, the package references two tables through APPS synonyms:

  • GME_TEXT_TABLE_TL — The translation table that stores language-specific text for each base text record. It is the primary table manipulated by INSERT_ROW, UPDATE_ROW, DELETE_ROW, ADD_LANGUAGE, TRANSLATE_ROW, and LOAD_ROW.
  • FND_LANGUAGES — The Oracle Application Object Library languages table, used to validate installed and enabled languages when adding or translating language rows.

The package is additionally referenced by the triggers GMA_GME_TEXT_TBL_T1, GMA_GME_TEXT_TBL_T2, and GMA_GME_TEXT_TBL_T3, which enforce the relationship between the base and translation tables, and by the GME_TEXT_DBL database library used by the GME text forms. This reference structure confirms that the package is the central write path for GME text data.

Usage Notes

GMA_GME_TEXT_TBL_PKG is typically invoked indirectly rather than directly by end users. Its callers include the GME text maintenance forms, which use GME_TEXT_DBL to drive the standard table-handler sequence during insert, update, and delete operations. The three GMA_GME_TEXT_TBL_T* triggers call into the package to synchronize base and translation rows during DML. Translation functionality is invoked when users maintain multilingual text through the corresponding forms or when the language rows are populated during installation and patching. Because the package is classified as OTHER rather than a public API, custom development should not call it directly; instead, developers should use supported GME APIs or perform DML against the text tables with appropriate validation. The package is present and valid in both 12.1.1 and 12.2.2, with no documented signature changes between those releases.