Search Results split_id

Overview

OKS_ITEM_SPLIT_V is a Service Contracts (OKS) dictionary view in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the item-level detail associated with contract line splits, capturing the state of a service item before and after a split operation. The view is defined as a thin projection over the base table OKS_ITEM_SPLIT, aliased internally as ISPLV, and carries every column of that table without joins, filters, or aggregation. Its role in EBS reporting and integration is therefore one of read-only abstraction: external interfaces, concurrent programs, and custom reports can query a stable, named view rather than referencing the base table directly, while the underlying OKS code retains freedom to evolve the physical storage. Because splits alter which inventory item and organization are responsible for servicing a contract line, this view is the primary source for reconciling pre-split and post-split item attribution, pricing precedence, and effective dating.

Underlying Base Objects

The documented metadata states that the view is not implemented in the reference database and that no base objects are documented beyond the statement text. The view text, however, unambiguously identifies the single source object: OKS_ITEM_SPLIT. No other tables, synonyms, or views are referenced in the SELECT list; all columns are projected directly from the alias ISPLV. Consequently, the relationship between view and base table is one-to-one at the row level, with ROWID surfaced as ROW_ID to preserve row identity for update-through-view or diagnostic purposes. There are no outer joins to OKS contract headers, OKS lines, or inventory master tables, so consumers requiring descriptive item or organization attributes must join to INV_ORG or MTL_SYSTEM_ITEMS separately.

Key Columns

• ROW_ID — the ROWID of the base table row, exposed for unique identification and direct row access.
• ID — primary key of the split-item record.
• ITEM_ID — inventory item identifier for the item participating in the split.
• INV_ORGANIZATION_ID — the inventory organization that owns the item; this is the column most frequently searched, because it determines which warehouse or business unit is accountable for the serviced item.
• ORG_ID — the operating unit (multi-org) identifier, enforcing data security and reporting partitions.
• START_DATE / END_DATE — the effective date range during which this item-to-split assignment is valid.
• SPLIT_ID — groups related rows belonging to the same split event.
• PRECEDENCE — ordering value used when multiple items apply to the same split.
• PRICE_ENGINE_FLAG — indicates whether the row participates in price engine processing.
• OBJECT_VERSION_NUMBER — optimistic locking token used by the OKS framework.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the standard EBS descriptive flexfield columns for client-specific extensions.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN provide standard who-column tracking.

Common Use Cases and Queries

Typical scenarios include determining which inventory organization now services an item after a contract line split, auditing split history within a date range, and validating that price engine flags and precedence values were set correctly. A representative query filtering on the searched column is:

• SELECT ID, ITEM_ID, INV_ORGANIZATION_ID, SPLIT_ID, START_DATE, END_DATE, PRECEDENCE FROM OKS_ITEM_SPLIT_V WHERE INV_ORGANIZATION_ID = :org_id AND TRUNC(SYSDATE) BETWEEN START_DATE AND NVL(END_DATE, TRUNC(SYSDATE));
• SELECT SPLIT_ID, COUNT(*) FROM OKS_ITEM_SPLIT_V GROUP BY SPLIT_ID HAVING COUNT(*) > 1; to detect multi-item splits.
• SELECT v.ID, v.ITEM_ID, m.segment1 FROM OKS_ITEM_SPLIT_V v, MTL_SYSTEM_ITEMS m WHERE v.ITEM_ID = m.INVENTORY_ITEM_ID AND v.INV_ORGANIZATION_ID = m.ORGANIZATION_ID; to resolve item descriptions.

Because ORG_ID governs multi-org security, integration queries must always supply or inherit the correct operating unit context; failure to do so returns rows across organizations and can distort split reconciliation. Joins to MTL_SYSTEM_ITEMS on both ITEM_ID and INV_ORGANIZATION_ID are required to obtain item names, since the view itself stores identifiers only.