Results for “hr_du_upload_lines”

50+ results




Overview
Explore in AI Chat

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

Overview

HR_DU_UPLOAD_LINES is a PER (Human Resources) module table in the HR schema that stores the row-level detail records for data upload activity performed through the Oracle E-Business Suite Data Upload / Data Loader utilities. Where a header record (HR_DU_UPLOAD_HEADERS) represents a single logical upload batch, HR_DU_UPLOAD_LINES captures the individual line items that must be processed, with a single logical item sometimes spanning one or more physical rows. This line-level granularity allows the upload framework to stage, validate, and reconcile large volumes of Human Resources data before it is committed to the operational tables.

The table is present and VALID in both Oracle EBS 12.1.1 and 12.2.2, owned by the HR schema. From a dimensional modeling perspective, the FK structure (a parent reference to HR_DU_UPLOAD_HEADERS and dependent HR_DU_ERRORS records) suggests a satellite-leaning classification: the table primarily describes attributes of an upload event captured by the header, rather than acting as a standalone hub or a link between business entities.

Key Information Stored

The documented physical schema exposes 244 columns. The most significant are:

  • UPLOAD_LINE_ID — the surrogate primary key, enforced by the unique index HR_DU_UPLOAD_LINES_PK. This is the sole documented unique index and therefore the only documented business-key candidate.
  • UPLOAD_HEADER_ID — foreign key to HR_DU_UPLOAD_HEADERS, tying each line to its parent upload batch.
  • BATCH_LINE_ID — identifier for the source batch line, supporting traceability to the originating file or feeder process.
  • ORIGINAL_UPLOAD_HEADER_ID — reference to a prior header, used when a line is re-uploaded or corrected.
  • REFERENCE_TYPE — categorizes the line by the kind of data being uploaded, enabling polymorphic handling of different HR entities.
  • LINE_TYPE and DI_LINE_NUMBER — describe the line's classification and its ordinal position within the upload sequence.
  • STATUS — the processing state of the line (for example staged, validated, errored, or processed).
  • PVAL001 through PVAL230 — the generic positional value columns. These hold the actual uploaded field data mapped positionally, which is why a single logical item can span multiple rows and why the column count is so large.
  • SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-org / security-group access control.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide standard EBS who-did-what-and-when tracking.

Common Use Cases and Queries

Typical uses include monitoring the progress of a data load, diagnosing failed lines, and reconciling uploaded values against target HR tables.

  • Status reporting by header: SELECT status, COUNT(*) FROM hr.hr_du_upload_lines WHERE upload_header_id = :p_header GROUP BY status;
  • Joining errors to their source lines: SELECT l.upload_line_id, e.error_message FROM hr.hr_du_upload_lines l JOIN hr.hr_du_errors e ON e.upload_line_id = l.upload_line_id WHERE l.upload_header_id = :p_header;
  • Extracting staged positional values for a given line: SELECT pval001, pval002, pval003 FROM hr.hr_du_upload_lines WHERE upload_line_id = :p_id;
  • Traceability of a corrected load: query rows where ORIGINAL_UPLOAD_HEADER_ID is not null and compare against the current header.

Because the PVAL columns are generic, no single static report covers all reference types; reporters must correlate REFERENCE_TYPE or LINE_TYPE with the interface specification for the corresponding HR entity.

Related Objects

  • HR_DU_UPLOAD_HEADERS — parent table; joined via HR_DU_UPLOAD_LINES.UPLOAD_HEADER_ID = HR_DU_UPLOAD_HEADERS.UPLOAD_HEADER_ID.
  • HR_DU_ERRORS — child table; joined via HR_DU_ERRORS.UPLOAD_LINE_ID = HR_DU_UPLOAD_LINES.UPLOAD_LINE_ID, providing validation and rejection messages per line.
  • FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID for access control.
  • HR_DU_UPLOAD_LINES_PK — the unique index on UPLOAD_LINE_ID that enforces the primary key and drives line-level lookups.
  • PER Data Upload concurrent programs and APIs — the Data Upload process consumes these lines, validates them, and writes resolved data into the operational PER/HR tables.