Migration Steps in Oracle Apps

Methodologies Objectwise

SQL’s :

Get the sql script from the appropriate custom Top directory (say, $IAC_AR_TOP/sql).
Run the sql script in the 10.7 instance as mentioned in the technical document using the appropriate parameters and responsibility. Make a copy of the output generated.
Now, run the sql in the 11i instance using the mentioned parameters and responsibility..
Check for the compilation errors.
Identify if the compilation errors are due to the standard Apps objects.
Understand the logic of the sql and modify the objects wherever applicable. If there is a change in the functionality of that object in relation to the sql , modify the sql to handle the changed functionality in 11i appropriately.
Test it by passing similar parameters to ensure that the output matches in both the instances.
Analyze the performance in both the instances.

Pl*Sql/Packages/Procedures :

· Get the appropriate code or file from the database or top directory.
· Clearly understand the code logic and then compile it in the 11i. environment. If the same logic exists in 11i. then just modify the object change if there is any. Otherwise change the code based on the new logic in 11i.
Test it by passing similar parameters to ensure that the output matches in both the instances.
Analyze the performance in both the instances.
Reports :

· Get the corresponding report from the object list which has to be migrate then open it in reports 6i.
· During Migration you have to check for two things.
0 Compilation Errors.
0 Functionality Changes.
· For compilation error you have to compile the report in the 11i. environment. If there is any compilation errors then identify the object changes in 11i. (tables or columns) and made the corresponding changes in custom report and compile again.
· For Functionality changes check for, whether the report is customized from vanilla report or developed from scratch. If it is customized from vanilla then compare the actual 10.7 report and 11i. vanilla report, and identify if there is any functional changes in 11i. Incorporate the changes in the custom report. This can be done in two ways , first implement the new functionality in the 10.7 custom report , second customize the 11i. Vanilla report. Choose whichever is easy.
· After making the proper changes in the report then compare the report out put in both 10.7 and 11i. environments.
· Make the layout changes if you need after comparing the outputs.

Forms :

· Get the corresponding report from the object list which has to be migrated, then open it in forms 6i.
· Analyze if the form to be migrated is a standard form, which has been customized, or if it is a custom form.
· If it is a standard form which has been customized, identify the standard form in 11i and analyze it functionally in the 11i scenario. And identify the appropriate customizations to be done in 11i and appropriately make the changes in it.
· If it is a custom form, use flint60 utility in the unix environment.
· Command : flint60 –uc .fmb .fmb
· This utility will create a new fmb which will have the appropriate new apps forms standards included.
· It will also create a log file of messages named as . Analyze each of the messages in the log file and take appropriate actions wherever necessary. (Refer to Oracle Application Developer’s Guide section ‘Customization Standards’ for more details).
· Compile the form in the 11i environment to ensure that all the objects are valid. If there exists some functionality changes to the custom forms, keenly analyze the same and make appropriate changes accordingly.
· Test the form to ensure that it gives the same functionality as in 10.7.



Shell Scripts :

· Get the shell script and run it in 10.7 environment and 11I environment with the appropriate parameters and identical variable settings.
· Compare the results in the two environment.
· Ensure that the calls to specific programs (say sqlload or sqlplus) are successful and appropriate programs run successfully.
· If there exists any calls to the ‘Concsub’, check if the appropriate concurrent program has been modified in 11i and if so, modify the ‘Concsub’ call accordingly to call the modified 11i program along with appropriate programs. Also ensure that the ‘Concsub’ parameters have the appropriate 11i responsibility.
· Test the execution of the script in both environments and ensure that the results are the same in 11i environment.

Control File :

· Get the script and check if all the objects mentioned in the control file are valid in the 11i instance.
· Run the script using sqlload in 107 environment and 11I environment with the appropriate datafiles.
· If there exists a difference in the output between both instances, analyze accordingly and make proper changes to fix the issue in 11i.

PLL :

· Get the pll and open it in Oracle Forms Builder 6i and compile it and check.
· If any compilation errors, identify the appropriate objects (tables or columns) in 11i and fix it.
· In case of functionality changes, thoroughly understand the functionality of the pll and analyze its implications in the new 11i environment.
· If it is a standard pll which has been customized in 107, identify the new pll in 11i and include the appropriate customizations in it.
· If it is a custom pll, analyze and study the pll functionally and make appropriate changes related to 11i in the pll.

Related Articles to Read