Release Notes: This release adds support for Java 7 and Windows 8, adds a function to download/upload a Workflow Definition, adds redirection of all log files to the log directory, changes "Reduce the loadable objects" to FND-related objects only, skips the DownloadModule screen (since FND is the only choice), fixes a NullPointerException bug which occurred when the download directory was invalid, and fixes incorrect TNS names used if FNDLOAD has been run multiple times.
Release Notes: FNDLOADER.xml was reworked and a Module Selection Screen was added for users to select which module of an object to download. This change allows end users to add any business object to the FNDLOADER.xml file for upload or download (Oracle EBS has hundreds of definition files, and this program only includes the most common objects). The code base was changed to use CALLA framework 1.0.
Release Notes: This is a feature complete release in which all the functionality of Oracle FNDLOAD is exposed. It adds a feature to download and upload NLS translations. It adds a feature to record answers and playback in text mode (silent operation). It adds a feature to create an Ant task to execute playback and automate FNDLOAD operations.
Release Notes: In the stand-alone version, the directory structure was changed to separate 11i and R12 files, and version-specific FNDLOAD and Oracle binaries are used. In the stand-alone and server addon version, instance information is stored in INSTANCE.XML, taking away from FNDLOADER.XML. In the CALLA engine, Question and Choices can be displayed in different colors.
Release Notes: This release has been split into two editions: Stand-alone Edition and Server Add-on Edition. JRE 1.5 or higher is required. It uses the SYMPLiK CALLA engine for the interactive wizard in the console and GUI. All the questions have been reworked to use the new engine. The standalone version does not depend on any pre-installed Oracle program. This release uses tnsnames.ora for database instance lookup.
Release Notes: Minor security enhancements were made. You no longer need to put the plain text APPS password in the config file. It will be stored as an encrypted hash in the config file after the first successful login. If the password is incorrect (e.g. you transfer the config files from one instance to another), you will be asked to enter it with a masked echo showing in the console. The program will exit if the password is entered incorrectly three times.
Release Notes: Initial release.