Results for “hr_du_errors”

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

Overview

HR_DU_ERRORS is a transactional table in the HR schema of Oracle E-Business Suite (validated in 12.1.1 and 12.2.2) that stores the error records produced when any Data Uploader module processes a batch. The Data Uploader framework is the mechanism by which Oracle Human Resources and related PER modules load bulk data — such as employee assignments, element entries, or other HR datable entities — from external sources or interface tables into the application. When a row within an upload batch fails validation or processing, the failure is not lost; it is persisted in HR_DU_ERRORS so that the underlying cause can be inspected, corrected, and reprocessed.

The table therefore functions as the diagnostic ledger of the Data Uploader pipeline. Each row records the module that ran, the batch, header, and line context in which the failure occurred, and a human-readable message describing the error. Because HR_DU_ERRORS carries foreign keys to four parent objects (uploads, upload headers, upload lines, and modules), its heuristic Data Vault classification is link, i.e., from a data-vault modeling perspective it can be treated as a many-to-one linking structure connecting a specific upload line to the module and batch that produced the error. This classification is a modeling suggestion only; the table is not part of a formal Data Vault implementation in EBS.

Key Information Stored

The documented physical schema contains 12 columns. The most significant are:

• ERROR_ID — Surrogate primary key, enforced by the HR_DU_ERRORS_PK unique index. This is the only documented business-key candidate; it carries no business meaning and exists solely to give each error row a stable identity.
• UPLOAD_ID — Foreign key to HR_DU_UPLOADS, identifying the top-level upload batch that failed.
• UPLOAD_HEADER_ID — Foreign key to HR_DU_UPLOAD_HEADERS, narrowing the failure to a specific header (business grouping) within the batch.
• UPLOAD_LINE_ID — Foreign key to HR_DU_UPLOAD_LINES, pinpointing the individual data line that could not be processed. This is typically the most granular reference used during correction and re-submission.
• MODULE_ID — Foreign key to HR_DU_MODULES, indicating which Data Uploader module generated the error.
• MESSAGE — The free-text description of the error condition, and the principal column read by end users and support staff when diagnosing a failed batch.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — Standard EBS WHO columns providing audit history of when and by whom the error row was created or amended.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, supporting multi-organization / security-group partitioning of the data.

Common Use Cases and Queries

The most frequent use is simply answering "what went wrong with my upload?" A typical query joins the error table to the upload hierarchy to present errors in a readable form:

• All errors for a known batch: SELECT e.error_id, e.upload_line_id, e.message FROM hr.hr_du_errors e WHERE e.upload_id = :upload_id ORDER BY e.upload_line_id;
• Errors grouped by module to identify systemic problems: SELECT module_id, COUNT(*) FROM hr.hr_du_errors GROUP BY module_id;
• Joining to HR_DU_UPLOAD_LINES to retrieve the offending source data alongside the message, so the payload can be corrected in the source and the batch resubmitted.
• Trend reporting on recurring validation messages, useful for improving upstream data quality or the loading templates themselves.

Because the table is transactional and can grow quickly in high-volume environments, purge or archival strategies should be considered alongside the standard Data Uploader reconciliation process.

Related Objects

• HR_DU_UPLOADS — parent batch/master record; joined on HR_DU_ERRORS.UPLOAD_ID = HR_DU_UPLOADS.UPLOAD_ID.
• HR_DU_UPLOAD_HEADERS — header-level grouping; joined on UPLOAD_HEADER_ID.
• HR_DU_UPLOAD_LINES — line-level detail; joined on UPLOAD_LINE_ID and the key object for error-to-row reconciliation.
• HR_DU_MODULES — registry of Data Uploader modules; joined on MODULE_ID.
• FND_SECURITY_GROUPS — security partitioning; joined on SECURITY_GROUP_ID.

Together these dependencies make HR_DU_ERRORS the central error-reporting artifact of the HR Data Uploader framework, and the first table examined when an HR bulk load fails.