Search Results gr_risk_combinations_u1




Overview
Explore in AI Chat

Overview

The GR_RISK_COMBINATIONS table is a core data structure within Oracle E-Business Suite Process Manufacturing Regulatory Management (GR) module. It serves a critical function in the management of chemical and product safety data by defining how individual risk phrases are logically grouped and sequenced for regulatory reporting and labeling. The table enables the creation of complex, multi-part risk statements from atomic risk phrase codes, which is a fundamental requirement for generating compliant safety data sheets (SDS) and product labels according to various global regulations like GHS, REACH, and CLP.

Key Information Stored

The table's primary purpose is to store the grouping and ordering logic for risk phrase combinations. Its key columns, as defined by its primary and unique keys, are central to this function. The COMBINATION_SEQUENCE_NUMBER acts as the primary identifier for a specific entry within a combination group. The COMBINATION_GROUP_NUMBER identifies a distinct logical set of risk phrases intended to be presented together. The table stores two critical risk phrase references: RISK_PHRASE_CODE, which is the base risk phrase being combined, and RISK_PHRASE_CODE_COMBO, which is the additional risk phrase it is combined with. The unique key constraint (GR_RISK_COMBINATIONS_U1) on these last three columns ensures data integrity by preventing duplicate combination definitions.

Common Use Cases and Queries

A primary use case is the dynamic assembly of regulatory text for a product's hazard classification. When the system generates a label or SDS section for a substance, it queries this table to find all risk phrases associated with the product, determines their defined combination groups, and assembles the final text in the prescribed sequence. A typical reporting query would join this table to the master risk phrase descriptions. For example, to retrieve all defined combinations for a specific risk phrase code 'R25', one might use:

  • SELECT grc.combination_group_number, grc.combination_sequence_number, grc.risk_phrase_code, grc.risk_phrase_code_combo, grp1.phrase_text AS base_phrase, grp2.phrase_text AS combo_phrase FROM gr.gr_risk_combinations grc JOIN gr.gr_risk_phrases_b grp1 ON grc.risk_phrase_code = grp1.risk_phrase_code JOIN gr.gr_risk_phrases_b grp2 ON grc.risk_phrase_code_combo = grp2.risk_phrase_code WHERE grc.risk_phrase_code = 'R25' ORDER BY grc.combination_group_number, grc.combination_sequence_number;

Data maintenance activities, such as adding new combination rules or modifying sequences for a regulatory update, are also common administrative tasks performed directly on this table's data.

Related Objects

The GR_RISK_COMBINATIONS table has a direct and exclusive relationship with the master risk phrase table, GR_RISK_PHRASES_B. This is enforced through two foreign key constraints, ensuring referential integrity. Both the RISK_PHRASE_CODE and RISK_PHRASE_CODE_COMBO columns reference the RISK_PHRASE_CODE column in GR_RISK_PHRASES_B. This design means that every code used in a combination must be a valid, predefined risk phrase in the system. The table is likely referenced by various Regulatory Management application forms, reports, and PL/SQL APIs responsible for product safety and regulatory compliance processes, which consume its combination logic to produce final output documents.