Results for “hxc_deposit_processes”

50+ results




Overview
Explore in AI Chat

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

Overview

HXC_DEPOSIT_PROCESSES is a configuration and control table in the Oracle E-Business Suite Time and Labor Engine module (product code HXC). It defines the deposit processes that govern how time collection data flows from external time sources into the Time and Labor repository. Each row represents a deposit process — a named definition that binds a specific time source to a mapping, thereby controlling how inbound time records are recognized, validated, and staged before they are consumed by Time and Labor processing. In releases 12.1.1 and 12.2.2 the table resides in the HXC schema and is exposed as a valid, documented object within the ETRM data model.

The table is classified in the metadata evidence as a link using a heuristic Data Vault classification mined from its foreign key structure. As a modeling suggestion, this reflects the table's role as an associative entity: rather than holding descriptive attributes of a business subject, it connects a time source to a mapping, forming a relationship that drives later transaction processing. Administrators and implementers configuring time collection integrations are the primary audience for this object.

Key Information Stored

The documented physical schema contains 11 columns. The surrogate primary key is DEPOSIT_PROCESS_ID, defined through the unique index HXC_DEPOSIT_PROCESSES_PK. In the 12.2.2 schema the unique index is composed of DEPOSIT_PROCESS_ID together with ZD_EDITION_NAME, reflecting the edition-based redefinition strategy used by EBS for online patching. ZD_EDITION_NAME therefore participates in the business-key candidate for uniqueness.

  • DEPOSIT_PROCESS_ID — surrogate primary key; system-generated identifier for each deposit process definition.
  • NAME — user-facing name of the deposit process, used in setup and administrative screens.
  • TIME_SOURCE_ID — foreign key to HXC_TIME_SOURCES, identifying the source of the time records to be deposited.
  • MAPPING_ID — foreign key to HXC_MAPPINGS, identifying the mapping used to translate source data into Time and Labor structures.
  • OBJECT_VERSION_NUMBER — optimistic locking column used by the framework to detect concurrent updates.
  • ZD_EDITION_NAME — edition identifier supporting EBR and online patching; part of the unique index.

The remaining documented columns are the standard WHO audit fields: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN. These provide change tracking and are populated automatically by the EBS framework.

Common Use Cases and Queries

Typical use cases center on validating integration configuration, tracing a deposit process to its underlying time source and mapping, and auditing when setup changed. A common reporting pattern joins the table to both foreign-key parents:

  • SELECT dp.deposit_process_id, dp.name, ts.name AS time_source, m.name AS mapping FROM hxc_deposit_processes dp, hxc_time_sources ts, hxc_mappings m WHERE dp.time_source_id = ts.time_source_id AND dp.mapping_id = m.mapping_id;
  • Identifying all deposit processes for a given time source: SELECT name FROM hxc_deposit_processes WHERE time_source_id = :source_id.
  • Auditing recent configuration changes using LAST_UPDATE_DATE and LAST_UPDATED_BY.

Because the table is configuration-oriented rather than transactional, query volumes are low and result sets small, making it suitable for setup validation reports and integration diagnostics.

Related Objects

Relationships are defined through the documented foreign keys and the primary key index.

  • HXC_TIME_SOURCES — referenced via HXC_DEPOSIT_PROCESSES.TIME_SOURCE_ID; identifies the origin of time data.
  • HXC_MAPPINGS — referenced via HXC_DEPOSIT_PROCESSES.MAPPING_ID; defines how source data maps into Time and Labor.
  • HXC_DEPOSIT_PROCESSES_PK — the unique index enforcing the primary key on DEPOSIT_PROCESS_ID and ZD_EDITION_NAME.

These objects form the configuration chain through which time deposit processing is established and executed.