ESS Object Migration Document

FOR

ESSOESPC_NEW

Prepared by:
Developer: Satish Pawnikar ______
Team Lead: ___________________
QA: ___________________
Creation Date: 22 Nov 2005 ________
Last Updated by: ___________________
Last Update Date : ___________________
File Name: <Object Name>.doc
 Document Control

Change Record

Date Author Version Change Reference

04-AUG-03 1.0 Created

Dev Track Issue#
15-AUG-03 ESS 1.1 Updated Test results and Accepted/Rejected

The Change Record section of the document should identify

the date of the initial release of the document as well as any
additional versions. When possible the change record should
indicate the primary focus for changes within ESS new version.
The change reference should be used to indicate what section
was changed as well as the content.
 Table of Contents

DOCUMENT CONTROL......................................................................................................................

TABLE OF CONTENTS.......................................................................................................................

OBJECT MIGRATION PROCESS TEMPLATE..................................................................................

QUERY MODIFICATION.....................................................................................................................

CHANGE HISTORY.............................................................................................................................

TEST SCENARIO................................................................................................................................

COMMENTS.........................................................................................................................................

ESS TESTING......................................................................................................................................

ACCEPTANCE.....................................................................................................................................
 Object Migration Process Template
Environment to install : <11.0.3> to 11i

Step A) Installing Codes and Scripts

Files to be copied to the specified environment are:

S. No. From Directory(<11.0.3>) To Directory (11i) <11.0.3> File 11i File Name
Name
1. $CUSTOM_TOP/sql $CUSTOM _TOP/sql <old file name> <new file name>
2 $CUSTOM_TOP/reports/US $CUSTOM _TOP/reports/US <old file name> <new file name>

Step B) Creating Database Objects and Granting Privileges to Users/Roles

To create or upgrade database objects:

Script Name (Path) Database User Parameters

(e.g. $ CUSTOM _TOP/install/sql/filename.sql) Name
(APPS / XX etc.)
$ CUSTOM _TOP/install/sql/<file name> (View) Not Applicable
$ CUSTOM _TOP/install/sql/<file name> (Function) <parameter name> <data type>
$ CUSTOM _TOP/install/sql/<file name> <parameter name> <data type>
(Procedure)
$ CUSTOM _TOP/install/sql/<file name> (Package) <parameter name> <data type>
$ CUSTOM _TOP/install/sql/<file name> (Table) Not Applicable
$ CUSTOM _TOP/install/sql/<file name> Not Applicable
(Synonym)

Step C) Setting Up AOL for the Custom Modules and Codes

Concurrent Definitions

Register Form

Application Name Form Name

Define Value Set

Value Set Name Description Validation Type

Information for Table Value Set

Table Application
Table Name
Table Colum Siz MESSnin MESSnin Siz I ID Siz Where/Orde Additional
Colum n Type e g g Type e D Typ e r By Columns
n e

Edit Information for the Pair Value Set

Event Function

Define Values for Independent Value Set

Value Set Name Values

Define Concurrent Executable

<11.0.3> Executable File Name 11i Executable File Name

Define Concurrent Program

Application Name Concurrent Program SHORT Incompatible to itself (Y/N)

Name

Define Incompatible Programs

Application Name Concurrent Program Name Scope Type Available (Y/N)

Define Concurrent Program Parameter

S Paramete Descriptio Valuese Defaul Default Require Displaye Prompt Token

q r n t t Type Value d d

Define Menu

Application Menu Name New Menu(Y/N) If No, Specify Changes

Administer Report Set

Application Report Set Name

Define Request Group

Application Request Group Name Program To Add

 Change History
Explanation:
1. Object <old rdf name> is changed to <new rdf name> in 11i.
2. Concurrent program name is changed from <old concurrent program > to <new concurrent
program >.
3. Concurrent program short name is changed from <old program short name> to <new program
short name>
4. The concurrent program short name is changed in the report layout from <old program short
name> to <new program short name>
5. The label on the report is changed from <old label> to <new label>
6. Printer style is changed from <old style> to <new style>
7. The name of the printer is changed from <old printer name> to <new printer name>
8. The concurrent program is added to the following request groups:
<request group name1>
<request group name2>
<request group name3>
9. Changed system.dual to dual.
10. Created new view/function/procedure/package with the file name <file name> and uploaded the
SQL script file in $CUSTOM_TOP/install/sql directory.
11. Createdd the synonym <synonym name> and the script is uploaded to $CUSTOM_TOP/install/sql
directory.
12. Createdted the table <table name> and the script is uploaded to $CUSTOM_TOP/install/sql
directory.
13. Defined table dependent value set <value set name>
14. Defined Independent value set <value set name> and its values.
15. The following tables are changed in the query, report triggers and in formula columns
<old table name1> to <new table name1>
<old table name2> to <new table name2>
<old table name3> to <new table name3>
…..
16. In the query the following column changes are made.
<old table name.old column name> to <new table name.new column name>
<old table name.old column name> to <new table name.new column name>
<old table name.old column name> to <new table name.new column name>
…………
17. The hard codings in the query, triggers and formula columns are changed using the SQL query /
package.
18. In the query, triggers and formula columns, the joins are changed as follows:
<old join1> to <new join1>
<old join2> to <new join2>
<old join3> to <new join3>
………
 Test Scenario
Sl. Navigation Path Test Scenario Results
No
.
1. Responsibility: Parameters: Mandatory Completed successfully.
New layout matches with the old layout.
Navigation: Request id: <request id>
2. Responsibility: Parameters: All parameters Completed successfully.
New layout matches with the old layout.
Navigation: No data found. Request id: <request id>
3. Responsibility: Parameters: Other parameters Completed with error.
Request id: <request id>
Navigation:
4. SQL*Plus Execute the from SQL*Plus View / Function / Procedure / Package Created
successfully.
5. SQL*Plus Execute Alert Query from <Rel.11> - <n> rows selected
SQL*Plus

Output:
11.0.3  $<old CUSTOM_TOP>/out/<Output file> (naming convention - object
name.SlNo.Requestid.out)

11i  $<New CUSTOM_TOP>/out/<Output file> (naming convention – object

name.SlNo.RequestId.out)
$<New CUSTOM_TOP>/out/<Output file> (naming convention – object
name.SlNo.RequestId.out)
$<New CUSTOM_TOP>/out/<Output file> (naming convention – object
name.SlNo.RequestId.out)
 Comments
Developer:
1. Object migrated successfully.
2. The following hard codings have not been replaced as they are seeded values:
<seeded values list>
3. The concurrent program has incompatibility which has been copied from the source instance
4. The incompatible program <program name> doesn’t exist
5. No data found in Rel.11i as the following join failed:
<no dat found >
6. The concurrent program goes into error in both the releses with the error message: <error
message>
7. The concurrent program goes into error in Rel.11i with the error message: “<error message>”. The
error is due to <error >
8. The concurrent program is dependent on the procedure / function / package
“<procedure/function/package name>”
9. The above procedure / function / package has been created in Rel.11i as it did not exist
10. The procedure / function / package “<procedure/function/package name>” is referenced in the
concurrent program / procedure / function / package “<concurrent
program/procedure/function/package name>”

QA:
Checked the object setup.

Verified the document .

Checked the query changes and explain plans.

Verified the test scenarios.

Verified the User’s comments

QA Passed.

Team Lead:
Verified the Developer and QA comments and found Ok.
 ESS Testing
ESS Owner Comments/Modifications:

Issues:
 Acceptance

This object has been tested successfully by _____________________

and found to be working as expected.

Accepted: YES / NO

Date: _________