Search Results exp_imp_id




Overview
Explore in AI Chat

Overview

HR_DM_AOL_DOWN_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the PER (Human Resources) product family, but its functional purpose is technical rather than business-facing: it exposes configuration rows that drive the AOL (Application Object Library) download phase of the Oracle HRMS Data Migration / DataMage utility. The view description states explicitly that it holds the "AOL loader plus parameters used during the AOL download phase."

The object is classified as VALID in the ETRM repository, and its documented status reflects a stable, packaged component rather than a customer-modified artifact. In practice, the view functions as a thin, filtered projection over a single control table, presenting the migration identifier, phase item identifier, and AOL code that the DataMage loader requires when it stages AOL definitions (menus, functions, responsibilities, and related setup) for extraction and subsequent import into a target instance.

The object surfaced in a user search for the term exp_imp_id, which is the primary key column of the underlying control table and the leading column of this view. This search pattern typically indicates an investigation into how the DataMage framework tracks individual migration requests, or a diagnostic review of stalled or failed AOL download jobs.

Underlying Base Objects

The view is defined over exactly one documented base object: the synonym HR_DM_EXP_IMPS, which resolves to the APPS-owned export/import control table used by the HR DataMage utility. The dependency is total — no joins, unions, or subqueries appear in the view definition. The relationship is therefore one of simple projection and filtering: HR_DM_EXP_IMPS holds all migration rows across every DataMage phase and component, while HR_DM_AOL_DOWN_V isolates the subset relevant to the AOL download step.

The filtering predicate is a literal self-reference: WHERE TABLE_NAME = 'HR_DM_AOL_DOWN_V'. Rows in HR_DM_EXP_IMPS that name this view as their target object are precisely those that parameterize the AOL download phase. Consequently, the cardinality of the view is small and tightly bounded. Because the base object is exposed through a synonym and the view carries APPS ownership, any session with standard EBS responsibility-level access can query it without direct grants on the underlying table.

Key Columns

Five columns are projected by the view. Two are passed through unmodified; three are aliased from generic parameter columns, which is the characteristic signature of the DataMage parameter-staging design.

  • EXP_IMP_ID — The unique identifier of the export/import record in HR_DM_EXP_IMPS. This is the key value most commonly used to correlate the view with concurrent request logs, other DataMage phase views, and troubleshooting queries.
  • TABLE_NAME — The target object name for the row. Within this view the value is always the constant 'HR_DM_AOL_DOWN_V', since the view itself enforces that predicate.
  • MIGRATION_ID — Aliased from PVAL001. Identifies the parent migration or migration set to which this AOL download step belongs, allowing multiple phase rows to be grouped under one logical migration run.
  • PHASE_ITEM_ID — Aliased from PVAL002. Identifies the individual phase item or step within the migration, giving ordering and granularity to the download activity.
  • CODE — Aliased from PVAL003. Carries the AOL code value associated with the step, such as the loader identifier or object code used by the AOL download routine.

Common Use Cases and Queries

Typical usage falls into three areas: confirming that an AOL download phase has been configured for a given migration, retrieving the parameters passed to the AOL loader, and tracing a failed concurrent request back to its controlling migration record.

The simplest access pattern returns all configured AOL download steps:

  • SELECT exp_imp_id, migration_id, phase_item_id, code FROM apps.hr_dm_aol_down_v ORDER BY exp_imp_id;

To examine a specific migration run, constrain on the aliased parameter:

  • SELECT exp_imp_id, phase_item_id, code FROM apps.hr_dm_aol_down_v WHERE migration_id = :migration_id;

To reconcile the view against its base catalog entry — useful when validating that a phase row exists at all — join back to the underlying table, taking care that the join predicate matches the view's internal filter:

  • SELECT v.exp_imp_id, e.pval001, e.pval002, e.pval003 FROM apps.hr_dm_aol_down_v v, apps.hr_dm_exp_imps e WHERE e.exp_imp_id = v.exp_imp_id;

Because the view is read-only and derived from a control table, direct DML against it is not supported. Modifications to DataMage phase configuration must be performed through the HRMS DataMage concurrent programs or, where documented, against HR_DM_EXP_IMPS itself. Queries should be executed with the APPS schema in the session's search path to resolve the synonym correctly.