Search Results gr_recipient_addr_types




Overview
Explore in AI Chat

Overview

The GR_RECIPIENT_ADDR_TYPES table is a reference data table within the Process Manufacturing Regulatory Management (GR) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. Its primary role is to define and maintain a list of specialized address classifications that extend beyond the standard transactional addresses, such as shipping or invoice addresses, commonly used in other EBS modules. This table is central to managing the diverse and often jurisdiction-specific address requirements for regulatory compliance in process manufacturing industries, such as chemicals, pharmaceuticals, and food. It provides a controlled, validated list of address types that can be associated with regulatory recipients, ensuring data consistency and integrity for compliance reporting and substance tracking.

Key Information Stored

The table's structure is designed to catalog unique address type codes and their descriptions. While the full column list is not detailed in the provided metadata, the documented primary and foreign key relationships reveal its core components. The primary key column, ADDRESS_TYPE, stores the unique code identifying a specific address classification (e.g., 'REGULATORY_AUTHORITY', 'EMERGENCY_CONTACT', 'MANUFACTURING_SITE'). This column is enforced by the GR_RECIPIENT_ADDR_TYPES_PK primary key constraint. Typically, a companion column, such as DESCRIPTION, would store the human-readable name or explanation for the address type code, though this is inferred from standard design patterns. The table's purpose is to serve as a static lookup for these user-defined classifications.

Common Use Cases and Queries

This table is primarily used in two contexts: application setup and regulatory data management. During implementation, administrators populate this table with the organization-specific address types required for compliance reporting. In daily operations, it is referenced when defining addresses for regulatory entities. Common SQL patterns include querying the list of available types for LOVs (Lists of Values) in application forms or validating address data in interfaces. For reporting, it is frequently joined to transactional address data to decode type codes into meaningful descriptions.

  • Retrieving all configured address types: SELECT address_type, description FROM gr_recipient_addr_types ORDER BY address_type;
  • Joining to address details for a report: SELECT addr.recipient_id, addr.address_line1, typ.description FROM gr_recipient_addresses addr, gr_recipient_addr_types typ WHERE addr.address_type = typ.address_type;

Related Objects

The GR_RECIPIENT_ADDR_TYPES table has a direct and critical relationship with the GR_RECIPIENT_ADDRESSES table, as defined by a foreign key constraint. The ADDRESS_TYPE column in GR_RECIPIENT_ADDRESSES references the primary key in GR_RECIPIENT_ADDR_TYPES, enforcing referential integrity. This means every address type used in a recipient's address record must be predefined in this lookup table. The table is part of the broader GR module's data model for managing regulated substances, recipients, and compliance documents, and it may be referenced by various GR forms, reports, and APIs that handle recipient address information.