Results for “time_source_id”

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

Overview

The HXC_TIME_SOURCES table is a core reference object within the Oracle Time and Labor Engine (product code HXC) in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the definition of "time sources" — the mechanisms by which timecard and time-entry data are captured and deposited into the Time and Labor Engine. Each row represents a distinct source from which time information originates, such as a self-service timecard, a web-based entry form, a device or external interface, or a batch process. The Time and Labor Engine relies on this definition to determine how incoming time records are processed, validated, and routed through the deposit pipeline.

The table resides in the HXC schema and was released as a standard EBS object with a VALID status. The documented physical schema contains 9 columns, with the primary key HXC_TIME_SOURCES_PK defined on TIME_SOURCE_ID. A unique index combining TIME_SOURCE_ID and ZD_EDITION_NAME also exists, reflecting the editioning and online-patching conventions introduced for the 12.2.x code line.

From a data-modeling perspective, the supplied relationship metadata classifies this object as hub-leaning. The heuristic is grounded in the foreign key structure: a single natural-key style identifier (TIME_SOURCE_ID) anchors the table, and HXC_DEPOSIT_PROCESSES references it. This suggests that HXC_TIME_SOURCES functions primarily as a hub (a stable set of distinct business keys) rather than a transactional link or a descriptive satellite, though the descriptive columns it carries mean it also exhibits satellite-like characteristics when modeled formally.

Key Information Stored

Only the columns documented in the ETRM schema metadata are described below. The most significant are:

• TIME_SOURCE_ID — The surrogate primary key and the column on which HXC_TIME_SOURCES_PK is defined. It uniquely identifies each time-source definition and is the value propagated into dependent transactional tables.
• NAME — The business-meaningful label for the time source. This is the principal descriptive attribute and the value most often surfaced in user-facing lists and reports.
• ZD_EDITION_NAME — The editioning column that participates with TIME_SOURCE_ID in the composite unique index. It supports the edition-based redefinition model used in 12.2.x.
• OBJECT_VERSION_NUMBER — Tracks the optimistic-locking version of the row, used by the framework to detect concurrent updates.
• CREATED_BY, CREATION_DATE — Standard audit columns recording the creating user and timestamp.
• LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard audit columns recording the most recent updater and modification timestamp.
• LAST_UPDATE_LOGIN — The login identifier associated with the last update, providing additional audit traceability.

The surrogate primary key (TIME_SOURCE_ID) should not be confused with the business-key candidate, which is the composite HXC_TIME_SOURCES_PK / unique index spanning TIME_SOURCE_ID and ZD_EDITION_NAME. The NAME column acts as the human-recognizable descriptor but is not itself documented as a unique key.

Common Use Cases and Queries

Typical scenarios involve identifying which time sources are configured, joining deposit processes back to their originating source, and reporting on volume by source. A straightforward lookup of source definitions is:

SELECT time_source_id, name FROM hxc_time_sources ORDER BY name;

To trace deposit activity back to its source for a given period, analysts join to the dependent table using the documented foreign key:

SELECT dp.time_source_id, ts.name, COUNT(*) FROM hxc_deposit_processes dp JOIN hxc_time_sources ts ON dp.time_source_id = ts.time_source_id GROUP BY dp.time_source_id, ts.name;

Because the table carries the standard WHO audit columns, it is also used in setup-audit reports that identify recently created or modified source definitions. Edition-aware queries may filter or join on ZD_EDITION_NAME when working in a 12.2.x multi-edition context.

Related Objects

The most significant related object is the foreign-key dependent that references this table:

• HXC_DEPOSIT_PROCESSES — References HXC_TIME_SOURCES through the column HXC_DEPOSIT_PROCESSES.TIME_SOURCE_ID. This is the primary documented join path and the principal consumer of the time-source definition, linking each deposit process run to the source it serves.

Beyond the documented foreign key, the Time and Labor Engine's surrounding configuration and transactional objects — such as timecard, time-entry, and deposit-related entities within the HXC schema — depend conceptually on the source definitions held here. However, only HXC_DEPOSIT_PROCESSES is confirmed by the supplied relationship metadata as a direct referencer, and it should be treated as the authoritative join target when navigating from a time source to its associated processing activity.