Oracle Forms: Frmall.jar and Frmwebutil.jar files are set to expire soon

So when I say soon, I mean the .jar files may have already expired in your system or will expire tomorrow.  Oops.  Find out more about this from My Oracle Support article "How to Extend Frmall.jar and Frmwebutil.jar Expiration Beyond 22, 23-Jan-2016" via note ID 2072400.1 to learn what can be done for 10gR2, 11gR1, and 11gR2!

R12.1 Oracle HR: Receiving FRM-40654 error when trying to modify name

You will not believe the root cause of the MOS article "FRM-40654: Record has been updated. Requery block to see change Error When Updating a Person's Name" from note ID 2096800.1 but it sure is a good reminder to add data checks like this to your testing suites!!

Windows: 12c forms instance does not exist after startup

Are you running 12c on Windows?  We don't really run on Windows, but MOS document "Forms 12c Instance (FORMS_INSTANCE) "forms1" and Forms Related Registry Variables Do not Exist after Starting Nodemanager and Adminserver" via note ID 2094031.1 taught me something new tonight about the folder structure and what the solution is for this problem so maybe someday I can use it!

R12.2.4: Application Tech Stack - Forms error with AWT-EventQueue-2 Java.lang.IllegalStateException messages

So much for trying to restart my posting streak right before a vacation huh?  Let's see how many days I get this time!

Trying to stay on top of recent R12.2.4 and R12.2.5 changes, My Oracle Support document "Random Forms Error "Exception In Thread "AWT-EventQueue-2" Java.lang.IllegalStateException: Applet'" from note ID 2075992.1 comes an issue where the wrong version of the $FND_TOP/html/oafcoreR122.js file is installed and needs updating so Internet Explorer 11 users can consistently access the application without errors.

ORA-06508 or FRM:40735 errors when opening EBS forms

Tonight, we have a general lesson in upgrades either with the EBS application or the Oracle database as My Oracle Support note "R12: Finally Close or Cancel FRM:40735: WHEN-BUTTON-PRESSED Trigger Raised Unhandled Exception ORA-06508" from document ID 2021590.1 shows us the simple reason why this happens as well as teaches us how to use adadmin also which you may not see if you are strictly Operations or Support.

JRE 1.8 upgrade activates TLS settings that knocks out Oracle Forms

I have talked about HeartBleed and POODLE vulnerabilities recently which both relate to SSL and TLS but tonight MOS document "Forms with SSL not Working After Upgrade to JRE 1.8 from 1.7" from note ID 1675195.1 combines them both with JRE updates and Oracle Forms!  Are you getting reading to update your version of the JRE soon?  Need to know more about JRE 1.7 and how it will be autoupdating to JRE 1.8?  Learn from Steven Chan's blog entry on the subject!

Weekend Learning: Oracle Forms Developer - Information Center

Yesterday I mentioned a Receivables Information Center on MOS so I go from a specific EBS application module to the more technical details behind the EBS application by introducing you to the "Information Center: Oracle Forms Developer" found from document ID 1370782.2!  Think you do not need to add this bookmark in MOS just because you are already using Forms Developer and there is nothing you to know?  Think again!  There are updated articles that might be relevant because while Forms Developer may not change, there are many different things related moving around behind the scenes that could affect how the Oracle Forms work!

GL: FRM-40654 when reversing journal

When our GL team was trying to close out the month, they were receiving the error "FRM-40654: Record has been updated. Requery block to see change." when trying to reverse a journal entry.  After looking at everything we could regarding locks, and other people being in the record or the form, I finally researched on My Oracle Support to find the document "GLXJEENT: Journal Reversal gives Error FRM-40654: Record has been updated. Requery block to see change" via note 1135903.1 which helped me solve the problem.

There is an enhancement bug and it seems that even though it is marked as fixed in 11.5.10.2 we still encountered it on R12.1.3 so we need to find out what patch to apply to prevent this in the future!

R12 Payables: Invoice Workbench error APP-SQLAP-10108 when committing

Some days, the articles I share have a very specific focus but today this feels like a much larger lesson on several fronts.  The MOS article "Invoice Workbench/Distributions - APP-SQLAP-10108: An Error has occurred while trying to commit" in 1570047.1 is very straightforward for how to replicate the issue and that the cause is non-printing characters but it goes to make me wonder why this was not included in a testing suite by Oracle.  Even more curious, is the reaction that "this just should not be done, so stop doing it" instead of Oracle development working to make sure the form will not accept these types of characters.  I wonder what other forms have this ticking time bomb lurking in them, and how many times it has to be reported until it gets resolved in an eventual release.