21 import data

Partner Boot Camp – Fusion HCM Global HR Import Data Instructor Guide

July 25, 2013

Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Disclaimer This document contains proprietary information and is protected by copyright and other intellectual property laws. You may copy and print this document solely for your own use in an Oracle training course. The document may not be modified or altered in any way. Except where your use constitutes "fair use" under copyright law, you may not use, share, download, upload, copy, print, display, perform, reproduce, publish, license, post, transmit, or distribute this document in whole or in part without the express authorization of Oracle. The information contained in this document is subject to change without notice. If you find any problems in the document, please report them in writing to: Oracle University, 500 Oracle Parkway, Redwood Shores, California 94065 USA. This document is not warranted to be error-free. Restricted Rights Notice If this documentation is delivered to the United States Government or anyone using the documentation on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS The U.S. Government’s rights to use, modify, reproduce, release, perform, display, or disclose these training materials are restricted by the terms of the applicable Oracle license agreement and/or the applicable U.S. Government contract. Trademark Notice Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

i

CONTENTS Lesson 1: Import Data ................................................................ 1

Lesson Objectives ...................................................................................... 1 Lesson Agenda ........................................................................................... 2 Importing Data: Introduction ....................................................................... 3 HCM File-Based Loader ............................................................................... 5

Lesson Agenda ........................................................................................ 5 HCM File-Based Loader: Overview .............................................................. 6 HCM File-Based Loader: Process Summary .................................................. 7 HCM File-Based Loader: Supported Objects ................................................. 9 HCM File-Based Loader: Supported Functionality ........................................ 10 Configuring the Load Batch Data Process .................................................. 12 Instructor Note: Activity 1 Timing ............................................................ 14 Activity 1 Introduction: Configuring the Load Batch Data Process ................. 15

Activity 1: Configuring the Load Batch Data Process ................................. 16 Configuring SFTP ................................................................................... 17 Instructor Note: Configuring SFTP Access ................................................. 18 Oracle Fusion Setup ............................................................................... 19 Generating the Mapping File .................................................................... 20 Instructor Note: Activity 2 Timing ............................................................ 22 Activity 2 Introduction: Generating the Mapping File .................................. 23

Instructor Note: Generating the Mapping File .......................................... 24 Activity 2: Generating the Mapping File .................................................. 25

Importing the Mapping File to the Source Environment ............................... 27 Key Mapping ......................................................................................... 28 Mapping Source Data to the Oracle Fusion Model ....................................... 30 Extracting the Source Data...................................................................... 31 HCM File-Based Loader: Structure of the Import File .................................. 32 Data-File Contents ................................................................................. 35 Data-File Contents: Examples .................................................................. 36 Instructor Note: Copying the Data File to the SFTP Server .......................... 37 HCM File-Based Loader: Importing Data to the Stage Tables ....................... 38 HCM File-Based Loader: The InboundLoaderProcess ................................... 40 Instructor Note: Activity 3 Timing ............................................................ 42 Activity 3 Introduction: Running the InboundLoaderProcess Web Service ...... 43

Activity 3: Running the InboundLoaderProcess Web Service ...................... 44 HCM File-Based Loader: Running the Import Process and Reviewing the Log File ........................................................................................................... 46 Instructor Note: Activity 4 Timing ............................................................ 47 Activity 4 Introduction: Running the Import Process and Reviewing the Log File48

Activity 4: Running the Import Process and Reviewing the Log File ............ 49 HCM File-Based Loader: Loading Data to the Application Tables ................... 51 Instructor Note: Activity 5 Timing ............................................................ 53 Activity 5 Introduction: Loading Data to the Application Tables .................... 54

Activity 5: Loading Data to the Application Tables .................................... 55 HCM File-Based Loader: Reviewing Load Batch Data Results ........................ 56 HCM File-Based Loader: Correcting Load Errors ......................................... 58 Validating Data Loaded Using HCM File-Based Loader ................................. 60 Instructor Note: Activity 6 Timing ............................................................ 61 Activity 6 Introduction: Validating the Loaded Data .................................... 62

Activity 6: Validating Loaded Data ......................................................... 63 Instructor Note: Activity 7 Timing ............................................................ 65 Activity 7 Introduction: Updating Loaded Data ........................................... 66

Activity 7: Updating Loaded Data ........................................................... 67 Instructor Note: Activity 8 Timing ............................................................ 70

ii

Activity 8 Introduction: Correcting Load Errors .......................................... 71 Activity 8: Correcting Load Errors .......................................................... 72

Instructor Note: Activity 9 Timing ............................................................ 74 Activity 9 Introduction: Validating Updated Data ........................................ 75

Activity 9: Validating Updated Data ........................................................ 76 Using Oracle WebCenter Content ............................................................. 77 HCM File-Based Loader: Best Practices ..................................................... 78

HCM Spreadsheet Data Loader ................................................................... 80 Lesson Agenda ...................................................................................... 80 HCM Spreadsheet Data Loader: Overview ................................................. 81 HCM Spreadsheet Data Loader: Process Summary ..................................... 83 HCM Spreadsheet Data Loader: Supported Objects .................................... 85 HCM Spreadsheet Data Loader: Supported Functionality ............................. 86 Finding Detailed Information About HCM Spreadsheet Data Loader Spreadsheets ........................................................................................................... 87 Instructor Note: Finding Detailed Information About Spreadsheets ............... 88 Generating the Spreadsheet .................................................................... 89 Instructor Note: Preparing for the HCM Spreadsheet Data Loader Demonstrations ........................................................................................................... 91 Instructor Note: Demo Timing ................................................................. 92 Demonstration: Generating the Spreadsheet ............................................. 93 Completing the Spreadsheet .................................................................... 95 Instructor Note: Demo Timing ................................................................. 96 Demonstration: Entering Data in the Generated Spreadsheet ...................... 97 HCM Spreadsheet Data Loader: Importing Data to the Stage Tables and Correcting Import Errors ........................................................................................ 99 Instructor Note: Demo Timing ................................................................ 100 Demonstration: Importing Data to the Stage Tables and Correcting Import Errors .......................................................................................................... 101 HCM Spreadsheet Data Loader: Loading Data to the Application Tables ....... 103 Instructor Note: Demo Timing ................................................................ 104 Demonstration: Loading Data to the Application Tables ............................. 105 HCM Spreadsheet Data Loader: Correcting Load Errors .............................. 106 Instructor Note: Demo Timing ................................................................ 108 Demonstration: Correcting Load Errors .................................................... 109 Instructor Note: Demo Timing ................................................................ 112 Demonstration: Validating Data Loaded Using HCM Spreadsheet Data Loader113 HCM Spreadsheet Data Loader: Best Practices .......................................... 115 Future Enhancements ............................................................................ 116 HCM File-Based Loader and HCM Spreadsheet Data Loader: Post-Load Processes .......................................................................................................... 117 HCM File-Based Loader and HCM Spreadsheet Data Loader: Use Cases ........ 119

Specialized Data Loaders .......................................................................... 121 Lesson Agenda ..................................................................................... 121 Payroll Batch Loader .............................................................................. 122 Compensation and Benefits Data Loaders ................................................. 123 Talent Data Loaders .............................................................................. 124 Core HR Data Loaders ........................................................................... 125

Future Plans for Data Loading ................................................................... 126 Lesson Agenda ..................................................................................... 126 HCM Data Loader .................................................................................. 127 Inbound Web Services ........................................................................... 129

Import Data Review Questions .................................................................. 130 Review Question 1 ................................................................................ 130 Review Question 2 ................................................................................ 131 Review Question 3 ................................................................................ 132 Instructor Note: Import Data Review Questions ........................................ 133

Lesson Highlights .................................................................................... 134

Lesson 1: Import Data

Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 1


Lesson Objectives After completing this lesson, you should be able to:

• Understand the ways in which Oracle Fusion Human Capital Management (HCM) supports data import

• Load data using HCM File-Based Loader • Load Data using HCM Spreadsheet Data Loader • Select the appropriate data-import mechanism for your purposes, based on

your coexistence strategies, integration approaches, and data-migration plans

• Understand how data-import approaches are being developed in future releases of Oracle Fusion HCM


2 Copyright © 2013, Oracle and/or its affiliates. All rights reserved.

Lesson Agenda

• Importing Data Introduction • HCM File-Based Loader • HCM Spreadsheet Data Loader • Specialized Data Loaders • Future Plans for Data Loading



Importing Data: Introduction However you implement Oracle Fusion HCM, data import is a necessary activity. You may be:

• Migrating your existing data completely to Oracle Fusion HCM before retiring a legacy product. This scenario typically requires a one-time data upload.

• Loading data from a third-party supplier. • Implementing a coexistence scenario, where Oracle Fusion HCM is being used

with another HR product. For example, you may want to use Talent Management in Oracle Fusion HCM but maintain person records elsewhere. Such scenarios require repeated data uploads to Oracle Fusion HCM.

In addition, your source data may originate in multiple systems.

Oracle Fusion HCM provides import solutions for loading:

• Initial enterprise structures, such as legal entities • Setup data, such as jobs, departments, and benefit plans • Transactional data, such as employee records • Transaction history, such as salary changes and performance reviews

You can load initial enterprise structures using the Enterprise Structures Configurator, which was covered earlier in this class. This lesson focuses on two key data loaders:



• HCM File-Based Loader • HCM Spreadsheet Data Loader

The lesson also introduces some specialized data loaders, such as the Payroll Batch Loader. HCM Spreadsheet Data Loader, HCM File-Based Loader, and the specialized data loaders together support the loading of setup data, transactional data, and transaction history.



HCM File-Based Loader

Lesson Agenda




HCM File-Based Loader: Overview HCM File-Based Loader enables you to load data in bulk from any source to Oracle Fusion HCM. It is a tool for populating the Load Batch Data stage tables with your data and preparing it for processing by Oracle Fusion object services. Benefits of HCM File-Based Loader include:

• Ability to load data from any source and from multiple sources to Oracle Fusion HCM

• Support for key Oracle Fusion HCM business objects • Use of the standard Load Batch Data process (also used by HCM Spreadsheet

Data Loader), which provides error handling and is multithreaded • Ability to both create and update business objects • Ability to upload partial object hierarchies for most supported business objects • Support for date-effective objects and the ability to upload object history

HCM File-Based Loader is most suitable for:

• Loading complex, hierarchical data • Loading large volumes of records • Repeated uploads, as may be required in a coexistence scenario or when source

data is being maintained for other reasons • Building integrations tailored to individual needs

HCM File-Based Loader can be used in all circumstances. However, for simple, one-time-only loading of small or medium data volumes, you may prefer HCM Spreadsheet Data Loader to HCM File-Based Loader for its speed and ease of use. Note: You are recommended not to mix use of HCM Spreadsheet Data Loader with use of HCM File-Based Loader for related data. Use HCM Spreadsheet Data Loader only if you can use it to load all of your data.



HCM File-Based Loader: Process Summary The process of extracting data from its source environment and uploading it using HCM File-Based Loader is summarized in the following figure:

1. In Oracle Fusion HCM, you define any Oracle Fusion business objects that are referenced by your source data and extract cross-reference information for those business objects. The cross-reference information is written automatically to the SFTP server.

2. You import the cross-reference information to your source environment and map it to your own data.

3. You map your data to the Oracle Fusion business-object model, extract your data, and deliver it to the Oracle Fusion SFTP server.

4. HCM File-Based Loader imports your source data to the Load Batch Data stage tables and resolves primary and foreign-key references in the data.

5. Load Batch Data loads your source data from the stage tables to the Oracle Fusion application tables.

Once all data is successfully loaded, you can validate it in the Oracle Fusion interfaces. For example, if you load persons, then you can search for them in the Person Gallery.



Note: From Oracle Fusion HCM 11g Release 7 (11.1.7), Oracle WebCenter Content can be used in place of SFTP for file transfers. This lesson uses SFTP in any examples. Use of WebCenter Content is covered briefly at the end of this section on HCM File-Based Loader. In the next few topics, we discuss supported objects and functionality before examining the process in more detail.



HCM File-Based Loader: Supported Objects Using HCM File-Based Loader, you can load the following Oracle Fusion HCM 11g Release 7 (11.1.7) business objects:

1. Actions and action reasons 2. Locations 3. Business units 4. Grades 5. Grade rates 6. Job families 7. Jobs 8. Salary bases 9. Educational establishments 10. Rating models 11. Talent profile content items 12. Talent profile content item relationships 13. Persons (employees, contingent workers, nonworkers, and pending workers) 14. Person contacts 15. Person documentation (citizenship, passports, and visas only) 16. Departments 17. Positions 18. Work relationships and assignments 19. Salaries 20. Element entries

Objects are listed here in the recommended initial load order, which respects dependencies between objects.



HCM File-Based Loader: Supported Functionality Using HCM File-Based Loader, you can create any of the supported objects. You can also update objects that you created using HCM File-Based Loader. However, you cannot delete objects, nor can you upload attachments. Updating Objects

• In most cases, you do not need to upload the entire object when you update it. You can upload just the relevant entities and attributes of the object. For example, if a person's address changes, then you can upload just the new address. You do not need to upload the person's e-mail, ethnicity, religion, phones, and so on. The exception to this general rule is work relationships. You must upload all entities of the work relationship when updating.

• Within an entity or object, you can omit optional attributes and you can change the order of the columns.

• If you change an attribute that appears in all entities of an object (for example, the logical start date of a work relationship), then you must remember to change it in all entities of the object.

Date-Effective Objects

• When updating a date-effective object, you do not need to upload the complete object history. You can upload a partial history (for example, changed attribute values with effective start and end dates). The changes are applied automatically to the relevant physical records of the logical object.

• You can specify a new logical start date or logical end date for an object. For date-effective objects, two additional columns exist in the data (.dat) file, LSD (Logical Start Date) and LED (Logical End Date). Setting either of these columns to Y indicates that a new value is specified.

• You cannot specify a logical end date for a primary object (such as a primary assignment) unless you make it nonprimary first.

Setting Attributes to NULL You can set non-NULL attributes to NULL using an appropriate directive value. If the attribute is a:

• VARCHAR2 or NUMBER value, then you set it to #NULL • DATE value, then you set it to 31-Dec-0001 (or date-format equivalent)

Flexfields You cannot load flexfield data using File-Based Loader. However, an alternative solution is provided for loading descriptive flexfields. Briefly, you:



• Configure and deploy your flexfields using the Manage Flexfields task. • Enter your flexfield data in a supplied data (.dat) file and save it in .csv format. • Open a service request to have the flexfield data loaded from the .csv file to your

environment.

This solution is available for the following 5 tables:

• PER_JOBS_F • PER_JOBS_LEG_F • PER_PERSONS • PER_ALL_ASSIGNMENTS_M • HR_ALL_ORGANIZATION_UNITS_F

More information is provided in the Migration section of the HCM Data Conversion Reference Library (https://beehiveonline.oracle.com/teamcollab/wiki/HCM_Data_Conversion_Reference_Library_Workspace:Release+5+Coexistence+Libray).

https://beehiveonline.oracle.com/teamcollab/wiki/HCM_Data_Conversion_Reference_Library_Workspace:Release+5+Coexistence+Libray�




Configuring the Load Batch Data Process The Load Batch Data process loads data from its stage tables to the Oracle Fusion application tables. How the Load Batch Data process operates in your environment is determined by parameters, which you set by performing the task Manage HCM Configuration for Coexistence. Default values for these parameters are shown in the following figure:

Setup and Maintenance > Manage HCM Configuration for Coexistence Several of these parameters are not directly relevant to HCM File-Based Loader, and in most cases you can use the default setting. Note the following exceptions:

• On Demand FTP Root Directory. Set this parameter to /u01/oracle/ODI_FILE_ROOT_HCM/ftp_inbox.

• Loader Number of Processes. Increment the value of this parameter, which is 1 by default, to 4 or 8. If you leave this parameter at its default setting, then the



Load Batch Data process does not run multithreaded. When you are loading large volumes of data, the performance impact can be severe.

• Use Python Loader. Set this value to Y.

If you leave Loader Maximum Errors set to 100, then the load process stops after 100 errors occur. Depending on data volumes, you may want to increase this value. You can find more information about each of these parameters in the HCM File-Based Loader User's Guide on My Oracle Support (1533860.1 (https://support.oracle.com/epmos/faces/DocumentDisplay?id=1533860.1)).

https://support.oracle.com/epmos/faces/DocumentDisplay?id=1533860.1�



Instructor Note: Activity 1 Timing

The course was designed for you to facilitate learners doing the specified activity at this point. Approximate Activity Timing: 10 minutes . Note: The activity should be performed once only in any environment. If students are sharing an environment, then select one student to perform the activity.



Activity 1 Introduction: Configuring the Load Batch Data Process Background As an implementation consultant, you use HCM File-Based Loader to bulk-load business objects to Oracle Fusion HCM. Requirements

• You must have access to Oracle Fusion Applications InFusion database (or comparable training or test instance at your site) on which to complete this practice.

Activity Scope Open the Manage HCM Configuration for Coexistence page and set parameters that affect the operation of HCM File-Based Loader. The parameters are:

• On Demand FTP Root Directory • Loader Number of Processes • Use Python Loader

Perform this activity once only in any environment.



Activity 1: Configuring the Load Batch Data Process In this activity, you set the parameters that control the Load Batch Data process. Sign in as user HCM_IMPL or another implementation user, such as HCM_IMPL1. In environments that are accessed by multiple students, only one student needs to perform this task. Start Here Setup and Maintenance work area, All Tasks tab

1. Enter Manage HCM Configuration for Coexistence in the Name field of the Search section.

2. Click Search. 3. In the Search Results section, click Go to Task. The Manage HCM

Configuration for Coexistence page opens. 4. In the Parameters section of the Manage HCM Configuration for Coexistence

page, click Detach to display all parameters at once. 5. In the On Demand FTP Root Directory field, enter

/u01/oracle/ODI_FILE_ROOT_HCM/ftp_inbox. 6. In the Loader Number of Processes field, enter 8 to replace the default value,

which is 1. 7. In the Use Python Loader field, enter Y to replace the default value, which is N.

You can leave other configuration parameters to use the default settings. 8. Click Detach to restore the parameters table to its default size. 9. Click Submit. 10. In the Confirmation message window, click OK.

.



Configuring SFTP SFTP credentials (the host name, port, user, and password) are provided to you by your CoE representative or PDIT (Product Development IT) team member. You have different credentials for your stage and production environments. Configure your SFTP session using these credentials (using an SFTP client such as WinSCP). Once the session is configured, you create the ftp_inbox folder in path /upload/E_1.



Instructor Note: Configuring SFTP Access No student activity is provided for this step because the way in which it works in the course is not typical. Instead, the files the students will upload to each environment will be staged on the SFTP server in directory /home/oracle/E_1/fapnnnn/ftp_inbox before the lesson. Details for accessing the SFTP server (using WinSCP, for example) are as follows:

• File Protocol: SFTP • Host Name: adcsamba.oracleads.com • Port: 22 • User: oracle • Password: welcome

Although the files are already on the SFTP server, they will also be provided in the course Beehive workspace in case they need to be loaded again or the students want to store the files locally for later study.



Oracle Fusion Setup Business objects that originate in your source environments may reference other business objects that originate in Oracle Fusion HCM. For these referenced business objects, you need to generate cross-reference information and include it in your source systems. The business objects that you need to have defined in your target Oracle Fusion HCM environment before generating the cross-reference information are:



Generating the Mapping File Having defined referenced business objects in Oracle Fusion HCM, you can generate the mapping file of cross-reference information for those business objects. The cross-reference information comprises GUIDs (Globally Unique Identifiers) for the business objects. To generate the file, you submit the Generate Mapping File for HCM Business Objects process on the Manage HCM Configuration for Coexistence page:

Setup and Maintenance > Manage HCM Configuration for Coexistence A process status value of 12 means that the process was successful. A process status value of 10 means that errors occurred. In this case, search for the process in the Scheduled Processes work area (Navigator > Tools > Scheduled Processes) and view the associated log file. The Generate Mapping File for HCM Business Objects process creates one or more data files (.dat files) for each business object. The .dat files are packaged automatically in a zipped data file that is written to directory /upload /E_1 on the SFTP server. The file is also written to the Oracle WebCenter Content account hcm/dataloader/export. The following individual .dat files are generated:



Notes:

1. The GUID values associated with an Oracle Fusion instance do not change. However, GUIDs vary among instances. Therefore, the GUIDs that you generate from the stage environment are different from those generated from the production environment.

2. Remember to regenerate these files whenever you make changes to any of the relevant Oracle Fusion HCM business objects. For example, if you define additional person types, then you need to regenerate the GUIDs for the Oracle Fusion instance.




The course was designed for you to facilitate learners doing the specified activity at this point. Approximate Activity Timing: 5 minutes .



Activity 2 Introduction: Generating the Mapping File Background As an implementation consultant, you use HCM File-Based Loader to bulk-load business objects to Oracle Fusion HCM. Requirements


Activity Scope Open the manage HCM Configuration for Coexistence page and generate the mapping file of cross-reference information for HCM business objects. Retrieve the file from the Oracle WebCenter Content account hcm/dataloader/export.



Instructor Note: Generating the Mapping File In Oracle Fusion Human Capital Management 11g Release 7 (11.1.7), the mapping file of cross-reference information is written to the Oracle WebCenter Content account only. It is not written to the SFTP server. This is a known issue. For this reason, students retrieve the mapping file from Oracle WebCenter Content during this activity.



Activity 2: Generating the Mapping File In this activity, you generate the mapping file of cross-reference information (GUIDs) for Oracle Fusion HCM business objects and retrieve the file from the Oracle WebCenter Content account hcm/dataloader/export. Sign in as user HCM_IMPL or another implementation user, such as HCM_IMPL1. Start Here Setup and Maintenance work area, All Tasks tab

1. In the Name field of the Search section, enter Manage HCM Configuration for Coexistence.

2. Click Search. 3. In the Search Results section, click Go to Task. The Manage HCM

Configuration for Coexistence page opens. 4. In the Generate Mapping File for HCM Business Objects section of the

Manage HCM Configuration for Coexistence page, click Submit. An information message showing the process ID appears. Make a note of your process ID.

5. Click OK. 6. In the Generate Mapping File for HCM Business Objects section of the

Manage HCM Configuration for Coexistence page, click Search to display the process summary. You may need to click Search more than once if the process takes more than a few seconds to complete.

7. The process status value for your process ID must be 12. Click Search again if the process status value is 13, which means that the process has paused.

8. If the process does not complete in a reasonable time, open the Scheduled Processes work area (Navigator > Scheduled Processes) and search for your process ID. In the Search Results section on the Scheduled Processes page, note the Scheduled Time value for your process. This time is set automatically and may be some minutes after the submission time. Return to the Manage HCM Configuration for Coexistence page (Navigator > Setup and Maintenance > Manage HCM Configuration for Coexistence).

9. Once the process completes, the File column for your process ID on the Manage HCM Configuration for Coexistence page shows the name of the zip file that contains the generated GUIDs for Oracle Fusion HCM business objects. Make a note of the file name.

10. Open the File Import and Export page (Navigator > File Import and Export). 11. In the Search section of the File Import and Export page, select

hcm/dataloader/export in the Account field.



12. Click Search. 13. In the search results, identify your mapping file by the name and date values. 14. Click the file name in the File Name column. 15. In the Opening window, select Save File and click OK. 16. In the Enter name of file to save to window, select a desktop location and click

Save. 17. Close the Downloads window. 18. On the File Import and Export page, click Sign Out.

Information For this lesson, you do not need to use the mapping file because the data that you will import and load to Oracle Fusion HCM is provided for you. However, you can extract the file to a desktop folder and review the contents.



Importing the Mapping File to the Source Environment To ensure that foreign-key references in your source data to existing Oracle Fusion objects are correct, the GUID (globally unique identifier) values from the mapping file must be used. You need to devise a way of generating the correct values in the business objects that you plan to extract and upload to Oracle Fusion HCM. For example, you could store the mapping data in a temporary storage table and join to the table in the extract process. The following example shows GUIDs from an XR_ASSIGNMENT_STATUS_TYPE.dat file.

Row 2 (from FusionGUID through Description2) identifies the values supplied in each subsequent row.

• FusionGUID is the unique, 32-character alphanumeric identifier used by both Oracle Fusion HCM and source applications such as Oracle PeopleSoft and Oracle EBS.

• FusionKey is the value that is used by Oracle Fusion HCM. • PeopleSoftKey is the value that is used by the source system (which may be

Oracle PeopleSoft or some other system). • Description and Description2 describe the value identified by the keys.

More information about key mapping in general is provided in the next topic.



Key Mapping Records loaded from an external source to Oracle Fusion HCM must be uniquely identified in both source and target environments. In addition, a mapping must be maintained between the source and target keys. Keys are used to identify:

• The row being created or updated • The parent of the row being created or updated • Any objects referenced by the row being created or updated

Records Sourced Externally A record that is sourced externally includes a pointer to the external record, which is the record's Globally Unique Identifier (GUID). Oracle Fusion HCM maintains a key-mapping table (HRC_LOADER_BATCH_KEY_MAP) that records, for each business object, its type, source GUID, and Oracle Fusion ID (the ID by which it is identified in Oracle Fusion). When a record is imported to the Load Batch Data stage tables, the import process compares the record's source GUID and object-type values with values in the key-mapping table:

• If the values exist in the key-mapping table, then the process replaces the source GUID in the stage tables with the Oracle Fusion ID.

• If the values do not exist in the key-mapping table, then an Oracle Fusion ID is generated for the record, recorded in the key-mapping table, and used to replace the source GUID in the stage tables.

By the time the data in the stage tables is ready for loading to the application tables, all Oracle Fusion IDs have been allocated. The Oracle Fusion object services can process predefined Oracle Fusion IDs when creating new records. Records Sourced in Oracle Fusion HCM For each reference object that originates in Oracle Fusion HCM, the process Generate Mapping File for HCM Business Objects generates a source GUID and creates a row in the key-mapping table that holds both the newly generated GUID and the existing Oracle Fusion ID for the object. The process also generates a zip file of data files containing the GUIDs for the reference objects, which you import into your source environment. When you import source data that references these objects to the Load Batch Data stage tables, you must ensure that you include the reference-object GUIDs so that the correct reference objects can be identified. Business Object Key Map Extract



A predefined Business Object Key Map extract is available. The extract enables you to:

• Extract GUID key-mapping information from the HRC_LOADER_BATCH_KEY_MAP table to a report or an XML-format file.

• Generate GUIDs for objects not created using HCM File-Based Loader so that you can update those objects using HCM File-Based Loader.

More information about the Business Object Key Map extract is available in the HCM Data Conversion Reference Library (https://beehiveonline.oracle.com/teamcollab/wiki/HCM_Data_Conversion_Reference_Library_Workspace:Release+5+Coexistence+Libray).





Mapping Source Data to the Oracle Fusion Model You need to define mappings between your source data and the Oracle Fusion business-object model by comparing fields in the source data with the available fields in the Oracle Fusion HCM object schema. Refer to the document DataLoader Column Mapping XLS for FBL V1.1 in the HCM Data Conversion Reference Library (https://beehiveonline.oracle.com/teamcollab/wiki/HCM_Data_Conversion_Reference_Library_Workspace:Release+5+Coexistence+Libray) for information about each Oracle Fusion business object.





Extracting the Source Data Extract your source data for delivery to Oracle Fusion HCM. You can use tools that are native to the source system, such as PL/SQL in Oracle E-Business Suite or SQR in Oracle PeopleSoft. Alternatively, you can use an ETL (Extract, Transform, and Load) tool, such as Oracle Data Integrator (ODI) or PowerCenter Informatica, for this step. Oracle E-Business Suite HCM Extraction Toolkit For Oracle E-Business Suite (EBS) Release 11i and Release 12.1.x, an HCM Extraction Toolkit is available on My Oracle Support in document 1556687.1 (https://support.oracle.com/epmos/faces/DocumentDisplay?id=1556687.1). The HCM Extraction Toolkit is a set of tools for extracting HR objects from Oracle EBS for upload to Oracle Fusion HCM using HCM File-Based Loader. Briefly, the HCM Extraction Toolkit:

1. Creates sample EBS data using data-creation scripts in your Oracle EBS test system

2. Creates stage tables in your Oracle EBS test system 3. Transforms the sample EBS data into Oracle Fusion HCM format and extracts it

into the EBS stage tables 4. Includes validation scripts that you can use to validate the extracted data before

uploading it to Oracle Fusion HCM 5. Generates the data (.dat) files from the EBS stage tables for delivery to HCM

File-Based Loader

The HCM Extraction Toolkit:

• Supports all business objects required by Oracle Fusion Talent Management. However, as the package includes the transformation logic, you can extend it to support Compensation business objects, for example.

• Is coded specifically for the sample data, which loads to Oracle Fusion HCM without modification. You can adapt the package to suit your business needs.

• Supports creation of objects for an initial load. You can modify the toolkit to support update of objects.

https://support.oracle.com/epmos/faces/DocumentDisplay?id=1556687.1�



HCM File-Based Loader: Structure of the Import File You deliver your source data to Oracle Fusion HCM as a set of data files (.dat files) in a zip file containing one folder for each object type. For example, jobs comprise job and job grade data, and departments comprise department and department details data. If you load both in the same zip file, then the file structure will be:

No parent folder exists in the zip file. Each logical business object in the zip file is processed as a separate batch for loading. In this example, there are two batches, one for jobs and one for departments. Directory and data-file names must be as specified in the following tables:





The expected file format and delivery process apply whether you are creating or updating business objects. Refer to the following documents in the HCM Data Conversion Reference Library (https://beehiveonline.oracle.com/teamcollab/wiki/HCM_Data_Conversion_Reference_Library_Workspace:Release+5+Coexistence+Libray) for more information about the data-file structure and contents:

• DataLoader Column Mapping XLS for FBL V1.1 • FBL v1.1 Sample Demo Data.zip





Data-File Contents Each data file (.dat file) has a predefined format. Header Rows Data-file header rows comprise the Datastore Attribute Names for the object separated by pipe (|) characters. Header rows must be in uppercase characters and spelled as shown in the sample data files in the HCM Data Conversion Reference Library (https://beehiveonline.oracle.com/teamcollab/wiki/HCM_Data_Conversion_Reference_Library_Workspace:Release+5+Coexistence+Libray). Columns can appear in any order and optional columns can be omitted. Data Rows One or more data lines follow the header row. Object attributes in data lines are also separated by pipe characters. The following example shows F_WORK_RELATIONSHIP_VO.dat. The object columns appear in a nonstandard order. Attributes for which values appear in the file are in bold text in the header row.





Data-File Contents: Examples In the following example of the F_GRADE_RATE_VO.dat file, the annualization factor of a grade rate (a NUMBER value) is removed by setting it to NULL:

In the following example of the F_POSITION_GRADE_VO.dat file, new logical start and end dates are specified for a position grade. The position and position grade already exist in Oracle Fusion HCM. This file is updating the position grade. It demonstrates:

• Use of the LSD and LED columns • Update of an object by uploading just the changed entity

Refer to the following documents in the HCM Data Conversion Reference Library (https://beehiveonline.oracle.com/teamcollab/wiki/HCM_Data_Conversion_Reference_Library_Workspace:Release+5+Coexistence+Libray) for more information about the data-file structure and contents:

• DataLoader Column Mapping XLS for FBL V1.1 • FBL v1.1 Sample Demo Data.zip • HCM File-Based Loader User's Guide





Instructor Note: Copying the Data File to the SFTP Server No student activity is provided for this step because the way in which it works in the course is not typical. Instead, the files the students will upload will be staged on the SFTP server in directory /home/oracle/E_1/fapnnnn/ftp_inbox before the lesson. Details for accessing the SFTP server (using WinSCP, for example) are as follows:

• File Protocol: SFTP • Host Name: adcsamba.oracleads.com • Port: 22 • User: oracle • Password: welcome

Although the files are already on the SFTP server, they will also be provided in the course Beehive workspace in case they need to be loaded again or the students want to store the files locally for later study. File Details In the directory /fapnnnn/ftp_inbox, two files are provided for each student, one that creates 10 objects and one that updates 1 object that was previously created. The files are named as follows:

• fapnnnnStudentnnCreate.zip • fapnnnnStudentnnUpdate.zip

For example, for the 2 partners using environment fap0584, the following 4 files are provided in /home/oracle/E_1/fap0584/ftp_inbox:

• fap0584Student01Create.zip • fap0584Student01Update.zip • fap0584Student02Create.zip • fap0584Student02Update.zip

The data has been created using the mapping file of GUIDs from the relevant environment. Students should attempt to load only the files provided for their environments. For each environment, you need to identify one student as Student01 and one student as Student02.



HCM File-Based Loader: Importing Data to the Stage Tables Use an SFTP client such as WinSCP to transfer the zip file of .dat files containing your transformed source data to the /upload/E_1/ftp_inbox directory on the SFTP server. When your data is delivered to the SFTP server, you are ready to import the contents to the Load Batch Data stage tables. To perform this step, you invoke the InboundLoaderProcess web service to register the file with Oracle Fusion HCM. How you call the service depends on your URL. If your URL contains the string "oracleoutsourcing", then use the following URL. Replace POD in the string hcm-aufsn4x0POD with your 3-character environment code: https://hcm-aufsn4x0POD.oracleoutsourcing.com/soa-infra/services/default/HcmCommonBatchLoaderCoreInboundLoaderComposite/inboundloaderprocess_client_ep (https://hcm-aufsn4x0pod.oracleoutsourcing.com/soa-infra/services/default/HcmCommonBatchLoaderCoreInboundLoaderComposite/inboundloaderprocess_client_ep) If your URL contains the string "ap2.oraclecloud", then use the following URL. Replace POD in the string POD.hcm with your 3-character environment code: https://POD.hcm.ap2.oraclecloud.com/soa-infra/services/default/HcmCommonBatchLoaderCoreInboundLoaderComposite/inboundloaderprocess_client_ep (https://pod.hcm.ap2.oraclecloud.com/soa-infra/services/default/HcmCommonBatchLoaderCoreInboundLoaderComposite/inboundloaderprocess_client_ep) If your URL contains the string "em2.oraclecloud", then use the following URL. Replace POD in the string POD.hcm with your 3-character environment code: https://POD.hcm.em2.oraclecloud.com/soa-infra/services/default/HcmCommonBatchLoaderCoreInboundLoaderComposite/inboundloaderprocess_client_ep (https://pod.hcm.ap2.oraclecloud.com/soa-infra/services/default/HcmCommonBatchLoaderCoreInboundLoaderComposite/inboundloaderprocess_client_ep) In all other cases, use your Apps Homepage URL (ATK), and replace /homePage/faces/AtkHomePageWelcome with

https://hcm-aufsn4x0pod.oracleoutsourcing.com/soa-infra/services/default/HcmCommonBatchLoaderCoreInboundLoaderComposite/inboundloaderprocess_client_ep�



https://pod.hcm.ap2.oraclecloud.com/soa-infra/services/default/HcmCommonBatchLoaderCoreInboundLoaderComposite/inboundloaderprocess_client_ep�








/soa-infra/services/default/HcmCommonBatchLoaderCoreInboundLoaderComposite/inboundloaderprocess_client_ep In addition, replace either fs- with hcm- or .fs. with .hcm. (depending on which string appears in your URL). These changes create a URL that is similar to the three shown above.



HCM File-Based Loader: The InboundLoaderProcess The InboundLoaderProcess web service appears as follows:

In the User Name and Password fields, enter your Oracle Fusion Applications user name and password.

In the payload section:



• Set RunControlID and ProcessInstance to place-holder values such as 1234. These values do not affect processing.

• Enter the name of your zip file and its location in the ZipFileName and FileLocation fields.

• Enter an approximate date and time for the load in the TimeStamp field. • Set AutoLoad to Y if the load process is to be run automatically when the import

completes. Set AutoLoad to N if you plan to run the load process manually. • Set LoadType to FBL. • Each business object is processed as a separate batch. If you leave the

BatchName field blank, then the batch name is formed automatically by prefixing the object type with the internal loader batch ID (for example, 123456789: Person). You can enter a name in the BatchName field if you prefer. The name must be unique.

In the LBOList section, create an entry for each top-level object included in the zip file. Use the object names as specified for the object directories in the zip file. Click Invoke to call the web service. On successful invocation, you see the message "No response message" in the Test Result window.







Activity 3 Introduction: Running the InboundLoaderProcess Web Service Background As an implementation consultant, you use HCM File-Based Loader to bulk-load business objects to Oracle Fusion HCM. Requirements

• To invoke the InboundLoaderProcess web service you use the following URL, replacing the value fapnnnn in the URL with your environment number:

https://fapnnnn-hcm.oracleads.com/soa-infra/services/default/HcmCommonBatchLoaderCoreInboundLoaderComposite/inboundloaderprocess_client_ep (https://fapnnnn-hcm.oracleads.com/soa-infra/services/default/HcmCommonBatchLoaderCoreInboundLoaderComposite/inboundloaderprocess_client_ep). For example, to invoke the web service for environment fap0118, you use the URL https://fap0118-hcm.oracleads.com/soa-infra/services/default/HcmCommonBatchLoaderCoreInboundLoaderComposite/inboundloaderprocess_client_ep. (https://fap0118-hcm.oracleads.com/soa-infra/services/default/HcmCommonBatchLoaderCoreInboundLoaderComposite/inboundloaderprocess_client_ep)

• A zip file of data for you to import is preloaded on the SFTP server. For this activity, two files are provided for each environment, one for each student. For example, for environment fap0552, the files are named fap0552Student01Create.zip and fap0552Student02Create.zip. For environment fap0633, the files are named fap0633Student01Create.zip and fap0633Student02Create.zip.


Activity Scope Run the InboundLoaderProcess web service to register the zip file of data that is preloaded on the SFTP server with Oracle Fusion HCM. This web service decompresses the zip file and prepares it for import it to the Load Batch Data stage tables.

https://fapnnnn-hcm.oracleads.com/soa-infra/services/default/HcmCommonBatchLoaderCoreInboundLoaderComposite/inboundloaderprocess_client_ep�



https://fap0118-hcm.oracleads.com/soa-infra/services/default/HcmCommonBatchLoaderCoreInboundLoaderComposite/inboundloaderprocess_client_ep�





Activity 3: Running the InboundLoaderProcess Web Service In this activity, you run the InboundLoaderProcess to prepare your data for import. Start Here Open Browser.

1. In the browser, enter the endpoint URL for the InboundLoaderProcess web service for your environment. For example, for environment fap0602, enter

https://fap0602-hcm.oracleads.com/soa-infra/services/default/HcmCommonBatchLoaderCoreInboundLoaderComposite/inboundloaderprocess_client_ep (https://fap0602-hcm.oracleads.com/soa-infra/services/default/HcmCommonBatchLoaderCoreInboundLoaderComposite/inboundloaderprocess_client_ep)

2. Press Enter to display the inboundloaderprocess_client_ep interface. 3. In the WS-Security section, click the plus sign (+) to expand the section. 4. In the User Name field, enter your Oracle Fusion Applications user name (for

example, HCM_IMPL). 5. In the Password field, enter the Oracle Fusion Applications password for your

environment. 6. In the payload section, enter 1234 in the RunControlID field. This value has no

effect on the processing. 7. In the ProcessInstance field, enter 1234. This value has no effect on the

processing. 8. In the ZipFileName field, enter the name of your zip file of data. For example, if

you are Student 01 in environment fap0135, then enter fap0135Student01Create.zip.

9. In the FileLocation field, enter /fapnnnn/ftp_inbox, where fapnnnn is your environment identifier. For example, in environment fap0584, enter /fap0584/ftp_inbox.

10. In the TimeStamp field, enter an approximate time stamp in the format YYYY-MM-DDTHH:mm:ss.SSS. For example, 2013-07-18T15:30:00.000. This value is required.

11. In the AutoLoad field, enter N. 12. In the LoadType field, enter FBL. 13. In the BatchName field, enter Student01Create or Student02Create, as

appropriate. 14. In the LBOName section, click the green plus sign (+) 9 times to create 9

additional fields.






15. Enter the following values, one in each of the 10 fields in the LBOName section, spelled exactly as shown here: Location, BusinessUnit, Grade, GradeRate, JobFamily, Job, Person, Department, Position, and WorkRelationship.

16. Select the XML Source radio button that appears immediately above the WS-Security section. The XML version of the values that you have entered appears.

17. Select all of the XML source, right-click, and select Copy. 18. Open Notepad (Programs > Accessories > Notepad). 19. In Notepad, right-click and select Paste. 20. In Notepad, select File > Save As. Save the Notepad file to your desktop as

FBLLoaderCreate.txt. Saving your values in this way may help you to correct any problems that arise from the web service call.

21. Close Notepad. 22. In the inboundloaderprocess_client_ep interface, click Invoke. 23. In the Test Result window, you see the message "No response message". 24. Close your browser.

Information For this activity, you specify the file location /fapnnnn/ftp_inbox. The environment identifier (for example, fap0135) is used in the file location value because all environments are sharing an SFTP server and use of the environment identifier enables separation of the files. In general, you need to specify ftp_inbox only.



HCM File-Based Loader: Running the Import Process and Reviewing the Log File Once the InboundLoaderProcess web service completes, your file is ready to be imported to the Load Batch Data stage tables. To import the file, you open the Load HCM Data for Coexistence page and click Schedule. On the Schedule Request page, you select your file and specify either Import or Import and Load as the Run Type value. If you select Import, then no attempt is made to load the data to the application tables. In this case, you run the load process separately. You also specify a batch name value. This value forms the prefix for each business object in your file. For example, if your file contains Job and Job Family objects and you specify the batch name JobsTest, then your batch names are JobsTest:Job and JobsTest:JobFamily. On the Load HCM Data for Coexistence page, you search for your file to see the results of the import process. Any errors that occur during the import to the stage tables are written to a log file. You can access the log file for a batch in the Log column of the Search Results region on the Load HCM Data for Coexistence page. You can download the log file to your desktop by clicking the Log icon. Errors that occur during the import to the stage tables include:

• Missing primary keys • Missing parent keys • Incorrect or missing reference-data GUIDs • Incorrect date-effective records

You need to correct these errors and import your data to the stage tables again before you can load the data to the application tables.




The course was designed for you to facilitate learners doing the specified activity at this point. Approximate Activity Timing: 15 minutes . The zip files of data may be available immediately for selection in the File Name field on the Schedule Request page or they may take several minutes to appear. Signing out and in again usually causes the files to appear.



Activity 4 Introduction: Running the Import Process and Reviewing the Log File Background As an implementation consultant, you use HCM File-Based Loader to bulk-load business objects to Oracle Fusion HCM. Requirements


Activity Scope You have run the InboundLoaderProcess web service to register your data file (for example, fap0584Student01Create.zip). You import the data to the stage tables and review the log file on the Load HCM Data for Coexistence page.



Activity 4: Running the Import Process and Reviewing the Log File In this activity, you run the import process to import your data to the stage tables and examine the log file produced during the process. Sign in as user HCM_IMPL or another implementation user, such as HCM_IMPL1. Start Here Data Exchange work area

1. In the Tasks pane, select the Load HCM Data for Coexistence task. The Load HCM Data for Coexistence page opens.

2. On the Load HCM Data for Coexistence page, click Schedule. The Schedule Request page opens.

3. On the Schedule Request page, select your zip file of data (for example, fap0040Student02Create.zip) in the File Name field.

4. In the Loader Run Type field, select Import. 5. In the Batch Name field, enter Student01Create or Student02Create, as

appropriate. 6. Click Submit. 7. In the Confirmation window, click OK. 8. If your zip file does not already appear in the Search Results section of the

Load HCM Data for Coexistence page, then enter its name in the File field in the Search section of the page and click Search. For example, if you are Student02 in environment fap0040, then enter fap0040Student02Create.zip.

9. In the Search Results section of the Load HCM Data for Coexistence page, click Refresh to update the status of the import process for your file. You may need to click Refresh more than once until the process completes and its status is Succeeded.

10. When the import-process status for your file is Succeeded, click the Download File icon in the Log File column for your file in the Search Results section of the page.

11. In the Opening window, select Open with and select Adobe Acrobat or a browser so that the log-file contents display formatted.

12. Click OK. The log file opens in the selected application. Review the file contents and save the file locally if you wish. Close the file.

13. Close the Downloads window. 14. On the Load HCM Data for Coexistence page, click Done.

Information The log file provides a summary of the process of unzipping the file and importing its contents to the stage tables. In the log file, look for the Total number of rows



processed, Total number of rows inserted into HRC_LOADER_BATCH_LINES_SRC, and Total number of rows discarded values. In this activity, you insert 187 rows into the HRC_LOADER_BATCH_LINES_SRC table and process 10 objects.



HCM File-Based Loader: Loading Data to the Application Tables To load data from the stage tables to the Oracle Fusion application tables, you run the Load Batch Data process from the Load Batch Data page. You open the Load Batch Data page by selecting the Load Batch Data task from either the Data Exchange or Setup and Maintenance work area.

Data Exchange > Load Batch Data > Schedule In the Batch Name field, you select the name of the batch to load. If you entered a batch name in the BatchName field of the InboundLoaderProcess web service, then you should see that name here. The remaining parameters inherit the values that you specified when you configured the Load Batch Data process. Ensure that Loader Number of Processes is set to 4 or 8. Notes:

1. For the initial load, be sure to load objects in the recommended order to avoid errors arising from object dependencies.

2. The Load Batch Data process runs automatically if you have set the AutoLoad parameter of the InboundLoaderProcess web service to Y.



Monitor the Load Batch Data process in the Search Results section of the Load Batch Data page. Click Refresh to update the Batch Status column.




The course was designed for you to facilitate learners doing the specified activity, at this point. Approximate Activity Timing: 15 minutes .



Activity 5 Introduction: Loading Data to the Application Tables Background As an implementation consultant, you use HCM File-Based Loader to bulk-load business objects to Oracle Fusion HCM. Requirements


Activity Scope You have imported your data to the Load Batch Data stage tables and corrected any import errors. The import process created 10 object-specific batches (for example, Student01Create: Location, Student01Create: BusinessUnit, and so on). To load the data from the stage tables to the application tables, you run the Load Batch Data process for each of the 10 batches.



Activity 5: Loading Data to the Application Tables In this activity, you load your data from the stage tables to the application tables. Sign in as user HCM_IMPL or another implementation user, such as HCM_IMPL1. Start Here Data Exchange work area.

1. In the Tasks pane of the Data Exchange work area, select the task Load Batch Data to open the Load Batch Data page.

2. In the Batch Name field of the Search section of the Load Batch Data page, enter Student01Create or Student02Create, as appropriate.

3. Click Search. 4. In the Search Results section of the Load Batch Data page, you see all 10

batches extracted from your zip file and imported to the stage tables. The status of all batches is New.

5. Select the batch Student01Create:Location and click Run. The Schedule Request page opens.

6. Check that the correct batch name appears in the Batch Name field (for example, Student01Create:Location). Accept the default values on the Schedule Request page, and click Submit.

7. In the Confirmation message window, click OK. 8. On the Load Batch Data page in the Search Results section, click Refresh to

update the Batch Status and Process Status values. You may need to click Refresh more than once until the process completes.

9. When the process completes, the Batch Status value for the Location batch is Complete.

10. On the Batch Summary tab in the Details section of the Load Batch Data page, review the summary of successful and failed objects in the batch.

11. Repeat this process from Step 5 for the remaining batches in the following order: BusinessUnit, Grade, GradeRate, JobFamily, Job, Person, Department, Position, and WorkRelationship. Allow each batch to complete before you run the next. When a batch completes, it moves to the top of the search results. To move Complete batches to the bottom of the list, you can select Sort Descending on the Batch Status column header.

12. When all batches are loaded, click Done to close the Load Batch Data page.



HCM File-Based Loader: Reviewing Load Batch Data Results The Details section of the Load Batch Data page provides detailed information about the batch currently selected in the Search Results section of the page.

Data Exchange > Load Batch Data (In the Search Results, business objects with the suffix Di were loaded by HCM Spreadsheet Data Loader rather than HCM File-Based Loader.)

• The Batch Summary tab provides details of the business objects in the batch. Numbers greater than 0 in the Failed Objects column are hyperlinks that open the Details page for the batch.

• The Processes tab provides the status and timings of the Load Batch Data process for the selected batch.

• The Failed tab shows the details of any errors in the batch. Numbers greater than 0 in the Total Objects column are hyperlinks that open the Details page for the batch.

On the Details page (opened from hyperlinks on the Batch Summary or Failed tabs on the Load Batch Data page), you can review any objects in error in the batch. The Object Status value Error in Row means that either the object itself is in error or the complex logical business object to which it belongs is in error. You can display source keys by making the Source Object and Source ID columns visible in the Business Objects section table (View > Columns > Source ID, for example.)



Data Exchange > Load Batch Data > Details



HCM File-Based Loader: Correcting Load Errors When you select a single object in the Business Objects section on the Details page, its attributes appear on the Attributes tab of the Details page.

Data Exchange > Load Batch Data > Details These values are from the Load Batch Data stage tables, and you can correct them here by entering values in the New Value column. You may want to correct the stage-table data to test that you have fixed the error before applying any correction to the source data. Alternatively, you can correct the source data and reload it if you prefer. Load errors include:

• Setup errors, such as missing lookup codes in Oracle Fusion • Load-order errors, which occur when you try to load an object before objects on

which it is dependent • Invalid, duplicate, or missing attribute values • Format errors

If you correct an object, then you can set the Object Status value to Ready to Process. If you set it to Ignore, then the object is not processed when you next run the batch. If you simply want to remove objects in error from the batch, then you can do so on the Load Batch Data page. On the Failed tab, select objects to be removed and click Create Batch. The selected objects are removed from the original batch and added to a new batch.



On return to the Load Batch Data page, you can select the original batch again and rerun it. Any object with the status Error in Row is reset to Ready to Process and included in the batch. Objects with the status Successful or Ignore are not processed.



Validating Data Loaded Using HCM File-Based Loader You can validate records interactively by searching for a representative sample. For example, you can search for person records in the Person Gallery or jobs on the Manage Jobs page. You can also use BI Publisher to generate a report on business objects that you loaded and extract the details to a spreadsheet. The File Based Loader UPK link in the Load > Tools section of the HCM Data Conversion Reference Library (https://beehiveonline.oracle.com/teamcollab/wiki/HCM_Data_Conversion_Reference_Library_Workspace:Release+5+Coexistence+Libray) includes a demonstration of the process. BI Publisher is covered later in this course.









Activity 6 Introduction: Validating the Loaded Data Background As an implementation consultant, you use HCM File-Based Loader to bulk-load business objects to Oracle Fusion HCM. Requirements


Activity Scope You have loaded objects from the stage tables to the application tables using the Load Batch Data process. In this activity, you search for several of the objects that you loaded to confirm that they loaded successfully.



Activity 6: Validating Loaded Data In this activity, you validate that your data loaded successfully. Sign in as user HCM_IMPL or another implementation user, such as HCM_IMPL1. Start Here Setup and Maintenance work area, All Tasks tab Locations

1. In the Name field of the Search section, enter Manage Locations. 2. Click Search. 3. In the Search Results section, click Go to Task for the Manage Locations task.

The Manage Locations page opens. 4. On the Manage Locations page, enter Student01 or Student02, as appropriate,

in the Name field. 5. Click Search. 6. In the Search Results section, click the name of one of your locations to open

the Location page. 7. Review the details of the location. 8. Click Done to close the Location page. 9. On the Manage Locations page, click Done to return to the All Tasks tab of the

Setup and Maintenance work area.

Grades

1. In the Name field of the Search section, enter Manage Grades. 2. Click Search. 3. In the Search Results section, click Go to Task for the Manage Grades task.

The Manage Grades page opens. 4. On the Manage Grades page, enter Student01 or Student02, as appropriate, in

the Name field. 5. Click Search. 6. In the Search Results section, click the name of one of your grades to open the

Grade page. 7. Review the details of the grade. 8. Click Done to close the Grade page. 9. On the Manage Grades page, click Done to return to the All Tasks tab of the

Setup and Maintenance work area.

Persons and Work Relationships



1. Select Navigator > Person Management to open the Person Management work area.

2. In the Person Number field of the Search section, enter Student01 or Student02, as appropriate.

3. Click Search. 4. In the Search Results section, select the entry for Gary Norman. 5. The Person Management work area is refreshed to show the details of the

selected person. 6. Explore the information on the tabs of the Manage Person page. Notice that

Gary Norman has one e-mail in the E-Mail Details section. 7. In the Tasks pane, click Manage Employment to display employment

information for the person. 8. Explore the work relationship and assignment information that you loaded. 9. Click Done to close the Manage Employment page. 10. In the Warning message window, click Yes. 11. On the Manage Person page, click Cancel to return to the Search Person

page. If you wish, search for and review other person records that you loaded.

If time allows, you can validate other business objects that you loaded. Enter your identifier (Student01 or Student02, as appropriate) in the Name field of the Search section on the following pages to find your business objects:

• Manage Business Unit • Manage Grade Rates • Manage Job Families • Manage Departments • Manage Positions




The course was designed for you to facilitate learners doing the specified activity at this point. Approximate Activity Timing: 20 minutes . Perform activities 7, 8, and 9 immediately following activity 6. Activities 7, 8, and 9 repeat processes covered in earlier activities, which will consolidate student learning.



Activity 7 Introduction: Updating Loaded Data Background As an implementation consultant, you use HCM File-Based Loader to bulk-load business objects to Oracle Fusion HCM. Requirements


Activity Scope You have loaded person records successfully to the Oracle Fusion application tables. In this activity, you upload an additional e-mail for one of the person records you created via upload. The activity is in 3 stages. You:

1. Register the zip file containing the new e-mail with the InboundLoaderProcess web service.

2. Import the zip file to the stage tables. 3. Load the batch extracted from the zip file to the application tables.

The data for this activity is in file fapnnnnStudentnnUpdate.zip. For example, if you are Student 01 in environment fap0633, then your file is fap0633Student01Update.zip.



Activity 7: Updating Loaded Data In the first stage of this activity, you run the InboundLoaderProcess to prepare your data for import. Start Here Open Browser.

1. In the browser, enter the endpoint URL for the InboundLoaderProcess web service for your environment. For example, for environment fap0602, enter

https://fap0602-hcm.oracleads.com/soa-infra/services/default/HcmCommonBatchLoaderCoreInboundLoaderComposite/inboundloaderprocess_client_ep (https://fap0602-hcm.oracleads.com/soa-infra/services/default/HcmCommonBatchLoaderCoreInboundLoaderComposite/inboundloaderprocess_client_ep)

2. Press Enter to display the inboundloaderprocess_client_ep interface. 3. In the WS-Security section, click the plus sign (+) to expand the section. 4. In the User Name field, enter your Oracle Fusion Applications user name (for

example, HCM_IMPL). 5. In the Password field, enter the Oracle Fusion Applications password for your

environment. 6. In the payload section, enter 1234 in the RunControlID field. This value has no

effect on the processing. 7. In the ProcessInstance field, enter 1234. This value has no effect on the

processing. 8. In the ZipFileName field, enter the name of your zip file of data. For example, if

you are Student 01 in environment fap0118, then enter fap0118Student01Update.zip.

9. In the FileLocation field, enter /fapnnnn/ftp_inbox, where fapnnnn is your environment identifier. For example, in environment fap0118, enter /fap0118/ftp_inbox.

10. In the TimeStamp field, enter an approximate time stamp in the format YYYY-MM-DDTHH:mm:ss.SSS. For example, 2013-07-18T15:30:00.000. This value is required.

11. In the AutoLoad field, enter N. 12. In the LoadType field, enter FBL. 13. In the BatchName field, enter Student01Update or Student02Update, as

appropriate. 14. In the LBOName section, enter Person. 15. Select the XML Source radio button that appears immediately above the WS-

Security section. The XML version of the values that you have entered appears.






16. Select all of the XML source, right-click, and select Copy. 17. Open Notepad (Programs > Accessories > Notepad). 18. In Notepad, right-click and select Paste. 19. In Notepad, select File > Save As. Save the Notepad file to your desktop as

FBLLoaderUpdate.txt. Saving your values in this way may help you to correct any problems that arise from the web service call.

20. Close Notepad. 21. In the inboundloaderprocess_client_ep interface, click Invoke. 22. In the Test Result window, you see the message "No response message". 23. Close your browser.

In the second stage of this activity, you run the import process to import your updated data to the stage tables and examine the log file produced during the process. Sign in as user HCM_IMPL or another implementation user, such as HCM_IMPL1. Start Here Data Exchange work area

1. In the Tasks pane, select the Load HCM Data for Coexistence task. The Load HCM Data for Coexistence page opens.

2. On the Load HCM Data for Coexistence page, click Schedule. The Schedule Request page opens.

3. On the Schedule Request page, select your zip file of data (for example, fap0040Student02Update.zip) in the File Name field.

4. In the Loader Run Type field, select Import. 5. In the Batch Name field, enter Student01Update or Student02Update, as

appropriate. 6. Click Submit. 7. In the Confirmation window, click OK. 8. If your file does not already appear in the Search Results section of the Load

HCM Data for Coexistence page, then enter its name in the File field of the Search section of the page and click Search. For example, if you are Student02 in environment fap0040, then enter fap0040Student02Update.zip.

9. In the Search Results section of the Load HCM Data for Coexistence page, click Refresh to update the status of the import process for your file. You may need to click Refresh more than once until the process completes and its status is Succeeded.

10. When the import-process status for your file is Succeeded, click the Download File icon in the Log File column for your file in the Search Results section of the page.

11. In the Opening window, select Open with and select Adobe Acrobat or a browser so that the log-file contents display formatted.

12. Click OK. The log file opens in the selected application. In this activity, the log file shows that you inserted 1 row into the HRC_LOADER_BATCH_LINES_SRC



table and processed 1 object. Review the file contents and save the file locally if you wish. Close the file.

13. Close the Downloads window. 14. On the Load HCM Data for Coexistence page, click Done.

In third stage of this activity, you load your data from the stage tables to the application tables. In the Tasks pane of the Data Exchange work area, select the task Load Batch Data to open the Load Batch Data page.

1. In the Batch Name field of the Search section of the Load Batch Data page, enter Student01Update or Student02Update, as appropriate.

2. Click Search. 3. In the Search Results section of the Load Batch Data page, you see the

Person batch (for example, Student02Update:Person) extracted from your zip file and imported to the stage tables. The status of the batch is New.

4. Select the batch Student01Update:Person or Student02Update:Person, as appropriate, and click Run. The Schedule Request page opens.

5. Accept the default values on the Schedule Request page, and click Submit. 6. In the Confirmation message window, click OK. 7. On the Load Batch Data page in the Search Results section, click Refresh to

update the Batch Status and Process Status values. You may need to click Refresh more than once until the process completes.

8. When the process completes, the Batch Status value for your Person batch is Complete with Errors.

9. On the Batch Summary tab in the Details section of the Load Batch Data page, review the summary of successful and failed objects in the batch. Notice that you have 1 Failed Object and 0 Successful Objects.

Information You correct the failed object directly in the stage tables in the next activity.







Activity 8 Introduction: Correcting Load Errors Background As an implementation consultant, you use HCM File-Based Loader to bulk-load business objects to Oracle Fusion HCM. Requirements


Activity Scope You have run Load Batch Data to load an additional e-mail for a worker and a load error has occurred. As an alternative to correcting the source data and importing it to the stage tables again, you correct the error in the stage tables, which you access from the Load Batch Data page. Having corrected the error, you rerun the load process.



Activity 8: Correcting Load Errors In this activity, you correct load errors in the stage tables. Sign in as user HCM_IMPL or another implementation user, such as HCM_IMPL1. Start Here Data Exchange work area, Load Batch Data page

1. If your Person batch with the Batch Status value Complete with Errors does not already appear in the Search Results section of the page, then search for the batch by entering Student01Update or Student02Update, as appropriate, in the Batch Name field of the Search section of the Load Batch Data page and clicking Search.

2. Select the batch in the Search Results section. 3. On the Batch Summary tab in the Details section of the page, you can see

details of the batch. 4. Click the Failed tab in the Details section to display details of the error. In this

case, the error message is "The e-mail address format is incorrect." 5. Click the Batch Summary tab in the Details section. 6. The Failed Objects column on the Batch Summary tab for the parent object

(Person) contains the number 1. Click the number to open the Details page for the object type.

7. In the Business Objects section on the Details: Person page, expand the Person object folder.

8. Expand the PersonEmail folder in the Person object folder, and then select the PersonEmail entry in the folder to display its details in the Details section of the page.

9. The Attributes tab in the Details section of the Details: Person page displays the object attribute values.

10. Correct the attribute in error by entering a corrected value in the New Value column. In this case, the @ sign is missing from the EmailAddress attribute value. The correct value is [email protected] or [email protected], as appropriate.

11. When you have finished updating the selected object instance, set the Object Status value for the object in the Business Objects section of the Details: Person page to Ready to Process.

12. Click Save and Close. 13. On the Load Batch Data page, find your batch again in the Search Results

section. 14. Click Run. 15. On the Schedule Request page, accept the default values and click Submit. 16. In the Confirmation window, click OK.



17. On the Load Batch Data page, click Refresh in the Search Results section. You may need to click Refresh more than once until the process completes.

18. When the Batch Status is Complete, review the contents of the Details section of the page. Notice that the batch now contains 1 successful object and 0 failed objects.







Activity 9 Introduction: Validating Updated Data Background As an implementation consultant, you use HCM File-Based Loader to bulk-load business objects to Oracle Fusion HCM. Requirements


Activity Scope You successfully corrected the data that you uploaded previously. In this activity, you search for the updated person record to confirm that the additional e-mail exists.



Activity 9: Validating Updated Data In this activity, you validate that you updated your data successfully. Sign in as user HCM_IMPL or another implementation user, such as HCM_IMPL1. Start Here Person Management work area, Search Person page

1. In the Person Number field of the Search section of the Search Person page, enter Student01_Person109 or Student02_Person109, as appropriate.

2. Click Search. 3. In the Search Results section, you see the person record for Gary Norman.

Click the name Norman, Gary in the Search Results section to open the Manage Person page.

4. On the Person Information tab of the Manage Person page, review the E-Mail Details section for Gary Norman. Notice that Gary Norman now has 2 e-mails, one for work and one for home.

5. On the Manage Person page, click Cancel. 6. On the Search Person page, click Sign Out



Using Oracle WebCenter Content Oracle WebCenter Content is a strategic solution for the management, security, and distribution of unstructured content such as documents, spreadsheets, presentations, and video. It is a component of Oracle Fusion Middleware and is integrated seamlessly with Oracle Fusion Applications. The outline process that you follow for bulk-loading data using HCM File-Based Loader is the same, regardless of whether you use SFTP or WebCenter Content for file transfers. When using WebCenter Content, you:

1. Set the Load Batch Data configuration parameters appropriately. 2. Generate the mapping file of cross-reference information, which is written

automatically to the hcm/dataloader/export WebCenter Content account. 3. Download the mapping file from the hcm/dataloader/export WebCenter Content

account. You can use either the File Import and Export page (Tools > File Import and Export) in Oracle Fusion Applications or a command-line tool to retrieve the file.

4. Upload your source data in a zip file to the hcm/dataloader/import WebCenter Content account. You can use either the File Import and Export page or a command-line tool to check in the file.

5. Run the Loader Integration Service to retrieve the file from the WebCenter Content server.

On input to the Loader Integration Service, you specify:

• The name of the zip file to be loaded • The business objects that you are loading • The batch name • The load type (FBL) • Whether the imported file is to be loaded automatically.

To import files to and export files from WebCenter Content, you need the Human Capital Management Integration Specialist job role. On the Load Batch Data page, you can review the progress of the data import and load the data to the application tables.



HCM File-Based Loader: Best Practices Prepare the Source Data Identify the business objects that you are planning to upload to Oracle Fusion HCM and their source systems. Review and analyze this legacy data, and work with the customer to verify that the data is both accurate and current. If it is not, then devise a plan to correct any problems before you attempt to load it. In particular:

• Ensure that a manager is identified for every employee and that the information is accurate.

• For jobs and positions, ensure that accurate job codes and titles exist in the legacy system.

• For job history, establish the accuracy of any historical data. Understand whether all historical data must be uploaded or just key events, such as hire, promotion, and termination.

Cleaning up the legacy data will minimize the problems that can occur when you upload the data to Oracle Fusion HCM. Prepare for Upload

• Know your SFTP or WebCenter Content user credentials. • Set the configuration parameters for the Load Batch Data process appropriately. • Understand the Oracle Fusion HCM implementation to which you are importing

data. For example, identify the legal employers, business units, and reference data sets.

• Know which Oracle Fusion lookups you need to set and identify required functional mappings (for example, worker numbers, job definitions, and position definitions).

• Design your data transformations. For any business object that you plan to load, refer to the reference information for HCM File-Based Loader in the Load Tools section of the HCM Data Conversion Reference Library (https://beehiveonline.oracle.com/teamcollab/wiki/HCM_Data_Conversion_Reference_Library_Workspace:Release+5+Coexistence+Libray).

Understand Your Deployment Model

• Are you migrating data or implementing a coexistence scenario? • If your deployment model requires that data be updated via upload, then devise a

strategy for ongoing data maintenance.

Manage the Upload Process





• Always perform a test load to the stage environment of a small amount of data for all object types that you need to load. Only when the test loads are successful and you have validated the data transformations should you load data to the production environment.

• Load objects in the prescribed order to avoid data-dependency errors. For initial loads, you are recommended to load each object type separately so that problems can be more easily diagnosed and fixed.

• Plan ahead if you need to load flexfields. You must log a service request and allow 5 days for the request to be processed.

• Do not mix your use of HCM File-Based Loader with HCM Spreadsheet Data Loader. Use one or the other, but not both, for related data.

• You may need to delete data loaded to the stage environment. Deletion scripts are preinstalled in your stage environment, and you follow supplied instructions to run them. Be aware that these scripts delete all data rather than just the rows in error. For more information, see the Delete Scripts Information document in the HCM Data Conversion Reference Library (https://beehiveonline.oracle.com/teamcollab/wiki/HCM_Data_Conversion_Reference_Library_Workspace:Release+5+Coexistence+Libray).





HCM Spreadsheet Data Loader

Lesson Agenda




HCM Spreadsheet Data Loader: Overview HCM Spreadsheet Data Loader generates spreadsheets dynamically for several Oracle Fusion HCM business objects. Each spreadsheet contains columns for the object attributes, identifies required values, and uses lists of values (LOVs) for many attributes to aid completion. Once you have populated the spreadsheet with your data, the upload, validation, and correction of the data are straightforward processes. Benefits of HCM Spreadsheet Data Loader include:

• Ease and speed of use • Support for some key business objects • Flexfield support • Use of the standard Load Batch Data process (also used by HCM File-Based

Loader), which provides error handling and is multithreaded • Minimal configuration • Mass error correction in spreadsheets • Offline working

HCM Spreadsheet Data Loader is most suitable for loading:

• Setup data • Nonhierarchical data and simple hierarchical data • Small-to-medium volumes of data • One-time-only data batches, as it offers very limited support for data update

HCM Spreadsheet Data Loader is unsuitable for:

• Loading large volumes (tens of thousands) of records • Coexistence and similar scenarios where repeated loading and update of data

may be required • Loading complex logical business objects, as objects are flattened to fit the

spreadsheet format • Loading object history

To use HCM Spreadsheet Data Loader:

• You must have installed the Oracle ADF Desktop Integration Add-in for Excel. If the client has been enabled for installation, it is available from Navigator > Tools. Instructions for enabling installation of the client are provided in the Oracle Fusion Applications Post-Installation Guide 11g Release 7 (11.1.7).

• You must be able to access the Oracle Fusion HCM Data Exchange work area. For this access, you need the Application Implementation Consultant or Human Capital Management Application Administrator job role.





HCM Spreadsheet Data Loader: Process Summary The process of generating a spreadsheet and uploading its contents using HCM Spreadsheet Data Loader is summarized in the following figure:

• In the Data Exchange work area, you generate the spreadsheet for a specific business object.

• After entering data in the spreadsheet, you import it to the Load Batch Data stage tables.

• Once the data is imported successfully, you run Load Batch Data to load the data to the application tables.

• If errors occur during the load stage, then you can extract them to an errors spreadsheet, correct the data, import it again to the stage tables, and rerun Load Batch Data.

Once all data is successfully loaded, you can validate it in the Oracle Fusion interfaces. For example, if you load positions, then you can search for them on the Manage Positions page.



In the next few topics, we discuss supported objects and functionality before examining the process in more detail and demonstrating the steps.



HCM Spreadsheet Data Loader: Supported Objects Using HCM Spreadsheet Data Loader, you can load the following Oracle Fusion HCM 11g Release 7 (11.1.7) business objects:

1. Locations 2. Grade ladders (grades) 3. Grades 4. Grade ladders (grades with steps) 5. Job families 6. Jobs 7. Departments 8. Positions 9. Persons (employees and contingent workers only) 10. Work relationships and assignments 11. Educational establishments 12. Salaries 13. Talent profile content items 14. Talent profiles

Objects are listed here in the recommended load order, which respects dependencies between objects. Some of these spreadsheets support multiple related objects. For example, the Grade Ladders (Grades) spreadsheet can be used to load grade ladders, grades, grade rates, and grade-rate values. The Persons spreadsheet includes Person Documentation.



HCM Spreadsheet Data Loader: Supported Functionality Using HCM Spreadsheet Data Loader, you can:

• Create supported objects. • Update worker and assignment records.

You can also update salary records by indicating in the spreadsheet itself whether to create, update, or delete. You cannot update other supported objects, nor can you delete other objects. Date Effectivity When updating worker and assignment records, you can both correct and update records:

• To correct a record, you specify the same effective start date as was used to create the record.

• To update a record, you specify a different effective start date from the date that was used to create the record.

Flexfield Support HCM Spreadsheet Data Loader support for flexfields is as follows:

• Descriptive flexfields (DFFs) are supported in the location, department, job, job family, position, worker, and work relationship assignment spreadsheets.

• Developer descriptive flexfields (DDFs) are supported in the worker and work relationship assignment spreadsheets.

• Extensible flexfields (EFFs) for Organization Manager Information, GL Cost Center Information, and Work Day Information are supported in the department spreadsheet.

• US and FR legislative flexfields are supported in the job and location spreadsheets.

• The person legislative flexfield is supported in worker spreadsheets. • The People Group flexfield is not supported.



Finding Detailed Information About HCM Spreadsheet Data Loader Spreadsheets In the HCM Data Conversion Reference Library (https://beehiveonline.oracle.com/teamcollab/wiki/HCM_Data_Conversion_Reference_Library_Workspace:Release+5+Coexistence+Libray) (in the Load > Tools section), you can find detailed information about each spreadsheet provided by HCM Spreadsheet Data Loader. Information provided here includes:

• An example spreadsheet for each supported object • Flexfield support • Use cases supported by the spreadsheet • Use cases not supported by the spreadsheet • Additional reference information

For example, for the Location spreadsheet, we learn that the following use cases are supported:

• Create locations. • Add location legislative information.

Also for locations, we learn that the following use cases are not supported:

• Add location extra information. • Update an existing location. • Delete an existing location. • Add another address to an existing location.

For the PER_LOCATIONS_DF flexfield, we learn that the following are supported:

• Attribute1 - Attribute15 • AttributeNumber1 - AttributeNumber10 • AttributeDate1 - AttributeDate5

Additional reference information for the Location spreadsheet identifies how address styles are supported. You are recommended to refer to the HCM Data Conversion Reference Library (https://beehiveonline.oracle.com/teamcollab/overview/HCM_Data_Conversion_Reference_Library_Workspace) before using HCM Spreadsheet Data Loader.



https://beehiveonline.oracle.com/teamcollab/overview/HCM_Data_Conversion_Reference_Library_Workspace�




Instructor Note: Finding Detailed Information About Spreadsheets Open the HCM Data Conversion Reference Library (https://beehiveonline.oracle.com/teamcollab/wiki/HCM_Data_Conversion_Reference_Library_Workspace:Release+5+Coexistence+Libray) and explore the HCM Spreadsheet Data Loader materials there (follow the link to the HCM Spreadsheet Data Loader wiki) so that partners will have a good idea of the scope and usefulness of this resource. Links in this course to the HCM Data Conversion Reference Library take you to the Release 5 library. All available libraries can be accessed from this page (https://beehiveonline.oracle.com/teamcollab/wiki/HCM_Data_Conversion_Reference_Library_Workspace). A Release 7 library will be published at some point and be accessible from the same page as the other libraries.



https://beehiveonline.oracle.com/teamcollab/wiki/HCM_Data_Conversion_Reference_Library_Workspace�

https://beehiveonline.oracle.com/teamcollab/wiki/HCM_Data_Conversion_Reference_Library_Workspace�



Generating the Spreadsheet You generate HCM Spreadsheet Data Loader spreadsheets on the Initiate Data Load page. To open the Initiate Data Load page, you can:

• Open the Data Exchange work area and select the Initiate Data Load task. Users with either the Application Implementation Consultant or Human Capital Management Application Administrator job role can open the Data Exchange work area directly.

• Perform the FSM task Initiate HCM Data Load. Users with the Application Implementation Consultant job role can perform this task.

Navigator > Data Exchange > Initiate Data Load Objects are listed on the Initiate Data Load page in the recommended load order. Notice also that the spreadsheets are specific to the action you are performing. Create Worker is a different spreadsheet from Update Person, for example. Similarly, Create Grade Ladder (Grades) is different from Create Grade Ladder (Grades with Steps).





Instructor Note: Preparing for the HCM Spreadsheet Data Loader Demonstrations During the HCM Spreadsheet Data Loader section of this lesson, you demonstrate use of the HCM Spreadsheet Data Loader to the class. You will be saving spreadsheets locally, so create a desktop folder for that purpose before you start. You also need the supplied file of sample data (Lesson22_ImportData_SDLData.txt). If the file has not been supplied to you by some other means, you can find it in this folder (https://stbeehive.oracle.com/teamcollab/library/st/2013+Fusion+HCM+Partner+Bootcamp+Initiative/Documents/Bootcamp+Content/Activity+Testing+-+Week+of+June+3/Lesson+22+-+Import+Data). You are recommended to save the sample-data file to the same desktop folder that you will use for the spreadsheets.

https://stbeehive.oracle.com/teamcollab/library/st/2013+Fusion+HCM+Partner+Bootcamp+Initiative/Documents/Bootcamp+Content/Activity+Testing+-+Week+of+June+3/Lesson+22+-+Import+Data�





Instructor Note: Demo Timing

Approximate Demonstration Timing: 13 minutes .



Demonstration: Generating the Spreadsheet Demonstration Background As an implementation consultant, you use HCM Spreadsheet Data Loader to bulk-load business objects to Oracle Fusion HCM. Demonstration Scope Go to the Initiate Data Load page, generate a spreadsheet from the page, and save it locally. Demonstration Steps Sign in as hcm_impl or hcm_impl1. Start Here Data Exchange work area

1. In the Tasks pane, click the task Initiate Data Load.

2. On the Initiate Data Load page, locate the spreadsheet row for Create Worker.

3. Click the Create Spreadsheet icon in the Create Worker row.

4. In the Opening HcmDataLoader.xlsx window, select to open the file rather than save it. For example, select Open with Microsoft Office Excel or Open with Microsoft Open XML Converter, whichever appears as the default option.

5. In the Login message window, in answer to the question "Do you want to connect?", click Yes.

6. In the Login window, enter your user ID (for example, HCM_IMPL) in the User ID field and your password in the Password field.

7. Click Sign In. The Invoke Action processing message may appear for several seconds before the spreadsheet opens fully.

8. In the spreadsheet, click Office Button > Save As > Excel Workbook.

9. In the Save As window, select your desktop or another convenient location.

10. Enter the name CreateWorkerExample in the File name field.



11. Click Save.

12. Close the spreadsheet. A few seconds may pass before the spreadsheet closes.

13. If a Downloads window is still open, then close it.

14. On the Initiate Data Load page, click Done.

Information The generated spreadsheet always has the name HcmDataLoader.xlsx, regardless of the object type. When you save the spreadsheet locally, you can rename it. You will use the saved spreadsheet in later demonstrations.



Completing the Spreadsheet When you have saved the spreadsheet locally, you are ready to start entering your data. The spreadsheet itself provides much of the information you need. It:

• Includes all supported attributes in the required order • Identifies required attributes with an asterisk • Includes lists of values with value names rather than codes, where appropriate • Links to Oracle Fusion Help, where you can find topics on the HCM Spreadsheet

Data Loader process

You can also refer to the HCM Data Conversion Reference Library (https://beehiveonline.oracle.com/teamcollab/overview/HCM_Data_Conversion_Reference_Library_Workspace) for more detailed reference information. This information will help you to prepare your data in the required format. To populate the spreadsheet, you can extract data from its source environment into a different spreadsheet, and copy and paste it from there into the HCM Spreadsheet Data Loader spreadsheet. Note that you must ensure that the column order in the source spreadsheet matches the order in the HCM Spreadsheet Data Loader spreadsheet. Also, you must have inserted the required number of blank rows in the HCM Data Loader spreadsheet before pasting in your data. Alternatively, you can enter data directly in the HCM Spreadsheet Data Loader spreadsheet. This approach may be efficient if you are using HCM Spreadsheet Data Loader to create a small number of objects, such as multiple jobs. You can copy the contents of one row, paste the copied data into a blank row, and edit relevant values.









Demonstration: Entering Data in the Generated Spreadsheet Demonstration Background As an implementation consultant, you use HCM Spreadsheet Data Loader to bulk-load business objects to Oracle Fusion HCM. Demonstration Scope Open the spreadsheet you saved locally in the previous demonstration and explore the spreadsheet structure and functions. Paste in supplied data. Demonstration Steps Sign in as hcm_impl or hcm_impl1. Start Here Desktop location of the saved CreateWorkerExample spreadsheet

1. Double-click the saved spreadsheet CreateWorkerExample to open it.

2. In the Batch Name field, enter the name CreateWorkerExample to replace the default batch name.

3. Scroll to the right through the spreadsheet and identify some of the required fields, marked with an asterisk, such as Country, Global Last Name, Work Relationship Start Date, and Worker Type.

4. Click in fields that provide lists of values to show their values. For example, Address Type, Phone Type 1, Marital Status, Ethnicity, and Gender. You may need to click the first field that you select more than once before the list of values appears. Any delay occurs with the first field that you select only.

5. Click View Help in the top left corner of the spreadsheet. The Invoke Action processing message may appear for a few seconds.

6. In the Login message window, in answer to the question "Do you want to connect?", click Yes.




8. Click Sign In. The Help pane opens showing links to help topics about HCM Spreadsheet Data Loader. A few seconds may pass before the links load.

9. Click the X in the Help pane to close it.

10. The spreadsheet contains one blank data row. Scroll to the left, select the blank data row, drag the mouse down to include 1 additional row only, right-click, and select Insert. This action adds 2 more blank rows to the spreadsheet. The spreadsheet now contains 3 blank rows.

11. In the desktop folder that you created for the demonstration files, double-click the supplied file of sample data Lesson22_ImportData_SDLData.txt to open it in Notepad.

12. In the sample data file, select Edit > Select All, then Edit > Copy.

13. Close the sample data file.

14. In the spreadsheet, place the cursor in the Country cell following the Person Number cell in the first blank row.

15. Right-click and select Paste. The 3 lines of sample data are copied to the 3 rows of the CreateWorkerExample spreadsheet.

16. Click Save.

17. Close the spreadsheet.

Information Whenever you connect to Oracle Fusion Applications from the spreadsheet, you must sign in using your Oracle Fusion Applications user name and password.



HCM Spreadsheet Data Loader: Importing Data to the Stage Tables and Correcting Import Errors When all data is in the HCM Data Loader spreadsheet, you click Upload to import it to the Load Batch Data stage tables.

HCM Spreadsheet Data Loader: Create Worker Spreadsheet As each row of data is imported to the stage tables, its status is updated automatically in the spreadsheet:

• Row inserted for batch processing means that the row was imported successfully.

• Insert failed means that the row was not imported.

Identify any rows with the status Insert failed in your spreadsheet and double-click the status value in each row to display a description of the error. After fixing the errors, click Upload in the spreadsheet to upload the corrected rows to the same batch.







Demonstration: Importing Data to the Stage Tables and Correcting Import Errors Demonstration Background As an implementation consultant, you use HCM Spreadsheet Data Loader to bulk-load business objects to Oracle Fusion HCM. Demonstration Scope Upload the data you entered in the spreadsheet CreateWorkerExample in the previous demonstration and correct any import errors. Demonstration Steps Sign in as hcm_impl or hcm_impl1. Start Here Desktop location of the saved CreateWorkerExample spreadsheet

1. Double-click the CreateWorkerExample spreadsheet to open it.

2. Click Upload in the spreadsheet.

3. In the Login message window, in answer to the question "Do you want to connect?", click Yes. The Invoke Action processing message may appear for a few seconds.


5. Click Sign In. The Invoke Action processing message may appear for a few seconds.

6. In the Upload Options window, accept the default options and click OK. The Invoke Action processing message may appear for a few seconds.

7. As each row is imported, its status in the spreadsheet is updated. Scroll left, if necessary, to review the import status for each row in the Status column.

8. Identify the row in the spreadsheet where the status is Insert failed.

9. Select the Status cell for the failed row.



10. Double-click the error message in the Status cell and review the error message that appears. In this demonstration, the work relationship start date for Ronnie Scott is in the incorrect format.

11. Click OK to dismiss the error message.

12. Scroll right to find the Work Relationship Start Date cell for Ronnie Scott.

13. Enter the date in the format DD/MM/YYYY. Press Enter or left-click in a different cell to align the date correctly in the cell.

14. Click Upload to import the corrected rows to the same batch. The Invoke Action processing message may appear for a few seconds.


16. Scroll to the left to view the Status column. Confirm that the status of the corrected row is now Row inserted for batch processing.


18. In the Microsoft Office Excel window, click Yes to save your changes.

Information Whenever you connect to Oracle Fusion Applications from the spreadsheet, you must sign in using your Oracle Fusion Applications user name and password.



HCM Spreadsheet Data Loader: Loading Data to the Application Tables Once all data from the HCM Data Loader Spreadsheet is imported successfully to the Load Batch Data stage tables, you are ready to load the data to the application tables. To load data from the stage tables to the application tables, you run the Load Batch Data process. To run the Load Batch Data process, you open the Load Batch Data page in the Data Exchange work area and search for your batch. Having selected your batch in the search results, you click Run.







Demonstration: Loading Data to the Application Tables Demonstration Background As an implementation consultant, you use HCM Spreadsheet Data Loader to bulk-load business objects to Oracle Fusion HCM. Demonstration Scope Search for the batch you imported successfully to the Load Batch Data stage tables and load it to the application tables. Demonstration Steps Sign in as hcm_impl or hcm_impl1. Start Here Data Exchange work area

1. In the Tasks pane, click the task Load Batch Data to open the Load Batch Data page.

2. Enter the batch name CreateWorkerExample in the Batch Name field.

3. Click Search.

4. In the Search Results section, select the batch CreateWorkerExample and click Run. The Schedule Request page opens.

5. Accept the default values on the Schedule Request page, and click Submit.

6. In the Confirmation message window, click OK.

7. On the Load Batch Data page in the Search Results section, click Refresh to update the Batch Status and Process Status values. You may need to click Refresh more than once until the process completes.

8. When the process completes, the Batch Status value is Complete with Errors.

Information You will correct the load errors in the next demonstration by extracting the errors to a spreadsheet.



HCM Spreadsheet Data Loader: Correcting Load Errors Having submitted the Load Batch Data process to load data to the application tables, you need to monitor the batch status and correct any errors. To review the batch status, you search for the batch on the Load Batch Data page (or just click Refresh if the batch already appears). If the Batch Status value in the search results for the batch is:

• Complete, then your data was loaded to the application tables without error • Complete with Errors, then at least one error occurred and you need to fix it.

Data Exchange > Load Batch Data > Search Results section To fix load errors, you select the batch in the Search Results section. In the Details section, you extract the errors for the selected batch to a spreadsheet by selecting Action > Extract Failed Objects to Spreadsheet.

Data Exchange > Load Batch Data > Details section The errors spreadsheet is created automatically and populated with the error rows. You can save the spreadsheet locally, review the error messages in the spreadsheet for each row, and fix the errors. When all errors are fixed, you click Upload to import the



corrected rows to the original batch in the Load Batch Data stage tables. When the import succeeds, you run Load Batch Data again to load the corrected data to the application tables. As an alternative to extracting errors to a spreadsheet, you can fix them directly in the stage tables before rerunning the batch. The stage-table data is accessible from the Failed Objects column of the Details section on the Load Batch Data page. You may prefer this approach if you have very few errors. We cover this approach in the HCM File-Based Loader section of this lesson.







Demonstration: Correcting Load Errors Demonstration Background As an implementation consultant, you use HCM Spreadsheet Data Loader to bulk-load business objects to Oracle Fusion HCM. Demonstration Scope You extract any load errors to a spreadsheet, correct them, and import and load the corrected rows again. Demonstration Steps Sign in as hcm_impl or hcm_impl1. Start Here Data Exchange work area, Load Batch Data page

1. If the batch CreateWorkerExample is not already visible in the Search Results section, then enter CreateWorkerExample in the Batch Name field and click Search.

2. In the Search Results section, the batch status is Complete with Errors.

3. Select the CreateWorkerExample batch in the Search Results section to display its details in the Details section.

4. On the Batch Summary tab of the Details section, notice that 2 objects succeeded and 1 failed. Click Action > Extract Failed Objects to Spreadsheet.

5. In the Opening HcmErrorCorrection.xlsx window, select to open the file rather than save it.

6. In the Login message window, in answer to the question "Do you want to connect?", click Yes. The Invoke Action processing message may appear for a few seconds.


8. Click Sign In. The Invoke Action processing message may appear for a few seconds.



9. The spreadsheet HcmErrorCorrection opens containing one row for the failed object.

10. In the HcmErrorCorrection spreadsheet, review the error message for the failed row. Select the Error Message cell to display the complete message at the top of the spreadsheet. In this example, a required field, Business Unit, is missing.

11. Scroll right or perform a text search to find the Business Unit cell of the failed row and enter USA1 Business Unit in the cell.

12. Scroll left to see the Changed cell for the row. If the cell does not include the Changed indicator ( ) then press Enter to show the indicator.

13. Click Upload to import the corrected row to the batch CreateWorkerExample. The Invoke Action processing message may appear for a few seconds.


15. Confirm that the status of any corrected rows in the spreadsheet is now Row updated for batch processing.


17. In the Microsoft Office Excel window, in answer to the question "Do you want to save HcmErrorCorrection.xlsx?", click No.

18. If a Downloads window is open, then close it.

19. On the Load Batch Data page, locate the batch CreateWorkerExample in the Search Results section and select it.

20. Click Run. The Schedule Request page opens.

21. Accept the default values on the Schedule Request page, and click Submit.

22. In the Confirmation message window, click OK.

23. On the Load Batch Data page, click Refresh in the Search Results section to update the Batch Status and Process Status values. You may need to click Refresh more than once until the process completes.

24. When the process completes, the Batch Status value is Complete. In the Details section for the batch, the Batch Summary tab shows that there are now 3 successful objects.



25. On the Load Batch Data page, click Done.

Information The errors spreadsheet is named HcmErrorCorrection.xlsx by default. If you save the spreadsheet, you can rename it. Once all records in a batch are successfully loaded, you cannot load additional records to the same batch and any upload attempt fails. Instead, you need to use a different batch name.







Demonstration: Validating Data Loaded Using HCM Spreadsheet Data Loader Demonstration Background As an implementation consultant, you use HCM Spreadsheet Data Loader to bulk-load business objects to Oracle Fusion HCM. Demonstration Scope You are signed in as user HCM_IMPL or another implementation user, such as HCM_IMPL1. In the Oracle Fusion HCM Person Gallery, search for the workers you loaded using HCM Spreadsheet Data Loader. Demonstration Steps Sign in as hcm_impl or hcm_impl1. Start Here Person Gallery

1. In the Keywords field on the Search tab, enter the last name Scott.

2. Click Search.

3. In the search results, click the worker name Ronnie Scott to open the worker's portrait.

4. In the worker's portrait, validate data that you included in the load, such as the work e-mail and phone.

5. Repeat steps 1 through 4 for the other workers in the load (Lorri Cope and Alice Wilkes).

6. In the Keywords field on the Search tab of the Person Gallery, enter the name of the manager of the new workers, Mateo Lopez.

7. Click Search.

8. In the search results, click View in Organization Chart for Mateo Lopez.

9. Click the plus sign + on the base of the node for Mateo Lopez in the organization chart to display his direct reports.



10. Confirm that each of the new workers (Ronnie Scott, Lorri Cope, and Alice Wilkes) reports to Mateo Lopez.

11. Click Sign Out.



HCM Spreadsheet Data Loader: Best Practices For successful use of HCM Spreadsheet Data Loader, the following approaches are recommended:

• Do not mix your use of HCM Spreadsheet Data Loader with use of File-Based Loader. Use one or the other, but not both, for related data.

• Always perform a test load of small amount of data for all object types that you plan to load to the stage environment. Only when the test loads are successful should you load data from a spreadsheet to the production environment.

• For any business object that you plan to load, refer to the guidance in the Load Tools section of the HCM Data Conversion Reference Library (https://beehiveonline.oracle.com/teamcollab/wiki/HCM_Data_Conversion_Reference_Library_Workspace:Release+5+Coexistence+Libray).

• Load objects in the prescribed order to avoid data-dependency errors.





Future Enhancements In Oracle Fusion HCM 11g Release 8 (11.1.8), HCM Spreadsheet Data Loader is enhanced as follows:

• Spreadsheets include a Configure Flexfield option. You select a flexfield type to include relevant columns in the spreadsheet.

• Import and load are both performed automatically when you click Upload in a spreadsheet. You no longer need to run Load Batch Data explicitly.

• Load errors are reported in the original spreadsheet when you click Refresh. You no longer need to extract load errors to an errors spreadsheet.

Beyond Release 8, the intention is to incorporate HCM Spreadsheet Data Loader in HCM Data Loader, which is discussed at the end of this lesson.



HCM File-Based Loader and HCM Spreadsheet Data Loader: Post-Load Processes After an initial or incremental load of person records, you run a set of processes to complete data setup in the Oracle Fusion HCM environment. You run these processes in the following order from the Scheduled Processes work area:

1. Synchronize Person Records 2. Update Person Search Keywords 3. Calculate Relationship Strength 4. Refresh Manager Hierarchy 5. Send Pending LDAP Requests

Synchronize Person Records This process communicates changes to person and assignment records that have occurred since the last data load to consuming applications, such as Oracle Fusion Trading Community Model and Oracle Identity Management (OIM). Update Person Search Keywords This process copies attributes of person, employment, and profile records that are used as search keywords to the PER_KEYWORDS table, where they are indexed to improve search performance. The process updates the entire PER_KEYWORDS table. Calculate Relationship Strength In the Person Gallery, search results can appear in order of the strength of the relationship between the person performing the search and each person in the search results: the stronger the relationship, the nearer to the top of the results a person's assignment appears. This process updates stored relationship-strength information. Refresh Manager Hierarchy For performance reasons, the complete manager hierarchy for each person is extracted from live data tables and stored in a separate manager-hierarchy table, known as the denormalized manager hierarchy. This process populates the denormalized manager hierarchy tables with latest information after each data load. Send Pending LDAP Requests When you load person records, user-account requests are created automatically. This process sends those bulk requests to OIM immediately to create (and also suspend or re-enable) user accounts, as appropriate. In addition, roles are provisioned to users in accordance with role-provisioning rules in effect when the accounts are created. Note: Before you run this process, review your data conversion fully and confirm its accuracy. If you need to purge your data and repeat the conversion, it will take much longer if you have created user accounts and notified users of their sign-in details.



You can control aspects of the provisioning process for the enterprise by setting the User and Role Provisioning options on the Manage Enterprise HCM Information page. For example, you can suppress the automatic creation of user accounts. Compensation Processes Depending on the business objects that you are loading and how you plan to use them, you may also need to run the following processes:

• Start Compensation Cycle. You run this process when all data is loaded and the compensation cycle is ready to be started.

• Refresh Workforce Compensation. You run this process if you upload changes to data in Oracle Fusion HCM and those changes need to be reflected in the compensation cycle.

You can find more information about these post-load processes in the Workforce Deployment Implementation Guide, the Compensation Management Implementation Guide, and the Coexistence for HCM Implementation Guide.



HCM File-Based Loader and HCM Spreadsheet Data Loader: Use Cases In this topic, we examine some data-loading use cases to confirm the strengths of each of the available solutions. Use Case 1 You need to load approximately 300 job definitions from a legacy system. The requirement is to load the definitions once only and maintain them in Oracle Fusion HCM. Solution: You could use either HCM Spreadsheet Data Loader or HCM File-Based Loader. However, as there is no requirement for update support, HCM Spreadsheet Data Loader's simpler configuration and ease of use make it the better option in this case. Use Case 2 You want to implement a coexistence scenario, where person and employment records are maintained in a legacy system but talent data is migrated to Oracle Fusion HCM. Solution: HCM File-Based Loader is the only possible solution for this or any other coexistence scenario, because you must be able to update data that you have previously loaded. HCM Spreadsheet Loader does not support update for most objects. In addition, HCM File-Based Loader supports automation of the load process, which is a useful feature in coexistence scenarios where data uploads are regular and predictable. Use Case 3 You need to migrate a variety of business objects from a legacy system to Oracle Fusion HCM. The data volumes are high, and for some types of objects you need to load tens of thousands of records. Solution: HCM File-Based Loader is the only possible solution for loading such volumes of data. Even if the volumes were much smaller for some objects, you could not use both HCM Spreadsheet Data Loader and HCM File-Based Loader to load related objects. In this case, you must load all of your data, both small volumes and large, using HCM File-Based Loader. Use Case 4 You need to load approximately 500 person records and their history. The data includes the records of some nonworkers. Solution:



HCM File-Based Loader is the solution because you cannot use HCM Spreadsheet Data Loader to load either nonworkers or object history.



Specialized Data Loaders

Lesson Agenda




Payroll Batch Loader The Payroll Batch Loader is a spreadsheet loader that is generic within Payroll. It is accessed from the Payroll Administration or Data Exchange work area and can be used to load the following Payroll objects:

• Balances • Balance groups • Bank information for EFT payments • Elements • Element entries • Fast Formula global values • Object groups • Payroll relationships • Personal payment methods

Data is imported initially to the Payroll Batch Loader stage tables, and you correct errors in the spreadsheet. The Transfer Batch process loads data from the stage tables to the application tables. You can use the Payroll Batch Loader to load payroll data during setup or for periodic updates.



Compensation and Benefits Data Loaders For Benefits, the following object-specific spreadsheets are launched from object interfaces, load directly to application tables, and support error correction in the spreadsheet:

• Benefit enrollments • Benefit rates • Person benefit balances • Person benefit groups • Person habits • Benefit plans • Postal code ranges and service areas • Benefit programs • Regulations • Reporting groups

You can use these spreadsheets to load Benefits data during setup and for periodic updates. For Compensation, the following object-specific spreadsheet is available in the Compensation work area:

• Stock grants

In addition, spreadsheet loaders are available from user interfaces for the following absences and availability entities:

• Absence history • Absence types and absence reasons • Accrual plans • Work schedule assignments • Work patterns • Work schedules



Talent Data Loaders For Talent Management, the following object-specific spreadsheets are launched from object interfaces, load directly to application tables, and support error correction in the spreadsheet:

• Competencies • Organization and worker goals • Performance ratings

You can load talent data from third-party suppliers or an existing library during setup. You can also use these spreadsheet loaders for periodic updates.



Core HR Data Loaders For Global Human Resources, the following object-specific spreadsheets are available from object interfaces, such as Manage Locations. They load directly to application tables and support error correction in the spreadsheet:

• Departments • Jobs • Legal entities • Locations

These spreadsheet loaders are effectively superseded by HCM Spreadsheet Data Loader (for departments, jobs, and locations) and the Enterprise Structures Configurator (for legal entities). They are mentioned here for completeness.



Future Plans for Data Loading

Lesson Agenda




HCM Data Loader The long-term plan for data loading is to provide a single tool, which is referred to as HCM Data Loader. Over several releases, HCM Data Loader will deliver the functions currently delivered by HCM File-Based Loader, HCM Spreadsheet Data Loader, and some of the specialized data loaders. However, until HCM Data Loader is able to deliver the full set of data-loading functions, it will coexist with the existing tools, which will continue to evolve. HCM Data Loader is intended to provide the standard data-import solution and a single entry point for managing bulk data loading to Oracle Fusion HCM.

In the long term, HCM Data Loader will:

• Deliver a new loading engine, data model, and file reader • Support multiple file formats • Generate file and spreadsheet templates dynamically

HCM Data Loader is scheduled for initial release in Oracle Fusion HCM Release 8 (11.1.8) and will continue to be developed in subsequent releases.



In addition to support for all HCM File-Based Loader functionality, features of HCM Data Loader in Oracle Fusion HCM Release 8 include

• A comprehensive user interface for data loading, error management, and configuration

• Support for fully automated imports • Support for additional business objects • Delimited-file imports with a simplified file structure

Documentation will be provided on My Oracle Support to help you convert from HCM File-Based Loader to HCM Data Loader at the appropriate time.



Inbound Web Services As an alternative to upload-specific tools, such as HCM Spreadsheet Data Loader and HCM File-Based Loader, it is possible to use inbound integration services for programmatic data exchange with external systems. Several Oracle Fusion HCM inbound integration services are to be published in a future release so that you can write your own integrations to the cloud. The initial roll-out will be managed on a customer-by-customer basis. Public integration services will be documented in Oracle Enterprise Repository (OER). For each service, OER will provide details of the service method and parameters with step-by-step instructions for invoking the service. Among the initial services to be published will be HR job and job family, organization, person, position, location, salary, payroll element and element entry, and talent profile.



Import Data Review Questions

Review Question 1 You are recommended to use HCM Spreadsheet Data Loader to load small volumes of complex hierarchical business objects.

1. True 2. False



Review Question 2 Using HCM File-Based Loader, you can:

1. Upload selected entities of a business object 2. Upload a partial object history for a date-effective business object 3. Set optional attributes to NULL 4. Change the logical start or end date of a date-effective object 5. All of the above



Review Question 3 A recommended approach is to mix and match your use of HCM File-Based Loader and HCM Spreadsheet Data Loader for loading related data. Use each loader for the business-object types and volumes that it is most suited to.

1. True 2. False



Instructor Note: Import Data Review Questions You are recommended to use HCM Spreadsheet Data Loader to load small volumes of complex hierarchical business objects.

1. True 2. False

Answer: 2 (False) Using HCM File-Based Loader, you can:

1. Upload selected entities of a business object 2. Upload a partial object history for a date-effective business object 3. Set optional attributes to NULL 4. Change the logical start or end date of a date-effective object 5. All of the above

Answer: 5 (All of the above) A recommended approach is to mix and match your use of HCM File-Based Loader and HCM Spreadsheet Data Loader for loading related data. Use each loader for the business-object types and volumes that it is most suited to.

1. True 2. False

Answer: 2 (False)



Lesson Highlights In this lesson, you should have learned about:

• The ways in which Oracle Fusion HCM supports data import • Loading data using HCM File-Based Loader • Loading data using HCM Spreadsheet Data Loader • Selecting an appropriate data-import mechanism for your purposes • Data-import approaches planned for future releases of Oracle Fusion HCM



Technology

21 import data