Fusion- EBS Payroll

Connector
Changes to Out of the Box Solution
Abhishek Satti
Archana Kalyanam
Hari Subramanyam
Rupesh Kumar
Rahul Krishna Putumbaka
5/2/2016
Issue 1.0

This document highlights the changes that need to be performed on the delivered Payroll connector Out
of the Box Solution that integrates Fusion HCM with e-Business Suite Payroll implementation. Please
note this is not an implementation guide. Check Oracle Support for latest Payroll Connector
Implementation guide. As of writing this document, we recommend referring to Payroll Integration with
HCM Cloud Release R12 Part No. E20148-01 for more details on Payroll Connector.

Table of Contents
Overview ....................................................................................................................................................... 3
Configure HCM Cloud ................................................................................................................................... 4
Changes require for Worker Extract: .................................................................................................... 8
Changes require for Work Structure Extract: ...................................................................................... 11
Changes require for Compensation Extract: ....................................................................................... 11
Configure EBS .............................................................................................................................................. 12
Create Configuration:.............................................................................................................................. 12
Checking UCM Connectivity: ................................................................................................................... 14
Setting Up Data ....................................................................................................................................... 14
Loading Data ........................................................................................................................................... 15
Scheduling ............................................................................................................................................... 18
Salient Features .......................................................................................................................................... 22

Overview
EBS Payroll Integration with HCM Cloud enables you to integrate HCM on the cloud with e-Business
Suite Payroll implementation. This means that you can use HCM Cloud with your existing e-Business
Suite Payroll.
On the HCM Cloud, you use the HR related tasks such as workforce management, HR information and
benefits management and talent related tasks such as succession planning, performance and goal
management. On the EBS side, you continue to use Oracle Payroll for the payroll related tasks.

This integration enables you to extract and transport employee data along with the necessary set up data
from HCM Cloud and intelligently synchronize selected business object data between Oracle EBS
application HCM Cloud.
After this implementation, users can use HCM Cloud for all HR related functions and continue to use
existing EBS HCM applications for all payroll related functions.
This document lists the changes that we need to perform for:
1. Payroll Connector to establish connectivity between Fusion HCM and Oracle EBS.
2. Correctly importing the delivered Extracts for initial key mapping and exporting Employee and Setup
data.

Configure HCM Cloud

HCM cloud offers certain delivered Extracts for integration using Payroll Connector:
1. Business Object Key Map

2. Worker Extract
3. Work Structure Extract
4. Compensation Changes extract

Changes require for Cross Reference Extract : Business Object Key Map:
1. Make a copy of the delivered Extract with appropriate prefix and suffix:

2. Create a BIP Report with Global reports Data Model:

3. Add Delivery Options to the Extract Definitions:

Output Type: Data

Report: / Custom./ BUSINESS_OBJ_KEY.xdo
Output Name: Any name suffixed by date time
Delivery Type: HCM Connect
Encryption Mode: None

Run Time File Name: Any name suffixed by date time

Integration Name: BOKMAP
4. Running Extract: It is recommended that this extract be run in two steps:
a. First run the extract with Extract Type Global Unique Identification Generation and Key Map
option selected. Business Object as Blank and Process End date as the Date of running of extract.

b. After the process has completed generation of GUID mapping. Run the extract with Extract
Type as Cross Reference File and rest parameters same as above to generate the cross reference file.
This file will be imported later to the EBS system. The purpose of this file is to keep a mapping of Fusion
Setup Data along with their IDs in the EBS Payroll Connector.

5. Verify if there are any duplicates in the table used by above extract. This can be avoided by not
running multiple instances of Extract at the same time. Run below query in BI Publisher. If query returns
any results then the Cross Reference File is likely to fail upon importing file in EBS tables.
select object_name, target_id, count(source_id) ct , min(source_id), max(source_id) from
hrc_loader_batch_key_map group by object_name, target_id having count(source_id) > 1

Changes require for Worker Extract:

Steps 1-3 should be performed in the manner similar to Business Object Key Map Extract. Perform
following steps thereafter.
1. Changes to structure of extract:
a. In Assignment Detail Block and Record make the Business Unit name as hidden and exclude from
comparison. This field is not maintained in EBS and is using incorrect DBI.

b. Do the same for Assignment Status Type User Status and Assignment Business Unit ID. These fields
are not required in EBS and are using incorrect DBI.

c. For Assignment Attribute1, change the DBI to Extract Historical Assignment Attribute1. Do this for all
Descriptive Flex fields. This field is using incorrect DBI.

d. Assignment Hourly Salary Code field should be Hidden in Extract and excluded from comparison:

In case this field is required to be interfaced then this DBI needs to be replaced with following rule:

DEFAULT FOR DATA_ELEMENTS IS EMPTY_TEXT_TEXT

DEFAULT FOR PER_ASG_HOURLY_SALARIED_CODE IS ' '
DEFAULT FOR RULE_VALUE IS 'XX'
INPUTS ARE DATA_ELEMENTS (TEXT_TEXT)
SDATE = TO_DATE(SUBSTR(TRANSLATE(DATA_ELEMENTS['Assignment Effective Start Dat'],
'01234567890:.-TZ', '01234567890:.- '), 1, 19), 'YYYY-MM-DD
HH24:MI:SS')
CHANGE_CONTEXTS(EFFECTIVE_DATE = SDATE)
(
RULE_VALUE = PER_ASG_HOURLY_SALARIED_CODE
)
IF RULE_VALUE = ' ' THEN

(
RULE_VALUE= 'XX'
)
RETURN RULE_VALUE
e.) In Assignment Status Detail Block/record make the Extract Assignment Status Type attribute as
Hidden:

f.) Add the following two attributes to the Extract. DO NOT USE these attributes for any other purposes
in Fusion HCM. These are required by payroll connector to store EBS Person ID and Assignment ID which
will be used during the initialize process to map the keys. AsgAttribute49 should be used to store EBS
Person ID and AsgAttribute50 to store Assignment ID. These fields should be configured in Fusion HCM
and they should be hidden from UI and not available for updates. These will be used only for migrated
data and not for newly hired Persons in EBS. Note: This step impacts data migration to ensure
Attribute 49 and 50 are migrated.

g) Using with Descriptive Flex Fields and Key Flex Fields: No delivered procedure is available in EBS for
DFF and KFF. User need to create their own procedures to handle these. However, delivered extract can
load Data into EBS Staging records. From there onwards custom procedures need to be written. For
more information on using DFF refer to Payroll Connector user guide.
KFF are not supported by extract but user can extract KFF in any of the DFF place holders available in the
extract.
Changes require for Work Structure Extract:
Steps 1-3 should be performed in the manner similar to Business Object Key Map Extract. There are no
extra steps that need to be performed.
Changes require for Compensation Extract:
Steps 1-3 should be performed in the manner similar to Business Object Key Map Extract. There are no
extra steps that need to be performed.

Configure EBS
Before we begin configuring Payroll Connector ensure following patches are applied in the EBS system:
Patch 21900413:R12.PER.C
Patch 22297163:R12.PER.C
Patch 22565203:R12.PER.C
Patch 22739064:R12.FND.C
Patch 22711359:R12.PER.C
Patch 22905642:R12.PER.C
Patch 22972452:R12.PER.C
Patch 23036162:R12.PER.C

HCM CLOUD TO EBS PAYROLL INTEGRATION 12.2

Update HCM CLOUD TO EBS PAYROLL INTEGRATION 12.2
Resolve Invalid package issue
Patch to support UCM based Integration for Release 12.2.X
Supporting patch to enable UCM in HCM Payroll connector
Standard Payroll Connector automation
Standard Payroll Connector Workstructures fix
Standard Payroll connector Working Hour rounding & Object summary
issue

Patch 23090069:R12.PER.C

Standard Payroll connector FTE fix

Create Configuration:
Enter configuration details similar to below:
For SFTP connectivity:

For UCM connectivity:

Please note: 1. Server User name should be present in Fusion OIM with UCM access to fetch files. If not
present, please create a user name with following fields:

2. Payroll connector does not support Federated SSO. Payroll connector uses RIDC to communicate
with UCM which does not support Federated SSO. As of writing this document, development is working
on a patch to change the solution to use Generic SOAP Service to communicate with UCM.

Checking UCM Connectivity:

Address for UCM/SFTP server and ports needs to be added to EBS system firewall Exception list. Please
note that exception should be based on address xxxx-test.fs.em2.oraclecloud.com and not IP address
based. IP address will change on regular basis for optimization purposes. Refer Doc ID 2091590.1

Setting Up Data
1. Importing Cross Reference Data- Please refer to standard payroll connector document for importing
cross reference data. There are no additional setups required.
2. Mapping Cross Reference data - Please refer to standard payroll connector document for mapping
cross reference data. Note: While mapping reference data set for locations which are to be created
Global should be explicitly mapped to blank. All other data set should be mapped to corresponding
Business Groups.
3. Initial Mapping of Primary Ids- This step is used to initialize worker and work Structure extract where
IDs are mapped between Fusion and EBS System. Run the Full Extract of Worker and Work Structure and
place them in UCM/SFTP.
Go To Task Initialize HCM Cloud Data

Enter Parameters:

Click on Continue and submit.

Note: Initialize following objects only.

1. Worker
2. Work Structure
3. Salary
Do not initialize any other object or Load the data set which has been initialized. Since Initialization
Extracts are full Extracts, it is recommended to delete the data set to prevent accidental loading of data
which will begin to update existing objects. For initialization to happen Worker Extract should have DFFs
Attribute49 and Attribute50 with Person and Assignment ID respectively. This has been discussed in
detail in HCM Extract configuration section for Worker Extract.

Loading Data
Loading of data from fusion to EBS comprises of two steps.
1. Import the data from Fusion to EBS staging tables.
The data file created by the Fusion extract from fusion cloud is imported from
UCM/SFTP (based on the delivery options and the payroll Connector configuration)
server. If the Payroll Connector uses the UCM method uses RIDC method of connecting
to the UCM server. This method (RIDC) is restricted to the environments where the
normal SSO is implemented. Where as in the environments for Federated SSO, RIDC
method of file import from UCM is limited. In such scenarios Generic Soap based
request will be used. Solutions to File import in the Federated SSO environments is still
in the delivery pipeline as mentioned in the above section (Create Configuration section;
Point 2).

The standard import program is used to import the data for standard objects. The
import program invoke is done through the import File button on the Import and Load
Data screen as mention in the below screen shot.

The import button invokes the import program Import HCM Cloud Data File for Payroll
Integration accepting the parameters based on the method of import (UCM/SFTP).
Below screenshot shows the data import using SFTP.

The file name and configuration values would differ in case of UCM and SFTP method of
File Transfer.
Parameters
Configuration

UCM Method of File Transfer

Configuration created for UCM
Ex:B03_TO_HCUX_UCM

SFTP Method of File Transfer

Configuration created for
SFTP
Ex:B03_TO_HCUX
Data Set Name
User Defined Name
User Defined Name
Ex:WORKRELATIONSHIP_H3G_ Ex:
WORKER_10052016212118
WORKRELATIONSHIP_H3G_W
ORKER_10052016212118
File Name
UCM ID should be given
File Name with extension
Ex: UCMFA016770
should be given
Ex:
H3G_WORKER_10052016212
118.xml
Business Object Business Object we want to
Business Object we want to
import
import
Ex: Worker
Ex: Worker
NOTE: Payroll Connector accepts multiple configurations. But in real time we use only one configuration
(SFTP or UCM based). For reference we have provided both the methods in the above table.

In order to handle the additional fields and additional objects a custom program
(wrapper program) is designed which will handle the importing of custom objects that
are not handled by standard import program. Ex: Payment Methods
This wrapper program will internally call the standard program Import HCM Cloud Data
File for Payroll Integration for the standard objects. For custom objects separate
custom import program (extended standard program) will be triggered.

Once the data is imported a data set would be created with the data set name provided
in the above screen shot.

2. Load the data from EBS staging tables to base tables.

In order to load the data set (data set can be a custom object or standard object), select
the respective data set and click on Load button as shown in below screenshot.

Load button triggers the standard program Load HCM cloud data. This load button can
be extended with the new load wrapper program to call both the custom objects
followed by custom objects. In H3G program H3G: UK Load HCM Cloud Data is created

as a wrapper program that triggers the standard load program. Once the standard
program completes, the successfully processed records again for supplement fields.

Once the data is loaded we can view the standard and custom objects load status as
shown in below screen shot.

The following objects are handled as part of supplement program.

Assignment Updates - Assignment Category ,Payroll ,Salary Basis, Expense Account
information, People Group
Organization and Organization Classification updates
Assignment DFF
Payment Methods
Element Entries
Person Extra Information
Assignment Extra Information
Absences

Scheduling

In order to Import and Load data for all the custom and standard objects a request set is
created and scheduled on daily basis.

Below is the order of execution for importing the standard objects. The loading of the
standard objects is done in the same order as of import.

The parameters for importing the data are defined as shown below.
Based on the UCM doc title and Object Name the file will be imported from UCM to EBS
local server and staging tables.

Standard payroll Connector creates the data set as Object Name_UCM Id. The same
method is followed for the Custom objects as well.

Custom objects are imported once the importing of standard objects is done.

Loading of standard objects is scheduled after the import is done for both standard and
custom objects.

Below screenshot depicts on how the parameters are defined for load objects.
The data set name will be obtained based on the object type and data set of the object
for which latest import has happened.

Salient Features
Features:

Supports Automation of Import and Load in EBS.

Provides feature rich monitoring framework.
Supports restartability and error recovery mechanism.
Fusion DFF fields are supported till Import stage (customer needs to write own load procedure).
Error and Monitoring framework can be extended for custom objects.

Limitations:
Currently uses RIDC based transfer utility to pull file from UCM. This may not work with
enterprise implementing Federated SSO.
No OOTB decryption support: Cannot use PGP encrypted file generated by Fusion HCM Extract.