User manual BUSINESS OBJECTS RAPID MARTS PACKAGES XI 3.2 UPGRADE WHITE PAPER

[. . . ] Rapid Marts are packaged solutions for building data marts with SAP BusinessObjects technology: Data Services, Universe Designer, and Web Intelligence. Rapid Mart packages deliver jump-start ETL mappings, schema, and initial reporting content, accelerating the deployment of BI (business intelligence) for enterprise applications from SAP, PeopleSoft, Oracle, and Siebel. Each Rapid Mart is designed to address the reporting needs of a specific business area (or department) like accounting, sales, or purchasing. A component-based framework allows conducting analysis across these selected business areas by combining different packages within the same source application suite. [. . . ] HR Rapid Mart upgrade is required for customers who upgrade from 8. 8 to 8. 9 or 9. 0; Siebel Applications - moderately volatile; there were significant changes between Siebel Applications version 6 and version 7; any changes within version 7 family do not affect Rapid Marts. · · · Below is a matrix of upgrades required for Rapid Mart and Business Objects tools' version by supported ERP Application version ERP Rapid Mart Release Rapid Mart Upgrade Data Services Upgrade No No Business Objects Enterprise Upgrade No No SAP 4. 6-6. 0 Oracle Apps 11. 5. 3 - 12. 0. 0 XI 3. 2 XI R2 No Yes 4 SAP BusinessObjects Rapid Marts packages XI 3. 2 - Upgrade White Paper When To Upgrade Rapid Mart 1 ERP Rapid Mart Release Rapid Mart Upgrade Data Services Upgrade Business Objects Enterprise Upgrade No PeopleSoft Apps 8. 8-9. 0 XI R2 GL/AP/AR/AM - No No HR - Yes No No Siebel Apps 7. 0- XI R2 8. 0 No Rapid Mart Service Packs Rapid Mart service packs typically address issues with mapping, transformation, or table joins logic within the Rapid Mart ETL job, universe, or reports. It is always the minimal incremental update that Rapid Mart development tools will allow. For example, if a service pack corrects mapping in a single Rapid Mart data flow, it will contain Data Services export file (ATL) with only that single data flow. Below is the excerpt from Sales Rapid Mart XI R2 for SAP (version 11. 5. 5. 1) release notes as an example of steps that are required to be performed in order to apply the patch. SAP BusinessObjects Rapid Marts packages XI 3. 2 - Upgrade White Paper 5 1 When To Upgrade Rapid Mart . Rapid Mart Release with New Content Some of Rapid Mart releases come with new business content. If this new functionality is beneficial to the existing implementation, you may consider Rapid Mart upgrade. 6 SAP BusinessObjects Rapid Marts packages XI 3. 2 - Upgrade White Paper When To Upgrade Rapid Mart 1 The next chapter describes the upgrade path in detail. SAP BusinessObjects Rapid Marts packages XI 3. 2 - Upgrade White Paper 7 1 Rapid Mart Upgrade Methodology Rapid Mart Upgrade Methodology Rapid Mart upgrade is a manual process. Even if you implemented the Rapid Mart 'as-is', you still need to apply some changes manually. After applying the upgrade, test the changes before moving the changes to production. The upgrade may affect every element of the reporting solution: · · · · ETL routine Reporting database schema Semantic Layer Reports Phase 1: upgrading back-end - ETL routine and reporting database schema; Phase 2: upgrading semantic layer - Universe; Phase 3: upgrading front-end - Web Intelligence reports. Rapid Mart upgrade path can be split in three phases: Each phase consists of the following milestones: 1. Setup DEV and TEST environments; In DEV environment, discover changes in the Rapid Mart ETL job, target database objects (data model), Universe, and Web Intelligence reports; Analyze changes; identify what is applicable; Apply changes; Test the upgrade in TEST environment; Deploy the upgrade in PROD environment. Setting up DEV and TEST environments Setting up the development (DEV) and test (TEST) environments is similar to that of a new Rapid Mart implementation. Make sure that SAP BusinessObjects tools needed for the Rapid Mart upgrade are tested in the new environment: · · · · Data Services BusinessObjects Enterprise Universe Designer Web Intelligence 8 SAP BusinessObjects Rapid Marts packages XI 3. 2 - Upgrade White Paper Rapid Mart Upgrade Methodology 1 For example, if changes are to be made to the ETL job, the upgrade requires DEV and TEST environments for Data Services. If there are changes to ETL process, reporting database schema, and semantic layer, you will need to setup DEV and TEST environments for Data Services and BusinessObjects Enterprise. Rapid Mart Change Discovery Each new release of a Rapid Mart comes with Release Notes document that describes shortly what changes have been made to the previous version. The Release Notes is a reference to what areas of the Rapid Mart have been changed. Data Services Metadata Reports or Metadata Manager may be used to perform impact and lineage analyses for Rapid Mart job, Universe, and Report objects subject to change. For detailed comparison (DIFF analyses) you need to use Data Services Designer. You can use Data Services Designer Compare Objects feature to view differences between the new version of Rapid Mart and your custom Rapid Mart ETL job objects. The Difference Viewer does not allow exporting comparison results; results are only available as displayed on the screen. 4. 5. 10 SAP BusinessObjects Rapid Marts packages XI 3. 2 - Upgrade White Paper Rapid Mart Upgrade Methodology 1 6. Rapid Mart Universe and Web Intelligence Reports: Currently BusinessObjects Enterprise does not offer DIFF tools for the semantic layer. Using combination of SAP BusinessObjects metadata tools (Data Services, Metadata Manager) will yield the best results. Data Services Object Comparison tool provides easy-to-read DIFF interface. Metadata Manager Explorer organizes Rapid Mart metadata into a directory structure through which you can easily navigate and analyze the metadata. In summary: · · · Applying Rapid Mart Upgrade The identified changes needs to be merged with the existing Rapid Mart implementation without overwriting any customizations. Rapid Mart database schema objects (Tables, Indexes): For existing tables, create 'ALTER TABLE' statements to add new columns. Rapid Mart ETL job: Any new Data Services Object Library object that does not exist in the customized Rapid Mart (such as a workflow, a dataflow, etc. ) can be imported into the Rapid Mart repository and added to the Rapid Mart job. See Data Services Designer User Guide for details about Export/Import Wizard. [. . . ] For the target database schema and ETL jobs: · · · · · · · · · if you decide to fully reload your data mart, you need to test initial (historical) data load and incremental load (daily updates); if you decide to update your existing data mart, you need to test the upgrade incremental load that will apply proper updates to the historical data and incremental load (daily updates); perform data validation to ensure that full/incremental loads transform and load data properly; verify that the incremental daily load will not exceed allowed time period; tune ETL jobs performance if necessary; test user query response time (or report performance). none of existing reports will be broken; all changes to existing objects and new objects are correct; all contexts and joins are correct; all existing and new reports produce correct results. For the semantic layer and reports, you need to ensure that: Deploying Rapid Mart Upgrade After the Rapid Mart upgrade is developed and tested, apply the upgrade package to PROD environment. As with the TEST phase, the same methodology applies to deploying an upgrade and deploying a new Rapid Mart. 12 SAP BusinessObjects Rapid Marts packages XI 3. 2 - Upgrade White Paper Conclusion 1 Conclusion Rapid Marts are Data Services and BusinessObjects Enterprise Business Intelligence (BI) best practice templates that are meant to be customized to better suit customer reporting needs. Once the reporting solution is in production, typically there is no need to upgrade. [. . . ]