Don't forget to apply this patch when upgrading to 12.1.1 !

In a recent test upgrade from 11.5.10.2 (ATG RUP6) to R12.1.1, one of the issues we discovered is that users are unable to login after the upgrade due to an "invalid password" message. Resetting the password using FNDCPASS did not help. After logging an SR with Support and much troubleshooting, we discovered that an important pre-requisite patch had been overlooked.


The patch number is 8764069 and it needs to be applied in pre-install mode (see the patch README for detailed instructions). The cause of the issue and the fix that this patch delivers is found in these MOS Documents -


566521.1 - Oracle Application Object Library Release Notes, Release 12.1.1 (see Section 5)
457166.1 - FNDCPASS Utility New Feature: Enhance Security With Non-Reversible Hash Password (see highlighted Note #5 (in yellow) in the "Goal" section)


In essence, if you are on 11.5.10.2 ATG RUP6 or higher, and have migrated to using non-reversible hash passwords using the FNDCPASS USERMIGRATE functionality delivered in ATG RUP6, and are now migrating to R12.1.x, this patch needs to be applied before the upgrade.


Not doing so will, unfortunately, make the upgraded instance unusable - and there is no fix, other than to re-do the upgrade from scratch. MOS Docs 942600.1 (Post Rapid Wiz Install Check Fails On Login Page With RW-50016 After Upgrading From 11i or 12.0.x to 12.1.x) and 566521.1 indicate that this patch can be applied after the upgrade, but this did not remedy the situation in our case. We basically had to start with the upgrade process all over again.


This important pre-requisite is not currently documented in any of the R12.1.x upgrade guides.


REFERENCES


566521.1 - Oracle Application Object Library Release Notes, Release 12.1.1
457166.1 - FNDCPASS Utility New Feature: Enhance Security With Non-Reversible Hash Password
942600.1 - Post Rapid Wiz Install Check Fails On Login Page With RW-50016 After Upgrading From 11i or 12.0.x to 12.1.x)

Bug 8207550 Not Dropping FA_JOURNAL_INTERIM Tables

If you run the Create Journal Entries request set in 11.5.10.2, you may have some unneeded tables hanging around in your system. The code to drop the FA_JOURNAL_INTERIM table has been inadvertently commented out of FAXCJEB.pls, allowing the tables to remain after they are no longer needed.


ISSUE

BUG 8207550 FA_JOURNALS_INTERIM tables are not dropped after Create Journal Entry.


SYMPTOM

FA_JOURNALS_INTERIM tables remain present in the database after Create Journal Entries run.


SOLUTION

There is no patch currently available to resolve this issue. You may choose to allow the tables to remain in your system, or these tables can be safely removed after the completion of the Create Journal Entries run.


TIP

If you aren't currently doing so, you should consider implementing a check for newly created objects in your database. This can help you identify objects that are not properly cleaned up.


REFERENCES

757666.1, FA_JOURNALS_INTERIM Tables are Not Dropped after Successful Create Journal Entry and Journal Import

732925.1, Journal Import Fails After Depreciation Run. Depreciation Journal Is Unbalanced

Bug 8819967 with JRE Plugin and R11i Oracle Sourcing

If you have migrated from JInitiator to the native SUN JRE Plugin and utlize the Oracle Sourcing module, you will need to apply this fix to your enviornment.

ISSUE
BUG 8819967 JINI 1.3.1.21 is hardcoded into applet

SYMPTOM
You've upgraded to use the SUN JRE Plugin, however, when using Oracle Sourcing, the application attempts to launch the JInitiator.

SOLTUION
Apply Patch 8819967
or
11.5.10 PRC RUP XIII

TIP
If you have not migrated to SUN JRE Plugin, please consider doing this. Note that JInitiator has been desupported.

R11i REFERENCE
290807.1, Deploying Sun JRE (Nativ Plug-in) for Windows Clients in Oracle E-Business Suite 11i

R12 REFERENCE
393931.1, Deploying Sun JRE (Native Plug-in) for Windows Clients in Oracle E-Business Suite Release 12

Bug 8264899 with 11.1.0.7 and UTLPRP.SQL

If you have recently upgraded to Oracle RDBMS 11.1.0.7, you may have noticed issues while using UTLPRP.SQL. If you are considering an 11.1.0.7 upgrade, please add this patch to your deployment.

ISSUE
BUG 8264899

SYMPTOM
UTLPRP.SQL failes from ORA-00904: "FALSE"; INVALID IDENTIFIER

SOLUTION
Apply patch 8264899 to Oracle RDBMS 11.1.0.7

TIP
Details for using 11gR1 with Oracle R11i and R12 can be found on My Oracle Support in the enclosed articles:
R11i Reference
452783.1, Interoperability Notes, Oracle E-Business Suite Release 11i with Oracle Database 11g Release 1 (11.1.0)
R12 Reference
735276.1, Interoperability Notes, E-Business Suite R12 with Oracle Database 11gR1 (11.1.0)