Search Results delete_timecard

Overview

The APPS.HXC_TIMECARD_SUMMARY_API package is the public, AUTHID CURRENT_USER API layer for Oracle E-Business Suite timecard summary processing, delivered as part of the Oracle Time and Labor (OTL) / HXC module stack. Its principal business function is to govern the lifecycle of a timecard summary record: creation and deposit of timecard data into the summary repository, deletion of existing timecard summaries, and reevaluation of timecard approval statuses aligned to an application period. The package header carries the version identifier hxctcsumapi.pkh 120.0, and all calls execute under the privileges of the invoking schema, so callers require direct object privileges on the underlying HXC tables.

Because the API is classified as an API in the ETRM metadata for 12.2.2 (and is unchanged in behavior across 12.1.1), it is the supported programmatic entry point for operations that would otherwise require direct DML against the timecard summary schema — a practice that is not supported and can corrupt OTL status transitions and workflow integrations.

Key Procedures and Functions

The documented interface exposes seven overloaded procedures across four logical operations:

• DELETE_TIMECARD — provided in two overloaded forms, one accepting a block table (hxc_block_table_type) together with a timecard identifier, and one accepting only the timecard identifier. Both accept a p_mode parameter defaulting to hxc_timecard_summary_pkg.c_normal_mode, allowing callers to select the operating mode used during deletion. This is the procedure surfaced by the delete_timecard search term.
• TIMECARD_DEPOSIT — likewise overloaded on block table versus timecard identifier. Each form accepts the same p_mode default and additionally accepts approval workflow arguments (p_approval_item_type, p_approval_process_name, p_approval_item_key) and Timekeeper audit arguments (p_tk_audit_item_type, p_tk_audit_process_name, p_tk_audit_item_key). These parameters bind the deposit to the Oracle Workflow approval process and to the Timekeeper audit trail.
• TIMECARD_DELETE — provided in two overloaded forms, one taking a block table and one taking only a timecard identifier. Unlike DELETE_TIMECARD, no mode parameter is exposed.
• REEVALUATE_TIMECARD_STATUSES — accepts a single application period identifier and recomputes timecard statuses for that period. This is the mechanism used to resynchronize status after period-level or workflow-driven changes.

Tables Accessed

The package reads and writes the following objects through APPS synonyms:

• HXC_TIMECARD_SUMMARY — the primary timecard summary entity; the anchor table for the identifier-based overloads.
• HXC_APP_PERIOD_SUMMARY — the application period summary supplying the scope for REEVALUATE_TIMECARD_STATUSES.
• HXC_ROLLBACK_TIMECARDS_ALL — supporting rollback/delete processing records.
• HXC_TC_AP_LINKS — links between timecards and approval processes.
• WF_ITEM_ACTIVITY_STATUSES — Oracle Workflow activity status, consulted to align timecard approval state with the workflow engine.
• PLITBLM — the PL/SQL character block table used by the block-table overloads.

Usage Notes

The package is referenced by seven other packages within the applications schema, indicating it is invoked both by OTL self-service forms and by internal processing such as the timecard summary deposit and workflow callback logic. Customizations should call the identifier-based overloads where a single timecard is affected, and the block-table overloads when processing a cached set of timecard rows. Because deletion and deposit both touch workflow status tables, callers must supply valid approval item type, process name, and item key values when using TIMECARD_DEPOSIT; omitting them can leave workflow activity records inconsistent. All execution occurs under AUTHID CURRENT_USER, so grants on the HXC and WF objects must be in place for any delegating schema.