Results for “gr_country_profiles_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The GR_COUNTRY_PROFILES_V view is a reporting and integration object owned by the APPS schema within the Oracle E-Business Suite environment, specifically under the Process Manufacturing Regulatory Management (GR) product family. In EBS 12.1.1 and 12.2.2, this view presents the rows that define country profiles, providing a denormalized, human-readable representation of the regulatory configuration that governs how product safety, labeling, and disclosure rules apply to a given territory. The base configuration resides in the GR_COUNTRY_PROFILES table, which stores only coded values; the view resolves those codes into descriptive text by joining to language, territory, label, disclosure, and document reference objects. This makes the view the principal access point for regulatory analysts, report developers, and integration interfaces that require decoded country-profile information without needing to write multi-table joins against the underlying transactional configuration tables.

Underlying Base Objects

The view is defined over six documented base objects. The driving table is GR_COUNTRY_PROFILES (exposed through a synonym), which supplies the territory, language, label, disclosure, and document codes along with standard WHO columns. Descriptive enrichment is provided by FND_LANGUAGES_VL and FND_TERRITORIES_VL, both views in the Application Object Library that map language and territory codes to their translated descriptions. Label text is resolved from GR_LABELS_TL, which is referenced twice in the join—once for the exposure label code and once for the toxic label code—using outer joins qualified by USERENV('LANG') so that label descriptions are returned in the session language. GR_DISCLOSURES and GR_DOCUMENT_CODES supply the disclosure and document descriptions respectively. The view therefore acts as a presentation layer over a normalized regulatory data model, collapsing six objects into a single queryable structure.

Key Columns

The view exposes ROW_ID along with the following columns:

• TERRITORY_CODE and TERRITORY_DESCRIPTION — the country or territory and its translated name.
• LANGUAGE and LANG_DESC — the language code associated with the profile and its description.
• LABEL_CODE_EXPOSURE and EXPOSURE_DESCRIPTION — the exposure label identifier and its session-language text.
• LABEL_CODE_TOXIC and TOXIC_DESCRIPTION — the toxic label identifier and its session-language text.
• DISCLOSURE_CODE and DISCLOSURE_DESCRIPTION — the disclosure rule and its description.
• DOCUMENT_CODE and DOCUMENT_DESCRIPTION — the regulatory document type and its description.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns inherited from the base table.

Common Use Cases and Queries

Typical uses include regulatory reporting by territory, populating label and disclosure defaults during product registration, and feeding external compliance systems. A basic listing query is:

SELECT territory_code, territory_description, language, exposure_description, toxic_description FROM gr_country_profiles_v ORDER BY territory_code;

A filtered query retrieving profiles for a specific country, such as the United States, is:

SELECT territory_code, disclosure_description, document_description FROM gr_country_profiles_v WHERE territory_code = 'US';

Because label descriptions are resolved against USERENV('LANG'), results for EXPOSURE_DESCRIPTION and TOXIC_DESCRIPTION reflect the language of the querying session; where no translated label exists, the outer join returns null. Developers should note that the view is read-only and that USERENV('LANG') has been superseded by SYS_CONTEXT('USERENV','LANG') in later releases, though the join behavior remains functionally equivalent.