Create a Load - 1
Create a Load - 2
The "Rules"
Editing a Load
Running the Load
Testing the Load
Character Sets

User Guide Home
DataLoad Home


DataLoad User Guide
Please read and apply the relevant section on this page before using forms playback.
This page is regularly updated, please check the web site version for latest changes.

Oracle Forms Playback Setup

Oracle E-Business Suite R12

DataLoad Professional's Forms Playback loads have been tested with R12 forms working in both Servlet (HTTP, the default) and Socket mode and both are certified for use with DataLoad. The default setup detailed below limits the number of screen updates shown during the load to maximise performance and stability. Full screen updates can be turned on by following the instructions in the section "Enabling Full Screen Updates" below, however these are far more likely to cause the Oracle Forms client to hang (this is an Oracle issue) although the load continues to run in the background.

R12 Oracle E-Business Suite will only record and play files in a single directory. That directory is held in the $FORMS_TRACE_DIR environment variable and by default it is the following location on the application server:

$INST_TOP/logs/ora/[Oracle Forms Version]/forms

When you record a file it will be created in that location and your playback file must later be copied to that directory. It is possible to use an alternative directory for your record and playback files - please click here for more details.

The Oracle E-Business Suite profile option "ICX: Forms Launcher" must be set for your record and playback users at user level. This profile option will contain an entry similar to the following at Site level:-


This value should be copied from Site level to User level for the user you are configuring. Next, edit the profile option to switch on either recording or playback.

To record a Forms Playback file the following should be added to the end of the recording user's profile option value:


That will cause Oracle to record to a file named record.fld. The file name may be changed but a directory path must not be included. A dummy playback file must also be included because R12 will not record a file without a playback file also existing. That is the noplay.fld file.

Next, create the following file, which is the dummy playback file:


Edit that file in any text editor and add the following line:


The setup for recording files is now complete. To playback a file add the following to the end of the playback user's ICX: Forms Launcher profile value at user level:


The file names may be changed if you wish but in this example you will playback from play.fld and an audit log of the playback session would be recorded to reclog.fld. The playback configuration is now complete.

R12 Hints - Please Read

Hint The order of the parameters in the profile values is critical, ie "record=" must be used and it must appear before "play=". Furthermore, these two parameters must be separated by "%20" and nothing else.

Hint Directory paths must not be included in the record= and play= parameters. In this version of Oracle the files can only be located in one directory and specifying a directory path can stop record and playback from working.

Hint The record= and play= file names in the playback profile option must be different otherwise the playback file is overwritten with the log file when the load starts and the load immediately stops.

Hint In the playback examples above the 'record=' parameter is still used. This is essential for playback to work without having to change some of the server based setup files. However, it also has two other benefits. First, a log of what was loaded will be recorded and that can be validated by opening the recorded file in DataLoad after the load. Second, the Oracle Forms have been found to be more reliable and stable during playback if they record at the same time as playing a session back.

Hint Profile option values are cached in R12, which means your configuration may not immediately work as expected. Please see the notes about profile option caching on this page. This is espceially important if your profile values are frequently changed, for example if you use a single user account for record, playback and your normal work.

Hint We recommend the latest Oracle Forms focus patch is applied to maximise forms stability. More details can be found here.

Enabling Full Screen Updates

The default R12 setup described above limits the screen updates that are displayed during playback, however the main Oracle window and status bar are displayed and updated during the load; all screen updates work as normal after the load. This approach improves Oracle's performance and stability. However, full screen updates can be enabled using these steps.

The file referenced by the following environment variable must be edited on the application server:


Add the following lines to the end of this file:


Finally, to use that configuration during playback the text "&config=playback" must be added to the end of the ICX: Forms Launcher profile option value at user level for the playback user. That profile option value will now look similar to the following (beginning of value removed for clarity):