WEEK: 2-3 PROJECT SUMMARY: Project Initiation and Team Selection Week Start Week End Project Name Prepared By 18th July 2016 29th July 2016 SAP Business Objects Migration CITIBANK Siva Chengalvala TASK OVERVIEW Task Identification After the formation of the group we did a research on what project my team is capable off. Based on the suggestions from the tutor and the project details on capstone uploaded on moodle we did a web search on the project. We thought of taking up an inventory project, since I have worked on SAP I have suggested my team mate to take up an SAP project. After doing a research on SAP we identified that CITIBANK is still using the older version of Business Objects3.1 which is out of date and SAP is not providing any support which is direct threat to data and we suggested them that we will perform a migration of the data in form of reports to the latest 4.1 version which is a 55 days project Work Done I have approached CITIBANK to discuss the project and our approach on why we want to do the migration. The client was really happy on our proposal and asked to start the migration. I prepared the project plan, work break down structure and the budget on how much its going to cost and the resources required and the environment. Submitted project proposal and plan. CHALLENGES FACED I am not that good at using Microsoft project so it took me time to create the WBS and allocate the resources. As the data of the client is very sensitive we had to do test migration at our office CQU campus and based on the results we should migrate it in production environment. To do so I had to make sure that the environment is ready at both the sites. CONCLUSION I discussed my findings at CITIBANK with my teammate and the platform readiness at test and production environments. I allocated the work that should be done in-order to finish the project in the assigned time frame. WEEK: 4 PROJECT SUMMARY: Project Kickoff Week Start Week End Project Name Prepared By 1st August 2016 5th August 2016 SAP Business Objects Migration CITIBANK Siva Chengalvala TASK OVERVIEW Task identification Identifying the process for getting the pre-requisites like access the repository of the organization to know how many reports to be migrated. To identify the the total number of reports for migration Test environment readiness and steps required for migration. Work Done Worked on progress report 1 showing the milestones completed from the start of the project I identified 1000 reports that are there in production in different applications like Trims Eye, Trims, Custody, Multi fond, tbms, Easy Pay, Clearing Switch. As a project manager I took the responsibility of installing Business Objects Enterprise 4.1 at test environment For any organization to get real time information we need access cards CHALLENGES FACED Though my team mate is good at developing and testing he is not aware of the project type and it took me time in explaining the project details, approach. I have faced issues with installing Business Objects 4.1 at test environment due to systems becoming slow and problems with configuring the server and creating a separate server for migration. I had to contact the admin a couple of times to resolve the right issues as I could not access with the default rights. Since the server of CQU is sitting at its main campus I had issues with getting disconnected from the main server. CONCLUSION Before starting a project we have to make sure that all the prerequisites are met with time to time meeting agendas and implementing the planned project plan and executing it without any delay. WEEK: 5 PROJECT SUMMARY: Key minutes and technical design Week Start Week End Project Name Prepared By 8th August 2016 12th August SAP Business Objects Migration CITIBANK Siva Chengalvala TASK OVERVIEW Task Identification Test the environments installed To discuss what how to approach the migration. To make sure that the report is not running during migration Work Done Post installing of Business Objects 4.1 I tested the environment whether it is working without any issues or not at both production and test platforms. I have discussed the migration approach with my team mate from where to start and what reports to migrate after the environment test. I also assessed the feasibility of the reports whether they can be migrated without any issues and the rights and filters that should be applied after migration. CHALLENGES FACED It was hard to find sample reports in the CQU cmc to perform sample migartion It was difficult to find the actual number of reports at CITIBANK as the audit software was showing all the reports instead of the actual reports in UAT. CONCLUSION Before diving into the actual migration environment test is very important because after the start of the project if I find any issue doing a rollback will be difficult. BREAK WEEK: 15TH August 2016 – 21st August 2016. WEEK: 6 PROJECT SUMMARY: Technical Upgrade Week Start Week End Project Name Prepared By 22nd August 2016 26th August 2016 SAP Business Objects Migration CITIBANK Siva Chengalvala TASK OVERVIEW Task Identification Perform sample migration with the reports available in CQU repository Issues in sample migration Progress report 2 Work Done I migrated the sample business objects reports that are available in CQU repository and which are not in use to test whether all the requirements given by CITIBANK in migration are met or not. I also created and submitted the progress report portraying the milestones achieved till date. CHALLENGES FACED The reports that I got for sample migration don't have the relevant universes to check the joins. It took time to find the actual universes as they were in another server. Due to connectivity issues I performed the sample upgrade in standalone mode. In business objects 4.1 I have found that the rights and filters are not applied which were there in its predecessor. I migrated them manually by applying the filters manually. CONCLUSION Performing a test upgrade in the home environment is always a best practice so that I can know what all the issues that can arise and be prepared with the solution while doing in production environment. WEEK: 7-8 PROJECT SUMMARY: Desktop Intelligence and BOE XI R2 report migration Week Start Week End Project Name Prepared By 29th August 2016 9th September 2016 SAP Business Objects Migration CITIBANK Siva Chengalvala TASK OVERVIEW Task Identification Most of reports are in Desktop Intelligence (Deski 3.0 Reports) Identify the schema Identify the tool required for reports in BOE R2 and BOE XI 3.x Upgraded and converted 1000 reports To identify the reports that are not running while upgrading Identify the type of upgrade Work Done Submitted the progress report 3 portraying the progress of the project I implemented the multiple star schema in BOE4.1 The result I got from audit database is that most of the reports are in Deski 3.0 which is not a direct upgrade and upgrade manager does not work for deski 3.0 reports. Upgrading BOE RS and BOE xi 3.x is a simple direct process which I did using upgrade manager and or Deski Reports I used Report Conversion Tool as they cannot be converted directly. I took care while migrating that none of the reports are been used while upgrading simultaneously I implemented Life cycle manager for my upgrade style by creating a duplicate server and taking biar files so that if there is any issue I can do a roll back without data loss CHALLENGES FACED The first few reports I upgraded I implemented the In place upgrade as the system goes live immediately without the backup of the old one. I came to know from the client that that some of rights that are used previously and the blocks and filters that were there prior to upgrading were missing in the new environment and it became difficult for me to apply the same as did not have a copy. So I started using the parallel upgrade using s biar files to make the data more secure. I had issues in migration of deski reports CONCLUSION By the end of week 8 I successfully completed the migration with issues still to be resolved. I analyzed the risk involved to the stakeholders by identifying the critical tasks. WEEK: 9 PROJECT SUMMARY: Identifying and fixing issues Week Start Week End Project Name Prepared By 12th September 2016 16th September 2016 SAP Business Objects Migration CITIBANK Siva Chengalvala TASK OVERVIEW Task Identification Resolving the issues after migration from 3.1 to 4.1 Identify the instances needed in new version Work Done In Deski 3.1 there are many instances which are applied in the newer version. I double checked the what instances are needed in newer version with the client and dropped all of them in 4.1. Objects that are hidden in 3.0 cannot be hidden in 4.1. I converted the 250 deski reports in Tryops application manually as they were not converted using report conversion tool. I did all of them from scratch by importing objects and classes in BO 4.1 launch pad. CHALLENGES FACED Across options for crosstabs in BO 4.1 are not there as there is no work around I applied them based on its actual functionality I edited the formula in webi 4.1 using computational context I need to migrate 350 reports manually in tryops, EPMS and DDE applications which took me a lot of time. CONCLUSION As I did the test migration at CQU I faced these issues and having a solution ready it dint delay the duration of the project and reduced the risk involved. WEEK: 10 PROJECT SUMMARY: Identifying and fixing issues Week Start Week End Project Name Prepared By 19th September 2016 23rd September2016 SAP Business Objects Migration CITIBANK Siva Chengalvala TASK OVERVIEW Task Identification I identified that rights to the report in 4.1 are renamed I identified that rights in 3.x are not supported 4.1 Presentation of the project due for next week Work Done Since it is new version for better understanding the rights have been reamed which I found out using the training material. Some of them are not supported in 4.1 by referring to the guide I applied them manually. In most cases the rights, filters were not applied while doing a complete upgrade using the upgrade manger. I did an incremental upgrade to all of reports with issues selecting what I need in particular in the newer version. Discussing the progress of the project with my team mate I created the presentation on our project. CHALLENGES FACED Getting the guide of BO4.1 took time to check rights that have been renamed. The server at client place to access the repository which had the reports was down for 6 hours which delayed my job CONCLUSION I successfully migrated all the reports within the planned time frame with minimum issues and fixing all the issues I faced. All the milestones were met and I have updated the project file. WEEK: 11 PROJECT SUMMARY: Project presentation Week Start Week End Project Name Prepared By 26th September 2016 30th September 2016 SAP Business Objects Migration CITIBANK Siva Chengalvala TASK OVERVIEW Task Identification The progress of the project till date, issues and the project has to be presented to my project facilitator Prepare the progress report 4 showing the progress and completion of the project To run and test the reports in Bo 4.1 Work Done I worked with my team mate discussing the milestones we achieved together and created a PowerPoint presentation and presented it to the project facilitator. I have prepared the progress report 4 and submitted. There was a cost cut in the project budget of 7000 dollars. CHALLENGES FACED Had difficulty in creating the presentation as there was no contribution from my team mate. CONCLUSION The dedication towards the success of the project worked so well as we could complete the project 10 days prior to the schedule and a 7000 dollars cost cut in the budget which is a big success. WEEK: 12 PROJECT SUMMARY: Project Report Go live and Support Week Start Week End Project Name Prepared By 3rd October 2016 7th october 2016 SAP Business Objects Migration CITIBANK Siva Chengalvala TASK OVERVIEW Task Identification After completing the project I have to provide training to client and the end users Provide support post migration Go live I have to prepare the project report summarizing my project Work Done I provided all the training materials to the client post upgrading and conducted sessions with the project manager of the CITIBANK explaining the features of the new version. After the training we finally went live with new version saying goodbye to business objects 3.0 at CITIBANK. I am still working on the project report CHALLENGES FACED Since all the clients were busy I dint get sufficient time to conduct the training sessions CONCLUSION I and my teammate worked hard in making the project a big success. After GO live and training we will provide support to CITIBANK for the Business object 4.1. The upgrade gives a better GUI experience, access multi source universes in one report and data security. ABBREVATIONS USED: BOE 4.1 SAP RCT BO UAT GUI BUSINESS OBJECTS ENTERPRISE 4.1 SYSTEMS, APPLICATIONS AND PRODUCTS REPORT CONVERSION TOOL BUSINESS OBJECTS USER ACCEPTANCE TESTING GRAPHICAL USER INTERFACE