Search Results gr_item_exposure




Overview
Explore in AI Chat

Overview

The GR_ITEM_EXPOSURE table is a core data object within the Oracle E-Business Suite Process Manufacturing Regulatory Management (GR) module. It serves as the central repository for storing regulatory exposure limit information for items (products or substances) as defined by specific authorities in different countries. Its primary role is to manage the permissible exposure levels that govern the handling, transportation, and documentation of items to ensure compliance with regional health, safety, and environmental regulations. The table enables the system to control the exposure limit information displayed on shipping and compliance documents, with rules configurable at both the country and document levels.

Key Information Stored

The table's structure is defined by a composite primary key that uniquely identifies each exposure limit record. The key columns, which also serve as foreign keys to related master data tables, are: ITEM_CODE (the specific product or substance), LABEL_CODE (the country or region), EXPOSURE_AUTHORITY_CODE (the governing regulatory body), and EXPOSURE_TYPE_CODE (the category of exposure limit, such as a time-weighted average or a short-term limit). Beyond these key columns, the table typically stores the numerical exposure limit value, the applicable unit of measure, and potentially effective date ranges. This design allows for the precise association of an item with multiple, potentially differing, exposure limits based on jurisdiction and authority.

Common Use Cases and Queries

A primary use case is the generation of compliant shipping documents, such as Safety Data Sheets (SDS) or transport manifests, where the system queries this table to retrieve and print the legally mandated exposure limits for the items being shipped to a specific destination country. Regulatory reporting and internal safety audits also rely on this data. Common SQL queries involve joining to master tables to produce human-readable reports. For example, to list all exposure limits for a specific item:

  • SELECT gie.*, ig.item_name, lb.label_name FROM gr_item_exposure gie, gr_item_general ig, gr_labels_b lb WHERE gie.item_code = ig.item_code AND gie.label_code = lb.label_code AND ig.item_code = 'ITEM123';

Another typical query retrieves the applicable limit for a document line by joining on item, ship-to country, and the relevant authority and type codes defined on the transaction document.

Related Objects

The GR_ITEM_EXPOSURE table maintains integral relationships with several foundational master data tables in the GR module, as defined by its foreign key constraints:

  • GR_ITEM_GENERAL: Joined via GR_ITEM_EXPOSURE.ITEM_CODE = GR_ITEM_GENERAL.ITEM_CODE. This links the exposure data to the base item definition.
  • GR_LABELS_B: Joined via GR_ITEM_EXPOSURE.LABEL_CODE = GR_LABELS_B.LABEL_CODE. This links to the country or regulatory jurisdiction.
  • GR_EXPOSURE_AUTHS_B: Joined via GR_ITEM_EXPOSURE.EXPOSURE_AUTHORITY_CODE = GR_EXPOSURE_AUTHS_B.EXPOSURE_AUTHORITY_CODE. This links to the specific regulatory authority (e.g., OSHA, EU-REACH).
  • GR_EXPOSURE_TYPES_B: Joined via GR_ITEM_EXPOSURE.EXPOSURE_TYPE_CODE = GR_EXPOSURE_TYPES_B.EXPOSURE_TYPE_CODE. This links to the category of the exposure limit.

These relationships ensure data integrity and provide the necessary context for the exposure limit values stored in the GR_ITEM_EXPOSURE table.