Search Results insert_header_row

Overview

APPS.GME_TEXT_DBL is a database-layer package body in the Oracle E-Business Suite Process Manufacturing (OPM / GME) schema. It belongs to the family of "DBL" (database-layer) packages that encapsulate low-level DML against the Process Manufacturing text and documentation tables. Its principal business function is to persist text header and text line data used by the GME text engine, which stores free-form descriptive and instructional text associated with process manufacturing entities such as formulas, recipes, specifications, and quality results.

The package is classified as OTHER in the ETRM metadata, indicating that it is an internal implementation utility rather than a published or certified public API. It is documented in ETRM 12.2.2 and carries a header dated 2005, reflecting its long-standing presence across the 11i and R12 code lines, including Oracle EBS 12.1.1 and 12.2.2. The package exposes exactly two documented program units: INSERT_HEADER_ROW and INSERT_TEXT_ROW. Both are functions returning BOOLEAN and are designed with IN and IN OUT NOCOPY parameters, a pattern typical of Oracle Forms-callable database packages that return success or failure to the calling form or caller.

Key Procedures and Functions

• INSERT_HEADER_ROW — Inserts a single row into the GME_TEXT_HEADER table, establishing a new text document header. The function accepts an input header record and returns the generated text code through an IN OUT NOCOPY header record parameter. The text code is sourced from the GEM5_TEXT_CODE_S sequence, while audit columns (created_by, creation_date, last_updated_by, last_update_date) are populated from the GME_COMMON_PVT package globals: g_user_ident for the user and g_timestamp for the timestamp. The function returns TRUE on success and FALSE on failure, with the exception handler routing the error message through FND_MSG_PUB.ADD_EXC_MSG (referenced as Bug2804440). Note that the internal API name constant in this unit is set to 'GET_ITEM_NO', which appears to be a code artifact in the original source.
• INSERT_TEXT_ROW — Inserts a single text line (paragraph) into the GME_TEXT_TABLE. Rather than performing direct DML, it delegates to GMA_GME_TEXT_TBL_PKG.INSERT_ROW, passing the row identifier, text code, language code, paragraph code, sub-paragraph code, line number, and the text content, along with audit columns populated from GME_COMMON_PVT. As with INSERT_HEADER_ROW, it returns TRUE on success and FALSE on failure, and logs exceptions through FND_MSG_PUB.ADD_EXC_MSG.

Tables Accessed

• GME_TEXT_HEADER — The parent table holding text document headers. INSERT_HEADER_ROW writes a new header row here and obtains the surrogate text_code key from the sequence GEM5_TEXT_CODE_S.
• GME_TEXT_TABLE — The child table storing the individual text lines or paragraphs associated with a header. INSERT_TEXT_ROW writes to this table indirectly via the GMA_GME_TEXT_TBL_PKG wrapper.
• GEM5_TEXT_CODE_S — The sequence used to generate the primary key (text_code) for each new text header.

All three objects are referenced through APPS synonyms, consistent with standard EBS schema access conventions.

Usage Notes

GME_TEXT_DBL is an internal package invoked by higher-level application logic rather than by end users directly. Typical invocation paths include Oracle Forms-based maintenance screens for process manufacturing text, non-form PL/SQL callers that create text headers and lines programmatically, and other PL/SQL packages that require the standard text-insert operations. The ETRM metadata records that it is referenced by two other packages, confirming its role as a shared utility.

Because the functions return BOOLEAN—a PL/SQL-only datatype—the package cannot be called directly from SQL or from Java/JDBC without a wrapper; this reinforces its origins as a Forms-oriented database-layer package. Customizations should prefer formally published APIs where available, treating GME_TEXT_DBL as internal. When auditing the originating user, the APPS.GME_TEXT_DBL source excerpt specifically names "insert_header_row," which corresponds to the INSERT_HEADER_ROW function described above.