11i HCM Coexistence

Oracle HCM Coexistence
Integrating Oracle HRMS with Oracle Fusion Talent and Workforce

Compensation
Release 11i
Part No. E20111-08
May 2013
Oracle HCM Coexistence Integrating Oracle HRMS with Oracle Fusion Talent and Workforce Compensation,
Release 11i
Part No. Not Applicable
Copyright 2011, 2013, Oracle and/or its affiliates. All rights reserved.
Primary Author: Swathi Mathur, Vinod Viswanathan, Rajshekar Ayyadevara
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of
their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are
used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron,
the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro
Devices. UNIX is a registered trademark of The Open Group.
This software and related documentation are provided under a license agreement containing restrictions on
use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your
license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license,
transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse
engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is
prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If
you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on
behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software,
any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are
"commercial computer software" pursuant to the applicable Federal Acquisition Regulation and
agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation
of the programs, including any operating system, integrated software, any programs installed on the
hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the
programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications.
It is not developed or intended for use in any inherently dangerous applications, including applications that
may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you
shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its
safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this
software or hardware in dangerous applications.
This software or hardware and documentation may provide access to or information on content, products,
and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly
disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle
Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your
access to or use of third-party content, products, or services.

Contents
Send Us Your Comments
Preface
1 HCM Coexistence
Overview................................................................................................................................... 1-1
2 Configuring Oracle EBS

Configure Oracle EBS for HCM Coexistence........................................................................... 2-1
3 Configuring Oracle Fusion

Configure Oracle Fusion for HCM Coexistence....................................................................... 3-1
4 Setting Up Data
Set up Data for HCM Coexistence............................................................................................ 4-1
5 Extracting EBS Data

Extract EBS Data for Oracle Fusion........................................................................................... 5-1
6 Importing Compensation Changes

Import Compensation Changes to EBS (Oracle Workforce Compensation Only).................. 6-1
7 Frequently Asked Questions

Frequently Asked Questions.................................................................................................... 7-2
Frequently Asked Questions................................................................................................ 7-2
iii
8 Troubleshooting
Extraction Issues........................................................................................................................ 8-1
A Appendix A
Invoking the Fusion Web Service............................................................................................ A-1
B Appendix B
Reference Java Code for Web Service Subscription................................................................ B-1
C Appendix C
Writing Formulas for Discretionary Job Title Mapping..........................................................C-1
D Appendix D
Writing Formulas for Person Number Mapping..................................................................... D-1
E Appendix E
Maintaining Parameters and Parameter Groups...................................................................... E-1
Index
iv

Send Us Your Comments
Oracle HCM Coexistence Integrating Oracle HRMS with Oracle Fusion Talent and Workforce
Compensation, Release 11i
Part No. Not Applicable
Oracle welcomes customers' comments and suggestions on the quality and usefulness of this document.
Your feedback is important, and helps us to best meet your needs as a user of our products. For example:
Are the implementation steps correct and complete?
Did you understand the context of the procedures?
Did you find any errors in the information?
Does the structure of the information help you with your tasks?
Do you need different information or graphics? If so, where, and in what format?
Are the examples correct? Do you need more examples?
If you find any errors or have any other suggestions for improvement, then please tell us your name, the
name of the company who has licensed our products, the title and part number of the documentation and
the chapter, section, and page number (if available).
Note: Before sending us your comments, you might like to check that you have the latest version of the
document and if any concerns are already addressed. To do this, access the new Oracle E-Business Suite
Release Online Documentation CD available on My Oracle Support and www.oracle.com. It contains the
most current Documentation Library plus all documents revised or released recently.
Send your comments to us using the electronic mail address: appsdoc_us@oracle.com
Please give your name, address, electronic mail address, and telephone number (optional).
If you need assistance with Oracle software, then please contact your support representative or Oracle
Support Services.
If you require training or instruction in using Oracle software, then please contact your Oracle local office
and inquire about our Oracle University offerings. A list of Oracle offices is available on our Web site at
www.oracle.com.
v

Preface
Intended Audience
Welcome to Release 11i of the Oracle HCM Coexistence Integrating Oracle HRMS with
Oracle Fusion Talent and Workforce Compensation.
This guide assumes you have a working knowledge of the following:
The principles and customary practices of your business area.
Oracle HRMS.
If you have never used Oracle HRMS, Oracle suggests you attend one or more of
the Oracle HRMS training classes available through Oracle University
Oracle Self-Service Web Applications.

To learn more about Oracle Self-Service Web Applications, read the Oracle
Self-Service Web Applications Implementation Manual.
The Oracle Applications graphical user interface.

To learn more about the Oracle Applications graphical user interface, read the
Oracle Applications User's Guide.
See Related Documents for more information about Oracle Applications product
information.
See Related Information Sources on page viii for more Oracle E-Business Suite product
information.
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle
Accessibility Program website at
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
vii
Access to Oracle Support
Oracle customers have access to electronic support through My Oracle Support. For
information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Structure
1 HCM Coexistence
2 Configuring Oracle EBS
3 Configuring Oracle Fusion
4 Setting Up Data
5 Extracting EBS Data
6 Importing Compensation Changes
7 Frequently Asked Questions
8 Troubleshooting
A Appendix A
B Appendix B
C Appendix C
D Appendix D
E Appendix E
Related Information Sources

Oracle HRMS shares business and setup information with other Oracle Applications
products. Therefore, you may want to refer to other user guides when you set up and
use Oracle HRMS.
You can read the guides online by choosing Library from the expandable menu on your
HTML help window, by reading from the Oracle Applications Document Library CD
included in your media pack, or by using a Web browser with a URL that your system
administrator provides.
If you require printed guides, you can purchase them from the Oracle store at
http://oraclestore.oracle.com.
Guides Related to All Products
Oracle Applications User's Guide
This guide explains how to enter data, query, run reports, and navigate using the
graphical user interface (GUI). This guide also includes information on setting user
profiles, as well as running and reviewing reports and concurrent processes.
You can access this user's guide online by choosing "Getting started with Oracle
Applications" from any Oracle Applications help file.
Guides Related to This Product
Oracle HR Intelligence Daily Business Intelligence for HRMS User Guide
viii
This guide describes the dashboards and reports available for HR Line Managers, Chief
HR Officer, Budget Managers, and Benefits Managers using Daily Business Intelligence
for HRMS. It includes information on using parameters, how DBI for HRMS derives
values, and how to troubleshoot dashboards and reports.
Oracle E-Business Intelligence Daily Business Intelligence Implementation Guide
This guide describes the common concepts for Daily Business Intelligence. It describes
the product architecture and provides information on the common dimensions, security
considerations, and data summarization flow. It includes a consolidated setup checklist
by page and provides detailed information on how to set up, maintain, and
troubleshoot Daily Business Intelligence pages and reports for the following functional
areas: Financials, Interaction Center, iStore, Marketing, Product Lifecycle Management,
Projects, Procurement, Sales, Service, Service Contracts, and Supply Chain.
Oracle E-Business Intelligence Daily Business Intelligence User Guide
This guide describes the common concepts for Daily Business Intelligence. It describes
the product architecture and provides information on the common dimensions, security
considerations, and data summarization flow. It includes a consolidated setup checklist
by page and provides detailed information on how to set up, maintain, and
troubleshoot Daily Business Intelligence pages and reports for the following functional
areas: Financials, Interaction Center, iStore, Marketing, Product Lifecycle Management,
Projects, Procurement, Sales, Service, Service Contracts, and Supply Chain.
OA Personalization Framework and OA Extensibility Framework
Learn about the capabilities of the 11.5.10 Framework technologies.
Oracle Human Resources Management Systems Enterprise and Workforce
Management Guide
Learn how to use Oracle HRMS to represent your enterprise. This includes setting up
your organization hierarchy, recording details about jobs and positions within your
enterprise, defining person types to represent your workforce, and also how to manage
your budgets and costs.
Oracle Human Resources Management Systems Workforce Sourcing, Deployment, and
Talent Management Guide
Learn how to use Oracle HRMS to represent your workforce. This includes recruiting
new workers, developing their careers, managing contingent workers, and reporting on
your workforce.
Oracle Human Resources Management Systems Payroll Processing Management Guide
Learn about wage attachments, taxes and social insurance, the payroll run, and other
processes.
Oracle Human Resources Management Systems Compensation and Benefits
Management Guide
Learn how to use Oracle HRMS to manage your total compensation package. For
example, read how to administer salaries and benefits, set up automated grade/step
ix
progression, and allocate salary budgets. You can also learn about setting up earnings
and deductions for payroll processing, managing leave and absences, and reporting on
compensation across your enterprise.
Oracle Human Resources Management Systems Configuring, Reporting, and System
Administration in Oracle HRMS
Learn about extending and configuring Oracle HRMS, managing security, auditing,
information access, and letter generation.
Oracle Human Resources Management Systems Implementation Guide
Learn about the setup procedures you need to carry out in order to successfully
implement Oracle HRMS in your enterprise.
Oracle Human Resources Management Systems FastFormula User Guide
Learn about the different uses of Oracle FastFormula, and understand the rules and
techniques you should employ when defining and amending formulas for use with
Oracle applications.
Oracle Self-Service Human Resources Deploy Self-Service Capability Guide
Set up and use self-service human resources (SSHR) functions for managers, HR
Professionals, and employees.
Oracle Human Resources Management Systems Deploy Strategic Reporting (HRMSi)
Implement and administer Oracle Human Resources Management Systems Intelligence
(HRMSi) in your environment.
Oracle Human Resources Management Systems Strategic Reporting (HRMSi) User
Guide
Learn about the workforce intelligence reports included in the HRMSi product,
including Daily Business Intelligence reports, Discoverer workbooks, and Performance
Management Framework reports.
Implementing Oracle Approvals Management
Use Oracle Approvals Management (AME) to define the approval rules that determine
the approval processes for Oracle applications. Download this guide from Oracle
MetaLink, Note: 282529.1.
Oracle iRecruitment Implementation and User Guide
Set up Oracle iRecruitment to manage all of your enterprise's recruitment needs.
Oracle Learning Management User Guide
Set up and use Oracle Learning Management to accomplish your online and offline
learning goals.
Oracle Learning Management Implementation Guide
Implement Oracle Learning Management to accommodate your specific business
practices.
x
Oracle Time and Labor Implementation and User Guide
Learn how to capture work patterns such as shift hours so that this information can be
used by other applications such as General Ledger.
Installation and System Administration
Oracle Applications Concepts
This guide provides an introduction to the concepts, features, technology stack,
architecture, and terminology for Oracle Applications Release 11i. It provides a useful
first book to read before an installation of Oracle Applications. This guide also
introduces the concepts behind Applications-wide features such as Business Intelligence
(BIS), languages and character sets, and Self-Service Web Applications.
Installing Oracle Applications
This guide provides instructions for managing the installation of Oracle Applications
products. In Release 11i, much of the installation process is handled using Oracle Rapid
Install, which minimizes the time to install Oracle Applications and the Oracle
technology stack by automating many of the required steps. This guide contains
instructions for using Oracle Rapid Install and lists the tasks you need to perform to
finish your installation. You should use this guide in conjunction with individual
product user guides and implementation guides.
Upgrading Oracle Applications
Refer to this guide if you are upgrading your Oracle Applications Release 10.7 or
Release 11.0 products to Release 11i. This guide describes the upgrade process and lists
database and product-specific upgrade tasks. You must be either at Release 10.7 (NCA,
SmartClient, or character mode) or Release 11.0, to upgrade to Release 11i. You cannot
upgrade to Release 11i directly from releases prior to 10.7.
"About" Document
For information about implementation and user document, instructions for applying
patches, new and changes setup steps, and descriptions of software updates, refer to the
"About" document for your product. "About" documents are available on Oracle
MetaLink for most products starting with Release 11.5.8.
Maintaining Oracle Applications
Use this guide to help you run the various AD utilities, such as AutoUpgrade,
AutoPatch, AD Administration, AD Controller, AD Relink, License Manager, and
others. It contains how-to steps, screenshots, and other information that you need to run
the AD utilities. This guide also provides information on maintaining the Oracle
applications file system and database.
Oracle Applications System Administrator's Guide
This guide provides planning and reference information for the Oracle Applications
System Administrator. It contains information on how to define security, customize
menus and online help, and manage concurrent processing.
Oracle Alert User's Guide
xi
This guide explains how to define periodic and event alerts to monitor the status of
your Oracle Applications data.
Oracle Applications Developer's Guide
This guide contains the coding standards followed by the Oracle Applications
development staff and describes the Oracle Application Object Library components that
are needed to implement the Oracle Applications user interface described in the Oracle
Applications User Interface Standards for Forms-Based Products. This manual also provides
information to help you build your custom Oracle Forms Developer forms so that the
forms integrate with Oracle Applications.
Oracle Applications User Interface Standards for Forms-Based Products
This guide contains the user interface (UI) standards followed by the Oracle
Applications development staff. It describes the UI for the Oracle Applications products
and how to apply this UI to the design of an application built by using Oracle Forms.
Other Implementation Documentation
Oracle Applications Product Update Notes
Use this guide as a reference for upgrading an installation of Oracle Applications. It
provides a history of the changes to individual Oracle Applications products between
Release 11.0 and Release 11i. It includes new features, enhancements, and changes
made to database objects, profile options, and seed data for this interval.
Oracle Workflow Administrator's Guide
This guide explains how to complete the setup steps necessary for any Oracle
Applications product that includes workflow-enabled processes, as well as how to
monitor the progress of runtime workflow processes.
Oracle Workflow Developer's Guide
This guide explains how to define new workflow business processes and customize
existing Oracle Applications-embedded workflow processes. It also describes how to
define and customize business events and event subscriptions.
Oracle Workflow User's Guide
This guide describes how Oracle Applications users can view and respond to workflow
notifications and monitor the progress of their workflow processes.
Oracle Workflow API Reference
This guide describes the APIs provided for developers and administrators to access
Oracle Workflow.
Oracle Applications Flexfields Guide
This guide provides flexfields planning, setup, and reference information for the Oracle
HRMS implementation team, as well as for users responsible for the ongoing
maintenance of Oracle Applications product data. This guide also provides information
on creating custom reports on flexfields data.
xii
Oracle eTechnical Reference Manuals
Each eTechnical Reference Manual (eTRM) contains database diagrams and a detailed
description of database tables, forms, reports, and programs for a specific Oracle
Applications product. This information helps you convert data from your existing
applications, integrate Oracle Applications data with non-Oracle applications, and write
custom reports for Oracle Applications products. Oracle eTRM is available on Oracle
Metalink.
Oracle Applications Message Manual
This manual describes all Oracle Applications messages. this manual is available in
HTML format on the documentation CD-ROM for Release 11i.
Do Not Use Database Tools to Modify Oracle E-Business Suite Data

Oracle STRONGLY RECOMMENDS that you never use SQL*Plus, Oracle Data
Browser, database triggers, or any other tool to modify Oracle E-Business Suite data
unless otherwise instructed.
Oracle provides powerful tools you can use to create, store, change, retrieve, and
maintain information in an Oracle database. But if you use Oracle tools such as
SQL*Plus to modify Oracle E-Business Suite data, you risk destroying the integrity of
your data and you lose the ability to audit changes to your data.
Because Oracle E-Business Suite tables are interrelated, any change you make using an
Oracle E-Business Suite form can update many tables at once. But when you modify
Oracle E-Business Suite data using anything other than Oracle E-Business Suite, you
may change a row in one table without making corresponding changes in related tables.
If your tables get out of synchronization with each other, you risk retrieving erroneous
information and you risk unpredictable results throughout Oracle E-Business Suite.
When you use Oracle E-Business Suite to modify your data, Oracle E-Business Suite
automatically checks that your changes are valid. Oracle E-Business Suite also keeps
track of who changes information. If you enter information into database tables using
database tools, you may store invalid information. You also lose the ability to track who
has changed your information because SQL*Plus and other database tools do not keep a
record of changes.
xiii
1
HCM Coexistence
Overview
HCM Coexistence enables you to integrate your existing Oracle Human Resource
Applications with a hosted Oracle Fusion Talent Management or Workforce
Compensation implementation. This means that you can use Oracle Fusion Workforce
Compensation and Talent Management functionality alongside your existing
E-business Suite setup.
Using HCM Coexistence, you can extract, transform, and transport files from Oracle
E-Business Suite and intelligently synchronize selected business object data between
your Oracle EBS application and Oracle Fusion HCM applications.
After this implementation, you can use Oracle Fusion Talent Management applications
for all talent related functions and Oracle Fusion Workforce Compensation for the
compensation review process but also continue to use existing EBS HCM applications
for all HR related functions.
HCM Coexistence provides the following responsibilities that you can use to perform
these tasks within the Coexistence Workbench:
HCM Coexistence Administrator to manage configurations
HCM Coexistence Manager to set up and import data
HCM Coexistence Integrator to extract and publish data
You can use these responsibilities to access various functions required for performing
the EBS HCM tasks such as:
Configure EBS HCM systems for coexistence
Identity the Business Groups to enable for HCM coexistence solution
Import Oracle Fusion cross-reference data for setup mapping
HCM Coexistence 1-1

Map EBS entities to Oracle Fusion using the WebADI spreadsheets
Extract the EBS data for importing to Oracle Fusion as a zip file
Place the extracted zip file in Oracle Fusion FTP Inbound server and invoke Oracle
Fusion Web Service
Import the compensation changes
Update the EBS system with the compensation changes
The following graphic illustrates the integration of EBS system with Oracle Fusion
Talent Management and Workforce Compensation using HCM Coexistence.
Perform the steps 1-6 if you are using HCM Coexistence for EBS - Oracle Fusion Talent
Management integration. Perform the steps 1-9 if you are using HCM Coexistence for
EBS - Oracle Fusion Workforce Compensation integration.
Oracle recommends that you perform the steps in the given sequence to ensure a
smooth and error-free integration. Perform the steps 1 - 3 consecutively to set up the
EBS and Oracle Fusion systems. If you encounter any error in any of the steps, Oracle
recommends you to troubleshoot before you proceed to the next step.
Perform the steps 4 and 5 consecutively to extract the EBS data.
1. Step 1 - Configure Oracle EBS and Oracle Fusion systems for coexistence
2. Step 2 - Import Oracle Fusion cross-reference data for setup mapping
1-2 Oracle HCM Coexistence Integrating Oracle HRMS with Oracle Fusion Talent and Workforce Compensation
Tip: You are advised to check the concurrent program log to ensure
that there are no failures during the import process.
3. Step 3- Create data maps using the WebADI spreadsheets
Tip: Oracle recommends you to check and resolve any error that
you may encounter during the upload process before you proceed
to the next step.
4. Step 4 - Extract the EBS data for importing to Oracle Fusion as a zip file
5. Step 5 - Place the extracted zip file in Oracle Fusion FTP Inbound server
6. Step 6 - Invoke the Oracle Fusion Load HCM Data for Coexistence process
7. Step 7 - Perform a compensation review
8. Step 8 - Import the compensation changes
9. Step 9 - Update the changes to EBS
This document describes each of these steps in detail in the following chapters.
Predefined Responsibilities and Tasks

HCM Coexistence provides the following responsibilities that you can use:
HCM Coexistence Administrator to manage configurations
HCM Coexistence Manager to set up and import data
HCM Coexistence Integrator to extract and publish data
HCM Coexistence Administrator

The HCM Coexistence Administrator responsibility enables you to perform the
following tasks:
Manage Configuration Function to create a new configuration.
Select Configuration to select the current configuration and to check the current
status of the configuration activities.
Setup Data Function to identify business groups to enable for coexistence, to import
cross-reference data from Fusion, to define mapping and validate the mapped
HCM Coexistence 1-3

entities.
Extract Data Function to export the mapped information and publish to Fusion.
Import Compensation changes from Fusion (Compensation Only)
HCM Coexistence Manager

The HCM Coexistence Manager responsibility enables you to perform the following
tasks:
Setup Data Function to identify business groups to enable for coexistence, to import
cross-reference data from Oracle Fusion, to define mapping and validate the
mapped entities.
Import Compensation changes from Fusion (Compensation Only).
Note: The HCM Coexistence Manager responsibility cannot access the

Manage Configuration Function.
HCM Coexistence Integrator

The HCM Coexistence Integrator responsibility enables you to perform the following
tasks:
Import Compensation changes from Fusion (Compensation Only)
Note: The HCM Coexistence Integrator responsibility cannot access the

Manage Configuration Function and Setup Data Function.
2
Configuring Oracle EBS
Configure Oracle EBS for HCM Coexistence

You must configure the EBS system before you can use HCM Coexistence for
integration between EBS and Oracle Fusion. This involves setting up a configuration
that enables you to integrate the EBS HCM data with the Oracle Fusion Talent
Management and Oracle Fusion Workforce Compensation data.
You can also specify the attributes you want to extract using the Manage Attributes for
Extraction option.
You can select a configuration using the Select Configuration option to perform the
various tasks such a setting up data, extracting and importing content.
Creating a Configuration
Using the HCM Coexistence Administrator responsibility, you can access the function
to create a configuration to set up the EBS data.
Use the Manage Configuration function to create a configuration.
The Create Configuration page enables you to enter a unique name and code for your
configuration. The various concurrent programs refer to this configuration code
internally.
You can specify whether you want to integrate either Oracle Fusion Talent Management
or Oracle Fusion Compensation or both by selecting the appropriate checkboxes in the
Integration Options field.
You can specify the service provider details to enable the application to import and
export data from EBS and Oracle Fusion. The details include:
The FTP protocol and the FTP server port
The server address and user name of the Oracle Fusion FTP server
Configuring Oracle EBS 2-1

The database vault key that holds the FTP password. You can load the password
into the vault using the following command :
sqlplus apps/apps@database @$FND_TOP/sql/afvltput.sql
HCM_COEXISTENCE <Key><Actual Password>
HCM_COEXISTENCE is the password module used for HCM Coexistence

<Key> - a user defined key, for example - FUSION_FTP_PASSWORD
<ActualPassword> - the actual password
The Outbound folder in Oracle Fusion FTP server to host the Oracle Fusion
cross-reference data
The file name of the Oracle Fusion cross-reference data file
The Inbound folder in Oracle Fusion server to which the e-Business Suite data is
exported
The local folder where data is staged before exporting
The Web Service FTP folder on the Fusion server from which the exported data is
loaded into the Fusion application using the Fusion Ready To Load web service
The table illustrates the parameters required for configuration:
Attributes Required Description
Configuration Details
Configuration Name Yes Name for the configuration
Configuration Code Yes Configuration short code

referred internally.
Configuration Description No A description for your

configuration
Active/Inactive Flag Yes
Integration Options Section Specify whether the current

configuration supports both
talent integration and
compensation integration or
either of them
Configuration Parameters
FTP Protocol Yes The FTP protocol to use

(FTP/SFTP)
FTP Server Port Yes The port of the Fusion FTP

server
FTP Server Address Yes The address of the FTP Server
FTP Server Username Yes The user name of the FTP

Server
FTP Server Password Key Yes The database vault key used
to store the FTP password
Outbound Folder Yes The folder in Fusion FTP

server that hosts the Fusion
cross reference data
Outbound File Name Yes The file name of the Fusion

cross reference data file
Local Staging Folder No The folder on eBusiness Suite

server used as a staging area
for exporting data. If you do
not specify any folder, then
APPLTMP folder will be used
as the staging area.
APPLTMP - This is the

directory for Oracle
E-Business Suite temporary
files.
Note: For more

information on APPLTMP,
see Environment Settings
in the Oracle E-Business
Suite File System in the
Oracle E-Business Suite
Concepts Guide.

Inbound Folder Yes The folder in Fusion server to

which the eBusiness Suite
data is exported
Web Service FTP Folder Yes The folder on the Fusion

server from which the
exported data is loaded into
the Fusion application using
the Fusion Ready To Load
web service
You can also edit, search, and delete your configurations using the Manage
Configuration function. You can also review any recent changes to your configurations.
Configuring EBS to Invoke Fusion Web Service

HCM Coexistence uses web services to communicate the availability of zip files for
import between EBS and Fusion and vice-versa.
To configure the web service, see: Appendix A - Invoking the Fusion Web Service
Managing Attributes for Extraction

Using the HCM Coexistence Administrator responsibility, you can access the function
to manage attributes for a configuration to set up the EBS data.
In the Manage Attributes for Extraction option, you can specify the attributes you want
restrict from being extracted in the extract file during the extraction process.
Select Yes or No in the Extract column for the particular attribute.
Managing a Configuration
After you have created a configuration, you can select it using the Select Configuration
option to perform the various tasks such a setting up data, extracting, and importing
content.
Selecting Configuration
Using the Select Configuration option, you can view the configuration details of the
selected configuration. You can also choose to view the activities being performed on
the configuration or any requests. You also have the option to remove any previously
created extracts.
View Recent Activities
This option enables you to view a log of the various actions performed on a selected
configuration such as configuration parameter update, import data from Fusion,
entity extraction, and extract to file.
View My Requests
- You can view the status of all your requests whether pending, running, or
completed using the View My Requests option for all the actions performed on a
selected configuration.
Purge Extracts - During an ongoing implementation of Fusion Coexistence, the

application generates a number of extract files. You can remove these previously
created unwanted extracts using the Purge Extracts option.
When you select the Purge Extract option, the application runs the Fusion
Coexistence Purge Extracts process on the selected configuration to delete these
extract files from the staging folder.
Specify the following parameters when you run the Fusion Coexistence Purge
Extracts process: .
Configuration Select a configuration which you want to purge.
Extract If you want to remove a particular extract, select from the list of values
under the selected configuration.
Older than - Optionally, you can specify to delete all the extracts created prior
to the specified number of days.

3
Configuring Oracle Fusion
Configure Oracle Fusion for HCM Coexistence

Configuring the Oracle Fusion system involves the following steps:
1. Step 1- Defining business objects in Oracle Fusion
2. Step 2 - Extracting cross-reference data
You must manually set up a few entities in Oracle Fusion prior to running the
integration and then generate a cross-reference file for EBS. You perform these steps
within Oracle Fusion applications. Ensure to have the Oracle Fusion system running
with the appropriate roles to perform this task.
See: Oracle Fusion Applications Coexistence for HCM Implementation Guide for setting
up the business objects.
Defining Business Objects in Oracle Fusion

Use the Oracle Fusion interface to manually define the business objects prior to
integration with the EBS data. Which business objects you need to define depends on
the Oracle Fusion functions you intend to use. You can define business objects such as
legal entities, legislative data groups, elements, and content types.
See: Oracle Fusion Applications Coexistence for HCM Implementation Guide for more
information.
Extracting cross-reference data

After you have configured the business objects in Oracle Fusion, you can generate a
cross reference data file and extract this information for mapping with the EBS system
so that data is synchronized as it is exchanged between EBS and Oracle Fusion.
To generate the cross-reference data, you run the Oracle Fusion process Generate
Mapping File for HCM Business Objects.
Configuring Oracle Fusion 3-1

This process creates .dat files containing Global Unique Identifiers (GUIDs) for each
business object. These files are packaged in a zipped data file that is written to the FTP
Inbound server.
4
Setting Up Data
Set up Data for HCM Coexistence

HCM Coexistence provides the HCM Coexistence Manager responsibility that enables
you to import the cross-reference data from Fusion to EBS for mapping and validation
processes. You can perform the following tasks using this responsibility:
1. Identify business groups to enable for coexistence
2. Import data from Fusion
3. Define mapping between the EBS and Oracle Fusion entities
4. Process and validate the mapped entities
HCM Coexistence provides WebADI spreadsheets that enable you to perform each of
these mapping tasks.
The following section outlines the steps that you can perform on the Setup functions
Identify Business groups to enable for Coexistence

HCM Coexistence provides a WebADI spreadsheet that enables you to select business
groups that you want to enable for coexistence.
Use the Identify Business Groups for Integration function to invoke a spreadsheet to
select a business group from the list of values. Select Yes in the Coexistence column if
you want to enable the business group for coexistence.
Import Cross-reference Data from Oracle Fusion

After you have identified and selected the business groups for integration, you can
import the cross-reference data onto EBS.
The Import Setup function enables you to import this cross-reference data file after the
Setting Up Data 4-1

cross reference data has been generated and placed as a zip file on the Fusion Outbound
FTP server.
Use the Import Setup function to import the cross-reference file to EBS specific staging
tables. You can select the configuration to which cross-reference data is imported.
Data Mapping between EBS and Oracle Fusion entities

The EBS entities that are migrated need to be mapped with entities manually defined in
Oracle Fusion such as enterprise, sets, and legal entities. The Setup: Mapping function
enables you to perform this mapping.
Use the Setup: Mapping functions using the EBS Coexistence Manager responsibility to
perform the following tasks.
Map business group defaults
Map HR organizations to legal employers in Oracle Fusion
Map GRE/Legal Entity to legal employers in Oracle Fusion
Map key flexfields (for job, position, grade, and competency)
Map user defined lookups
Map person types to Oracle Fusion person types
Map EBS assignment status to Oracle Fusion assignment status
Map action reasons
Use the Setup: Mapping : Talent function using the HCM Coexistence Manager
responsibility to perform the following task:
Map Qualification Type Categories to Content Type in Fusion (For Oracle Fusion
Talent Management only)
Use the Setup: Mapping : Compensation function using the HCM Coexistence Manager
responsibility to perform the following task:
Map Elements (For Oracle Fusion Compensation Workforce only)
If you are using Workforce Compensation for integration, you must also map the
salary component codes. Use the Map Action Reasons to map the salary component
codes.
HCM Coexistence provides WebADI spreadsheets to enable you to perform mapping.

You can restrict the mapping to a particular business group by selecting it on the Define
Mapping page or selecting all business groups. Select each task to download a
spreadsheet to perform the mappings.
Important: Certain fields are pre-populated and you cannot add new
rows. You can update the existing data.
Map Business Group Defaults

Use the Map Business Group Default function to invoke the spreadsheet to specify
values for certain EBS entities such as set name, legal employer, and business unit
name.
You must define a business unit for each business group. As a part of this mapping, you
provide the name of the business unit to create in Fusion for the selected business group
in EBS and a default set for the business unit. For every business group that you are
integrating, you must define a set and a business unit.
You also have the option to define an eligibility profile to filter the data (by person
based on the criteria defined) and associate it to the business group. This is optional.
The business group mapping requires 1-to-1 relationship from business group (BG) to
set ID and business group to business unit. The set provided in the mapping will be
used as the default set for the business unit that will be created for the business group.
Column Name Required Description
Business Group Yes Business Groups enabled for

Integration. This field is
pre-populated.
Legislation Name Yes Legislation name for the

selected business group. This
field is pre-populated.
Enterprise Yes Name of the Enterprise to

which the data will be
integrated. This field is
pre-populated.
Default Set Yes The name of the Set to which

business group specific data
will be created such as
Location, Job, Position
Default Legal Employer Yes The name of the default legal

employer for those employees
without an HR organization
Setting Up Data 4-3

Default Business Unit Name Yes Name of the Business Unit to

be created for the Business
Group
Default Business Unit Set Yes Reference Set to be used for

the Business Unit
Legislative Data Group (For No The Legislative Data Group is

Workforce Compensation an optional field for Oracle
only) Fusion Talent only integration
and mandatory for Oracle
Fusion Workforce
Compensation integration.
Eligibility Profile No This is an optional field.

Define an eligibility profile to
filter the data (by person
based on the criteria defined
in the profile) and associate
with a business group.
Person information being

extracted into the ZIP file will
be based on these eligibility
criteria. The criteria is ONLY
used to filter Person and its
dependent data and NOT the
work structure entities such
as job, position, grade,
department
Employer Identifier No The segment in Soft Coded

KeyFlexfield that holds the
GRE/Legal Entity
information. This field is
pre-populated for the seeded
legislations.
Unique Identifier No This field is user-enterable.

Use this field to add a prefix
or suffix to the internal codes
to make them unique. For
example assignment number,
department name.
Org Mapping ID No Used for internal mapping

purposes only. Do not modify
or update this field.
After you have identified the business groups for integration and have completed the
Import Setup task, the spreadsheet gets pre-populated with the business group
information that you have selected. Additionally a new row gets populated with a
value of Default for which you need map a Default Set. Global entities such as Global
Locations are mapped to this set in Fusion. It is not necessary to specify the remaining
columns in the spreadsheet for this Default row.
Map HR Organizations to Fusion Legal Employers
HR Organization to Legal Employer mapping is an optional step.
You use the HR Organization to Fusion Legal Employer mapping if you want to
employ employees from different HR Organizations to a specific Fusion Legal
Employer.
As part of the Provide Business Group Defaults mapping in the earlier step, you
provide a default Fusion Legal Employer for each business group. When you do not
specify any HR Organization to Fusion Legal Employer mapping, then all employees in
the selected business group will be employed under the default Fusion Legal Employer
as specified in the Map Business Group Defaults spreadsheet for the business group.
You cannot map legal employers from multiple business groups to a single Fusion
Legal Employer. For each business group defined in EBS, you must define and map
atleast one legal employer in Fusion.
Column Name Description
Business Group Business Groups enabled for Integration. This

HR Organization HR Organizations in EBS for the selected

business group
Legal Employer The name of the Legal Employer to which

employment is created for those employees
with the specified HR Org in EBS.
Setting Up Data 4-5

Legislation Data Group The name of the Legislative Data Group for
the legal employer selected previously. This is
an optional field for Talent integration and
mandatory for Compensation integration.
Org Mapping Id Used for internal mapping purposes only. Do

not modify or update this field.
Map GRE/Legal Entity to Fusion Legal Employer

GRE/Legal Entity to Fusion Legal Employer mapping is an optional step.
You use the GRE/Legal Entity to Fusion Legal Employer mapping if you want to
employ employees from GRE/Legal Entity to a specific Fusion legal employer.
As part of the Provide Business Group Defaults mapping in the earlier step, you
provide a default Fusion Legal Employer for each business group.
When you do not specify any GRE/Legal Entity to Fusion Legal Employer mapping,
then HR Organization mapping is used to derive the Fusion legal employers for the
employees.
If you do not specify both GRE/Legal Entity and HR Organization mapping, then all
employees in the selected business group will be employed under the default Fusion
Legal Employer as specified in the Map Business Group Defaults spreadsheet for the
business group.

GRE/Legal Entity GRE/Legal Entity in EBS for the selected

business group. This field is pre-populated.
Legal Employer Select the name of the legal employer to which

employment is to be created for those
employees with the specified GRE/Legal
Entity in EBS.
Legislative Data Group The name of the Legislative Data Group for
the legal employer selected previously. This is
an optional field for Talent integration and
mandatory for Compensation integration.
Map Key Flexfield
For job, position, grade, and competency definitions defined using the flexfield
structure in EBS, map them to Fusion equivalents. You can do the mapping by
identifying the segment or a combination of segments to the entity code (for example
Job code) and entity name (for example Job Name) for each of the entities. Use the Map
Key Flexfield function to download a spreadsheet to map the segments for each of these
flexfields.

Mapping Type Includes the following mapping types:
Job Code for Job Code mapping
Job Name for Job Name mapping
Position Code for Position Code mapping
Position Name for Position Name mapping
Grade Code for Grade Code mapping
Grade Name for Grade Name mapping
Competency Name for Competency Name

mapping
EBS Structure The existing flexfield structure in the current

business group.
Expression Provide an expression to extract the entity

values from the existing flexfield structure.
For example : SEGMENT1 (if the entity value
is based on a single segment) SEGMENT1 ||
SEGMENT3 (if entity value is based on a
combination of segments)
Entity Mapping Id Used for internal mapping purposes only. Do

Note: While providing the Expression for Job Code mapping ensure
that Job code does not exceed more than 25 characters.
Map User Defined Lookups
Setting Up Data 4-7

If you have any user-defined lookups created in EBS, then you must define these
lookups in Fusion. You can then map the list of lookup type and lookup codes to the
lookup types and codes for the entities transferred to Fusion. The Map User Defined
Lookup function enables you to perform this task.
Map Id Used for internal mapping purpose only. Do

EBS Lookup Type Consists of list of lookup type that exist in EBS
for the entities that are transferred to Fusion.
EBS Lookup Code Consists of list of user defined lookup codes

that exist in EBS for the entities that are
transferred to Fusion
Seeded This is a read-only Yes/No field that indicates

whether the entity is seeded. You cannot
update the Seeded mappings.
Fusion Lookup Type Consists of the lookup type that corresponds

to the EBS lookup type
Fusion Lookup Code User to provide fusion lookup code for the
user defined ones in EBS.
Map Id Used for internal mapping purpose only. Do

Note: You must map all the user defined lookup codes for type
NATIONALITY to its corresponding Fusion Lookup code to ensure
successful upload of Person data to Oracle Fusion.
Map Person Types

If you have created any other person types other than the predefined ones in EBS, you
must ensure to create them in Oracle Fusion and then map the each of these person
types accurately. Use the Map Person types function to define this mapping.

EBS Person Type EBS Person Type names to be auto-populated

based on the business group selected
Fusion Person Type Fusion person Type names to be listed in this

LOV. User maps and EBS person type to a
Fusion person type.

Map Action Reasons

You must map the leaving reasons (for Talent configuration) and salary components
(for Compensation configuration) defined in EBS to an appropriate action and action
reason in Fusion. Use the Map Action Reasons function to invoke the spreadsheet to
perform this mapping:
Entity Contains the pre-populated Entity Type such

as Employee Leaving Reason for leaving
reason and Salary Component Code for salary
components.
EBS Code Contains the pre-populated EBS Code for the

Entity Type
EBS Meaning User displayed value for the EBS code
Fusion Action Fusion Actions LOV
Fusion Action Reason Actions Reasons for the selected Actions

Map Assignment Status Types

If you have created any user-defined Assignment Status Types other than the
Setting Up Data 4-9

predefined ones, you must ensure to create them in Fusion and then map the correct
Assignment Status Types. Use the Map Assignment Status Types function to define this
mapping.
Column Description
Business Group/Legislation Displays the business group or legislation

name for the specified EBS assignment status
type. This field is pre-populated.

EBS Assignment Status Type EBS Assignment Status Type names

pre-populated based on the business groups
selected
HR Status Human Resource system status of the

specified Assignment Status type. This is
pre-populated.
Payroll Status Payroll system status of the specified

Assignment Status type. This is
pre-populated.
Fusion Assignment Status Type Fusion Assignment Status type LOV. User
maps an EBS assignment status type to a
Fusion assignment status type.

Map Qualification Type Categories (Talent only)

If you have any user defined qualification types, then you must map the Qualification
Type Category in EBS to an existing Content Type in Oracle Fusion. Use the Map
Qualification Type Category task on the Setup : Mapping Talent function to download a
spreadsheet and perform this mapping:

Qualification Type Category Consists of the list of Qualification Type

Category that exist in EBS

Content Type List of content types defined in Fusion. User

maps an EBS Qualification type Category to a
Content Type in Fusion .

Map Elements (Workforce Compensation only):

You must map the EBS elements and input values to their equivalent counterparts in
Oracle Fusion if you plan to use Workforce Compensation as part of coexistence. Use
the Map Elements task on the Setup: Mapping: Compensation function to map the
elements using the spreadsheet.
EBS Element Name EBS Compensation Element Name
EBS Element Input Value Name Input Values for the Element selected
Fusion Element Name Fusion Compensation Element Name
Fusion Element Input Value Name Input Values for the Fusion Element selected
Entity Mapping Id Used for internal mapping purpose only. Do

You can add rows in the Map: Elements spreadsheet to add the elements and then map
each of these EBS to the Oracle Fusion elements.
Process and Validate Mapping

When you have completed mapping the EBS and Oracle Fusion entities, the next task
involves validating the mapped information. The Process and Validate task enables you
Setting Up Data 4-11

to validate the uniqueness of the mapped information and identify invalid codes, if any.
The Setup : Process and Validate Mapping function consists of the following sub-tasks:
Process and Validate Mappings
Review Mapping
Process and Validate Mapping

The Process and Validation process reads the mapped entities information and
validates the uniqueness of the codes. You can select the configuration name and the
business group to validate.
Note: Ensure that the Job code value does not exceed more than 25
characters.
The validation process identifies duplicate objects based on the mapped information
and flags these values by setting Yes in the Duplicate column in the spreadsheet.
Review Mapping
After you have completed the validation process, you can review and correct the
invalid codes or invalid name identified by the validation process.
You can use the Review Mapping task to view the duplicate objects and correct them, if
required. You can correct these duplicate entities either manually or using the Define
Mapping > Map Flexfields option.
To correct the duplicate values manually, select the entity in the Default entity
column, edit it, and set the Duplicate column to No.
To correct the duplicate values using the Define Mapping option:

1. Clear the Derived Value cells in the Review Mapping spreadsheet for which
you want the expression to be recomputed.
2. Select the Define Mapping > Map Flexfields option to change the expression.
Repeat the Process and Validate task until there are no duplicates
If you want to edit any flexfield expressions after you have run the Process and Validate
task, then you must Clear the Derived Value cells (set the cell value as blank) in the
Review Mapping spreadsheet for which you want the expression to be recomputed.
After making your changes to the mapping expression, you also need to run the Process
and Validate task to recompute the values.
5
Extracting EBS Data
Extract EBS Data for Oracle Fusion

After you have completed the mapping and validation process, you can extract the data
from EBS to load into Oracle Fusion for maintenance or further processing.
Before you begin your extraction, ensure that there are no duplicate codes as identified
in the Review Mapping task.
HCM Coexistence provides the HCM Coexistence Integrator Responsibility that enables
you to access the coexistence workbench to export the mapped information and publish
into Oracle Fusion.
You can perform the following sub-functions:
Run Extraction Process
Generate Extract File
Publish to Oracle Fusion System
The following tables list the entities that you can extract:
Entity
Work Structures Location, Department, BusinessUnit, Job,

Position, Grade, GradeRate
Person and Assignment Person, PersonDocumentation,

WorkRelationship
Profile (Initial Load Only) Profile, Profile Item, Profile Relation
Extracting EBS Data 5-1

Entity
Talent Setup (Initial Load Only) Rating Model, Establishment, ContentItem
Compensation Setup Salary Basis
Compensation Salary, ElementEntry
Running the Extraction Process

You run the Extraction Process to make the necessary transformations to EBS data and
populate the staging tables in EBS for various business objects.
1. Select the configuration name to extract.
2. You can select the entities from the list of values:

All
Work Structures
Department Trees
Talent Setup
Compensation Setup
Person and Assignment
Profile
Compensation
Person, Assignment and Compensation
3. Select the Action Parameter Group.

Action parameters enable you to set number of parallel processes that need to be
spawned for the Extraction process.
For information regarding the Action Parameter Group, refer to the Appendix
section.
4. Select the Extraction Mode as Initial Load or Incremental Load.

You use Initial Load when you are extracting for the first time and use Incremental
Load for subsequent extractions.
Generating Extract File into a Zip file

The Generate Extract File task enables you to extract the EBS data into a zip file for each
of the transformed entities that can be exported to Oracle Fusion.
Select the configuration name.
Select the objects to extract from the following list of values:
All
Work Structures
Department Trees
Talent Setup
Compensation Setup
Person and Assignment
Profile
Compensation
Person, Assignment and Compensation
You can choose to publish to the Oracle Fusion system by selecting Yes in the Publish
option.
Publishing to Fusion System

Run the Publishing to Fusion System process to upload the zip file to Fusion inbound
FTP server location. This invokes the Fusion web service that informs the users that a
zip file has been placed in the FTP folder for importing to Fusion systems.
To configure the web service, see: Appendix A - Invoking the Fusion Web Service.
Loading EBS Data to Fusion

You can load the data to Fusion from the Data Exchange Work Area by running the
Load HCM Data for Coexistence process.
See : Oracle Fusion Applications Coexistence for HCM Implementation Guide for more
information on the steps for loading the zip file data to Oracle Fusion.
Extracting EBS Data 5-3

Using the Fusion Coexistence Extraction Request Set
HCM Coexistence also provides the Fusion Coexistence Extraction Request Set that
enables you to schedule the extraction process to export the extracted data and publish
to Oracle Fusion. When you run the request set, the application performs the following
sub-functions:
Run Extraction Process
Generate Extract File
Publish to Oracle Fusion System
Prior to running the request set, ensure to add the request set to the appropriate request
group assigned to your responsibility.
You run the Fusion Coexistence Extraction Request Set from the Submit Request Set
window.
To run the Fusion Coexistence Extraction Request Set:
1. Select Request Set from the Submit a New Request window.
2. Select Fusion Coexistence Extraction Request Set.
3. Click in the Parameters field to open the Parameters window.
4. Select your configuration.
5. Select the appropriate entity you want to extract and publish.
6. Click OK and Submit.
6
Importing Compensation Changes
Import Compensation Changes to EBS (Oracle Workforce Compensation

Only)
If you are integrating EBS data with the Oracle Fusion Workforce Compensation, after
you have completed the compensation review process within your enterprise, run the
Extract HCM Data for Coexistence from the Oracle Fusion Data Exchange work area.
This process generates the zip file and invokes an EBS web service to intimate that the
back feed changes have been placed on Oracle Fusion Outbound FTP Server location.
You can perform the following sub-tasks:
1. Import Compensation changes
2. Post Compensation changes
Import Compensation Changes

You can invoke the back feed import task using the Coexistence Integrator
responsibility: Import > Import Compensation changes. This process reads the zip file,
stages the zip file in EBS temporary folder, extracts, and loads the back feed staging
tables.
Post Compensation Changes
The Post Compensation Changes process posts any compensation and assignment
changes to EBS.
You must enter the following details:
Configuration ID
Run ID
Effective Date
Importing Compensation Changes 6-1

Commit or Rollback Mode
Audit Log Enabled or Not
Debug Level
7
Frequently Asked Questions
Frequently Asked Questions 7-1

Do I move history for all the entities?

Yes. History information for all the entities identified for integration (Work structures,
Employment, Compensation Setup, Compensation) is moved across to Fusion.
Is there any mechanism to send across a subset of people during initial testing or as a
part of phased rollout?
Yes. You can define an eligibility profile to filter the person and associate it with a
Business Group.
Please refer to Provide Business Group Defaults section in Data Mapping between EBS
and Oracle Fusion entities.
Can I map multiple elements in Element/Input Value mapping sheet?

Yes. With the Element/Input Value Mapping spreadsheet in EBS, you can map any
number of EBS elements and their input values to Fusion elements and input values.
When the compensation changes are imported from Fusion to EBS, Fusion
Compensation process returns only those element entries that have been modified as a
part of the Fusion compensation review process. Only these element entries will be
updated in the EBS system.
Can I update the expression for entity code or entity name for job, position, grade, and
competency already mapped using Map Key Flexfield spreadsheet?
Yes. You can update the expression for the entity code or entity name or job, position,
grade, and competency already mapped using Map Key Flexfield spreadsheet. To
update the values already defined in the Define Mapping option, perform the following
steps:
1. Clear the Derived Value cells in the Review Mapping spreadsheet for which you
want the expression to be recomputed.
2. Select the Define Mapping > Map Flexfields option to change the expression.
3. Run the Process and Validate task .
4. Run the Review Mapping task to review the invalid codes/name identified by the
validation process.
Can I map Discretionary Job Title in EBS to an Oracle Fusion attribute?

Yes. You can map Discretionary Job Title in EBS to an Oracle Fusion attribute. HCM
Coexistence provides you with a mechanism to map Discretionary Job Title or Business
Title held in EBS to Assignment Name field in Oracle Fusion by writing a custom
fastformula.
See: Appendix C Writing Formulas for Discretionary Job Title Mapping.
Can I map custom value in EBS to an Oracle Fusion attribute?

HCM Coexistence provides you with a mechanism to map a custom value to Person
Number field in Oracle Fusion so that it can be used to query the person in Fusion
search pages and also used for any end-user reports.
See: Appendix D - Writing Formulas for Person Number Mapping
Can I restrict attributes from being extracted in the extract file?

Yes. You can restrict attributes from being extracted in the extract file. Use Manage
Attributes for Extraction option to configure the attributes to be restricted.
See: Managing Attributes for Extraction in the Configuring EBS topic.
Can I purge previously created extracts?

Yes. You can purge the previously created extracts.
See: Purge Extracts in the Configuring Oracle EBS topic.
Can I create multiple configurations?

Yes. You can create multiple configurations.
Can I move the data from multiple configurations from EBS to a single enterprise in
Oracle Fusion?
No. You cannot move the data from multiple configurations to a single enterprise in
Oracle Fusion.
Is there any request set that I can use to schedule the extraction and publishing of
extracted data to Oracle Fusion?
Yes. Oracle Coexistence provides the Fusion Coexistence Extraction Request Set that
you can run to schedule the extraction and publishing of extracted data to Oracle

Fusion.
See: Extracting EBS Data for more information.
Can I extract Department Trees from EBS?

In E-Business Suite, organization hierarchies are used to show reporting lines and other
hierarchical relationships between the organizations in an enterprise. Besides
constructing hierarchies to reflect reporting lines, you can also use hierarchies to control
access to information.
There are two types of organization hierarchies in EBS:
Organization Hierarchy Hierarchy of organizations from a single Business Group
Global Organization Hierarchy - Hierarchy of organizations from multiple Business

Groups
These organization hierarchies can be modified to reflect any simple changes in the
reporting lines. A new version of an existing hierarchy can be created and it's structure
can be modified.
As a part of EBS HCM to Fusion Talent and Compensation Coexistence solution, HR
Organizations in EBS are migrated as Departments in Fusion.
Department Trees in Fusion are used to build hierarchical representations of the
departments within an organization. The top node of the tree is a department, and all
the child nodes are also departments.
EBS does not have a concept of Department Trees. EBS has Organization hierarchies or
trees where each of the tree node represents an Organization (of any classification). You
can select any type of organization for the top node and for the child nodes.
From a migration perspective, the Extraction Process follows the rule given below to
identify a Department tree from the existing Organization Hierarchies in EBS :
An organization hierarchy in which EVERY organization/node is classified as a HR
Organization ONLY is considered for data extraction as Department Tree.
Any organization hierarchy that has an organization that is NOT classified as HR Org is
not considered for data extraction.
How can the EBS Coexistence Extraction process extract and create Work Relationships
in Fusion when there is a change in Legal Employer in EBS?
In Fusion, a WorkRelationship (WR) can only have one Legal Employer (LE) associated
with it. The Work Terms (WT) and Work Assignments (A) for the WorkRelationship
must have the same Legal Employer.
If there is a change in Legal Employer (LE1 to LE2) in the EBS system, then two Work
Relationships (WRs) must be created in Fusion - WorkRelationship 1 (WR1) for Legal
Employer (LE1) and WorkRelationship 2 (WR2) for Legal Employer 2 (LE2).
Follow the steps given below to ensure that the EBS Coexistence Extraction process
extracts the data accurately and creates WorkRelationships in Fusion appropriately
when there is a change in Legal Employer.
1. Create a new assignment and associate with the new Legal Employer (LE2). You
can use this assignment as the primary assignment going forward.
2. Terminate the assignment associated with Legal Employer 1 (LE1). Set the
Assignment Status accordingly.
Creating a new assignment ensures that the existing WorkRelationship (WR1) is either
terminated or kept active, based on the assignment status specified, and a new
WorkRelationship (WR2) is created in Fusion for the new Legal Employer (LE2).
Please note that there are no changes to the Performance documents and Goals defined
for assignment associated with Legal Employer (LE1) and WorkRelationships (WR1),
even after the creation of a new WorkRelationships (WR2), WorkTerms (WT2) , and
assignment in Fusion for the new Legal Employer (LE2).
You must follow the above process to ensure that the EBS Coexistence Extraction
process extracts the data accurately and creates WorkRelationships in Fusion
appropriately when there is a change in Legal Employer.

8
Troubleshooting
Extraction Issues
If the extraction process - Fusion Coexistence Entity Extraction process ends in an error
or you observe a discrepancy from your expected data, then you must perform the
following steps to identify and resolve the issues.
1. Check for Error or Exception messages in the log files for the following processes:
Fusion Coexistence Entity Extraction
Fusion Coexistence Prepare Employment
All the Payroll Worker Processes
The error or exception messages are displayed within the following section in the
log files
+-----------------------------------------------------------------+
Start of log messages from FND_FILE
+-----------------------------------------------------------------+
+-----------------------------------------------------------------+
End of log messages from FND_FILE
+-----------------------------------------------------------------+
Sample log with error message for illustrative purposes only.

+-----------------------------------------------------------------+
Start of log messages from FND_FILE
+-----------------------------------------------------------------+
Error : The extraction failed for Person ID [5452 - 8029] at
export_all_assignments_m_2 with the following error
ORA-00001: unique constraint (HR.PER_RI_I_PER_ASSIGNMENTS_M_PK)
violated
+-----------------------------------------------------------------+
End of log messages from FND_FILE
+-----------------------------------------------------------------+
The error in the above example indicates that the extraction process failed for one or
more persons in the person id range [5452 - 8029]. The extraction process skips all
Troubleshooting 8-1
the persons within the person id range from 5452 to 8029.
2. Verify the person and assignment data for these persons for data integrity issues.
Extraction failures can happen due to data integrity issues such as:
Person has multiple primary assignments for a given period
Start dates and End Dates overlap
Start date is later than the End date
Multiple records exist in person type usages for a specific system person type
You can use the following queries to identify the data integrity issues.
SELECT * FROM per_all_people_f WHERE person_id IN (<person id>)
ORDER BY effective_start_date
SELECT * FROM per_all_assignments_f WHERE person_id IN (<person id>)
ORDER BY effective_start_date
SELECT * FROM per_person_type_usages_f WHERE person_id IN (<person
id>) ORDER BY effective_start_date
SELECT * FROM per_periods_of_placement WHERE person_id IN (<person
id>)
SELECT * FROM per_periods_of_service WHERE person_id IN (<person
id>)
The following table illustrates the possible errors and their causes:
Common Data Integrity Errors
Error Cause
APP-PAY-06881: Error ORA-01436: Start date is later than the End date.
CONNECT BY loop in user data
APP-PAY-06881: Error ORA-00001: unique Person has multiple primary assignments

constraint (HR.PER_RI_I_XXXXXXX_PK) for a given period.
violated
Multiple records exist in Person Type
Usages for a specific system person type
with overlapping Start date and End date.
Start date and End Date overlap.
3. Resolve the data extraction issues by correcting the data and re-run the extraction
process.
A
Appendix A
Invoking the Fusion Web Service

HCM Coexistence uses web services to communicate the availability of extracted zip
files from EBS for Fusion to consume and also to communicate the availability of the
compensation backfeed file in Fusion for EBS to consume.
Invoking a web service to publish to Oracle Fusion FTP Server

When you run the Publish to Oracle Fusion after posting the zip to Fusion InBound FTP
Server, it invokes a Business Event in EBS with the name
oracle.apps.per.ri.coexistence.service.ReadyToLoad<Configuration_code>. You must
create a subscription for this event to invoke the Oracle Fusion web service in EBS. You
must also create an error subscription for this event to invoke the error notifications.
Creating a Subscription for Invoking a Web Service

1. Login into EBS application as System Administrator.
2. Navigate to Workflow Administrator Web Applications responsibility. Select the

Administrator Workflow > Business Events function.
3. On the Business Events > Events tab, select your configuration. Search for the
Fusion Coexistence event
oracle.apps.per.ri.coexistence.service.ReadyToLoad.<Configuration_Code>
Note: Configuration code is recorded as a part of the Configuration

definition. See: Configuring Oracle EBS for HCM Coexistence, page
2-1.
4. In the Results: Events table Click on Subscription for the
Appendix A A-1
oracle.apps.per.ri.coexistence.service.ReadyToLoad.<Configuration_Code> event
5. Click Create Subscription.
6. In the Create Event Subscription step, select the Action Type as Custom and click
Next.
7. Specify the Java Rule function as a Java class name<Package><class>. A sample

reference Java implementation of web service invocation is provided in Appendix
B.
8. Specify the subscription parameters. The Fusion web service uses the Username
Token based WS-Security headers. Specify the Fusion Application username /
password to the subscription as subscription parameters. The Fusion application
user password should be stored in EBS database vault. The password can be loaded
into the vault using the following command :
sqlplus apps/apps@database @$FND_TOP/sql/afvltput.sql
.<Module><Key><Value>
9. In the Subscription Parameters step region, add the following parameters and click
Apply to save the subscription.
This table lists the values that you must enter:
Parameter Name Description
HCM_COEX_R2L_ENDPOINT_URL Specify the web service endpoint URL to the

Fusion InboundLoader Process web service
HCM_COEX_R2L_USERNAME Fusion application username
HCM_COEX_R2L_PASSWORD_MOD The module value used in the previous step

to store the Fusion application password
HCM_COEX_R2L_PASSWORD_KEY The key value used in the previous step to

store the Fusion application password
10. In the Documentation region, enter the following parameters :
Owner Name as Human Resources
Owner Tag as PER
A-2 Oracle HCM Coexistence Integrating Oracle HRMS with Oracle Fusion Talent and Workforce Compensation
Creating an Error Subscription
1. Login into EBS application as System Administrator.
2. Navigate to Workflow Administrator Web Applications responsibility. Select the

Administrator Workflow > Business Events function.
3. On the Business Events > Events tab, select your configuration. Search for the
Fusion Coexistence event
oracle.apps.per.ri.coexistence.service.ReadyToLoad.<Configuration_Code>
See: Configuring Oracle EBS for HCM Coexistence
4. In the Results: Events table Click on Subscription for the

oracle.apps.per.ri.coexistence.service.ReadyToLoad.<Configuration_Code>event.
5. Click Create Subscription.
6. In the Create Event Subscription step, provide the following details:.

System name
Source Type Error
Event Filter - Event name
Phase - 90
Status - Enabled
Rule Data - Key
Action Type - Launch Workflow from the list of values
On Error - Stop and Roll Back
7. Click Next and enter the remaining values:

Workflow Type WFERROR from the list of values
Workflow Process DEFAULT_EVENT_ERROR
Owner Name - Human Resources
Owner Tag - PER
8. Click Apply.
Appendix A A-3
If any error occurs while executing the subscription, the above error subscription sends
a notification to SYSADMIN alongwith the error details. Please review the SYSADMIN
notifications for any errors.
A-4 Oracle HCM Coexistence Integrating Oracle HRMS with Oracle Fusion Talent and Workforce Compensation
B
Appendix B
Reference Java Code for Web Service Subscription

You can use the following reference code to call web service. Customize this code to suit
your requirement.
Appendix B B-1
package custom.coexistence.subscription;
import java.io.IOException;
import java.io.InputStream;
import java.io.InputStreamReader;
import java.io.OutputStream;
import java.io.OutputStreamWriter;
import java.io.Reader;
import java.io.Writer;
import java.io.BufferedReader;
import java.io.PrintWriter;
import java.io.StringReader;
import java.io.StringWriter;
import java.net.HttpURLConnection;
import java.net.MalformedURLException;
import java.net.URL;
import java.sql.Connection;
import oracle.apps.fnd.common.Log;
import oracle.apps.fnd.wf.bes.BusinessEvent;
import oracle.apps.fnd.wf.bes.BusinessEventException;
import oracle.apps.fnd.wf.bes.SubscriptionInterface;
import oracle.apps.fnd.wf.bes.server.Subscription;
import oracle.apps.fnd.wf.common.WorkflowContext;
import oracle.apps.per.ri.integration.common.CommonException;
import oracle.apps.per.ri.integration.common.Vault;
public class ReadyToLoadSubscription implements SubscriptionInterface {
public static final String PARAM_ENDPOINT_URL =

"HCM_COEX_R2L_ENDPOINT_URL";
public static final String PARAM_USERNAME = "HCM_COEX_R2L_USERNAME";
public static final String PARAM_PASSWORD_MOD =

"HCM_COEX_R2L_PASSWORD_MOD";
public static final String PARAM_PASSWORD_KEY =

"HCM_COEX_R2L_PASSWORD_KEY";
public ReadyToLoadSubscription() {
}
public void onBusinessEvent(Subscription eo, BusinessEvent event,
WorkflowContext context)
throws BusinessEventException {
Log log = context.getLog();
try {
log.write(this, "Entered ReadyToLoadSubscription ...",Log.ERROR);

log.write(this, "Subscription version:" + eo.RCS_ID,Log.ERROR);
log.write(this, "All Params:" + eo.getParameters(),Log.ERROR);
log.write(this, "Fetching Parameter:" + PARAM_ENDPOINT_URL,
Log.ERROR);
String endPointURLString = eo.getParameterByName(PARAM_ENDPOINT_URL);

log.write(this, "Parameter Value:" + endPointURLString,Log.ERROR);
URL endPointURL = new URL(endPointURLString);
Connection jdbcConnection = context.getJDBCConnection();
log.write(this, "Fetching Parameter:" + PARAM_USERNAME,Log.ERROR);
String username = eo.getParameterByName(PARAM_USERNAME);
B-2 Oracle HCM Coexistence Integrating Oracle HRMS with Oracle Fusion Talent and Workforce Compensation
log.write(this, "Parameter Value:" + username, Log.ERROR);
String passMod = eo.getParameterByName(PARAM_PASSWORD_MOD);
String passKey = eo.getParameterByName(PARAM_PASSWORD_KEY);
String password = Vault.retreiveInformation(jdbcConnection, passMod,
passKey);
log.write(this, "The payload is -" + username, Log.ERROR);
String payload = event.getData();
log.write(this, payload, Log.ERROR);
String message = prepareSOAPMessage(payload, username,password);
log.write(this, "SOAP Message -", Log.ERROR);
log.write(this, message, Log.ERROR);
log.write(this, "Opening HTTP Connection ...", Log.ERROR);
HttpURLConnection connection =
(HttpURLConnection)endPointURL.openConnection();
connection.setRequestMethod("POST");
connection.addRequestProperty("Accept","text/xml, text/html," +
"image/gif, image/jpeg, *; q=.2, */*; q=.2");
connection.addRequestProperty("Content-Type",
"text/xml; charset=utf-8");
connection.addRequestProperty("Content-Length",
String.valueOf(message.length()));
connection.addRequestProperty("SOAPAction", "process");
connection.setDoOutput(true);
connection.setDoInput(true);
connection.setUseCaches(false);
connection.setAllowUserInteraction(false);
OutputStream out = connection.getOutputStream();
log.write(this, "Writing to HTTP Stream ...", Log.ERROR);
Writer writer = new OutputStreamWriter(out, "UTF-8");
writer.write(message);
writer.close();
out.close();
log.write(this, "Write Complete.", Log.ERROR);
log.write(this, "Reading Response ...", Log.ERROR);
InputStream in = connection.getInputStream();
Reader reader = new InputStreamReader(in);
StringBuffer response = new StringBuffer();
char[] chrs = new char[4096];
while (true) {
int size = reader.read(chrs);
if (size == -1)
break;
response.append(chrs, 0, size);
}
reader.close();
in.close();
log.write(this, "Read Complete.", Log.ERROR);
if(response.length() > 0) {
String responseText = response.toString();
if(responseText.indexOf("fault") >= 0) {
log.write(this, "Web Service Returned Error Response - ",
Log.ERROR);
log.write(this, responseText, Log.ERROR);
connection.disconnect();
throw new BusinessEventException ("Web Service failed " +
"with message - " + responseText);
}
}
log.write(this, "Exit ReadyToLoadSubscription - SUCCESS",
Log.ERROR);
connection.disconnect();
Appendix B B-3
} catch (MalformedURLException e) {
log.write(this, "MalformedURLException - " + e.getMessage(),
Log.ERROR);
printErrorStackToLog (log, e);
throw new BusinessEventException("Error creating endpoint URL - ",
e);
} catch (CommonException e) {
log.write(this, "CommonException - " + e.getMessage(),
Log.ERROR);
throw new BusinessEventException("Error retreiving information " +
"from DB vault",e);
} catch (IOException e) {
log.write(this, "IOException:" + e.getMessage(), Log.ERROR);
throw new BusinessEventException("Error calling web service", e);
}
}
private String prepareSOAPMessage(String payload, String username,
String password) {
return "<soap:Envelope xmlns:" +
"soap=\"http://schemas.xmlsoap.org/soap/envelope/\">\n" +
" <soap:Header>\n" +
" <wsse:Security soap:mustUnderstand=\"1\" " +
"xmlns:wsse=\"http://docs.oasis-open.org/wss/2004/01/oasis" +
"-200401-wss-wssecurity-secext-1.0.xsd\">\n" +
" <wsse:UsernameToken>\n" +
" <wsse:Username>" + username +
"</wsse:Username>\n" +
" <wsse:Password " +
"Type=\"http://docs.oasis-open.org/wss/2004/01/oasis-" +
"200401-wss-username-token-profile-1.0#PasswordText\">" +
password + "</wsse:Password>\n" +
" </wsse:UsernameToken>\n" +
" </wsse:Security>\n" + " </soap:Header>\n" +
" <soap:Body " +
"xmlns:ns1=\"http://xmlns.oracle.com/apps/hcm/common/" +
"batchLoader/inboundLoaderProcess\">\n" +
payload + " </soap:Body>\n" + "</soap:Envelope>";
}
private void printErrorStackToLog (Log log, Throwable t) {
final StringWriter sw = new StringWriter();
final PrintWriter pw = new PrintWriter(sw);
t.printStackTrace(pw);
StringBuffer buf = sw.getBuffer();
StringReader sr = new StringReader(buf.toString());
BufferedReader br = new BufferedReader(sr);
try {
while(true) {
String line = br.readLine();
if(line == null)
break;
log.write(this, line, Log.ERROR);
}
} catch(IOException ex) {
;
}
}
}
B-4 Oracle HCM Coexistence Integrating Oracle HRMS with Oracle Fusion Talent and Workforce Compensation
C
Appendix C
Writing Formulas for Discretionary Job Title Mapping

HCM Coexistence provides you with a mechanism to map Discretionary Job Title or
Business Title held in EBS to Assignment Name field in Oracle Fusion so that it can be
used in performance reviews and any end-user reports.
EBS HCM application users hold the Discretionary Job Title or Business Title for an
assignment as a part of custom DFF available in assignment entity or as a customized
implementation in EBS.
To map this custom title to the Assignment Name field, you can write a custom formula
with the name HCM_COEX_ASG_CUSTOM_MAP and the formula type as QuickPaint
for specific business groups. The formula logic needs to derive the required
Discretionary Job Title from the EBS source and return the value as an output
parameter. Once you have defined and validated the formula, the HCM Coexistence
Data Extraction process executes the formula and populates the Assignment Name field
with the value returned as output parameter to the formula.
Formula Name and Parameters
Name :
HCM_COEX_ASG_CUSTOM_MAP
Important: You must define the formula for each of the business group
and the formula must have the name
HCM_COEX_ASG_CUSTOM_MAP. The formula has no effect if you
do not use the specified name and the specified list of input and output
parameters.
Input Parameters:
Assignment_ID
Appendix C C-1
Effective_Start_Date
Effective_End_Date
Output Parameters:
Assignment_Name
Sample Formula
/* -------------------------------------------------------------------
NAME : HCM_COEX_ASG_CUSTOM_MAP
This formula provides user an option to map Discretionary Job Title
to Assignment Name.
------------------------------------------------------------------*/
INPUTS ARE ASSIGNMENT_ID
,EFFECTIVE_START_DATE (DATE)
,EFFECTIVE_END_DATE (DATE)
/* -------------------------------------------------------------------
Provide the logic to derive the value for Discretionary Job Title or
Business Title from EBS DFF or custom fields using a database items
or formula functions
-----------------------------------------------------------------*/
ASSIGNMENT_NAME = ''
RETURN ASSIGNMENT_NAME
For information on writing formulas, see : Oracle Human Resources Management

Systems FastFormula User Guide
C-2 Oracle HCM Coexistence Integrating Oracle HRMS with Oracle Fusion Talent and Workforce Compensation
D
Appendix D
Writing Formulas for Person Number Mapping

HCM Coexistence provides you with a mechanism to map a custom value to Person
Number field in Oracle Fusion such that you can query the person on the Oracle Fusion
search pages and for any end-user reports.
To map the custom value to the Person Number field, you can write a custom formula
with the name HCM_COEX_PER_CUSTOM_MAP and the formula type as QuickPaint
for specific business groups. The formula logic needs to derive the required custom
value from the EBS source and return the value as an output parameter. Once you have
defined and validated the formula, the HCM Coexistence Data Extraction process
executes the formula and populates the Person Name field with the value returned as
output parameter to the formula.
If you do not provide a formula, then by default the person id from the EBS source will
be populated to Person Number field in Fusion.
Formula Name and Parameters:
HCM_COEX_PER_CUSTOM_MAP
Important: You must define the formula for each of the business group
and the formula must have the name
HCM_COEX_PER_CUSTOM_MAP. The formula has no effect if you
do not use the specified name and the specified list of input and output
parameters.
Input Parameters:
PERSON_ID
Output Parameters:
PERSON_NUMBER
Appendix D D-1
Sample Formula:
/* -------------------------------------------------------------------
NAME : HCM_COEX_PER_CUSTOM_MAP
This formula provides user an option to map custom value for
Person Number in Fusion.
------------------------------------------------------------------*/
INPUTS ARE PERSON_ID
/* -------------------------------------------------------------------
Provide the logic to derive the value for Person Number using
database items or formula functions.
The output variable PERSON_NUMBER should be of character datatype.
e.g. PERSON_NUMBER = to_char(PERSON_ID)
-----------------------------------------------------------------*/
PERSON_NUMBER = ' '
RETURN PERSON_NUMBER
For information on writing formulas, see : Oracle Human Resources Management

Systems FastFormula User Guide
D-2 Oracle HCM Coexistence Integrating Oracle HRMS with Oracle Fusion Talent and Workforce Compensation
E
Appendix E
Maintaining Parameters and Parameter Groups

Action parameters enable you to set number of parallel processes that need to be
spawned for the Extraction process. Use the Action Parameters window to define your
parameter values and create parameter groups. You can create a default group to
specify global values, or you can define your own group to provide a customized set of
processing conditions.
Important: If you create your own group, select it in the Action

Parameter Group field.
To maintain parameter groups:

Do one of the following:
To define or maintain the default group, check the default group check box. Only
do this if you want the parameter values that you select to be the default for all
processes and business groups.
To create your own parameter group, enter the name of the group.
Note: You cannot enable a named parameter group as the default

group.
To maintain process parameters:

1. From the Parameters tab, select the name of the parameter that you want to modify,
or enter a parameter name.
For details of the parameters that you can enter, see the Technical Essay: Payroll
Appendix E E-1
Action Parameters, Oracle HRMS Implementation Guide.
2. If you do not specify any values for the parameters that you select, then the values
held at the global level default to the group level. But, if values are specified at the
group level, then the group level values take precedence over the global parameter
values.
To maintain logging parameters:

1. Select the Logging tab.
2. Check each of the logging categories that you want to enable.
3. Uncheck any logging categories that you want to disable.
4. Save your changes.
E-2 Oracle HCM Coexistence Integrating Oracle HRMS with Oracle Fusion Talent and Workforce Compensation

Index
C S
compensation changes, 6-1 Setting up data, 4-1
configure EBS system, 2-1
configure Fusion, 3-1
Configuring Oracle EBS, 2-1
Configuring Oracle Fusion, 3-1
cross reference data import, 4-1
D
Defining Business Objects, 3-1
E
extracting, 5-1
Extracting cross-reference data, 3-1
Extracting EBS Data, 5-1
Extraction Process, 5-1
H
HCM Coexistence, 1-1
HCM Coexistence Administrator, 2-1
I
Importing, 6-1
Importing compensation changes, 6-1
Importing Cross-reference data, 4-1
importing data, 4-1
Integration, 1-1
M
Manage Configuration, 2-1
Index-1

11i HCM Coexistence

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

11i HCM Coexistence

Uploaded by

Copyright:

Available Formats

Oracle HCM Coexistence

Integrating Oracle HRMS with Oracle Fusion Talent and Workforce

Part No. Not Applicable

Primary Author: Swathi Mathur, Vinod Viswanathan, Rajshekar Ayyadevara

Send Us Your Comments

2 Configuring Oracle EBS

3 Configuring Oracle Fusion

5 Extracting EBS Data

6 Importing Compensation Changes

7 Frequently Asked Questions

Oracle Self-Service Web Applications.

The Oracle Applications graphical user interface.

Related Information Sources

Do Not Use Database Tools to Modify Oracle E-Business Suite Data

HCM Coexistence Manager to set up and import data

HCM Coexistence Integrator to extract and publish data

Identity the Business Groups to enable for HCM coexistence solution

Import Oracle Fusion cross-reference data for setup mapping

HCM Coexistence 1-1

Import the compensation changes

Update the EBS system with the compensation changes

2. Step 2 - Import Oracle Fusion cross-reference data for setup mapping

3. Step 3- Create data maps using the WebADI spreadsheets

7. Step 7 - Perform a compensation review

8. Step 8 - Import the compensation changes

9. Step 9 - Update the changes to EBS

Predefined Responsibilities and Tasks

HCM Coexistence Manager to set up and import data

HCM Coexistence Integrator to extract and publish data

HCM Coexistence Administrator

HCM Coexistence 1-3

Import Compensation changes from Fusion (Compensation Only)

HCM Coexistence Manager

Import Compensation changes from Fusion (Compensation Only).

Note: The HCM Coexistence Manager responsibility cannot access the

HCM Coexistence Integrator

Import Compensation changes from Fusion (Compensation Only)

Note: The HCM Coexistence Integrator responsibility cannot access the

Configure Oracle EBS for HCM Coexistence

Configuring Oracle EBS 2-1

HCM_COEXISTENCE is the password module used for HCM Coexistence

The file name of the Oracle Fusion cross-reference data file

The local folder where data is staged before exporting

The table illustrates the parameters required for configuration:

Attributes Required Description

Configuration Name Yes Name for the configuration

Configuration Code Yes Configuration short code

Configuration Description No A description for your

Active/Inactive Flag Yes

Integration Options Section Specify whether the current

FTP Protocol Yes The FTP protocol to use

FTP Server Port Yes The port of the Fusion FTP

FTP Server Address Yes The address of the FTP Server

FTP Server Username Yes The user name of the FTP

Outbound Folder Yes The folder in Fusion FTP

Outbound File Name Yes The file name of the Fusion

Local Staging Folder No The folder on eBusiness Suite

APPLTMP - This is the

Note: For more

Configuring Oracle EBS 2-3

Inbound Folder Yes The folder in Fusion server to

Web Service FTP Folder Yes The folder on the Fusion

Configuring EBS to Invoke Fusion Web Service

Managing Attributes for Extraction