Академический Документы
Профессиональный Документы
Культура Документы
Rajendra Jagtap
Agenda
Deprecated Technologies
Overview
3
KPIT Cummins Infosystems Ltd. Confidential
Key points to note in Oracle Apps R12 upgrade from 11i
-- R 12 upgrade process involve replacing 11i Tech stack (9iAS & 806) to Fusion
Middleware (10g Application Server)
-- Minimum version from which you can upgrade to R12 is 11.5.7 and higher
Key Facts
Feature
Example
6
KPIT Cummins Infosystems Ltd. Confidential
R12.1 / R12.2 Key Facts :R12.1 / R12.2 Technology
Stack
Per product database object comparison between two releases for the following
object types (1290886.1)
Benefits
Differences viewable for all products in the same report via simple UI
Per product EBS ATG Seed data type comparison between two
releases (1327399.1)
Supports most of the EBS delivered seed data types. e.g. Menus,
Functions, Profiles and many more
Benefits
Meant for Advanced user with prior knowledge about EBS Seed data
Delivery
Benefits
In upgrade planning phase, customers can get information about new,removed
and changed files
Differences viewable for all products in the same report via a simple UI
Profile
Samples
Migrations
Values inherit the definition from the level immediately above unless changed
Function
Site
Operating Unit
Responsibility
You all are may be well aware that we use f60gen for compiling forms and libraries in
Oracle Applications Version 11i,But this is deprecated in R12 and we need to use
frmcmp(Form Compiler) To compile forms,menus,PL/SQL libraries
Compiling forms
-----------------
11.5.9 and 11.5.10
R12
=====
$ frmcmp_batch module=<path to the fmb file> userid=apps/<apps pwd>
output_file=<path to the fmx file> compile_all=special batch=yes
eg.
frmcmp_batch module=FNDFBMAS.fmb userid=apps/<apps password> module_type=form
batch=yes compile_all=yes
------------------------
11.5.9 and 11.5.10
$ f60gen module=/test/applmgr/11510/au/11.5.0/resource/OEXOELIN.pll
userid=apps/passwd
output_file=/test/applmgr/11510/au/11.5.0/resource/OEXOELIN.plx module_type=library
batch=no compile_all=special
R12
$ frmcmp_batch module=/test/applmgr/11510/au/11.5.0/resource/OEXOELIN.pll
userid=apps/passwd
output_file=/test/applmgr/11510/au/11.5.0/resource/OEXOELIN.plx module_type=library
batch=no compile_all=special
Personalization
Forms Extensions
CUSTOM Library
Personalizations
Oracle Forms
Web ADI
Workflow
A screen or page has been sufficiently modified in the new version of the
product such that the old objects, such as fields, that were personalized no longer
exist in the new version. For the 11i to 12 upgrade, however, forms are more likely
to have been rebuilt in Oracle Application Framework than to have been modified
using Oracle Forms.
Modifications you may have to make to your Oracle Forms code fall into three
main categories:
1. Obsolete Forms Built-ins and Properties
2. Enhanced syntax checking in Forms PL/SQL
3. Change from 4.5 to 5.0 Compatibility Mode (primarily affects mirror items,
validation, and navigation)
Most required changes can be identified at build time. Some changes, such as
changes in validation, can only be identified at run time.
The CUSTOM library is an Oracle Forms stub library that receives trigger events
as Oracle Forms run. Many customers have used the CUSTOM library
(CUSTOM.pll) to modify the appearance and behavior of Oracle Forms-based
forms.
The CUSTOM library still exists and works in Release 12. However, the same
caveats apply to the CUSTOM library as to form personalizations. That is, if an
Oracle Forms-based form no longer exists in Release 12, any CUSTOM library
logic for that form would need to be retired.
When you install Release 12, you get a new, empty version of CUSTOM.pll in
the new Release 12 file system. You need to copy your 11i CUSTOM.pll, upgrade
it to Oracle Forms 10g, and put it in place in your new Release 12 file system.
Alternatively, you can put your code into the Release 12 CUSTOM.pll after
backing up the new, empty version.
If you created custom integrators for Web ADI in Release 11i using shipped
APIs, you should be able to upgrade those. You must test them after the upgrade
to make sure they still work as expected. If you modified integrators that were
shipped as part of the product, you will need to redo any layout modifications
after the upgrade, since those will be overwritten.
Note that starting with Release 12.1.2, Web ADI offers a powerful new feature
called the Desktop Integration Framework for creating your own custom
integrators more easily.
37 7/10/17 KPIT Technologies Limited Proposal For R12 Technical Upgrade
Upgrading Workflow Customizations
There are two options for customers to customize seeded business flows:
Plug in a custom flow into a seeded flow where a product has provided a
placeholder
Extend a default business flow implementation with some configurations
Workflow developers operate with a specific Access Level when creating
workflows:
Oracle Workflow Development - 0-9
Other Applications Technology Products - 10 - 19
Product Teams - 20 - 100
Customers and their subsidiaries - 101 - 1000
Workflow developers and customers can set their flows to be protected from
upgrade. Before upgrading, check that your protection and customization options
are set correctly.
If seeded flows are revamped during a major upgrade from 11i to R12, such as
changing entire business process flow definition by refactoring their flows or
redesigning the activities, then customizations to those seeded flows might need
to be redone. These cases are described in the product-specific documentation.
Deprecated Technologies
FORM
APEX
ADF
OAF