Human Capital Management Data Conversion (Employee Locations)

 

 

Data Conversion Mapping Specification

 

 

              Human Capital Management Data Conversion

 (Employee Locations)

 

 

 

 

 

Author:                              

Creation Date:                     

Last Updated:                      

Document Ref:                   

Version:                                 0.1

 

Note:Title, Subject, Last Updated Date, Reference Number, and Version are marked by a Word Bookmark so that they can be easily reproduced in the header and footer of documents.  When you change any of these values, be careful not to accidentally delete the bookmark.  You can make bookmarks visible by selecting Tools->Options…View and checking the Bookmarks option in the Show region.

 

 

Document Control

Change Record

2

Date	Author	Version	Change Reference

 

 

Reviewers

Name	Position

 

Approvers

 

Name	Position

 

 

Contents

Document Control...................................................................................... 2

Change Record........................................................................................... 2

Reviewers.................................................................................................. 2

Approvers.................................................................................................. 2

Introduction.............................................................................................. 4

Conversion Scope, Strategy And Assumptions.................................................. 4

Prerequisites.............................................................................................. 4

MAPPING SPECIFICATIONS........................................................................... 5

Data Extract Component Logic...................................................................... 7

Data Extraction Rules................................................................................... 7

Upload Component Logic............................................................................. 8

Data Flow Assumptions/ Prerequisites............................................................ 8

Navigation Steps........................................................................................ 8

Open and Closed Issues............................................................................. 10

Open Issues.............................................................................................. 10

Closed Issues............................................................................................ 10

 

Note:To update the table of contents, put the cursor anywhere in the table and press [F9].  To change the number of levels displayed, select the menu option Insert‑>Index and Tables, make sure the Table of Contents tab is active, and change the Number of Levels to a new value.

 

Introduction

Note:A work product document should be produced for each of the business entities being converted.  You may want to use the Subject field to indicate the business entity.

The purpose of this document is to document and communicate the configurations, data mapping, interdependency and component design specifications for the conversion of an individual entity that is going to be converted to the Oracle Cloud applications.

Following Objects will be converted:

Employee Locations

Conversion Scope, Strategy And Assumptions

The Conversion Component Designs is used by the project team as the basis for the design and construction of the Employee Locations data conversion.

High Level Conversion Process Overview- Employee Locations data

a.      The Data Migration of Oracle Employee Locations data data will involve conversion of data from CLIENT’s old legacy system (Workday) into CLIENT’s new Oracle Fusion.

b.      The data being migrated from CLIENT’s old system into new system will be transformed because the source and target data structures are different.

c.      The datafile provided will be used to build the import HDL file templates with Metadata of Locations

 

Prerequisites

Following configurations are required in SaaS

None

MAPPING SPECIFICATIONS

Please find attached import datafile provided to build the data as per HDL import file. The detail mapping is provided in the table below.

 

Location HDL (Employee Location Detail)

Oracle FBDI Field Name	Description	Mapping from legacy system/Values
*METADATA	This is HDL System required field	Default “MERGE”
Location	This is HDL System required field	Default “Location”
SourceSystemId	This is HDL System required unique value for Location Metadata. Will be concatenated with Sequence_NumberI’_’II’LOC’	Default “Sequence_Number’_’II’LOC’”
SourceSystemOwner	This is HDL System required field	Default “SYSTEMOWNER_HDL”
EffectiveStartDate		Effective start date defaulted to earlier start date “1900/08/16”
EffectiveEndDate		Default to “4712/12/31” which is Open dated
SetCode		Default “COMMON” to be used across global employee
ActiveStatus		Default “A”
LocationCode		Datafile.Work Location
LocationName		Datafile.Work Location
Description		Datafile. Work Location Address Full
AddressLine1		Datafile. Work Location Address Line 1
Country		Datafile. Work Location Address Country
PostalCode		Datafile. Work Location Address Postal Code
TownOrCity		Datafile. Work Location Address City
ReplaceFirstEffectiveStartDate		Default “Y”

 

Data Extract Component Logic

Note:Describe the component logic for the download component(s) used to convert the entity being converted.

Bring  Employee Locations and related details from existing legacy system to New Fusion

 

Pool: Only Include Active Employees Locations Data

 

 

Data Extraction Rules

·        Only Active Employees Locations from workday for all the countries in scope will be extracted in the Data File.

·        Location Name and Location Code should be first two parts of Work Location (BRA - Barueri)

o   BRA - Barueri - Videojet Do Brasil Comércio de Equipamentos Para Codificação Industrial Ltda.

·        Description should have the entire Work Location

·        Special characters should be populated correctly

 

 

Upload Component Logic

 

1. Download the template:

        1. Log in to Oracle Fusion Applications.

        2. Navigate to My Client Groups.

        3. Go to Data Exchange and click on View Business Objects under HCM Data Loader.

        4. Search for Location Business object and click on the Template File to download the template.

        5. Save the template to your local drive.

2. Prepare the data in the HDL file, then save the file and click on Compress to ZIP file to generate the ZIP file.

3. Upload the template:

        1. Navigate to My Client Groups.

        2. Go to Data Exchange and click on Import and Load Data.

        3. Click on Import File and select the Zip File from your system.

        4. Click Submit Now to upload the Location data. A confirmation message will display the Process Request ID for the upload. Use these IDs to track the progress of the upload process.

        5. Monitor the progress of process request ID in the Search Results section. Click the Refresh icon to refresh the status.

        6. You can view the Import success (%), Load success (%) and previous upload submission. Click the Refresh icon to refresh the status.

Navigation Steps

1.      Log in to Oracle Fusion Applications.

2.    2.  Click on username icon on the top right. See the highlighted part below:

1.    3.  After clicking on username, click on Setup and Maintenance.

1.      4. Click on Search from the right side.

5. Search ‘Manage Locations’.

6.Click on ‘Manage Locations’ and give the location name on the Name field as per below screenshot:

7.Click on the location name to see the details.

8.      Below is the screenshot from location screen:

Data Flow Assumptions/ Prerequisites

The development specifications for Employee Locations data assume the following:

Key Assumptions are:

·        The data of Employee Locations data will be provided by the CLIENT extraction team directly into CSV Datafile.

·        Oracle technical team will prepare the data in the required Oracle standard HDL formats.

·        HDL Metadata for Location will be build based on single Employee datafile provided

 

 

 

Open and Closed Issues

 

Note:Add open issues that you identify while writing or reviewing this document to the open issues section.  As you resolve issues, move them to the closed issues section and keep the issue ID the same.  Include an explanation of the resolution.

When this work product is complete, any open issues should be transferred to the project- or process-level Issue Log (Manage focus area) and managed using a project level Issue Form (Manage focus area).  In addition, the open items should remain in the open issues section of this work product, but flagged in the resolution column as being transferred.

Open Issues

 

ID	Issue	Resolution	Responsibility	Target Date	Impact Date
1	Length of location field. Need solution for conversion and integration	Open
2	Inventory Locations are needed
3.	Decision is required on duplicate location code	open
4

 

Closed Issues

 

ID	Issue	Resolution	Responsibility	Target Date	Impact Date
1	Length of location field. Need solution for conversion and integration	Closed
2
3.
4