AIM

END USER GUIDE

Oracle Financials
Oracle Applications 12 Implementation

Training Manual for Lagos State Government

Employees

Dataload for Data Migration

AUTHOR/APPROVAL

CREATION DATE: APRIL 29, 2019

Last Updated: April 29, 2019
Author: John Odion OSHIOTSE
Document Ref: DAT/MIG/1.0
Version: 1.0

Approvals:

Softalliance GM Implementation Gbenga Omolokun

Soft Alliance Project Manager Esther Eruga

1 Document Control

Change Record
3

Reviewers

Name Position

Distribution

Copy No. Name Location

1
Library Master Project Library
2 Project Manager
3
4

Note to Holders:
If you receive an electronic copy of this document and print it out, please
write your name on the equivalent of the cover page, for document control
purposes.
If you receive a hard copy of this document, please write your name on the
front cover, for document control purposes.

Table of Contents
AIM 1
END USER GUIDE 1
AUTHOR/APPROVAL 2

DOCUMENT CONTROL 3

1.0 What is Dataload

2.0 Dataload Commands, Mouse and Key Board Simulation

2.10 Commands
2.20 Mouse Simulation
2.30 Key Board Simulation

3.0 How to use dataload

3.10 Understanding the Navigation Interface
3.20 Reference Targeted Window
3.30 Dataload Macro recording Simulation

4.0 Dataload limitations

4.10 Data Skip
4.20 Poor Network
4.30 Poor Monitoring

Overview
 Objectives: This document explains how to use dataload for data migration in
oracle e-business suite applications.
Prerequisites: Oracle forms in HR, Fixed Asset, GL applications etc.

1.0 What is Dataload

Dataload is a tool oracle application use for data migration. DataLoad enables users to control
and manipulate other applications. It is most often used to load data into these applications
and in to Oracle E-Business Suite in particular. Although DataLoad is aimed at Oracle E-Business
Suite, it can be used with any program running in the Windows environment, including Java
based software and those running within thin client environments, e.g. Citrix.
DataLoad enables non-technical end users to create and use loads in almost any area of an
application. DataLoad includes a number of options for loading data through an application's
forms. Because the data is entered through the forms these loads can be setup by non-
technical end users and no programming or technical database knowledge is required.
Furthermore, when data is entered through the forms there should be no support implications
because the data is validated by the application in the normal way, i.e. as if it had been entered
by a user.
Please see screen shot of a dataload interface below.

2.10 Dataload Commands

To use dataload for data migration in any application, one has to be extremely conversant with
the various commands. Here we will highlight few of the major commands required and the
expected behavior in oracle forms. This however depends on the navigation of the interface the
data is intended.

2.20 Dataload Mouse Simulation

 A number of people have difficulty with the *ML command, to do a Left Mouse click. I
did, too, to begin with, but this is the technique that I use, and it works for me.

 Arrow When you type *ML in a DataLoad cell, you get a pop-up window - read it. Take
your hands off the mouse and the keyboard and read it again.

 Arrow Then use ALT+TAB to move to the Form you want to click and position the mouse
pointer over the appropriate field and let go of the mouse - do NOT click, do NOT press
"Enter".

 Arrow Use ALT+TAB to get back to DataLoad - KEEP YOUR HANDS AWAY FROM THE
MOUSE.

 Arrow Now press "Enter" and DataLoad will record the co-ordinates of the mouse. Yes,
it is on the wrong window, but it is in the right position on the screen if the correct Form
was open (which it will be during playback).

Screen shot of Mouse

Simulation
 2.30 Dataload Keyboard Simulation

The easiest way to load data into a form is using a keyboard and mouse and this is what
DataLoad does with Macro loads. You configure in DataLoad the data, keystrokes and mouse
clicks that you want loaded into your application form(s). When you run the load DataLoad
sends the data, presses the keys and clicks the mouse as you specified. All keyboard keys can be
used by DataLoad in any combination and the left and right mouse buttons can also be used.
DataLoad calls the same low-level Windows code that is used when users press keys or use the
mouse, so the application you are loading data into cannot differentiate between data entered
by you and data entered by DataLoad.

To build a DataLoad Macro load write down the keystrokes and mouse clicks you use to enter
one record in your application. Now enter that into a DataLoad row and copy the instructions
down into as many rows as the number of records you are going to load. Finally, paste your
data into the DataLoad cells that correspond to the fields in your form. Your load is now built!

In Forms Data Loader you can send keystrokes to the target application by entering the "\" as
the starting letter. FDL recognizes a cell as keystroke if the cell contains as back slash "\" in the
first position. For Example, to send ALT and F keystroke enter \%f to send "ALT-FV" enter \%fv. 

E.G: Macro Coded DL to delete element simulating the keyboard, mouse and use of command

Data DL Commands Mouse Simulation Keystroke Simulation

3.10 Understanding the Navigation Interface

This is extremely important for one to effectively utilize dataload for migrating data. Knowing
and understanding the application/forms navigation is crucial for successful simulation of
keyboards, mouse and use of dataload commands. In a nutshell, one should know how to
navigate through forms to be able to design data load for migration.

Let’s consider the screen shot below showing the form HR Jobs are loaded

Navigation: Login to the Application – Go to System Administrator Responsibility – Click on

Applications – Go and Click Validation – Click on Values then enter the search parameters on
the Name Field in the Find Value Set Form and click on Find at the bottom right of the form
 Note: Understanding the application navigation is paramount to data migration.

3.20 Reference Targeted Window and Command Group

Designing dataload requires that one should know how to reference the targeted window and the
command group before data can be migrated to the application. When this is not done or not
done correctly, dataload will declined at the point of loading. See the screen shot below

Window
Command Group

3.30
Dataload Macro Recording Simulation

Automating loading of data through Macro Loading feature can be carried out in just 3 steps.
 1. Record
2. Populate the data from Excel or CSV or any delimited file.
3. Play

Here’s short description of above steps.

Start your target application form in which you would like to automate loading of data and move the cursor
on the 1st field.

For Example, we want to add new users in Oracle EBS. Login to Oracle Apps and navigate to System
Administrator->Security->Users 
as shown in picture below

 Start Forms Data Loader by clicking on its desktop icon.

 Click “Create New by Macro Recording” button and a dialog will be displayed.

 Click “Icon ” button in the

toolbar and OK in
dialog popup
Click “check box” button to start recording

 Change to your target application

form window by using mouse click or Alt+TAB keys
 At this point enter a sample record in your target application form just as you do normally.
Remember to use Keyboard keys to navigate in the target form and not to use mouse clicks to
navigate between fields unless you have checked "Record Mouse Clicks" checkbox

 Copy the recorded row and past on the dataload workspace

 Make copy of the coded row and replace the testuser5-------10

4.0 Dataload Limitations

4.10 Data Skip

One major limitation to dataload usage is data skip. This implies that dataload can skip data
meant for a row to another if not well monitored.

4.20 Poor Network

This is another major limitation which hamper data during loading. Dataload can not function
properly when there is poor network. Though loading can be delayed, by doing this the whole
essence of using dataload must have been defeated. The aim of using dataload is to make task
faster.

4.30 Poor Monitoring

Monitoring dataload while migrating data is significant because poor network or other factor
which are application based can make the data to skip row. Poor monitoring will Invariably
affect data accuracy and completeness.

Note: Dataload can be very interesting when all the above-mentioned limitation are properly
handled

Appendices

Fig 1: Dataload Command

 Equivalent Keystroke Sent in
Shortcut Description Behaviour in Oracle Forms Oracle Apps Oracle Rel Other
Oracle Apps NCA
11i/R12 10SC Apps
TAB TAB Key Key Next_item \{TAB} \{TAB} \{TAB} \{TAB}
ENT Enter Depends on Context \{ENTER} \{ENTER} \{ENTER} \{ENTER}
*UP Up arrow key Key Up \{UP} \{UP} \{UP} \{UP}
*DN Down arrow key Key Down \{DOWN} \{DOWN} \{DOWN} \{DOWN}
*LT Left arrow key Depends on Context \{LEFT} \{LEFT} \{LEFT} \{LEFT}
*RT Right arrow key Depends on Context \{RIGHT} \{RIGHT} \{RIGHT} \{RIGHT}
*SP Save & Proceed MENU CUSTOM FILE ACCEPT \%F%V \%A%{DOWN 4}{ENTER} \%A%A
*SAVE Save Key Commit_form \^S \^S \{F10}
*NB Next Block Key Next_block \+{PGDN} \+{PGDN} \^{PGDN}
*PB Previous Block Key Previous_block \+{PGUP} \+{PGUP} \^{PGUP}
*NF Next Field Key Next_item \{TAB} \%G%{DOWN}{ENTER} \{TAB}
*PF Previous Field Key Previous_item \+{TAB} \%G%{DOWN 2}{ENTER} \+{TAB}
*NR Next record Key Down \{DOWN} \%G%{DOWN 3}{ENTER} \+{DOWN}
*PR Previous record Key Up \{UP} \%G%{DOWN 4}{ENTER} \+{UP}
*FR First record MENU CUSTOM RECORD FIRST \%V%DF \%G%{DOWN 5}{ENTER} \%G%F
*LR Last record MENU CUSTOM RECORD LAST \%V%DL \%G%{DOWN 6}{ENTER} \%G%L
*ER Erase record Key Clear_record \{F6} \{F6} \+{F4}
*DR Delete record Key Delete_record \^{UP} \^{UP} \+{F6}
*SB Space bar Depends on Context \{SPACE} \{SPACE} \{SPACE} \{SPACE}
*ST Select field text [none] \{HOME}+{END} \{HOME}+{END} \{HOME}+{END}
*BM Block menu Key Block_menu \^B \^B \{F5}
*QE Query enter Key Enter_query \{F11} \{F11} \{F7}
*QR Query run Key Execute_query \^{F11} \^{F11} \{F8}
*FI Find MENU CUSTOM VIEW FIND \%V%F \%Q%{DOWN}{ENTER}
*FA Find all MENU CUSTOM VIEW FIND_ALL \%V%I \%Q%{DOWN 2}{ENTER}
*IR Insert record Key Create_record \^{DOWN} \^{DOWN} \{F6}
*CL Clear field Key Clear_item \{F5} \{F5} \^U
*FE Field edit Key Edit \^E \^E \^E
*AA Alt A Depends on Context \%A \%A \%A \%A
*AB Alt B Depends on Context \%B \%B \%B \%B
*AC Alt C Depends on Context \%C \%C \%C \%C
*AD Alt D Depends on Context \%D \%D \%D \%D
*AE Alt E Depends on Context \%E \%E \%E \%E
*AF Alt F Depends on Context \%F \%F \%F \%F
*AG Alt G Depends on Context \%G \%G \%G \%G
*AH Alt H Depends on Context \%H \%H \%H \%H
*AI Alt I Depends on Context \%I \%I \%I \%I
*AJ Alt J Depends on Context \%J \%J \%J \%J
*AK Alt K Depends on Context \%K \%K \%K \%K
*AL Alt L Depends on Context \%L \%L \%L \%L
*AM Alt M Depends on Context \%M \%M \%M \%M
*AN Alt N Depends on Context \%N \%N \%N \%N
*AO Alt O Depends on Context \%O \%O \%O \%O
*AP Alt P Depends on Context \%P \%P \%P \%P
*AQ Alt Q Depends on Context \%Q \%Q \%Q \%Q
*AR Alt R Depends on Context \%R \%R \%R \%R
*AS Alt S Depends on Context \%S \%S \%S \%S
*AT Alt T Depends on Context \%T \%T \%T \%T
*AU Alt U Depends on Context \%U \%U \%U \%U
*AV Alt V Depends on Context \%V \%V \%V \%V
*AW Alt W Depends on Context \%W \%W \%W \%W
*AX Alt X Depends on Context \%X \%X \%X \%X
*AY Alt Y Depends on Context \%Y \%Y \%Y \%Y
*AZ Alt Z Depends on Context \%Z \%Z \%Z \%Z
To close a
\%-C window
To close a
\{^F4} window

Fig 2: Keystroke

Key Code
BACKSPACE \{BACKSPACE}, \{BS}, or \{BKSP}
BREAK \{BREAK}
CAPS LOCK \{CAPSLOCK}
DEL or DELETE \{DELETE} or \{DEL}
DOWN ARROW \{DOWN}
END \{END}
ENTER  \{ENTER}or ~
ESC \{ESC}
HELP \{HELP}
HOME \{HOME}
INS or INSERT \{INSERT} or \{INS}
LEFT ARROW \{LEFT}
NUM LOCK \{NUMLOCK}
PAGE DOWN \{PGDN}
PAGE UP \{PGUP}
PRINT SCREEN \{PRTSC}
RIGHT ARROW \{RIGHT}
SCROW LOCK \{SCROWLOCK}
TAB \{TAB}
UP ARROW \{UP}
F1 \{F1}
F2 \{F2}
F3 \{F3}
F4 \{F4}
F5 \{F5}
F6 \{F6}
F7 \{F7}
F8 \{F8}
F9 \{F9}
F10 \{F10}
F11 \{F11}
F12 \{F12}
F13 \{F13}
F14 \{F14}
F15 \{F15}
F16 \{F16}

Fig 3: Mouse Click

 
Code What it does
If you enter *MC(x,y) in a cell, it tells FDL to simulate a mouse click in the target
application while loading.
*MC(x,y)  
 X means X - Screen Coordinate and Y means Y - Screen Coordinate.
OR  
For example if you enter *MC(430,240) then FDL will simulate a mouse left click on
*ML(x,y) the screen at the 430,240 coordinate while loading.
 
To capture exact coordinates please use our Get Screen Coordinate Tool by clicking on
the Tools Menu. 
 
f you enter *MR(x,y) in a cell, it tells FDL to simulate a Right mouse click in the target
application while loading.
 
*MR(x,y)  X means X - Screen Coordinate and Y means Y - Screen Coordinate.
 
For example if you enter *MR(530,440) then FDL will simulate a mouse Right click
on the screen at the 530,440 coordinate while loading.