Fusion

Moving from Forms to J2EE. Almost as much a problem for the Oracle applications developer as moving from PeopleSoft.


http://searchsoa.techtarget.com/originalContent/0,289142,sid26_gci894857,00.html

The latest version of forms uses the default 5.0 JVM and not Oracle's proprietary JVM Jinitiator so it is easier to get the client installed.




Technical Tsunami. Underlines the need for certain developers/supporters to have a solid Java knowledge.
http://blog.oraclecontractors.com/?p=320

OA Framework - A Java framework to extend the previous versions of Oracle EBS, Superseded by Oracle Application Development Framework
http://en.wikipedia.org/wiki/Oracle_Application_Development_Framework
http://www.orafaq.com/forum/t/63823/0/





The Joys of Release 12 Early Adoption
http://blog.oraclecontractors.com/?p=322

We are at the leading edge with the Oracle product set. Oracle R12 was released at the end of January this Year.






Reporting Tools for Oracle Applications. 6 reporting tools plus the analytics tools and doing things like reporting direct from PL/SQL, Lots to learn.
http://blog.oraclecontractors.com/?p=121






Difference between configuration, personalization, and Custom Extensions. So much more complicated than PeopleSoft.
http://blog.oraclecontractors.com/?p=258

Forms Personalization :
http://blogs.ittoolbox.com/oracle/appstraction/archives/oracle-form-personalization-basic-example-11936
http://www.oracle.com/technology/products/applications/development_pesonalization/index.html

OA Framework Personalization :
The OA Framework's declarative architecture and object-oriented implementation enable personalisation's to be saved as offsets from the base component meta data definition. Hence patching the base component definition doesn't lose the customer personalisation's.
Personalisation's can be implemented at several levels by three types of users: application developers, application administrators and end users. End-user personalisation's can be applied to particular user interface components and are only visible in the context of the implementing user. For example, an end user may save an employee search result sorted by manager and choose to hide the employee's date of birth column. The result is called a view and is given a name by the user. The user can retrieve that view again in the future by name. Application administrators and application developers are offered the flexibility to tailor user experience at several levels. They can author personalisation's that affect all users, users of a particular locale, users of a particular organization, users with a particular role and in the context of a particular function. Several levels can apply at the same time with a predetermined precedence order that yields a very personalized user experience. For example, human resource managers in Japanese and Spanish subsidiaries could have a different user experience that reflect personalisation's made to accommodate legal and language differences between the two countries and possible personalisation's done by the individual human resource managers.
Using a combination of JDeveloper wizards and built-in personalization screens, several user interface and business logic extensions are made possible at a minimal cost of development and little-to-no maintenance cost. In addition, Oracle E-Business Suite customers continue to enjoy the extensibility features offered by Flexfields, Oracle Workflow and Business Events.