HCM Extracts Guide REL10 - RJ PDF

User Guide for HCM Extracts (Release 10 onwards)
HCM Extracts: User Guide for Release 10 onwards
Purpose:
This document provides an overview of features and enhancements included in Oracle Fusion Applications 11gR1 Release 11.1.1.10.0 and
applicable updates. It is intended solely to help you assess the business benefits of upgrading your existing Oracle Products to this release, or
implementing completely new Oracle developed products, and planning your I.T. Projects.
Disclaimer:
This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to
and use of this confidential material is subject to the terms and conditions of your Oracle Software License and Service Agreement or other
applicable contract with Oracle, with which you agree to comply. This document and information contained herein may not be disclosed,
copied, reproduced or distributed to anyone outside Oracle without Oracle’s prior written consent. This document is not part of your license
agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.
This document is intended to outline our general product direction. It is intended for informational purposes only and solely to assist you in
planning for the implementation and upgrade of the product features described. Release information contained in this document is not a firm
development plan. Release information published here should not be used as the basis for customer delivery commitments, as part of marketing
efforts, or during contract negotiations. This is not a commitment to deliver any material, code, or functionality, and should not be relied upon in
making purchasing decisions. The development, release, and timing of any features or functionality, and inclusion or not thereof in the
commercially available version of the Software, if any, is subject to change at any time and is always at Oracle’s sole discretion. This document is
not considered part of the applicable program documentation.
Due to the nature of the product architecture, it may not be possible to safely include all features described in this document without risking
significant destabilization of the code.
Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential. Page 1 of 73
Document Control
Date Author Version Change Reference
10-April- Ventrapragada Rajasekhar/ Parag 0.1 First Release

2012 Jain/Shesha Shila Bharadwaj R
04 July- Parag Jain 0.2 Details of ‘Changes Only’ functionality
2012
29-Aug-2012 Parag Jain 0.3 Note added for Delivery Option setup under sub-point-20 of Manage
HCM Extract Definition
23-Oct-2012 Ventrapragada Rajasekhar 0/4 Details on Copy and Export/Import functionality
16-Jan-2013 Shesha Shila Bharadwaj R 0/5 Corrected Document and added Criteria Formula , Rollback
19-Mar-2013 Shesha Shila Bharadwaj R 0/6 Added Section on Recursive Scheduling
21-Mar-2013 Shesha Shila Bharadwaj R 0/7 Add Changes Only Attribute level features.
13-May-2013 Shesha Shila Bharadwaj R 0/8 Added Generating DBI for flex fields
03-June- Alison Firth 0/9 Edited guide for publication to MOS
2013
10-Sept- Alison Firth 1.0 Edited guide to include release 8 changes
2013
04-Apr-2014 Alison Firth 1.1 Edited guide to include new UI screenshots
08-Oct-2014 Alison Firth 1.2 Updating guide to include Release 8/9/10 information
03-Dec-2015 Rajesh Jupudi 1.3 Reorganized and added additional content
Documentation on MOS
Note Details
1960148.1 Central Note for all HCM Extracts Collateral
1677090.1 HCM Extract Step-by-Step Definition Approach and Troubleshooting Guide
1964920.1 Oracle HCM Extracts: Running a Changes-Only Extract
1559127.1 Oracle Fusion HCM Extracts User Guide
- HCM Extracts User Guide
- Release 9 Entity Attributes
- Extracts presentation (ppt)
1573099.1 Oracle Fusion HCM Extracts: Delivery Options
1536245.1 How to Enable Logging for Oracle Fusion Global Payroll

1559161.1 Oracle Fusion HCM Extracts FAQs for Release 5
1504483.1 All White Papers for Fusion Applications HCM
1565118.1 Database Items for Extracts and Formulas in Oracle Fusion HCM
1327881.1 Fusion Applications Technology: Master Note on Business Intelligence and Reporting
1340506.1 Important Documentation for Business Intelligence and Reporting, contains troubleshooting
documentation, all the guides for BI publisher.
1595283.1 Oracle Fusion Human Capital Management File-Based Loader for Release 7. This document contains
good information about setting up the extract and viewing its results.
1429892.1 Defining a Simple HR Outbound Interface Using HCM Extracts
- Glossary of terms like database item, data base item group, user entity, contexts
- Overview of the extract definition, parameters, data groups, data group connections, data group
criteria, attributes
- Designing the extract structure
- Creating an extract definition
Contents
Document Control...................................................................................................................................................................................................... 2
Documentation on MOS ............................................................................................................................................................................................ 3
1. Overview ................................................................................................................................................................................................................ 6
1.1. Tasks .............................................................................................................................................................................................................. 7
1.2. Architecture ................................................................................................................................................................................................... 8
2. Extract Components............................................................................................................................................................................................... 9
2.1. Definition ....................................................................................................................................................................................................... 9
2.2. HCM Extract Types ....................................................................................................................................................................................... 13
2.3. Using Different Modes for HCM Extracts ..................................................................................................................................................... 14
3. Worked Example .................................................................................................................................................................................................. 17
3.1. Manage HCM Extract Definitions ................................................................................................................................................................. 20
4. Migrating an Extract............................................................................................................................................................................................. 35
4.1. Copying an Extract ....................................................................................................................................................................................... 35
4.2. Export/Import of Extract .............................................................................................................................................................................. 35
5. Refine HCM Extracts ............................................................................................................................................................................................ 36
5.1. Context Binding ............................................................................................................................................................................................ 38
6. Submit HCM Extracts ........................................................................................................................................................................................... 39
6.1. Recursive Scheduling ................................................................................................................................................................................... 39
7. Other details ........................................................................................................................................................................................................ 42
7.1. View HCM Process ....................................................................................................................................................................................... 42
7.2. Rollback an Extract Run ............................................................................................................................................................................... 43
7.3. Generate DBIs for Customer Defined Flexfields .......................................................................................................................................... 44
8. How to define Fast Formula ................................................................................................................................................................................. 46
8.1. Sample Formula ........................................................................................................................................................................................... 50
8.1.1. Flow Schedule .......................................................................................................................................................................................... 50
8.1.2. Data Group Criteria Formula:................................................................................................................................................................... 50
8.1.3. Rule type Formula: ................................................................................................................................................................................... 52
9. Integration with BI Publisher ............................................................................................................................................................................... 57
9.1. Installing BI Publisher Plug-in ....................................................................................................................................................................... 59
9.2. Defining the Report...................................................................................................................................................................................... 63
1. Overview
Use HCM Extracts for archiving, reporting, and as an outbound interfacing tool. HCM Extracts is primarily an outbound integration tool that lets
you choose the HCM Data, it then gathers it from the database, then processes and archives it. HCM Extracts can then convert this archived data
to a format of your choice and deliver to recipients. This document includes information on how you can use the HCM Extract tool to create
outbound interfacing, or reporting.
The Data Exchange work-area allows you to perform tasks related to inbound and outbound interfaces, which allows exchange of data between
different HR systems.
1.1. Tasks
1.1.1. Manage Extract Definitions

Define new extracts, edit/modify or delete existing extracts using the Simplified or Professional interface. The Simplified interface is an easy-to-
use graphical interface for defining and designing HCM extracts. You can access the Professional interface by clicking the Switch Layout button
on the Manage HCM Extract Definitions page.
Extract definition contains details of what data you want to extract and the structure in which you need to extract the data, and how you want
to deliver this data (ftp, email, fax, etc) as formatted output (xls, csv, pdf, etc) using BI publisher.
You can copy an extract in the same instance and also export or import extracts.
1.1.2. Refine Extracts

When we create an extract, the application creates a flow pattern (i.e. checklist) automatically, which includes a task for executing the extract.
So to run and extract the output, we need to use the flow pattern / task. We can (1) refine the flow by adding pre or post tasks that need to be
executed along with data extraction (2) bind context to the parameter
1.1.3. Submit Extracts

Submit the extract for processing after entering the parameter values. If the extract definition contains delivery options that specify an output
format and delivery method (email, ftp, etc), then the output will be generated through the integration with BI Publisher application. Otherwise
a raw XML would be generated.
1.1.4. View Extract Results

Archived output stored in tables can be viewed at anytime through Results UI.
1.2. Architecture
The extracted data is retrieved from the database, through different means, for example, Fast Formula, Balance Groups and Custom Logic
defined in PLSQL or Java method.
A HCM Extract definition contains records that contain multiple attributes. These records are archived based on Fast Formula Database Item
(DBI) groups, or based on the structure of the balance group, or based on logic defined in PL-SQL or Java method.
The extracted data is archived into result tables and stored as an XML output in the database. This XML output is transformed into formatted
output of HTML, PDF, EFT, XLS, etc and delivered as email, fax, ftp, print, based on the delivery options set up for the extract.
2. Extract Components
The HCM Extracts feature is a flexible tool for generating data files and reports. This topic covers how you can use the extract components to
define what information you want the application to extract and report on. It also explains how the application displays, formats, and delivers
the information.
2.1. Definition
An extract definition refers to the complete setup of an extract, which consists of extract data groups, criteria, records, attributes, advanced
conditions and output delivery options. An extract definition consists of:
o One or more extract data groups, depending on how many logical entities you want to extract.
o One or more extract records depending on how many groups of information you want to collect.
o One or more attributes depending on how many individual fields of data you want to collect.
You use HCM extracts to extract, archive, transform, report, and deliver high volumes of HCM data from the Fusion HCM database. You can
generate the output in a variety of formats like CSV, XML, Excel, HTML, RTF, PDF.
You can distribute the extracted information to destinations like FTP, UCM and by e-mail, fax and other delivery modes (Note that some of these
delivery destinations are not applicable for cloud installations). Some common examples of extracts are: PDF payslips delivered to employees'
mailboxes, payroll or benefits data transferred to third-party service providers, HR and talent data exchange between Fusion and legacy
applications, for example in a coexistence scenario.
2.1.1. Design
2.1.1.1. Data Groups

Extract data groups represent a business area or logical entity, for example person, assignment, or benefits. The application uses this
information to retrieve the database item groups. You define one data group as the primary or root data group and this data group is the
starting point of the data extraction.
Extract data group connections capture the association details between the current data group and the parent data group. The data group
connections form the hierarchical relationship among the data groups.
You can define a set of filtering conditions the application must perform on an extract data group using the extract data group criteria. You
specify the criteria conditions using an expression or fast formula.
2.1.1.2. Extract Records

Extract records represent a grouping of related data or a physical collection of all fields required in the extract. For example, the Employee data
group can have records such as Basic Details, Pay Details, Location Details, and Primary Contact. An extract record is a collection of attributes
which you can organize in a required sequence. For example, if a data group has 3 records, then you can specify the sequence in which the
application processes the records. You can also select the next data group to identify which data group the application processes next.
2.1.1.3. Attributes
Attributes are the individual fields inside the extract record. An attribute is the lowest attribute level of a HCM extract and represents a piece of
information, for example, person first name, person last name or person date of birth.
2.1.2. Delivery Option

You specify delivery options as part of the extract definition. Delivery option parameters specify the output format, the delivery method (email,
FTP), and other parameters required for integration with BI Publisher layer.
2.1.2.1. How Delivery Options Work

HCM Extracts archives the extracted data into result tables and stores it as an XML output in the database. The application transforms the XML
output into a formatted output such as HTML, PDF, EDT, or XLS. The formatted output is then delivered through email, fax, FTP, or print,
depending on the delivery options you set in the extract definition. You can define delivery options for an extract using a BI Publisher template,
with the following delivery file output types: PDF, XLS, XML, DOC, and the following delivery modes: FTP, email, and fax.
2.1.2.2. Using Delivery Types

The type of delivery you select determines the destination of the extract. Some delivery types require additional information. You can select
Documents of Record as the delivery mode to store the output in the database and allow employees to view the output from document of
records. An example of a document is a payslip. If the XML output is split and burst as separate files, then you can select the bursting node. For
example, if you want all employees to receive an email with their payslip, then set the bursting node to Employee_ID. Select the HCM Connect
delivery type to create extracts with encrypted or non-encrypted data and transmit them to Oracle WebCenter Content. You can then transfer
the data manually or using your own scripts to your own server.
2.1.2.3. Delivering Data to Oracle WebCenter Content Using HCM Extracts

You can deliver encrypted and unencrypted files using HCM Extracts to Oracle WebCenter Content. You use the HCM Connect delivery type in
the Deliver page of the Manage Extract Definitions task to create an extract to send to Oracle WebCenter Content. HCM Extract transfers the file
to Oracle WebCenter Content. You can then transfer the files manually, or write scripts to perform the transfer. By selecting the HCM Connect
delivery type you can enter additional details to ensure the extract is identifiable in Oracle WebCenter Content. For example, specify the
integration name, select whether you want to encrypt the file using the encryption mode, and a file name for your reference. This additional
setup ensures the document has the correct encryption mode and is stored in Oracle WebCenter Content with a specific filename.
For more information see the Oracle Fusion HCM Extracts: Delivery Options whitepaper in MOS: 1573099.1
2.1.2.4. Dynamic Output Filename

When configuring the output filename in the delivery option, you can use the following parameters:
Parameter What it does to the filename
%y Displays the system date year in four digits: Example: 2011
%m Displays the system date month in two digits: 01-12 (where 01 = January)
%d Displays the system date in two digits: 01-31
%H Displays the system date hour in two digits based on 24-hour day: 00-24
%M Displays the system date minute in two digits: 00
%S Displays the system date number of seconds in two digits: 00 - 59
%l Displays system date milliseconds in three digits: 000 – 999
%edy Displays the effective date year in four digits: Example: 2011
%edm Displays the effective date month in two digits: 01-12 (where 01 = January)
%edd Displays the effective date in two digits: 01-31
%edH Displays the effective date hour in two digits based on 24-hour day: 00-24
%edM Displays the effective date minute in two digits: 00
%edS Displays the effective date number of seconds in two digits: 00 – 59
Sample configuration using above parameters in the Output Name:
Perform the following steps to base the output filename on an attribute of the extract:
1. Add ‘%de’ in the output name where you want the attribute to appear. The tag is replaced with the attribute value.
2. In the additional details section, assign the ‘Run Time File Name’ property of the Delivery Type, with the attribute. This will indicate the
attribute value that should be assigned at the ‘%de’ location.
For the above setup, Department Name is suffixed in the filename. If ‘Vision Corporation’ is the department name, then the extracted output
filename will be ‘File_Vision Corporation’.
Perform the following steps to base the output filename on a parameter value:
a) Create an attribute of type 'Parameter Element'.
b) Assign the ‘Run Time File Name’ property of the delivery type with the attribute.
c) Place the ‘%de’ at the appropriate place in ‘Output Name’
Perform the following steps to base the output filename on complex logic:
a) Create an attribute of type ‘Rule Based’ which has the underlying logic defined in a Fast Formula.
b) Assign the ‘Run Time File Name’ property of the delivery type with the attribute.
c) Place the ‘%de’ at the appropriate place in ‘Output Name’.
Note: Post sql default is not advisable for effective date defaulting in a recurring schedule.
2.2. HCM Extract Types

The type of extract you select determines the purpose of the extract. It also determines the parameters that are automatically generated. For
example, if you select the Payroll Interface extract type, then the application creates a changes only parameter, as well as the other parameters.
You can select the extract type on the Manage HCM Extract Definitions page.
This table lists the different extract types and why you select them.
Extract Type Purpose Comments

Full Profile Use for complete employee and payroll data archives.
Payroll Interface Use for providing data to third party payroll service providers.
Payments Use for salary payment method archives. For example, Paid through cheque or bank Development use only
transfer.
Benefit Carrier Use for providing data to third party benefits service providers.
Archive Retrieval Use for reports based on permanently archived data, for example, payslip.
EOY Archive Use for end of year archives (HR, Benefits). Development use only
HR Archive Use for all HR archives.
Payroll Archive Use for all payroll or payslip archives. Development use only
Other Payroll Archive Use for all payroll archives.
2.3. Using Different Modes for HCM Extracts

You can create an extract to output data in different modes in the Manage Extract Definitions page. Use modes to extract data that has changed
since the previous extract runs. For example, you can extract employee details whenever there is a change in the employee's location. The
processing engine generates the current status of the data, compares it with the base-lined data of the previous runs, and identifies the new as
well as any modifications. The output from such changes-only extract has the incremental data only.
You can manipulate the output in a changes-only extract to either exclude or include certain attributes, regardless of whether the attribute has
changed or not. For example, by selecting an option to exclude an attribute from comparison, you can ensure that that attribute is not compared
while identifying changes to include in the generated output of the next extract run. Therefore, even if the attribute has changed since the
previous extract run, it will not be included in the output. You can also select an option to always include an attribute in the generated output of
an extract run, even if the attribute has not changed.
2.3.1. Extract Modes

To enable different modes in an extract, you include the CHANGES_ONLY parameter and set up threading details in the extract definition. While
running the extract you can use the CHANGES_ONLY parameter to control the extract mode. For example, to find out if the job name has
changed on a person's assignment, set up multi-threading database items at assignment level and include the CHANGES_ONLY parameter. When
you run the extract in the ATTRIBUTE mode, the extract compares data from the multi-threading level and outputs the incremental changes. You
can link the PER_EXT_CHANGES_ONLY lookup to the CHANGES_ONLY parameter so that you can select a mode when you submit the extract.
2.3.1.1. What's a threading database item and what is its connection to the extract data group?
A threading database item is required for implementing the Changes Only feature. The threading database item is a unique ID in the chosen user
entity (UE). Generally, for Pay Employee UE and Assignment UE it would be DBI with %ASSIGNMENT%ID. For Person UE, it would be DBI with
pattern %PERSON%ID. You can declare one threading database item at the root data group or any child data group level. For example, you
declare the threading database item from the location where you need changes only.
The following table describes the different extract modes, their lookup values and descriptions.
Mode Lookup Value Description
N All attributes Includes all data in the extract. A full extract is run which produces the full data output at
that point of time. The archived data is utilized as a baseline.
Y Changed attributes Compares this extract run with the previous extract runs and by comparing against the
baseline (to identify the incremental data), displays the data that has changed only.
ATTRIBUTE Changed and marked attributes Includes elements that have changed or marked as mandatory
ATTRIB_OLD Changed and marked attributes with Displays elements that have changed or marked as mandatory plus their previous value
previous values
Note
You must run the Payroll Interface with the Attrib_Old mode whenever you use the US
ADP PayForce Third-Party Periodic Extract.
BLOCK_OLD Changed, marked attributes, Displays the following data under threading data group:
previous data under threading group
Changed data
Data marked as mandatory
Previous values
Parent data group values
BLOCK Changed and marked attributes Displays the following data under threading data group:
under threading group
Changed data
Data marked as mandatory
Parent data group values
For more information see the Oracle HCM Extracts: Running a Changes-Only Extract whitepaper in MOS: 1964920.1
3. Worked Example
This example demonstrates how to create a HCM extract including creating data groups, records, and attributes using the simplified interface.
You create an extract definition to capture the details of what you want to extract, the structure in which the data must be extracted and how
you want to deliver this data. FAST Bank is a global organization with subsidiaries all over the world. As part of an external reporting
requirement, FAST Bank must obtain the department and employee details across the entire company. This information must be sent to a third
party in an XML file and to the HR manager with employee details grouped by department as a Headcount Report.
The following table summarizes the key decisions in this scenario:
Decisions to Consider In This Example
How many extracts do I need to create You create one extract definition to define a headcount report.
to produce this type of report?
What type of extract do I create? You create a HR Archive extract.
How many data groups do I need to In this example there are 2 functional groups of information, therefore you create two data groups,
create? one for department and one for employees.
How many records do I need to create? You decide the number of records based on the sub-group of attributes within a data group. In this
example, you create two records for the department data group:
 Department Details
 Department Summary
You create one record for the Employees data group: Employee Details.
How many attributes do I need to You decide the number of attributes based on the specific information required for that report. In
create? this example, create the following attributes for the Department Details record:
 Department Name
 Department Location
For the Department Summary record, create the following attributes:
 Record Code
 Report Date
 Employee Count
For the Employees Details record, create the following attributes:
 Full Name
 Gender
 Date of Birth
 Salary
 Bonus
 Tax Rate
Do I need to create any fast formulas? You can use fast formulas at the following levels:
 Extract Criteria level to determine certain conditions.
 Extract Rule level to derive attribute values.
 Extract Advanced Condition level to specify complex conditions.
 Extract Record level to automatically generate formulas when you use the Generate Formula
option.
Fast Bank Extract Design

This Extract consists of 2 logical entities or data groups (i.e. Departments, Employees), which consists of few records in each data group and
different type of attributes.
Data
Groups
3.1. Manage HCM Extract Definitions

1. Click on the Data Exchange work area to perform tasks related to extracts.
2. Click on the Manage HCM Extract Definitions task and select the Create button.
2. Enter FAST Bank Extract, 01/01/2010 and select HR Archive as the extract type, and click ok.
The application creates the definition and you navigate to the Manage HCM Extract Definitions page in the Simplified interface:
The Tag Name field is derived and defaulted automatically based on the extract name you enter (for all levels, such as: definition, parameters,
data groups, records and attributes) and is used while generating the XML output.
3. Click Save and the application saves the extract definition and automatically generates the parameters based on the type of extract. The
parameters control the output of an extract. In this example, the application creates the following parameters:
o Effective Date
o Legislative Data Group
o Parameter Group
o Report Category
o Request ID
o Start Date
Note: Use the Switch Layout button to open the extract in the professional interface. Use the professional interface to create and define HCM
extracts without using a drag and drop system. You can perform most of the tasks for defining the extract in the Simplified interface. To enter an
effective date for the extract, you must switch to the professional interface. The session effective date is an effective start date that applies to all
date-effective interactions in the current session.
NOTE: Change the Session Effective Date to a fixed value (for example: 01/01/2000) before you create or update any data. Entities such as
criteria, records, attributes are date effective and dated; therefore if you create or edit the extract setup with different Session Effective Dates
then those entities will have different dates. The extract definition may produce non-uniform archive for different dates.
Creating Extract Data Groups
1. Select the Design icon to create the data groups.
2. Select the Create icon or use the HCM Data Objects tree to drag and drop a data group into the local area. A data group represents data
that belongs to one or more logical data entities. User Entity (Logical Entity) is the name of the query for fetching the required data, for
example, departments and employees.
The HCM Data Objects tree displays the key DBIs based on the selected extract type and organizes them into a hierarchy for easy
viewing and searching. DBIs are grouped into folders such as Worker, Person, Contacts, and Assignment, which makes it easier for you to
identify or select the required DBI. You can access and search for DBIs that are not available in the HCM Data Objects hierarchy using the
Extracts Attributes section.
3. Add the following details to the data group:
Field Name Entry
Name Departments
User Entity PER_EXT_SEC_ORGANIZATION_UE
Root Data Group Yes (By selecting this checkbox you select this data group as the starting point for the extract execution.)
4. Select Save and create another data group with the following information:
Field Name Entry
Name Employees
User Entity PER_EXT_SEC_ASSIGNMENT_UE
Root Data Group No
Creating Extract Data Group Connections
1. Ensure you enter the following details to create the extract data group connections. Data group connections enable you to define the
master-detail of parent-child relationship between the entities. For example the Department and Employees data groups are linked with
Department ID.
2. Complete the general fields, as shown in this table:
Field Name Entry
Parent Data Group Departments
Parent Data Group Database Item PER_EXT_ORG_ORGANIZATION_ID
Data Group Database Item PER_EXT_ASG_ORG_ID
Define the data group criteria for each data group. Data group criteria enables you to specify the filter conditions of what data you want to
archive. You can specify the filter conditions as an expression or fast formula.
Once all data group connections are defined, select each data group available under the Extract Data Group folder and define the criteria and records for each
data group. Using the Extract Data Group Criteria, you can specify the filter conditions of what data you want to extract. Also, you can specify the conditions as
an expression and/or fast formula. You can add data group criteria; click on the ‘Add’ button in the Extract Data Group Criteria table.
You can define data group criteria expression using the Edit icon in ‘Criteria Expression’. Data Group criteria expression is translated into WHERE
clause of SELECT query and provides better performance compared to criteria formula.
You can create data group criteria formula using the ‘Manage Fast Formulas’ UI and by selecting the ‘Extract Criteria’ formula type. The formula
returns a single value called either ‘EXCLUDE’ or ‘INCLUDE’, has a value of ‘TRUE’ or FALSE’ and determines whether to process the record.
More details on Fast formulas can be found here
Creating Extract Records
1. Select the Department Data Group and ensure it includes the following extract record details. Extract records represent a physical
collection of all required fields. If a data group has 3 records, then you can specify the sequence in which the application processes the
records using the sequence field. You can also select the Next Data Group to identify which data group the application processes next.
2. Select the Configure icon and then Create Record. Complete the general fields, as shown in this table:
Field Department Summary Department Details
Name Department Summary Department Details
Effective Start Date 1/1/00 1/1/00
Sequence 20 10
Type Trailer Record Header Record
Process Type Fast Formula Fast Formula
Next Data Group NA Employees
3. Save the records and then select the Employees Data Group. Ensure this data group includes the following extract record details.
Field Name Entry
Name Employee Details
Effective Start Date 1/1/00
Sequence 10
Type Detail Record
Process Type Fast Formula
Creating Attributes
1. Select the Departments Details record within the Department Data Group and ensure it includes the following extract attribute details.
Field Name Attribute Entry Attribute Entry
Name Department Name Department Location
Type Database item group Database item group
Database Item Group Organization Name Organization Location Country
3. Select the Department Summary record and ensure it includes the following extract attribute details.
Field Name Attribute Entry Attribute Entry Attribute Entry
Name Record Code Report Date Employee Count
Data Type Text Date Number
Type String Parameter Element Summary Element
String Value 999 NA NA
Parameter Effective Date NA NA
Aggregate Function NA NA Count
Aggregate Record Name NA NA Employees Employee Details
5. Select the Employee Details record within the Employees Data Group and ensure it includes the following extract attribute details.
Name Full Name Gender Date of Birth
Start Date 1/1/00 1/1/00 1/1/00
Data Type Text Text Date
Type Database Item Group Decoded database item group Database item group
Database Item Group Person Full Name Person Gender Person Date of Birth
Name Salary Bonus Tax rate
Start Date 1/1/00 1/1/00 1/1/00
Data Type Number Number Text
Type Database item group Record Calculation Rule
Database Item Group Assignment Salary Amount NA NA
Calculation Expression NA Salary * 0.5 NA
Rule NA NA FAST Bank Tax Rule
Attributes with ‘Database Item Group’ as the type are associated with a fast formula database item that corresponds to SQL query for fetching
the field value (For example: Organization Name, Person Full Name, Job Name, etc.).
You can add conditional actions to records and attributes within a record, that specify an action, such as, log error or warning, to be performed
when the condition is evaluated as true. You can specify a condition as an expression or as fast formula. Define formula using ‘Manage Fast
Formulas’ UI with formula type as ‘Extract Advanced Condition’, and return value of Y or N for output variable DO_ACTION.
Defining the Delivery Options
1. Select the Deliver icon and then the Add icon to define the delivery options.
Field Value Value
Start Date 1/1/00 1/1/00
End Date 12/31/12 12/31/12
BI Publisher Template ReportLayout EFTLayout
Output Type PDF EFT
Delivery Type E-mail FTP
Delivery Option Name E-mail to HR FTP to 3rd Party
Output Name HeadcountReport EFTReport
3. Ensure you enter the additional information such as, the server, username, and password for the FTP delivery type.
4. Enter FAST Bank Extract as the reporting category and click Submit.
Validating the Extract
1. View the extract definition details and ensure the structure is valid in the Validate page by selecting the Validate icon.
2. Review any automatically generated connections. Connections are created automatically if the same database items exist across data
groups.
3. Select Export XSD to download the XML Schema Definition (.XSD) file for this extract setup. This exported file contains the structure of
the extract definition: the data groups, records, and attributes. You can view the exported XSD through any browser.
You can define delivery options for an extract using a BI publisher template, with the following delivery file output types: PDF, XLS, XML, DOC,
and the following delivery modes FTP, email, fax. You can also choose Documents of Record as the delivery mode. This delivery mode enables
you to store the output in the database and allows employees to view online payslips from documents of record. If the XML output is split and
burst as separate files, then you can select the bursting node. For example, if you want all employees to be sent an email with their payslip, then
set the bursting node to Employee_ID.
1. After defining the extract [setup and structure] details, define the formatting or layout options using BI Publisher.
More details on BI Publisher are available here.
Integration of extracts and BIP (the ability to view output directly from extracts UI rather than navigating to BI) is available in Release 4.
This allows users to view the output directly after the extract process is complete.
2. Save the BI report in any of the 'Shared Folders' locations (accessible to all logins), instead of the 'My Folders' location (accessible to the
logged in user only). Users on Release 3 SaaS environments should contact their BI admin to create the required folder structure.
3. Specify the extract delivery option with the BI report path and the process can access the report and show the output directly from the
UI. The suggested values are:
4. Report path: /Custom/Human Capital Management/ReportName.xdo
5. Template name: Layout name
Submitting an Extract
An extract definition automatically creates an extract process (payroll flow) with the same name as the extract. The extract process enables you
to define an execution sequence of multiple tasks, including pre and post tasks.
1. Select the Submit Extracts task and select the FAST Bank Extract process.
2. Select Next.
3. Enter FAST Bank Extract - Jan 2012 as the Payroll Flow (extract process).
4. Enter 1/1/15 as the End Date.
5. Select Next. You can specify interaction details if the task is dependent on other tasks with different extract processes. For example, this
task must wait because another task is running.
6. Select Next and review the extract. You can schedule the extract, or run it immediately.
7. Select Submit.
8. Select OK and View Checklist to view the status of the process.
9. Select the View Extract Results task to review the results of the extract run. Search for the FAST Bank Extract process.
10. Select Go to Task for FAST Bank Extract - Jan 2012, click the eyeglasses, and view the report output by selecting the report name.
You can navigate to any data group or record in the extract definition by clicking the links in the navigation tree. To view the complete execution
tree, select the Extract Execution Tree option. This action validates the extract definition setup and the application provides validation messages,
along with fast formula compilation status.
Click on the Export to XML Schema button to download the XML Schema Definition (.xsd) file for this extract setup.
After defining the extract [setup and structure] details, define the formatting or layout options using BI Publisher.
More details on BI Publisher are available here.
4. Migrating an Extract
There are multiple ways in which you can create a copy of an extract, migrate an extract from one instance to another. ‘Copy’ will let you create
a copy of the extract in the current instance, while ‘Export’ along with ‘Import’ lets you migrate the extract to another instance. You can also use
the FSM migration tools to migrate incremental changes, and multiple extract at the same time. Refer to the FSM documentation for more
details.
4.1. Copying an Extract

You can use the Copy facility to make a copy of an existing extract.
1. Search and select the extract that you want to copy, and click on the Copy button.
2. Specify the new extract definition name, and click on Ok. A new extract is created and displayed in the search list, (the new extract definition
includes parameters, data groups, records, attributes).
4.2. Export/Import of Extract

You can create a copy of an existing extract within the instance or across instances (i.e. Test to Production instance – instead of re-creating the
complete extract manually), then you can use the Export-Import option.
1. Search and select the extract that you want to export, and select the Export XML Schema button.
2. Select the Save File option and save it to local file system [complete extract definition setup information is downloaded as XSD file].
3. Select the instance where you want to export this extract, and select the Import XSD File button.
4. Specify the new extract definition name, select the legislative data group and the XSD file you downloaded earlier, and click on Ok. The
application creates a new extract and you can query the extract from the search region.
5. Refine HCM Extracts

After you define an extract a flow pattern is automatically created with the same name as the extract. The flow pattern enables you to define an
execution sequence of multiple tasks, and enables you to add any pre or post tasks along with extraction of data (default task that is created
automatically).
You can:
 View and modify the flow pattern using the Refine HCM Extracts task.
 Search for existing flow patterns and select Edit to view or modify.
 Add additional (pre or post) tasks (if needed).
 Modify the sequence in which you want to execute these tasks (if needed).
 Define additional parameters to use across multiple tasks in the flow pattern (if needed).
 Edit parameters by selecting the required parameter row and clicking on the Edit Icon.
When a Parameter is created in HCM Extracts Setup UI it is automatically visible in the flow to refine. If you want to associate a common lookup
with the parameter, then select the required parameter, and click on the Edit Icon on the top of table.
Select Display Format and choose ‘Lookup Choice List’. In the lookup field provide the common lookup code you want to display. This lookup is
displayed for the parameter when you submit the process.
5.1. Context Binding

Use context binding to dynamically increment date parameters, especially for scenarios where you want to recursively schedule extract runs.
The parameter details should specify Context Binding for the parameter basis, and System Date for the basis value.
For example, you might have an extract that retrieves data based on an effective date. In the Refine HCM Extracts UI, you need to specify the
Context Binding for the ‘Effective Date’ parameter with parameter basis as ‘Context Binding’, and Basis Value as ‘System Date’. Setting these
parameters ensures that the dates the application derives from the defaulted date parameter are incremented appropriately.
6. Submit HCM Extracts

You can submit an extract run to run immediately or run as per a schedule. You can also recursively schedule an extract such that the extract will
run as per a schedule like daily, weekly, monthly or custom.
6.1. Recursive Scheduling

You can select the following options for recursive scheduling: Daily, Weekly, and Monthly. If you want to create a custom schedule, then you
create a Fast Formula of type ‘Flow Schedule’. You can create a custom schedule by creating a fast formula with Flow Schedule and return when
next flow has to be run, for example, gap in days.
Use Case: You require recursive scheduling for every 5 minutes.
1. Create a fast formula with Flow Schedule as the type.
2. Write formula to return number of days as gap. In this case since we require 5 minutes, return, ((1/24)/60)*5 days as return value for
flow schedule formula.
3. Follow same steps to Submit HCM Process, including below values in ‘Schedule’ section.
The instance is generated every 5 minutes from when the process is submitted.
7. Other details
7.1. View HCM Process
View HCM process allows you to view the results of an extract run. Search for the different runs of extract by entering the Flow Pattern name.
Select the flow instance name to display the status page and select the Go to Task icon to show the report output.
7.2. Rollback an Extract Run

Open Payroll Checklist >Submit a Process or Report, select the ‘Roll Back Process’ task.
Enter the Payroll Flow name to indicate it to be a Roll back run instance. Select the Payroll Process Lookup and select the Payroll Flow or Instance
that you want to roll back. This Payroll Flow or Flow Instance can be Changes-Only run also. Submit the flow and select the ‘Ok and View
Checklist’ option.
7.3. Generate DBIs for Customer Defined Flexfields

The Generate Database Items process allows you to generate DBIs for the flexfields associated with particular context.
Navigator > Payroll Checklist
1. Select the 'Submit a Process or Report' option.
2. Search and select for Generate Database Items.
3. Provide a unique free text value for the Payroll Flow field.
4. Provide a valid DDF or EFF name for 'Name' and valid context related to the EFF typed in for 'Context'.
A list of the most frequently used flex-fields which support the above:
PER_ORGANIZATION_INFORMATION_EFF, PER_ACCRUAL_PLAN_LEG_DDF, PER_ASG_LEG_DDF, PER_ASSIGNMENT_EIT_EFF, PER_JOBS_EIT_EFF,

PER_JOBS_LEG_EFF, PER_LOCATION_INFORMATION_EFF, PER_LOCATION_LEG_EFF, PER_PERSON_EIT_EFF,
PER_PERSON_LEGISLATIVE_DATA_LEG_DDF, PER_PERSON_NAME_LEG_DDF, PER_POSITIONS_EIT_EFF, PER_POSITIONS_LEG_EFF,

PER_PPS_LEG_DDF
7.4. Web Services

HCM Extracts uses the payroll flows infrastructure to run an Extract. When we create an extract, the application creates a flow pattern (i.e.
checklist) automatically, which includes a task for executing the extract. It is actually the flow infrastructure that calls the extracts processing
engine and extracts the data when an extract is run.
The flows infrastructure has web services to (1) run, (2) check the status and (3) rollback. The same web services can also be used to submit an
extract, check the status of an extract and rollback an extract run.
For more details on the web services, refer to the payroll flows documentation.
8. How to define Fast Formula

You can launch the Manage Fast Formulas UI from the Navigator Menu – Payroll Calculation workarea - > Manage Fast Formulas task.
The following table lists the different types of formula you can use for extracts:
Formula Type Description
Extract Criteria Formulas of this type will be listed in the Data Group Criteria Fast formula list, can be used for specifying complex criteria
which indicates if record should be extracted or not
Extract Rule Formulas of this type will be listed in the Rule type Attributes Fast formulas list can be used for deriving/calculating attribute
value if it is based on complex logic or business rules
Extract Formulas of this type will be listed in the Record/Attribute Advanced conditions Fast formulas list can be used for specifying
Advanced complex conditions which indicates if actions (eg: log error/warning) should be raised.
Condition
Extract Record Formulas of this type will be generated automatically when using ‘Generate Formula’ option in Extract Records.
You can query/view/edit/create formulas from this UI. Fast formula can contain any complex business logic, and you can use it along with
extracts.
Enter the relevant fast formula details and select the Continue button. Enter the formula text in the Manage Formula details page.
[Sample Extract Rule formula text is given below]
Extract Rule formula should have value returned through variable ‘RULE_VALUE’
Similarly extract criteria (data group criteria) formula should have value returned through variable INCLUDE/EXCLUDE and return value as
TRUE/FALSE.
[Sample Extract Criteria formula text is given below]
8.1. Sample Formula
8.1.1. Flow Schedule

Formula to recursively schedule an extract run for every 5 minutes.
/*****************************************************************************
FORMULA NAME: Sample Flow Schedule
FORMULA TYPE: Flow Schedule
DESCRIPTION: Formula to return a date time.
Returns NEXT_SCHEDULED_DATE;
Formula Results:
NEXT_SCHEDULED_DATE This will be a date time value with yyyy-MM-dd HH:mm:ss format.
*******************************************************************************/
/* Inputs */
INPUTS ARE SUBMISSION_DATE(DATE), SCHEDULED_DATE(DATE)
/* Calculations */
NEXT_SCHEDULED_DATE = ADD_DAYS(SCHEDULED_DATE,0.00347)
/* Returns */
RETURN NEXT_SCHEDULED_DATE
/* End Formula Text */
8.1.2. Data Group Criteria Formula:

1) Sample Data Group Criteria Formula to filter based on runtime Department Name.
a) Create Extract Parameter of text type, with name DEP_NAME.

b) Formula to filter based on runtime DEP_NAME
DEFAULT FOR PER_ASG_ORG_NAME IS ' '

dept_name_from_dbi = PER_ASG_ORG_NAME
dept_name_from_param = GET_PARAMETER_VALUE('DEP_NAME')
IF dept_name_from_dbi = dept_name_from_param THEN (
INCLUDE = 'TRUE'
)ELSE (
INCLUDE = 'FALSE'
)
return INCLUDE
===
2) Sample Data Group Criteria Formula to filter based on runtime Relationship Attribute1.
Use case: Here Periods of Service customer flex stores Payroll Provider in ATTRIBUTE1.
a) Create Extract Parameter of text type, with name 'Provider Name' and Ess Parameter name as 'Provider_Name'.
b) Formula to filter based on runtime DEP_NAME
DEFAULT FOR PER_REL_ATTRIBUTE1 IS ' '

rel_attribute1_from_dbi = PER_REL_ATTRIBUTE1
provider_param = GET_PARAMETER_VALUE('Provider_Name')
IF rel_attribute1_from_dbi = provider_param THEN (
INCLUDE = 'TRUE'
)ELSE (
INCLUDE = 'FALSE'
)
return INCLUDE
In the scenarios above, there is a known issue if Payroll Provider Name or Department Name has a space. Ensure that you truncate the
parameter until first space; otherwise the results might have a different output. The following bug needs to be fixed to resolve the issue.
BUG 15921815 - RUP3MAINTAINANCE: SPACE IS NOT WORKING PARAMETERS, UNABLE TO GET SENTENCES
3) Data Group Criteria Formula to deal with Multi Row Data.
DEFAULT FOR "PER_EXT_CONT_CONTACT_TYPE" IS ' '

INPUTS ARE "PER_EXT_CONT_CONTACT_TYPE" (text)
INCLUDE = 'FALSE'
IF ("PER_EXT_CONT_CONTACT_TYPE" = 'M' ) THEN (

INCLUDE = 'TRUE'
)
RETURN INCLUDE
8.1.3. Rule type Formula:
Use case: Get Primary NID of Contact
Get Contact Person Id via Attribute, set PERSON_ID context to Contact Person Id, Get DBI Value of Primary NID to get NID of contact effectively.
By this way you can get any information related to contact.
a) Create an attribute with dbi as 'Extract Contact Person Id’, with short code as 'CONTPID'.
b) Create an 'Extract Rule' Type Formula (CONTACT_NID_FF) with the following text:
DEFAULT FOR DATA_ELEMENTS IS EMPTY_TEXT_TEXT
DEFAULT FOR PER_PER_PRIMARY_NID_NUMBER IS ' '
INPUTS ARE DATA_ELEMENTS (TEXT_TEXT)
X = DATA_ELEMENTS['CONTPID']
CHANGE_CONTEXTS(PERSON_ID = TO_NUMBER(X) )
(
RULE_VALUE = PER_PER_PRIMARY_NID_NUMBER
)
RETURN RULE_VALUE
c) Create Rule type attribute (with Name: Contact NID) as sibling of attribute created in (1) .
Associate CONTACT_NID_FF as fast formula.
Use case: Get Contact Full Name
Get Contact Person Id via Attribute, set PERSON_ID context to Contact Person Id, Get DBI Value of Person Local Name to get Local Name
of contact effectively. By this way you can get any information related to contact.
a) Create an attribute with DBI as 'Extract Contact Person Id’, with short code as 'CONTPID'.
b) Create an 'Extract Rule' Type Formula (CONTACT_LOCNAME_FF) with the following text:
DEFAULT FOR PER_PERSON_LOCAL_FULL_NAME IS ' '
X = DATA_ELEMENTS['CONTPID']
CHANGE_CONTEXTS(PERSON_ID = TO_NUMBER(X) )
(
RULE_VALUE = PER_PERSON_LOCAL_FULL_NAME
)
RETURN RULE_VALUE
c) Create Rule type attribute (with Name: Contact Local Full Name) as sibling of attribute created in (1) .
Associate CONTACT_LOCNAME_FF as fast formula
Use Case: Using Predefined Formula Functions.
You can get availability details of a person using predefined fast formula function between a start date and an end date.

SDATE = TO_DATE(SUBSTR(TRANSLATE(DATA_ELEMENTS['StartDate'],
'01234567890:.-TZ', '01234567890:.- '), 1, 19), 'YYYY-MM-DD HH24:MI:SS')
EDATE = TO_DATE(SUBSTR(TRANSLATE(DATA_ELEMENTS['EndDate'],
'01234567890:.-TZ', '01234567890:.- '), 1, 19), 'YYYY-MM-DD HH24:MI:SS')
RULE_VALUE = to_char(GET_PAY_AVAILABILITY('ASSIGN',SDATE ,EDATE,'Y','Y','N','N','H'))
RETURN RULE_VALUE
Use Case: Working with Array DBIs
Get all Contact Names, comma appended as single item.
Create a root data group with Assignment User entity, which sets context of Person Id. PER_EXT_CONT_FIRST_NAME will return you array of
contact names associated with the person.
Create a Rule Element with the following code and associate it with a attribute (Contact Names) in root data group.
DEFAULT_DATA_VALUE for PER_EXT_CONT_FIRST_NAME IS ' '
I=1
N=''
WHILE PER_EXT_CONT_FIRST_NAME.EXISTS(I) LOOP

(
IF I <> 1 THEN
(
N = N || ','
)
N = N || PER_EXT_CONT_FIRST_NAME[I]
I=I+1
)
RULE_VALUE = N
RETURN RULE_VALUE
Use Case: Using loop to iterate and get value
You can get the last termination date of an employee.
DEFAULT_DATA_VALUE for PER_HIST_ASG_REL_ACTUAL_TERM_DATE IS '01-JAN-0001'

(DATE)
I=1
MAXTDATE = '01-JAN-0001' (date)
@ DEFAULTDATE = '01-JAN-0001' (date)
WHILE PER_HIST_ASG_REL_ACTUAL_TERM_DATE.EXISTS(I) LOOP

(
IF ( PER_HIST_ASG_REL_ACTUAL_TERM_DATE[I] > MAXTDATE ) THEN (

MAXTDATE = PER_HIST_ASG_REL_ACTUAL_TERM_DATE[I]
)
I=I+1
)
IF ( MAXTDATE = DEFAULTDATE ) THEN (

RULE_VALUE = ' '
) ELSE (
RULE_VALUE = TO_CHAR(MAXTDATE ,'YYYY/MM/DD')
)
RETURN RULE_VALUE
9. Integration with BI Publisher

You can launch BI publisher from the Navigator menu – Reports and Analytics workarea.
Click on the Browse Catalog option to open the BI Publisher Enterprise.
9.1. Installing BI Publisher Plug-in

Template Builder for Word is a plug-in available from BI Publisher Enterprise Home page or you can download it from Oracle link.
This Plug-in provides sample documents, demos, templates and Template Viewer. These will help you understand the concepts and also create
templates (EFT, RTF, etc.) to view formatted output of XML.
After installing the BI Publisher plug-in for MS Word, you can find the Oracle BI Publisher option in the ‘Add-Ins’ tab. Use the ‘Add-ins’ option to
load the structure of data (XSD) using ‘Load XML Schema’ option.
After the ‘Load XML Schema’ is complete, you can arrange fields in the required layout and format, and upload the template to BI Publisher as
mentioned below.
9.2. Defining the Report

The report is based on a BI Publisher Data Model.
You can use the existing standard data model available at this folder location: /Human Capital Management/Payroll/Data
Models/globalReportsDataModel.
This data model contains SQL query to get XML output taking flow instance run name as parameter.
Click on Save to save the report.
There are many options available for defining the layouts of a report.
Based on template uploaded, which can be based on RTF, PDF, etc. created using MS Word plugin
Based on Basic Templates and inbuilt layout editor available in BI Publisher Enterprise
Based on template generate automatically based on selected data model.
You can upload the earlier defined BI publisher RTF template, and test the layout by clicking on ‘View Report’ and you can view the output in the
required file format.
The contents of the Report Layout are displayed below. You can download this report as a pdf file by clicking on the ‘PDF’ option.
The latest data model has the flow instance name parameter along with the Payroll Action ID. The flow instance name is the name of the flow
pattern run which was provided earlier when submitting the extract.
A PDF file is generated and displayed in a new window.
You can upload other templates (for EFT) by defining the layout in MS-Word. You can use the EFT template for generating fixed length delimited
text files.
You must upload the EFT templates as type ‘eText Template’
Test the layout by clicking on ‘View Report’ and view the output in the required file format.
Two tabs – ReportLayout and EFT Layout are displayed.
The latest data model has the flow instance name parameter along with the Payroll Action ID. The flow instance name is the name of the flow
pattern run given earlier when submitting the extract.
The contents of the EFT Layout are displayed below.

HCM Extracts Guide REL10 - RJ PDF

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

HCM Extracts Guide REL10 - RJ PDF

Transféré par

Droits d'auteur :

Formats disponibles

User Guide for HCM Extracts (Release 10 onwards)

HCM Extracts: User Guide for Release 10 onwards

Date Author Version Change Reference

10-April- Ventrapragada Rajasekhar/ Parag 0.1 First Release

1536245.1 How to Enable Logging for Oracle Fusion Global Payroll

Documentation on MOS ............................................................................................................................................................................................ 3

1.1. Tasks .............................................................................................................................................................................................................. 7

1.2. Architecture ................................................................................................................................................................................................... 8

2.1. Definition ....................................................................................................................................................................................................... 9

2.2. HCM Extract Types ....................................................................................................................................................................................... 13

2.3. Using Different Modes for HCM Extracts ..................................................................................................................................................... 14

3. Worked Example .................................................................................................................................................................................................. 17

3.1. Manage HCM Extract Definitions ................................................................................................................................................................. 20

4.1. Copying an Extract ....................................................................................................................................................................................... 35

4.2. Export/Import of Extract .............................................................................................................................................................................. 35

5. Refine HCM Extracts ............................................................................................................................................................................................ 36

5.1. Context Binding ............................................................................................................................................................................................ 38

6. Submit HCM Extracts ........................................................................................................................................................................................... 39

6.1. Recursive Scheduling ................................................................................................................................................................................... 39

7. Other details ........................................................................................................................................................................................................ 42

7.1. View HCM Process ....................................................................................................................................................................................... 42

7.2. Rollback an Extract Run ............................................................................................................................................................................... 43

7.3. Generate DBIs for Customer Defined Flexfields .......................................................................................................................................... 44

8. How to define Fast Formula ................................................................................................................................................................................. 46

8.1. Sample Formula ........................................................................................................................................................................................... 50

8.1.1. Flow Schedule .......................................................................................................................................................................................... 50

8.1.2. Data Group Criteria Formula:................................................................................................................................................................... 50

8.1.3. Rule type Formula: ................................................................................................................................................................................... 52

9. Integration with BI Publisher ............................................................................................................................................................................... 57

9.1. Installing BI Publisher Plug-in ....................................................................................................................................................................... 59

9.2. Defining the Report...................................................................................................................................................................................... 63

1.1.1. Manage Extract Definitions

1.1.2. Refine Extracts

1.1.3. Submit Extracts

1.1.4. View Extract Results

2.1.1.1. Data Groups

2.1.1.2. Extract Records

2.1.2. Delivery Option

2.1.2.1. How Delivery Options Work

2.1.2.2. Using Delivery Types

2.1.2.3. Delivering Data to Oracle WebCenter Content Using HCM Extracts

2.1.2.4. Dynamic Output Filename

Parameter What it does to the filename

%y Displays the system date year in four digits: Example: 2011

%d Displays the system date in two digits: 01-31

%M Displays the system date minute in two digits: 00

%S Displays the system date number of seconds in two digits: 00 - 59

%l Displays system date milliseconds in three digits: 000 – 999

%edd Displays the effective date in two digits: 01-31

%edM Displays the effective date minute in two digits: 00

%edS Displays the effective date number of seconds in two digits: 00 – 59

Sample configuration using above parameters in the Output Name:

a) Create an attribute of type 'Parameter Element'.

c) Place the ‘%de’ at the appropriate place in ‘Output Name’

c) Place the ‘%de’ at the appropriate place in ‘Output Name’.

2.2. HCM Extract Types

Extract Type Purpose Comments

2.3. Using Different Modes for HCM Extracts

2.3.1. Extract Modes

Mode Lookup Value Description

Data marked as mandatory

Parent data group values

Data marked as mandatory