Search Results hr_du_upload_headers_pk




Overview
Explore in AI Chat

Overview

The HR_DU_UPLOAD_HEADERS table is a core technical table within the Oracle E-Business Suite (EBS) Human Resources (HR) module, specifically supporting the Data Upload (DU) framework in releases 12.1.1 and 12.2.2. This framework facilitates the batch upload of data via Application Programming Interfaces (APIs). The table functions as a header-level control and tracking entity, storing metadata for each distinct API batch process initiated within a broader data upload session. It is central to managing the execution flow, status, and relationships of batch data loads.

Key Information Stored

The table's structure is designed to track administrative and process control information for each API batch. The primary and most critical columns include:

  • UPLOAD_HEADER_ID: The system-generated primary key uniquely identifying each API batch header record.
  • UPLOAD_ID: A foreign key to HR_DU_UPLOADS, linking the batch header to its parent upload session.
  • API_MODULE_ID: A foreign key to HR_API_MODULES, identifying the specific API being invoked for the data upload (e.g., for creating assignments or persons).
  • STATUS: A mandatory field indicating the current state of the batch header. This is a lookup code for the lookup type HR_DU_STATUS, which is defined in the FND lookup tables. This directly addresses the user's search context, as this column's values are derived from the HR_DU_STATUS lookup.
  • SOURCE_REFERENCE_TYPE: Defines the referencing methodology (e.g., Parent-Child or Child-Parent) used for rows within this batch, governing how related records are linked during processing.
  • Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) for audit purposes.

Common Use Cases and Queries

This table is primarily queried for monitoring, troubleshooting, and reporting on the progress of data upload batches. A common scenario involves identifying all batches within an upload session that have encountered errors or remain in a pending state. The following sample query demonstrates joining to the parent upload table and filtering by status, which is central to the user's interest in "hr_du_status":

SELECT hdr.UPLOAD_HEADER_ID,
       hdr.UPLOAD_ID,
       hdr.API_MODULE_ID,
       hdr.STATUS,
       lk.MEANING AS STATUS_MEANING,
       hdr.SOURCE_REFERENCE_TYPE
FROM   hr.hr_du_upload_headers hdr,
       fnd_lookup_values lk
WHERE  hdr.UPLOAD_ID = :p_upload_id
AND    hdr.STATUS    = lk.lookup_code
AND    lk.lookup_type = 'HR_DU_STATUS'
AND    lk.LANGUAGE = USERENV('LANG')
AND    hdr.STATUS IN ('ERROR', 'PENDING');

Another critical use case is tracing data lineage and errors. Technical support or developers often join this table to HR_DU_UPLOAD_LINES and HR_DU_ERRORS to diagnose specific failures within a problematic batch.

Related Objects

The HR_DU_UPLOAD_HEADERS table is a pivotal node in the Data Upload schema, with defined relationships to several key tables:

  • References (Parent):
    • HR_DU_UPLOADS via UPLOAD_ID. This is the master upload session table.
  • Referenced By (Child):
    • HR_DU_DESCRIPTORS via UPLOAD_HEADER_ID. Stores descriptive flexfield data for the batch.
    • HR_DU_ERRORS via UPLOAD_HEADER_ID. Logs errors associated with the batch processing.
    • HR_DU_UPLOAD_LINES via UPLOAD_HEADER_ID. Contains the individual data rows submitted for the API batch.

Additionally, the API_MODULE_ID column references HR_API_MODULES, and the STATUS column is governed by the HR_DU_STATUS lookup type in FND_LOOKUP_VALUES.