Hi All,

These days, BODS is playing a very important role in the SAP system landscape.

Many customers use BODS to pull data from Non-SAP systems to SAP BW.

These documents are primarily intended for BW consultants who would like to know more about the Integration, Modelling and Transport mechanism related to BODS.

In part 1, we will go through how to integrate BW and BODS using RFC connection.(This topic has been explained many a times in SDN. For making 2nd and 3rd part more meaningful, I have included the integration as Part 1.

Part 2 will help you to understand how modelling is done in BODS

Part 3 will help you to understand the transport mechanism in BODS(Will be published later)

Environment:

BODS – Version is 14.0.3.273(Also BO and BODS are installed in the same server)

BW – BW7.3 (where BODS is now available in the source systems list in BW)

BODS/BO server is running on Windows platform and the BW OS is HP-UX and database is Oracle.

Step 1:

Login to RSA1 Source systems and create a new connection under BO Dataservices.

Please note that for all BW versions prior to 7.3, you will not see BODS as a source system.

In such case, you will have to depend on 'External System' source system type for creating the connection.

Right click on BODS and press create

Give the required credentials

Give the Logical system name(in this case - BODSPB1) and Source system name(description and in this case it is Logical system for SAP BODSPB1) .Type and release is not mandatory.

Give a Program id (in this case it is SAPBODSPB1) . This is a very important step.

Important point to be noted here is that when you give details for external source system in RSA1,better dont give the gateway host and gateway service in case if you are not 100% sure about it(in simple words, keeps them blank)

See discussion here --> http://scn.sap.com/thread/3247518

The system itself will manipulate it(default gateway value) with the program id, provided you give the same(case sensitive) in both the ends(BW and BODS)

Save and go back and give the required credentials..

Give credentials like BODS Repository, Job Server, Back ground BW user, Password and so on.

The same can be seen in SM59 also under TCP/IP connections.

Now BO Dataservices will have a connection names BODSPB1 under it.

Now log into BODS Management console and give the corresponding BW server details.

The required BW credentials can be obtained in the context menu of the BW server in the SAP Logon pad.

RFC Program id is the same one SAPBODSPB1(case sensitive) which we had given in BW side.

The user used here is of type Service User.

For RFC to work as expected, the status should be in STARTED state.

Check the RFC connection in SM59 by using Test Connection option.

The connection test should be successful.

There can be lot of issues which might come in between during the configuration,and it depends on the  landscape in which you work:

Anyways, please find some points which you can check if you encounter any issues in between.These were  some of the solutions that were given by experts when we were facing some challenges in integrating BW with BODS.

1) There can be a problem in the gateway; you need to contact your basis team for this issue.The gateway for BW might not have been opened to connect the BODS server, for checking this we need to ping the command telnet <hostname of BO server> 3300 in the BW server. If it's not listening, then gateway is the culprit.

2) Change the gateway to its port number.Find the port number in the services file (windows\ststem32\drivers\etc\) of a machine with the sap GUI installed.There is a chance that your BODS server doesn't have the sapGUI installed and doesn't have the services file and thus can't translate the gateway name to a port number. Installing the sapGUI may also fix an issue setting up the RFC but not being able to see it in the list of available RFC connections in the BODS console.

3) Check the SAP system number. The gateway service should SAPGWXX where XX is ur SAP system number.

Hope this was useful.

Regards,

Prabhith

This page provides  information,  about the new functionalities provided with SAP NetWeaver Business Warehouse 7.4 in general and the new functionalities of SAP NetWeaver BW powered by SAP HANA provided with SAP NetWeaver Business Warehouse 7.4 - SP 05

Preliminary delivery of Support Package 6 for SAP NetWeaver BW 7.4

The planned delivery of the regular of SAP NetWeaver BW 7.4 SP 6 is scheduled for middle of March as announced on the official SMP delivery schedule.

Due to a high amount of requests a preliminary version of this SP 6 was released. Please read SAP Note 1978179 - Early delivery of NW 7.40 SP06 (ABAP) to learn about the implied restrictions and the download instructions.

SAP NetWeaver BW 7.4 SP05 is released!

Read the information on the Support Package page for SAP NetWeaver BW 7.4

SAP BW? - Three Things to Know ... Blog by Roland Kramer.

General Availability Care Program for SAP NetWeaver BW 7.4 SP05

For SAP NetWeaver BW 7.4 Support Package 05, we offer the SAP general availability care (GAC) program. Via the SAP GAC program, SAP reaches out to the first customers who receive SAP’s new solution for Business Warehouse and who want to implement one of the key topics listed below. With your active participation, you help SAP to gain early feedback from the productive usage of the latest software which may serve as a basis for further improvements. At the same time, SAP would like to engage with productive customers who are interested in a collaboration regarding marketing and communication activities for the new functionalities provided

Overview SAP BW 7.4 SP05 on SAP HANA and further Roadmap

SAP NetWeaver BW on SAP HANA continues to be the  cornerstone of SAP’s strategic vision for enterprise data warehousing providing organizations a solid data foundation to capture, store, transform and manage data in a scalable, enterprise-ready data warehouse. And as new challenges arise in the market (exploding data volumes, new data sources, the need for real-time information access, etc), SAP BW on HANA continues to evolve in order to meet the growing challenges imposed on IT by these ever changing market forces. The release of SAP BW running on SAP HANA is a great example of how SAP BW has evolved to ensure organizations continue to leverage  their investment in SAP BW to meet these new  challenge.

See this presentation to learn what SAP is doing next to evolve SAP BW on SAP HANA with the SAP BW 7.4., SP 05 on HANA

Key Features

• Enhanced Data Modeling
  • Common Eclipse based Modeling Tools
  • BW/HANA Smart Data Access providing the logical EDW
  • Easy integration of external data models with Open ODS Layer
  • Further reduce data layers in BW via Operational Data Provisioning
  • New Composite Provider
• Push down further processing logic to HANA
  • BW Analytic Manager
  • HANA  Analysis Processes
  • BW Transformations
  • PAK (Planning Application Kit) – Pushing down more planning semantics
• Converged planning solutions (i.e. BPC unified)

Recommendations:

• Apply SAP NetWeaver BW 7.4 with support package lower than SP 5 for Embedded Use Case scenarios only
• For EDW Use Case scenarios: Start only with SAP NetWeaver BW 7.4 SP05
• If you plan to upgrade your ERP first to EhP7 (based on NetWeaver 7.40), you MUST first upgrade your corresponding BW System at least to 7.31 or higher, to stay compatible with the ERP Backend, check the Information attached to the following SAP Notes
  • Note 1388258 - Version Interoperability within the SAP Business Suite
  • Note 1951805 - Adjusted Version Interoperability for Business Suite 7i2013
• If you are running  SAP BusinessObjects BI Suite on SAP NetWeaver 7.4, please be aware of the following:
  • SAP BusinessObjects BI Suite 4.1 Support Pack 1  or BusinessObjects BI Suite 4.0 Support Pack 6 is mandatory! Lower SP levels do not incorporate the enhancements delivered with SAP NetWeaver 7.4
  • See more in the SAP BusinessObjects BI Suite release restriction e.g. SAP BusinessObjects BI Suite   4.1 Support Pack 1 Release Restrictions
• If you are still running Query Designer 3.x on your BW system, please note the following:
  • The BEx tools from SAP BW 3.5 are not available in SAP NetWeaver 7.40. Whereas the Analytic Engine of BW 7.4 can still execute queries which were  with the defined with the BEx 3.5 Query Desginer, the workbooks  created with the BEx Analyzer or WEB Templates need to be migrated . Please read “Cookbook for Migration to BEx 7.0” in SAP Note 1807522 - BEx 3.5 Objects Migration to BEx 7.0
  • If you are upgrading your BW system to BW 7.40 and are still using the obsolete Query Designer 3.x, SAP provides the following additional information:
    • To check which old query features are no longer supported in 7.40, use the reporting tool described in SAP Note 1911469.
      This tool will check the queries in your system and shows those which contain features that are no longer supported.
      Note 1911469 - Check report for discontinued query features in 7.40
      Note 1962865 - Check ReportSAP_QUERY_CHECKER_740 dump
    • Use the report attached to Note 1915309 - Query Migration Tool – 3.x to 7.x to do a mass migration of the existing queries.
    • You find can find a list of obsolete functions and proposed workarounds in the SAP Help Library
    • The detailed maintenance strategy for the SAP NetWeaver 04 BW 3.5 front-end add-ons is described  in SAP Note 1932461
  • SAP strongly advises you to read the available documentation thoroughly in order to benefit from the support SAP offers now and in the future, and to make it easier for the customer to make the transition away from the obsolete reporting tools.
  • More information can also be found under http://scn.sap.com/community/business-explorer
• Pre upgrade activities are described in SAP Note 1879618 - Pre Upgrade Activities for Upgrade/Update to 7.4
• Do not upgrade lower than NetWeaver 7.40 SR1! (which is SP05)
  Note 1962880 - RDDMASGL job fails during ACT_UPG phase during Netweaver 7.4 upgrade
• Oracle and DB6 based systems: please check the following SAP Note:
  Note 1805195 - Handling and troubleshooting of tablespaces during Upgrades, EhPs and SPs updates
• The maximum length of texts for characteristic values is increased. For changes that might be advised, please see SAP Note1823174 - BW7.40 Changes and customer-specific programs
• Please read also SAP Note1600929 - SAP BW powered by SAP HANA DB: Information and1729988 - SAP NetWeaver BW powered by SAP HANA - Checklist Tool

• If the SEM Add-On is applied on the NetWeaver system, you can change the modeling in the Solution Manager for better handling at any time,  see the blog "Good News - Easier Modeling of the SEM Add-On in Solution Manager"

Additional Information:

Positioning of SAP NetWeaver Business Warehouse powered by SAP HANA and SAP HANA Live for SAP Business Suite

  Roadmap for SAP NetWeaver BW on SAP HANA - One slider

SAP NetWeaver 7.4  BW ABAP Support Packages Schedule and Implications

Applies to

SAP BI Input Ready Query- Integrated Planning in SAP BI.

For more information, visit the Business Intelligence homepage.

Summary

This article describes the steps required to build an Input Ready Query to load data into BW system through BI Integrated Planning. It also describes the steps to create MultiProvider, Aggregation level and input enabled query.

Integrated Planning

            Planning is an integral part of the management cycle. The management cycle helps companies to position themselves in complex environments and to keep on track in reaching their overall company goal. Planning supports decision making, the coordination of different divisions towards a common goal and defines general conditions for operation.

            BI Integrated Planning provides business experts with an infrastructure for realizing and operating planning scenarios or other applications. BI Integrated Planning can be used to create process-oriented planning.

            BI Integrated planning fulfills both the end user’s and the administrator’s wishes at the same time. The end user can work from a plan query that is equally valid for all planners in a planning area, can open Excel offline planning and then carry out significantly more detailed planning there. Only part of this data is then written back to the enter-able query; that is, the part refers to the cell in question.

Overview of Input Ready Query

                   Input-ready queries are used to create applications for manual planning. These can range from simple data entry scenarios to complex planning applications. You define queries for manual planning in BEx Query Designer. In Web Application Designer or BEx Analyzer, you can combine input-ready queries with other queries and planning functions to create complex planning applications.

            A query that is defined upon an InfoProvider of type aggregation level, it is input ready and can be used for manual planning. Whether a particular cell is input ready depends on the drill-down, specifically whether characteristic relationships and data slices are permitted for the cell.

Prerequisites

            Fundamentals of SAP Business Intelligence, SAP Integrated Planning. Good knowledge of BEx.

Business scenario

            The business requirement is to have a Dispatch Plan upon the actual data. Architecturally this has been enabled by using actual InfoCube which provides the available Data that is used for reporting. The goal is to enable an Input Ready field for Dispatch Plan in Report that allows users to enter data which in background will get updated to the Realtime Cube.

            In the example below Actual Cube is ‘ZS_ICACT’ which contains necessary data for reporting and ‘ZS_IPTRD’ is the Realtime cube that’s used to store the data entered through the reports.

How to start with Integrated Planning:

Creating a Real Time Info Cube

            Real-time Info Cubes differ from Standard Info Cubes in their ability to support parallel write accesses. Standard Info Cubes are technically optimized for read accesses to the detriment of write accesses.

Right click on the Info Area and select ‘Create Info Cube’.

Give name for InfoCube and click on ‘Create’ button. ‘ZS_IPTRD’ is the name of the InfoCube.

Creating a Multi Provider

            A MultiProvider is a type of InfoProvider that combines data from a number of InfoProviders and makes it available for reporting purposes. The MultiProvider does not itself contain any data. Its data comes entirely from the InfoProviders on which it is based. These InfoProviders are connected to one another by a union operation. 

            MultiProviders only exist as a logical definition. The data continues to be stored in the InfoProviders on which the MultiProvider is based. A query based on a MultiProvider is divided internally into subqueries. There is a subquery for each InfoProvider included in the MultiProvider. These subqueries are usually processed in parallel.

Right click on the Info Area and select ‘Create MultiProvider’.

Give name for MultiProvider and click on ‘Create’ button. ‘ZS_MULPRO’ is the name of the Multi Provider.

In the next screen, select the Info Cubes which should be in the MultiProvider. So select the check-box for ‘ZS_ICACT’ and ‘ZS_IPTRD’.

Drag and drop Info Objects from the ‘Involved Info Providers’ pane to the right side pane of MultiProvider. 0Calday and 0Calyear should be dragged to the dimension ‘Time’. Drag key figures to the dimension ‘KeyFigures’. Drag Material to the dimension ‘Dimension1’.

Right click on any characteristic and select the option ‘Identify (Assign)’.

Select the check-boxes for the InfoProvider.

In the same way assign all characteristics and keyfigures to both Info Cubes and activate the MultiProvider.

Steps in Planning Modeler

            Go to tcode RSPLAN. Click on the button ‘Start Modeler’ to start the Planning Modeler.

            The Planning Modeler is a Web-based modeling environment for all tasks related to planning. The Planning Modeler is the central modeling tool for all planning-specific objects. You can use the Planning Modeler to model, manage and test all the metadata that belongs to the planning scenario. The different objects are maintained in the modeler in connection with planning, such as aggregation levels, as are the relationships between these objects.

Give the name of the MultiProvider and click on either ‘Start’ button or press ‘Enter’ key.

The Info Objects of the MultiProvider will be listed in the lower part of the screen.

Aggregation levels

            To determine the level on which data can be entered or changed (manually through user input or automatically by a planning function), you define an InfoProvider of type aggregation level. An aggregation level consists of a subset of the characteristics and key figures of a MultiProvider or real-time InfoCube. Real-time InfoCubes are used to store data.

            All Info Objects of the MultiProvider will be listed. Select the Info Objects that should be included in the MultiProvider by checking the check-box in the ‘Used’ column.

Check the Aggregation level by clicking on the ‘Check’ button. Save and activate the Aggregation level.

Steps in BEx Query Designer

            Once you have defined a query on one of the InfoProvider types listed above, you see the Planning tab under the Properties of structural components (in key figures or restricted key figures, for example). You can use the options here to set which structural components of an input-ready query you want to be input ready at run-time. For structural components that are not input ready, you can also set whether they are viewed as data not relevant for locking or are just protected against manual entry.

In the selection which is needed as Input-Ready, Go to Planning Tab of Properties and in Change Data select ‘Input ready (relevant for locking)’.

Finally in overall properties of query( Ctrl+P) in the Planning tab select ‘Start Query in Change Mode’.

RSRT Output

Then to add the entered values to the Real-time cube click on ‘Save’ and then ‘Transfer’.

BEx Analyzer Output

In BEx analyzer to add the entered values to the Real-time cube click on ‘Save Values’ and then ‘Transfer Values’.

Points to be noted:

• Ensure that Realtime InfoCube is in Planning Mode.

• To ensure that only one user is able to change data, “their” data is locked and cannot be changed by other users. Depending on the expected load (determined by the number of users working in parallel and the complexity of the selection), you can specify one of several lock processes as the default. The lock algorithm is used by BW-BPS and BI Integrated Planning.

• Lock can be released using the Tcode: SM12.

• All the Infoobjects selected in the aggregation level should be maintained in the query; otherwise at times Input Ready Field will be disabled.
• Once you click on Save in the Input Ready Query, then a request is created in the Manage Tab of your Info Cube.

• Data requests in real-time InfoProviders stay open until the number of records in the data request exceeds 50,000. When an application writes data to the request and the limit of 50,000 records is exceeded, the data is stored and the request is closed. Thus, a request can actually contain more than 50,000 records.
• It is still possible to roll-up and define aggregates, compress and so on.
• Note that switching from planning to loading automatically closes the open planning request.

Upgrade/Migration/Implementation/Systemcopy -
SAPNetWeaver Business Warehouse 7.3 and Higher

Product Road Map Updates => the mayor source of all Product Updates

BLOG:SAP BW? - three things to know ...

Workshop - Migrate your BW System database to SAP HANAfrom 17. - 20.03.2014 bookable for Customers and Partners!

Content

• SAP Business Intelligence Architecture
• BW Technical and Functional Upgrade
• BW and BI-JAVA Installation
• Migration to BW on HANA
• BW System Copy
• BW Housekeeping Tasks
• Event Presentations
• References/Experiences/DSAG

SAP Business Intelligence Architecture

• top

BW Technical and Functional Upgrade

BLOG: Software Update Manager (SUM): introducing the tool for software maintenance

BLOG: Good News - Easier Modeling of the SEM Add-On in Solution Manager

New:

Immediately after the upgrade to SAP NetWeaver BW 7.3x Note 1720495 (Invalid deimplementation of obsolete notes by SNOTE tool)should be applied.

 

With the release of SAP NetWeaver BW 7.30 new and innovative capabilities have been added to SAP's EDW premium solution. SAP NetWeaver BW 7.30 as the backbone for a successful usage of SAP BusinessObjects Platform and SAP Business Warehouse Accelerator - BWA is the heart of the SAP Business Intelligence Architecture. The updated presentation SAP NetWeaver 7.0x - Upgrade to SAP NetWeaver 7.30 ABAP BW (full version with complete technical details) provided you with must-know delta information to quickly and effective upgrade to SAP NetWeaver 7.30 BW including existing information from the resources of this page and the updates for SAP NetWeaver 7.30 EhP1 (7.31).

 

See also the changes to the existing BEx Versions 3.5 and 7.x after Upgrade to NetWeaver BW 7.30 or 7.31
Be sure to read these Notes prior to the technical Upgrade in order to prevent any unwanted incompatibilities or unforeseen changes.

• top

 

BW ABAP and BI-JAVA Installation

The Software Provisioning Manager 1.0 (SWPM) can be used to install all SAP NetWeaver 7.30 based instances onwards.

See the details of the Software Logistics Toolset 1.0 here.

 

See SAP NetWeaver BW Installation/Configuration (also on HANA). This document also includes the complete SAP NetWeaver BW basis customizing settings, together with an example configuration of the System Parameter. The guidance raises no claim to completeness.

New: It is now possible to install the ABAP CI as well on the HANA Appliance!
     Overview - SAP HANA and SAP NetWeaver AS ABAP o... | SAP HANA

     Note 1978179 - Early delivery of NW 7.40 SP06 (ABAP)

See all SAP First Guidance Documents here -BW on SAP HANA First Guidance Collection

 

New Installation of  SAP BI JAVA 7.30 - Options, Connectivity and Security

With the release of SAP NetWeaver 7.30 all previous J2EE stacks are now synchronized in one platform. BI JAVA 7.30 is still available with the usage type BI-JAVA to connect to an existing SAP NetWeaver BW 7.30 stack for the classical usage of BEx Web or the native dashboards (former Xcelsius). The presentation SAP NetWeaver 7.30 – BI JAVA Implementation shows the new SAP NetWeaver 7.30 installation and configuration options with the functional unit configuration UI (former CTC BI-Java Template) All informations are also valid vor SAP NetWeaver 7.30 EhP1 (7.31)

 

SAP NetWeaver 7.0 - Deinstalling Java Add-In (also valid for SAP NetWeaver 7.30 JAVA Add-In)

The separation of the doublestack (ABAP and JAVA in one instance) into two separate stacks is a SAP recommendation. An option available since SAP NetWeaver BW 7.0 is the deinstallation of the Java Add-In with SAPInst. This presentation provides details and guidance about the process to prepare for upgrade to SAP NetWeaver BW 7.30, concentrating on the ABAP stack.

 

As a successor for most scenarios, we offer the combined export of the Java system, deinstallation of the Java Add-In and installation of a new Java system using the dual-stack split tool available as part of the SL toolset 1.0 (SP5). For more information, see "Dual-Stack Split".

 

If you are running SAP NetWeaver 7.30 JAVA Add-In you can use the software provisioning manager 1.0 (SWPM) as part of the SL toolset for the deinstallation process, as this always contains the latest software components (Note 1680045). Note that the dual split process is not supported for SAP NetWeaver 7.30 systems (Note 1655335)

 

With SAP NetWeaver 7.3x JAVA the Functional Unit Configuration UI (former CTC BI-JAVA Template) is available

 

In Advance check the WebAS/SSO Settings after the Upgrade to NetWeaver 7.3x. The settings are almost identical to NetWeaver BW 7.0x

• top

 

Migration to BW on HANA

Migration to HANA made easy with DMO

DMO is an option of SUM (Software Update Manager) for a combined update and migration: update an existing SAP system to a higher Software Release and migrate to SAP HANA database including the unicode conversion of the source database. The procedure is only available for systems based on AS ABAP, hence the executable SAPup is used in background. DMO migrates from an existing relational database type (“anyDB”) to SAP HANA. Software Update Manager (SUM) is the tool for system maintenance: Release upgrades, EHP implementation, applying SP stacks.

 

SAP First Guidance - Migration BW on HANA using the DMO option in SUM

Database Migration Option (DMO) of SUM - Introduction

 

more flexibility with BW Post-Copy Automation

To reduce downtime for your production landscape, one of the recommended migration paths of SAP NetWeaver Business Warehouse (SAP NetWeaver BW) to SAP NetWeaver BW on SAP HANA comprises a system copy of your SAP NetWeaver BW system. The system copy procedure of SAP NetWeaver BW systems and landscapes is complex for a number of reasons however. A large number of configuration settings are involved for example (such as connections and delta queue handling for data loading), as well as system copy scenarios of SAP NetWeaver BW (each with different landscape aspects) that have to be handled as part of every system copy, regardless of whether the system copy is part of the migration to SAP HANA or you want to perform regular system copies of your SAP NetWeaver BW landscape.

 

DSAG Technology Days 2014 - Migration BW on HANA - Update 2014 | SCN

 

To achieve this, SAP NetWeaver Landscape Virtualization Management offers preconfigured "task lists" used by the ABAP task manager for lifecycle management automation.

You can also enable SAP NetWeaver BW powered by SAP HANA to “go productive” with parallel operation of your existing production system, both connected to the same back-end systems. This is achieved with a special and unique automated solution for delta queue cloning and synchronization on production systems.

SAP Note 886102 (SMP login required) thus becomes obsolete. Using the post-copy automation for SAP NetWeaver BW (BW PCA) in the migration process of SAP NetWeaver BW to SAP NetWeaver BW on SAP HANA, this process can be shortened by weeks and becomes easier, faster and more reliable.

 

The Presentation Teched 2012 - Session EIM300  illustrates the Migration to BW on HANA from an end-to-end perspective.

 

BLOG:Three things to know when migrating NetWeaver BW on HANA

BLOG: Upgrade and Migration - BW on HANA

BLOG: Where to find information on SAP BW on HANA migrations

BLOG: SAP NetWeaver BW Powered by SAP HANA Scale Out - Best Practices

BLOG: The SAP Hana Reference for NetWeaver Basis Administrators

 

 

• top

 

BW System Copy

 

SAP NetWeaver 7.30 BW - Systemcopy ABAP

Since Release 7.30 SP05, it is now possible to perform a heterogenous system copy (incuding unicode migration) to migrate existing systems based on SAP NetWeaver BW 7.30 SP05 and higher to SAP NetWeaver BW on HANA (HDB) based systems.

With this major step forward, a new procedure called "Post Copy Automation (BW PCA)" now supports customers with what can often be complex post-steps before and after the homogenous/heterogenous BW system copy. This presentation is the delta information to the existing document "SAP NetWeaver 7.0 - BW Systemcopy ABAP" shown above. The technical Improvements with the leaner data model provides advantages with BW on HANA too.

To ease this generic step of BW system copy, a new procedure called "BW Post Copy automation (BW PCA)" is available, which supports customer now in the complex pre and post steps during the homogeneous/heterogeneousBW system copy (information from the SAP ALM group) procedure.

Please note that these procedure can be used independently from your BW and Database Version starting fromNetWeaver 7.0x

 

We distinguish between two use cases explained in the FaQ for BW-PCA:

- initial copy based on an existing original BW system and connected BW source systems

  Task Lists - SAP_BW_COPY_INITIAL_PREPARE (BW systems only) andSAP_BW_BASIS_COPY_INITIAL_CONFIG

- refresh of an existing system based on an existing BW system and connected BW source systems

  Task List - SAP_BW_BASIS_COPY_REFRESH_CONFIG

 

The following Notes are the pre-requisites for the use cases (included in 7.01 SP14 and higher):

- Note 1683554 - SAPI tasks for System Copy Automation

- Note 1844297 - Corrections on SAPI-Tasks for System Copy Automation

- Note 1614266 - System Copy: Post Copy Automation (PCA) / LVM

- Note 1707321 - BW System Copy: Note analyzer Post Copy Automation (BW-PCA)

- Note 1780190 - SAPI Corrections for System Copy Automation- Refresh Usecase

- Note 1894679 - Avoiding the conversion of BW DataSources by BDLS

Updating to the minimum level of the mentioned Support Stacks is recommended to minimize the manual effort.

 

For both cases the BW-PCA Tasklists support the Customer together with the software provisioning manager 1.0 (SWPM) in these software lifecycle management tasks. BW-PCA is embedded in the SAP NetWeaver Landscape Virtualization Management

• top

 

 

BW Housekeeping Tasks

 

Important Housekeeping Principles for keeping your SAP NetWeaver BW in good shape

In this session, you will learn about various housekeeping activities that should be part of the operational concept of your Enterprise Data Warehouse. These housekeeping activities will support you in removing unwanted and unneeded data as well as unused metadata. Scheduling these activities regularly in the system will ensure optimum utilization of system resources while at the same time increasing the overall system performance.

 

New: SAP First Guidance - BW Housekeeping and BW-PCA

 

New: Note 1829728 - BWHousekeeping Task List

(contains manual steps ZNOTE_1829728_PRE_70x/ZNOTE_1829728_PRE_73x, and automated steps applied with SNOTE)

The newly released Housekeeping Task List (Pre/Post Steps) allows you to automate mandatory tasks prior to upgrade/migration with DMO to ensure the quality of the migration process and the health of your BW System.

SCN:Create #SAP #BW Housekeeping task list

BLOG:House Keeping / Performance Tuning Activities in SAP BW Systems

 

Apply the following Notes in advance and run the tasks in advance to ensure smooth implementation of the BW Housekeeping Task List.

Note 1710719 - Corrections on SAPI-Tasks for System Copy Automation

Note 1767420 - Task Manager for Technical Configuration (6. Improvements)

(contains manual steps ZNOTE_1767420, and automated steps applied with SNOTE)

To solve the problem with the endless loop on the last task, apply the following Note:

Note 1880465 - SAP_BW_HOUSEKEEPING not terminating

• top

 

Event Presentations

TechEd 2012 Las Vegas/Madrid

TechEd 2013 Las Vegas/Amsterdam

 

Navigating and Networking at SAP TechEd => Live from TechEd Amsterdam, Replay from 05.11.2013, 18.00 Uhr

 

• top

 

 

References/Experiences/DSAG

This is a collection of ressources from the SAP SCN Network and it´s content is not reflecting the findings from this Document of future Upgrade and Enhanchements.

See how the german customer Kärcher upgraded their BW System Landscape (Three System plus Sandbox) within 8 weeks including BI-IP and BIA. It is still a good reference from the project perspective

 

See Dr. Berg's Upgade to 7.30 Experience. This is a overview Presentation based on 2011 findings.

See the Doc - SAP BW 7.3 Promising Features This is a very nice overview based on the 2012 findings.

Recent Blog - SAP BW 7.3 Upgrade Issues and Solutions is based on 2013 findings, esspecially application side.

Blog - BW 7.30: Hierarchy loading becomes easier with the help of new framework

DSAG Forum: "Upgrade NetWeaver BW 7.3x" => (DSAG-ID requested) share you experience with other DSAG members.

• top

 

This Document will explain only in a very high level on how to use the interrupts and events in a Process chain effectively.

The advantages of using interrupts and events in a Process chain are many. It handles the lookups easily, gives us more flexibility to run many chains in parallel using Meta chains depending on the system size, provides an easy way to monitor and resolve issues and it uses  all standard SAP.

I have below used two process chains one raising the event and the other one capturing the event using interrupt process.  This process chains can be run in two ways. First trigger PC1 this will raise an event. Then trigger PC2 this will capture that event and then allow the DTP to run.

Second way is trigger Pc 2 first then it will wait in the interrupt stage for the event to be raised. Only when the Pc1 is triggered and raised an event then the PC2 continues and load DTP.

Now this is only in a high level. But imagine we have so many Meta chains and so many dependent and non-dependent Process chains and with many lookups. Then this approach can be used very effectively

PC 2 :

Thanks,

Sathya

Hi All,

These days, BODS is playing a very important role in SAP system landscape.

Many customers use BODS to pull data from Non-SAP systems and load to SAP BW.

These documents are primarily intended for BW Consultants who would like to know more about integration, modelling, and transport mechanism related to BODS.

In part 1, we have gone through integration between BW and BODS using RFC Functionality.(http://scn.sap.com/docs/DOC-48917)

In part 2, we have gone through BODS modelling especially when we have SAP BW as a data target. (http://scn.sap.com/docs/DOC-52550)

In this part 3 document, we will try to understand the transport mechanism within BODS.

1) Log into the BODS Development server

2) Go to Tools Menu --> Export Option.

3)  Navigate to the flow which you wants to transport.

In this case, I want to transport the Financier job and the included objects to the Production system.

4) Drag the required job to 'Objects to Export' Pane:

5) After step 4, the datastores included in the job will automatically get collected in the 'Datastores to export' pane.

In my case, the source datastore is the Oracle CRM and target datastore is BW target.

Also, I have already transported the above 2 datastores previously. So I will exclude both the datastores in this transport.

6) Excluded datastores will be shown in Red cross mark

7) Now Right click on the selected job and click 'Export to XML file' option.

Export to ATL file is another option to transport, but it is not in scope of this document.

8) Save the xml file in a convenient folder, In this case I am saving it in my Desktop,

9) System will prompt you to enter a password. This will be required in later stage.

10) You get will get the status of Export.

11) Now open the file which you saved in step 8.

(Using open with  --> Notepad option)

12) Open the notepad and find the source CRM Dev connection name and replace(all) it with oracle CRM Prod connection name.

Source -- APPS

Target -- CRMTST1

13) Similarly do the same for BODS Connections aswell.

Dev - SAPBODSDEV

Prod - BODSPB1

14) Enter the BODS designer and give the Production Credentials.

15) Goto Tools --> Import from file.

16) Select the XML file from the saved folder(in my case, it's desktop)

17) System will prompt you for a password.

Give the same password entered in step 9.

18) Now you will see the exported job and the related objects in the Production environment.

19) Remember to change the source system names in BW aswell.

BW --> RSA1 --> Tools Menu --> Conversion of Logical Systems Name.

Hope you got a basic understanding on the transport/Export mechanism in BODS.

Regards,

Prabhith

This page provides  information,  about the new functionalities provided with SAP NetWeaver Business Warehouse 7.4 in general and the new functionalities of SAP NetWeaver BW powered by SAP HANA provided with SAP NetWeaver Business Warehouse 7.4 - SP 05

Preliminary delivery of Support Package 6 for SAP NetWeaver BW 7.4

The planned delivery of the regular of SAP NetWeaver BW 7.4 SP 6 is scheduled for middle of March as announced on the official SMP delivery schedule.

Due to a high amount of requests a preliminary version of this SP 6 was released. Please read SAP Note 1978179 - Early delivery of NW 7.40 SP06 (ABAP) to learn about the implied restrictions and the download instructions.

SAP NetWeaver BW 7.4 SP05 is released!

Read the information on the Support Package page for SAP NetWeaver BW 7.4

SAP BW? - Three Things to Know ... Blog by Roland Kramer.

General Availability Care Program for SAP NetWeaver BW 7.4 SP05

For SAP NetWeaver BW 7.4 Support Package 05, we offer the SAP general availability care (GAC) program. Via the SAP GAC program, SAP reaches out to the first customers who receive SAP’s new solution for Business Warehouse and who want to implement one of the key topics listed below. With your active participation, you help SAP to gain early feedback from the productive usage of the latest software which may serve as a basis for further improvements. At the same time, SAP would like to engage with productive customers who are interested in a collaboration regarding marketing and communication activities for the new functionalities provided

Overview SAP BW 7.4 SP05 on SAP HANA and further Roadmap

SAP NetWeaver BW on SAP HANA continues to be the  cornerstone of SAP’s strategic vision for enterprise data warehousing providing organizations a solid data foundation to capture, store, transform and manage data in a scalable, enterprise-ready data warehouse. And as new challenges arise in the market (exploding data volumes, new data sources, the need for real-time information access, etc), SAP BW on HANA continues to evolve in order to meet the growing challenges imposed on IT by these ever changing market forces. The release of SAP BW running on SAP HANA is a great example of how SAP BW has evolved to ensure organizations continue to leverage  their investment in SAP BW to meet these new  challenge.

See this presentation to learn what SAP is doing next to evolve SAP BW on SAP HANA with the SAP BW 7.4., SP 05 on HANA

Key Features

• Enhanced Data Modeling
  • Common Eclipse based Modeling Tools
  • BW/HANA Smart Data Access providing the logical EDW
  • Easy integration of external data models with Open ODS Layer
  • Further reduce data layers in BW via Operational Data Provisioning
  • New Composite Provider
• Push down further processing logic to HANA
  • BW Analytic Manager
  • HANA  Analysis Processes
  • BW Transformations
  • PAK (Planning Application Kit) – Pushing down more planning semantics
• Converged planning solutions (i.e. BPC unified)

Recommendations:

• Apply SAP NetWeaver BW 7.4 with support package lower than SP 5 for Embedded Use Case scenarios only
• For EDW Use Case scenarios: Start only with SAP NetWeaver BW 7.4 SP05
• If you plan to upgrade your ERP first to EhP7 (based on NetWeaver 7.40), you MUST first upgrade your corresponding BW System at least to 7.31 or higher, to stay compatible with the ERP Backend, check the Information attached to the following SAP Notes
  • Note 1388258 - Version Interoperability within the SAP Business Suite
  • Note 1951805 - Adjusted Version Interoperability for Business Suite 7i2013
• If you are running  SAP BusinessObjects BI Suite on SAP NetWeaver 7.4, please be aware of the following:
  • SAP BusinessObjects BI Suite 4.1 Support Pack 1  or BusinessObjects BI Suite 4.0 Support Pack 6 is mandatory! Lower SP levels do not incorporate the enhancements delivered with SAP NetWeaver 7.4
  • See more in the SAP BusinessObjects BI Suite release restriction e.g. SAP BusinessObjects BI Suite   4.1 Support Pack 1 Release Restrictions
• If you are still running Query Designer 3.x on your BW system, please note the following:
  • The BEx tools from SAP BW 3.5 are not available in SAP NetWeaver 7.40. Whereas the Analytic Engine of BW 7.4 can still execute queries which were  with the defined with the BEx 3.5 Query Desginer, the workbooks  created with the BEx Analyzer or WEB Templates need to be migrated . Please read “Cookbook for Migration to BEx 7.0” in SAP Note 1807522 - BEx 3.5 Objects Migration to BEx 7.0
  • If you are upgrading your BW system to BW 7.40 and are still using the obsolete Query Designer 3.x, SAP provides the following additional information:
    • To check which old query features are no longer supported in 7.40, use the reporting tool described in SAP Note 1911469.
      This tool will check the queries in your system and shows those which contain features that are no longer supported.
      Note 1911469 - Check report for discontinued query features in 7.40
      Note 1962865 - Check ReportSAP_QUERY_CHECKER_740 dump
    • Use the report attached to Note 1915309 - Query Migration Tool – 3.x to 7.x to do a mass migration of the existing queries.
    • You find can find a list of obsolete functions and proposed workarounds in the SAP Help Library
    • The detailed maintenance strategy for the SAP NetWeaver 04 BW 3.5 front-end add-ons is described  in SAP Note 1932461
  • SAP strongly advises you to read the available documentation thoroughly in order to benefit from the support SAP offers now and in the future, and to make it easier for the customer to make the transition away from the obsolete reporting tools.
  • More information can also be found under http://scn.sap.com/community/business-explorer
• Pre upgrade activities are described in SAP Note 1879618 - Pre Upgrade Activities for Upgrade/Update to 7.4
• Do not upgrade lower than NetWeaver 7.40 SR1! (which is SP05)
  Note 1962880 - RDDMASGL job fails during ACT_UPG phase during Netweaver 7.4 upgrade
• Oracle and DB6 based systems: please check the following SAP Note:
  Note 1805195 - Handling and troubleshooting of tablespaces during Upgrades, EhPs and SPs updates
• The maximum length of texts for characteristic values is increased. For changes that might be advised, please see SAP Note1823174 - BW7.40 Changes and customer-specific programs
• Please read also SAP Note1600929 - SAP BW powered by SAP HANA DB: Information and1729988 - SAP NetWeaver BW powered by SAP HANA - Checklist Tool

• If the SEM Add-On is applied on the NetWeaver system, you can change the modeling in the Solution Manager for better handling at any time,  see the blog "Good News - Easier Modeling of the SEM Add-On in Solution Manager"

Additional Information:

Positioning of SAP NetWeaver Business Warehouse powered by SAP HANA and SAP HANA Live for SAP Business Suite

  Roadmap for SAP NetWeaver BW on SAP HANA - One slider

SAP NetWeaver 7.4  BW ABAP Support Packages Schedule and Implications

Applies to

SAP BI Input Ready Query- Integrated Planning in SAP BI.

For more information, visit the Business Intelligence homepage.

Summary

This article describes the steps required to build an Input Ready Query to load data into BW system through BI Integrated Planning. It also describes the steps to create MultiProvider, Aggregation level and input enabled query.

Integrated Planning

            Planning is an integral part of the management cycle. The management cycle helps companies to position themselves in complex environments and to keep on track in reaching their overall company goal. Planning supports decision making, the coordination of different divisions towards a common goal and defines general conditions for operation.

            BI Integrated Planning provides business experts with an infrastructure for realizing and operating planning scenarios or other applications. BI Integrated Planning can be used to create process-oriented planning.

            BI Integrated planning fulfills both the end user’s and the administrator’s wishes at the same time. The end user can work from a plan query that is equally valid for all planners in a planning area, can open Excel offline planning and then carry out significantly more detailed planning there. Only part of this data is then written back to the enter-able query; that is, the part refers to the cell in question.

Overview of Input Ready Query

                   Input-ready queries are used to create applications for manual planning. These can range from simple data entry scenarios to complex planning applications. You define queries for manual planning in BEx Query Designer. In Web Application Designer or BEx Analyzer, you can combine input-ready queries with other queries and planning functions to create complex planning applications.

            A query that is defined upon an InfoProvider of type aggregation level, it is input ready and can be used for manual planning. Whether a particular cell is input ready depends on the drill-down, specifically whether characteristic relationships and data slices are permitted for the cell.

Prerequisites

            Fundamentals of SAP Business Intelligence, SAP Integrated Planning. Good knowledge of BEx.

Business scenario

            The business requirement is to have a Dispatch Plan upon the actual data. Architecturally this has been enabled by using actual InfoCube which provides the available Data that is used for reporting. The goal is to enable an Input Ready field for Dispatch Plan in Report that allows users to enter data which in background will get updated to the Realtime Cube.

            In the example below Actual Cube is ‘ZS_ICACT’ which contains necessary data for reporting and ‘ZS_IPTRD’ is the Realtime cube that’s used to store the data entered through the reports.

How to start with Integrated Planning:

Creating a Real Time Info Cube

            Real-time Info Cubes differ from Standard Info Cubes in their ability to support parallel write accesses. Standard Info Cubes are technically optimized for read accesses to the detriment of write accesses.

Right click on the Info Area and select ‘Create Info Cube’.

Give name for InfoCube and click on ‘Create’ button. ‘ZS_IPTRD’ is the name of the InfoCube.

Creating a Multi Provider

            A MultiProvider is a type of InfoProvider that combines data from a number of InfoProviders and makes it available for reporting purposes. The MultiProvider does not itself contain any data. Its data comes entirely from the InfoProviders on which it is based. These InfoProviders are connected to one another by a union operation. 

            MultiProviders only exist as a logical definition. The data continues to be stored in the InfoProviders on which the MultiProvider is based. A query based on a MultiProvider is divided internally into subqueries. There is a subquery for each InfoProvider included in the MultiProvider. These subqueries are usually processed in parallel.

Right click on the Info Area and select ‘Create MultiProvider’.

Give name for MultiProvider and click on ‘Create’ button. ‘ZS_MULPRO’ is the name of the Multi Provider.

In the next screen, select the Info Cubes which should be in the MultiProvider. So select the check-box for ‘ZS_ICACT’ and ‘ZS_IPTRD’.

Drag and drop Info Objects from the ‘Involved Info Providers’ pane to the right side pane of MultiProvider. 0Calday and 0Calyear should be dragged to the dimension ‘Time’. Drag key figures to the dimension ‘KeyFigures’. Drag Material to the dimension ‘Dimension1’.

Right click on any characteristic and select the option ‘Identify (Assign)’.

Select the check-boxes for the InfoProvider.

In the same way assign all characteristics and keyfigures to both Info Cubes and activate the MultiProvider.

Steps in Planning Modeler

            Go to tcode RSPLAN. Click on the button ‘Start Modeler’ to start the Planning Modeler.

            The Planning Modeler is a Web-based modeling environment for all tasks related to planning. The Planning Modeler is the central modeling tool for all planning-specific objects. You can use the Planning Modeler to model, manage and test all the metadata that belongs to the planning scenario. The different objects are maintained in the modeler in connection with planning, such as aggregation levels, as are the relationships between these objects.

Give the name of the MultiProvider and click on either ‘Start’ button or press ‘Enter’ key.

The Info Objects of the MultiProvider will be listed in the lower part of the screen.

Aggregation levels

            To determine the level on which data can be entered or changed (manually through user input or automatically by a planning function), you define an InfoProvider of type aggregation level. An aggregation level consists of a subset of the characteristics and key figures of a MultiProvider or real-time InfoCube. Real-time InfoCubes are used to store data.

            All Info Objects of the MultiProvider will be listed. Select the Info Objects that should be included in the MultiProvider by checking the check-box in the ‘Used’ column.

Check the Aggregation level by clicking on the ‘Check’ button. Save and activate the Aggregation level.

Steps in BEx Query Designer

            Once you have defined a query on one of the InfoProvider types listed above, you see the Planning tab under the Properties of structural components (in key figures or restricted key figures, for example). You can use the options here to set which structural components of an input-ready query you want to be input ready at run-time. For structural components that are not input ready, you can also set whether they are viewed as data not relevant for locking or are just protected against manual entry.

In the selection which is needed as Input-Ready, Go to Planning Tab of Properties and in Change Data select ‘Input ready (relevant for locking)’.

Finally in overall properties of query( Ctrl+P) in the Planning tab select ‘Start Query in Change Mode’.

RSRT Output

Then to add the entered values to the Real-time cube click on ‘Save’ and then ‘Transfer’.

BEx Analyzer Output

In BEx analyzer to add the entered values to the Real-time cube click on ‘Save Values’ and then ‘Transfer Values’.

Points to be noted:

• Ensure that Realtime InfoCube is in Planning Mode.

• To ensure that only one user is able to change data, “their” data is locked and cannot be changed by other users. Depending on the expected load (determined by the number of users working in parallel and the complexity of the selection), you can specify one of several lock processes as the default. The lock algorithm is used by BW-BPS and BI Integrated Planning.

• Lock can be released using the Tcode: SM12.

• All the Infoobjects selected in the aggregation level should be maintained in the query; otherwise at times Input Ready Field will be disabled.
• Once you click on Save in the Input Ready Query, then a request is created in the Manage Tab of your Info Cube.

• Data requests in real-time InfoProviders stay open until the number of records in the data request exceeds 50,000. When an application writes data to the request and the limit of 50,000 records is exceeded, the data is stored and the request is closed. Thus, a request can actually contain more than 50,000 records.
• It is still possible to roll-up and define aggregates, compress and so on.
• Note that switching from planning to loading automatically closes the open planning request.

Upgrade/Migration/Implementation/Systemcopy -
SAPNetWeaver Business Warehouse 7.3 and Higher

Product Road Map Updates => the mayor source of all Product Updates

BLOG:SAP BW? - three things to know ...

Workshop - Migrate your BW System database to SAP HANAfrom 17. - 20.03.2014 bookable for Customers and Partners!

Content

• SAP Business Intelligence Architecture
• BW Technical and Functional Upgrade
• BW and BI-JAVA Installation
• Migration to BW on HANA
• BW System Copy
• BW Housekeeping Tasks
• Event Presentations
• References/Experiences/DSAG

SAP Business Intelligence Architecture

• top

BW Technical and Functional Upgrade

BLOG: Software Update Manager (SUM): introducing the tool for software maintenance

BLOG: Good News - Easier Modeling of the SEM Add-On in Solution Manager

New:

Immediately after the upgrade to SAP NetWeaver BW 7.3x Note 1720495 (Invalid deimplementation of obsolete notes by SNOTE tool)should be applied.

 

With the release of SAP NetWeaver BW 7.30 new and innovative capabilities have been added to SAP's EDW premium solution. SAP NetWeaver BW 7.30 as the backbone for a successful usage of SAP BusinessObjects Platform and SAP Business Warehouse Accelerator - BWA is the heart of the SAP Business Intelligence Architecture. The updated presentation SAP NetWeaver 7.0x - Upgrade to SAP NetWeaver 7.30 ABAP BW (full version with complete technical details) provided you with must-know delta information to quickly and effective upgrade to SAP NetWeaver 7.30 BW including existing information from the resources of this page and the updates for SAP NetWeaver 7.30 EhP1 (7.31).

 

See also the changes to the existing BEx Versions 3.5 and 7.x after Upgrade to NetWeaver BW 7.30 or 7.31
Be sure to read these Notes prior to the technical Upgrade in order to prevent any unwanted incompatibilities or unforeseen changes.

• top

 

BW ABAP and BI-JAVA Installation

The Software Provisioning Manager 1.0 (SWPM) can be used to install all SAP NetWeaver 7.30 based instances onwards.

See the details of the Software Logistics Toolset 1.0 here.

 

See SAP NetWeaver BW Installation/Configuration (also on HANA). This document also includes the complete SAP NetWeaver BW basis customizing settings, together with an example configuration of the System Parameter. The guidance raises no claim to completeness.

New: It is now possible to install the ABAP CI as well on the HANA Appliance!
     Overview - SAP HANA and SAP NetWeaver AS ABAP o... | SAP HANA

     Note 1978179 - Early delivery of NW 7.40 SP06 (ABAP)

See all SAP First Guidance Documents here -BW on SAP HANA First Guidance Collection

 

New Installation of  SAP BI JAVA 7.30 - Options, Connectivity and Security

With the release of SAP NetWeaver 7.30 all previous J2EE stacks are now synchronized in one platform. BI JAVA 7.30 is still available with the usage type BI-JAVA to connect to an existing SAP NetWeaver BW 7.30 stack for the classical usage of BEx Web or the native dashboards (former Xcelsius). The presentation SAP NetWeaver 7.30 – BI JAVA Implementation shows the new SAP NetWeaver 7.30 installation and configuration options with the functional unit configuration UI (former CTC BI-Java Template) All informations are also valid vor SAP NetWeaver 7.30 EhP1 (7.31)

 

SAP NetWeaver 7.0 - Deinstalling Java Add-In (also valid for SAP NetWeaver 7.30 JAVA Add-In)

The separation of the doublestack (ABAP and JAVA in one instance) into two separate stacks is a SAP recommendation. An option available since SAP NetWeaver BW 7.0 is the deinstallation of the Java Add-In with SAPInst. This presentation provides details and guidance about the process to prepare for upgrade to SAP NetWeaver BW 7.30, concentrating on the ABAP stack.

 

As a successor for most scenarios, we offer the combined export of the Java system, deinstallation of the Java Add-In and installation of a new Java system using the dual-stack split tool available as part of the SL toolset 1.0 (SP5). For more information, see "Dual-Stack Split".

 

If you are running SAP NetWeaver 7.30 JAVA Add-In you can use the software provisioning manager 1.0 (SWPM) as part of the SL toolset for the deinstallation process, as this always contains the latest software components (Note 1680045). Note that the dual split process is not supported for SAP NetWeaver 7.30 systems (Note 1655335)

 

With SAP NetWeaver 7.3x JAVA the Functional Unit Configuration UI (former CTC BI-JAVA Template) is available

 

In Advance check the WebAS/SSO Settings after the Upgrade to NetWeaver 7.3x. The settings are almost identical to NetWeaver BW 7.0x

• top

 

Migration to BW on HANA

Migration to HANA made easy with DMO

DMO is an option of SUM (Software Update Manager) for a combined update and migration: update an existing SAP system to a higher Software Release and migrate to SAP HANA database including the unicode conversion of the source database. The procedure is only available for systems based on AS ABAP, hence the executable SAPup is used in background. DMO migrates from an existing relational database type (“anyDB”) to SAP HANA. Software Update Manager (SUM) is the tool for system maintenance: Release upgrades, EHP implementation, applying SP stacks.

 

SAP First Guidance - Migration BW on HANA using the DMO option in SUM

Database Migration Option (DMO) of SUM - Introduction

 

more flexibility with BW Post-Copy Automation

To reduce downtime for your production landscape, one of the recommended migration paths of SAP NetWeaver Business Warehouse (SAP NetWeaver BW) to SAP NetWeaver BW on SAP HANA comprises a system copy of your SAP NetWeaver BW system. The system copy procedure of SAP NetWeaver BW systems and landscapes is complex for a number of reasons however. A large number of configuration settings are involved for example (such as connections and delta queue handling for data loading), as well as system copy scenarios of SAP NetWeaver BW (each with different landscape aspects) that have to be handled as part of every system copy, regardless of whether the system copy is part of the migration to SAP HANA or you want to perform regular system copies of your SAP NetWeaver BW landscape.

 

DSAG Technology Days 2014 - Migration BW on HANA - Update 2014 | SCN

 

To achieve this, SAP NetWeaver Landscape Virtualization Management offers preconfigured "task lists" used by the ABAP task manager for lifecycle management automation.

You can also enable SAP NetWeaver BW powered by SAP HANA to “go productive” with parallel operation of your existing production system, both connected to the same back-end systems. This is achieved with a special and unique automated solution for delta queue cloning and synchronization on production systems.

SAP Note 886102 (SMP login required) thus becomes obsolete. Using the post-copy automation for SAP NetWeaver BW (BW PCA) in the migration process of SAP NetWeaver BW to SAP NetWeaver BW on SAP HANA, this process can be shortened by weeks and becomes easier, faster and more reliable.

 

The Presentation Teched 2012 - Session EIM300  illustrates the Migration to BW on HANA from an end-to-end perspective.

 

BLOG:Three things to know when migrating NetWeaver BW on HANA

BLOG: Upgrade and Migration - BW on HANA

BLOG: Where to find information on SAP BW on HANA migrations

BLOG: SAP NetWeaver BW Powered by SAP HANA Scale Out - Best Practices

BLOG: The SAP Hana Reference for NetWeaver Basis Administrators

 

 

• top

 

BW System Copy

 

SAP NetWeaver 7.30 BW - Systemcopy ABAP

Since Release 7.30 SP05, it is now possible to perform a heterogenous system copy (incuding unicode migration) to migrate existing systems based on SAP NetWeaver BW 7.30 SP05 and higher to SAP NetWeaver BW on HANA (HDB) based systems.

With this major step forward, a new procedure called "Post Copy Automation (BW PCA)" now supports customers with what can often be complex post-steps before and after the homogenous/heterogenous BW system copy. This presentation is the delta information to the existing document "SAP NetWeaver 7.0 - BW Systemcopy ABAP" shown above. The technical Improvements with the leaner data model provides advantages with BW on HANA too.

To ease this generic step of BW system copy, a new procedure called "BW Post Copy automation (BW PCA)" is available, which supports customer now in the complex pre and post steps during the homogeneous/heterogeneousBW system copy (information from the SAP ALM group) procedure.

Please note that these procedure can be used independently from your BW and Database Version starting fromNetWeaver 7.0x

 

We distinguish between two use cases explained in the FaQ for BW-PCA:

- initial copy based on an existing original BW system and connected BW source systems

  Task Lists - SAP_BW_COPY_INITIAL_PREPARE (BW systems only) andSAP_BW_BASIS_COPY_INITIAL_CONFIG

- refresh of an existing system based on an existing BW system and connected BW source systems

  Task List - SAP_BW_BASIS_COPY_REFRESH_CONFIG

 

The following Notes are the pre-requisites for the use cases (included in 7.01 SP14 and higher):

- Note 1683554 - SAPI tasks for System Copy Automation

- Note 1844297 - Corrections on SAPI-Tasks for System Copy Automation

- Note 1614266 - System Copy: Post Copy Automation (PCA) / LVM

- Note 1707321 - BW System Copy: Note analyzer Post Copy Automation (BW-PCA)

- Note 1780190 - SAPI Corrections for System Copy Automation- Refresh Usecase

- Note 1894679 - Avoiding the conversion of BW DataSources by BDLS

Updating to the minimum level of the mentioned Support Stacks is recommended to minimize the manual effort.

 

For both cases the BW-PCA Tasklists support the Customer together with the software provisioning manager 1.0 (SWPM) in these software lifecycle management tasks. BW-PCA is embedded in the SAP NetWeaver Landscape Virtualization Management

• top

 

 

BW Housekeeping Tasks

 

Important Housekeeping Principles for keeping your SAP NetWeaver BW in good shape

In this session, you will learn about various housekeeping activities that should be part of the operational concept of your Enterprise Data Warehouse. These housekeeping activities will support you in removing unwanted and unneeded data as well as unused metadata. Scheduling these activities regularly in the system will ensure optimum utilization of system resources while at the same time increasing the overall system performance.

 

New: SAP First Guidance - BW Housekeeping and BW-PCA

 

New: Note 1829728 - BWHousekeeping Task List

(contains manual steps ZNOTE_1829728_PRE_70x/ZNOTE_1829728_PRE_73x, and automated steps applied with SNOTE)

The newly released Housekeeping Task List (Pre/Post Steps) allows you to automate mandatory tasks prior to upgrade/migration with DMO to ensure the quality of the migration process and the health of your BW System.

SCN:Create #SAP #BW Housekeeping task list

BLOG:House Keeping / Performance Tuning Activities in SAP BW Systems

 

Apply the following Notes in advance and run the tasks in advance to ensure smooth implementation of the BW Housekeeping Task List.

Note 1710719 - Corrections on SAPI-Tasks for System Copy Automation

Note 1767420 - Task Manager for Technical Configuration (6. Improvements)

(contains manual steps ZNOTE_1767420, and automated steps applied with SNOTE)

To solve the problem with the endless loop on the last task, apply the following Note:

Note 1880465 - SAP_BW_HOUSEKEEPING not terminating

• top

 

Event Presentations

TechEd 2012 Las Vegas/Madrid

TechEd 2013 Las Vegas/Amsterdam

 

Navigating and Networking at SAP TechEd => Live from TechEd Amsterdam, Replay from 05.11.2013, 18.00 Uhr

 

• top

 

 

References/Experiences/DSAG

This is a collection of ressources from the SAP SCN Network and it´s content is not reflecting the findings from this Document of future Upgrade and Enhanchements.

See how the german customer Kärcher upgraded their BW System Landscape (Three System plus Sandbox) within 8 weeks including BI-IP and BIA. It is still a good reference from the project perspective

 

See Dr. Berg's Upgade to 7.30 Experience. This is a overview Presentation based on 2011 findings.

See the Doc - SAP BW 7.3 Promising Features This is a very nice overview based on the 2012 findings.

Recent Blog - SAP BW 7.3 Upgrade Issues and Solutions is based on 2013 findings, esspecially application side.

Blog - BW 7.30: Hierarchy loading becomes easier with the help of new framework

DSAG Forum: "Upgrade NetWeaver BW 7.3x" => (DSAG-ID requested) share you experience with other DSAG members.

• top

 

Hi All,

These days, BODS is playing a very important role in the SAP system landscape.

Many customers use BODS to pull data from Non-SAP systems to SAP BW.

These documents are primarily intended for BW consultants who would like to know more about the Integration, Modelling and Transport mechanism related to BODS.

In this part 1 document, we will go through how to integrate BW and BODS using RFC connection.(This topic has been explained many a times in SDN. For making 2nd and 3rd part more meaningful, I have included the integration as Part 1.

Part 2 will help you to understand how modelling is done in BODS with BW as the data target (http://scn.sap.com/docs/DOC-52550)

Part 3 will help you to understand the transport mechanism in BODS(http://scn.sap.com/docs/DOC-52808)

Environment:

BODS – Version is 14.0.3.273(Also BO and BODS are installed in the same server)

BW – BW7.3 (where BODS is now available in the source systems list in BW)

BODS/BO server is running on Windows platform and the BW OS is HP-UX and database is Oracle.

Step 1:

Login to RSA1 Source systems and create a new connection under BO Dataservices.

Please note that for all BW versions prior to 7.3, you will not see BODS as a source system.

In such case, you will have to depend on 'External System' source system type for creating the connection.

Right click on BODS and press create

Give the required credentials

Give the Logical system name(in this case - BODSPB1) and Source system name(description and in this case it is Logical system for SAP BODSPB1) .Type and release is not mandatory.

Give a Program id (in this case it is SAPBODSPB1) . This is a very important step.

Important point to be noted here is that when you give details for external source system in RSA1,better dont give the gateway host and gateway service in case if you are not 100% sure about it(in simple words, keeps them blank)

See discussion here --> http://scn.sap.com/thread/3247518

The system itself will manipulate it(default gateway value) with the program id, provided you give the same(case sensitive) in both the ends(BW and BODS)

Save and go back and give the required credentials..

Give credentials like BODS Repository, Job Server, Back ground BW user, Password and so on.

The same can be seen in SM59 also under TCP/IP connections.

Now BO Dataservices will have a connection names BODSPB1 under it.

Now log into BODS Management console and give the corresponding BW server details.

The required BW credentials can be obtained in the context menu of the BW server in the SAP Logon pad.

RFC Program id is the same one SAPBODSPB1(case sensitive) which we had given in BW side.

The user used here is of type Service User.

For RFC to work as expected, the status should be in STARTED state.

Check the RFC connection in SM59 by using Test Connection option.

The connection test should be successful.

There can be lot of issues which might come in between during the configuration,and it depends on the  landscape in which you work:

Anyways, please find some points which you can check if you encounter any issues in between.These were  some of the solutions that were given by experts when we were facing some challenges in integrating BW with BODS.

1) There can be a problem in the gateway; you need to contact your basis team for this issue.The gateway for BW might not have been opened to connect the BODS server, for checking this we need to ping the command telnet <hostname of BO server> 3300 in the BW server. If it's not listening, then gateway is the culprit.

2) Change the gateway to its port number.Find the port number in the services file (windows\ststem32\drivers\etc\) of a machine with the sap GUI installed.There is a chance that your BODS server doesn't have the sapGUI installed and doesn't have the services file and thus can't translate the gateway name to a port number. Installing the sapGUI may also fix an issue setting up the RFC but not being able to see it in the list of available RFC connections in the BODS console.

3) Check the SAP system number. The gateway service should SAPGWXX where XX is ur SAP system number.

Hope this was useful.

Regards,

Prabhith

During analysis for Cache memory I accidentally found few new features of BW 7.3 (EHP 1)

*(Please ignore if you already know this or not new )

Generally for process chain data load, we use delete index and create index option. This will make the data load fast and also aviod the locking error becasue of the indexes.

Similarly one should update the statistics data as well roll up data in cube (for aggregates).

Why should I maintained it in PC level, if I am loading the data into same infoProvider (say Cube) using multiple PCs.

Why not at Cube level.

Answer is with BW 7.3 via T Code RSDIPROP

As description indicate

In this transaction you edit the performance, data load, and

query properties of an InfoProvider

Go to DB Performance and get various options to manage the data load as below

The F1 help available for more info.

Also Other tab page like Roll Up will give option to select the roll up process used for aggregate and Cache setting options at cube level to improve report performance.

DSO and even infoobject properties can also be set if they are also infoproviders

I found it useful and hence to share.

Thank-You.

Regards,

VB

SAP NetWeaver BI Java 7.3 SP/Patch Upgrade without NW Stack Upgrade

File operations in SAP Application server (AL11) using UNIX Command

Applies to:

SAP BW 3.5, BI 7.0

Summary

This paper demonstrates how to implement basic file operations like move, merge and delete files in SAP Application server (AL11) by calling UNIX script file through OS commands and to automate the OS command through process chain.

Introduction

UNIX shell

A Unix shell is a command language interpreter, the primary purpose of which is to translate command lines typed at a terminal into system actions. The shell itself is a program through which other programs are invoked. The shell has some built-in functions, which it performs directly, but most commands that you enter cause the shell to execute programs that are external to the shell. This sets the shell apart from other command interpreters, because it is just another user program at the same time that it functions almost exclusively as a mechanism for invoking other programs. With Shell we can use standard UNIX commands as building blocks to create new commands.

External Commands

An external command is a pre-defined operating system command that can be executed within the SAP system. Both the maintenance and execution of external commands is protected with SAP authorizations. You can maintain and execute external commands in dialog (from the CCMS menu) or in ABAP programs, using special function modules. External commands can also be executed as a step in a background job.

As the CCMS administrator, you can modify commands and activate additional security mechanisms without having to change the program. You can add your own commands and parameters to the variety of (pre-defined) commands delivered by SAP

Business Scenario

  There can be scenarios to perform basic file operations (like move, merge, Zip, delete etc.) on files generated in AL11 via Open hub destinations or APDs. These operations can be achieved in SAP BW by direct use of UNIX commands in OS command or calling UNIX script file through OS command.

Consider that an open hub destination is generating .csv file in AL11. Every time when you run the DTP for that Open hub it will overwrite the existing file which was already generated. So if we need to retain the previously generated file, then every time when a file is generated we can move it to a new file with time stamp in the file name. There can be a requirement to merge files generated in AL11 to a single file before sending out of SAP BW. Similarly as a part of data retention & clean up activity it may be required to delete older files.

Procedure to implement the above scenarios

In this approach we will create a UNIX script file (UNIX commands for the file handling operations are written in this file) and access this UNIX script file through OS command.

Following steps will demonstrate how to achieve the above mentioned scenarios.

Step 1:

Create UNIX script file containing UNIX commands for performing the required file handling operations.

Write the UNIX script in notepad and save it as “.sh” file format.

Below provided sample code will merge two files (FILE1 and FILE 2) into a single file with a new name (MERGERFILE) and timestamp. It will also delete files with name starting ‘MERGEFILE’ in AL11 older than 30 days.

Sample code:

timestamp=$( date +%Y%m%d%H%M%S )              */ Assign server time stamp to variable timestamp.   

cat /var/opt/sapbi/FILE1.txt  /var/opt/sapbi/FILE2.txt  > /var/opt/sapbi/ MERGEFILE"$timestamp".txt

*/ Combine the data in FILE1 & FILE2 present the path /var/opt/sapbi/ into a new file and the new file will have name MERGEFILE preceded by the timestamp at which it was generated.

find /var/opt/sapbi/ -type f -name ' MERGEFILE*.txt.gz' -mtime +29 -exec rm {} \;

*/ Files having name starting with MERGEFILE and older than 30 days present in the path /var/opt/sapbi/ in AL11 will be deleted

Upload the unix script file into Application server (AL11). 

Function module: ARCHIVFILE_CLIENT_TO_SERVER can be used to upload.

UNIX command syntax used and its meaning:

cat [path of file1] [path of file2] > [path of merged file] : This command will merge the mentioned files present in the given path and make a new merged file in the mentioned path with the given name.

gzip [path of file]   : this command will zip the file.

Step 2:

Go to Tcode SM69 and click on create button to create OS command as shown below:

Enter the details:

Command name: Give a name for the command.

Operating system command: sh

Parameters for operating system command: enter the UNIX script file path.                                               

Command sh will trigger/execute the script file mentioned in the parameter box.

Below are the screenshots of application server:

UNIX script file “Script.sh” is uploaded in AL11

FILE1 & FILE2 present in AL11. This may be generated by open hub destinations or APDs or flat file loads.

Data in FILE1:

Data in FILE2:

Click on “Execute” button after opening the OS command in SM69 to execute it.

Merge file generated in AL11 after execution of the OS command.

Data in Merge File:

If gzip command is used, then generated file will be zipped and will have extension as.gz

If this file handling has to be done after the execution of Open hub DTPs or APD execution or flat file load via process chain, then this can be added in to the process chain flow.

OS command process type in Process chain can be used for this.

Inside the process variant enter the OS command Name & details which was already created.

So when the process chain executes this step, it will trigger the OS command & which in turn will trigger the UNIX script “script.sh” and the file handling operations will be carried out.

The below listed partner software is licensed for the certification category Business Information Warehouse.

It is updated quarterly. Last update: Feb 2014. Next Update: May 2014.

For a complete and up to date picture please visit our  Partner Information Center http://www.sap.com/partners/directories/SearchSolution.epx and search in the according certification categories.

Integration Scenario BW-OBI - OLAP BAPI

Integration Scenario BW-ODB- Reporting for OLAP

Integration Scenario BW-OHS Open Hub Service

Integration Scenario BW-SCH Job Scheduling

Integration Scenario BW-STA Data Staging

Integration Scenario BW-UDC-JDBC Universal Data Connect JDBC

Integration Scenario BW-XMLA XML for Analysis

Integration Scenario NW-BI-NLS  Nearline Storage

In addition to the Certified Partner Software nearline storage can be implemented on IBM DB2.

The Nearline Storage solution for SAP NetWeaver BW on IBM DB2 LUW  is utilizing various DB2
capabilities and is included in SAP DB2 OEM licence.
Further information can be found in note 1405664

High Performance Near-Line Storage leverages the High Performance Storage Saver functionality of the
IBM DB2 Analytics Accelerator and DB2 for z/OS.
Further information can be found in note 1815192.

Partner Integration:

Integration Scenario BO_DS Integration with BusinessObjects
-  SAP BusinessObjects Data Services:

SAP BWNews Notes

Check out the listed SAP BWNews notes to see which notes are delivered with the according Support Package.

What comes with the Support Packages?

Support Package 10

• For detailed information read the release notes for the Support Package 10.
• Learn here about the enhancements in DataStore Objects in SAP NetWeaver BW 7.30 on SAP HANA delivered with SP 10. 

Support Package 9

• Please see the according  release notes for Support Package 9 
• Support Package 9 is providing the SAP NetWeaver BW Near Line Storage solution (NLS) based on Sybase IQ.
• This solution helps to reduce TCO by reducing data volume in SAP NetWeaver BW, shortens backup time frames, provides high speed analysis for NLS residing historical information and is a SAP owned solution out of one hand.
• For the SAP recommendation of notes on top of SAP Netweaver SP09 when your system is running on HANA DB see note 1846493

Support Package 8

For detailed information read the release notes for the Support Package 8.
In summary the SP 8 is providing:

• SAP HANA specific features:
  • Performance boost for data loading, query  response time and In-memory planning
  • SAP HANA-optimized InfoCubes and Data Store Objects
  • Simplified and faster data modeling/remodeling
  • “Not active” data concept
  • SAP NetWeaver BW and SAP HANA Mixed Scenarios (BO Explorer, BW Virtual Master Data, etc.)
  • Support of Semantic Partitioned Objects and enhanced partitioning for write optimized DSOs
  • Simplified system landscape
• Platform independent highlights
  • Graphical data flow modeling and enhanced support of 3.x-> 7.x data flow migration
  • Semantic Partitioned Objects (SPO)
  • Rapid prototyping of Ad Hoc scenarios via BW Workspaces
  • File download of BW meta data
  • DSO planning
  • Tighter integration with SAP Data Services

For details read the presentation Support Package 8 for SAP NetWeaver BW on SAP HANA-Overview

For the SAP recommendation of notes on top of SAP Netweaver SP08 when your system is running on HANA DB see note 1769670 - Important Notes for SAP BW powered by HANA on SP8.

The presentation SAP NetWeaver 7.30 SPS8 - Planning on DSO shows the new planning on DataStore objects comming with SPS 8 for SAPNetWeaver 7.3

Support Package 7

Investigate the release notes for Support Package 7 and find there the desriptions of the deliverered fixes and enhancements:

• Find out about the enhancements for SAP HANA optimization and the Data Warehouse Management. Further more you can read about the enhancements of the Analytic Engine in the OLAP Cache Monitor and for creation of CompositeProviders. For the BW Workspaces some handy improvements have been developed as well.

Check out all release notes for detailed information on SAP NW 7.3 SPS. (Logon to SAP Help Library is required)

Generell Information

• SAP always recommends to apply the latest Support Package
• For all SAP NetWeaver BW 7.3 powered by SAP HANA Ramp up customers it is strongly recommended to implement SP06. For detailed information please have a look at note 1657994. SAP also recommends to apply the latest available SAP HANA revision.
• The release dates for the Support Package Stacks can be found in the Support Package Stack Schedule (SMP login required).
• Please see the SAP NetWeaver 7.3 Support Package Stack page (SMP login required). This page is the central point of information for planning the implementation of Support Package Stacks (SP Stacks) for SAP NetWeaver 7.0.
• For regular updates please subscribe to the notes above as follows: You need to display the note on the service marketplace page. Use the direct links above or use SAP notes search and enter the note number directly. To subscribe to this special note activate the "subscribe" button (left hand above the title line of the note page). Also make sure that your E-Mail notification is activated (for activation see note 487366).
• Importing Support Packages: Please note that after implementing a Support Package, you are usually required to perform additional maintenance in transaction SNOTE. SAP Notes that are already installed may become inconsistent. This can lead to function errors or syntax errors. Go to transaction SNOTE and reimplement the SAP Notes that are no longer consistent. Your BW system is only operable and consistent after you have reimplemented these SAP Notes.

Establish a Rock Solid Enterprise Data Warehouse for a Single Version of the Truth

Capture, store, and consolidate your vital information with our enterprise data warehouse platform, SAP NetWeaver Business Warehouse (SAP NetWeaver BW). Tightly integrate your warehousing capabilities for a single version of the truth, decision-ready business intelligence, and accelerated operations. Supercharge your data warehouse environment with SAP NetWeaver BW powered by SAP HANA. Leverage reliable data acquisition, business modeling, and analytic capabilities. Extend your applications to reach more business users with minimal IT effort. Reduce total cost of ownership by automating design and development processes

Listen to Dr. Vishal Sikka, Member of the SAP Executive Board! In this interview from SAP Teched in Bangalore, he is talking about SAP NetWeaver BW on SAP HANA. Watch this video from SAPTechEd India showfloor. January 2014

(Click to start video)

See also  the Recently Featured Content for SAP NetWeaver BW..

Business Scenario:

An organization is operating its business in many continents/regions. When it comes to data analysis and decision making based on the BW data, the organization might face various problems because of the larger geographical area and different standard time zones. There might be following problems:

1. The data would be very huge. It will take significantly more time to get even a small data records.
2. Data loading is usually done in non-business hours. Because of the different time zones, some down time would be required. Reason is that when data load is done as per the non-business hours of 1 region, it could be business hours in other regions.
3. If an error occurs in the data of a particular region, it will have impact on the global business. Request will be red and concerned persons from other regions also would not be able to do the analysis.

Solution:

To overcome such hurdles, SAP has provided an InfoProvider, Semantically Partitioned Object. It is an Infoprovider that contains many InfoCubes or DataStore Objects with same structure. At the time of defining the InfoProvider, we decide to make it as Semantically Partitioned Object.

Note: This feature is available for BI 7.3 or higher version.

Creation of Semantically Partition Object:

1. Right Click InfoArea - > Select Create InfoCube

2. Following screen is displayed. Enter the name of the infoCube. Tick the check box ‘Semantically Partitioned’ and click Create button.

3. Enter the characteristics InfoObjects for this InfoProvider.

4. Enter the KeyFigures.

5. Click Maintain Partition as shown below:

6. We get the following screen:

7. Select the characteristics based on which partition has to be created.

Here we are creating partition based on geography.

8.  Click Partition to create required number of partitions. Enter the geography name as required.

9. Here we have created 4 partitions as shown:

10. Now activate the InfoProvider as shown below:

11. InfoProvider gets activated. Now create the transformation as shown below:

12. Enter the details for source.

13. Transformation is created. Activate the transformation.Now create the DTP as shown below:

14. Click Folder to create a new template folder as shown below:

15. Enter the name of Template folder:

16. Right click the created template (ZGEO_SL)  à  Click Create New DTP Template:

17. Enter DTP Template name.

18. DTP setting screen is displayed:

19. Click Save. Following screen is displayed.

       Select DTP Template and the DataSource connected to first partition. Click Assign.

20. Following screen is displayed. Select the ‘Not Yet Generated’ DTP and click Generate.

21. Follow steps 19 and 20 to create the DTP for all the partitions. All the DTPs are created as shown below:

22. Click Create Process Chains to create the process chains  for all the partitions:

23. Select  first DTP and click Add as shown below:

24.  Follow the same procedure to add all the remaining DTPs in process chain.

25. Once all the DTPs are added , click Generate as shown below:

26.  After successful generation of process chain, we see the following screen:

27.  Click Process Chain Maintenance to display the generated process chain:

28.  We get the following process chain created:

Now run this process chain and check the data in each InfoCube:

Data in partition 1:

Data in partition 2:

Data in partition  3:

Data in partition 4:

Check the number of records in PSA.

We find that there are 10 records in PSA but depending on the geographical partition, only the relevant data is being loaded in each InfoCube.

Benefits:

1.       Report execution time will be tremendously decreased

2.       If error occurs in one partition, other partitions will be not affected and those will be available for reporting.

3.       No downtime is required for data load; data in each partitions can be loaded as required.