Results for “hxt_timecards_x”

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

Overview

APPS.HXT_TIMECARDS_X is a date-effective (concurrent-effective) view in the Oracle E-Business Suite Time and Labor module (HXT). It presents the currently effective row set from the underlying timecard base table, HXT_TIMECARDS_F, filtered so that only records whose effective date range covers the current system date are visible. In EBS Release 12.1.1 and 12.2.2 the _X suffix identifies the standard "current effective" view that Oracle DateTrack applies to an _F (base) table. Consumers query HXT_TIMECARDS_X to read timecard header information — the record that groups a person's reported time for a pay period — without having to construct their own effective-date predicate against the base table. The view carries the full column list of the base table, including all 30 descriptive flexfield attribute columns and the object version number used for optimistic locking, and it remains VALID in the APPS schema across both releases.

Underlying Base Objects

The view is defined over a single documented base object, HXT_TIMECARDS_F (referenced in the metadata as a synonym). The view text is a straight projection of the base table's columns with one WHERE clause restriction:

• EFFECTIVE_START_DATE <= TRUNC(SYSDATE)
• EFFECTIVE_END_DATE >= TRUNC(SYSDATE)

Because both comparisons use TRUNC(SYSDATE), the view resolves the effective row as of midnight of the current day, consistent with DateTrack semantics. Rows that have been end-dated in the past, or that carry a future effective start date, are excluded. The date-effective columns themselves (EFFECTIVE_START_DATE and EFFECTIVE_END_DATE) are still exposed in the projection, so callers can inspect the validity window of the row they retrieve. No joins, unions, or aggregate expressions are present; this is a pure filtered view.

Key Columns

• ID – Primary key of the timecard header row; the value joining to timecard detail lines (HXT_TIMECARD_ITEMS) and downstream payroll/time processing.
• FOR_PERSON_ID – The person for whom time is being reported; foreign key to PER_ALL_PEOPLE_F.
• TIME_PERIOD_ID – The time period (pay period or time period) to which the timecard belongs.
• APPROV_PERSON_ID – The approver (supervisor or authorized delegate) who acted on the timecard.
• APPROVED_TIMESTAMP – The date and time at which approval occurred. This is the column most relevant to the user's search term "approved_timestamp"; it is the canonical timestamp for timecard approval state, as opposed to CREATION_DATE or LAST_UPDATE_DATE, which reflect row audit activity rather than the business approval event.
• STATUS – Workflow/approval status code of the timecard (for example, submitted, approved, rejected, or returned).
• AUTO_GEN_FLAG – Indicates whether the timecard was generated automatically rather than entered by a user.
• BATCH_ID / PAYROLL_ID – Identifiers linking the timecard to batch processing and payroll contexts.
• OBJECT_VERSION_NUMBER – Optimistic locking token; callers performing updates should pass the value read from the view.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE30 – Descriptive flexfield context and segment values.
• Audit columns – CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE – The DateTrack validity window used by the view predicate.

Common Use Cases and Queries

Reporting and integration routines query HXT_TIMECARDS_X whenever they need the current state of timecards without managing effective dating. Typical uses include approval-audit reports keyed on APPROVED_TIMESTAMP, downstream extracts for payroll or project costing, and custom OAF or Forms validation logic. A representative query for approved timecards in a period is:

• SELECT id, for_person_id, time_period_id, approv_person_id, approved_timestamp, status FROM apps.hxt_timecards_x WHERE status = 'APPROVED' AND time_period_id = :p_period_id;
• SELECT for_person_id, approved_timestamp, approv_person_id FROM apps.hxt_timecards_x WHERE TRUNC(approved_timestamp) BETWEEN :p_from AND :p_to ORDER BY approved_timestamp;
• SELECT id, approved_timestamp FROM apps.hxt_timecards_x WHERE auto_gen_flag = 'Y' AND status = 'APPROVED';

Because the view already restricts rows to the current effective date, it should not be combined with additional EFFECTIVE_START_DATE/EFFECTIVE_END_DATE predicates unless historical (non-current) versions are deliberately required, in which case HXT_TIMECARDS_F should be queried directly. Callers should also note that APPROVED_TIMESTAMP is populated only when approval has actually occurred; for timecards in submitted or rejected states the column may be null.