Search Results loader_config_file




Overview
Explore in AI Chat

Overview

APPS.HR_DM_AOL_FILES_V is a reporting and configuration view in the Oracle E-Business Suite Human Resources (HR) data migration framework. It exposes the flat, positional column storage of the HR_DM_EXP_IMPS table as a set of named, semantically meaningful attributes that describe an Oracle Application Object Library (AOL) file loader definition. Because HR_DM_EXP_IMPS stores heterogeneous configuration records using generic columns such as PVAL001 through PVAL016, this view acts as a decoding layer, projecting those generic columns onto logical names such as APPLICATION_ID, LOADER_NAME and LOADER_CONC_PROGRAM.

In the Oracle EBS 12.1.1 and 12.2.2 environments the object is defined in the APPS schema and is queried through the usual APPS credentials and responsibilities. Its role is primarily diagnostic and integration-oriented: it allows forms, concurrent programs and external scripts to retrieve loader metadata without needing to interpret the underlying generic value columns. The view is filtered internally so that only rows whose TABLE_NAME equals 'HR_DM_AOL_FILES_V' are returned, meaning the view effectively presents the subset of HR_DM_EXP_IMPS records that were staged specifically for the AOL files loader definition.

Underlying Base Objects

The view is defined over a single referenced base object, HR_DM_EXP_IMPS, which is accessed through a synonym in the APPS schema. There are no joins to other tables; all columns in the view map directly to columns in HR_DM_EXP_IMPS. The KEY column EXP_IMP_ID is the surrogate identifier of the export/import configuration row, and TABLE_NAME carries the literal value 'HR_DM_AOL_FILES_V'.

The remaining payload is derived entirely from the generic value columns. This design is characteristic of the HR data migration (HR_DM) framework, in which a single physical table holds many logical record types, discriminated by TABLE_NAME. Consequently HR_DM_AOL_FILES_V behaves as a filtered, renamed projection rather than as a genuinely normalized entity: the business meaning of each PVALnnn column is fixed only by the view definition itself.

Key Columns

  • EXP_IMP_ID — Surrogate primary key of the export/import configuration record.
  • TABLE_NAME — Discriminator column; always 'HR_DM_AOL_FILES_V' for rows returned by this view.
  • APPLICATION_ID — Mapped from PVAL001; identifies the owning Oracle application (for example, the HR application identifier).
  • LOADER_NAME — Mapped from PVAL002; logical name of the AOL file loader.
  • LOADER_CONC_PROGRAM — Mapped from PVAL003; the concurrent program used to execute the loader. This is the column most relevant to a search on loader_conc_program.
  • LOADER_CONFIG_FILE — Mapped from PVAL004; the configuration file consumed by the loader.
  • LOADER_APPLICATION — Mapped from PVAL005; the application short name or identifier under which the loader runs.
  • PARAMETER1 through PARAMETER10 — Mapped from PVAL006 through PVAL015; positional loader parameters passed to the concurrent program.
  • FILENAME — Mapped from PVAL016; the name of the file processed by the loader.

Common Use Cases and Queries

The view is typically used to verify which concurrent program is associated with a given AOL file loader, to audit loader configuration before running a data migration, and to drive integration scripts that need to invoke the correct concurrent program. A representative query is:

  • SELECT loader_name, loader_conc_program, loader_application, filename FROM apps.hr_dm_aol_files_v; — lists all AOL file loaders with their executing concurrent program.
  • SELECT exp_imp_id, loader_conc_program, parameter1, parameter2, filename FROM apps.hr_dm_aol_files_v WHERE loader_name = :p_loader; — retrieves the parameter set for a specific loader.
  • SELECT loader_name FROM apps.hr_dm_aol_files_v WHERE loader_conc_program IS NULL; — identifies loader definitions that are not yet bound to a concurrent program.

Because the view performs no joins, queries against it are inexpensive, but callers should remember that it exposes only configuration metadata; the actually executed loader logic resides in the referenced concurrent program and its configuration file.