Search Results gr_recipient_info




Overview
Explore in AI Chat

Overview

The GR_RECIPIENT_INFO table is a core data object within the Process Manufacturing Regulatory Management (GR) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It functions as a master repository for storing supplementary, customer-specific information pertaining to recipients of regulatory documents. Its primary role is to centralize recipient details beyond basic address data, enabling comprehensive tracking and management of entities that receive critical compliance communications, such as cover letters, disclosures, and other regulated materials. The table's extensive network of foreign key relationships underscores its integral position in the GR module's data model, linking recipients to specific documents, regions, and dispatch histories.

Key Information Stored

While the specific column list is not detailed in the provided metadata, the foreign key constraints and primary key definition reveal the table's critical data elements. The primary key is RECIPIENT_CODE, which serves as the unique identifier for each recipient record. Essential foreign key columns, which define the recipient's context and associations, include: COVER_LETTER_ID (linking to GR_COVER_LETTERS_B), DOCUMENT_CODE (linking to GR_DOCUMENT_CODES), DISCLOSURE_CODE (linking to GR_DISCLOSURES), REGION_CODE (linking to GR_REGIONS), and TERRITORY_CODE (linking to GR_COUNTRY_PROFILES). These columns indicate that the table stores recipient information specific to document types, regulatory disclosures, and geographical jurisdictions, fulfilling its purpose of holding "additional customer specific information."

Common Use Cases and Queries

This table is pivotal for regulatory reporting, audit trails, and ensuring accurate document distribution. Common operational scenarios include generating recipient lists for a specific regulatory disclosure, auditing all documents sent to a particular recipient, and managing region-specific recipient profiles. A typical query might involve joining with related tables to retrieve a comprehensive recipient profile. For example:

  • Identifying all recipients for a specific document code: SELECT ri.* FROM gr_recipient_info ri WHERE ri.document_code = :p_doc_code;
  • Generating a dispatch history report for a recipient: SELECT ri.recipient_code, dh.* FROM gr_recipient_info ri, gr_dispatch_histories dh WHERE ri.recipient_code = dh.recipient_code;
  • Linking recipient details with their associated addresses: SELECT ri.recipient_code, ra.address FROM gr_recipient_info ri, gr_recipient_addresses ra WHERE ri.recipient_code = ra.recipient_code;

Related Objects

The GR_RECIPIENT_INFO table is a central hub with numerous dependencies, as evidenced by its foreign key relationships. Key related objects include:

  • Parent/Reference Tables: GR_COVER_LETTERS_B, GR_DOCUMENT_CODES, GR_DISCLOSURES, GR_REGIONS, GR_COUNTRY_PROFILES. These tables provide valid codes and master data for the foreign key columns in GR_RECIPIENT_INFO.
  • Child/Dependent Tables: GR_DISPATCH_HISTORIES, GR_RECIPIENT_ADDRESSES, GR_RECIPIENT_DOCUMENTS. These tables use the RECIPIENT_CODE as a foreign key to log dispatch events, store physical addresses, and track document associations for each recipient.
  • The primary key constraint GR_RECIPIENT_INFO_PK enforces uniqueness on the RECIPIENT_CODE column, ensuring data integrity across these relationships.