Results for “api_module_id”

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

Overview

The HR_DU_UPLOAD_HEADERS table is a core repository object in the Oracle E-Business Suite Human Resources (PER) module. It resides in the HR schema and stores the header-level details for each Application Programming Interface (API) that has been queued for upload through the Data Upload (DU) mechanism. In Oracle EBS, the Data Upload framework provides a bulk-processing alternative to the Data Pump and standard HR API interfaces, allowing high volumes of person, assignment, and related records to be validated and loaded in a controlled batch fashion. Each row in HR_DU_UPLOAD_HEADERS represents one logical upload unit tied to a specific API module, and it acts as the parent record for the descriptor and line-level details that define the individual data values to be processed.

From a data modeling perspective, the mined relationship structure suggests a hub-leaning classification. The table participates in a star-like pattern, with HR_DU_UPLOAD_LINES, HR_DU_DESCRIPTORS, and HR_DU_ERRORS all referencing it through the UPLOAD_HEADER_ID foreign key.

Key Information Stored

The table contains 11 documented columns. The surrogate primary key, UPLOAD_HEADER_ID, is defined by the unique index HR_DU_UPLOAD_HEADERS_PK and uniquely identifies each upload header. It is the reference point used by all child tables. The most significant columns include:

• UPLOAD_HEADER_ID — Surrogate primary key; the unique identifier for an upload header record.
• UPLOAD_ID — Foreign key to HR_DU_UPLOADS, linking the header to the parent upload batch.
• API_MODULE_ID — Foreign key to HR_API_MODULES, identifying the specific HR API targeted by the upload.
• STATUS — Tracks the processing state of the header (for example, unprocessed, in progress, completed, or errored).
• SOURCE_REFERENCE_TYPE — Describes the origin or reference type of the source data.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, supporting multi-tenant or business-group data partitioning.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns capturing modification history.
• CREATED_BY, CREATION_DATE — Standard WHO columns recording record creation.

No additional business-key candidate beyond the primary key is documented.

Common Use Cases and Queries

Developers and support analysts query this table to monitor the progress of bulk HR API loads, diagnose failures, and reconcile uploaded records. A typical status report joins the header to its parent upload:

• Upload status monitoring: SELECT h.UPLOAD_HEADER_ID, h.STATUS, h.API_MODULE_ID FROM HR_DU_UPLOAD_HEADERS h WHERE h.UPLOAD_ID = :upload_id;
• Error investigation: Join HR_DU_UPLOAD_HEADERS to HR_DU_ERRORS on UPLOAD_HEADER_ID to list all validation failures for a given header.
• API-level reporting: Aggregate headers by API_MODULE_ID to determine which HR APIs are most frequently invoked.
• Audit trails: Filter on LAST_UPDATE_DATE and LAST_UPDATED_BY to trace who modified upload headers.

Related Objects

HR_DU_UPLOAD_HEADERS is tightly coupled to several PER framework objects through documented foreign keys:

• HR_DU_UPLOADS — Parent batch table; joined via UPLOAD_ID.
• HR_API_MODULES — Reference table for the target API; joined via API_MODULE_ID.
• FND_SECURITY_GROUPS — Security partitioning; joined via SECURITY_GROUP_ID.
• HR_DU_UPLOAD_LINES — Child lines holding individual data values; joined via UPLOAD_HEADER_ID.
• HR_DU_DESCRIPTORS — Child descriptors defining column mappings; joined via UPLOAD_HEADER_ID.
• HR_DU_ERRORS — Child error log capturing validation and processing messages; joined via UPLOAD_HEADER_ID.