Skip to main content

HCM Extract 20D Update

There are some changes for HCM Extract in Rel 20D update.

Let's see the changes one by one:

1) Rename HCM Extract

It was not possible to rename the HCM Extract earlier than Rel 20D. Now after 20D, users can update the name of HCM Extract. 

    Please follow the below steps to rename the HCM Extract:

    1) Navigation: Navigator> My Client Groups > Data Exchange> Extract Definitions

    2) Search for HCM Extract and click on Copy Marked in Yellow:

 

    3) Two Action will be there: Copy and Rename. Please select rename.


    4) Provide the new name and click on "Ok".

2) Defaulting Rule for Effective Date:
    There is an option to default the Effective Date to SYSDATE.
    Please follow the below step to enable the defaulting to Effective date Parameter.
   1) Search of HCM Extract where effective date parameter need to be updated and click on HCM  Extract.
   2) Go to Parameter Section > Select Effective Date parameter > Change from Basic View to Advance View > Select Parameter Basis as Context Binding and Default Value will automatically set to System Date.



3) SFTP Configuration

From Rel 20D, users can set up the SFTP configuration in fusion application instead of BIP configuration.

Please follow the below steps to do this SFTP configuration:
1) Navigate to Navigator > Data Exchange > Data Exchange Configuration > File Transfer Configuration and Click On "Add".

  2) Enter the SFTP Details and click on Save and Close.

4) Separate tagging for Full Run and Incremental:
    During the versions earlier than Rel 20D , user was not able to differentiate between the Changes only and Full run extract at the start of creation of HCM Extract but now there is check box enabled from Rel 20D that user can select whether the HCM extract is changes Only or Full Extract.
Users have to select this check box when they click "+" to create HCM Extract and the screen below will popup and users have to select or unselect the Changes Only checkbox marked in Yellow in screenshot.


 
Hope this will be helpful.

Labels:

Comments

Post a Comment

Popular posts from this blog

Supported Keys in Oracle Fusion HCM Data Loader(HDL)

Today we will go through the few concepts of HCM Data Loader (HDL). HDL is data loading tool for Oracle fusion HCM. It helps us to do bulk loads during implementation projects or also for on going work. HDL works on predefined template provided by  Oracle.  Keys supported by HDL: 1) Source Key: Source Key is combination of  Source System Id and Source System Owner.  It can be used for both  Create  and  Update.      Source System Id: It is key to represent record uniquely. It can be one column or concatenation of column.      Source System Owner: It generally represents the source of data. We add the source name in Lookup type:   HRC_SOURCE_SYSTEM_OWNER. 2) User Key: These are columns available at object level which are user friendly.  It can be one column or combination of column. e.g Job Code and Set Code are user keys for Job. I t can be used for both  Create  and  Update. 3)  GUID...
Post a Comment
Read more

Loading External Bank Account Using HDL

There are general requirements for loading the External Bank Account for employees during the project implementation which will be used either for expenses or Payroll.  Let's go through the pre-requisite and steps for loading the External bank account using HDL Pre-Requisite: There is pre-requisite to generate party id before loading the External Bank Account.  1) We need to run the " Synchronize Person Records "  scheduled process by entering the details: This process should generate the Party Id for employee which have been migrated using HDL. 2) If Party Id is still not generated even after running the above process then run the " Maintain Party and Location Current Record Information " This process should generate the Party Id for employee which have been migrated using HDL. Once the Party Id is generated run Load the External Bank Account HDL file. Below is sample ExternalBankAccount.dat file: METADATA|ExternalBankAccount|BankNumber|BankName|BankBranchNumbe...
Post a Comment
Read more

Automatic Calculation of FTE while HDL Worker Load

Full-time equivalent (FTE) is an important component when we load worker data in Oracle fusion using HCM Data Loader(HDL). F ull-time equivalent (FTE) value gets calculated by diving the assignment normal working hours by standard working hours of employee. You can refer  Loading Worker object using Fusion HCM Data Loader(HDL)   article to see steps to load worker. During the migration, we can either migrate the FTE using the AssignmentWorkMeasure Metadata of Worker file from the legacy system or we can request FTE to be calculated  automatically. We will see how can request FTE to be calculated automatically while doing the Data Migration. We need to include the  following  instruction in Worker.dat file to calculate FTE automatically while loading worker. SET CALCULATE_FTE Y; Worker file will look like as below: Once this file gets loaded the FTE of employee will be automatically calculated. Please see the screenshot of employee from UI We had not pa...
Post a Comment
Read more