Results for “hxc_timecard”

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

Overview

The APPS.HXC_TIMECARD package is the core PL/SQL API within Oracle E-Business Suite's Oracle Time and Labor (OTL) module, responsible for the creation, retrieval, modification, and deletion of timecard structures. It is declared with AUTHID CURRENT_USER and is a public (non-wrapped) specification owned by the APPS schema, classified under the broader ETRM "OTHER" API category. The package operates on the HXC schema family (Time and Labor) and exposes the underlying time-building-block, transaction, attribute, and locker subsystems through a controlled programmatic interface.

Because it is referenced by 28 other packages, it serves as a foundational service layer for higher-level OTL components — most notably the Timecard entry forms, self-service timecard flows, transaction validation logic, and locker management utilities. Its scope constants (TIMECARD, TIMECARD_TEMPLATE, DAY, DETAIL) confirm that callers can target operations at multiple granularities of time data.

Key Procedures and Functions

• CREATE_TIMECARD — Builds a timecard by assembling time building blocks into a coherent timecard structure. It is the primary entry point for populating a new timecard from supplied block attributes, feeding the transaction and building-block tables.
• LOAD_BLOCKS — Loads time building blocks into the package's internal block_list collection (a numeric PL/SQL associative array), preparing them for subsequent timecard operations.
• LOAD_ATTRIBUTES — Retrieves and loads time attribute definitions and their usages, ensuring that timecard creation honours the attribute framework configured for the applicable timecard layout or template scope.
• DELETE_TIMECARD — Removes an existing timecard and its associated building blocks, commonly invoked during timecard cancellation or administrative cleanup.
• DELETE_NULL_ENTRIES — Purges null or empty timecard entries, maintaining data integrity by eliminating orphaned or unpopulated records from the timecard hierarchy.

The specification also defines the record types transaction_record and transaction_info, plus a comprehensive set of status constants (SUBMIT, SAVE, AUDIT, DELETE, ERROR, CONFIRMATION, INFORMATION, WARNING, EXCEPTION, BUSINESS_MESSAGE) used to communicate operation outcomes to calling modules.

Tables Accessed

• HXC_TIME_BUILDING_BLOCKS — The central table holding timecard vertices; read and written during create/delete operations.
• HXC_TRANSACTION_DETAILS — Tracks transaction status and exception descriptions for each timecard operation.
• HXC_TIMECARD_SUMMARY — Provides aggregated timecard totals used during save and submit processing.
• HXC_TIME_ATTRIBUTES / HXC_TIME_ATTRIBUTE_USAGES — Supply attribute definitions and their usage context during LOAD_ATTRIBUTES.
• HXC_BLD_BLK_INFO_TYPES — Defines informational field types available on building blocks.
• HXC_LOCKER_TYPES / HXC_LOCKS — Manage timecard locking to prevent concurrent modification.
• WF_ITEMS / WF_PROCESS_ACTIVITIES — Interface with Oracle Workflow for approval and business-message routing.
• FND_ATTACHED_DOCUMENTS — Supports attachments associated with timecard records.
• PLITBLM — The standard PL/SQL table used for bulk message handling and error reporting.

Usage Notes

This package is typically invoked indirectly rather than called directly by end users. The primary callers are OTL forms (such as the Timecard entry and Administrative timecard forms), self-service timecard pages, and concurrent programs that pre-populate or mass-process time data. Custom extensions should invoke HXC_TIMECARD through its documented procedures rather than writing directly to HXC base tables, since the package enforces validation, transaction logging, workflow integration, and locker semantics that direct DML would bypass.

When extending or troubleshooting, note that the package's behaviour is governed by the scope constants above, so callers must pass the appropriate scope (TIMECARD, TIMECARD_TEMPLATE, DAY, or DETAIL) to obtain correct block and attribute loading. Because it is an AUTHID CURRENT_USER package, execution privileges and any private synonyms depend on the connected schema; in Oracle EBS 12.1.1 and 12.2.2 the standard invocation path is through the APPS schema or a responsibility-linked application user with the appropriate grants.