Search Results g_end_item

Overview

GR_PROCESS_DOCUMENTS is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the Oracle Process Manufacturing (OPM) regulatory and product-labeling functionality. Its business purpose is to assemble, resolve, and print regulatory documents — such as Material Safety Data Sheets, ingredient declarations, toxicological summaries, exposure statements, and product labels — from the underlying GR_* (regulatory) tables. The package header, defined with AUTHID CURRENT_USER, declares the global PL/SQL record and collection types used to govern the print sequence for ingredient, toxic, and exposure information, including G_Toxic_Line, G_Ingred_Line, G_Exposure_Line, and G_Ingred_Size.

A key declared structure is the print_ingredient record type and its associated t_print_ingredient PL/SQL table, used to consolidate print ingredient section data by item group. The package also declares numerous global variables that hold session state during document processing, such as G_PKG_NAME, G_DOCUMENT_CODE, G_DISCLOSURE_CODE, G_ING_DISCLOSURE, G_START_ITEM, G_END_ITEM, G_CURRENT_PHRASE, G_CURRENT_ITEM, G_ML_ITEM, G_CURRENT_LABEL, and G_OPM_VERSION. The presence of G_ML_ITEM and the references to FND_LANGUAGES and GR_LABELS_TL indicate that multilingual and language-code handling is intrinsic to document generation; a search for g_language_code therefore maps to the language-resolution logic that governs translated label and phrase text.

Key Procedures and Functions

The package exposes 38 documented procedures and functions. The primary entry points and their roles include:

• BUILD_DOCUMENT_DETAILS — assembles the detailed content for a document.
• BUILD_ITEM_DOCUMENT — constructs the document for a specific item.
• PRINT_DOCUMENT and PRINT_WORKSHEET — render the finished document and worksheet output.
• PROCESS_DOCUMENT_STRUCTURE — drives the overall structural flow of document processing (composition).
• RESOLVE_PHRASE_CONFLICTS, CONFLICT_ACTION, GET_PHRASE_TYPE, UPDATE_PHRASE_GROUPS, and THIRD_PHRASE_INSERT_ROW — govern phrase selection, conflict resolution, and phrase-line assembly.
• PRINT_INGREDIENT_DATA, PRINT_TOXIC_DATA, PRINT_EXPOSURE_DATA, PRINT_PHRASE_LINES, and PRINT_LABEL_LINES — emit the individual content sections (ingredients, toxicity, exposure, phrases, and labels).
• PRODUCT_TOXIC_DATA and PRODUCT_EXPOSURE_DATA — retrieve product-level toxicological and exposure information.
• SORT_LINE_DATA — order line-level output, often sizing and sequencing ingredient lines.
• INSERT_WORKSHEET_MESSAGE and CLEAR_WORKSHEET_SESSION — manage worksheet session messaging and cleanup.

These routines collectively translate stored regulatory content into printable, language-aware document sections.

Tables Accessed

All tables are referenced through APPS synonyms. Document and disclosure definitions reside in GR_DOCUMENT_CODES and GR_DISCLOSURES. Item data is drawn from GR_ITEM_GENERAL, GR_GENERIC_ITEMS_B, GR_ITEM_CONCENTRATIONS, GR_ITEM_DISCLOSURES, and GR_ITEM_DOC_STATUSES. Label and classification content is held in GR_LABELS_B, GR_LABELS_TL, GR_LABEL_CLASSES_B, and GR_LABEL_PROD_CLASSES, with GR_LABELS_TL providing translated label text. Phrase content is sourced from GR_PHRASES_B. Language and localization are resolved via FND_LANGUAGES, while FND_PROFILE_OPTION_VALUES supplies profile-option settings such as the OPM version, and FND_USER identifies the acting user. The GR_EMEA table supports region-specific regulatory content. The language-code lookup performed against FND_LANGUAGES is central to selecting the correct translated label and phrase rows during printing.

Usage Notes

GR_PROCESS_DOCUMENTS is typically invoked from the Oracle Process Manufacturing regulatory and labeling forms that compose, review, and print MSDS and label documents, and it may be called by concurrent programs that batch-generate document output. It is referenced by one other package, indicating it functions as a shared processing engine within the GR module. Custom code should call the public procedures rather than manipulate the global collections directly. Because the package maintains session-scoped global state and multilingual variables such as G_ML_ITEM, callers should ensure CLEAR_WORKSHEET_SESSION is invoked appropriately between document runs to avoid residual data. The package is documented for EBS 12.1.1 and 12.2.2, and definitions are stored in the file GRPDOCUS.pls.