Oracle Forms 12c is the first version of Forms to be supported with the new Java Web Start functionality. This allows you to launch your Forms application using any certified browser including Google Chrome. PITSS.CON can also be configured to run with Java Web Start. To implement this functionality with PITSS.CON, you will need to run these steps:

  1. Open up formsweb.cfg located in %DOMAIN_HOME%\config\fmwconfig\servers\WLS_FORMS\applications\formsapp_12.2.1\config.
  2. Within your config section(s) for PITSS.CON, add the following parameters inside it:
    1. basejnlp=webutil.jnlp
  3. Save and close the file.
  4. Go to %ORACLE_HOME%\forms\java and open up extensions.jnlp in a text editor (make a backup of this file first).
  5. Look for <!– <jar href=”jacob.jar”/ –>. Uncomment this line. It should look like this: <jar href=”jacob.jar”/>
    1. NOTE: This fixes a Forms startup issue when using Java Web Start. Source: Oracle Support note 2083540.1
  6. Add the following lines for each of the PITSS.CON jar files (this will allow all jar files for PITSS.CON to be used while running Java Web Start):
    1. <jar href=”/forms/PitssJava/pitssicon.jar”/>
      <jar href=”/forms/PitssJava/pitssE.jar”/>
      <jar href=”/forms/PitssJava/pitssH.jar”/>
      <jar href=”/forms/PitssJava/pitssFS.jar”/>
      <jar href=”/forms/PitssJava/pitssCFS.jar”/>
      <jar href=”/forms/PitssJava/pitssLE.jar”/>
      <jar href=”/forms/PitssJava/FileLastModified.jar”/>
      <jar href=”/forms/PitssJava/pitss_calendar.jar”/>
      <jar href=”/forms/PitssJava/pitssXSL.jar”/>
      <jar href=”/forms/PitssJava/classes12.jar”/>
      <jar href=”/forms/PitssJava/PitssFileUtils.jar”/>
      <jar href=”/forms/PitssJava/BarChart.jar”/>
      <jar href=”/forms/PitssJava/colorpicker.jar”/>
      <jar href=”/forms/PitssJava/jcommon-1.0.16.jar”/>
      <jar href=”/forms/PitssJava/jfreechart.jar”/>
      <jar href=”/forms/PitssJava/PieChart.jar”/>
      <jar href=”/forms/PitssJava/OGD.jar”/>
    2. The file should look like this:
    3. Java Web Start PITSSCON
  7. Save and close the file.
  8. Clear your Java cache on your PC where you plan to launch PITSS.CON.
  9. Launch PITSS.CON.

After completing the steps above, you should be able to use PITSS.CON using Java Web Start.

There is a known issue where running tree reports from PITSS.CON 15.4.2 installed in a Forms 12c environment where the error “Error when running report” appears when attempting to create a PDF tree report. This happens to not be a bug with the latest PITSS.CON release. To get tree reports to generate in PITSS.CON, a new configuration is required in Forms and Reports 12c to run PITSS.CON tree reports in 12c.

First, make sure that all environment files (.env) have the new COMPONENT_CONFIG_PATH environment variable set up. For more information, you may check out our knowledge base article on setting up this environment variable here:

Once the variable is set up, you will also need to set up two environment variables for your Reports 12c environment. This should be set up in rwserver.conf. If you are using a standalone reports server, the file is located in %DOMAIN_HOME%\config\fmwconfig\components\ReportsServerComponent\%RptSvr%; if you are using the in-process reports server, the file is located in %DOMAIN_HOME%\config\fmwconfig\servers\WLS_REPORTS\applications\reports_12.2.1\configuration. Before modifying this file, please make a backup. Inside the file after the <engine> tag containing the id=”rwEng” line, add the following lines (you may use the screenshot below as a guide):

<environment id=”pitss”>
<envVariable name=”REPORTS_PATH” value=”C:\pitsscon\tool;c:\pitsscon\%PITSS_USER%\rdf;c:\pitsscon\%PITSS_USER%\olb;” />
<envVariable name=”TNS_ADMIN” value=”%DOMAIN_HOME%\config\fmwconfig”/>

NOTE: This assumes that PITSS.CON is installed in C:\pitsscon as it uses paths such as C:\pitsscon\tool and C:\pitsscon\%PITSS_USER%\rdf. Also, %PITSS_USER% should be your PITSS.CON user. If you have more than one PITSS.CON user, please specify the RDF and OLB paths for all PITSS.CON users here. For the TNS_ADMIN variable, the fully-written path for %DOMAIN_HOME%\config\fmwconfig should be filled inside the value attribute.

rwserver.conf for PITSS.CON

After the update is made, save and close the file. Once the file is updated, you will need to restart your reports server (the standalone reports server if you configured the standalone reports server or WLS_REPORTS if you configured the in-process reports server).

After restarting your reports server, you should be able to run a tree report in PITSS.CON.

Updated: 3/23/16

In PITSS.CON 15.3.1, there is a known bug where if you check the Module Summary for a particular module (form, menu, library, etc.), the right column will be blank:


The Module Summary can be accessed by going into the Application Analysis module in PITSS.CON and right-clicking on a form to select “Module Summary”. NOTE: The application must be parsed first.

A bug fix is available for this problem. The newest version of PITSS.CON, version 15.4.2, has this bug already patched. Upgrading PITSS.CON 15.4.2 will fix this problem (version 15.4.1 has this problem still). Please contact PITSS Support for how you can upgrade to the latest version of PITSS.CON. However, if you cannot upgrade right away, you may also contact PITSS Support for the SQL script to patch the PITSS.CON repository. The file is called patch_290915.wrp. Once you have received it, you may follow these steps to apply the patch:

  1. Download the patch to the PITSS.CON server or client.
  2. Log into SQLPLUS as each of your PITSS.CON users (except for MIG). NOTE: Please be in the same directory as the patch when launching SQLPLUS.
  3. Run the command to install the patch: start ‘patch_290915.wrp’
  4. Log out of the PITSS.CON user in SQLPLUS and log into your other PITSS.CON users and repeat the process.
  5. Log out of PITSS.CON and log back in.

After completing the steps above, everything should work normally:

AA works

Even when WebUtil and Jacob have been fully configured in the PITSS.CON server environment as documented in, there have been known issues where users (on the first use of PITSS.CON) are unable to log in due to the following error:

NoClassDefFoundError – com/jacob/com/ComFailException

No Jacob

The reason for this error is because the Java cache may be interfering with properly finding the Java classes associated with jacob.jar. Clearing the Java cache should fix the problem:

  1. Open up the Control Panel on the end user’s PC
  2. Go to All Control Panel Items and click “Java”
  3. With the General tab highlighted in the Java Control Panel, click “Settings…”Java Control Panel
  4. Click “Delete Files…”Delete Temporary Java Files
  5. In the new pop-up window, have only “Trace and Log Files” and “Cached Applications and Applets” selected and click “OK”.Clearing Java cache
  6. After the window closes, click “OK” twice to close all windows in the Java Control Panel.
  7. Close all web browser windows and try launching PITSS.CON.

After completing the steps above, PITSS.CON should launch without any problems.

When running a project for upgrading forms in PITSS.CON such as the project to replace the text_io function with webutil.client_text_io, if you happen to encounter the following error:

Search&Replace Error : ORA-06550: line 1, column 7:

PLS-00306: wrong number or types of arguments in call to ‘SYNCRN’

ORA-06550: line 1, column 7:

PL/SQL: Statement ignored.


There is a possibility that you might have encountered a bug with the Oracle Database especially if the database version is It has also been noted that this error also happens when you attempt to delete a form from Module Handling. There are two solutions which can be done to fix the problem:

1. Apply Oracle Patch 17501296 to the Oracle Database (version only). More information is provided in Oracle Support note 1586704.1.

2. Re-create the CTXSYS.SYNCRN procedure. The full SQL commands can be found in Oracle Support note 1586704.1.

After applying either one of the two solutions, the problem should no longer occur.

Source: Oracle Support note 1586704.1

PITSS.CON users can be reinstalled when needed to whether the user needs to be installed a different group or if installing in a new PC. Normally PITSS.CON users can be reinstalled in an existing group without any issues. However, there can be a time where the following error is presented when a PITSS.CON user is being reinstalled (or even installed) in an existing group:

“Invalid database! Does not fit with Group “GROUP_NAME” connection! Logon denied!


The reason is because the group which the PITSS.CON user is being installed into has an application connect string different from the default “system/*@DB” connect string. You will need to type in the full application database connect string used by the GROUP in the App Connect String field (username/password@DB). If you are unsure what the application connect string is, you can find this out with the MIG user:

1. Log into PITSS.CON with the MIG user.

2. Go to User Access

3. Click on the group name you are installing the new PITSS.CON user.

4. If you look on the right side near the top, you will see the application connect string being used by the group. For security reasons, the password will not be shown here. If you are unsure what the user’s password is, please consult your DBA.

After the App Connect String field is filled in, the (re)installation will proceed like normal.

It is recommended that all PITSS.CON users have an unlimited quota to the tablespace which each PITSS.CON belongs to. If any of the PITSS.CON users do not have an unlimited quota to the tablespace, the following errors could be presented:Insert…ORA-01536: space quota exceeded for tablespace… fix this, all PITSS.CON users including the MIG user should have the following database privilege granted:grant UNLIMITED TABLESPACE to USER;ORalter user USER quota unlimited on PITSS_TABLESPACE;After applying one of the grants above on each PITSS.CON user (including MIG), the error should disappear.Source: Oracle Support note 1084014.6

IMPORTANT: As of September 4, 2015, NPAPI has been completely removed from Google Chrome in version 45. Due to this, Oracle Forms will no longer work in Chrome starting with Chrome version 45. The solution in this article below will no longer work. The only alternative is to use another supported Web browser such as Internet Explorer, Mozilla Firefox, or Safari.

Recently, Google has removed NPAPI support from Google Chrome, one of the supported Web browsers which can be used to run Oracle Forms or any application requiring the use of a Java Runtime Environment (JRE).  Starting with the latest Google Chrome update (released in April 2015), version 42, there is a possibility where all applications such as Oracle Forms (includes PITSS.CON) which rely on JREs will no longer work in Google Chrome. You may encounter an error such as:

“This plug-in is not supported.”


NPAPI is used to support non-Internet Explorer browsers with different plug-ins including Java (JRE). With Google Chrome no longer supporting NPAPI starting April 2015, NPAPI is now disabled by default. There are different workarounds which can be done to get Forms (or other applications using a JRE) to work in Chrome:

1. Manually enable NPAPI in Chrome:

a. In the URL in Chrome, type in: chrome://flags/#enable-npapi

b. An entry, “Enable NPAPI”, should appear. Click “Enable”. WARNING: Please be careful when enabling anything in this page. Neither PITSS nor Google will not be held responsible for anything that is enabled by accident. Before clicking to Enable NPAPI, please read and understand the warning message printed at the very top of the page (or you may read the warning message in the screenshot below as it is a snapshot of it).



c. At the bottom of the page, you will see a “Relaunch Now” button appear. This is necessary to activate the change just made. Click “Relaunch Now”.


d. Google Chrome will relaunch. After applying the steps above, any application (including Oracle Forms and PITSS.CON) will be able to use the JRE in Google Chrome.

2. Use other Web browsers supported by Oracle per the certification matrix as they have not disabled NPAPI:

a. Internet Explorer

b. Mozilla Firefox

c. Safari

NOTE: Sometime in September 2015 according to the Chromium Blog,, NPAPI will be permanently removed and solution #1 above will no longer work then. Oracle is aware of this issue. Solution #2 will still work even when NPAPI is completely removed from Chrome in September 2015.

Source: (Chromium Blog for Google Chrome)

Source: (Oracle’s explanation regarding NPAPI support with Chrome)

In PITSS.CON 12.3.1 and older, there is a button in Application Analysis called “Custom Reports” which will take you to a page to do an analysis of dead code in your Forms application. This is a button which could be selected after parsing the application.


Once the Custom Reports module (also shows as “Dead Code Analyse” in PITSS.CON), if you click the “Run Task” button in this window, there is a possibility that the following error is produced:

“Error: ORA-01422: exact fetch returns more than requested number of rows”

NOTE: This does not happen with all PITSS.CON installations.

This was actually another method of performing an Unused Objects Analysis. To perform an Unused Objects Analysis (same as performing the dead code analysis), go to Application Engineering in the main menu and go to “Unused Objects Analysis”. Inside this module, you can perform the analysis to check for all of the unused objects in your application.

NOTE: Starting with PITSS.CON 15.1.1, the button in Application Analysis has been removed.

GraphViz is a great third-party tool which can be used to generate graphs. By default, if you generate a graph from PITSS.CON (such as from the “Generate Forms Flow as DOT file” button in ADF Assistant) as a DOT file, it will create the DOT file code in the PITSS.CON Editor:


The code can be then copied into GraphViz and a graph can be generated.

However, you can configure PITSS.CON to automatically create a graph for you upon request. You can configure this with the steps below:


1. PITSS.CON must be installed and configured

2. GraphViz must be downloaded from (be sure to accept the license agreement before downloading and installing the product) and installed in the machine where PITSS.CON is installed.


1. If PITSS.CON is currently open, please log out of PITSS.CON.

2. Open up pitsscon.env (or the env file associated with your PITSS.CON user)

3. In the PATH environment variable, add the following entry to the end of the PATH:

;C:\PROGRA~2\Graphviz2.38\bin (NOTE: The path may be different if you installed GraphViz in a different location)


4. Save and close the file.

5. Repeat steps 2-4 for any other PITSS.CON-related env files.

After applying the steps above, if you attempt to generate a graph from modules such as ADF Assistant or Systems Analysis (inside Application Engineering), a graph will automatically be created in a separate tab or window (depending on your Web browser configuration).


This will also prevent end users from having to install GraphViz on their local machines as it will be used from the installation on the server.