Last updated on JANUARY 31, 2017
Applies to:Oracle Time and Labor - Version 12.1.3 and later
Information in this document applies to any platform.
While running "Retrieve Timecard Data from OTL to EAM" concurrent program
from EAM, concurrent request has terminated without any error after calling
below API, when it was expected to return back for further processing from
> HXC_INTEGRATION_LAYER_V1_GRP.execute_retrieval_process (
p_process => 'Maintenance Retrieval Process'
, p_transaction_code => p_transaction_code
, p_start_date => to_date(p_start_date,'DD-MM-YYYY')
, p_end_date => to_date(p_end_date,'DD-MM-YYYY')
, p_incremental => 'Y'
, p_rerun_flag => 'N'
, p_where_clause => l_where_clause
, p_scope => 'DAY'
, p_clusive => 'EX'
Logging this SR as per below update from OTL team:
For the same error EAM Dev has worked with OTL DEV for another customer in the past via below mentioned Bug.
Bug 3061414 [https://bug.oraclecorp.com/pls/bug/webbug_edit.edit_info_top?rptno=3061414] - ADS1159.18: RETRIEVE TIME CARD DATA REPORT COMPLETE WITHOUT ERROR BUT HAS ERRORS
But this was on 11i.
This is occurring from within the standard API.
So, now the recommended action plan is that you need to request your(EAM) DEV team to raise a spin off Bug with OTL DEV providing the concurrent request log and the latest OTL Analyzer uploaded by customer on SR.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms