Search Results gr_recipient_documents_pk




Overview
Explore in AI Chat

Overview

The GR_RECIPIENT_DOCUMENTS table is a core data entity within the Process Manufacturing Regulatory Management (GR) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. Its primary role is to manage the association between regulatory recipients and the specific documents that must be printed and distributed to them. This table is conditionally populated; it only stores data when the ADDITIONAL_DOCUMENT_FLAG on the corresponding customer or recipient entity is set to 'Y'. This design enables businesses to configure the automatic inclusion of supplementary documents—such as safety data sheets, certificates of analysis, or regulatory statements—alongside a primary shipping document like an invoice or packing slip, ensuring compliance with customer-specific or regional regulatory requirements.

Key Information Stored

The table functions as a junction entity, primarily storing foreign key relationships that define document-recipient rules. Its structure is defined by a composite primary key and critical foreign keys. The key columns are:

  • RECIPIENT_CODE: A foreign key linking to the GR_RECIPIENT_INFO table. This identifies the customer or regulatory entity mandated to receive specific documents.
  • DOCUMENT_CODE: A foreign key linking to the GR_DOCUMENT_CODES table. This identifies the specific additional document type (e.g., MSDS, allergen statement) that must be printed for the associated recipient.

Together, these columns form the primary key (GR_RECIPIENT_DOCUMENTS_PK), ensuring a unique rule that a specific document is required for a specific recipient. The table's existence for a given recipient is contingent upon the master ADDITIONAL_DOCUMENT_FLAG setting.

Common Use Cases and Queries

The primary use case is the automated generation of document packages during order fulfillment and shipping processes. When the EBS system prints a primary shipping document for a customer, it queries this table to determine which additional regulatory documents must be included in the print batch. A common reporting need is to audit all document requirements for recipients. A sample SQL query to retrieve this information would be:

  • SELECT ri.recipient_name, dc.document_name, dc.description FROM gr_recipient_documents grd JOIN gr_recipient_info ri ON grd.recipient_code = ri.recipient_code JOIN gr_document_codes dc ON grd.document_code = dc.document_code WHERE ri.enabled_flag = 'Y' ORDER BY ri.recipient_name;

Another critical operational query validates if a specific recipient requires any additional documents, which is essential for optimizing document printing logic and ensuring compliance.

Related Objects

The GR_RECIPIENT_DOCUMENTS table is centrally linked to two key master tables via foreign key constraints:

  • GR_RECIPIENT_INFO: This table stores the master definition of regulatory recipients (customers). The foreign key on RECIPIENT_CODE enforces referential integrity, ensuring a document rule cannot exist for an undefined recipient.
  • GR_DOCUMENT_CODES: This table defines the valid types of additional documents available within the system. The foreign key on DOCUMENT_CODE ensures that only predefined, valid document codes can be assigned to a recipient.

These relationships form a critical part of the regulatory document management framework, ensuring data consistency and supporting the business process of compliant document distribution.