We'd love to hear from you! Provide  feedback  to earn a badge today. Take our quick survey
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

20D upgrade - issues being faced with HDL tables

Received Response
34
Views
4
Comments
edited Oct 28, 2020 2:38PM in HCM Integrations 4 comments

Summary

Some of the conditions that used to work in HDL data loader tables are not working in 20D.

Content

Earlier for successful load of element entry ,HDL records DATA_SET_BUS_OBJ_ID of HRC_DL_FILE_HEADERS and hrc_dl_data_set_bus_objs table would be same. But now it is different in 20D instance. Because of which our error reports would need change . We see issue with performance when decode/NVL and other functions are used in select clauses too.

Version

20D

Code Snippet


select fr.* from
From hrc_dl_stg_file_rows fr
		, HRC_DL_FILE_LINES fl
		, HRC_DL_FILE_HEADERS fh
		, fusion.hrc_dl_stg_physical_lines pl
		, fusion.hrc_dl_data_set_bus_objs  bo
		, fusion.hrc_dl_business_objects  hbo  
		, HRC_DL_DATA_SETS HDDS
	WHERE fl.line_id = fr.line_id
		AND fr.header_id = fh.header_id
		AND hbo.business_object_id      = bo.business_object_id
		AND fh.DATA_SET_BUS_OBJ_ID = bo.DATA_SET_BUS_OBJ_ID
		AND bo.data_set_id = HDDS.data_set_id
		AND fr.row_id             = pl.row_id
		AND fl.line_id            = fr.line_id
		AND (HDDS.DATA_SET_NAME = :Dataset_Name||'.zip' OR HDDS.UCM_CONTENT_ID =:P_CONTENT_ID)
		AND PL.IMPORTED_STATUS  = 'SUCCESS' AND PL.VALIDATED_LOADED_STATUS = 'LOADED_SUCCESS'

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!