Results for “execute_retrieval_process”
18 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
APPS.HXC_GENERIC_RETRIEVAL_PKG is a core Time and Labor retrieval engine package in Oracle E-Business Suite (12.1.1 and 12.2.2). Its business function is to pull approved timecard and time entry data from source transactional tables into the downstream Time and Labor processing and build structures. The package is driven by retrieval processes defined by the customer (for example, incremental or date-bounded runs) and operates on the premise that each retrieval process selects which transactions are eligible for transfer based on scope, date range, incremental flag, and a generated WHERE clause.
The package body declares a substantial global record type, r_parameters, that captures the runtime context of a retrieval: process name, transaction code, start and end dates, incremental and rerun flags, a dynamic WHERE clause, scope, clusive indicators, unique parameter strings, transfer batch size, retrieval options, and a since_date. Complementary global DBMS_SQL number, date, and varchar2 tables hold old and new building block references, day and detail level sequences, override numbers, start/stop times, comments, and deleted flags. This architecture supports set-based, dynamic SQL assembly so that a single retrieval job can handle heterogeneous timecard structures without hard-coded cursors.
Key Procedures and Functions
- EXECUTE_RETRIEVAL_PROCESS — The primary driver. It accepts the retrieval parameters, resolves the process definition in HXC_RETRIEVAL_PROCESSES, builds and executes the dynamic retrieval SQL, stages the qualifying time data, and hands it to the downstream build and transfer logic. This is the entry point invoked by the retrieval concurrent program.
- UPDATE_TRANSACTION_STATUS — Updates the status of HXC_TRANSACTIONS rows after retrieval or transfer, ensuring the transactional record reflects the outcome of the process (for example, retrieved, transferred, or errored).
- PUT_LOG — Writes diagnostic and audit messages. It is used throughout the package to log progress, timing, and errors, particularly when debugging is enabled via HR_UTILITY or the HXC_DEBUG table.
- UPDATE_RDB_STATUS — Updates status information on the retrieval data build/result side, coordinating the state of the records produced by the retrieval so subsequent phases or reruns see an accurate picture.
Tables Accessed
The package reads and writes the following documented APPS synonyms. HXC_RETRIEVAL_PROCESSES and HXC_DATA_SETS drive configuration and process definition. HXC_TRANSACTIONS and HXC_TRANSACTION_DETAILS provide the source time entries. HXC_TIME_BUILDING_BLOCKS, HXC_BLD_BLK_INFO_TYPES, and HXC_BLD_BLK_INFO_TYPE_USAGES define the block structures and information types. HXC_TIME_ATTRIBUTES supplies attribute values, HXC_MAPPING_COMPONENTS and HXC_BEE_PREF_ADJ_LINES support mapping and adjustment logic, and HXC_TIME_RECIPIENTS identifies recipients. PER_ALL_ASSIGNMENTS_F supplies assignment context. FND_CONCURRENT_REQUESTS links the run to its concurrent request. HR_SOFT_CODING_KEYFLEX is read for key flexfield validation, and HXC_DEBUG supports diagnostic output.
Usage Notes
This package is normally invoked indirectly by the Time and Labor retrieval concurrent program, which calls EXECUTE_RETRIEVAL_PROCESS on behalf of a configured retrieval process. It is referenced by seven other packages, indicating that it is a shared service within the HXC schema rather than a standalone entry point. The incremental and rerun flags, together with since_date and the date range parameters, allow repeatable and corrective runs. Because it constructs dynamic SQL and uses DBMS_SQL arrays, customizations should modify retrieval process configuration rather than package code; direct calls from custom code are possible but must respect the expected parameter record and concurrent request context.