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

Dynamic Password Protected report output (Part 2)

This post is in continuation of  Password protected report output (Part 1) post where we discussed about generating the static password protected output. In this post we will go through steps to have dynamic password protected report output. This is a common requirement when a company send offer letter, payslips, appraisal letter etc in HCM. We might have also similar requirement when we send some bills to users. Let's go through the required steps to enable the password protected report output. 1) Create a SQL Data Model which should have one column password like below query have NID :   Note: We can have combination of one or more than one column as password. 2) Create a report for which we have to create a RTF template. While creating the RTF template we need to setup word properties to enable the password for PDF. Please follow the navigation: File > Info > Advance Properties > Custom 3) Add the below two properties: Name Value
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

Loading Worker object using Fusion HCM Data Loader(HDL)

This post is going to be first part of loading different objects using HCM Data Loader (HDL). In this post we will Hire Worker using the HDL. Before starting with steps to load worker data using HDL , please go through the post Supported Keys in Fusion HCM Data Loader   Now we will go through the steps to prepare Worker file and load data: 1)  Generate the Template:           Please follow the Navigation to generate the worker template          Navigator > My Client Group > Data Exchange> View Business Objects > Search for Worker                Select the business object and Click on " Refresh Business Object " 2)   Download the template 3)  Populate the worker file and worker file will look like as below. 4)  zip the Worker.dat file. 5)  Run HDL using the following Navigation:  Navigator > My Client Group > Data Exchange> Import and Load  > Import file  6)   Browse file from you local machine and Submit as shown in below screenshot: 7)  You can verif
Post a Comment
Read more