Search Results gr_country_profiles




Overview
Explore in AI Chat

Overview

The GR_COUNTRY_PROFILES table is a core master data object within Oracle E-Business Suite Process Manufacturing Regulatory Management (GR). It functions as a central repository for defining country-specific regulatory and document formatting profiles. Its primary role is to enable the system to generate and present regulatory documents, such as safety data sheets (SDS) and labels, in the correct format mandated by a particular country or region. By linking a customer or recipient to a specific profile via its TERRITORY_CODE, the application ensures compliance with local regulatory requirements for document content, layout, and language.

Key Information Stored

The table stores configuration that maps a geographical territory to specific regulatory artifacts. Its primary key is the TERRITORY_CODE, which directly references a standard Oracle EBS territory from FND_TERRITORIES. Other critical columns establish links to various regulatory components. The LANGUAGE column references FND_LANGUAGES to define the default document language. The table holds foreign keys to specific regulatory codes, including a DOCUMENT_CODE (linking to GR_DOCUMENT_CODES), a DISCLOSURE_CODE (linking to GR_DISCLOSURES), and distinct label codes for exposure (LABEL_CODE_EXPOSURE) and toxicological information (LABEL_CODE_TOXIC), both linking to the GR_LABELS_B table. This structure allows a single profile to dictate the complete set of document rules for a country.

Common Use Cases and Queries

The primary use case is the automated selection of a regulatory profile during document generation. When a transaction requires a regulatory document for a shipment destination, the system queries this table using the recipient's territory code to fetch the appropriate formatting rules. Common reporting and validation queries include listing all configured country profiles with their associated document codes, or identifying territories missing a required profile. A typical SQL pattern joins the table to its referenced master data tables for a comprehensive view:

  • SELECT gcp.territory_code, ft.territory_short_name, gdc.document_code, glb_exposure.label_name AS exposure_label FROM gr_country_profiles gcp JOIN fnd_territories ft ON gcp.territory_code = ft.territory_code LEFT JOIN gr_document_codes gdc ON gcp.document_code = gdc.document_code LEFT JOIN gr_labels_b glb_exposure ON gcp.label_code_exposure = glb_exposure.label_code WHERE gcp.territory_code = 'US';

Related Objects

GR_COUNTRY_PROFILES is a central hub with defined foreign key relationships to several key tables in the GR module, as documented in the ETRM.

  • Primary Key Reference: The GR_RECIPIENT_INFO table references GR_COUNTRY_PROFILES.TERRITORY_CODE via its TERRITORY_CODE column, applying the profile to specific customer data.
  • Foreign Key Dependencies (Parent Tables):
    • FND_TERRITORIES (TERRITORY_CODE)
    • FND_LANGUAGES (LANGUAGE)
    • GR_LABELS_B (LABEL_CODE_EXPOSURE and LABEL_CODE_TOXIC)
    • GR_DOCUMENT_CODES (DOCUMENT_CODE)
    • GR_DISCLOSURES (DISCLOSURE_CODE)

These relationships enforce data integrity and ensure that profiles are built upon valid, existing regulatory definitions and application setup data.