Upgradation Project

Up gradation

1. Why Upgrade?

2. Version

3. People Involved

4. Stages

5. Observations.

Why upgrade?

 Oracle has decided to stop the support in future for 11i versions.

Version

•       Present version is 11.5.10.2

•      Initial upgrade to 12.1.1

•     Final upgrade 12.1.3

People Involved

•      DBA: Upgrading the database, application and applying Patches.

•      Functional: Setups, Training and Change in Process.

•      Technical: Object validations, functionality of reports, forms, alerts and workflow.

Stages

3 phases

1.     Iteration 1

a.     Pre upgrade

b.     Upgrade

c.      Post upgrade

2.     Iteration 2

a.     Pre upgrade

b.     Upgrade

c.      Post upgrade

3.     Iteration 3

a.     Pre upgrade

b.     Upgrade

c.      Post upgrade

Pre Upgrade

•      Need to meet system requirements.

•      Make sure all application versions are synchronized to present version of 11.5.10.2

•      To upgrade to 12.1.3 we need to upgrade it to 12.1.1.

•      DBA team will apply patches according to Oracle document.

•      Technical team will be responsible in clearing the interfaces and make sure no data is found in interface tables.

Upgrade

•      DBA team will apply patches.

•      Initially 11.5.10.2 is upgraded to 12.1.1

•      Functional team will check few cycles and setups.

•      12.1.1 will be upgraded to 12.1.3

Post upgrade

•      Check every custom objects are moved properly.

•      Object validations through compliance for invalid table names, reports validation, value sets, alerts and workflow.

•      Conference Room Pilot -1 (CRP-1), in which functional team will start validating.

•      We also provided training to users by functional team.

•      Issue with standard report of objects will be solved by raising an SR (Service Request).

Post Upgrade Activities

Testing

Table changes

New R12 tables                                              Old 11i Tables

•      AP_SUPPLIERS                              PO_VENDORS

•      AP_SUPPLIER_SITES_ALL            PO_VENDOR_SITES_ALL

•   CE_BANK_ACCOUNTS                 AP_BANK_ACCOUNTS_ALL

•      CE_BANK_ACCT_USES_ALL      AP_BANK_ACCOUNT_USES_ALL

•      XLA_EVENTS                                 AP_ACOCUNTING_EVENTS_ALL 

•      XLA_AE_HEADERS                       AP_AE_HEADERS_ALL

•      XLA_AE_LINES                              AP_AE_LINES_ALL 

Iteration 2 and 3

•      Iteration 2 will follow the same procedure as in iteration 1.

•      Setups and issues handled in iteration 1 will be observed.

•      Iteration 2 will have User Acceptance Test (UAT), the same setups will be carried forward to production

•      Iteration 3 is to reduce the down time.

Observations

•      Data match with previous version.

•      Path of reports uploaded is same as the application is picking from while running from front end.

•      Custom fonts are also moved.

•      Fresh clone should be used for initial technical backups or changes.