Business Requirement
HCM Extracts and BI / OTBI / OBIA (currently enabled in on premise) are the most commonly used modes via which data can be transferred from Fusion Applications to 3rd Party System.
While BI Publisher even OTBI and OBIA in same cases allows you to get the specific data set which is being desired by the third party system, we still need a robust outbound tool / mechanism to cater to all business needs. Some important features being:
a) Dynamic File Name
b) Dynamic File Location
c) Capability to capture ‘Changed Data’ only feature
d) Capability to provide data into different formats like E-Text, XML, PDF, RTF
While it is agreed all this can be done using BI Publisher ( Using advanced Features like Bursting which allows dynamic file name generation and also allows encryption too) still for large Data Set and for more coherent integration the preferred and most commonly used mechanism( as of today) is HCM Extract.
The literal meaning of HCM Extract as the name suggests is HR Output. ‘HR’ for HCM and Output for ‘Extract’ so HCM Extract means HR Output in simple terms i.e. when you get HR Data as Output from Fusion Applications it is called HCM Extract.
Custom HCM Extract Creation: Available Options
There are three available options while creating Custom HCM Extract in a Fusion POD (Application Environment):
A) Import Custom HCM Extract from another Fusion Instance
B) Make a copy of existing delivered extracts. Add/Edit/Delete/Modify/Extend the same and make a Custom HCM Extract
C) Create a Custom HCM Extract from scratch
To make things simpler we would try to publish all three categories in three different articles which would be posted soon. The article names (proposed) are:
A) How-to Migrate Custom HCM Extract
B) How-to Make a Copy of Existing Delivered HCM Extracts
Apps2Fusion Articles 