You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Orange County Convention Center<br />
Orl<strong>and</strong>o, Florida | June 3-5, 2014<br />
<strong>Business</strong> <strong>Objects</strong> 3.1 <strong>to</strong> 4.1 <strong>Migr<strong>at</strong>ion</strong> <strong>and</strong> <strong>Benefits</strong> <strong>at</strong> <strong>Eli</strong> <strong>Lilly</strong><br />
Thyagarajan Balasubramanian<br />
Rajavelu K<strong>and</strong>asamy
Introduction<br />
• <strong>Eli</strong> <strong>Lilly</strong> is a global pharmaceutical company head<br />
quartered in Indianapolis, US with a net revenue of<br />
approxim<strong>at</strong>ely US $ 23 Billion <strong>and</strong> over 38,000<br />
employees.<br />
• Thyagarajan Balasubramanian (“Bala”), Senior Architect<br />
Global <strong>Business</strong> Intelligence <strong>and</strong> Analytics, <strong>Eli</strong> <strong>Lilly</strong><br />
• Rajavelu K<strong>and</strong>asamy (“Raj”), Technical Lead <strong>and</strong> Manager,<br />
SAP <strong>Business</strong><strong>Objects</strong> <strong>and</strong> Basis, IBM
Background<br />
• <strong>Eli</strong> <strong>Lilly</strong> has large investment globally in SAP ERP <strong>and</strong> SAP<br />
<strong>Business</strong><strong>Objects</strong>. Critical analytics for Finance, HR, SCM, <strong>and</strong><br />
Research on SAP <strong>Business</strong><strong>Objects</strong> (Web Intelligence, Crystal<br />
Reports)<br />
• Multiple versions of SAP <strong>Business</strong><strong>Objects</strong> exists (XIR2, XIR3,<br />
<strong>and</strong> BI4). Efforts underway <strong>to</strong> migr<strong>at</strong>e all versions <strong>to</strong> BI4.1<br />
• Successful implement<strong>at</strong>ions of Webi based SAP<br />
<strong>Business</strong><strong>Objects</strong> Mobile for Sales force in AsiaPac.<br />
• Leverage SAP BI4 for <strong>Business</strong> Analytics in the next 2 years<br />
with HANA.
LEARNING POINTS<br />
• Underst<strong>and</strong>ing the steps involved in planning <strong>and</strong><br />
execution of a large BOXI 3.1 <strong>to</strong> BI4.1 SP2 migr<strong>at</strong>ion for<br />
Finance <strong>at</strong> <strong>Eli</strong> <strong>Lilly</strong><br />
• Underst<strong>and</strong> the BI4.1 architecture <strong>and</strong> pl<strong>at</strong>form<br />
optimiz<strong>at</strong>ion steps <strong>at</strong> <strong>Eli</strong> <strong>Lilly</strong><br />
• Share the learning from our BI4.1 implement<strong>at</strong>ion<br />
• Know how we engaged pilot users prior <strong>to</strong> go-live for<br />
feedback <strong>and</strong> continuous improvement of the solution
Agenda<br />
• Architecture<br />
• Project Scope<br />
• Reports Inven<strong>to</strong>ry<br />
• Implement<strong>at</strong>ion Methodology<br />
• Project Tracking (Daily, Weekly St<strong>at</strong>us)<br />
• Scope containment<br />
• <strong>Migr<strong>at</strong>ion</strong> Str<strong>at</strong>egy<br />
• Universe <strong>Migr<strong>at</strong>ion</strong><br />
• Reports <strong>Migr<strong>at</strong>ion</strong><br />
• Testing Str<strong>at</strong>egy<br />
• <strong>Migr<strong>at</strong>ion</strong> Testing<br />
• Performance Testing <strong>and</strong> L<strong>and</strong>scape Optimiz<strong>at</strong>ion<br />
• User Pilot Testing<br />
• Roll-out Str<strong>at</strong>egy
BOXI 3.1 vs. BI 4.1 (Shared<br />
D<strong>at</strong>abase, Separ<strong>at</strong>e Pl<strong>at</strong>forms)<br />
Existing BOXI 3.1<br />
Reports<br />
Existing SAP<br />
<strong>Business</strong><strong>Objects</strong> BOXI 3.1<br />
Reports, Security<br />
New BI4.1 Pl<strong>at</strong>form<br />
New SAP <strong>Business</strong><strong>Objects</strong><br />
BI 4.1 Pl<strong>at</strong>form<br />
Existing BOXI 3.1 Pl<strong>at</strong>form<br />
SAP <strong>Business</strong><strong>Objects</strong><br />
BOXI 3.1 Pl<strong>at</strong>form<br />
M1,M2<br />
Modular<br />
Rapid Marts<br />
COPA<br />
Purch<br />
Old <strong>and</strong> New BOXI share the<br />
Same WHP d<strong>at</strong>abase<br />
Upgraded SAP<br />
<strong>Business</strong><strong>Objects</strong> BI 4.1<br />
Universes Reports,<br />
Security<br />
CCA<br />
AP<br />
AR<br />
FSCM<br />
SAP<br />
SCM<br />
SPL<br />
Sales<br />
HR<br />
Extract <strong>and</strong><br />
Merge Rapid<br />
Marts (SAP<br />
D<strong>at</strong>aServices)<br />
• Few Intraday d<strong>at</strong>a refresh, mostly<br />
nightly daily d<strong>at</strong>a refresh<br />
SAP Rapid Marts<br />
D<strong>at</strong>abase (WHP)<br />
(ORACLE)<br />
Upgraded<br />
Reports<br />
(BI 4.1)
SAP <strong>Business</strong><strong>Objects</strong> 3.1 <strong>and</strong> 4.1 Architecture<br />
BO 3.1CMS - Oracle 11g<br />
BO 4.1 CMS – DB2 9.7
SAP <strong>Business</strong><strong>Objects</strong> 3.1 <strong>and</strong> 4.1 Architecture<br />
Front End Clients<br />
Lap<strong>to</strong>p, Desk<strong>to</strong>p, Mobile<br />
Devices<br />
Load Balancer<br />
Web Tier<br />
Tomc<strong>at</strong> Server<br />
Intelligence Tier<br />
Processing Tier
Project Scope (Inven<strong>to</strong>ry)<br />
Object Name<br />
Universes (.UNV) 4<br />
User Groups 500+<br />
User IDs 3500+<br />
Webi Reports 9500+<br />
Webi Reports Tabs<br />
Reporting Environment Summary<br />
Total Number of <strong>Objects</strong><br />
Ranging from 4 <strong>to</strong> 80 Tabs per Report<br />
Global Single Instance <strong>Business</strong> <strong>Objects</strong> <strong>Business</strong> Intelligence Pl<strong>at</strong>form <strong>and</strong> SAP<br />
ECC. D<strong>at</strong>amart d<strong>at</strong>abase residing here in the U.S. (Indy)<br />
Oracle 11g based SAP Rapid Marts d<strong>at</strong>amart; Source SAP ECC 6.0; SAP<br />
D<strong>at</strong>aServices ETL<br />
Self Service Web Intelligence based reporting; Webi Reports developed by<br />
Financial Analysts (not IT)<br />
Management Reporting for Analysts through C-Level execs<br />
First implemented in 2010 with 200 users. Users in all continents.
Project Implement<strong>at</strong>ion Methodology<br />
• Highly <strong>Business</strong> Critical Reporting migr<strong>at</strong>ion<br />
• Narrow window <strong>to</strong> implement (January-June, 2014)<br />
• Dual pl<strong>at</strong>form (BO 3.1 & 4.1) availability with practically<br />
no freeze on changes in 3.1.<br />
• Follow the Sun On-site, Off-shore model with an IT<br />
Vendor as implement<strong>at</strong>ion partner. One expert<br />
resource in Indy, Six experienced resources in India<br />
(one expert <strong>and</strong> 5 mid-level resources)<br />
• 12 weeks of conversion <strong>and</strong> testing in Non-Prod by<br />
developers <strong>and</strong> BI-COE; 6-8 weeks of “user pilot”<br />
testing in Production by real users.
Project St<strong>at</strong>us Dashboard<br />
Current St<strong>at</strong>us<br />
Deliverables<br />
Budget/Cost<br />
Schedule<br />
Scope<br />
Overall Summary<br />
• Testing completed for 110 report tabs; From overall testing progress st<strong>and</strong>point<br />
– we are <strong>at</strong> 660 reports tested vs 680 planned. Reasons: Reprioritized Pilot User<br />
Testing & Onboarding Startup Activities <strong>and</strong> Team is working on Issue fixes in<br />
the Reports. Planning <strong>to</strong> complete the targeted reports in the upcoming weeks.<br />
• D<strong>at</strong>a Security Testing in Progress, completed testing of 160 Restrictions in the<br />
Universes.<br />
• User groups testing is in Progress completed 230 User groups.<br />
• Pilot User Testing <strong>and</strong> Onboarding Start up Activities in Progress
Project Tracking <strong>and</strong> St<strong>at</strong>us Reporting
<strong>Migr<strong>at</strong>ion</strong> Str<strong>at</strong>egy
<strong>Migr<strong>at</strong>ion</strong>/Conversion Tools<br />
Tools<br />
Upgrade Management Tool<br />
Promotion Management Tool<br />
Purpose<br />
This is used <strong>to</strong> migr<strong>at</strong>e the BI Content from SAP BO 3.1 Environment <strong>to</strong> the SAP BO 4.1 Non<br />
Production Environment.<br />
This is used <strong>to</strong> Migr<strong>at</strong>e the BI 4.1 Content from SAP BO 4.1 Development Environment <strong>to</strong> SAP<br />
BO SAP BO 4.1 Production Environment<br />
DiffPdf (Public Domain)<br />
This is used <strong>to</strong> verify the form<strong>at</strong> <strong>and</strong> D<strong>at</strong>a content of the Reports from both the environments<br />
(3.x <strong>and</strong> 4.1) <strong>and</strong> highlight the differences in the reports. This is the primary <strong>to</strong>ol used in Report<br />
Testing.
<strong>Migr<strong>at</strong>ion</strong> Str<strong>at</strong>egy<br />
Task<br />
<strong>Migr<strong>at</strong>ion</strong> of Universes,<br />
Reports <strong>and</strong> User Groups<br />
from BO 3.1(BOP) <strong>to</strong> BO 4.1<br />
Development(BJJ)<br />
environment<br />
Description<br />
• <strong>Migr<strong>at</strong>ion</strong> of Finance Rapidmarts Universes, Reports, web services, schedules, calendars, Report instances<br />
<strong>and</strong> User Groups along with security from BO 3.1 Production <strong>to</strong> BO4.1 Development Environment by Using<br />
Incremental Upgrade option in Upgrade Management Tool<br />
Post <strong>Migr<strong>at</strong>ion</strong> Verific<strong>at</strong>ion • Evalu<strong>at</strong>e the success of Upgrade Process<br />
• Correct any problems indic<strong>at</strong>ed in the UMT Log file<br />
• Set up a folder structure as same as BOP<br />
Testing Phase • Regression Testing of Reports, Universes, D<strong>at</strong>a Security <strong>and</strong> User Security. Please refer the Testing Str<strong>at</strong>egy<br />
document for more details<br />
Fix the Issue • Fix the Identified issues in the Testing Phase <strong>and</strong> execute all the Test cases again<br />
Identify changed content • Identify the changed content in BO 3.1 Environment by running query on Query Builder or Get the<br />
inform<strong>at</strong>ion from Users<br />
Move the changed Content<br />
from BO 3.1 <strong>to</strong> BO 4.1<br />
Development<br />
• <strong>Migr<strong>at</strong>ion</strong> of changed content Universes , Reports <strong>to</strong> BO 4.1 Development <strong>and</strong> do regression testing for the<br />
newly upgraded content<br />
Promote Reports ,<br />
Universes, User Groups &<br />
Users <strong>to</strong> BO 4.1 Production<br />
• <strong>Migr<strong>at</strong>ion</strong> of Finance Rapidmarts Universes, Reports, User Groups <strong>and</strong> User along with security from BO<br />
4.1 development Environment <strong>to</strong> BO4.1 Production Environment<br />
Performance Testing • Execute set of Reports in BO 4.1 Production environment <strong>and</strong> capture the execution by running the audit<br />
reports <strong>and</strong> closely with <strong>Lilly</strong> IT team<br />
User Acceptance Testing • Support UAT<br />
• Fix defects <strong>and</strong> execute testing cycles (again)<br />
• Prepare guide <strong>to</strong> deploy solution in production environment
Testing Str<strong>at</strong>egy (3.1 vs 4.1)<br />
Universe Testing<br />
• Universe structure, D<strong>at</strong>a found<strong>at</strong>ion summary,<br />
<strong>Objects</strong>, joins, conditions, Row level & Table level<br />
access restrictions, query limits, query options. Run<br />
Sample reports <strong>to</strong> check results, export universe etc<br />
Reporting Testing<br />
Security Testing<br />
Performance Testing<br />
• Report open, refresh, prompts, input controls,<br />
filters, export <strong>to</strong> XL, PDF, edit<br />
• DiffPDF - # of pages, charts, font/form<strong>at</strong>ting, page<br />
orient<strong>at</strong>ion, table form<strong>at</strong>s<br />
• Object Security: Folders, Reports, users <strong>and</strong> roles,<br />
Functional Security: Drilldown, scheduling,<br />
publishing<br />
• Authentic<strong>at</strong>ion<br />
• D<strong>at</strong>a Security: Row level<br />
• Report Open, Prompts display, D<strong>at</strong>a Retrieve, d<strong>at</strong>a<br />
display on selected reports <strong>and</strong> their report tabs<br />
• Au<strong>to</strong>m<strong>at</strong>ed login/logout; Report open, Report<br />
Refresh using LoadRunner <strong>to</strong> simul<strong>at</strong>e mass users
Test Results Verific<strong>at</strong>ion<br />
Document<br />
Tracking Sheet<br />
Report Test Cases & Results<br />
Description<br />
Tracking Sheet is used <strong>to</strong> track the list of<br />
Reports, Universes, User Groups & Users<br />
migr<strong>at</strong>ion <strong>and</strong> Testing<br />
Capture the report test results<br />
Universe Test cases & Results Capture the Universe Test results<br />
User Security & D<strong>at</strong>a Security Capture the user security & d<strong>at</strong>a security<br />
Defects Tracking<br />
Capture issues <strong>and</strong> their resolutions
Roll-Out Str<strong>at</strong>egy<br />
• Decision – Migr<strong>at</strong>e all users or in b<strong>at</strong>ches from 3.1<br />
• B<strong>at</strong>ch migr<strong>at</strong>ion will stretch go-live over several weeks or<br />
months. With Dual pl<strong>at</strong>form, will be difficult <strong>to</strong> freeze<br />
development/changes.<br />
• We decided hybrid approach – first set of expert users<br />
identified during user pilot <strong>and</strong> then rest of the users. This<br />
shortened migr<strong>at</strong>ion <strong>to</strong> just one month<br />
• Support – During go-live have your support lined up <strong>to</strong><br />
answer/fix issues quickly<br />
• Provide succinct upd<strong>at</strong>es <strong>to</strong> key stakeholders before<br />
<strong>and</strong> after go-live. Get them on your side.
BEST PRACTICES<br />
• Adjust memory for UMT (Upgrade management Tool)<br />
before migr<strong>at</strong>ion<br />
• Make sure BI 4 System L<strong>and</strong>scapes are optimized <strong>to</strong> have<br />
dedic<strong>at</strong>ed servers for CMS, Web Server <strong>and</strong> Processing<br />
Server for optimal performance<br />
• Disable APS th<strong>at</strong> are not in use<br />
• Fine tuned memory for various APS<br />
• Adjust web server memory (in our case Tomc<strong>at</strong> server<br />
memory)<br />
• Perform risk based testing of Reports<br />
• Perform pre go-live testing with subset of users before<br />
releasing the system <strong>to</strong> everyone
KEY LEARNINGS<br />
• Prepare <strong>and</strong> share migr<strong>at</strong>ion plan, risks, <strong>and</strong> benefits with key<br />
stakeholders<br />
• Scope the project <strong>and</strong> select project team carefully<br />
• Perform risk based testing (not test every single report in the system)<br />
• Track project st<strong>at</strong>us <strong>and</strong> read-out <strong>to</strong> stakeholders once a month<br />
• Collect artifacts of issues <strong>and</strong> resolutions. It will serve as a knowledge<br />
base for support<br />
• Tune the system on a continuous basis by g<strong>at</strong>hering metrics during<br />
migr<strong>at</strong>ion, testing phases.<br />
• Moni<strong>to</strong>r the system closely <strong>and</strong> adjust settings
FOLLOW US
THANK YOU<br />
THANK YOU FOR PARTICIPATING<br />
Please provide feedback on this session by completing<br />
a short survey via the event mobile applic<strong>at</strong>ion.<br />
SESSION CODE: <strong>0206</strong><br />
For ongoing educ<strong>at</strong>ion on this area of focus,<br />
visit www.ASUG.com
Backup Slides
Testing Progress – St<strong>at</strong>us Dashboard for week ending 3/7
Testing Progress – St<strong>at</strong>us Dashboard as of EOD 3/10
Summary of Issues identified during Testing (Cumul<strong>at</strong>ive)
Summary of Issues identified during Testing (Cumul<strong>at</strong>ive)
Change language