Results for “category_value”

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

Overview

The GR.GR_WORK_SAFETY_PHRASES table resides in the GR schema, which supports the Process Manufacturing Regulatory Management (GR) module of Oracle E-Business Suite. It is a valid, documented object in both EBS 12.1.1 and 12.2.2. Per the ETRM documentation, the table "contains a temporary table used during the document build process." This characterization is significant: rather than serving as a persistent master or transactional store, GR_WORK_SAFETY_PHRASES functions as a staging or work area populated transiently while the regulatory document generation engine assembles safety phrase content for items under a given session.

Records are scoped by SESSION_ID, meaning each document build run or user session writes its own isolated set of rows. Once the build completes, rows tied to that session may be purged or overwritten. The heuristic Data Vault classification is standalone, suggesting no foreign-key dependencies were mined from the schema; from a modeling perspective this object behaves most like a satellite attached to a session-level parent, carrying descriptive attributes about safety phrases rather than acting as a hub or link in its own right.

Key Information Stored

The documented physical schema records nine columns. The most operationally important are:

• SESSION_ID — Identifies the document build session that produced the row; the primary partitioning and scoping key.
• ITEM_CODE — The item for which safety phrase evaluation is performed.
• SAFETY_PHRASE_CODE — The regulatory safety phrase being considered or emitted.
• SAFETY_RULE_LEVEL — The rule tier governing phrase selection.
• SAFETY_RULE_GROUP — The grouping construct used to organize rules during evaluation.
• SAFETY_CATEGORY_CODE — The category under which the phrase is classified.
• CATEGORY_VALUE — The resolved value associated with the category.
• RECOMMENDED_OBLIGATORY_IND — Indicates whether the phrase is advisory (recommended) or mandatory (obligatory).
• ASSIGN_FLAG — Signals whether the phrase has been assigned into the final document output.

The surrogate primary key is GR_WORK_SAFETY_PHRASES_PK, a composite of SESSION_ID, ITEM_CODE, SAFETY_PHRASE_CODE, SAFETY_RULE_LEVEL, SAFETY_RULE_GROUP, and SAFETY_CATEGORY_CODE. The same column set is documented as the sole unique index, so it doubles as the business-key candidate. Note that CATEGORY_VALUE, RECOMMENDED_OBLIGATORY_IND, and ASSIGN_FLAG are non-key attributes.

Common Use Cases and Queries

Because the table is session-scoped and temporary by design, the principal use case is diagnostic: inspecting what a specific document build produced or determined for a set of items. A typical pattern inspects all rows for the most recent session:

SELECT item_code, safety_phrase_code, safety_category_code, recommended_obligatory_ind, assign_flag
FROM gr.gr_work_safety_phrases
WHERE session_id = :p_session_id ORDER BY item_code, safety_phrase_code;

Analysts may want to compare which phrases were recommended versus obligatory and whether each was actually assigned:

SELECT recommended_obligatory_ind, assign_flag, COUNT(*)
FROM gr.gr_work_safety_phrases
WHERE session_id = :p_session_id
GROUP BY recommended_obligatory_ind, assign_flag;

Because rows are transient, the table should never be treated as a reporting source of record. Persistent safety phrase definitions and assignments reside in the GR configuration tables, and production extracts should join to those objects. Queries should always constrain on SESSION_ID to avoid scanning unrelated build sessions and to respect the composite primary key.

Related Objects

The mined relationship data classifies this object as standalone, meaning no foreign keys were surfaced to sibling tables. In practice, the following objects are the most relevant contextually, joined on the columns shown:

• GR_SAFETY_PHRASES (or equivalent phrase master) — source definitions joined via SAFETY_PHRASE_CODE.
• GR_SAFETY_RULES — rule definitions joined via SAFETY_RULE_LEVEL, SAFETY_RULE_GROUP.
• GR_SAFETY_CATEGORIES — category reference joined via SAFETY_CATEGORY_CODE.
• GR_ITEM_SAFETY_PHRASES — item-level assignments joined via ITEM_CODE and SAFETY_PHRASE_CODE.
• MTL_SYSTEM_ITEMS_B — item validation joined via ITEM_CODE to SEGMENT1.
• GR_DOCUMENT_BUILD_SESSIONS (or the session control table) — parent session joined via SESSION_ID.

Where these join targets exist, they provide the persistent counterpart to the transient work rows, and referencing them is essential for any authoritative regulatory reporting.