Results for “data_reference_complete”

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

Overview

HR_DU_UPLOADS is a Human Resources (PER) module table in the Oracle E-Business Suite 12.1.1 and 12.2.2 data model. It stores the header-level record representing a single data upload operation sourced from one external file. Each row captures the metadata and processing state of one upload event, including its batch identity, originating source, and the various status flags used by the Data Upload (DU) concurrent processes to track progress through validation, reference resolution, and error reporting.

In Data Vault modeling terms, HR_DU_UPLOADS can be characterized heuristically as hub-leaning. Its primary key, UPLOAD_ID, uniquely identifies each upload instance and is referenced by multiple dependent tables, which is consistent with a hub entity that anchors surrounding satellite and detail structures. This classification is offered as a modeling suggestion only; the table is a conventional transactional header in the EBS schema.

Key Information Stored

The table contains 15 documented columns. The most consequential are:

• UPLOAD_ID — the surrogate primary key defined by the unique index HR_DU_UPLOADS_PK. It is the single business-key candidate for this object and the join column for all child tables.
• MODULE_ID — a foreign key to HR_DU_MODULES identifying the Data Upload module that governs the upload.
• BATCH_ID — groups an upload with the batch that spawned it, enabling batch-level reconciliation.
• SOURCE — records the origin or channel of the uploaded source file.
• STATUS and DATA_INPUT_STATUS — the two primary state indicators used to track overall upload processing and the input validation stage.
• DATA_REFERENCE_COMPLETE — a flag indicating whether reference-data resolution for the upload has finished.
• BUSINESS_GROUP_NAME — the HR business group under which the upload executes.
• DO_REQUEST_ID — the concurrent request identifier of the underlying Data Upload request, useful for tracing the upload back to the concurrent manager.
• SECURITY_GROUP_ID — a foreign key to FND_SECURITY_GROUPS controlling row-level security.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — the standard EBS audit columns.

Common Use Cases and Queries

Typical scenarios include tracking the status of batch uploads, diagnosing failed uploads through HR_DU_ERRORS, and reconciling headers against the source file via HR_DU_UPLOAD_HEADERS.

• Find an upload by its primary key:

  SELECT * FROM hr.hr_du_uploads WHERE upload_id = :p_upload_id;

• List uploads for a given module and status:

  SELECT upload_id, batch_id, source, status
  FROM   hr.hr_du_uploads
  WHERE  module_id = :p_module_id
  AND    status = :p_status;

• Trace an upload back to its concurrent request:

  SELECT upload_id, do_request_id, status
  FROM   hr.hr_du_uploads
  WHERE  do_request_id = :p_request_id;

• Report error counts per upload:

  SELECT u.upload_id, COUNT(e.upload_id) errors
  FROM   hr.hr_du_uploads u, hr.hr_du_errors e
  WHERE  e.upload_id = u.upload_id
  GROUP BY u.upload_id;

Related Objects

The table participates in a rich foreign-key network:

• HR_DU_MODULES — referenced through HR_DU_UPLOADS.MODULE_ID.
• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID.
• HR_DU_UPLOAD_HEADERS — dependent child; joined on UPLOAD_ID.
• HR_DU_ERRORS — dependent child; joined on UPLOAD_ID.
• HR_DU_DESCRIPTORS — dependent child; joined on UPLOAD_ID.

Note the reciprocal relationship on HR_DU_DESCRIPTORS, which participates both as a referring and referenced object relative to HR_DU_UPLOADS.UPLOAD_ID. Collectively these tables form the core of the HR Data Upload infrastructure.