Results for “hxt_timecards”

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

Overview

HXT_TIMECARDS is a public synonym view owned by the APPS schema in the Oracle E-Business Suite Time and Labor module (product code HXT). It presents a date-effective, session-filtered projection of timecard header records drawn from the underlying timecards entity. The view exposes the full attribute column set (ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE30) plus the standard Oracle EBS who-columns and an OBJECT_VERSION_NUMBER, and it is defined so that only the row version effective for the current user session is visible.

The defining characteristic of the view is its dependence on FND_SESSIONS. The predicate compares EFFECTIVE_START_DATE and EFFECTIVE_END_DATE against TRUNC(EFFECTIVE_DATE) for the FND_SESSIONS row matching USERENV('SESSIONID'). Consequently, the view returns exactly one effective version of each timecard per session, based on the session's effective (login) date rather than SYSDATE. This makes the view suitable for online forms, concurrent programs, OTL self-service pages, and integration extracts that must honor the effective-dating and session context conventions used by Time and Labor.

Underlying Base Objects

The ETRM metadata for 12.2.2 documents two referenced base objects: HXT_TIMECARDS_F (SYNONYM) and FND_SESSIONS (SYNONYM). The view text is a straightforward SELECT of all listed columns FROM HXT_TIMECARDS_F, with the effective-date predicate applied in the WHERE clause and FND_SESSIONS accessed twice through scalar subqueries keyed on SESSION_ID = USERENV('SESSIONID').

HXT_TIMECARDS_F is the "_F" (date-effective/entity) table that stores the timecard header, including its effective start and end dates, and is the table that carries the ATTRIBUTE1–30 descriptive flexfield columns, the approval columns, payroll reference, batch reference, and status. The "_F" suffix in Oracle Application Object Library denotes a table whose rows are versioned over time and typically paired with a "_TL" translation table and a "_V" or base view. HXT_TIMECARDS is that base, session-aware view. FND_SESSIONS is the Applications session table maintained by Oracle Forms; the correlation to USERENV('SESSIONID') ensures the effective date is derived from the session record rather than the database server clock.

Key Columns

• ID — Primary identifier of the timecard header record.
• FOR_PERSON_ID — The person (employee/assignment holder) for whom the timecard is filed.
• TIME_PERIOD_ID — The Time and Labor time period to which the timecard belongs.
• AUTO_GEN_FLAG — Indicates whether the timecard was generated automatically rather than entered manually.
• BATCH_ID — Batch to which the timecard was assigned, used in Time and Labor batch processing.
• APPROV_PERSON_ID, APPROVED_TIMESTAMP, STATUS — Approval chain and current workflow status of the timecard.
• PAYROLL_ID — Payroll associated with the timecard, where applicable.
• EFFECTIVE_START_DATE, EFFECTIVE_END_DATE — The date-effective range of this version; these drive the session-based filter predicate.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit (who) columns.
• OBJECT_VERSION_NUMBER — Optimistic locking / concurrency token.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE30 — Descriptive flexfield context and segment values.

Common Use Cases and Queries

Typical usage includes reporting on timecard headers for a person or period, verifying approval state before submitting to payroll, and joining to HXT_TIMECARD_ITEMS or HXT_TIME_ENTRY views for line-level detail. Because the view is already session-filtered, queries executed through Oracle Forms or OTL self-service automatically see the correct effective version. Reports executed outside a Forms session, however, may return no rows because no matching FND_SESSIONS record exists for the database session.

• Timecards for a person in a period:

  SELECT id, for_person_id, time_period_id, status,
         approved_timestamp, payroll_id
    FROM apps.hxt_timecards
   WHERE for_person_id = :p_person_id
     AND time_period_id = :p_period_id;

• Pending approval list:

  SELECT id, for_person_id, time_period_id, approved_timestamp
    FROM apps.hxt_timecards
   WHERE status = :p_pending_status
   ORDER BY for_person_id, time_period_id;

• Batch-level audit:

  SELECT batch_id, COUNT(*) timecard_count
    FROM apps.hxt_timecards
   GROUP BY batch_id;

For processes requiring all effective versions irrespective of session (for example, historical audit extracts), query HXT_TIMECARDS_F directly with explicit effective-date range predicates rather than relying on the view, since the view's FND_SESSIONS dependency constrains visibility to the current session's effective date.