Search Results offline_notexists

Overview

APPS.HXC_RESOURCE_TIMECARDS_V is a reporting view in the Oracle E-Business Suite (EBS) Time and Labor (OTL / HXC) module, owned by the APPS schema. It presents a consolidated, read-friendly projection of timecard header information for resources, joining the timecard summary record to its associated comment text. Its distinguishing feature is two derived status columns—data_set_status and offline_exists—that classify each timecard relative to the state of HXC data sets. This makes the view particularly relevant to the "off_line" search context: it explicitly exposes whether a given timecard falls within an offline, restore-in-progress, or backup-in-progress data set window, and whether any such offline data set exists at all. The view therefore serves reporting, integration, and diagnostic purposes, allowing consumers to identify timecards whose data may be unavailable or in a transitional state during offline processing, restoration, or backup operations.

Underlying Base Objects

The view is defined over the following documented base objects, all referenced as APPS synonyms or packages:

• HXC_TIMECARD_SUMMARY (alias HTS) — the driving table supplying timecard identity, approval status, timing, hours, and submission details.
• HXC_TIME_BUILDING_BLOCKS (alias TBB) — outer-joined to the summary via timecard_id = time_building_block_id(+) and timecard_ovn = object_version_number(+), supplying comment_text.
• HXC_DATA_SETS (alias D) — queried in correlated sub-selects to evaluate offline data set windows against the timecard's stop time.
• HR_GENERAL (PACKAGE) — invoked through decode_lookup to translate the approval status code.
• DUAL (SYNONYM) — used as the EXISTS sub-query driver for the DECODE expressions.

The join to HXC_TIME_BUILDING_BLOCKS is a left outer join, so timecards without a matching comment building block are still returned.

Key Columns

• timecard_id / timecard_ovn — primary and object version identity of the timecard.
• resource_id — the resource (person) to whom the timecard belongs.
• approval_status — raw approval status code; the view also exposes a decoded, 80-character description via HR_GENERAL.DECODE_LOOKUP('HXC_APPROVAL_STATUS', ...).
• start_time / stop_time — the timecard interval; stop_time is the anchor for the offline data set evaluation.
• recorded_hours, submission_date, has_reasons — hours logged, when submitted, and whether reasons are attached.
• comment_text — free-text comment from the time building block.
• data_set_status — DECODE returning 'OFF_LINE' when the timecard's stop time falls within a data set whose status is OFF_LINE, RESTORE_IN_PROGRESS, or BACKUP_IN_PROGRESS; otherwise 'OTHERS'.
• offline_exists — returns 'OFFLINE_EXISTS' if any data set currently holds one of those three statuses; otherwise 'OFFLINE_NOTEXISTS'.

Common Use Cases and Queries

Typical scenarios include identifying timecards impacted by offline data sets, auditing backup/restore windows, and feeding integration extracts.

• List timecards currently falling inside an offline data set window:

  SELECT timecard_id, resource_id, stop_time, data_set_status
  FROM   apps.hxc_resource_timecards_v
  WHERE  data_set_status = 'OFF_LINE';

• Check whether any offline activity exists before publishing timecard data:

  SELECT timecard_id, offline_exists
  FROM   apps.hxc_resource_timecards_v
  WHERE  offline_exists = 'OFFLINE_EXISTS';

• Report approved timecards with decoded status and hours by resource:

  SELECT resource_id,
         hts.approval_status status_desc,
         SUBSTR(comment_text,1,60) comment_text,
         recorded_hours
  FROM   apps.hxc_resource_timecards_v hts
  WHERE  recorded_hours > 0;

Because the view contains no DML constructs and relies on read-only lookups and sub-queries, it is safe for reporting and read-only integration usage across EBS 12.1.1 and 12.2.2.