Search Results check_inputs




Overview
Explore in AI Chat

Overview

HXC_DEPOSIT_CHECKS is a PL/SQL package in the Oracle E-Business Suite Applications (APPS) schema that supports the Oracle Time and Labor (OTL) module. Its principal business function is to validate timecard deposit data before it is written to the repository, ensuring that submitted or processed timecards satisfy the business rules, template constraints, and audit requirements defined for a given deposit operation. The package operates within the Time and Labor time-deposit processing flow, where timecard blocks, attributes, and template properties are collected, checked, and either accepted or rejected with explanatory messages returned to the caller.

In the ETRM documentation, the package is classified with an API classification of OTHER, indicating it is an internal processing package rather than a formally published public API. The header comment confirms a build at version 120.0.12020000.1 (2012/06/28), consistent with the 12.1.1 and 12.2.2 code lines, and notes that the package body contains additional comments. It is referenced by four other packages, confirming its role as a shared validation utility within the Time and Labor deposit subsystem.

Key Procedures and Functions

The ETRM metadata documents seven program units, described below by name and purpose only.

  • CAN_DELETE_TEMPLATE — Determines whether a given template may be deleted, reporting the outcome through the message table. It supports template maintenance by preventing removal of templates that are still in use or otherwise referenced.
  • CHECK_INPUTS — Validates the incoming timecard blocks, attributes, deposit mode, and template prior to deposit, returning messages for any input that fails the applicable rules.
  • CHK_TIMECARD_DEPOSIT — An overloaded boolean function that evaluates whether a timecard block qualifies for deposit. Two signatures exist: one accepting the standard HXC_BLOCK_TABLE_TYPE block collection, and one accepting the self-service timecard information structure. The overload allows the same validation logic to serve both administrative and self-service deposit paths.
  • AUDIT_CHECKS — Performs audit-oriented validation over blocks and attributes, populating the message table with any audit findings.
  • PERFORM_CHECKS — Executes the core validation logic over blocks, attributes, timecard properties, and the supplied day and detail block lists.
  • PERFORM_PROCESS_CHECKS — Extends the check process by additionally accepting a template and deposit mode, so that validation can be tailored to the specific processing context.

Tables Accessed

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

  • HXC_TIME_BUILDING_BLOCKS — The central timecard repository, referenced directly for the template identifier type used in CAN_DELETE_TEMPLATE and for the block data under validation.
  • HXC_TIME_ATTRIBUTES — Stores time attributes applied to timecards; consulted during input and audit checks.
  • HXC_TEMPLATE_SUMMARY — Holds template definitions used to resolve the template passed into the checks and to support template deletion decisions.
  • HXC_PREF_HIERARCHIES — Preference hierarchies that influence which rules apply during validation.
  • HXC_APP_PERIOD_SUMMARY and HXC_AP_DETAIL_LINKS — Supporting summary and linkage tables for approval-period and deposit detail data.
  • PLITBLM — The PL/SQL internal table type used for message collections returned to callers.

Usage Notes

HXC_DEPOSIT_CHECKS is an internal Time and Labor package and is not intended for direct invocation by customer code. It is typically called from Time and Labor forms and from the concurrent programs that perform timecard deposit and retrieval processing, and it participates in the standard deposit pipeline alongside the four packages that reference it. The check procedures populate an in/out message table, so callers are expected to supply a message collection and to inspect it for errors after each call. Because the package uses AUTHID CURRENT_USER, execution privileges derive from the calling user or invoking program unit. Customizations should avoid modifying this package; integrators requiring deposit validation should instead rely on supported Time and Labor APIs and flexfields. Regarding the search term "isu_c4c_v2_sec_deposit_calc," that identifier does not correspond to any object documented for HXC_DEPOSIT_CHECKS in ETRM, and no release status for it can be established from this metadata.