Results for “status_code”
8 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
RRS_LOC_TRADE_AREA_GRPS is a Site Management table owned by the RRS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It defines the association between operational locations and trade area groups, establishing which trade areas are assigned to a given site and, through the IS_PRIMARY_FLAG column, which of those assignments serves as the primary trade area for that location. In the RRS (Site Management / Retail and site operations) model, this table acts as the configuration bridge that drives trade-area-based reporting, planning, and site hierarchy logic.
The ETRM metadata classifies this object, using a heuristic Data Vault analysis mined from its foreign-key structure, as a standalone entity. In Data Vault modeling terms this is best treated as a modeling suggestion rather than a strict rule: the table is a link-style resolver between locations and trade area groups, but the absence of a documented multi-parent foreign-key web within the metadata means it can also be modeled as a standalone reference/link table without dedicated hub ancestors. Practitioners designing a Data Vault or dimensional layer over RRS should confirm actual parent relationships against the live schema before finalizing the model.
Key Information Stored
The table is documented with 10 physical columns. The most significant are summarized below; surrogate and business-key roles are distinguished where the metadata documents them.
- GROUP_ID — Identifier of the trade area group. Part of the composite primary key.
- LOCATION_ID — Identifier of the location (site) to which the trade area group is assigned. Part of the composite primary key.
- IS_PRIMARY_FLAG — Indicates whether this trade area group assignment is the primary one for the location.
- STATUS_CODE — Lifecycle or activation status of the relationship record.
- OBJECT_VERSION_NUMBER — Optimistic locking column used by the EBS framework to detect concurrent updates.
- CREATED_BY, CREATION_DATE — Standard WHO columns recording the creating user and timestamp.
- LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO columns recording the last modifying user, timestamp, and login.
The composite surrogate primary key is defined as RRS_LOC_TRADE_AREA_GRPS_PK (GROUP_ID, LOCATION_ID). A separate unique index, RRS_LOC_TRADE_AREA_GRPS_U1 (LOCATION_ID, GROUP_ID), serves as the business-key candidate, enforcing uniqueness on the location-to-group pairing. Because the primary key and the unique index contain the same two columns in reversed order, the table enforces that any given location can be associated with a trade area group only once.
Common Use Cases and Queries
Typical scenarios include retrieving the trade area groups for a site, determining the primary trade area, and joining to location and trade area group reference tables for reporting. Common query patterns include:
- Listing all trade area groups for a specific location:
SELECT GROUP_ID, IS_PRIMARY_FLAG, STATUS_CODE FROM rrs.rrs_loc_trade_area_grps WHERE LOCATION_ID = :location_id. - Identifying the primary assignment: filter on
IS_PRIMARY_FLAG = 'Y'and an activeSTATUS_CODE. - Reporting joins against location and group reference tables using LOCATION_ID and GROUP_ID as the join keys.
- Data auditing, using CREATION_DATE, LAST_UPDATE_DATE, and OBJECT_VERSION_NUMBER to trace changes over time.
Related Objects
As a standalone object per the metadata, the table has no documented child foreign keys. The most significant related objects are those supplying the LOCATION_ID and GROUP_ID values and consuming the assignment:
- Location master/reference table — joined on
LOCATION_IDto resolve site details. - Trade area group master/reference table — joined on
GROUP_IDto resolve group attributes. - RRS_LOC_TRADE_AREA_GRPS_PK — the composite primary key constraint.
- RRS_LOC_TRADE_AREA_GRPS_U1 — the unique business-key index on (LOCATION_ID, GROUP_ID).
- Standard RRS location/site management views and concurrent programs that read and maintain trade area assignments.
-
This table stores the information related to Trade Area Groups
-
This table stores the association between Trade Area Groups and Locations
-
This table stores information about how a site is used. Site can have multiple uses, for example Store , Distribution Centre , Mail Box etc.
-
Trade Area Primary Attribute Group
-
Trade Area Primary Attribute Group