Regression%20Testing%20the%20Oracle%20E-Business%20Suite%20Presenter:%20A%20Kumar%20Acharya%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20Ramesh%20Padmanabhan

1
Regression Testing the Oracle E-Business
SuitePresenter A Kumar Acharya
Ramesh Padmanabhan
2
Agenda

• Introduction
• Background
• Problem Statement
• Objectives
• Solutions
• Implementation Details
• Lessons Learnt (Key Users)
• Q A

3
History of Marvell

• Founded 1995
• Fabless semiconductor
• Global operations
• Israel
• Europe (Germany, Italy, Switzerland)
• Asia Pacific (Singapore, India China)
• USA
• Annual Revenue (MM)
• FY 2002 288.8
• FY 2003 505.3
• FY 2004 819.8
• FY 2005 1,224.6
• FY 2006 1,670.3
• 1st Half FY 2007 1,095.2
• 4000 employees across US, Europe and Asia

4
Marvells Journey

• AUG 2001 Galileo Go-live on Oracle Apps 11.0.3
• DEC 2001 Upgrade Oracle Apps 11i (11.5.4)
• JAN 2002 Convert Oracle Apps to Multi-Org and
  Fiscal Calendar
• MAY 2002 Migrate North America to OM/FI to
  Oracle Apps 11i
• OCT 2002 Go-live OSFM
• OCT 2002 Implement Rosettanet PIP 3D8 with 10
  Sub Contractors
• AUG 2003 Install Oracle 10G iAS for Rosettanet
• DEC 2003 Upgrade Oracle Apps to 11.5.9
• JAN 2004 Migrate SysKonnect GmbH from BAAN to
  Oracle Apps 11i
• FEB 2004 Migrate RADLAN IL to Oracle Apps 11i
  (New Company)
• APR 2004 Install UTF8 to accommodate multi-byte
  characters
• SEP 2004 Implement Basic HRMS
• DEC 2004 Implement WEB based Employee Expense
  System for North America
• JAN 2005 Implement Compensation Work Bench
• JUL 2005 Implement Phase 1 ASCP (Wafer Buy Plan)
• AUG 2005 Upgrade Oracle Apps to 11.5.10
• JAN 2006 Integrate Q-Logic Acquisition
• FEB 2006 Integrate UTStarcom Acquisition
• APR 2006 Integrate National Semiconductor
  Acquisition

5
Problem Statement

• Numerous configuration changes, patches,
  enhancements and new product introductions were
  being migrated to production on a weekly basis.
• The knowledge to do end to end test does not
  exist with one individual.
• Some of the business processes had numerous steps
  and dependencies making those processes very
  complex to test.
• The high growth of the company and the volume of
  changes compromised the breadth of testing
• The manual testing processes did not have
  adequate audit trail to satisfy the SOX
  compliance needs and put a very heavy strain on
  the already stretched IT staff

6
Objective Production Control

• Establish QA as a critical part of the overall IT
  governance process
• Establish a central repository of interconnected
  and stand alone business functions that will
  need to be tested as part of the QA process
• Establish Integrated test data management
• Automate the testing process to increase the
  breadth of testing and reduce the burden on IT
  staff
• Ensure that the automated testing process
  generates adequate audit trail to meet the SOX
  compliance requirements
• Ensure that the solution implemented is both
  scalable and low maintenance

7
Solutions

• Marvell decided to implement the Entegration
  Attest Test management console.
• The Entegration Attest is a portal test console
  that is built to specifically address the testing
  needs of Oracle E-Business suite.
• Entegration Attest helped us address our
  objectives.
• Maintain a test script repository
• Automate the test process
• Generate Audit trail
• Flexibility and scalability
• Entegration Attest uses the industry leader
  Mercurys Quick Test Professional (QTP) as the
  execution engine.

8
Components of Entegration Attest
Test Run
Test Suite Comprises of multiple scenarios
Test Scenarios Logically organized functions will
make up a scenario
Test Functions The test functions are the lowest
building blocks and will correlate with
individual business functions
9
Creating a New Test Scenarios/Test Suites

• Identify the Reusable Components or Functions
• Select from existing function or Create a new
  function
• Logical grouping of Functions or Scenarios/ Test
  Suites
• Logical Business Flow to satisfy Test Cases
• Logical Grouping of Scenarios to create a Test
  Suites
• Logical Flow of In and Out Parameters
• Inputs required for Functions
• Static Input Parameter csv File
• Dynamic Input Parameter SQL Query
• Application Signature
• Oracle User Name
• Responsibility Name
• Instance Name

10
Entegration Attest Test Process
Intermediate Test Console User

• Static Data (csv File)
• SQL Statement

Create Functions
Create Scenarios
Create Data Queries
Create Test Cycles
Create Test Suites
Create Data Sets
Create Test Runs
View Results
Performed by Test Administrator
Performed by Intermediate User
Performed by Beginner User
11
Implementation Details
12
Architecture

• Components used during BPT

User Machine in Marvell intranet

• Windows Server
• QTP Software
• QTP Scripts

• Linux Server
• Entegration Attest
• Oracle Database
• Web Server

• Oracle ERP
• Stage
• Devt
• PrjX

13
BPT Details for Phase-I and II

• Order to Cash
• OM Functions
• AR Functions
• Item Master
• INV Functions
• BOM Functions
• Costing Functions
• General Ledger
• GL Functions
• Manufacturing
• MFG Functions
• OSFM Functions
• INV Functions
• WIP Functions
• Procure to Pay
• AP Functions
• PO Functions

14
OM Functions

• 1 OM Apply Hold on Order
• 2 OM Copy and Book
• 3 OM Create New Customer
• 4 OM Create New Order
• 5 OM Create RMA MSI Credit
• 6 OM Create RMA MSI Replacement
• 7 OM Pick Release
• 8 OM RMA Receive Returns
• 9 OM Release Hold
• 10 OM Reprice Item in Order Line
• 11 OM Ship Confirm
• 12 OM Ship Confirm and Back Order
• 13 OM Split Order Line
• 14 OM Transact Move Order

15
AR Functions

• 1 AR Changes to Invoice
• 2 AR Auto Invoice
• 3 AR Create Manual Credit Memo Transaction
• 4 AR Create New Invoice
• 5 AR Create Receipt Adjustment
• 6 AR Create Receipts
• 7 AR Create and Reverse Receipt
• 8 AR Get IC Invoice Details
• 9 AR Inter Company Invoice
• 10 AR Period Open Status Check
• 11 AR Print Invoice by Order Number
• 12 AR Print New Invoices
• 13 AR to GL Transfer

16
INV Functions

• 1 INV Account Alias Issue
• 2 INV Account Alias Receipt
• 3 INV Create Item
• 4 INV Create Location
• 5 INV Create Planner
• 6 INV Create Subinventory
• 7 INV Inventory Lot Merge
• 8 INV Inventory Lot Split
• 9 INV Inventory Lot Translate
• 10 INV Item Cross Reference
• 11 INV Org Period Open Status Check

17
GL Functions

• 1 GL Balance Inquiry
• 2 GL Enter Journal
• 3 GL Period Open Status Check
• 4 GL Query Journal

18
MFG Functions

• 1 BOM Co-Products
• 2 BOM Create Bill
• 3 BOM Create Common Bill
• 4 BOM Resource Creation
• 5 BOM Routing
• 6 CST Enter Item Cost
• 7 CST Submit Cost Rollup
• 8 MFG OSP Close Job using Form
• 9 MFG OSP Complete Job No Charges
• 10 MFG View MIL Requisition Details
• 11 MFG Wafer AutoCreate PO
• 12 MFG Wafer Check Item Onhand
• 13 MFG Wafer MVL Auto ISO Request Submit
• 14 MFG Wafer Requisition Import Submit
• 15 MFG Wafer Requisition Process Start
• 16 OSFM Create Lot Based Job Standard
• 17 OSFM Create Non Standard Lot Job
• 18 OSFM Lot Creation
• 19 OSFM Lot Merge

19
P2P Functions

• 1 AP Enter Invoices
• 2 AP Payments for Invoice
• 3 AP Period Open Status Check
• 4 AP Transfer to GL
• 5 PO Approval
• 6 PO Cancel PO
• 7 PO Change PO
• 8 PO Create Expense PO
• 9 PO Create Supplier
• 10 PO Period Open Status Check
• 11 PO Receive Shipments
• 12 PO Return Shipments

20
Results

• A comprehensive QA process was established for
  Marvell. All changes that needed to be
  implemented in production first needed to be
  implemented in a QA environment. Unless all tests
  passed, the code was not approved to migrate to
  production. This was established as part of the
  overall IT governance process.
• A comprehensive test script library of over 85
  test scripts covering all the major business
  process was created to support the above process
• What would take one week to test now takes six
  hours

21
Continued

• This solution allows us to test the applications
  using the same user and responsibility as in
  production without having to worry about
  maintaining the scripts for menu changes.
• There is complete audit trail for the tests
  executed with screen shots and time stamps
• The Entegration Attest is the single user
  interface for managing the tests and viewing test
  results.

22
Lessons Learnt

• Planning is a key to success.
• A phased implementation approach proved very
  beneficial to us.
• Do not expect 100 automation. Certain processes
  will still continue to be tested manually. Be
  sure to clearly identify processes that will lend
  themselves best to automated testing.
• Identify the Key Users or BSA for detail
  information and make sure they are engaged from
  start to finish
• Good and effective communication between QA
  functions and BSA on process changes
• Prepare to make a small investment in maintenance
  of your scripts. Changes in business processes
  may require some changes in the test scripts

23
Q A
24
Contact Details

• Name A Kumar Acharya
• E-Mail aacharya_at_marvell.com
• Name Ramesh Padmanabhan
• E-mail rpadmanabhan_at_entegration.com