Search Results gr_document_rtk




Overview
Explore in AI Chat

Overview

The GR_DOCUMENT_RTK table is a core data object within the Oracle E-Business Suite (EBS) Process Manufacturing Regulatory Management module (GR). It serves a critical compliance function by storing detailed Right-to-Know (RTK) information. RTK regulations, such as those enforced by OSHA in the United States, mandate that workers have access to safety information for hazardous chemicals. This table is the repository for the specific RTK data that is configured to display or print on regulatory documents, such as Material Safety Data Sheets (MSDS) or shipping labels. Its role is to link document templates with location-specific RTK requirements, ensuring generated documents contain the legally mandated hazard communication for a given geographic or organizational segment.

Key Information Stored

The table's structure is designed to associate document codes with specific operational locations and their corresponding RTK details. Its primary key is a composite of four columns, indicating the precision of its data relationships. The key columns are DOCUMENT_CODE, which identifies the type of regulatory document; LOCATION_SEGMENT_QUALIFIER and LOCATION_SEGMENT_VALUE, which together define the specific location (e.g., a particular state, country, or facility) for which the RTK rules apply; and PARENT_SEGMENT_ID, which provides a hierarchical context for the location segment. While the specific RTK detail columns (like hazard statements or precautionary codes) are not enumerated in the provided metadata, the table's description confirms it holds the substantive RTK information that is rendered onto the final document output.

Common Use Cases and Queries

A primary use case is the batch generation of compliant safety documents for shipments destined for different regulatory jurisdictions. System processes query this table to retrieve the correct RTK text based on the document type and the ship-to location. Common reporting needs include auditing document configurations and validating that all required locations have associated RTK data. A typical query would join this table to location and document master tables to list all configured RTK rules.

SELECT rtk.document_code,
       rtk.location_segment_qualifier,
       rtk.location_segment_value,
       doc.document_name
FROM gr_document_rtk rtk,
     gr_document_codes doc
WHERE rtk.document_code = doc.document_code
AND rtk.location_segment_qualifier = 'STATE';

Related Objects

The GR_DOCUMENT_RTK table maintains defined foreign key relationships with two other EBS tables, forming the integrity backbone for its data.

  • GR_DOCUMENT_CODES: This is the master table for document definitions. The relationship is enforced via the DOCUMENT_CODE column (GR_DOCUMENT_RTK.DOCUMENT_CODE references GR_DOCUMENT_CODES.DOCUMENT_CODE). This ensures all RTK details are attached to a valid, predefined document type.
  • AR_LOCATION_VALUES: This table, from the Receivables module, stores validated location segment values. The relationship is a composite foreign key on three columns: LOCATION_SEGMENT_QUALIFIER, LOCATION_SEGMENT_VALUE, and PARENT_SEGMENT_ID. This ensures that the locations specified for RTK rules are valid within the enterprise's defined location hierarchy.