Results for “gr_risk_combinations”

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

Overview

GR_RISK_COMBINATIONS is a table in the GR schema, part of the Process Manufacturing Regulatory Management (GR) module in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to hold the group and sequence information used to list multiple Risk Phrase Codes together — for example, when regulatory labeling requires a set of R-phrases (such as R11, R20, R36/37/38) to be displayed as a single combined statement rather than as separate entries. The table therefore acts as the configuration bridge between individual risk phrases and the pre-combined phrase strings that appear on labels, MSDS/SDS documents, and compliance reports.

From a Data Vault modeling perspective (a heuristic classification mined from the foreign key structure), this object resolves to a link table. It records associations between two logical entity references — the individual risk phrase and the combined risk phrase — together with grouping and ordering attributes, rather than functioning as a standalone hub of business keys or a descriptive satellite. This classification should be treated as a modeling suggestion, since the physical table also carries descriptive attributes such as display order and audit columns.

Key Information Stored

The table is documented with ten columns. The most significant are:

• COMBINATION_SEQUENCE_NUMBER — the surrogate primary key, enforced by the index GR_RISK_COMBINATIONS_PK. It uniquely identifies each row regardless of the underlying combination it represents.
• RISK_PHRASE_CODE — the individual risk phrase participating in the combination. This column carries a foreign key to GR_RISK_PHRASES_B.
• RISK_PHRASE_CODE_COMBO — the resulting combined risk phrase. This column also carries a foreign key to GR_RISK_PHRASES_B, meaning both the component phrase and the composite phrase are validated against the same phrase repository.
• COMBINATION_GROUP_NUMBER — identifies which grouping a component row belongs to, allowing multiple components to be assembled into one combined phrase.
• DISPLAY_ORDER — controls the order in which component phrases are presented within the combination when rendered.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN track row provenance and change history, consistent with standard EBS WHO-column conventions.

The business-key candidate is documented by the unique index GR_RISK_COMBINATIONS_U1, which spans (RISK_PHRASE_CODE, COMBINATION_GROUP_NUMBER, RISK_PHRASE_CODE_COMBO). This guarantees that a given component phrase appears only once within a given group targeting a given composite phrase — the combination definition cannot be duplicated. Note that COMBINATION_GROUP_NUMBER is part of the business key but not of the surrogate primary key, so joins used to reassemble a full combination must group on the combination group number rather than on the sequence number alone.

Common Use Cases and Queries

Typical scenarios involve retrieving the ordered component phrases that make up a combined risk phrase, validating that a configured combination is complete, and reporting on combination definitions for regulatory review.

• Retrieving components of a combination in display order, joined back to GR_RISK_PHRASES_B for phrase text.
• Detecting orphaned or single-component groups — groups defined with only one member, which may indicate incomplete setup.
• Reconciling configuration after a patch or data migration, using the unique index columns to detect duplicate definitions.
• Feeding label and SDS generation logic that must emit combined rather than individual phrases.

A representative query pattern joins the combination rows to the phrase repository for both the component and the composite:

• SELECT c.COMBINATION_GROUP_NUMBER, c.DISPLAY_ORDER, p.PHRASE_CODE, p.PHRASE_TEXT FROM GR.GR_RISK_COMBINATIONS c, GR.GR_RISK_PHRASES_B p WHERE c.RISK_PHRASE_CODE = p.RISK_PHRASE_CODE ORDER BY c.COMBINATION_GROUP_NUMBER, c.DISPLAY_ORDER;

To enumerate the composite side, the same query can be written with RISK_PHRASE_CODE_COMBO joined to GR_RISK_PHRASES_B, which is useful when confirming that every configured combination resolves to a valid combined phrase entry.

Related Objects

• GR_RISK_PHRASES_B — referenced twice: GR_RISK_COMBINATIONS.RISK_PHRASE_CODE → GR_RISK_PHRASES_B and GR_RISK_COMBINATIONS.RISK_PHRASE_CODE_COMBO → GR_RISK_PHRASES_B. This is the primary dependency; the phrase repository supplies the text and validation for both the component and the composite phrase.
• GR_RISK_PHRASES_TL — the translated phrase table, commonly joined through the base phrase table to obtain language-specific phrase text for multi-language label printing.
• GR_RISK_COMBINATIONS_PK / GR_RISK_COMBINATIONS_U1 — the indexes that enforce uniqueness and support lookups by sequence number and by business key.
• GR substance and label configuration tables — downstream consumers that select combined phrases for printed hazard statements and MSDS/SDS generation; these read GR_RISK_COMBINATIONS indirectly through the phrase repository rather than through a direct foreign key.

Because the documented physical schema exposes no additional foreign keys beyond the two references to GR_RISK_PHRASES_B, the object sits at the perimeter of the phrase configuration area, bound tightly to the phrase repository and consumed indirectly by regulatory document generation components.