Results for “concentration_display”

8 results




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

Overview

GR_CONC_RANGES is a reference and configuration table residing in the GR schema, owned by the Process Manufacturing Regulatory Management (GR) product within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the concentration range definitions used by regulatory and compliance calculations, holding one record for each organization code. In regulatory management workflows, concentration thresholds drive hazard classification, labeling, SDS (Safety Data Sheet) generation, and ingredient disclosure logic, so this table supplies the boundary values that downstream GR programs consult when evaluating a material's composition against regulatory limits.

From a data-modeling perspective, the metadata's heuristic Data Vault classification is standalone. This suggests the table functions as an independent reference/lookup entity rather than a strictly dependent child of another hub: it has no mined foreign-key parents and is keyed by a single surrogate sequence, with no documented foreign-key links to other hubs. Where an integration or warehouse model is being built, GR_CONC_RANGES is best treated as a standalone reference set rather than a hub, link, or satellite in the strict Data Vault sense, though its organization-scoped nature invites consideration as a small reference satellite if a natural business key for "organization code" is established externally. No relationship data beyond its own primary key is documented.

Key Information Stored

The table carries nine documented columns. The most significant are:

Because the surviving columns are low/high boundaries plus a display value and audit fields, the table's role is clearly that of a threshold definition list. Organization scoping is referenced in the object description (one record per organization code) but is not evidenced among the documented physical columns for this excerpt; implementers should confirm the organization association against the live 12.2.2 data dictionary before designing joins.

Common Use Cases and Queries

Typical usage centers on retrieving the applicable low/high boundaries for classification and reporting. A simple lookup by primary key is:

SELECT concentration_seqno, concentration_low, concentration_high, concentration_display FROM gr.gr_conc_ranges WHERE concentration_seqno = :seqno;

For presentation-oriented reports, developers frequently select the display string directly. A range-resolution query that locates the band into which a given percentage falls follows the pattern:

SELECT concentration_display FROM gr.gr_conc_ranges WHERE :pct BETWEEN concentration_low AND concentration_high;

Audit and data-stewardship reporting uses the standard EBS columns, for example listing recently changed thresholds via last_updated_by and last_update_date. Because the table is small and reference-like, it is commonly extracted into regulatory BI datasets and cached by PL/SQL validation routines in the GR module.

Related Objects

The provided metadata documents no foreign-key relationships and lists GR_CONC_RANGES as standalone, so no dependent tables or views are confirmed by the FK map. Based on the GR module context, the most significant related objects are process-manufacturing regulatory entities and standard EBS audit references:

  • GR.GR_CONC_RANGES_PK — the unique index enforcing the primary key on CONCENTRATION_SEQNO.
  • Other GR regulatory definition tables (for example, concentration or composition rule tables) that consume these ranges in classification logic, joined by the applicable organization or sequence identifier.
  • Oracle HR / organization definition objects (HR_OPERATING_UNITS, HR_ALL_ORGANIZATION_UNITS) that supply the organization code referenced in the description — subject to confirmation against the live dictionary.
  • Standard audit trail views such as FND_USER (via CREATED_BY / LAST_UPDATED_BY) for stewardship reporting.

Because the FK data is absent, all relationships beyond the primary key should be validated against the actual 12.2.2 schema before being relied upon in custom development.