Results for “instance_label”

2 results




Overview
Explore in AI Chat

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

Overview

The ONT.OE_ACTION_PRE_REQS table is a legacy Order Management object within the Oracle E-Business Suite, documented as VALID in the ONT schema under the Order Management (ONT) product. Per the ETRM metadata, its defining purpose is narrow and historical: it is described as "a temporary table used during the WF upgrade into R11i." This indicates the object was created to stage intermediate data required when migrating workflow (WF) definitions and their associated cycle/action dependencies into the Release 11i architecture. It is not a transactional table used by day-to-day order capture, pricing, or fulfillment processing, and it does not participate in the standard Order Management entity lifecycle.

A heuristic Data Vault classification derived from the foreign key structure places this table as standalone. From a modeling perspective, this suggests the object does not function as a true hub, link, or satellite in a dimensional or ensemble model; it is better treated as a transient staging or migration artifact rather than a persistent integration target. In EBS 12.1.1 and 12.2.2 environments, the table typically persists as a residual upgrade object, retained for schema compatibility even where the original upgrade path is no longer executed.

Key Information Stored

The documented physical schema for ETRM 12.2.2 lists 11 columns. The most significant are:

  • CYCLE_ACTION_ID — The principal relationship column, carrying the foreign key reference to SO_CYCLE_ACTIONS. It links the staged row back to a specific cycle action definition, making it the central join key for reconstruction of upgrade data.
  • ACTION_ID — Identifies the workflow action associated with the cycle action being reconciled during the upgrade.
  • RESULT_ID — Captures the result or outcome identifier attached to the staged action, used to reconstruct action-to-result mappings.
  • GROUP_NUMBER — A grouping ordinal, likely used to batch or sequence staged rows during processing.
  • INSTANCE_LABEL and INSTANCE_ID — A paired label/identifier for a workflow instance reference; the label provides a human-readable name while the ID carries the surrogate value.
  • INSTANCE_LABEL2 and INSTANCE_ID2 — A secondary instance reference pair, indicating the staging table could hold two related instance references per row.
  • CYCLE_ID — Identifies the parent cycle to which the staged action belongs.
  • TYPE and LINE_TYPE — Classification columns distinguishing the nature of the staged action and the line category being processed.

The metadata does not document a primary key constraint, and no unique index is reported; CYCLE_ACTION_ID serves as the de facto business-key candidate through its foreign key relationship rather than as a guaranteed surrogate key.

Common Use Cases and Queries

Practical use of this table is limited to upgrade archaeology and data cleanup. Typical scenarios include:

  • Verifying whether a completed R11i upgrade left residual staging rows that can be purged.
  • Auditing the migration of cycle action definitions by comparing staged rows against the surviving SO_CYCLE_ACTIONS records.
  • Diagnosing orphaned or unreconciled workflow action data after an upgrade.

Representative query patterns join the staging table to its FK parent:

  • SELECT p.CYCLE_ACTION_ID, p.ACTION_ID, p.RESULT_ID, c.* FROM ONT.OE_ACTION_PRE_REQS p, ONT.SO_CYCLE_ACTIONS c WHERE p.CYCLE_ACTION_ID = c.CYCLE_ACTION_ID;
  • Row-count and residue checks: SELECT COUNT(*) FROM ONT.OE_ACTION_PRE_REQS;
  • Detection of unmatched staging rows: SELECT p.* FROM ONT.OE_ACTION_PRE_REQS p WHERE NOT EXISTS (SELECT 1 FROM ONT.SO_CYCLE_ACTIONS c WHERE c.CYCLE_ACTION_ID = p.CYCLE_ACTION_ID);

No seeded concurrent program or standard Order Management report is documented as consuming this table.

Related Objects

The documented relationship data identifies one foreign key dependency. The most significant related objects are:

  • ONT.SO_CYCLE_ACTIONS — The FK parent referenced by OE_ACTION_PRE_REQS.CYCLE_ACTION_ID; the primary and most important join target.
  • ONT.SO_CYCLE_ACTION_RESULTS — The natural companion to SO_CYCLE_ACTIONS and the likely source of the staged RESULT_ID values.
  • ONT.SO_CYCLES — The parent cycle table corresponding to the staged CYCLE_ID.
  • ONT.OE_ACTIONS — The action definition source aligned with the staged ACTION_ID.
  • WF_ITEM_ACTIVITY_STATUSES / WF_ITEM_ATTRIBUTES — Workflow runtime tables relevant to the WF upgrade context.

Because the object is classification-standalone, no other tables depend on it as a parent; its role is strictly that of a dependent staging artifact referencing SO_CYCLE_ACTIONS.