1. Survivor! Oracle Financials 11i Upgrade Release 10.6 character/10.7 NCA to 11i

2. 2 Mirant  The Premier Global Integrated Power Provider We see the opportunity to change the world with our energy u A global competitive energy company with leading energy marketing and risk management expertise u Integrated business model:  Mirant develops, constructs,owns, and operates power plants  Sells electricity, gas, and other energy related commodity products u Extensive operations in the Americas, Europe, and Asia  Assets of $17.7 billion  Year 2000 earnings of $366 million  More than 18,000 MW of electric generating capacity worldwide  Formerly known as Southern Energy Inc. u A subsidiary of the Southern Company  The Premier Global Integrated Power Provider We see the opportunity to change the world with our energy u A global competitive energy company with leading energy marketing and risk management expertise u Integrated business model:  Mirant develops, constructs,owns, and operates power plants  Sells electricity, gas, and other energy related commodity products u Extensive operations in the Americas, Europe, and Asia  Assets of $17.7 billion  Year 2000 earnings of $366 million  More than 18,000 MW of electric generating capacity worldwide  Formerly known as Southern Energy Inc. u A subsidiary of the Southern Company

3. 3 What Happened?  April 17, 2000 - Southern Company Board Announces IPO of Southern Energy u offering up to 19.9% of ownership u subsequent spinoff of remaining ownership to SoCo shareholders within 12 months  April 2, 2001 - Spinoff of Southern Company ownership u Mirant separation from Southern Company is completed  April 17, 2000 - Southern Company Board Announces IPO of Southern Energy u offering up to 19.9% of ownership u subsequent spinoff of remaining ownership to SoCo shareholders within 12 months  April 2, 2001 - Spinoff of Southern Company ownership u Mirant separation from Southern Company is completed

4. 4 Mirant Business Responsibilities  Identify and replace Southern Company shared services u Human Resources, Payroll, Treasury, Tax, Finance  Oracle HR/Payroll apps selection forced early upgrade of Oracle Financials to release 11i  Hardware Evaluation, Selection, and Implementation u existing HP K570 server would not meet new requirements u purchased 2 HP N4000 servers - one Test and one Production box  Focus on Oracle HR and Payroll applications implementation  Identify and replace Southern Company shared services u Human Resources, Payroll, Treasury, Tax, Finance  Oracle HR/Payroll apps selection forced early upgrade of Oracle Financials to release 11i  Hardware Evaluation, Selection, and Implementation u existing HP K570 server would not meet new requirements u purchased 2 HP N4000 servers - one Test and one Production box  Focus on Oracle HR and Payroll applications implementation

5. 5 Oracle Financials 11i Upgrade Background  Mirant Oracle Financials u Implemented Financials 8.3 beginning last Qtr 1992 u Currently 225 Oracle Financials users located across U.S.  Managing a 3 Ring Circus u Ongoing Production Support for Financials 10.7 NCA and Character versions u Backlog of Financials enhancement and customization requests u Planning and executing the Oracle Financials 11i upgrade  Recognized need for external expertise u Partnered with System Architechs to manage and execute the Financials 11i upgrade  Mirant Oracle Financials u Implemented Financials 8.3 beginning last Qtr 1992 u Currently 225 Oracle Financials users located across U.S.  Managing a 3 Ring Circus u Ongoing Production Support for Financials 10.7 NCA and Character versions u Backlog of Financials enhancement and customization requests u Planning and executing the Oracle Financials 11i upgrade  Recognized need for external expertise u Partnered with System Architechs to manage and execute the Financials 11i upgrade

6. 6 Oracle Financials 11i Upgrade Project Scope and Approach  Base software upgrade and retrofit of customizations  Limited deployment of new functionality  Freeze production environment for better manageability  Isolate Database and Applications upgrade u Separate database upgrade using interoperability patches u Allow stepped approach to migrate to new HP boxes u Minimize outage window needed for upgrades  Financials 11i versions and release dates u Production upgrade - Financials 11.5.2 - completed Mar. 12, 2001  Base software upgrade and retrofit of customizations  Limited deployment of new functionality  Freeze production environment for better manageability  Isolate Database and Applications upgrade u Separate database upgrade using interoperability patches u Allow stepped approach to migrate to new HP boxes u Minimize outage window needed for upgrades  Financials 11i versions and release dates u Production upgrade - Financials 11.5.2 - completed Mar. 12, 2001

7. 7 Oracle Financials 11i Upgrade Project Organization  Develop communication plan and identify stakeholders  Prepare documentation portfolio and archive folders u project plan, customization documentation, change log, issue log, test scripts, training materials, etc.  Secure appropriate internal resources  Identify date for production upgrade - changed twice  External resources used: u project manager, functional (2), technical (2), DBA (part-time) u Approximately 2700 external resource man-hours to complete  Develop communication plan and identify stakeholders  Prepare documentation portfolio and archive folders u project plan, customization documentation, change log, issue log, test scripts, training materials, etc.  Secure appropriate internal resources  Identify date for production upgrade - changed twice  External resources used: u project manager, functional (2), technical (2), DBA (part-time) u Approximately 2700 external resource man-hours to complete

8. 8 Oracle Financials 11i Upgrade Upgrade Assistant and EMM  Available on Oracle Metalink under Apps 11i Information  Excel file of all Category 1-6 upgrade steps  Mirant enhanced internally to identify relevant tasks and assign resources  Oracle’s EasiPath Migration Method (EMM) is an option - for a price  Available on Oracle Metalink under Apps 11i Information  Excel file of all Category 1-6 upgrade steps  Mirant enhanced internally to identify relevant tasks and assign resources  Oracle’s EasiPath Migration Method (EMM) is an option - for a price

9. 9 Oracle Financials 11i Upgrade Upgrade Assistant Examples Original Revised

10. 10 Oracle Financials 11i Upgrade Customization Management  Research infrastructure changes to determine impact u Developed scripts to search sql scripts and reports  Developed customization workbook for recording impact, tracking changes and managing future change  Developed customization statistics summary for management reporting and monitoring progress to plan  Customization summary: u 86 sql scripts u 48 host/shell scripts u 7 forms u 69 reports u 16 extensions (packages, procedures, triggers) u 67 tables, 24 indexes, 19 views  Research infrastructure changes to determine impact u Developed scripts to search sql scripts and reports  Developed customization workbook for recording impact, tracking changes and managing future change  Developed customization statistics summary for management reporting and monitoring progress to plan  Customization summary: u 86 sql scripts u 48 host/shell scripts u 7 forms u 69 reports u 16 extensions (packages, procedures, triggers) u 67 tables, 24 indexes, 19 views

11. 11 Oracle Financials 11i Upgrade Customization Workbook

12. 12 Oracle Financials 11i Upgrade Customization Statistics

13. 13 Oracle Financials 11i Upgrade Supplier Banks  Supplier banks no longer supported in 11i  Category 2 Payables pre-upgrade step #2: u run apmsbrep.sql script  Review output for incomplete supplier banks  Fix incomplete records before running the upgrade  Oracle has patch 747306 to fix incomplete supplier banks u Populates bank_number and branch_number with “UNKNOWN”  Mirant developed semi-automated process to fix all errors u Loaded ABA banking information from third-party into temp table u Developed scripts to cleanse incomplete supplier banks u Manual updates to fix the leftovers u Resulting in 100% accuracy  Supplier banks no longer supported in 11i  Category 2 Payables pre-upgrade step #2: u run apmsbrep.sql script  Review output for incomplete supplier banks  Fix incomplete records before running the upgrade  Oracle has patch 747306 to fix incomplete supplier banks u Populates bank_number and branch_number with “UNKNOWN”  Mirant developed semi-automated process to fix all errors u Loaded ABA banking information from third-party into temp table u Developed scripts to cleanse incomplete supplier banks u Manual updates to fix the leftovers u Resulting in 100% accuracy

14. 14 Oracle Financials 11i Upgrade Supplier Banks  How 10.x supplier banks are mapped to 11i: u Bank Name  po_vendor_sites.bank_number => ap_bank_branches.bank_name  po_vendor_sites.bank_number => ap_bank_branches.bank_number u Bank ABA Number  po_vendor_sites.bank_num => ap_bank_branches.bank_num  po_vendor_sites.bank_num => ap_bank_branches.bank_branch_name u Bank Account Name  po_vendor_sites_all.bank_account_name => ap_bank_accounts_all.bank_account_name u Bank Account Number  po_vendor_sites_all.bank_account_num => ap_bank_accounts_all.bank_account_num u Missing link between suppliers and banks is ap_bank_account_uses_all  How 10.x supplier banks are mapped to 11i: u Bank Name  po_vendor_sites.bank_number => ap_bank_branches.bank_name  po_vendor_sites.bank_number => ap_bank_branches.bank_number u Bank ABA Number  po_vendor_sites.bank_num => ap_bank_branches.bank_num  po_vendor_sites.bank_num => ap_bank_branches.bank_branch_name u Bank Account Name  po_vendor_sites_all.bank_account_name => ap_bank_accounts_all.bank_account_name u Bank Account Number  po_vendor_sites_all.bank_account_num => ap_bank_accounts_all.bank_account_num u Missing link between suppliers and banks is ap_bank_account_uses_all

15. 15 Oracle Financials 11i Upgrade Workflow  Get trained on Workflow before the upgrade  Account Generator replaces Release 10 Flexbuilder  Document business rules for modified Flexbuilder rules  Generate accounts using Flexbuilder rules is an option in 11i  Workflow impact at Mirant: u PO and requisition distribution accounts - we used the default u PO and requisition approval process for notifications u FA Generate Accounts - see next slide  Get trained on Workflow before the upgrade  Account Generator replaces Release 10 Flexbuilder  Document business rules for modified Flexbuilder rules  Generate accounts using Flexbuilder rules is an option in 11i  Workflow impact at Mirant: u PO and requisition distribution accounts - we used the default u PO and requisition approval process for notifications u FA Generate Accounts - see next slide

16. 16 Oracle Financials 11i Upgrade FA Generate Accounts  New Assets concurrent process to create account combinations for each asset  Generates a plethora of accounts for each asset - whether used or not  Difficult to resolve problems - but there is a way  Profile option available to control number of workers to accelerate the process  First execution involves significant processing time  Process improved from 11.0.x to 11i - now it reports all errors to a log rather than reporting errors incrementally  Mirant added minor customization to FA generate accounts  New Assets concurrent process to create account combinations for each asset  Generates a plethora of accounts for each asset - whether used or not  Difficult to resolve problems - but there is a way  Profile option available to control number of workers to accelerate the process  First execution involves significant processing time  Process improved from 11.0.x to 11i - now it reports all errors to a log rather than reporting errors incrementally  Mirant added minor customization to FA generate accounts

17. 17 Oracle Financials 11i Upgrade ADI Spreadsheets  Research identified numerous versions of ADI deployed  Used Citrix solution to standardize single version throughout the company  Murphy’s Law appears...  ADI worksbooks have one hidden sheet for each sheet in the workbook u “Criteira X ” is the hidden sheet name, where X represents the sheet number in order from left to right u Contains pointers to database that needed to be updated  Developed Excel macro to automatically update older workbooks - preserving precious time and energy  Research identified numerous versions of ADI deployed  Used Citrix solution to standardize single version throughout the company  Murphy’s Law appears...  ADI worksbooks have one hidden sheet for each sheet in the workbook u “Criteira X ” is the hidden sheet name, where X represents the sheet number in order from left to right u Contains pointers to database that needed to be updated  Developed Excel macro to automatically update older workbooks - preserving precious time and energy

18. 18 Oracle Financials 11i Upgrade Receivables  Significant infrastructure changes in 11i on customers  Trading Community Architecture (TCA)/Customer Model u HZ_PARTIES, HZ_LOCATIONS, HZ_CUST_SITE_USES… u Beware of the “TCA” patch - many problems in 11.5.2  Review Customer addendum from Metalink u Apps 11i Information > Technical Articles, under Documentation heading for Financials select Accounts Receivable u Two important documents to review: u Oracle Receivables Customer Addendum Release 11i 276828 u Doc Addendum: Customer Find/Enter User Interface Update 279687  Significant infrastructure changes in 11i on customers  Trading Community Architecture (TCA)/Customer Model u HZ_PARTIES, HZ_LOCATIONS, HZ_CUST_SITE_USES… u Beware of the “TCA” patch - many problems in 11.5.2  Review Customer addendum from Metalink u Apps 11i Information > Technical Articles, under Documentation heading for Financials select Accounts Receivable u Two important documents to review: u Oracle Receivables Customer Addendum Release 11i 276828 u Doc Addendum: Customer Find/Enter User Interface Update 279687

19. 19 Oracle Financials 11i Upgrade Testing Strategy  Acceptance testing requires management support  How you manage it is another challenge  Establish dedicated facilities for acceptance testing  DO NOT limit the number of resources involved in testing  Perform upgrade simulations u Mirant results: Alpha (weeks), Beta (days), Gamma (hours)  Keep copious notes organized and centralized u Documents known issues at go-live u Identifies custom post-upgrade steps  Acceptance testing requires management support  How you manage it is another challenge  Establish dedicated facilities for acceptance testing  DO NOT limit the number of resources involved in testing  Perform upgrade simulations u Mirant results: Alpha (weeks), Beta (days), Gamma (hours)  Keep copious notes organized and centralized u Documents known issues at go-live u Identifies custom post-upgrade steps

20. 20 Oracle Financials 11i Upgrade Preparing for Production  What Mirant did to support a successful upgrade to 11i: u Developed milestones spreadsheet to calculate and estimate actual and revised completion times during the upgrade u Organized two conference calls during the weekend to discuss progress and estimated completion time u Established dedicated email address and phone number for reporting problems u Staffed centralized problem tracking and resolution group u Morning meetings with key stakeholders to discuss issues  What Mirant did to support a successful upgrade to 11i: u Developed milestones spreadsheet to calculate and estimate actual and revised completion times during the upgrade u Organized two conference calls during the weekend to discuss progress and estimated completion time u Established dedicated email address and phone number for reporting problems u Staffed centralized problem tracking and resolution group u Morning meetings with key stakeholders to discuss issues

21. 21 Oracle Financials 11i Upgrade I Wish...  The production date didn’t change twice  We had more resources assigned on acceptance testing  We upgraded to multi-org  HRMS didn’t create a new business group  We tested the Citrx/ADI solution outside the project team  The production date didn’t change twice  We had more resources assigned on acceptance testing  We upgraded to multi-org  HRMS didn’t create a new business group  We tested the Citrx/ADI solution outside the project team