Results for “oco_38365034”
6 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
IBE_MSITE_ORGS is a transactional configuration table in the IBE (iStore) product module of Oracle E-Business Suite, owned by the IBE schema. Its documented purpose is to define the organizations supported by the mini-sites. In iStore implementations, a mini-site is a customer- or partner-facing storefront partition that exposes only a scoped set of catalog content, price lists, and ordering privileges. IBE_MSITE_ORGS provides the association layer that limits each mini-site to an explicit whitelist of operating units or inventory organizations, thereby governing which organizations can transact through that storefront.
The table exists in both Oracle EBS 12.1.1 and 12.2.2, where it holds ten documented columns in the ETRM 12.2.2 physical schema. Its heuristic Data Vault classification, mined from the foreign-key structure, is satellite-leaning. This is a modeling suggestion rather than a functional designation: the table records descriptive relationships and attributes surrounding the IBE_MSITES_B master rather than acting as a pure many-to-many junction. Practically, it behaves as a dependent child of the mini-site header with an additional organizational scope reference.
Key Information Stored
The table's surrogate primary key is MSITE_ORG_ID, implemented through the constraint identified as OCO_38365034. A second documented unique index, OCO_38365036, covers MSITE_ID in combination with ORG_ID, making the (MSITE_ID, ORG_ID) pair the business-key candidate that enforces one row per organization per mini-site. The two substantive foreign-key columns are:
- MSITE_ID — references IBE_MSITES_B, the mini-site header. This column anchors each scope record to a specific storefront.
- ORG_ID — the organization identifier supported by that mini-site. This is the operating unit or inventory organization context used by iStore for pricing, availability, and order capture.
Standard EBS WHO columns are also documented: OBJECT_VERSION_NUMBER, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN. These support concurrent-program-safe updates and auditability, with OBJECT_VERSION_NUMBER enabling optimistic locking during DML through the Oracle Applications framework. SECURITY_GROUP_ID references FND_SECURITY_GROUPS, applying the standard Multi-Org security model to the row.
Common Use Cases and Queries
The most common reporting requirement is resolving the organizations enabled for a given mini-site, typically joined to the mini-site header and to HR operating unit definitions for readable names:
SELECT m.MSITE_ID, m.MSITE_NAME, o.ORG_ID, o.NAME FROM IBE.IBE_MSITE_ORGS s, IBE.IBE_MSITES_B m, HR_OPERATING_UNITS o WHERE s.MSITE_ID = m.MSITE_ID AND s.ORG_ID = o.ORGANIZATION_ID AND m.MSITE_ID = :p_msite_id;
Validation queries detect mini-sites with no organization mapping, which would prevent ordering or pricing resolution. Reverse-lookup queries identify every mini-site that exposes a particular organization, useful during organization closures or security reviews. Because the table is seed-style configuration rather than high-volume transaction data, a full-table scan is acceptable in most reporting contexts.
Related Objects
- IBE_MSITES_B — joined on IBE_MSITE_ORGS.MSITE_ID = IBE_MSITES_B.MSITE_ID; the parent mini-site header.
- FND_SECURITY_GROUPS — joined on IBE_MSITE_ORGS.SECURITY_GROUP_ID; enforces Multi-Org security group restriction.
- HR_OPERATING_UNITS / HR_ALL_ORGANIZATION_UNITS — resolves ORG_ID to a displayable organization name.
- IBE_MSITES_TL — the translatable mini-site name and description table for the header.
- IBE_MSITE_CONTENT / IBE_MSITE_PRICES and related mini-site content tables — share the MSITE_ID scope key.
- IBE_ORDERS / OE_ORDER_HEADERS_ALL — downstream order capture where ORG_ID determines the transactional organization for the storefront.
Collectively, these relationships establish IBE_MSITE_ORGS as a configuration dependency for iStore storefront behavior, and modification of its rows should be treated as a controlled setup change rather than routine data maintenance.
-
Define the organizations supported by the mini-sites
-
Define the organizations supported by the mini-sites
-
eTRM - IBE Tables and Views 12.1.1
This table stores information about supported Work Flow notifications in iStore.
-
eTRM - IBE Tables and Views 12.2.2
This table stores information about supported Work Flow notifications in iStore.
-
eTRM - IBE Tables and Views 12.1.1
This table stores information about supported Work Flow notifications in iStore.
-
eTRM - IBE Tables and Views 12.2.2
This table stores information about supported Work Flow notifications in iStore.