JPublisher Wrapper Details

After JPublisher executes the command successfully, two PL/SQL files are generated. One is the wrapper file which exposes data structure types and stored procedures for the execution through JDBC. The other file with the drop suffix contains scripts used to undo the changes of the wrapper, and makes the database return to its prior state.

For example, the files generated by JPublisher by executing the command in Running JPublisher are as follows:

BOM_BO_PUB.sql
BOM_BO_PUB_drop.sql

Inspection of the generated wrapper file shows that the package types are mapped to general SQL types, and the package procedures and functions are mapped to identical procedures in the generated wrapper package. The Oracle E-Business Suite apps user or users with equivalent privileges can access the SQL type and wrapper package.

You can edit the wrapper file to restrict the access to certain procedures and types so that the entire package content might not be exposed. However, this operation requires extensive knowledge of PL/SQL, the API package, and API and type relationships for the particular API that is being configured. It is good practice to run the unmodified file in its entirety.

When using an SQL execution tool such as Oracle SQL Developer, you can use the plug-in user if privileges to the package have been granted to the plug-in user or simply use the apps user, and execute this script.

Note: The execution of the wrapper files might require a SQL tool that can accommodate very long individual lines. It is good practice to use Oracle SQL Developer to execute this script, because SQL*Plus might encounter problems when it executes lines that are very long, even after you increase the line size.