The significance of many problems lessens over time, so procrastination has its place as a stress management technique. Unfortunately, putting off your EBS end-user migration from Oracle JInitiator to the native Sun Java plug-in doesn't fall into that
category. We are down to the last grains of sand in this particular hourglass.

Error Correction Support (ECS) for JInitiator 1.1.8 will end on December 31, 2008. In other words, the Oracle Forms group will no longer issue bug fixes for the JInitiator 1.1.8 codeline as of tomorrow.

Error Correction Support for JInitiator 1.3 for E-Business Suite Release 11i customers will end on July 31, 2009.

Why Did We Once Need JInitiator At All?

Some additional background might be useful here: Oracle JInitiator was originally released as a licenced version of Sun's Java client back when specific features were required to support Oracle Forms. This was particularly necessary for E-Business
Suite Forms-based functionality, since the E-Business Suite pushed the envelope of what Forms and Java could do collectively from a user interface perspective.

Sun has since incorporated all of the enhancements needed to support Oracle Forms into their native Sun Java plug-in. This eliminates the need for Oracle to package its own Java client just for running Oracle Forms-based applications.

What Are the Support Implications for JInitiator Users?

Here's what you can expect if you log an Oracle E-Business Suite Release 11i service request against JInitiator after the respective dates shown above:

Oracle Support will help you diagnose and isolate the root cause of any compatibility issues between JInitiator and the E-Business Suite.

If there's a workaround or an existing Forms or JInitiator patch, Oracle Support will help you obtain the fix.

If the issue requires a new Forms patch and can be reproduced using the native Sun JRE plug-in, a new bug will be logged against Oracle Forms.

If the issue cannot be reproduced with the native Sun JRE client, no new Forms or JInitiator bugs will be logged.

What Do You Do Now?

If you haven't already started migrating your end-users to the native Sun JRE plug-in, I'd strongly recommend that you begin this process immediately.

Apps 11i is certified with the native Sun Java (JRE) plug-in. You can use any JRE release from 1.5.0_13 and higher, or 1.6.0_03 and higher. Your end-users can
upgrade their JRE clients whenever Sun releases a new JRE release on either codelines -- without waiting for Oracle to certify these new JRE plug-ins with EBS 11i.

Why Choose the native Sun JRE over JInitiator 1.3?

Upgrading your Apps 11i end-users to the native Sun JRE directly will be less time-consuming and disruptive than upgrading them first from JInitiator 1.1.8 to 1.3 and then upgrading them again to the native Sun Java client before the July 2009 deadline.

The elimination of Oracle JInitiator simplifies your desktop administration environment. Apps DBAs who have migrated their users to the native Sun JRE no longer have to struggle with compatibility and coexistence problems between JInitiator and other
Java runtime clients on the same desktop.

Which JRE Versions Are Certified With Which Browsers?

This depends on your Windows operating version and the browser that your firm has deployed. Various combinations of Windows XP, Windows Vista, Microsoft Internet Explorer (IE) 6 and 7, and Firefox are now certified with JRE 1.5 and 1.6. To review the new
minimum certification levels, see:

We recently migrated to JRE from jinitiator 1.3.
Here are our experiences:

Installing the JRE plugin requires user to be at least "Power User". Many of our users are not power users.
So, this requires some kind of automated pushing the jre software to users.
This is the same requirement for jinitiator too.
The issue gets complex due to the need to maintain the JRE up to date and keep the user's desktop secure. This requires uninstalling the old versions and installing new versions.
Unfortunately, we don't have any automated tools to do this at this time. Going forward, we are trying to use MS' System Management Server to automate that.

What are your thoughts on this and could you suggest any tools that could help with that?

Congratulations on your migration, and thanks for sharing your experiences with our readers.

Keeping JRE up-to-date is like any other update to software on your end-users' desktops. I would presume that you have to periodically update your end-users' antivirus scanners, malware protection, browsers, Windows security patches, and so on.

I'd infer from your email address that your organization is part of a larger statewide organization that has standardized tools for deploying desktop updates. It might be worthwhile contacting your peers in your sister organizations at the state level to see whether they have negotiated site licences for desktop administration tools like MS SMS (which is one of the most commonly-used tools for Windows desktops, in my experience).

There are many other desktop administration tools, of course. Unfortunately, I have limited visibility into this space and lack sufficient hands-on experience to recommend one tool over another. Other readers might chime in with their experiences, if we're lucky.

We recently migrated to Oracle version 12 and have many of our users experiencing loss of focus on the forms (ie, cannot click on fields or tab to fields). Can you tell what version of Java we should have installed on workstations and/or how could we resolve this issue.

You should ensure that you have JRE 1.6.0_03 -- at minimum -- installed on your desktops. If possible, I'd recommend installing the latest 1.6.x version available from Sun. Instructions are linked from this article:

We're seeing persistent although intermittent and seemingly random crashes of the client forms sessions. The forms process is still there on the server after the crash (for about 10-15mins when it get's cleaned up), but the java and IE session seemingly crashes. No focus in the form, console stops logging and no buttons click etc. No error messages reported on the client. Users have to restart their browsers to log back in (IE6 and IE7)

Nothing to indicate what the issue might be in the java console and I've not been able to find anything in any of the server side logs that I've looked at.

I'll most likely raise an SR in the morning, but wondered if you'd come across this before, and whether there are any compatibility issues with having J2sdk 1.4.2 on the server and using jre 1.6.0 plugin on the client?

I'm sorry to hear that you're encountering this issue. There should be no issues with having J2SE 1.4.2 on the application tier and JRE 1.6.0 on the client. The JRE clients should be backwards-compatible with earlier JDK/J2SE releases.

However, you may be encountering a variant of the more-common mouse focus issues that a few others have reported. This may be due to the Forms 6i patchset level on your EBS 11i application tier.

Support has just published an excellent diagnostic note with tips on troubleshooting these types of issues. See:

I hope the latest update on your SR has resolved your question, but please update the SR if you need to discuss further.

The certdb.txt file in Jinitiator stores the CA Certificates, so the equivilent in JRE is the "cacerts" file (which stores the seeded certificates) Any user accepted certificates are stored in seperate files in the users home directory (for example "trusted.cacerts")

Unless you need to work with unrecognized Certificate Authorities (or Client Certificates) you would not normally need to worry about these files as such

You can read more about JRE Plugin security at http://java.sun.com/javase/6/docs/technotes/guides/deployment/deployment-guide/security.html You may also find the information about "keytool" useful, which is the java tool provided to manage certificate stores. This is documented at http://java.sun.com/javase/6/docs/technotes/tools/windows/keytool.html

Just wondering if anyone has encountered the problem we are not experiencing.

We have multiple versions of Sun Java installed on our PC's and the server set to tell the client to use at leaset use 1.4.2_06. For some reason the system is connecting to Discoverer exceptionally slow (several minutes) and opens a dialog box that says 'The application requires an earlier version of Java. Do you want to continue? The required version of Java, 1.4.2_13, is not the latest and may not contain the latest security updates.' When we click 'Run' to the above message it launches version 1.6.0_11 and Discoverer opens.

I've heard of situations like this. The solution depends on both your circumstances and your requirements. This all hinges upon how your environment handles "static versioning."

In the EBS world, the expected behavior changes depending upon the specific combination of your JRE release, browser, and EBS JRE setting. We've described a number of different EBS scenarios for handling static versioning in Microsoft IE in Metalink Note 290807.1 (for Apps 11i).

Although this Note is written specifically for EBS, I would suspect that the same principles apply to Discoverer, as well. In fact, I'd be very surprised if they *didn't* apply to Discoverer.

If that Note doesn't help, I'd recommend logging a formal Service Request with details about the JRE versions installed on your desktops, the browser used (i.e. Internet Explorer or Firefox), and the JRE specifications on your applications tier.

- Simplified chinese and japanese character set issue
Both languages displayed as square instead of actual character. Resolved by installing Albany WT J Font.. note: 240862.1.

Steven,

There is some issue whereby Sun JRE is not get loaded/installed after click on any form responsibility. The page seems to be hanging. This issue happened when user PC's already have highest version of Sun JRE compared to the apps server. For ex: we installed sun jre 1.5.0.17 on apps server. If user PC had higher than that, it may facing that issue. What we did is uninstall the java on user PC. Is there any other way to overcome this issue?

Thanks for sharing your experiences with the Sun JRE. It's possible that your environment isn't configured correctly. For example, there may be a conflict between the installed JRE on the desktop and the JRE that your EBS environment is requesting.

Rather than debug that here, I'd recommend logging a formal Service Request via Metalink to get one of our ATG Support specialists engaged. If your SR gets bogged down for some reason, please feel free to email it to me.

hi can someone help me out!!!! i am trying to access oracle rapid webbased application and when i logon i am getting a runtime error because i have java and jinitiator installed on my pc ,if i uninstall java it works fine , but i need java installed for some other applications please can someone help me out with this ?? Do i have to change any settings???

A User is accessing a java application via IExplorer 6 on XP SP1 using Sun JRE
1.4.2_04. No problems when only accessing this application. However, when
user opens another IExplorer window at the same time to access an Oracle 11i
application which uses a JInitiator 1.3.1.18 browser add-on, the user will
get:

Once user clicks OK on error, both IExplorer windows crash, i.e., they
disappear. Client needs to have both applications open simultaneously. The
Oracle 11i application does not have a specific JRE requirement. A native JRE
1.3.1.18 version was installed but we have removed, rebooted and installed 1.
4.2_04 JRE. The Oracle 11i application does use a Jinitiator 1.3.1.18 which
is a self-contained separate plug-in. Using either application using
IExplorer one at a time is no problem but as soon as they are both open at
same time in 2 different browser windows, that is when runtime error occurs.
]

could you please help me in fixing this as the user needs both java and jinitiator to be working for his applications

This sounds remarkably similar to a query I just handled about an Australian organization. If you haven't already done so, I'd recommend logging a formal Service Request via Metalink to get one of our Support Engineers engaged.

Until then, here's are my notes that I shared with the Australian consultant:

IE can only use a single JVM at a time (this is an Internet Explorer limitation and will apply also to JRE, too). Attempts to use a different JVM will cause IE crashes.

It is theoretically possible to start a new IE session with a different JVM, even while another IE session is still running. The catch lies in how this new session is started.

If you hit Ctrl+N while in IE, that's just opening a new window, not a new IE session. The only way to start a new IE session is to click the IE icon on your Start Menu. This behaviour is true for IE 7. I don't know if this is true for IE 6, though -- and I see you're using IE 6.

If this doesn't work, I'd recommend trying to reproduce the behaviour with IE 7. If multiple IE 7 sessions still cause crashes, then... well, you may wish to consider moving to the Sun JRE. Switching from JInitiator to the native Sun JRE should simplify your life, since the absence of JInitiator means just one less JVM to deal with. If I were in your shoes, I'd make sure that all of my Java-based applications all run on the same JRE release.

This includes E-Business Suite, of course. That's why we've tried to give you as many certified JRE options for EBS as possible: 1.5.0_13 and higher or 1.6.0_03 and higher. We don't want the E-Business Suite to be the one application holding you back.

Once you've got your Java applications on the same JRE level, desktop management issues like the one's you're experiencing now pretty much go away.

We migrated to JRE on one of our instances. For some people draging forms around the screen is very slow. It can take 10 seconds for a form to move from one locaiton to another. Is there a fix for this?

I'm sorry to hear that you've been bitten by this. It appears to be a hardware-specific issue with the Sun JRE.

I've heard reports of this with all JRE releases up to and including JRE 1.6.0_12. This appears to be a Sun JRE issue with certain graphics cards and drivers (including nVidia Feforce, nVidia Quadro, and ATI Radeon cards).

This has been reported to Sun, and we're waiting for a fix from them. In the interim, a possible workaround is described in Note 757618.1 (cross-referenced from Notes 290807.1 and 393931.1).

For a permanent fix, we're waiting for Sun to resolve their bug #6635462:

http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6635462

If you're encountering different behaviour on different hardware than described in the above Notes and Sun bug, please log a formal Service Request via Metalink and send me the details.

I am having an issue with Oracle Forms 10g. If I use the Sun Java JRE 1.6.0_02 I am unable to use the mouse to select a record in the data block, the form appears to be frozen on the first record. If I use jinitiator the form works fine, whichever record I select becomes highlighted.

Is there a specific version of JRE that I should be using with Forms 10g?

Hi Steven,
I've decided to change from JInitiator(1.3.1) to JRE (6u13) in our CRP instance and followed the instructions on ML Note 290807.1. Everything went well, but now if I try using any browser, I click on System Administrator responsibility and get a blank page with the following:
"Please make sure that JDK 1.6.0_13 is installed on your client. To download JDK 1.6.0_13 plugin you can visit http://finappstest01kt.seattlepacificindustries.com:8002/OA_HTML/oaj2se.exe. Please contact your System Administrator to know the correct version of the plugin."
If I click on the link it downloads plugin and next time it asks for the same thing, I openned an SR with Oracle support (21054158.6 ). They verified that JRE install went fine and now they want me to patch my Developer 6i. It is a lot of work to install 8+ patches and deal with unpredictable results (if you ask me). I don't see the benefit of going through all that if can ride JInitiator for some time and then, maybe upgrade to 12.

We just migrated from Jinitiator 1.3.1 to JRE 1.5.0_19-b02 and having issues with mouse navigation with our custom forms 10g applications. Has anyone encountered this issue? Please let me know what I need to do to fix this.

I am not clear if you are using eBusiness Suite or standalone Forms Server, but in either case it would probably be best to raise a Service Request with Oracle Support (with either the eBiz team or Forms team respectively) in order we can investigate the exact circumstances of your issue.

For eBusiness Suite 11i customers having this kind of issue, there is Note 760250.1 "Diagnosing Forms Mouse Focus Problems Using JRE in Release 11i" which may be useful to help diagnosing the root cause

I have been following your blog with interest, and wonder if you can clarify a situation please - or direct me to a contact in Oracle to obtain clarification.

We have recenlty upgraded our desktops to Sun JRE 1.5.0_16 for use with eBusiness 11.5.10 - as per your postings to move off JInitiator.

I need some clarification around the supported levels of JRE clients. Reading around there are references to the minimum supported JRE's. However with Sun's End of Life date for 1.5 does this not impact the support?
Also, is there a date planned where Oracle would no longer support eBusiness on JRE 1.5 clients, prompting a move to 1.6

2.After you receive the core dump the next time you try to launch the application you may receive the following error in the forms console window, in the message area.
error:java.lang.ExceptionInitializerError

If you do not close the start page (HTML start page to launch the application) you
Will receive the following message.
error:java.lang.NoClassDefFoundError

If you close the start page and reopen it forms will launch properly.

3.The last issue we have found is forms sometimes seems to freeze and not repaint the screen when selecting menu options.

I'm afraid that I don't have any insight into the root cause of this. Since this problem is occurring with a generic Forms-based application and not the Oracle E-Business Suite, your best bet might be to log a formal Service Request with the Oracle Forms team directly.

If I were an IT manager facing the choice between J2SE 1.5 and 1.6, I'd go with 1.6 without hesitation. There's no real reason to upgrade to a Java release that will be desupported by Sun in a matter of weeks.

Currently we have two sets of clients trying to access Ebusiness Suite via JRE. One set who uses JRE controlled via individual desktop level, and another set who access it via some Citrix infrastructure.

The first set at individual desktop level, has been 99% successful bar some slow loading at times (sometimes up to about 4mins). It always seems to be the first time which is slow?

The second set is having serious issues in that it can sometimes take up to 30mins to load the EBS Forms session. Its also sometimes refusing to load at all. This has been very serious and we've had to revert the clients back to Jinit at user profile option level in EBS, which you'll appreciate is not ideal.

In my mind, the odd 4mins loading period (window just appears to be inactive and suddenly pops the core forms session up), is highly unacceptable.

Thanks for the feedback on our blog. Glad to hear that you've found it useful.

The slowness of the first load is likely due to the fact that the JRE is downloading from your application tier server to your end-user's desktop. This is a one-time process, since subsequent Forms invocations should notice that the JRE is already installed, and thereby will skip the download.

The second issue you note is not what I'd expect to see. I'd like to ensure that you get some help from us in investigating this. Your best bet would be to log a formal Service Request via My Oracle Support (formerly Metalink) to get one of our specialists engaged.

Please feel free to forward your Service Request number to me if it gets stuck in the support process for some reason.

I'm afraid that I don't have any insight into what might be going on here. I'd like to have one of our JRE experts look into this for you. If this is still an issue, please log a formal Service Request via My Oracle Support (formerly Metalink) to get one of our specialists engaged.

Please feel free to forward your Service Request number to me if it gets stuck in the support process for some reason.

Hello. We have migrated from Jinitiator 1.3.1.28 to JRE 1.6.0_16-b01 and are experiencing freezing and crashing issues with Oracle EBS (11.5.10.2). The issue happens sporatically and we are unable to recreate it at will. I've read that having Jinitiator and JRE on the system creates a conflict. Our machines currently have both installed as some of our other applications use Jinitiator. We are not sure what the impact would be on these other applications if we remove Jinitiator (I would think the applications should automatically point to JRE???). Do you have any insight on this? If both JVM's must remain on the machines, any idea on how to resolve the issue? We have been communicating to our users to open separate IE sessions when opening other applications however, we are still having the issue. Some of the users only have Oracle and Outlook open and still freeze and crash. I've found this blog to be very informational but not sure how to go about resolving our issue. One more thing to note, when a user crashes, a log file is created on their desktop. Please see below. The one thing I did notice consistent in all of the log files we've viewed is the problematic frame references mshtml.dll. The only thing I've been able to find on this is to install a new version of IE (we are currently on IE7).

If you've gone through those troubleshooting steps and are still having problems, your next step would be to log a formal Service Request via My Oracle Support (formerly Metalink) to get one of our specialists engaged.

Please feel free to forward your Service Request number to me if it gets stuck in the support process for some reason.

I guess I am in the right place. I share the same pain with everyone else is experiencing. We have migrated from Jinitiator 1.3.1.18 to JRE 1.6.0_17 and experiencing forms losing focus with Oracle EBS (11.5.10.2). The issue happens sporatically and we are unable to recreate it at will. We have reapplied the following patch 8717874. We have also regen the forms with the parameter force 'Y'. I am no further along in finding a solution and I am afraid my users are getting little vulgar with their language towards me. I have opened a Service Request with Oracle Support but it is just going back and forth. Does anyone have any ideas I can sure use some help in resolving this issue.

We've found that the vast majority of focus issues are resolved by following the steps in that Note. If you've applied all of the patches listed there and still have issues, please send me your SR number so that I can have someone in Development work with the Support engineer assigned to your SR.

I just checked Note 761159.1 -- it seems to be accessible via My Oracle Support (formerly Metalink). Are you having issues because you don't have an account for My Oracle Support?

If so, I'm afraid that Notes are available only to My Oracle Support subscribers. I'm not permitted to distribute those to non-subscribers.

It's a pretty short Note, though. It simply states that Error Correction Support (ECS) for generic JInitiator users on Windows will end as of 31-JAN-2010, and Extended Support (ES) will end as of 31-JAN-2013.

If you've gone through that and are still having problems with focus issues, your next step would be to log a formal Service Request via My Oracle Support (formerly Metalink) to get one of our specialists engaged.

Please feel free to forward your Service Request number to me if it gets stuck in the support process for some reason.

Hi Gurus,
We have custom Oracle forms application and after upgrading to SUN JRE 1.6.0_16 we started getting Row lis locked by another user issue in forms.When we switch back to Jinitiator this problem doesn't exist(code remains same).

Given that you're encountering an issue with a custom Forms application, I suspect that there might be some coding standards at the root cause of this. Your best bet would be to log a formal Service Request via My Oracle Support (formerly Metalink) to get an Oracle Forms specialist engaged.

Recently, we migrated to Sun JRE 1.6.0.17, Since then often having issues with IE 6.0 crashes suddenly . Referring "mshtml.dll" in the log generated. Some times users are panic when it happens. Please suggest whether this issue is addressed in the later version of JRE.

Without knowing the root causes of the crashes that you're experiencing, I can't comment on whether that will recur with later releases. I would recommend upgrading to the latest JRE on a testbed desktop to see whether you can replicate your issue there. See this recent article:

What are the problems will be occured while migrating application from jdk 1.4 to jdk 1.6?
What are the steps needs to follow to avoid those errors?
What info should be kept in mind while migrating jdk 1.4 to jdk 1.6?

You've referred explicitly to the JDK -- not the JRE, although you're commenting on a JRE-related article. Remember, these are two different things. The JDK resides on your EBS application tier server, and the JRE resides on your Windows desktop clients that access your E-Business Suite environment.

Assuming that you know what you're doing here, you can find complete JDK upgrade instructions for your EBS application tier linked off this article:

Hi Steven,
Just wanted to get this out to you. We've migrated most of our users to the latest Sun JRE 1.6.0_20 update 5 (we waited because we also run Discoverer and wanted to use a common version for both).
One thing that we have noticed is frequent forms crashes and slowness in the forms, even though the load on the server has remained the same. We also have some thin client users accessing 11i forms over RDP and they experienced slowness as well.
The solution to the forms crashes and performance problem was to add this runtime parameter on the client side in the Java control panel applet:
-Dsun.java2d.noddraw=true
We also had done this on our older Jinitiator clients, but I didn't think we would need to do it with the newer JRE. Once we put that in it stops the intermittent forms crashes and the forms perform much better.
As always, test it out, but I just wanted to get this out there to others who may be experiencing some problems with the newer JRE.

Thanks for sharing this tip. Can you provide me with your Service Request number where this was investigated and replicated by Oracle Support? I'd like to review their analysis and see whether this has been formally reported as a bug to the Sun JRE team (or the Forms team).

Hi Steven,
Unfortunately I didn't raise an SR for this. We've been using that parameter since JInitiator 1.3.1.18 to increase the performance of the forms interface through RDP (Remote Desktop Protocol) sessions. At that time we experienced issues with poor performance (forms slow to drag, slow data population) on thin clients connecting to a terminal server via RDP. I found the -D setting in a discussion on increasing java applet graphics performance. I thought I would give it a shot in Jinitiator and it made all the slow dragging and slow data population errors disappear.
When we began moving to the JRE 1.6 I thought we could leave that parameter behind, but right after deployment my users began complaining of forms crashes and poor forms performance, particularly in order entry when tabbing into the unit price field. Adding the -D parameter fixed the crashing and jacked up the forms performance again. This time though we weren't using RDP sessions, they were native sessions on desktop client machines, not thin clients.
I'll be glad to provide you any test data or test cases I can if necessary.
Thanks,
Mark

In rereading this thread, I realized that this is a workaround that you've come up with for your thin clients accessing EBS over RDP. It all comes clear now.

As you probably know, our official position is that we certify and support only Windows and Mac desktops accessing the E-Business Suite, so we don't have the infrastructure to validate this and update our official documentation accordingly.

I'm glad that you've been able to find a workaround for your thin clients. Thanks for sharing this tip with our readers. These kinds of insights are priceless for customers operating in slightly nonstandard environments, and it's great that we have a forum to share your experiences here.

Hi Steven,
We found the parameter originally to help our thin client display performance, but we have been using it on both thin clients and Windows desktops since Jinitiator 1.3.1.18 to improve display performance and avoid forms crashing issues. When we moved to the JRE 1.6 I thought we could leave it behind, but the parameter solves several forms crash issues on the Windows desktops, so we put it back in on both.
You're correct in that originally it was for thin clients, which you guys don't officially support, but we are now using it on thin clients and Windows desktops with good results.
Just wanted to clarify, not trying to beat a dead horse! Thanks to you and all the good people at Oracle who put out this info!

Hi Steven,
We are a little bit late, but now we want to change from JInitiator to JRE.
Current config: Oracle EBS 11.5.10.2 and JInitiator 1.3.1.25.

Our clients are spread all over the world and only partially controlled by us.
Currently we believe that we have not the ability to migrate all users/clients of an EBS instance at a big bang without problems. Introducing a new JRE will impact older Java applications.

Our idea is to configure our EBS to support JRE and JInit in parallel for a limited time. The intention is to support a fallback to JInitiator for clients with JRE problems to have some time to solve those issues without a fallback for all users.
We are running such a config in a test environment but Oracle does not recommend this for production.

It seems that all other customers switched all users of one EBS instance to JRE at a single blow or?
Is a step wise recommended migration strategy known by you?
Any customer experience?

I haven't spoken to many customers about this directly. I would be very surprised if very large organizations (e.g. those with tens of thousands of EBS users) could switch over in a big bang conversion, though. I suspect that those organizations took a staged approach that allowed both JInitiator and JRE to run side-by-side.

Hi Steven,
We are planing to upgrade JDK of our EBS 11.5.10.2 configured with SSl, i would like to know if there are any precautions need to be taken before upgrading the JDK which will not impact SSL configuration.

I'm sorry to hear that you've encountered an issue with this. It sounds like you're reporting an issue with a custom application and not Oracle E-Business Suite. This blog is for Oracle E-Business Suite topics, so we don't have much advice for generic issues like the one you're reporting.

Your best bet would be to log a formal Service Request via My Oracle Support (formerly Metalink) to get one of our Forms specialists engaged.