Results for “ibe_migration_history”

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

Overview

IBE_MIGRATION_HISTORY is a table owned by the IBE schema within Oracle E-Business Suite, belonging to the IBE – iStore product family. Its documented purpose is to keep track of migration history, meaning it serves as an audit and control record for the process of migrating iStore-related data between environments, releases, or staging schemas. In Oracle EBS 12.1.1 and 12.2.2 the table is marked VALID and contains nine documented columns. It is a low-volume, administrative data object rather than a transactional store; it does not participate in the day-to-day commerce flows of the storefront, but instead records the outcome of migration runs that transform or move iStore configuration and content.

From a heuristic Data Vault modeling perspective, the table is classified as standalone. This classification suggests treating IBE_MIGRATION_HISTORY as an independent satellite-like record set, because the mined FK structure reveals only a single foreign key (to FND_SECURITY_GROUPS via SECURITY_GROUP_ID) and no parent-child dependency within the IBE schema itself. Analysts modeling this object should therefore avoid assuming a hub-and-link relationship with other IBE tables; the migration code is the effective business key, and the remaining attributes are descriptive history.

Key Information Stored

The table's most significant columns, as documented in the ETRM 12.2.2 physical schema, are as follows.

• MIGRATION_CODE – the business-key candidate, protected by the unique index IBE_MIGRATION_HISTORY_U1. It identifies a specific migration run or migration unit and is the column most commonly used for lookups and joins in reporting.
• STATUS – records the state or outcome of the migration (for example completed, failed, or pending), supporting both operational monitoring and historical audit.
• SECURITY_GROUP_ID – the foreign key to FND_SECURITY_GROUPS, tying the migration record to the security group (operating unit context) under which it was executed.
• OBJECT_VERSION_NUMBER – the standard EBS optimistic locking column, used to detect concurrent updates to the row.
• CREATED_BY, CREATION_DATE – the standard who/when audit columns capturing the user and timestamp of the initial insert.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – the standard audit triad capturing the identity, timestamp, and login of the most recent modification.

Because no separate surrogate primary-key column is documented, MIGRATION_CODE functions as the practical unique identifier, while the WHO columns and OBJECT_VERSION_NUMBER follow the standard EBS audit and concurrency conventions. The table is standalone, so no child tables depend on it.

Common Use Cases and Queries

The primary operational use is post-migration verification: confirming which migrations ran, when, and with what outcome. A typical query retrieves the latest migration status for a given code or set of codes.

• Status lookup: SELECT migration_code, status, creation_date, last_update_date FROM ibe.ibe_migration_history WHERE migration_code = :code;
• Recent activity report: SELECT migration_code, status, created_by, creation_date FROM ibe.ibe_migration_history ORDER BY creation_date DESC;
• Failure triage: SELECT migration_code, status FROM ibe.ibe_migration_history WHERE status != 'COMPLETE';
• Security-group context join: SELECT m.migration_code, m.status, s.security_group_name FROM ibe.ibe_migration_history m, fnd_security_groups s WHERE m.security_group_id = s.security_group_id;

Reporting use cases include migration audit trails for change management, reconciliation between source and target environments, and trend analysis of migration success rates over time.

Related Objects

The documented relationship data identifies the following significant objects.

• FND_SECURITY_GROUPS – referenced by IBE_MIGRATION_HISTORY.SECURITY_GROUP_ID; provides the security group / operating unit context for each migration record.
• IBE_MIGRATION_HISTORY_U1 – the unique index on MIGRATION_CODE, enforcing the business key.
• Other IBE iStore administrative tables – logically related migration and configuration control tables in the IBE schema that track setup and content migration activities.
• FND standard audit infrastructure – the CREATED_BY, LAST_UPDATED_BY, and LOGIN columns depend on the FND user and login tables (FND_USER, FND_LOGINS) for identity resolution.

Because the table is standalone with a single documented FK, its relational footprint in EBS is intentionally small; dependencies are limited to FND_SECURITY_GROUPS and the standard FND audit framework.