Search Results get_app_hook_params

Overview

HXC_INTEGRATION_LAYER_V1_GRP is a PL/SQL package belonging to the Oracle E-Business Suite Time and Labor (HXC) schema, declared with AUTHID CURRENT_USER and classified as a GRP (group) API in the ETRM repository. In Oracle EBS 12.1.1 and 12.2.2 it functions as the integration layer that bridges self-service timecard entry, timecard retrieval, and downstream time processing. Its header signature maps to version 115.6 (dated 2004), confirming the package has been part of the Time and Labor integration stack since the early 11i releases and remains available through 12.2.2.

The package exposes a mix of hook procedures used by the self-service time deposit flow and generic retrieval utilities. It is referenced by six other packages, which indicates it is a callable integration point rather than an end-user entry point.

Key Procedures and Functions

The ETRM metadata documents 23 procedures and functions. The primary groupings are:

• Application hook procedures — GET_APP_HOOK_PARAMS and SET_APP_HOOK_PARAMS exchange timecard building blocks, application attributes, and message tables between the integration layer and calling applications.
• Retrieval processing — EXECUTE_RETRIEVAL_PROCESS drives a named retrieval process from HXC_RETRIEVAL_PROCESSES, honoring transaction code, date range, incremental and rerun flags, where-clause, scope, and unique parameters.
• Status management — UPDATE_TRANSACTION_STATUS and SET_PARENT_STATUSES propagate status changes across transaction hierarchies.
• Change detection — TIME_BLD_BLK_CHANGED flags whether a building block has been modified.
• Error handling — ADD_ERROR_TO_TABLE inserts a message into the message table; MESSAGES_TO_STRING renders the accumulated messages as text.
• String conversion utilities — ATTRIBUTES_TO_STRING and BLOCKS_TO_STRING serialize attribute and building-block structures.
• Mapping utilities — GET_MAPPINGVALUE_SUM and CHK_MAPPING_EXISTS validate and total mapping values.
• Timecard lifecycle — GET_TIMECARD_APPROVAL_STATUS, GET_TIMECARD_SUBMISSION_DATE, and GET_TIMECARD_APPROVAL_DATE retrieve approval and submission metadata.
• Structured accessors — PERIOD_START_STOP, BUILD_BLOCK, BUILD_ATTRIBUTE, GET_WF_G_TIME_BUILDING_BLOCKS, and GET_WF_G_TIME_APP_ATTRIBUTES assemble period boundaries and workflow-facing block/attribute sets.

The user's search term "add_error_to_table" corresponds directly to ADD_ERROR_TO_TABLE, the documented procedure used to append an error message to the package's message table parameter.

Tables Accessed

Documented table references, accessed through APPS synonyms, are:

• HXC_RETRIEVAL_PROCESSES — defines the retrieval process invoked by EXECUTE_RETRIEVAL_PROCESS.
• HXC_TIMECARD_SUMMARY — supplies summary timecard data for retrieval and approval queries.
• HXC_TIME_ATTRIBUTES and HXC_TIME_ATTRIBUTE_USAGES — store time attribute definitions and their usage, consumed by attribute building and mapping checks.
• HXC_TIME_BUILDING_BLOCKS — provides building-block definitions used by BUILD_BLOCK and change detection.
• HXC_TRANSACTIONS — the transactional detail against which status updates and error associations occur.
• FND_NEW_MESSAGES — the standard messages repository consulted for error text.
• PLITBLM — the standard PL/SQL message buffer used for output formatting.

Usage Notes

HXC_INTEGRATION_LAYER_V1_GRP is invoked from self-service Time and Labor forms, concurrent programs (particularly retrieval and time processing runs), and workflow-driven processes. Custom integrations that need to execute a retrieval process, build time blocks or attributes, query timecard approval metadata, or push errors into the Time and Labor message table call this package rather than reimplementing the logic. Because it declares AUTHID CURRENT_USER, callers must ensure appropriate privileges on the underlying HXC and FND objects. ADD_ERROR_TO_TABLE is typically called after a failed validation or retrieval step to populate the message table that is subsequently rendered by MESSAGES_TO_STRING.