Introduction
As some of you might be aware by now that HCM Extracts is the recommended Outbound Integration tool for transferring data from Fusion HCM Cloud Application (applicable for On-Premise Deployment Model too) to external third party systems. While most of the times the Data Elements required by the consuming system can be fetched by using the available Database Item in the HCM Cloud Application in some of the cases the requirement might be a little complex and an already available Database Item may not exist. In such cases, one has to raise a SR and await Oracle Development team to provide a new Database Item but this might take a long time. As an alternative, one may use the “Extract Rule” Type Fast Formula to perform complex calculations and get desired results.
In this article, we would try to make use of a very simple “Extract Rule” Type Fast formula and illustrate its usage in implementation projects to achieve desired results.
Creating a Basic Custom HCM Extract
For this demonstration we would create a very simple HCM Extract which would consist of just two elements namely:
-
Person Number
This Data Attribute would hold the Person Number. This Data Attribute is fetched using the Database Item Extract Person Number.
-
PreviousEmployerLOS
This Data Attribute is intended to hold the Length of Service In Years for an Employee. An Employee might have worked in multiple organizations prior to joining the current one and must have different length of service. These details might be captured in some information element ( Descriptive Flex Fields, Information Type Elements.. etc). In order to fetch this value we would have to use a Fast Formula and in such cases “Extract Rule” Fast Formula comes to rescue. For this example, we would have a constant value (say 2) returned from the Fast Formula.
As a prerequisite, we already have created a Fast Formula of Type “Get Previous Employer LOS In Years”.
Fast Formula Details |
|
Attribute Name / Label / Prompt |
Attribute Value |
*Formula Name |
Get Previous Employer LOS In Years |
*Type |
Extract Rule |
Description |
Custom Fast Formula Created to Fetch a Constant Value 2 |
Legislative Data Group |
|
Effective Start Date |
1/1/1951 |
Type of Editor |
Text |
Formula Text |
RULE_VALUE = ‘2’ RETURN RULE_VALUE |
Now that we are aware of the Data Attributes we need to create our HCM Extracts let-us get started with creating a simple extract. Just for the sake of simplicity we would also have a very simple Extract Filter criteria where-in we would only fetch data for “Extract Person Number = 541”
We would use the following details to Create Extract (Navigation is Data Exchange->Manage Extract Definitions-> Create (+) )
Attribute Name |
Attribute Value |
Name |
ExtractRuleCriteriaBasedCustomExtract |
Start Date |
1/1/1951 |
Type |
HR Archive |
Next, we need to click on “Switch Layout” button.
Once we click on “Data Group” (above) it would take us to a new screen where we would need to populate following details:
Data Group |
|
Attribute Name |
Attribute Value |
Name |
Person |
*Tag Name |
Person |
User Entity |
PER_EXT_SEC_PERSON_UE |
Threading Database Item |
Extract Person ID |
*Threading Action Type |
Object Actions |
Interlocking Database Item |
|
Root Data Group |
Checked |
Description |
Main Data Group |
Also, we would need to define a Data Group Filter Criteria
Data Group Filter Criteria |
|
Attribute Name |
Attribute Value |
Filter Criteria |
Extract Person Number = 541 |
Next, we need to create a Record. We would need to populate the following details:
Record |
|
Attribute Name |
Attribute Value |
Effective Start Date |
1/1/1951 |
Effective End Date |
|
Sequence |
1 |
Name |
PersonRecord |
TagName |
PersonRecord |
Type |
Detail Record |
ProcessType |
Fast Formula |
Next Data Group |
|
Hidden |
|
Required |
|
Enable edits to output results |
|
Generated Fast Formula |
<Auto Generated When Record Attributes are Defined> |
Description |
Main Person Record |
Now, we need to define the Extract Attributes:
-
PersonNumber
-
PreviousEmployerLOS
Next, we need to populate the Extract Delivery Options using following details
Extract Delivery Options |
|
Attribute Name |
Attribute Value |
Start Date |
1/1/1951 |
End Date |
|
*Delivery Option Name |
ExtractRuleCriteriaBasedCustomExtract |
*Output Type |
Data |
Report |
/Custom/Practice Samples/ExtractReport |
Template Name |
|
*Output Name |
ExtractRuleCriteriaBasedCustomExtractOutput |
*Delivery Type |
None |
Bursting Node |
|
Override Delivery Node |
As a last step, we would search for the Extract and check if it is in Valid Status
Submitting Extract
We would now try to Submit the Extract
Navigation: Data Exchange->Submit Extracts
View Extract Results
We can view Extract Results now using the View Extract Results Link
We could clearly see that the PreviousEmployerLOS field is holding the value 2. While in this article we have used a hardcoded value one may always use complex calculation in the Fast Formula to get desired results.
I hope this would serve as a Prototype and someone of you would be able to extend on this to develop more interesting, robust and complex Extracts.
Do give a try and share your findings.
Good Bye for now and have a nice day ahead!.