Results for “mapped_to_name”

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

Overview

HR_DU_COLUMN_MAPPINGS is a Human Resources (PER) module table in the Oracle E-Business Suite database, owned by the HR schema. It stores the mapping relationship between a column name used in a source object — for example, a spreadsheet column presented to end users during a Data Pump or Data Loader upload — and the corresponding output target, such as the internal Data Pump parameter name. In effect, the table acts as a translation dictionary that converts user-facing import structures into the technical field names recognized by the Data Pump / Data Upload engine.

Under the heuristic Data Vault classification derived from its foreign key structure, the table is modeled as standalone. This classification is a modeling suggestion only; it indicates that no dependent sat-ellite or link relationships were mined from the foreign keys. The table behaves as a configuration/reference object rather than a transactional hub, and its rows are typically seeded and maintained as setup data rather than created at runtime by business users.

The documented physical schema for 12.2.2 shows the object as VALID with 13 columns, one primary key, and two foreign key relationships. The same structure applies to 12.1.1, where the table forms part of the Data Upload / Data Pump foundation shared across HRMS products.

Key Information Stored

The columns documented for this table capture both the mapping definition and the standard Oracle WHO audit trail. The most significant columns are:

• COLUMN_MAPPING_ID — surrogate primary key, enforced by the HR_DU_COLUMN_MAPPINGS_PK index, uniquely identifying each mapping row. It is the only documented unique index and therefore the only business-key candidate; because it is a generated surrogate, no natural business key is enforced at the database level.
• API_MODULE_ID — identifies the API module (from HR_API_MODULES) to which the mapping belongs, scoping the mapping to a specific Data Pump interface or business object.
• COLUMN_NAME — the source column name as presented in the source object, such as a spreadsheet column heading.
• MAPPED_TO_NAME — the target name, typically the Data Pump parameter or destination attribute that the source column is translated into.
• MAPPING_TYPE — the classification of the mapping, distinguishing how the source column should be interpreted or routed.
• PARENT_API_MODULE_ID — references the parent API module where a hierarchical or nested mapping applies.
• PARENT_TABLE — the parent table context for the mapping, supporting nested or related data structures.
• SECURITY_GROUP_ID — the security group (from FND_SECURITY_GROUPS) that owns the row, enabling multi-tenant style separation of setup data.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — the standard audit columns recording who created and last modified each mapping.

Together these attributes allow the Data Pump engine to resolve a submitted column into its correct internal parameter without requiring custom code.

Common Use Cases and Queries

The primary use case is diagnostics and configuration review during Data Pump or spreadsheet-based uploads. When a column is not recognized or is routed to the wrong destination, querying this table reveals the configured translation.

• List all mappings for a given API module:
  SELECT column_name, mapped_to_name, mapping_type FROM hr.hr_du_column_mappings WHERE api_module_id = :p_module_id;
• Resolve a specific source column:
  SELECT mapped_to_name FROM hr.hr_du_column_mappings WHERE api_module_id = :p_module_id AND column_name = :p_column_name;
• Review mappings modified recently, using the audit columns, to trace setup changes.
• Validate security-group partitioning when mappings appear missing for a given operating unit context.

Reporting is generally restricted to implementation and support teams, since the data supports setup rather than business transactions.

Related Objects

• HR_API_MODULES — joined via HR_DU_COLUMN_MAPPINGS.API_MODULE_ID = HR_API_MODULES.API_MODULE_ID; the parent module owning the mapping.
• FND_SECURITY_GROUPS — joined via HR_DU_COLUMN_MAPPINGS.SECURITY_GROUP_ID = FND_SECURITY_GROUPS.SECURITY_GROUP_ID; provides the security group context.
• HR_DU_COLUMN_MAPPINGS_PK — the primary key index on COLUMN_MAPPING_ID.
• HR_API_MODULE_PARAMETERS and related Data Pump definition tables — consume the mapped target names as valid parameter entries.
• Data Pump / Data Loader concurrent programs — the runtime consumers that read these mappings during spreadsheet upload processing.

No child tables were identified in the mined relationship data, confirming the standalone classification.