HCM Extract - Inbound Interface Delivery Option - File Should Be Ready To Be Processed by HDL
(Doc ID 2256089.1)
Last updated on FEBRUARY 06, 2019
Applies to:Oracle Fusion Global Human Resources Cloud Service - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
In the document "Implementing Information Retention and Disposal Policies in Oracle Fusion HCM" available through Doc ID 2216828.1 it is stated: Page 15 - Defining the Inbound Interface Delivery Option:
"The file will be created with a txt file extension. Before you can upload it using HDL you must first change the file extension to .dat and add this file to a compressed zip file. Whilst compressing the file you can encrypt the zip file. The individual business object files should not be encrypted separately."
Actually, if user configures the Inbound Delivery Option as illustrated in the attached document "HCM Extract Inbound Delivery Option.doc", HCM Extract loads the file to the account hcm/dataloader/import, the file is compressed but its extension is not ".zip" and the inner file is not a ".dat" file that HDL is able to process.
Will future releases of HCM Extract be able to produce a file that is ready to be processed by HDL without the need of manually change its extension and zip it up? Moreover, in order to automate the whole process, will also HCM Extract able to submit the import and load process of HDL for the file generated? We need to know it in order to understand if we can automate some processes we have to implement in our project.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document