Search Results gr_recipient_addresses




Overview
Explore in AI Chat

Overview

The GR_RECIPIENT_ADDRESSES table is a core data object within the Process Manufacturing Regulatory Management (GR) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It serves as the central repository for storing multiple physical or postal addresses associated with a customer, specifically in the context of regulatory compliance. Its primary role is to manage the complex address requirements for entities that receive regulated products, ensuring accurate documentation for shipping, reporting, and legal adherence. The table's existence underscores the module's need to handle detailed recipient information beyond a single primary address, which is critical for industries like chemicals, pharmaceuticals, and food processing governed by strict regulatory frameworks.

Key Information Stored

The table's structure links a recipient to one or more addresses and defines the purpose of each address link. The primary key is a composite of ADDR_ID and RECIPIENT_CODE, enforcing uniqueness for each address-recipient combination. The RECIPIENT_CODE is the foreign key linking to the GR_RECIENT_INFO table, identifying the specific customer or recipient entity. The ADDR_ID is a foreign key to the SY_ADDR_MST table, which is a common EBS address master, thereby leveraging the application's standardized address format and validation. A critical column is ADDRESS_TYPE, which is a foreign key to GR_RECIPIENT_ADDR_TYPES. This column categorizes the address (e.g., 'Ship To', 'Bill To', 'Regulatory Contact', 'Plant Site') and is essential for determining the address's functional role in business and compliance processes.

Common Use Cases and Queries

A primary use case is retrieving all addresses of a specific type for a recipient to generate compliant shipping documentation or regulatory submissions. For instance, a report may need to list all 'Ship To' addresses for a customer. Another common scenario involves data validation, ensuring a recipient has at least one address of a mandatory type defined by regulatory rules. Sample queries often join this table with the address master and recipient information tables.

  • Find all addresses for a recipient: SELECT gra.recipient_code, gra.address_type, sam.* FROM gr_recipient_addresses gra, sy_addr_mst sam WHERE gra.addr_id = sam.addr_id AND gra.recipient_code = 'RECIP123';
  • List recipients with a specific address type: SELECT gri.recipient_name, sam.* FROM gr_recipient_addresses gra, gr_recipient_info gri, sy_addr_mst sam WHERE gra.recipient_code = gri.recipient_code AND gra.addr_id = sam.addr_id AND gra.address_type = 'SHIP_TO';

Related Objects

GR_RECIPIENT_ADDRESSES is a nexus table with key relationships to several other EBS objects. Its primary dependencies are defined by its foreign key constraints:

  • GR_RECIPIENT_INFO: The master table for recipient/customer information. The RECIPIENT_CODE in GR_RECIPIENT_ADDRESSES references this table to establish the recipient entity.
  • SY_ADDR_MST: The shared Address Master table. The ADDR_ID links to this table to store the actual address lines, city, state, postal code, and country details, avoiding data redundancy.
  • GR_RECIPIENT_ADDR_TYPES: A lookup table defining the valid address type codes (e.g., SHIP_TO, BILL_TO) referenced by the ADDRESS_TYPE column, controlling the address categorization.

Data in this table is typically created and maintained through the Regulatory Management module's forms and interfaces, which internally call the relevant GR APIs.