Results for “gr_emea”

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

Overview

The GR_EMEA table is a core data object within Oracle Process Manufacturing Regulatory Management (GR), a module that supports regulatory compliance for process-manufactured items across EMEA jurisdictions. Its documented description states that it "contains Europe and Middle East-specific regulatory information about the item," positioning it as the EMEA regional extension of an item's regulatory profile. Whereas general item attributes live in GR_ITEM_GENERAL, GR_EMEA captures the classification, hazard, and supply-list attributes that apply specifically under European and Middle Eastern regulatory frameworks, including European Index numbers, EEC numbers, and consolidated risk and safety phrases.

Based on the ETRM heuristic Data Vault classification mined from the foreign key structure, GR_EMEA leans toward a hub role. This is a modeling suggestion only: the table carries a clean single-column unique business key, ITEM_CODE, which is enforced by the GR_EMEA_PK primary key. In Data Vault terms, GR_EMEA behaves as a business-key hub from which several satellite-style dependent tables hang, rather than as a transactional link table.

Key Information Stored

The table is physically owned by the GR schema and contains 42 documented columns. The most significant are:

• ITEM_CODE – The primary key column and business-key candidate. It uniquely identifies the item for which EMEA-specific regulatory data is recorded and is the target of the GR_EMEA_PK unique index.
• EUROPEAN_INDEX_NUMBER and EEC_NUMBER – Regulatory identifiers used to classify the substance under European directives.
• CONSOLIDATED_RISK_PHRASE and CONSOLIDATED_SAFETY_PHRASE – Aggregated R-phrase and S-phrase text presented on labels and safety documentation.
• APPROVED_SUPPLY_LIST_CONC – The approved supply list concentration threshold applicable to the item.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE30 – The standard Oracle descriptive flexfield columns reserved for client-specific EMEA regulatory extensions, enabling site-specific data capture without schema changes.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard Oracle audit and concurrency columns.

ITEM_CODE is the surrogate/business primary key; no additional composite unique index is documented beyond GR_EMEA_PK, so care must be taken when treating the flexfield attributes as alternate keys.

Common Use Cases and Queries

Regulatory reporting is the principal use case. Analysts frequently join GR_EMEA to GR_ITEM_GENERAL to produce an item-by-item EMEA compliance report, or extract hazard-phrase data for label generation and safety data sheets (SDS). A typical query pattern is:

• SELECT i.ITEM_CODE, e.EUROPEAN_INDEX_NUMBER, e.EEC_NUMBER, e.CONSOLIDATED_RISK_PHRASE FROM GR_ITEM_GENERAL i, GR_EMEA e WHERE i.ITEM_CODE = e.ITEM_CODE;
• Filtering by APPROVED_SUPPLY_LIST_CONC to identify items that breach concentration thresholds.
• Auditing changed records using LAST_UPDATED_BY and LAST_UPDATE_DATE for regulatory change-history reviews.
• Cross-referencing consolidated phrases against GR_ITEM_RISK_PHRASES and GR_ITEM_SAFETY_PHRASES for full phrase lineage.
• Reporting on the flexfield ATTRIBUTE columns after mapping them through ATTRIBUTE_CATEGORY for country-specific requirements.

Related Objects

GR_EMEA sits at the centre of a documented foreign key cluster. The following relationships are the most significant:

• GR_ITEM_GENERAL – Referenced by GR_EMEA.ITEM_CODE; the parent item master record supplying general item attributes.
• GR_ITEM_CLASSNS – References GR_EMEA.ITEM_CODE; holds EMEA-specific item classifications.
• GR_ITEM_RISK_PHRASES – References GR_EMEA.ITEM_CODE; stores individual risk phrases that roll up into CONSOLIDATED_RISK_PHRASE.
• GR_ITEM_SAFETY_PHRASES – References GR_EMEA.ITEM_CODE; stores individual safety phrases underlying CONSOLIDATED_SAFETY_PHRASE.
• GR_EMEA_PK – The primary key constraint defined on ITEM_CODE, enforcing uniqueness and supporting the documented unique index.

Together these objects form the EMEA regulatory data model, with GR_EMEA acting as the hub keyed by ITEM_CODE and the phrase and classification tables serving as dependent extensions.