Results for “unit_of_measure_code”

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

Overview

The RRS_TRADE_AREA_GROUPS_B table is a core base table within the Oracle E-Business Suite (EBS) Site Management module (product code RRS), introduced to support downstream energy trading operations. Its purpose is to store the definition of trade area groups — logical groupings of geographic or commercial trade areas used to organize pricing, scheduling, and contractual activity for crude oil, natural gas, refined products, and related commodities handled by the ETRM (Energy and Commodity Trading) application.

The table resides in the RRS schema and is flagged VALID in Oracle EBS 12.1.1 and 12.2.2. It serves as the master definition of a group header; descriptive, multi-language text is stored separately in RRS_TRADE_AREA_GROUPS_TL, and the detailed membership of trade areas within each group is held in RRS_GROUP_TRADE_AREAS. From a Data Vault modeling perspective, the mined metadata classifies this object as hub-leaning: it contains a surrogate key (GROUP_ID) and relatively few foreign dependencies, making it a plausible candidate hub around which satellites (translated text, membership) and links (group-to-trade-area associations) revolve. This classification is offered as a modeling suggestion, not a documented Oracle construct.

Key Information Stored

The table physically comprises 11 columns. The most significant are summarized below.

• GROUP_ID — The surrogate primary key (constraint RRS_TRADE_AREA_GROUPS_PK) that uniquely identifies each trade area group. It is also the sole documented unique index candidate (RRS_TRADE_AREA_GROUPS_B_U1), meaning it acts as both the surrogate and the business-key anchor. All child tables join to this column.
• GROUP_TYPE_CODE — The classification code that distinguishes the operational type or category of the group.
• NUM_OF_TRADE_AREAS — A denormalized count of the trade areas associated with the group, typically maintained for fast list-of-values and reporting retrieval.
• STATUS_CODE — The lifecycle state of the group (for example active versus inactive), driving eligibility in downstream trading documents.
• UNIT_OF_MEASURE_CODE — The unit of measure applicable to quantities associated with trade areas in the group.
• OBJECT_VERSION_NUMBER — The optimistic-locking column standard across OAF-based EBS tables.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — The standard Oracle "WHO" audit columns capturing user identity and timestamps for insert and update operations.

Common Use Cases and Queries

The primary operational use case is maintaining and reporting on group-to-trade-area hierarchies that feed trade capture, allocations, and settlement. Typical queries include:

• Listing active groups with their member counts: SELECT group_id, group_type_code, num_of_trade_areas FROM rrs_trade_area_groups_b WHERE status_code = 'ACTIVE';
• Resolving group description through the translation table: SELECT b.group_id, t.description FROM rrs_trade_area_groups_b b, rrs_trade_area_groups_tl t WHERE b.group_id = t.group_id AND t.language = USERENV('LANG');
• Enumerating the trade areas for a given group: SELECT g.group_id, g.trade_area_id FROM rrs_group_trade_areas g WHERE g.group_id = :p_group_id;
• Audit and change-tracking reports relying on last_updated_by and last_update_date.

Related Objects

The following objects are most significant to the integrity and usability of this table:

• RRS_GROUP_TRADE_AREAS — child/link table joined via GROUP_ID, holding the many-to-many membership of trade areas within each group.
• RRS_TRADE_AREA_GROUPS_TL — the translation table storing language-specific names and descriptions, joined via GROUP_ID.
• RRS_TRADE_AREAS — the trade area master referenced indirectly through the group link table.
• Standard OAF/ADF-based RRS Site Management UI pages that expose group maintenance and validation APIs built on this base table.