Setting Up Oracle Forms Record and Playback in Oracle Apps

DataLoader loads data into any application running in Windows, and contains extra functionality for loading data and setup into Oracle Applications. Data can be loaded using DataLoader in two ways - DataLoad Classic or DataLoad Professional.

DataLoad Classic is the free version of DataLoad while Professional is a commercial product. If DataLoad Classic provides all the functionality you require then you can freely use it for as long as you want without any restrictions. However, if you want faster, more reliable loads or product support then you have to use DataLoad Professional. DataLoad Professional provides the Forms Playback functionality for very fast and reliable loading of data. It also includes Load Control to make Macro loads faster and more reliable.

For using Dataloader Professional for Fast and Accurate data loading into Oracle Applications, we need two separate Oracle Applications IDs to be setup in Oracle Applications. They are –

Ø Record ID – Record the Data loading with sample data

Ø Play ID – Loading of actual data using the Recording

Setup

Following Application and DBA setup is required in order Data Loader to work with RECORD and PLAY ids.

Application Side Setup

Ø Create two Oracle Application IDs for a User who already has an ID in Oracle Apps. For Example, if user “ZA92” is already setup as an Oracle Applications user then create two new IDs ZA92RECORD/ZA92REC and ZA92PLAY. Responsibility setup for these IDs should be same as user ZA92 (or it should be given all responsibilities which would be used for data loading)

v For the RECORD id the ID may be like ZA92RECORD or ZA92REC

v For the PLAY id the ID would be ZA92PLAY

Ø Need to setup Profile Option - ICX: Form Launcher for these two IDs as per the details given below

RECORD ID – ZA92RECORD

Site Level Value à http://<Server.Domain>:<Port>/dev60cgi/f60cgi

http://glwuat.test:8001/dev60cgi/f60cgi (Example)

User Level Value à http://<Server.Domain>:<Port>/dev60cgi/f60cgi?record=<ORACLE_APPS_ID>record<INSTANCE_SHORT_NAME>.fld

http://glwuat.test:8001/dev60cgi/f60cgi?record=za92recordPREP.fld (Example)

PLAY ID – ZA92PLAY

Site Level Value à http://<Server.Domain>:<Port>/dev60cgi/f60cgi

http://glwuat.test:8001/dev60cgi/f60cgi (Example)

User Level Value à http://<Server.Domain>:<Port>/dev60cgi/f60cgi?record=<ORACLE_APPS_USER_ID>reclogPROD.fld%20play=<ORACLE_APPS_USER_ID>player< INSTANCE_SHORT_NAME >.fld

http://glwuat.test:8001/dev60cgi/f60cgi?record=za92reclogPREP.fld%20play=za92playerPREP.fld (Example)

DBA Setup

DBAs need to create a “/tmp” folder in proper location in the Application Server. This folder would be used to store the Data Loader files (.fld) both RECORD and PLAY.

Change the default value for $FORMS60_TRACE_PATH to /tmp

For Oracle E-Business 11.5.9 with Oracle Forms prior to 6.0.8.25.2, the file $OA_HTML/bin/appsweb.cfg (or appsweb_[ORACLE_SID]_[HOSTNAME].cfg if present) must be edited. At the very end of the file insert the highlighted lines before the "End customizations" message as shown below:

[playback]

code=oracle.forms.engine.MainRT

;# ********************

;# End customizations

;# ********************