Fusion Blog

EBS Blog


Contact Us

Fusion PayRoll
  • Register

Oracle Gold Partners, our very popular training packages, training schedule is listed here
Designed by Five Star Rated Oracle Press Authors & Oracle ACE's.

webinar new Click here to raise Support Ticket. Get reply within 48 hours.

Search Courses

User Rating: 0 / 5

Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive


One of the most common requirement for all HCM Implementations is Data Integration from Fusion Applications to external 3rd party system. HCM comprises of Employee Data so more often then not there is a constant need of HR Related data to other applications. Generally consultants create separate Extracts / Data Models ( in case some-one prefers this approach) to cater to business needs, but there is a smart way of creating One Extract which could be an input to multiple different templates ( which if smartly created) would only display data needed by the system

If Application ‘A’ needs N fields says only associated with Personal Information we may use this XML Data Source and have a specific template T1 to display only those N fields

If Application B needs (N + P) fields associated with Personal Information and Work Relationship we may still use the same XML Data Source but a different template say T2 to generate data in desired format

In this article we would not be discussing about template but rather the single XML Data Source which could provide us a solution to all our Outbound Integration Issues (at least for HCM domain).

Let’s get started then.

Step1: Find an Employee (1826)

Step2: Create a Report from globalReportsDataModel


Navigator -> Reports and Analytics


Next Click on the Book Icon (When you hover the mouse over the icon the tooltip would say Browse Catalog)


A mouse-click on the icon takes you to the next screen


Next navigate to Shared Folders -> Human Capital Management -> Payroll Data Models -> Data Models

And point to globalReportsDataModel


Click on Edit (Link in Blue Color just beneath the globalReportsDataModel)


This takes you to a new screen



Click on the Create Report Icon (An icon on top right hand corner)


A new popup window opens up with few pre-populated fields

Choose the “Use Report Editor” Radio Button and Click on “Finish”


Click on the Finish Button and a popup will appear seeking the folder where you want to save the same.

It is generally preferred to save under some sub folder under Shared Folders -> Custom but then the choice depends on individual. We have named this as “ExtractReport” and saved the same.


Once done the next screen should look as:


Next we need to find the location of the Report. For this we need to hover to the Catalog text on the top right-hand corner


Once you click on the link it takes you to the next screen where it displays all the items under the specified folder


Next Select the Properties Section and note the location of the report


Click on ‘Properties’ and this opens a popup which has lot of details. We are interested in Location and would copy the same as displayed below:

Location is: /shared/Custom/Practice Samples

Now Shared Folders is the Root Folder and hence need not be mentioned explicitly

Report Name is ExtractReport

So the exact location becomes: /Custom/PracticeSamples/ExtractReport.xdo

Wondering why xdo?

Well all reports have a file extension as xdo, like all text files have as.txt or for that matter a Word files has .doc or .docx. Similarly.

This brings us to end of step 2.

Step3: Verify the existence of a Lookup

In this example we would try to use a lookup named ‘ORA_HRC_EXT_EXTRACT_TYPE’ but this a new lookup added by Oracle Development team and its worth to verify whether the same exists in the Application.

In order to verify we have to follow below navigation

Navigator-> Setup and Maintenance -> Manage Common Lookups


Once you click on the link its takes you to the next screen


Search for “Manage Common Lookups” and click on “Go to Task”


This should take you to the next screen


Type “ORA_HRC_EXT_EXTRACT_TYPE” in the textbox beside Prompt Lookup Type and click on search. Let’s hope the Lookup exists


Good News!!!! , The Lookup exists and this brings us to end of step3.

Step4: Search for Delivered Extract named “Worker Extract”

As a next step we need to search for a Delivered HCM Extract named “Worker Extract”. Before proceeding further let us try to get a brief idea of what this “Worker Extract” is. “Worker Extract” as the name suggests is an HCM Extract pre-delivered by Oracle Development team and comprises of most of the attributes associated with a Worker. The sad part though being this is a non-compiled/ non-validated extract. Wondering how come a delivered extract and still non-validated version, because of a bug which is to be fixed in future releases but there are some workarounds. While I would not be detailing the workarounds but let us start with creating an Extract.

Navigate to Data Exchange -> Manage Extract Definitions



Search for Worker Extract


So we have found the Worker Extract and with this we complete Step4.

Step5: Make a copy of “Worker Extract”

We would now try and create a copy of “Worker Extract”. We would name it as XXWorkerExtract.


Once you click this a textbox appears with a Prompt as ‘Specify New Name”. Enter XXWorkerExtract.



Wait until the copy-process is completed.

Let us now search for XXWorkerExtract


Next Click on ‘XXWorkerExtract’ and try to see what awaits us.

Extract Definition it says! (Screen below)

Next, we have to make following changes

Tag Name: XXWorkerExtract

Description: This is an attempt of creating an HCM Extract from delivered Worker Extract with the intent of having one single Extract to accommodate all / most of the worker attributes.

Lookup: Change from PER_EXT_CHANGES_ONLY to ORA_HRC_EXT_EXTRACT_TYPE (Remember Step 3)


Next, we should click the “Design” Icon.


Collapse all the Data-Groups and this will help us understand all the Data-Groups which are part of this extract.



So we see Person Name, Person Phone, Person Email, Person NID, Person Absence, Assignments, Work Relationship, Person Address Details, Salary…… and what not. Pretty much covers the entire attribute buckets (if it does not you may always add new ones….)

Next we need to define a filter-criteria and for this example we would have the condition such that we get data for Employee Number 1826 (Remember Step 1)

Let us see how to add the filter criteria then.

Click on the Data Group Filter Criteria (a filter icon on top)


This opens up a new popup screen. Click on the (+) icon


This takes you to new window with a pencil icon (tool-tip says Edit)


Yes!! You guessed it right we need to click on Edit and again a new window pops up


On the left side we have Database Item Name and on the right hand side we have Operators.

Our condition is:

Extract Person Number = 1826

For this first select ‘Extract Person Number’ and click on the arrow (blue colored


Next select the ‘=’ from Operators section followed by inserting a constant 1826 and the resultant screen should look like


Next you have to press OK button twice (Obviously on two different popups and the following message is displayed).


Please fill in the following details:



Next, we need to move to the ‘Validate’ section


Too Many issues…..

Nevertheless, I have managed to create a similar extract named ‘XX Worker Extract’ and fortunately that works fine.

We would navigate to the Validate Section of ‘XX Worker Extract”


The connect data groups issue are gone but fast formula are not in compiled state.

Time for troubleshooting. Let’s start

Click on the Design Icon and press the ‘Switch Layout’ button


Click on ‘Person Detail’


Once you click on the Generate Formula there would be a name appearing in the Generated Fast Formula section

Post Generation we would need to compile the generated Fast Formula too as shown below:

At this point it is worth navigating to the Validate section and check whether this fast formula shows up as compiled


It does (Notice the Green Tick Arrow beside Person Detail)

We need to repeat the same steps for all other Record ( am not pasting screen-shots as I guess this would be simple and also this document now keeps on getting longer and longer. )

Post the activity we can view that all of the Fast Formula are in compiled state (You need to navigate to VALIDATE and then select Detach Table to reach at below screen)


We will click on the ‘Validate’ button and there should be a popup message confirming the validity of the Hierarchy Structure.


This brings us to end of Step5.

Next we will try to Execute the Step6 and verify whether all the hard-work has materialized or not.

Step6: Running the Extract

For this step its assumed that the user who would be trying to run the extract should have ‘Payroll Administrator’ role assigned to him.

Navigation: Navigator -> Payroll->Checklists->


Once you click on the same, it would take you to a new screen where you need to select ‘Submit a process and Report’ and also choose ‘XX Worker Extract’ for Select Flow Pattern.


Next, we need to provide input parameters as below:

Flow Pattern (Auto-Populated non editable): XX Worker Extract

Payroll Flow (Mandatory, Needs user input): XXWorkerExtract_Run1

Process End Date (Mandatory, Needs user input): 4/6/2016

Changes only (Optional, LOV, Needs User Input): Full Extract  


Click on Next



Once more click on next


A repeat of the same activity takes us to review screen


We are now ready to ‘Submit’ the extract and hope for output. click on Submit Option


Now, we should click on ‘Ok and View Checklist’ button. This takes us to a new screen.


If we click on the ‘Go to Task’ Option this takes us to a new screen


Next, click on the Specs icon (‘View Results’)


The XML data has been generated. (Hard work paid off) Snap-shot below

XML data in screenshot

This XML would hold all details for a worker (only not null values) and an individual may now smartly alter some data elements here and there as per the need to generate required data in appropriate format to be send across to the designated system.

You might like to choose a Person Number (instead of 1826) such that it has all data-attributes be it Person, Work-relationship, Address, Email … or even Absences and other entity items holding not null values in the application so that the XML file has more info.

Associated Files:

  1. XML Data File

  1. Extract Export ( This may be imported into any Fusion Environment)


 N.B: Post import the following things needs to be changed as per Fusion Pod


  1. Check Person Number and make changes in Data Group Filter Criteria

  2. Check whether a Report exists ( created based on globalReportsDataModel )

  3. Check Extract Delivery Options (Provide appropriate details)

  4. Compile All Fast Formulas (You would need to first Generate them )

And with this I come to an end of this exhaustive article.

Thanks all for your time and hope it helped.

Have a Nice Day!!!!!

Ashish Harbhajanka

About the Author

Ashish Harbhajanka


Oracle Fusion HCM Techno Functional Consultant with overall 10 years of Experience in software industry with 5 years in EBS HRMS and rest 5 in Fusion HCM.

My areas of intesrest in Fusion HCM include :

a) Inbound Outbound Integration using FBL/HDL or BIP/HCM Extracts.

b) Fast Formula

c) BIP Reports

d) OTBI Reports

e) RESTFUL API / Web Service Call

f) Functional Setup

g) End to End Testing

h) Regression Testing

i) Preparing COnfiguration Workbooks

j) Creating Speed Solutions

k) Preparing User Guides

l) UPK


More articles from this author

Overall Rating (0)

0 out of 5 stars
  • No comments found

Search Trainings

Fully verifiable testimonials

Apps2Fusion - Event List

<<  Aug 2018  >>
 Mon  Tue  Wed  Thu  Fri  Sat  Sun 
    1  2  3  4  5
  6  7  8  910

Enquire For Training

Fusion Training Packages

Get Email Updates

Powered by Google FeedBurner