FNDLOAD and WFLOAD

FNDLOAD

These are the extensive list which can be done through FNDLOAD.

  • Concurrent Programs, Executables
  • Request Groups, Request Sets
  • Profile Options
  • Key and Descriptive Flexfields
  • Menus and Responsibilities
  • Forms and Form Functions/Personalizations
  • Attachments
  • Messages
  • Value Sets and Values
  • Lookup Types
  • User Responsibilities
  • Printer Definitions
  • FND Dictionary
  • Help Configuration
  • Document Sequences
  • Alerts
  • Concurrent Manager Schedules
  • AME Setups
  • Web ADI
  • Post Accounting Programs SLA

The FNDLOAD: Concurrent Program – FNDLOAD can be executed as a concurrent program.

Some advantages when using FNDLOAD:

  • Because downloaded data is stored in a text file, version administration is possible.
  • There is nothing to worry to go to purchase because Investment = 0$.
  • No learning curve. this is relief for developer and dba.
  • Fully supported and recommended by Oracle.
  • Capture the migrations in a file and use it during installations, clones etc. to migrate in batch.
  • Pin-point when something happened and where (database) easily.
  • Your AOL data migration process is now simplified and streamlined goal attained.

Some disadvantages when using FNDLOAD:

  • Applications patching mechanisms use FNDLOAD heavily possibility of negative impact is not zero.
  • UPLOAD_MODE=REPLACE only for menus.
  • No validation against migrating database/instance sensitive data.

Syntax:

The Generic Loader is a concurrent program named FNDLOAD. The concurrent executable takes the following parameters:

FNDLOAD apps/pwd 0 Y mode configfile datafile entity [ param …]
where

<apps/pwd>
The APPS schema and password in the form username/password[@connect_string]. If
connect_string is omitted, it is taken in a platform-specific manner from the environment
using the name TWO_TASK.

< 0 Y >
Concurrent program flags.

mode
UPLOAD or DOWNLOAD. UPLOAD causes the datafile to be uploaded to the database. DOWNLOAD causes the loader to fetch rows and write them to the datafile.

<configure>
The configuration file to use (usually with a suffix of .lct, but not enforced or supplied by the loader).

<datafile>
The data file to write (usually with a suffix of .ldt, but not enforced or supplied by the loader). If the data file already exists, it will be overwritten.

<entity>
The entity(ies) to upload or download. When uploading, always upload all entities, so specify a “-” to upload all entities.

< [param] >
Zero or more additional parameters are used to provide bind values in the access SQL (both UPLOAD and DOWNLOAD). Each parameter is in the form NAME=VALUE. NAME should not conflict with an attribute name for the entities being loaded.

Modes of Operation
This is important because it would drive the whole flow, and it always be either Upload or Download.

Example of download
FNDLOAD apps/pwd 0 Y DOWNLOAD ${FND_TOP}/patch/115/import/afcpprog.lct myfile.ldt \ PROGRAM CONCURRENT_PROGRAM_NAME= concurrent_program_short_name> APPLICATION_SHORT_NAME=<application_short_name>

Example of Upload
FNDLOAD apps/pwd 0 Y UPLOAD ${FND_TOP}/patch/115/import/afcpprog.lct myfile.ldt – CUSTOM_MODE=FORCE undocumented parameter

What are FNDLOAD Options?

  • Application level OR single entity level download
  • (Example) Download all the profile options of Inventory or just the INV: Default Primary UOM
  • Entire OR Partial upload of a data file
  • (Example) Upload the entire myfile.ldt or just a single entity indicated by – and mode UPLOAD or  UPLOAD_PARTIAL
  • Entity name required for UPLOAD_PARTIAL mode
  • Custom mode force update
  • To override Oracle’s upload algorithm and update the custom AOL data regardless, use CUSTOM_MODE= FORCE
  • UPLOAD_MODE= REPLACE (only for menus)
  • Support for NLS uploads
  • NLS data uploads for translated columns are supported, use UPLOAD_MODE= NLS

Where is Configuration File Located
By default Oracle delivers most of configuration files that can be used to download certain entities.

  • Configuration files with extension .lct
  • On Unix – all the configuration files are in $FND_TOP/patch/115/import directory
  • On Unix Oracle also places the original configuration files in $FND_TOP/admin/import directory
  • Data files with extension .ldt

FNDLOAD File Structure

  •   The configuration files (.lct) are delivered and maintained by Oracle.
  •   It has entity definitions, parent-child relationships and user input parameters identified by :NAME.
  • Downloading a parent automatically downloads all children – (Example) Concurrent Program download.
  • The data files (.ldt) have both entity definition and the data.
  • It also shows the version and the location of the configuration file (.lct) that was used.
  • Without the configuration file, a data file is useless.
  • Without the data file, a configuration file is meaningless.

FNDLOAD Files

  • Key files: .lct and .ldt
  • FNDLOAD must be run as the apps user not as applsys or any other user, otherwise an Ora-6550 error will be received.
  • Both are easily readable, editable and portable.
  • Do not modify Oracle .lct files.
  • Use a favorite editor to manipulate only the .ldt files but be cautious about data type, length, delimiter placements etc.
  • Use the log file outputs or .ldt file contents creatively for quick file comparisons and answer questions as: (Why can this be accessed? What is that profile option name, value and level? What is the value set used for that DFF segment attribute10 etc.)
  • Partial string searches (which value set has Priority something in its where clause, etc)

Examples on FNDLOAD

Related posts:

Leave a Reply