Search Results gr_document_codes




Overview
Explore in AI Chat

Overview

The GR_DOCUMENT_CODES table is a core configuration table within the Oracle E-Business Suite Process Manufacturing Regulatory Management (GR) module. It serves as a master repository for defining the formatting and content rules for regulatory documents, such as Material Safety Data Sheets (MSDS) and labels. Each record represents a unique document code that controls the visual presentation and data inclusion for generated documents, ensuring compliance with regional or customer-specific regulatory requirements. Its primary role is to act as a central reference point, governing how detailed ingredient, toxicological, and exposure information is displayed or printed.

Key Information Stored

While the specific column list is not detailed in the provided metadata, the description and foreign key relationships indicate the table stores critical configuration attributes. The primary key is the DOCUMENT_CODE column, which uniquely identifies each document format rule. Based on its described purpose, the table likely contains columns to control the date format for documents, Boolean flags (e.g., Y/N) to determine the printing of detailed ingredient, toxic, and exposure sections, and fields for customizing the appearance of these detailed elements (such as font, layout, or section ordering). The presence of a foreign key to FND_USER.USER_ID also suggests it tracks creation or last update user information.

Common Use Cases and Queries

A primary use case is the setup and maintenance of document templates during the implementation of the Regulatory Management module. Administrators create and configure document codes to align with the legal requirements of different countries or the specific needs of key customers. Common reporting and validation queries include listing all configured document codes and their active settings, or identifying which codes are assigned to specific country profiles. For example, a basic query to audit document configurations would be:

  • SELECT document_code, date_format, print_ingredients_flag FROM gr.gr_document_codes WHERE enabled_flag = 'Y' ORDER BY document_code;

Another critical operational use case is during the batch generation of regulatory documents for shipped products, where the system references the GR_DOCUMENT_CODES table via foreign keys (like in GR_DISPATCH_HISTORIES) to apply the correct formatting rules.

Related Objects

The GR_DOCUMENT_CODES table has a central relationship with numerous other tables in the GR schema, as evidenced by its foreign key constraints. It is primarily referenced by transactional and setup tables that require a document format definition.

  • GR_COUNTRY_PROFILES: Links a country profile to a default document code (GR_COUNTRY_PROFILES.DOCUMENT_CODE).
  • GR_DISPATCH_HISTORIES: Associates a specific dispatch or shipment transaction with a document code (GR_DISPATCH_HISTORIES.DOCUMENT_CODE).
  • GR_DOCUMENT_HEADINGS, GR_DOCUMENT_PRINT, GR_DOCUMENT_RTK: These are likely child tables storing additional, code-specific document content or print parameters.
  • GR_ITEM_DOC_STATUSES, GR_RECIPIENT_DOCUMENTS, GR_RECIPIENT_INFO: Track the document status and association for items and recipients against a specific document code.
  • FND_USER: References the application user who created or last updated the document code record (GR_DOCUMENT_CODES.USER_ID).