Search Results print_toxic_data




Overview

GR_PROCESS_DOCUMENTS is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema that supports the Product Lifecycle Management / regulatory compliance domain — specifically the generation, assembly, and printing of item documents, disclosures, and safety worksheets. In the Oracle EBS 12.1.1 and 12.2.2 environments, this package is classified under the ETRM (E-Business Suite Technical Reference Manual) as an "OTHER" API, meaning it is not a formally published public API but is relied upon internally by related packages and forms. Its central responsibility is to build document detail records from generic item, label, concentration, and phrase data, resolve conflicts between phrases, and render the resulting output to a printable form.

Key Procedures and Functions

The package exposes 38 documented procedures and functions. The most prominent include:

Tables Accessed

The package reads and writes through APPS synonyms, including: FND_LANGUAGES, FND_PROFILE_OPTION_VALUES, and FND_USER for language, profile, and user context; GR_DOCUMENT_CODES and GR_DISCLOSURES for document type and disclosure definitions; GR_GENERIC_ITEMS_B, GR_ITEM_CONCENTRATIONS, GR_ITEM_DISCLOSURES, GR_ITEM_DOC_STATUSES, and GR_ITEM_GENERAL for item-level composition and status; GR_LABELS_B, GR_LABELS_TL, GR_LABEL_CLASSES_B, and GR_LABEL_PROD_CLASSES for label and classification data; and GR_EMEA for regional regulatory content.

Usage Notes

GR_PROCESS_DOCUMENTS is typically invoked from Oracle EBS forms and concurrent programs within the regulatory/document management module, and is referenced by one other package. Custom code should treat it as an internal implementation package rather than a supported public API. A historical note in the source (BUG 2381697, 20-Jun-2002) indicates print-related logic has been maintained since early releases. All routines conform to the FND_API error-handling convention, returning x_return_status, x_msg_count, and x_msg_data. Because the documented source excerpt shows stub bodies carrying a success return status, integrators should validate behavior against the actual installed version before relying on it.