Applications Technology Tasks

Complete the tasks in this section before you complete the product-specific tasks.

System Administration

These tasks must be carried out regardless of the products that are active in your system.

1. Verify completion of Compile Security concurrent program (required)

You must wait and verify that the 'Compile Security' concurrent program successfully
completed before attempting to log into EBS. You can run the following pl/sql block to
view the status of this concurrent request:

set serverout on
declare
res boolean;
request_id number := null;
phase varchar2(80);
status varchar2(80);
dev_phase varchar2(80);
dev_status varchar2(80);
message varchar2(255);
begin
res := fnd_concurrent.get_request_status(request_id,
'FND',
'FNDSCMPI',
phase,
status,
dev_phase,
dev_status,
message);
if (res) then
dbms_output.put_line('Request Id : ' || request_id);
dbms_output.put_line('Phase : ' || phase);
dbms_output.put_line('Status : ' || status);
dbms_output.put_line('Completion Message : ' || message);
else
dbms_output.put_line('Unable to retrieve the information');
end if;
end;
/
.

Results should appear as follows:

o Phase: Completed
o Status: Normal
o Completion Message: Normal Completion
2. Verify completion of concurrent programs (recommended)
 The upgrade process creates numerous concurrent program requests. Once you bring up
the application tier, these programs run automatically to complete tasks such as data
cleanup and upgrades to historical data, among others.

Note: Before you continue, ensure that all concurrent programs generated by the upgrade
have run successfully. Refer to the Managing Concurrent Processes appendix of this
guide for a sample list of concurrent programs.

1. Install online help (recommended)

Applies to 11i release level: All

TUMS step key: N/A

To install the American English online help, run the database portion of the online help
patch (u10201000.drv). It is located in $AU_TOP/patch/115/driver directory. You must
apply the American English online help patch driver
($AU_TOP/patch/115/driver/u10201000.drv) using AD Online Patching (adop) with
phase=apply hotpatch=yes and options=nocopyportion,nogenerateportion,forceapply.

adop phase=apply patchtop=$AU_TOP/patch/115 patches=driver:u10201000.drv

options=nocopyportion,nogenerateportion,forceapply hotpatch=yes

2. Update and verify custom responsibilities (conditional)

Verify that all custom responsibilities use the correct menu. From the System
Administrator responsibility, navigate to Security > Responsibilities. Query each custom
responsibility and update as necessary.

3. Grant flexfield value set access to specific users (required)

Release 12.2 includes a new security feature, flexfield value set security; it controls who
can create or modify flexfield values in the Flexfield Values Setup window
(FNDFFMSV). Flexfield value set security requires some mandatory setup steps before
any user can create or update values in the Values window. You must perform this step if
you have not already done so for a previous version of Release 12.2.

Note: See the Flexfield Value Set Security chapter in Oracle E-Business Suite Flexfields
Guide, Release 12.2 (Part No. E22963-07).

4. Migrate custom development to new technologies (recommended)

Applies to 11i release level: All

TUMS step key: N/A

In this release, Oracle E-Business Suite is migrating to new technologies in certain areas.
If you have built custom development on the out-dated technologies, you should migrate
to the new technologies as part of the upgrade.

Note: See Preparing Custom Development for Next Oracle Applications Release (Doc
ID: 374398.1) for more information.

mod_plsql:

If you have custom development on mod_plsql, migrate your web pages to Oracle
Application Framework.

Note: See Oracle Application Framework Developer's Guide (Doc ID: 1315485.1) for
more information.

Oracle Reports Server Reports:

If you have custom development that uses reports that are run through Oracle Reports
Server, the following migration alternatives are available.

New Technology Advantages and Considerations

Convert to Prepares your application both for E-Business Suite Release 12 and
Oracle XML for Oracle Fusion Applications. Allows you to take advantage of the
Publisher benefits of XML Publisher. Some automated tools are available to
help you migrate to XML Publisher. See Oracle XML Publisher
Administration and Developer's Guide for more information.
Convert to May be appropriate for some reporting needs. However, note that no
Oracle automated migration tools are available. You must rewrite any charts
Application using the Framework Charting tool (BI Chart Bean). See Oracle
Framework Application Framework Developer's Guide (Doc ID: 1315485.1).
Run through the If you follow coding standards, you must modify your PL/SQL code
Concurrent to meet the concurrent manager standards. In particular, you must
Manager use some user exits. Rewrite any charts using the Oracle Reports
Charting tool (BI Chart Bean). See Oracle E-Business Suite
Developer's Guide and Oracle Reports: Building Reports for more
information.

Oracle Graphics Integrations with Oracle Forms:

If you have custom development that uses Oracle Graphics (Charting) integrated with
Oracle Forms, the following alternatives are available.

New Technology Advantages and Considerations

Convert both the form and the chart to a
Framework-based application.
Convert the chart to a Framework-based
page that can be launched from Oracle
Forms.
Prepares your application both for Release
12 and for Oracle Fusion Applications.
See Oracle Application Framework
Developer's Guide (Doc ID: 1315485.1)

AK Mode:

o Personalizations

Personalized Oracle E-Business Suite Framework-based pages in the AK

repository, are automatically migrated from AK to MDS during the upgrade - if
the AK and MDS repositories are in the same database instance.

The upgrade does not automatically migrate custom personalizations if the AK

and MDS repositories are in separate instances. In this case, you must run the
Personalization Migration tool manually to perform the migration.

Note: See Migrating AK Personalizations in Oracle Application Framework

Personalization Guide for more information.

o AK/ICX Web Inquiries

If you have previously used AK/ICX Web Inquiries, then use the Oracle
Application Framework Search feature to recreate search regions that can be
personalized.

Note: See Implementing Specific UI Features in Oracle Application Framework

Developer's Guide (Doc ID: 1315485.1)

o Migrate the CUSTOM library (conditional)

Before you copy custom code in the CUSTOM library to the new directory structure,
refer to the backup you previously created and verify that the customizations are valid for
the new version of Oracle Applications.

For valid customizations, place a copy of the new CUSTOM library (CUSTOM.pll) in a
safe place. It is located in the $AU_TOP/resource directory (UNIX), or the %AU_TOP
%\resource directory (Windows). Then, make a copy of the old Oracle Forms CUSTOM
library and place it in the new directory. Upgrade to Oracle Forms Developer 10g by
regenerating the library. Or, you can cut and paste the existing custom code into the new
library, and then regenerate it.

Note: See Using the CUSTOM Library in the Oracle E-Business Suite Developer's
Guide.
 o Copy and re-customize modified scripts or reports (conditional)

Copy custom shell scripts or reports to the custom application directories and re-
customize the copy as necessary.

Note: See Product Customization Standards in Oracle E-Business Suite Developer's

Guide.

o Copy existing custom start scripts (conditional)

If you have customized the concurrent manager startup script

($FND_TOP/bin/startmgr.sh on UNIX), then you must copy the customized script from
the old environment to the new environment. You should then verify that your
customizations are valid for the new environment.

Warning: Oracle does not recommend customizing this script. If you perceive a need to
change this script, then contact Oracle Support before making changes. For more
information, see the Oracle E-Business Suite Setup Guide.

Note: The default location in UNIX for the startmgr script is $FND_TOP/bin. For more
information, see the Oracle E-Business Suite Setup Guide.

o Review user responsibility assignments (recommended)

Applies to 11i release level: All

TUMS step key: N/A

Although user/responsibility assignments are preserved during the upgrade, the effective
permissions granted by the seeded responsibilities, menus, functions, and report security
groups may have changed. Use the information on the Forms or Security reports in the
System Administrator responsibility to confirm that permissions granted by
responsibilities continue to meet the requirements of the job roles (without granting more
privileges than are necessary).

Note: See Organizing Programs into Request Groups in the Oracle E-Business Suite
Setup Guide for more information.

o Configure applications client software for forms applet (required).

The connection between the client and the applications forms is provided through an
applet in the client web browser. Instead of using the browser's own JVM, Oracle E-
Business Suite uses the Sun Java (J2SE) native plug-in. You can find download
instructions in Deploying JRE (Native Plug-in) for Windows Clients in Oracle E-
Business Suite Release 12 (Doc ID: 393931.1)..
Alerts

These tasks apply to Oracle Alerts.

1. Associate organization names with custom Alert definitions (conditional)

Manually update custom alerts that you want to assign to a particular organization:

1. As the Alerts Manager, navigate to the Alerts form (Alert > Define) and query the
definition.
2. Choose Alert Details, then display the Installations tabbed region in the Alert
Details window.
3. Enter the ORACLE ID and organization name that you want to run this alert
against.
4. Make sure you check Enabled before saving the changes.

Multiple Organizations

These tasks apply to Multiple Organizations for Oracle E-Business Suite.

1. Set operating unit mode for customizations (conditional)

With the introduction of multiple organizations In this release, an applications

responsibility can access multiple operating units. Some concurrent programs have been
enhanced to be able to process multiple operating units simultaneously, whereas for most
others, the operating unit must be specified when you run the program.

To support this new functionality, concurrent programs are defined with an operating unit
mode of S for single operating unit or M for multiple operating units. This mode is set
automatically during the upgrade.

However, if you have modified the definition for any concurrent programs, then the
upgrade will not set the operating unit mode in order to preserve the customization.
Depending on how you run the customized program, you may need to set the operating
unit mode manually. Run the following SQL command to set a concurrent program for a
single operating unit:

UPDATE FIND_CONCURRENT PROGRAMS

SET MULTI_ORG_CATEGORY='S'
WHERE CONCURRENT_PROGRAM_NAME = '<your program name>'

Enter M instead of S for multiple operating units.

If you want to know which setting is appropriate for a given program, then you may
review the setting in the appropriate .ldt file.
 Note: If you have customized the concurrent program definition, this setting may not be
appropriate given the way you use the program.

Oracle Web Applications Desktop Integrator

These steps apply to Oracle Web Applications Desktop Integrator and to products that use Oracle
Web Applications Desktop Integrator to generate spreadsheets.

1. Recreate existing spreadsheets (conditional)

Applies to 11i release level: All

TUMS step key: N/A

Spreadsheets created in previous versions of Oracle Web Applications Desktop Integrator

do not interact with Oracle E-Business Suite products after the upgrade. You must
replace existing spreadsheets with ones that you create using the new technology stack.
Follow the procedures in your product-specific documentation to create the new
spreadsheets.

Workflow

These steps apply only to Oracle Workflow.

1. Update Status Monitor URLs (required)

Applies to 11i release level: All

TUMS step key: N/A

Oracle Workflow provides URL access to the Status Monitor through the Application
Framework Agent, rather than through the PL/SQL Web agent used in Release 11i. Run
the Workflow Plsql Cartridge Dependency Removal From Data concurrent program to
update the Status Monitor URLs that appear in existing workflow attribute values to the
new Web agent structure. The program updates item attribute values for active workflow
processes and message attribute values for open notifications.

Note: The update for message attribute values applies only to notifications accessed
through the Worklist Web pages. Status Monitor links in e-mail notifications that were
sent or generated before the upgrade cannot be automatically updated. Log on to Oracle
E-Business Suite separately to access the Status Monitor after the upgrade.

Oracle E-Business Suite Integrated SOA Gateway

Oracle E-Business Suite Integrated SOA Gateway requires manual post-installation steps. If you
want to use the Oracle E-Business Suite Integrated SOA Gateway feature for Web service
generation, deployment, and invocation, then perform the steps documented in Installing Oracle
E-Business Suite Integrated SOA Gateway, Release 12.2 (Doc ID: 1311068.1).

Note: After the upgrade, the deployed Web service's WSDL URL will be changed. You may
have to replace it with the new WSDL URL and service location, or address accordingly in Web
service clients while invoking the Oracle E-Business Suite service.

Oracle XML Gateway

Complete the installation and setup tasks described in Installing Oracle E-Business Suite
Integrated SOA Gateway, Release 12.2 (Doc ID: 1311068.1) for enabling Oracle E-Business
Suite Integrated SOA Gateway and generic XML Gateway services.

Note: After the upgrade, the deployed WSDL URL for a generic XML Gateway service will be
changed. You may have to replace it with the new WSDL URL and service location or address
accordingly in Web service clients while invoking the generic XML Gateway service. For more
information about XML Gateway Web services, see the Oracle XML Gateway User's Guide.