Results for “so_item_groups”

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

Overview

SO_ITEM_GROUPS is an Oracle Order Entry (OE) base table that defines price list item groups. It resides in the OE schema and carries a VALID status in the E-Business Suite 12.1.1 and 12.2.2 data model. The table serves as a classification mechanism by which sets of orderable items are grouped together and subsequently referenced by pricing, order sourcing, and warehouse picking logic. Rather than holding transactional lines, SO_ITEM_GROUPS supplies the named group definitions that other functional tables consume through foreign key relationships.

From a Data Vault modeling perspective, the documented foreign key structure suggests a hub-leaning classification. The table functions primarily as a durable business entity whose surrogate identifier, GROUP_ID, is referenced by multiple dependent tables. A Data Vault implementation would therefore typically model SO_ITEM_GROUPS as a hub, with descriptive attributes such as NAME and DESCRIPTION carried in an associated satellite. This is a heuristic suggestion derived from the foreign key topology, not a prescribed EBS design.

Key Information Stored

The table contains 24 documented columns. The most significant are:

• GROUP_ID — The surrogate primary key, enforced by SO_ITEM_GROUPS_PK and also by the unique index SO_ITEM_GROUPS_U1. Every downstream reference from other application tables resolves through this column.
• NAME — The business-key candidate for the group, enforced by the unique index SO_ITEM_GROUPS_U2. This provides the human-readable identifier presented to users when selecting or maintaining an item group.
• DESCRIPTION — Free-text description of the group's purpose or contents.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — The standard Oracle EBS WHO columns providing auditability of record creation and maintenance.
• CONTEXT — The descriptive flexfield context column enabling attribute-based extensibility.
• ATTRIBUTE1 through ATTRIBUTE15 — The fifteen descriptive flexfield segment columns available for customer-specific extensions without schema modification.

The distinction between the surrogate key and the business key is important. GROUP_ID is system-generated and should be used for joins, while NAME is the unique, user-facing identifier enforced by the SO_ITEM_GROUPS_U2 index. The remaining columns are largely administrative or extensibility-related and are not required for typical reporting.

Common Use Cases and Queries

Typical usage centers on resolving group membership and tracing which business processes depend on a given group. A common reporting pattern joins the group definition to its line-level members to enumerate items in a named group:

• Retrieve a group by business key: SELECT group_id, name, description FROM oe.so_item_groups WHERE name = :group_name;
• Enumerate group members: SELECT g.name, l.* FROM oe.so_item_groups g, oe.so_item_group_lines l WHERE g.group_id = l.group_id AND g.name = :group_name;
• Identify picking rules or batches referencing a group: SELECT p.* FROM oe.so_picking_rules p WHERE p.group_id = :group_id;
• Audit recently maintained groups: SELECT name, last_updated_by, last_update_date FROM oe.so_item_groups ORDER BY last_update_date DESC;

These patterns support pricing administration reports, warehouse picking configuration inquiries, and data migration validation where group names must reconcile against legacy values.

Related Objects

Four documented dependent tables reference SO_ITEM_GROUPS through the GROUP_ID column:

• SO_ITEM_GROUP_LINES — Stores the individual items assigned to each group via SO_ITEM_GROUP_LINES.GROUP_ID.
• SO_PICKING_BATCHES_ALL — Associates picking batches with the item group via SO_PICKING_BATCHES_ALL.GROUP_ID.
• SO_PICKING_RULES — Defines picking rules scoped to a group via SO_PICKING_RULES.GROUP_ID.
• SO_PRICE_COPY_PARAMETERS — Uses the group identifier in price copy operations via SO_PRICE_COPY_PARAMETERS.GROUP_ID.

Together these relationships confirm the table's role as a shared reference hub for pricing and warehouse execution within Order Entry.