Search Results oa_java

Overview

APPS.FND_HELP_BUILDER is a server-side PL/SQL package that provides the launch mechanism for the Oracle E-Business Suite Help System Builder, a Java-based administrative tool used to create and maintain hierarchical help content in EBS 12.1.1 and 12.2.2. The package body is a thin, single-purpose wrapper: it does not itself manage help data, but instead assembles the runtime parameters, JAR archive list, and classpath required to instantiate the HelpTreeViewer Java applet through the framework's generic applet launcher. Application developers and system administrators use this builder to define and reorganize the help hierarchy that end users see when they open context-sensitive help from forms. The package header comment identifies the launch entry point as the "HTML page that loads the Help System Builder," confirming its role as the bridge between the EBS middle tier and the client-side Java help authoring tool.

Key Procedures and Functions

• LAUNCH — The single documented procedure in the package, and the only public entry point. It invokes fnd_applet_launcher.launch to instantiate the HelpTreeViewer applet, passing a fixed applet class path and a comma-separated archive list of core FND Java libraries. It also builds the applet's user arguments, including the web agent URL, web server, database identifier, host, port, language, and the help tree data source class (oracle.apps.fnd.help.server.HelpServer). The procedure accepts optional parameters that allow the caller to scoped the builder to a particular node of the help tree, including a customization level and root parent/node application and key values, enabling targeted rather than global editing of help hierarchies.

Tables Accessed

Per the documented package metadata, no tables are referenced directly through APPS synonyms. The package does not perform SQL against help content tables. Its data access is entirely indirect: help hierarchy data is retrieved at runtime by the Java HelpServer class through the web agent URL that LAUNCH constructs, and configuration values are obtained through FND profile and configuration APIs (such as fnd_profile.value for TCF:HOST and TCF:PORT, and fnd_web_config calls for the web server and database identifier) rather than through direct table joins. Session language is sourced from the userenv('LANG') built-in.

Usage Notes

FND_HELP_BUILDER.LAUNCH is not intended for direct invocation from custom PL/SQL. It is invoked from the EBS Help menu or from an administrative HTML page that triggers the applet launch, typically through the FND framework's launcher infrastructure. The archive list it assembles references the /OA_JAVA path, which is why the term "oa_java" is associated with this object in search behavior: the JAR files under /OA_JAVA/oracle/apps/fnd/jar/ (including fndhelpc.jar, fndaol.jar, and fndforms.jar) must be available on the web server for the Help System Builder to load. Because the procedure depends on profile options and web configuration values, it only functions correctly in an environment where the standard EBS middle-tier services and Java classpath are properly deployed. The optional parameters support custom scoping when embedding the builder in a specific application context, but the standard framework invocation relies on the default values.