Search Results gme_text_table




Overview
Explore in AI Chat

Overview

GME_TEXT_DBL is a database-layer PL/SQL package owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Process Manufacturing (GME) product family and provides the low-level insert primitives used to persist free-form text associated with process manufacturing entities. In Oracle Process Manufacturing, descriptive text is stored in a parent/child model: header-level text is captured in GME_TEXT_HEADER, while the individual text lines or segments are stored in GME_TEXT_TABLE. The GME_TEXT_DBL package encapsulates the physical INSERT operations against those two tables, insulating callers from the underlying column layouts and allowing the data access logic to be maintained in a single location.

The suffix "DBL" follows the Oracle EBS convention denoting a database-layer package — as opposed to an API or validation-layer package — and its public interface consists solely of two boolean-returning functions, one for each level of the text hierarchy. This package is classified as OTHER in the ETRM repository, meaning it is an internal utility rather than a formally published, customer-callable API.

Key Procedures and Functions

The package exposes two documented functions:

  • INSERT_HEADER_ROW — Inserts a single row into the text header table. It accepts an input record typed against gme_text_header%ROWTYPE and an IN OUT NOCOPY output record of the same type, returning BOOLEAN to indicate success or failure. Because the output parameter is passed by reference, any server-side defaults or derived values assigned during the insert are returned to the caller without a copy.
  • INSERT_TEXT_ROW — Inserts a single row into the text line table. Its signature mirrors the header function: an input record typed against gme_text_table%ROWTYPE, an IN OUT NOCOPY output record of the same type, and a BOOLEAN return value. This function persists the individual text segments that belong to a header row created by the preceding call.

The use of %ROWTYPE anchoring means the parameter structures automatically track changes to the underlying table definitions, and the BOOLEAN return value allows callers to branch on success without relying on exceptions.

Tables Accessed

  • GME_TEXT_HEADER — The parent table holding header-level text records. INSERT_HEADER_ROW writes to this table; the %ROWTYPE anchoring on the function signature confirms the column mapping.
  • GME_TEXT_TABLE — The child table holding the individual text lines keyed to a header. INSERT_TEXT_ROW writes to this table, and it is the object the user searched for under the term "gme_text_table."
  • GEM5_TEXT_CODE_S — A text-code sequence referenced via an APPS synonym, used by the package to generate or validate key values for the text records being inserted.

All three objects are resolved through APPS synonyms, consistent with standard EBS schema architecture in which the APPS layer owns the synonyms and grants while the base objects reside in the product schema.

Usage Notes

GME_TEXT_DBL is not intended to be invoked directly by end users. It is a building block consumed by higher-level logic: the ETRM repository records that this package is referenced by two other packages, which are the more likely entry points for text creation. Typical invocation patterns include Oracle Forms triggers and program units that capture user-entered text, and concurrent or PL/SQL batch programs that create text records programmatically. Custom development should generally call the referencing API packages rather than GME_TEXT_DBL itself, because those wrappers are expected to supply validation, key derivation via GEM5_TEXT_CODE_S, and transaction control that the DBL layer deliberately omits. Callers that do use the functions directly must handle the BOOLEAN return value, manage their own COMMIT or ROLLBACK, and populate the input record completely before calling INSERT_HEADER_ROW followed by one or more INSERT_TEXT_ROW calls for the associated lines.