SAP BO Rapid Mart

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 1

SAP BusinessObjects Rapid Marts

Overview - 2

Applies to:

SAP BusinessObjects XI 3.0, SAP BusinessObjects XI 3.1 all support packs, SAP R/3 4.6 and above, SAP ERP ECC 5.0 and above. For more information, visit the Business Objects homepage.

Summary

This document describes the high level implementation of SAP BusinessObjects Rapid Mart. Also, it describes the customization of Rapid Mart standard content.

Author: Ramakrishna Kamurthy

Company: Intelligroup, Inc.

Created on: 28 January 2011

Author Bio

Ramakrishna Kamurthy works with Intelligroup, Inc. as Senior Consultant – SAP BI / BOBJ with over three years of SAP experience specializing in End-to-End SAP Data Archiving, SAP DWH implementation, SAP/BOBJ integration, administration and configuration.

https://www.sdn.sap.com/irj/boc

SAP BusinessObjects Rapid Marts Overview - 2


© 2011 SAP AG 2

Table of Contents

Introduction ......................................................................................................................................................... 3

Prerequisites ....................................................................................................................................................... 3

Rapid Mart Package ........................................................................................................................................... 4

ETL Repository ................................................................................................................................................... 4

Repository Creation ........................................................................................................................................ 4

Repository Assignment ................................................................................................................................... 5

Installation of Rapid Marts .................................................................................................................................. 5

ETL (ATL File) ................................................................................................................................................. 5

Data Model (SQL Script File) .......................................................................................................................... 6

Visuals – Reporting Content (BIAR File)......................................................................................................... 7

Configuration of Rapid Marts .............................................................................................................................. 8

ETL Datastore Maintenance ........................................................................................................................... 8

ETL Directories Maintenance .......................................................................................................................... 9

Reporting Universe Maintenance .................................................................................................................. 10

File Maintenance ........................................................................................................................................... 10

Data Loads & Monitoring .................................................................................................................................. 11

Global Variables ............................................................................................................................................ 11

Data Loads – Initial Vs Delta ......................................................................................................................... 12

Data Load – Monitor ...................................................................................................................................... 12

Visuals – Reports & Dashboards ...................................................................................................................... 13

Standard Reports .......................................................................................................................................... 13

Standard Dashboards ................................................................................................................................... 13

Related Content ................................................................................................................................................ 14

Disclaimer and Liability Notice .......................................................................................................................... 15



© 2011 SAP AG 3

Introduction

In my last article SAP BusinessObjects Rapid Marts Overview - 1, explained overview of SAP BOBJ Rapid Marts in details as follows: Data Warehouse solution, DWH with SAP BOBJ tools, time, risk and efforts, available Rapid Mart packages, versions, architecture, advantages and limitations.

In this article, I am going to explain the technical high level implementation of Rapid Marts for SAP solutions. This document helps the technical consultants / Developers to know more about the implementation of SAP BOBJ Rapid Marts in detail like perquisites, installation and configuration, pre and post implementation steps and customization of standard Rapid Mart content. Finally I explain the implementation of multiple Rapid Mart packages in a single repository and its maintenance.

The following are the steps discussed in detail to make better and clear understanding of implementation of SAP BusinessObjects Rapid Marts

Prerequisites

Rapid Mart Package

SAP BusinessObjects Data Services Repository

Installation of Rapid Marts

Configuration of Rapid Marts

File Maintenance

Data Load & Monitoring

Visuals – Reports & Dashboards

Prerequisites

The following are the prerequisites to be performed before stating the implementation of SAP BOBJ Rapid Marts.

Integration between SAP and BusinessObjects ETL (BODI / BODS) should be available and all the privileges to access / extract the data from SAP are assigned to the user, which is going to use in ETL tool

Two database schemas are to be created with all appropriate privileges (one for ETL Repository and another for Data model)

ETL Job Server details are required if already job server is available for processing the ETL jobs. If not, create a new job server

Collect the details of directories like working directory in SAP sever, ABAP generated directory, local directory in ETL server, etc.

Collect SAP source system authentication details like Client ID, User, Password, FTP details, System Number, etc.

Collect SAP BusinessObjects Enterprise system details (to enable reporting content) like System ID, User Name & Password, Authentication, InfoView, etc.

Note: Once you get all the above information, cross check the system release and versions with Rapid Mart package version for compatibility. You can use the Rapid Mart supported platform document available in

http://sdn.sap.com or Supported Platform section in SAP BusinessObjects Rapid Marts Overview - 1. If any

system (SAP or BOE) or DB or H/W is not compatible, recommend the client to upgrade to the required versions.

http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/b09a16ee-ec63-2d10-cfa9-979a9081458d

http://sdn.sap.com/




© 2011 SAP AG 4

Rapid Mart Package

In a standard Rapid Mart package, SAP provided a set of files as readymade objects, which accelerates the implementation of DWH solution. The following picture explains the content of Rapid Mart package:

ETL Repository

Once all the perquisites information is available, the following are the Pre-Implementation steps to be performed before starting the Rapid Mart installation. Here I am using SAP BusinessObjects Data Services 3.2 SP1 as an ETL tool.

Repository Creation

In a standard Rapid Mart package, an ATL file (as showed above) is provided as readymade ETL logic to extract the data from source system, transform and load into data model. To process / execute this ETL, we need one repository to import and use the ETL (Projects, Jobs, Work Flow, Data Flow and Transforms)

Create a BODS Repository using Repository Manager tool. Provide the schema details which we collected in perquisites phase.



© 2011 SAP AG 5

Repository Assignment

After successful creation of Repository, assign this repository to the Job Server which we created in perquisites phase. Test whether the repository is working and the assigned job server status by logging in to the repository using Data Services Designer.

Installation of Rapid Marts

Once repository and job server assignment is done, then system is ready for installing the Rapid Mart package. As shown in above picture, Rapid Mart package includes different objects to install and start using the system. Below, installations of each object in Rapid Mart package are explained in detail.

ETL (ATL File)

First I am going with ETL installation. For ETL transformations, SAP provided an exported ATL file in each Rapid Mart package (application specific). This ATL file is located under ETL folder of the software provided, which can be access and can be used by importing it into BODS repository.

Import the ATL file into BODS Repository which we created above, though Data Services Designer with Import from File option



© 2011 SAP AG 6

As all Rapid Mart ETL are huge design, it will take some time to import the file successfully. After importing the ATL file, we can able to see all the ETL objects as follows: Projects, Jobs, Work Flows, Data Flows and so on.

Data Model (SQL Script File)

Second, I am going with Data Model creation. For creating a data model, SAP provided database specific SQL script files for all the Rapid Mart packages. The following are the list of different SQL script files included in Rapid Mart package. These script files are located under Data Model folder of the software provided.

Create Tables & Drop Tables

Create SAP Comments & Drop SAP Comments

Create Indexes & Drop Indexes

Create Stored Procedures & Drop Stored Procedures

Create Tables and Create Stored Procedures script files are mandatory files to create data model. The rest of the files are optional.

Create a Data Model, by executing the appropriate script files on database schema



© 2011 SAP AG 7

After successful execution of script files, the data model is created. The list of tables created on database schema can be seen.

Note: The script files provided in all the Rapid Mart for SAP ERP solution are common files.

Visuals – Reporting Content (BIAR File)

Finally, I am going with visuals (for example, Universe and sample reports installation). For each Rapid Mart package, SAP provided one or more Universes and 10 to 15 sample standard reports which help business users for analysis. Both Universe and Web Intelligence reports are collectively provided in a single BOE exported file i.e. BIAR file.

Import Wizard is a tool, which helps to extract the BIAR file and to import all the Universes and sample reports into the BOE server / repository.

Using Import Wizard, import all the Universes and sample reports into the BO server.



© 2011 SAP AG 8

Select the appropriate options in Import Wizard while importing the objects from BIAR file. View the log for any errors to re-import the failed objects.

From the above, the installation phase of Rapid Mart package is successfully done.

Configuration of Rapid Marts

After successful installation of all the Rapid Mart objects, configuration of objects to maintain the interface between the source system and ETL tool, Data model and BusinessObjects Reporting tool is the next step. All the below steps / tasks I am calling as post installation activities after Rapid Mart installation.

ETL Datastore Maintenance

In the configuration phase / post installation steps, first I am going with Datastore maintenance. After importing the ATL file, all the readymade ETL Jobs, Data Flows, Transformations, and similar files are available for extracting SAP ERP application specific data. As this ETL transformations provided by SAP are outbox, we manually need to maintain the Datastore parameters to point this ETL to our respective SAP source system and connect the data model to update the data.

Edit the default source Datastore i.e. R3_DS which comes along with Rapid Mart ATL file. Provide the parameter details to point the SAP source system to extract data.



© 2011 SAP AG 9

Similarly, edit the default target Datastore (for example, RM_DS which comes along with Rapid Mart ATL file). Provide the parameter details to point the target data model to update data.

Note: By default in all the Rapid Mart packages, the Datastore naming convention is maintained as common i.e. for source Datastore it is R3_DS and for target Datastore it is RM_DS. It is not mandatory to use the same naming conventions; it allows editing the Datastore name. Details of editing the Datastore name provided in the Rapid Mart User Guide available under document folder in the provided software.

ETL Directories Maintenance

While maintaining the ETL Datastores, it is mandatory to provide the different directory details like name and path. ETL directory maintenance is depends on the type of Data Transfer method chosen. Selecting the right method again depends on data volume extraction and environment of all the systems exists (unique or multi-operating system environment). Generally the best option in worst case is FTP data transfer method.

Maintain all the directory details based on the data transfer method selected.



© 2011 SAP AG 10

Reporting Universe Maintenance

When ATL file imported, along with transformations two Datastores are imported to maintain the interface between the source system and ETL tool and ETL tool and Data Model. Similarly, when BIAR file is imported into BO server / repository, along with Universes, Universe Connections are also imported. As this Rapid Mart package is developed out of box, we manually need to maintain the Universe Connection parameters to point these Universes to our respective Data Model. Default connection name is CHANGE_THIS.

Edit the Universe connection or create a new connection and assign it to Rapid Mart Universes to point the correct Data Model.

File Maintenance

In the configuration phase, ABAP file maintenance is the last step. Along with Rapid Mart package, SAP provided some ABAP files for custom transforms. While importing the ATL file, all the related custom transforms are imported automatically under Platform transforms section. These transforms are executed based on the ABAP programs provided by SAP in the form of file. So, it is mandatory to place these ABAP files in an appropriate directory to successfully utilize the functionality of custom transforms.

For Time dimension, SAP provided another file called Dates.dat that contains the list of dates from 1900.01.01 to 2013.12.31, allowed to extend / add dates as per requirement. Similarly this file is also to be placed in an appropriate directory to fill the time dimension. These two file are available under ETL directory of the software provided and separated by ABAP and Data sub directories.

Copy all the ABAP files from the ABAP directory and place all the files in the ABAP Generated directory / path which you maintained in the SAP Datastore. Similarly copy the file Dates.dat from Data folder and place in the Working Directory on SAP server which you maintained in the SAP Datastore.



© 2011 SAP AG 11

Note: In this step (File Maintenance), the ABAP file maintenance is for only some Rapid Mart packages. That is, SAP

provided ABAP files for some Rapid Marts only, not for all (for example, SAP General Leger Rapid Mart).

Data Loads & Monitoring

From the above step, the configuration of Rapid Mart content is done and now the system is ready to start pulling / extracting data from SAP source system and load into target data model.

Global Variables

Before starting data loads, having analysis of source system data helps to maintain the ETL job parameters. For example, how many years of historical data are planning to maintain in EDW, database growth in source system like number of transactions per day. All these information helps in pulling the data from source system.

For all the Rapid Mart ETL jobs, SAP maintained a common Global Variables, and classified these as

Used in all Rapid Marts

Used in 2 to 10 Rapid Marts

Used in only one Rapid Mart

All the details about common variables and their usage are clearly given in a script file under each Rapid Mart ETL job. We can maintain the Global Variable values permanently in this script file by removing the comment or we can maintain at the time of executing the job (it will trough the Global Variable screen)

These Global Variables controls the data extraction process like Initial or Delta load, volume of data extraction, Index creation and dropping, Data load mode settings, default number, character& date and so on.

Note: Here I am not giving the full details of Global Variables, as my main concentration is on Installation and

Configuration of Rapid Mats. In the next article, I will give the complete details about Global Variables and its role.



© 2011 SAP AG 12

Data Loads – Initial Vs Delta

All the Rapid Mart ETL jobs are designed in a way it supports for both Initial / First load (for example, for extracting historical data and Incremental / Delta loads to extract the day to day transactions).

Global Variable $G_LOAD_TYPE, controls to run the Initial load or Delta Load. If you maintain the variable value as ‘FIRST’ then it will act as initial load, pulls the historical data of specified dates. If the variable value is ‘DELTA’, job acts as incremental load and pulls the daily transactions.

Before executing the job, edit the global variable $G_LOAD_TYPE value and maintain the value as FIRST for initial load or as DELTA for incremental load.

Data Load – Monitor

Once the initial load is successfully completed, like normal Data Servers jobs we can schedule these Rapid Mart ETL jobs for incremental loads. All the jobs are monitored from Data Services Management Console.

Note: Here I am not giving the full details of how Initial load and incremental loads are running on specific application wise ( like Financial Documents in GL Rapid Mart or Profit Center in Cost Center Rapid Mart) and even I didn’t explained about Rapid Mart Recovery Mechanism to avoid duplicate data if any job fails. I will explain all these in separate article.



© 2011 SAP AG 13

Visuals – Reports & Dashboards

Once data load is done, all the standard reports and dashboards are available for refreshing to see the reports with the data which we loaded.

Standard Reports

For all the Rapid Marts, SAP provided 15 to 20 sample standard reports which are readily available for analysis. Open the reports, refresh to see the reports with loaded data and start analysis.

All standard reports are editable. Alternately, you can develop custom reports on the standard universe if the standard reports have not met requirements.

Standard Dashboards

For some Rapid Mart packages, SAP provides five to six sample Dashboards which enables the graphical analysis and alerts to make quick decisions. In the current available latest Rapid Mart versions, only for Sales Rapid Mart, SAP provided sample dashboards.



© 2011 SAP AG 14

Related Content

SAP BusinessObjects Rapid Marts Overview – 1

SAP BusinessObjects Data Services Designer Guide

SAP BusinessObjects Data Services Supplement for SAP

For more information, visit the Business Objects homepage


http://help.sap.com/businessobject/product_guides/boexir32/en/xi32_ds_designer_en.pdf

http://help.sap.com/businessobject/product_guides/boexir32/en/xi32_ds_sap_en.pdf

https://www.sdn.sap.com/irj/boc



© 2011 SAP AG 15

Disclaimer and Liability Notice

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.

SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk.

SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document.