Search Results save_timecard




Overview
Explore in AI Chat

Overview

HXC_TIMEKEEPER is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under the "OTHER" API category. It is a core component of the Oracle Time and Labor (OTL) module (HXC schema), providing the programmatic interface through which timecards are persisted, submitted into the approval and processing workflow, and removed from the repository. In Oracle EBS 12.1.1 and 12.2.2, Time and Labor relies on the HXC_TIME_BUILDING_BLOCKS table as the central store for timecard structures; HXC_TIMEKEEPER acts as the write-side gateway to that store, insulating callers from the internal mechanics of block/attribute persistence, validation messaging, and workflow initiation.

The package is designed around a set of collection-based IN OUT NOCOPY parameters—block, attribute, and message tables—that carry the timecard payload, its descriptive attributes, and any validation or processing messages returned to the caller. This architecture allows the package to be invoked from both self-service timecard entry pages and batch processes while maintaining a consistent persistence contract.

Key Procedures and Functions

The documented package spec exposes three public procedures:

  • SAVE_TIMECARD — Persists a timecard payload without submitting it into the approval workflow. It accepts the timecard blocks, attributes, and messages collections, returns the generated timecard identifier and object version number, and optionally records timekeeper context and audit/notification parameters. It is used to stage or draft timecards prior to formal submission.
  • SUBMIT_TIMECARD — Persists the timecard and drives it into the Time and Labor submission process, initiating downstream approval routing and summary aggregation. It shares the same collection-based signature as SAVE_TIMECARD, returning the timecard ID and OVN, and honours optional timekeeper, audit, and notification arguments.
  • DELETE_TIMECARD — Removes a timecard identified by its time_building_block_id, returning processing messages through the message collection. It is used to eliminate timecard data that should not remain in the repository.

No functions (only procedures) are documented, and no additional procedural overloads appear in the excerpted specification.

Tables Accessed

The package accesses the following objects via APPS synonyms:

  • HXC_TIME_BUILDING_BLOCKS — Primary timecard storage; the source of the timecard ID and object version number data types and the target of SAVE/SUBMIT/DELETE operations.
  • HXC_TIMECARD_SUMMARY and HXC_APP_PERIOD_SUMMARY — Summary structures maintained as timecards are submitted, supporting period and approval aggregation.
  • HXC_TRANSACTIONS and HXC_TRANSACTION_DETAILS — Transaction records generated as side effects of timecard submission.
  • HXC_TC_AP_LINKS — Link records associating timecards with approvers or approval processes.
  • WF_ITEMS — Oracle Workflow item records, confirming that submission initiates workflow-driven approval.
  • DUAL and PLITBLM — Utility references for scalar evaluation and PL/SQL table (collection) handling.

Usage Notes

HXC_TIMEKEEPER is typically invoked from OTL self-service timecard forms, from concurrent programs that process or migrate timecard data, and from custom extensions that need to create, submit, or delete timecards programmatically. Because the procedures use IN OUT NOCOPY collection parameters, callers must initialise and populate the block and attribute tables prior to invocation and should inspect the returned message table for validation errors. The package is referenced by two other packages, indicating it functions as a shared dependency within the Time and Labor API layer and should not be modified directly in a production environment.