Search Results gr_item_concentrations_pk

Overview

The GR_ITEM_CONCENTRATIONS table is a core data structure within the Oracle E-Business Suite (EBS) Process Manufacturing Regulatory Management (GR) module. It functions as a temporary staging table, specifically designed to hold intermediate data during the automated document build process. This process is critical for generating regulatory and compliance documentation, such as safety data sheets (SDS) or product specification sheets, where precise ingredient concentration information is legally mandated. The table's primary role is to facilitate the accurate aggregation and calculation of ingredient concentrations for finished goods or intermediate items before the final regulatory document is assembled and published.

Key Information Stored

The table is designed to store concentration data at a summary level, keyed by a specific item and its constituent ingredients. Its structure is defined by a composite primary key, ensuring a unique record for each item-ingredient combination. The key columns are ITEM_CODE, which identifies the finished good or formulation, and INGREDIENT_ITEM_CODE, which identifies a specific component within that formulation. While the provided metadata does not list all data columns, the table's purpose implies it likely stores calculated concentration percentages, ranges, or flags related to regulatory thresholds. The existence of a related detail table (GR_ITEM_CONC_DETAILS) suggests this table may hold summarized or header-level concentration information derived from more granular data.

Common Use Cases and Queries

The primary use case is the batch-driven generation of regulatory documents. A concurrent program likely populates this table with current concentration data from the product formulation (e.g., Bills of Material) and inventory systems before the document engine references it. Common queries would involve selecting all ingredients for a given item to list in a document or verifying concentration levels against regulatory limits. A typical reporting pattern would join this table to item master data.

SELECT gic.ITEM_CODE,
       gic.INGREDIENT_ITEM_CODE,
       ig.ITEM_DESCRIPTION
FROM GR.GR_ITEM_CONCENTRATIONS gic,
     GR.GR_ITEM_GENERAL ig
WHERE gic.INGREDIENT_ITEM_CODE = ig.ITEM_CODE
  AND gic.ITEM_CODE = :p_item_code;

Data in this table is typically transient, being populated and purged within the scope of a single document build job.

Related Objects

• Primary Key: GR_ITEM_CONCENTRATIONS_PK (on columns ITEM_CODE, INGREDIENT_ITEM_CODE).
• Referenced Foreign Key (Outbound): The ITEM_CODE column references the GR_ITEM_GENERAL table. This establishes that any item in GR_ITEM_CONCENTRATIONS must be a valid regulatory item defined in the general master table.
• Referencing Foreign Key (Inbound): The GR_ITEM_CONC_DETAILS table references GR_ITEM_CONCENTRATIONS via its ITEM_CODE and INGREDIENT_ITEM_CODE columns. This creates a parent-child relationship where GR_ITEM_CONCENTRATIONS is the header and GR_ITEM_CONC_DETAILS contains supporting detail records, such as concentration data for specific sub-lots, batches, or under different regulatory contexts.