Search Results gr_labels_b




Overview
Explore in AI Chat

Overview

The GR_LABELS_B table is a core master data table within the Oracle E-Business Suite Process Manufacturing Regulatory Management (GR) module. It serves as the central repository for defining the individual data elements, or "labels," that appear on regulatory and safety documents, such as Material Safety Data Sheets (MSDS) and product labels. Each record in this table represents a specific piece of information (e.g., boiling point, flash point, hazard classification) and defines its fundamental attributes for document generation. The table's primary role is to provide the structural and textual building blocks that, when organized into label classes, determine the precise format and content of compliance documentation.

Key Information Stored

The table's structure is designed to uniquely identify and describe each label. The primary key, LABEL_CODE, is a unique identifier for the label definition. A critical foreign key, LABEL_CLASS_CODE, associates the label with a specific grouping or section in a document as defined in the GR_LABEL_CLASSES_B table. Another significant foreign key, SAFETY_CATEGORY_CODE, links the label to a defined safety category in GR_SAFETY_CATEGORIES_B. While the full column list is not detailed in the excerpt, typical columns would include fields to control the label's display sequence, formatting rules, data type, and a reference to the default text or translatable description (handled via the related GR_LABELS_TL translation table).

Common Use Cases and Queries

This table is central to configuring and generating regulatory documents. Common use cases include setting up document templates for a new country's regulations, modifying the display of hazard information, or troubleshooting missing data on an MSDS. A typical reporting query would join this table to its translation and class tables to extract a list of all labels for a specific document section. For example, to list all labels within the 'PHYSICAL_CHARS' class, one might use:

  • SELECT glb.LABEL_CODE, glt.DESCRIPTION, glb.LABEL_CLASS_CODE FROM GR.GR_LABELS_B glb, GR.GR_LABELS_TL glt WHERE glb.LABEL_CODE = glt.LABEL_CODE AND glb.LABEL_CLASS_CODE = 'PHYSICAL_CHARS' AND glt.LANGUAGE = USERENV('LANG');

Another critical query pattern involves tracing label usage to specific items by joining through intermediary tables like GR_ITEM_EXPOSURE or GR_ITEM_TOXIC.

Related Objects

The GR_LABELS_B table has extensive relationships, acting as a key referenced entity within the GR schema. Its primary key (LABEL_CODE) is referenced by numerous other tables, as documented in the foreign key metadata:

  • GR_LABELS_TL: Stores translated descriptions for the label (GR_LABELS_TL.LABEL_CODE).
  • GR_LABEL_CLASSES_B: Parent table defining the class grouping (GR_LABELS_B.LABEL_CLASS_CODE references GR_LABEL_CLASSES_B).
  • GR_SAFETY_CATEGORIES_B: Parent table for safety categorization (GR_LABELS_B.SAFETY_CATEGORY_CODE references GR_SAFETY_CATEGORIES_B).
  • GR_COUNTRY_PROFILES: References labels for default exposure and toxic categories (GR_COUNTRY_PROFILES.LABEL_CODE_EXPOSURE, .LABEL_CODE_TOXIC).
  • GR_DOCUMENT_STRUCTURES: Uses labels to define document layout (GR_DOCUMENT_STRUCTURES.LABEL_CODE).
  • GR_ITEM_EXPOSURE & GR_ITEM_TOXIC: Link specific items to their assigned exposure and toxic labels (GR_ITEM_EXPOSURE.LABEL_CODE, GR_ITEM_TOXIC.LABEL_CODE).
  • GR_LABEL_PROPERTIES & GR_LABEL_PROD_CLASSES: Store additional attributes and product class associations for the label.
  • GR_GENERIC_ML_NAME_TL & GR_MULTILINGUAL_NAME_TL: Reference labels for multilingual name management.