New Exciting Features in Bw 7.3

SAP COMMUNITY NETWORK scn.sap.com

© 2012 SAP AG 1

SAP BW 7.3 -- Promising Features

Applies to:

SAP BW 7.3

Summary

While working with a SAP BW 7.3 project, I came across a lot of exciting and promising features that have come up with the new release. This is my humble attempt to include those features in a single document.

Author: Prabhith Prabhakaran

Company: Capgemini Consulting Pvt. Ltd., India

Created on: 14 July 2012

Author Bio

Prabhith is a Senior SAP BW-BOBJ Consultant with more than five plus years of experience and is currently working with Capgemini Consulting, India. His area of expertise includes BW/BI, BODS, BOBJ and HANA.



© 2012 SAP AG 2

Table of Contents

Evolution and promising features of SAP BW 7.3 .............................................................................................. 5

Evolution ............................................................................................................................................................. 5

Beta shipment in July, 2010 ................................................................................................................................ 5

Released in May, 2011 ....................................................................................................................................... 5

Promising features .............................................................................................................................................. 5

New Master Data Deletion .................................................................................................................................. 5

New options in RSA1 screen .............................................................................................................................. 6

Data Flows: ..................................................................................................................................................... 6

Planning Sequences: ...................................................................................................................................... 7

Process Chains: .............................................................................................................................................. 7

Graphical Data flow modeling option in RSA1 screen ........................................................................................ 7

Data Flow generation wizard .............................................................................................................................. 8

Migration of 3.X data flow to 7.X data flow ......................................................................................................... 8

New options in Info Area Context Menu ........................................................................................................... 11

New options in Create / Edit DSO screen ........................................................................................................ 11

New options in Create Infocube screen ............................................................................................................ 12

New options in Generic search screen (like process chain & open hubs) ....................................................... 13

New features in the Context menu of Info cubes.............................................................................................. 13

New options in Infoprovider and transformation ............................................................................................... 14

New rule type "Read from Data store” for an optimised data Lookup‟s to DSO............................................... 15

BO Data Services (BODS) as new source system -- Increased Flexibility with Non-SAP Systems15

New options in the Administration tab in RSA1 ................................................................................................ 16

New options in the DTP Extraction tab ............................................................................................................. 16

Delta Init without Data: .................................................................................................................................. 16

Parallel Extraction: ........................................................................................................................................ 17

New options in the DTP Execute tab ................................................................................................................ 17

Example Project schedule for the Migration Combined technical Upgrade & Authorization Migration ........... 18

Remarks: ....................................................................................................................................................... 18

Upgrade decisions to BW 7.3 (Low, Standard and High resources) ................................................................ 18

Upgrade Resources for BW 7.3 ........................................................................................................................ 19

Massive Parallel Processing (MPP) in BW 7.3 ................................................................................................. 19

Difference between BW 7.3 Running on HANA and BW running on xDB ....................................................... 21

SAP NetWeaver BW 7.30 Powered by SAP HANA – Database Migration ...................................................... 22

1) Primary Concepts in the conversion process to SAP HANA: ................................................................... 22

2) SAP HANA release required to run SAP NetWeaver BW on HANA: ....................................................... 22

3) Requirements for SAP NetWeaver BW to Run on HANA: ....................................................................... 22

SAP HANA Optimized DSO‟s ........................................................................................................................... 23

Hybrid Infoproviders .......................................................................................................................................... 24



© 2012 SAP AG 3

Features: ....................................................................................................................................................... 24

Create /Edit Hybrid Infoproviders ..................................................................................................................... 24

Semantic Partitioned Objects (SPO) ................................................................................................................ 25

Features: ....................................................................................................................................................... 25

Semantic Partitioned Objects (SPO) with example .......................................................................................... 26

Semantic Partitioned Objects (SPO)(steps for creation) .................................................................................. 28

Benefits: ........................................................................................................................................................ 28

Transient Providers ........................................................................................................................................... 28

Advantages: .................................................................................................................................................. 29

New authorization concept must be in place .................................................................................................... 29

Mass maintenance of Authorization objects (T-code RSECSY) .................................................................. 30

More options while creating Multi Providers ..................................................................................................... 32

Data Extraction from Multi Provider .................................................................................................................. 32

Version Management in BW 7.3 ....................................................................................................................... 32

We need to Follow the below steps for doing version Management in 7.3: ................................................. 32

NEW MDX test environment ............................................................................................................................. 34

Use of Navigational attributes as source fields in transformations ................................................................... 35

Master data new features ................................................................................................................................. 36

a) Mass look ups during master data loads: ................................................................................................. 36

b) Insert only flags for Master data loads: ..................................................................................................... 36

SID Handling ..................................................................................................................................................... 37

Performance improvements for DSO ............................................................................................................... 37

a) DB partitioning for DSO ............................................................................................................................ 37

b) Dynamic flag “Unique data records” (Activation of request) ..................................................................... 38

c) Mass lookups in activation of requests in DSO ........................................................................................ 39

d) Faster request activation in DSO on DBs with massive parallel processing architecture. ....................... 39

SPO included as a source in transformation to open hubs .............................................................................. 39

Exporting hierarchy using OHD into Flatfile ..................................................................................................... 40

Database Partitioning ....................................................................................................................................... 40

BW Workspaces & Composite Providers ......................................................................................................... 41

SAP BW 7.3 Near-Line Storage Solution ......................................................................................................... 43

1) Definition of a near-line storage variable for the query selection screen:................................................ 43

2) Properties of BEx Query Designer: .......................................................................................................... 44

3) Properties of the MultiProvider: ............................................................................................................... 44

4) Properties of the PartProvider: ................................................................................................................ 44

The new BW 7.3 hierarchy framework ............................................................................................................. 45

a) With SAP NetWeaver BW 7.30 the hierarchy framework has been improved, you could now use the 7.x data flow with all its following advantages. ................................................................................................... 45

b) New rule type "hierarchy split" .................................................................................................................. 45

c) Creating a new DataSource for hierarchies .............................................................................................. 45

d) Creating transformation and DTP ............................................................................................................. 46



© 2012 SAP AG 4

Let's have a look at the involved data transfer process (DTP). .................................................................... 47

Archiving of non-compressed data for InfoCubes ............................................................................................ 48

Automatic rebuild of BWA index during deletion is possible ............................................................................ 49

Integrated planning front end ............................................................................................................................ 50

New Look and Feel of the RSPC and RSPCM screens ................................................................................... 50

New Options like BPC –Process types ............................................................................................................. 51

New Process types (for BPC) ........................................................................................................................... 52

New option in the General services screen ...................................................................................................... 52

Simple supervision of Process chains .............................................................................................................. 52

More Options: ................................................................................................................................................ 53

Switch Infopackages in PC to Delta ................................................................................................................. 54

Automatically repeat red requests in process chains ....................................................................................... 55

Additional Features ........................................................................................................................................... 56

List of new T-codes in BW 7.3 .......................................................................................................................... 58

General Guidelines and Notes.......................................................................................................................... 59

Useful Notes ..................................................................................................................................................... 59

Related Content ................................................................................................................................................ 61

Copyright........................................................................................................................................................... 62



© 2012 SAP AG 5

Evolution and promising features of SAP BW 7.3

Evolution

Beta shipment in July, 2010

Released in May, 2011

Promising features

New Master Data Deletion

Deleting Master Data in BW has always been a performance intensive operation. The reason being that before any Master Data can be physically deleted, the entire system (Transaction Data, Master Data, and Hierarchies etc) are scanned for usages. Therefore, if a lot of Master Data is to be deleted, it takes some time to establish the data that is delete-able (i.e., has no usages) and data that is not (has usages). In addition, with the classical Master Data Deletion involving large data volumes, users sometimes ran into memory overflow dumps.

To address these issues, the Master Data Deletion was completely re-engineered. The result is the New Master Data Deletion. In addition to being much faster than the classical version, the new Master Data deletion offers interesting new features like Search-modes for the usage check, Simulation-mode etc. The screen shot below shows the user interface for the new Master Data Deletion when accessed via the context menu of Info Objects in the Data Warehousing Workbench.



© 2012 SAP AG 6

Although the new Master Data Deletion has been available for some time now (since BW 7.00 SP 23), it was never the default version in the system. This implied that the BW System Administrators needed to switch it ON explicitly. With BW 7.30 however, the New Master Data Deletion is the default version and no further customizing is necessary to use it.

New options in RSA1 screen

Data Flows:

From the data flows tab/option we can copy the existing flow to a new data flow as per the requirement, this can be useful for doing the physical partition of a data flow.

For Ex:- There are different data flows for each year and the same flow is to be created as a new flow with reference to existing flow, there we can use this option.

Same data flow for process chain can be copied for creating new process chain which automatically generates for the given inputs.

If there is a 3.X data flow which should be migrated to 7.X, then it can be copied as a new project in the migration tool (available from 7.3) and use the 3.X data flow in it, and then it will migrate the same to 7.X objects.



© 2012 SAP AG 7

Planning Sequences:

Will contain all the planning objects used or created, same as RSPLAN. ABAP based planning modeler is used to customize the planning objects and related BW objects.

Process Chains:

When you use the RSPC t-code, it will directly take you to this screen (RSA1 Modeling Process chains).

In RSPCM, the monitoring of the data loads are more user friendly such that it will display the load details step by step, reason for failure of the load and steps to be taken when the load gets failed.

Graphical Data flow modeling option in RSA1 screen

A graphical way of building a data model has been introduced in BW 7.3. The Graphical Dataflow Modeler is a new function within the Administrator Workbench (transaction RSA1). Using a drag-and-drop interface, a developer can build a dataflow by selecting either existing objects, or by directly creating new objects from within the modeler. The entire dataflow can be modeled in this way, from the DataSource to the MultiProvider, and even as an OpenHub destination.



© 2012 SAP AG 8

Data Flow generation wizard

Have you ever thought: How many steps do we need to do, until we can load a flat file into BW? We need so many objects, foremost we need lots of Infoobjects before we can even start creating the infoprovider. Then we need DataSource, Transformations (where we need to draw many arrows), DTP and InfoPackage.

We just want to load a file! Why is there no help by the system?

Now there is - BW 7.30 brings the DataFlow Generation Wizard!

You start by going to BW DataWarehouse workbench (as always), then selecting the context menu entry ,”Generate Data Flow..." on either the File-Source system (if you just have a file and want to generate everything needed to load it) or on an already existing DataSource (if you have that part already done - this works also for non-file-source systems!) or on an infoprovider (if you have your data target already modeled and just want to push some data into it).

Click on Wizard tool icon in RSA1 to get the following screen:

Migration of 3.X data flow to 7.X data flow

In SAP BW 7.3, we have a new wizard to migrate entire data flow from 3.X to 7.X. Prior to BW 7.3 we have to migrate each object separately. In 7.3 we can migrate entire dataflow to 7.0, the wizard also modifies the process chain to 7.0 flow. (i.e, it adds the DTPs automatically to the process chain).

There is a new migration project concept where you can group all the dataflows into different projects and carry out the migration once for each project. If there are issues during migration you can revert to 3.X flow by executing recovery for that particular project.



© 2012 SAP AG 9

Below are step by step instructions with screenshots to convert 3.X dataflow to 7.X data flow in SAP BW 7.3

1) Right click on the data source you want to migrate and select "Migrate Data Flow“.

2) It will ask you for a migration project, we are going to create a new migration project so enter a name for the migration project and click on create button as shown below.

3) This will take to migration project screen; here select the objects that you want to migrate. You can select all the objects including process chains and then click on save. After that click on 'Migration/Recovery' button as shown below.



© 2012 SAP AG 10

4) In the next screen select all the checkbox and click on 'Migrate/Recover' button.

5) It will ask if want to run migration now, say yes.

6) It will show the migration status at the bottom of the screen. You can revert back to 3.X flow if there are any errors in the migration. To recover 3.X flow, click on 'Migration/Recover' button again. The next screen will show the objects that are already migrated and failed to migrate.

7) Select the objects that you want to recover and click on 'Migrate/Recover' button. It will ask if you want to migrate now, say yes.

8) It will show "Restore complete: No Error" message at the bottom of the screen after the recovery is complete.

9) If there are no errors in step 5, all the objects are successfully migrated to 7.X flow and it will display below 'Success" message at the bottom of the screen.

You can verify that all the objects are converted properly and also check the process chain to make sure that DTPs are added correctly.



© 2012 SAP AG 11

New options in Info Area Context Menu

New options in Create / Edit DSO screen



© 2012 SAP AG 12

New options in Create Infocube screen



© 2012 SAP AG 13

New options in Generic search screen (like process chain & open hubs)

New features in the Context menu of Info cubes



© 2012 SAP AG 14

New options in Infoprovider and transformation



© 2012 SAP AG 15

New rule type "Read from Data store” for an optimised data Lookup’s to DSO

In SAP BW 7.30, you can define a transformation rule to fill a field in the transformation target by reading the value from a DSO (similar to reading from master data).

This new method of reading from DSO in a transformation is intended to replace the routines written by users as transformation rules to read values from DSO‟s. Besides making it more convenient to read from DSO‟s, this replacement will result in performance gains in many cases (depending on the implementation of the replaced user routine). This is because data is read from the DSO once per data package instead of record by record.

BO Data Services (BODS) as new source system -- Increased Flexibility with Non-SAP Systems

The close integration of SAP BusinessObjects Data Services (BODS) with SAP NetWeaver BW 7.3 enables SAP NetWeaver BW to be significantly more open and flexible toward non-SAP systems, making it easier to bring in external data. The direct connection between SAP NetWeaver BW 7.3 and SAP BusinessObjects Data Integrator (technically realized using the new source system type “Data Services”) enables you to establish connections between SAP NetWeaver BW and non-SAP systems, and trigger the generation of metadata and data flows. With the integration of SAP BusinessObjects Data Integrator, which has predefined extractors for non-SAP systems, companies now have the full functionality of a complete extract, transform, and load (ETL) tool.

Now we can execute and control PC‟s for BODS to extract data via Openhubs.



© 2012 SAP AG 16

New options in the Administration tab in RSA1

New options in the DTP Extraction tab

Delta Init without Data:

This option specifies whether the first request of delta DTP should be transferred without any data. This is same as “Initialization without data transfer” in Delta Info Package.

If we select this option, the source data is only flagged as extracted and is not moved to the target (first request of delta DTP will get successful with one record).This option will sets the data mart status for the requests in source and we cannot extract this requests using delta DTP anymore.

We will have this option in Extraction tab of Data transfer Process and can be seen in the below screen as well.

Note: If we are running any DTP for testing purpose, then it is not recommended to use this option. Instead, on Execute tab page, set the processing type to “Mark Source Data as Retrieved”.



© 2012 SAP AG 17

Parallel Extraction:

System uses Parallel Extraction to execute the DTP when the following conditions are met.

The Source of the DTP supports Parallel Extraction (Ex: Data Source).

Error Handling is De-activated.

The list for creating semantic groups in DTPs and transformations is empty.

The Parallel Extraction field is selected.

This field allows us to control the processing type of the Data Transfer Process and switch between the “Parallel Extraction and Processing” and “Serial Extraction, Immediate Parallel Processing” processing types.

How it works: If the system is currently using the processing type “Parallel Extraction and Processing”, we can select this option and change the processing type to “Serial Extraction, Immediate Parallel Processing”.

If the system is currently using the processing type “Serial Extraction, Immediate Parallel Processing”, we can select the Parallel Extraction field and change the processing type to “Parallel Extraction and Processing” (provided that error handling is deactivated and the list of grouping fields is empty).

Note: This field will be selected automatically if source of the DTP support parallel extraction.

New options in the DTP Execute tab

Automatically repeat red requests in PC can be used in cases where DTP fails due to RFC connection or due to DB connection issues.



© 2012 SAP AG 18

Example Project schedule for the Migration Combined technical Upgrade & Authorization Migration

Remarks:

Overall project duration dependents on the system complexity.

Given example is based on a higher complexity.

To match with typical technical Upgrade Plan, start two month in advance.

Upgrade decisions to BW 7.3 (Low, Standard and High resources)

a) Low resource use (Long downtime, slow import, archiving off).

b) Standard resource use (minimal downtime, slow import, archiving off).

c) High resource use (minimal downtime, fast import, archiving off).

d) High resource use (Minimal downtime, fast import, achieving on).

e) Manual selection of parameters.

A major decision is : Are you going to minimize the system down time or using a low resource upgrade. The trade off is between using more system resources or downtime.

In standard upgrade, we create a shadow system, while the BW system is still operating. We turn off any achieving to make sure that we do not miss any data and do our system backup right before the downtime starts. Therefore, we can do much of the upgrade before the downtime (shorten the outage).

In a very high system resource upgrade, we also use a shadow system but imports are much faster and we can keep achieving on(many create large logs) but downtime starts earlier.

Most companies should use standard method, unless their system is very small or have limited resources. For those, shadow system is created during the downtime.



© 2012 SAP AG 19

Upgrade Resources for BW 7.3

a) Basis resource

b) Technical reviewer/BW Developer

c) Upgrade support external

d) Regression testers

A dedicated team with a technical team lead (100%) , a basis resource(100%) and a technical reviewer/tester(100%).

A dedicated “go –to “ resource for technical issues is recommended. This should be a person that have solid knowledge about the upgrade and have done this before.

Regression testing is required on behalf of the user community. This should be coordinated with Power user or existing developers.

Massive Parallel Processing (MPP) in BW 7.3

SAP NetWeaver BW 7.3 can process the activation of new data in standard DSO using Massive Parallel Processing (MPP) on IBM DB2 for Linux, UNIX, and Windows and “Teradata Foundation for SAP NetWeaver BW” databases that use the Database Partitioning Feature (DPF). With the MPP-optimized implementation, the runtime of data activation can be considerably reduced.



© 2012 SAP AG 20

The traditional activation of requests in a standard DSO is done by splitting the data of the activation queue into packages that are activated independently of each other (and usually simultaneously). The system ensures that records with identical keys are placed into the same package and stay in their original sequence. It is very important that records with identical keys are activated in the correct sequence to guarantee correct results. Therefore a package is activated sequentially - record by record.

Usually there are not many records with identical keys in an activation run. SAP BW 7.30 offers you a new activation method that can be used on databases with massively parallel processing architecture.

This new activation method finds all the records in the activation queue that do not have unique keys and activates them in the traditional way. All the other records have unique keys in the activation queue and can be activated regardless of the sequence. These records are activated simultaneously using a few SQL statements. This means that the majority of records are no longer read from the database to the application server, processed and written back to the database. Instead they are processed directly in the database. This results in a considerable improvement of the activation runtime, in databases with a massively-parallel-processing architecture.

This new activation method is used automatically by the system (i.e. no user action is needed), provided that certain conditions are met:

this new activation method is supported for the database used (currently only “IBM DB2 for Linux, UNIX, and Windows” and “Teradata Foundation for SAP NetWeaver BW”).

SID generation during activation is not requested.

the option “unique data records” is not set.

the aggregation behaviors of all (load) requests that are activated in one go are identical.

the option “do not condense requests” is not set.

The performance gains depend on the data as well as on the hardware. In scenarios with very suitable conditions, performance can improve 2 to 3 times.



© 2012 SAP AG 21

Difference between BW 7.3 Running on HANA and BW running on xDB

SAP NetWeaver BW 7.x on xDB

Standard DSO

Data Base server and SAP NetWeaver BWA

Standard InfoCubes

BW Integrated Planning

HANA Data Marts running side-by-side BW

SAP NetWeaver BW 7.3 on HANA

SAP HANA-optimized DSO

SAP HANA In-Memory platform

SAP HANA-optimized InfoCubes

In-Memory planning engine

Consumption of HANA artifacts created via HANA studio



© 2012 SAP AG 22

SAP NetWeaver BW 7.30 Powered by SAP HANA – Database Migration

The high level overview in the process for converting a SAP NetWeaver BW System to an SAP NetWeaver BW System Powered by SAP HANA is explained with the following main elements:

1) Primary concepts in the conversion process to SAP HANA.

2) SAP HANA release required to run SAP NetWeaver BW on HANA.

3) Requirements for SAP NetWeaver BW to Run on HANA.

1) Primary Concepts in the conversion process to SAP HANA:

When evaluating a conversion of an SAP NetWeaver BW system to SAP HANA, there are some defined concepts that describe how this is accomplished. The conversion process is called an Operating System/Database Migration (OS/DB Migration). This process uses standard SAP tools that have been time tested to be reliable. In basic terms, this process allows an SAP system to be migrated from either one Operating System or Database System to another respective system. The process includes preparing a new instance on the target platform, and export of the source system, and then an import into the target system. There are several steps that have to be completed both in preparation and completion of the migration.

2) SAP HANA release required to run SAP NetWeaver BW on HANA:

In order to run SAP NetWeaver BW on SAP HANA, the SAP HANA system must be on SAP HANA release 1.0 SPS3 or greater. The functionality to support SAP NetWeaver BW is not available in SAP HANA until this release. Currently there are certain restrictions in production as to what concurrent systems can run on the same SAP HANA instance. Currently only one (1) application (e.g. SAP NetWeaver BW, SAP Smart Meter Analytics, etc.) and SAP HANA Data marts are supported in the productive system. The primary reason surrounds lifecycle management topics related to resource allocation/commitment and possible disruptive software patch applications.

3) Requirements for SAP NetWeaver BW to Run on HANA:

There are several system requirements in order to conduct an SAP BW system migration to SAP HANA. The following items must be in place for system migration:

SAP NetWeaver BW must be upgraded to SP05 or greater (SP06 is available to Ramp-Up Customers upon request).

SAP NetWeaver BW system must be a Unicode System. The Unicode conversion can be completed as part of the migration to SAP HANA as long as the project work has been completed.

SAP NetWeaver BW 7.30 no longer supports Role Based Authorization concepts. In order to Run SAP NetWeaver BW Release 7.30, all authorizations must be upgraded the Analytical Authorization concept that was delivered as part of SAP NetWeaver 7.0.

Customers need to evaluate their source system level and the add-on applications that have been installed as part of BW 7.0. Not all Add-Ons are support on SAP NetWeaver BW 7.30. Even the Add-ons that are support on BW 7.30 are not necessarily supported and available yet on SAP NetWeaver BW Powered by SAP HANA.

Ensure that hardware procured for the SAP HANA system is certified and from a certified partner and sized accordingly for your environment.

Review and understand all additional elements are required for pre and post migration.



© 2012 SAP AG 23

SAP HANA Optimized DSO’s

Delta calculation completely integrated in HANA

Using in-memory optimized data structures for faster access

No roundtrips to application server needed

Speeding up data staging to DSOs by factor 5-10

Avoids storage of redundant data

After the upgrade to BW on HANA all DSOs remain unchanged

Tool support for converting standard DSOs into SAP HANA-optimized DSOs

No changes of Data flows required



© 2012 SAP AG 24

Hybrid Infoproviders

It helps in displaying the most current data in the real time reporting scenarios. It normally consists of a DSO and infocubes with automatically generated dataflow between these objects. During runtime, It combines the mass historic data in the infocubes with the latest data in the DSO. This means that the data in the new request that is loaded into DSO but not yet loaded into cube is available for reporting.

Also, If datasource can provide delta info in direct access mode, a virtual provider can also be used instead of DSO. (Virtual in the sense that they don‟t store data).

Features:

Hold exactly 2 BW infoproviders.

Used when reporting requirements are real time.

DSO or Virtual provider once included in HP cannot be reused.

DSO in Hybrid provider doesn‟t support non cumulative Key Figures.

Infocubes part of Hybrid provider supports Key figures with SUM aggregation type only.

Transformation between DSO and Cube cannot be changed.

New transformation and DTP‟s cannot be created to the cube.

Changes in metadata of Hybrid provider results in deletion and recreation of transformations and DTP‟s.

Create /Edit Hybrid Infoproviders



© 2012 SAP AG 25

Semantic Partitioned Objects (SPO)

Features:

Single point of entry for creation and easy maintenance of semantic partitioned data model.

Wizard based partitioning of cubes and DSO along with criteria such as calendar year or region to

manage high volume data at different time zones.

Easy setup of multiple time based partitions with a minimum of manual effort.

You can spread similar data across several cubes or DSO, split according to region or year.

Can be embedded into MP.

Integration of data achieving/NLS to achieve SPO.

Good query performance by leveraging BWA as well as partition pruning when accessing

partitioned cubes.

If you create a data archieving process for SPO, the data archieving process(DAP) will apply to all

part providers. You can only create a data archieving process for semantically partitioned standard

Info Cubes and standard DSO.

The Semantic Partitioned Object (SPO) comprises multiple InfoCubes or DataStoreObjects that are

logically partitioned.

It is capable to handle mass data (and data flows) more efficiently.



© 2012 SAP AG 26

Semantic Partitioned Objects (SPO) with example

Here is an example of a typical modeling scenario. Documents need to be saved in a DSO. These documents can come from anywhere in the world and are extracted on a country-specific basis. Here each request contains exactly one country/region.

If an error occurs (due to invalid master data) while the system is trying to activate one of the requests, the other requests cannot be activated either and are therefore initially not available for reporting. This issue becomes even more critical if the requests concern country-specific, independent data.

Semantic partitioning provides a work around here. Instead of consolidating all the regions (Americas, Europe, Asia) into one DataStore object, the system uses several structurally identical DataStore objects or “partitions”. The data is distributed between the partitions, based on a semantic criterion (in this example, "region").



© 2012 SAP AG 27

Any errors that occur while requests are being activated now only affect the regions that caused the errors. All the other regions are still available for reporting. In addition, the reduced data volume in the individual partitions results in improved loading and administration performance.

However, the use of semantic partitioning also has some clear disadvantages. The effort required to generate the metadata objects (Info Providers, transformations, data transfer processes) increases with every partition created. In addition, any changes to the data model must be carried out for every partition and for all dependent objects. This makes the change management more complex.



© 2012 SAP AG 28

Semantic Partitioned Objects (SPO)(steps for creation)

Benefits:

Reduced development and maintenance efforts

Accelerated EDW implementation

Better performance with mass data

Better error handling

Working with different time zones

Improves Query Performance collaborate

Wizard support maintenance

Transient Providers

InfoProvider that allows analysis and reporting with BI tools (including BW OLAP functionalities) on top of an application (e.g. Business Suite system). It is not modeled in the Data Warehousing Workbench of BW and the data is not replicated.

Reporting is performed directly on the Business Suite tables using the BEx tools (or another reporting tool –MDX and BICS capable).

The source of the data can be either:



© 2012 SAP AG 29

- a classic InfoSet (based on DDIC tables or logical databases) (main focus of this presentation).

- a DataSource (via ODP framework) in the Business Suite system OR

- an Analytical Index build with the Analysis Process Designer (APD) OR

- Fast Search Index(FSI)-Views (only for SAP Business ByDesign).

A Transient Provider does not have any persistent BW meta data (no InfoObjects, etc. visible in Data Warehouse Workbench).

A Transient Provider is derived from the Analytical Index.

Advantages:

Executed in the Business Suite system, no separate SAP BW system needed.

Operational reporting tailored for the applications.

Real-time data access (zero latency).

No duplication of data / objects necessary. For scenarios like merging of data or large scale

reporting applications, replication and transformation of the data to an EDW is still feasible.

No BW metadata model.

Complete set of Analytical Functions (Restricted / Calculated key figures, Exceptions, etc.).

Pre-delivered content by SAP (which might be embedded in the operative transaction).

New authorization concept must be in place

It is mandatory to setup/migrate to the new concept prior to the upgrade.

The former authorization concept is no longer supported with BW 7.3x.

You cannot switch back to the former concept.



© 2012 SAP AG 30

New Transaction RSECADMIN, see SAP Notes 942799 and 944929.

Mass maintenance of Authorization objects (T-code RSECSY)

Can search for analysis authorization in various ways.



© 2012 SAP AG 31

In Release 7.30, a new feature for analysis authorization has been introduced. Mass maintenance will improve the daily work of every authorization administrator. Transaction RSECSY is just one of a number of clever innovations.

Analysis authorizations are special authorizations in BW. With these authorizations it is possible to develop a very complex and individual concept to grant and deny access to the data in your InfoProviders. It is possible to save the structure of a hierarchy of your products and to save the name or personnel number of your employees. Transaction RSECADMIN is the entry point for all main use cases. Mass Maintenance will also be available there. In Mass Maintenance, we can search for all analysis authorizations in various ways, for example by a simple name pattern or by a complex search via special entries in authorizations. Another use case would be to clean up the authorization, adjusting all authorizations that contain Info Objects that are not authorizations relevant. The complex search delivers this kind of search feature too.



© 2012 SAP AG 32

More options while creating Multi Providers

Data Extraction from Multi Provider

We can extract data from Multi Provider which was not possible in earlier version.

Version Management in BW 7.3

Until BI 7.0, we could find only last changed information for the changes.

We need to Follow the below steps for doing version Management in 7.3:

SPRO

IMG

Net weaver

BW



© 2012 SAP AG 33

General settings

Create historical TLOGO versions automatically.

Click on New Entries and maintain Object type (CUBE/DSO/Info Object etc...) from TLOGO object like below screen.

Enter the object type as IOBJ for Info Object (ex.).Check the below screen.



© 2012 SAP AG 34

Then goto RSA1 and select object maintenance screen then click on version management from Goto menu.

NEW MDX test environment

SAP BW offers with the query language MDX an open, generic interface for clients.

Both query definition and its execution plan can become quite complex.

New tool (transaction: MDXTEST) with powerful debugging and editing functions.

Accelerate performance tuning and testing of MDX statements generated by SAP Business Objects BI clients.

Create MDX Statements independently with full access to the metadata objects of the underlying InfoCube.

Drag-and-Drop of MDX function snippets in editor.



© 2012 SAP AG 35

Use of Navigational attributes as source fields in transformations

Quite often there are scenarios in SAP BW where data being loaded from a source to a target needs to be augmented with information that is looked up from Masterdata of Infoobjects. For instance - loading sales data from a source that contains data on Material level to a Data Target where queries require the sales data to be aggregated by Material Group. In such cases, the Master Data Lookup rule-type in Transformations is used to determine the Material Group for any given Material (given that Material Group is an attribute of Material).

Although the performance of the Masterdata Lookup rule-type has been optimized in earlier versions of BW (starting BI 7.0), there is an alternative to this rule-type in BW 7.30. Now, navigational attributes of Infoobjects are available as source fields in Transformations. The benefits of this feature are the following:

The fact that the data from the navigational attributes is available as part of the source structure allows the data to be used in custom logic in Transformations (example : Start Routines).



© 2012 SAP AG 36

Secondly, the data from the navigational attributes is read by performing database joins with the corresponding needed Masterdata tables during extraction. This helps in improving the performance of scenarios where a lot of look-ups are and/or a lot of data is to be looked-up.

To use this feature in Transformations, the navigational attributes need to be switched ON in the source InfoProvider in the InfoProvider maintenance screen as below -

Once this is done, the selected navigational attributes are available as part of the source structure of Transformations as shown below –

Master data new features

a) Mass look ups during master data loads:

Data loads into a MD bearing characteristic require database lookups to find out if records exits in the DB with the same key as the ones being loaded. Earlier this was done record wise. So huge data means huge confusion. Now BW 7.3 performs a mass lookup on the database so that all the records in the datapackage are looked up in one attempt.

b) Insert only flags for Master data loads:

With NW 7.30 SP03, this flag will be renamed to – “New Records Only”. The renaming has been done to align with a similar feature supported by activation of DSO data.



© 2012 SAP AG 37

The Master Data Load performs a look-up on the database for every data-package to ascertain which key values already exist on the database. Based on this information, the Master Data load executes Updates‟ (for records with the same key already existing in the table) or Inserts‟ (for records that don‟t exist) on the database.

With the „Insert-Only‟ feature for Master Data loads using DTPs, users have the opportunity to completely skip the look-up step, if it is already known that the data is being loaded for the first time. Obviously, this feature is most relevant when performing initial Master Data loads. Nevertheless, this flag can also be useful for some delta loads where it is known that the data being loaded is completely new.

The „Insert-Only‟ setting for DTPs loading Master Data can be found in the DTP Maintenance screen under the „UPDATE‟ tab as shown below.

SID Handling

This feature relates to the handling of SIDs in the SAP BW system and while it is certainly relevant for Master Data loads, it is not restricted to it. The performance improvements in SID handling are relevant for all areas of SAP BW where SIDs are determined, for example – Activation of DSO Requests, InfoCube Loads, Hierarchy Loads and in some cases, even Query processing.

In BW 7.30, SIDs are determined en-masse‟ meaning that database SELECTs and INSERTs that were done record-wise previously have been changed to the mass SELECTs (using the ABAP SELECT FOR ALL ENTRIES construct) and mass INSERTs. The system switches to this mass-data processing mode automatically when the number of SIDs to be determined is greater than a threshold value. The default value of this threshold is 500.

The threshold value is customizable of course and that can be done in the SAP IMG for customizing under the transaction SPRO by following the path: SAP Netweaver Business Warehouse Performance Settings Optimize SID-Determination for MPP-Databases.

Note: As the threshold value corresponds to the minimum number of SIDs to be determined in one step, setting the threshold to a very high value, (For example: 100000) cause the system to switch back to the classical behaviour.

Performance improvements for DSO

a) DB partitioning for DSO



© 2012 SAP AG 38

If standard DSO has atleast one Key field referring to Info objects 0calmonth or 0fiscper, then the active tables of this DSO can be portioned by one of these key fields. A popup appears where you can select a key field that refers to the above said infoobjects.

You cannot select anything if there is no field referring to one of these info objects.

Can do this only when DSO is empty.

b) Dynamic flag “Unique data records” (Activation of request)



© 2012 SAP AG 39

c) Mass lookups in activation of requests in DSO

The lookup is not performed record by record, but all packages in one go.

d) Faster request activation in DSO on DBs with massive parallel processing architecture.

The records are activated simultaneously using SQL commands.

SPO included as a source in transformation to open hubs



© 2012 SAP AG 40

Exporting hierarchy using OHD into Flatfile

Openhubs allows extraction of Hierarchies.

Database Partitioning

The E fact tables of InfoCubes can be partitioned, by month or fiscal period, on databases that support range partitioning. In SAP BW 7.30, this is now also possible for the active tables of standard DataStore Objects. More precisely, if a standard DataStore Object has at least one key field referring to InfoObject 0CALMONTH or InfoObject 0FISCPER, then the active table of this DataStore Object can be partitioned by one of these key fields.

To activate partitioning, go to the menu and choose “Extras → DB Performance → DB Partitioning (in edit mode of a standard DataStore Object).



© 2012 SAP AG 41

A popup appears where you can select a key field that refers to the InfoObject 0CALMONTH or InfoObject 0FISCPER (you cannot select anything if there is no field referring to one of these InfoObjects).

Any changes made here will become effective after activating the DataStore Object.

Note that you can only change the partitioning settings if the DataStore Object is empty. This means that you should decide whether you want a DataStore Object to be partitioned before you load any data into it.

BW Workspaces & Composite Providers

BW Workspaces addresses a specific gap often encountered in data warehousing implementation projects, the conflict between the central IT department and the business development requirements.

Tcode RSWSPW, RSWSP

The above screenshot shows the transaction RSWSP (single maintenance) in SAP NetWeaver Business Warehouse.

Business user can upload own data eg) from a file (CSV or Excel) a query result or data from a BW datasource. These locally uploaded models can be easily combined with centrally exposed models in a composite provider via union and join combinations.



© 2012 SAP AG 42

The above screen shot shows the BW Workspace Designer running in SAP NetWeaver Business Client.

Sample Business Scenario: The business department needs to act in an agile way in its day-to-day business. For example, a marketing department meets today and wants to initiate a marketing campaign in a few weeks time. In order to monitor the data for the campaign, the marketing department wants to set up an InfoCube to track customer reactions, for example. The business department approaches the IT department with this request and is told that a new InfoCube could be deployed in two months time at the earliest. This results in a conflict between the two departments.

EX: Let us assume that you are working as a global sales account manager for a company, selling computer hardware and corresponding accessories. In the central enterprise data warehouse, the SAP NetWeaver BW, sales data for 2010 and 2011 is provided in InfoCubes with a MultiProvider on top.

Additionally, the central SAP NetWeaver BW provides the company‟s central ABC Rating information of customers worldwide in an InfoProvider, but you have an own ABC Rating available in a file you would like to use to enrich the central sales data with your local information and report on the merged data.

The above screen shot shows the BW Workspace Scenario Content: Different Providers and Relationships.



© 2012 SAP AG 43

SAP BW 7.3 Near-Line Storage Solution

SAP NetWeaver BW offers a near-line storage (NLS) interface that enables customers to separate frequently accessed data from older, less frequently accessed data.

Configuration for NLS use is possible on four different levels:

1) In the query selection screen

2) In the properties of the BEx Query Designer

3) In the properties of the MultiProvider

4) In the properties of the PartProvider

1) Definition of a near-line storage variable for the query selection screen:



© 2012 SAP AG 44

2) Properties of BEx Query Designer:

3) Properties of the MultiProvider:

4) Properties of the PartProvider:



© 2012 SAP AG 45

The new BW 7.3 hierarchy framework

a) With SAP NetWeaver BW 7.30 the hierarchy framework has been improved, you could now use the 7.x data flow with all its following advantages.

You are able to use any BW object as source for a hierarchy, you are not limited to a DataSource for hierarchies. This leads to simpler scenarios if you want to transform your hierarchy according to your needs. You just have to connect your hierarchy through a transformation and a data transfer process.

Within this transformation you are able to use all features of a transformation, for example start, end or expert routines. You are not limited as you were in the 3.x data flow.

You can use any DataSource as a source for your hierarchy, you are not restricted to hierarchy DataSources any more. This makes hierarchy extraction of SAP source systems possible, too.

b) New rule type "hierarchy split"

In SAP NetWeaver BW 7.30 both structures are available, the old one and the new one. Please be aware that most of the DataSources of the Business Content have not been migrated to the new structure. That could lead to a problem because you have to map the old DataSource structure to the new structure within the hierarchy. To avoid the problem SAP has introduced a new rule type which automatically maps the old structure to the new one (see figure).

This new rule type is called "hierarchy split". To use the new rule type you have to map the field NODENAME to every InfoObject of your structure, in this case the controlling area and the cost center. The hierarchy split automatically transforms the value of NODENAME to the corresponding values of controlling area and cost center.

Please remember that this functionality only works if you haven't changed the length of the corresponding InfoObjects.

c) Creating a new DataSource for hierarchies

If you want to create a new DataSource for hierarchies just navigate to transaction RSA1 and open a DataSource tree of a source system, for example a flat file source system. Right-click on a display component and create a new DataSource for hierarchy



© 2012 SAP AG 46

After choosing the correct type of DataSource you can edit the properties of your DataSource. The main properties can be found in the tab "extraction" which is shown in the following figure.

In the top of the screen you can provide information on full/delta loading and the direct access, both you will know of other DataSources. The interesting parts are highlighted. If you select "hierarchy is flexible", the DataSource will be created in the new structure, if you leave it blank the DataSource will consist of the old structure. Second you are now able to create the hierarchy header directly from the DataSource. In older releases you had to maintain the hierarchy header in the InfoPackage.

d) Creating transformation and DTP

After activating your DataSource, you can create a transformation between your new DataSource and the hierarchy of an InfoObject. The following picture shows how this is displayed in the system.



© 2012 SAP AG 47

Within the transformation you have to map the corresponding segments to each other. The interesting one is the mapping of source segment "hierarchy structure" to the correspondent target segment.

You can see that there are a lot of 1:1 rules within the transformation except the mapping of field NODENAME to 0COSTCENTER and 0CO_AREA. Here, the new rule type "hierarchy split" has been set.

Maybe you have noticed that the key field 0OBJECTID has not been mapped. This field will be used to load more than one hierarchy to have a unique key. Please be aware that in this case each data package has to contain exactly one complete hierarchy.

Let's have a look at the involved data transfer process (DTP).

There are two major changes when loading data through a hierarchy DataSource:

If you select full extraction mode in the DTP there's a new flag called "only retrieve last request". This flag is helpful if you don't want to clear your PSA before loading the new hierarchy. Only the newest request in the PSA will be selected and loaded.

In the update tab of your DTP (see figure) you can decide how to update your hierarchy (full update, update subtree, insert subtree). Furthermore you can activate the hierarchy from within the DTP, no separate process step in a process chain is necessary to activate the hierarchy!

Now you are able to load a hierarchy from a hierarchy DataSource to an InfoObject.



© 2012 SAP AG 48

Archiving of non-compressed data for InfoCubes

The option to archive non-compressed data was requested by customers for whom data compression was a time consuming operation and did not really lead to significant compression rates (highly granular data).

Data compression was a precondition for archiving InfoCube data since release 700. Before data can be compressed, it must be:

Distributed to subsequent data marts

Rolled up to existing aggregates

As of SAP NetWeaver BW 730, it is no longer necessary to compress data before archiving. To ensure data consistency in different data layers, the two preconditions above must be met before data can be archived.

The flag ‟Allow Archiving of Non-Compressed Data‟ is a central setting in the data archiving process.

The flag can be changed in the DAP even if data has already been archived. If you change this flag (Allow Archiving of Non-Compressed Data) in the DAP definition, all archiving requests that are not completely finished (Status „70 Deletion Phase Confirmed and Request Completed‟) must be finished in the old „Compression Mode‟ or must be set to invalid before you can archive data in the new „Compression Mode‟.

Archiving of uncompressed data results in partially or completely archived requests. This is shown in the Requests tab in the column „Selectively Deleted Records/Archived Requests‟.

http://scn.sap.com/servlet/JiveServlet/showImage/38-56857-70690/ICONArchive.png



© 2012 SAP AG 49

Note that partially or completely archived requests cannot be deleted and subsequently reloaded with delta DTP requests. The consequences of deleting these requests are described in Note 1360751. This Note is referenced in the popup that appears when you delete a partially or completely archived request.

Automatic rebuild of BWA index during deletion is possible

In SAP NetWeaver BW 730, the BWA, online and near-line partitions stay consistent during the archiving process. After data has been copied to the archive, the corresponding BWA index is invalidated and can be rebuilt during the deletion phase of the archiving request.

If you use process chains for data archiving, we recommended that you use the process step „Initial Activation and Filling of BWA Indexes‟ to rebuild the BWA index. If you have set the „Rebuild BWA Index‟ flag in the Data Archiving Process Deletion step, the following question appears:



© 2012 SAP AG 50

Integrated planning front end

Integrated planning front end (ABAP based Planning Modeler w/o requiring a Java stack)

SAP has now migrated the IP frontend to a traditional transaction screen within the SAPGUI.

The screens are quicker and easier to use, and have no dependency on either a Portal or Java

stack.

New Look and Feel of the RSPC and RSPCM screens



© 2012 SAP AG 51

New Options like BPC –Process types



© 2012 SAP AG 52

New Process types (for BPC)

New option in the General services screen

Simple supervision of Process chains

At last you are able to search for process chains by name directly in the workbench. The display components are ordered hierarchical like any other folder in RSA1. But not only the display components, but also the chains itself have a hierarchical structure, displaying the metachain – subchain relationship. So you can directly navigate to the lowest subchain in your metachain hierarchy if you only remember the name of the top-level master.



© 2012 SAP AG 53

Also, we have option to refresh the status of all chains or only the status of the process chains currently running.

More Options:



© 2012 SAP AG 54

Switch Infopackages in PC to Delta

As of BW 7.0 we need to manually change all the delta init packages in the process chains to delta when we move the changes to QA or Production environments or we have to create separate delta init packages and manually run them to do initialization before we could schedule the process chains with delta info packages.This is going to change in SAP BW 7.3.

There is a new option "Switch InfoPack. in PC to Delta" under update tab of infopackage. If we check this option the infopackage will be automatically executed as delta package if already there is a successful initialization. Otherwise, it will be executed as a init package when there is no successful initialization. This will be useful and save us some time with new projects and enhancements.



© 2012 SAP AG 55

Automatically repeat red requests in process chains

This is another great feature in BW 7.3. Some times DTP load fails with one off error messages like RFC connection error, missing packets, database connection issues etc. Usually these are resolved by repeating the failed DTP load.

In BW 7.3 there is an option under execute tab which if you check will automatically repeat red requests in process chains. This saves us time and effort in monitoring data loads.



© 2012 SAP AG 56

Additional Features

1) Predefined best practice data flow templates for ready to run scenarios (eg: Template LSA

reference architecture).

2) BW 7.3 initial load runtime option “Insert only and the unique data records only” prevents all

lookup‟s during activation.

3) New DataSource Adapter Type „Web Service Pull‟:

A new type of web-service-based DataSource can be created which pulls data from a 3rd party

source system into PSA.

Available for transactional data and master data (except hierarchies).

Initially available for pilot customers and partners only (i.e. the function are there and can be

activated quickly).

4) Possibility to load master data using RDA.

5) Generic delta for further type of datsources such as a) DB connect b) UD connect c) Flat-files

d) Web services.

6) New monitors in BWA admin cockpit: DB usage monitor.

Display the usage of DB space (in MB by infoprovider).

Enhanced usability through Xcelcius integrations of monitors.

7) Accelerated loading and activation process.

SAP has rewritten underlying code for data loads for optimized performance. In many places in

BW 7.3, the technical coding have been optimized to improve the loading performance. Load of

times into DSO objects has been reduced by up to 40% when compared to BI7, plus the

loading Master Data has been accelerated.

8) Teradata and HP Neoview supported as additional databases for BW.

9) Query as an InfoProvider enabled for mass data handling.

10) SQL access via SAP Business Objects Data Federator.

11) BWA reporting is now available on DSO.

12) BW data can be extracted in XML format.

13) DTP can extract data from Multiproviders.

14) Complete copy of existing PC (including related process variants and dataflow objects).

15) Migration of BW3.X BW7.X can be repeated/reversed as often as required.

16) Table which hold all the monitor entries for DTP‟s tends to grow very big in long time. A new

feature is available to archieve this kind of data to speed up DTP monitor.

17) Hierarchies – Integration of hierarchies into process flow(DTP, Transformation).

18) Loading hierarchies from Flatfile to BW 7.3 using transformation, DTP and IP.

19) Hierarchy extraction by Openhubs.

20) After migration if Infosets are inactive, use program RSQ_ISET_MASS_OPEARATIONS.



© 2012 SAP AG 57

21) Analytical indexes(AI):

An Analytical Index (AI) is a transient dataset that is stored within the BWA. BEx or Business Objects can be used to report on them directly. They are defined and loaded from within the Analysis Process Designer (APD), and can contain the results of a JOIN between a CSV file and query. The fact that they do not exist in the database and the ease at which they can be defined makes them a very interesting concept for inclusion in BW. Up until now, creation of datasets to address specific requirements has always been a significant exercise and has required transports and loading. So AI‟s reduce the development effort needed to produce a fast-performing tool that addresses a specific current requirement.

22) Transformation:

Semantic grouping possible in Transformations (in addition to semantic grouping in DTPs).

Possibility to select the InfoObjects (fields) the user wants to use in a Start- / Endroutine.

Currency and unit conversion for DataStore object and InfoSource as target of a

transformation.

Navigation attributes of InfoCubes / DataStore objects can be used as source fields in the

transformation and as Filter/select options in the DTP.

Automated generation of a proposal by mapping fields of the DataSource to Infoobjects.

23) ABAP program for controlled suspension and re-starting of all process chains and RDA daemons during restart of the application server. (Name of program: RS_SYSTEM_SHUTDOWN).

24) The ABAP program RSDDSTAT_DATA_DELETE was enhanced to also be able to delete the content of table RSDDSTATWHM which is constantly growing over time (all entries up to a certain date).

25) Disable delta consistency check for write-optimized DataStore objects:

Protects delta requests that have been already propagated per delta mode from deletion.

Can be switched on/off – e.g. for write-optimized DataStore objects as initial staging layer.

26) BW 7.3 will run together with BW Accelerator 7.20 and will provide support for exception aggregation.

27) You can upgrade to BI7.3 from BW3.5 but for BI 7.3 it is mandatory to have analysis authorizations. So before upgrading to 7.3, you will have to switch to analysis authorization.

28) We can publish SAP HANA models in the BW system. Once published in the BW system, these SAP HANA models are saved as analytic indexes and can be linked to other BW InfoProviders in a Composite Provider.

This enables you to combine ad-hoc data with consolidated data from the BW system and also use the OLAP functions of the BW system for analysis.

29) Web Application Designer remains, but Bi Services connectors (BICS) is better solution for Xcelsius and analysis Tools.

30) SAP HANA is not part of BW 7.3. HANA needs additional License.



© 2012 SAP AG 58

List of new T-codes in BW 7.3

RSA19 To get data flow screen

RSA20 To get planning sequences screen

RSCUSTV31 RFC destination for BI model generation

RSCUSTV32 Hide old DWB functions

RSCUSTV33 FAE threshold value for SID service

RSCUSTV34 Asy. Threshold deletion from write optimised DSO‟s

RSAP_AUDIT_PREVIEW Preview of system measurement in BI

RSAUDIT_SYSTEM_ENV System and client settings

RSAUDIT_SYSTEM_ENV_X System and client settings

RSB_RELEASE Release clients for ETL tool

RSBCT_SREP_SLC Scalability level config.

RSBUCKET To fill bucket

RSCNV_MONITOR DB6 MDC reclustering

RSCOPY Dataflow copy

RSDD_LTIP Administration of Analytical indexes

RSDD_LTIP_PUBLISH Publish a Trex cube index

RSDD_MU Maxwell export manager

RSDDB BWA maintenance index

RSDDG Demo data generation

RSDDTPS Start explorer maintenance, BOBJ polestar

RSDEMO_DROPDOWN_LIST Report RSDEMO_DROPDOWN_LISTBO

RSDF Edit data flows

RSDFWIZ Data flow generation wizard

RSDHYBR Accessing edit hybrid provider screen

RSDHYBRD, RSDHYBRM Initial screen: edit hybrid data provider

RSDS_PROPOSE Find info objects for data sources

RSECAUTHO2 , RSECSY Mass maintenance analysis authorization

RSFI1 Virtual info provider for fast search

RSHOWINDEX Show index

RSINSP Inspection plan

RSLIMO BW lean moduler test UI

RSLPO_MASS_ACT Activation of BAdi SPO‟s

RSMIGRATE Migration tool/project

RSOBIXP Maintenance of conversion objects

RSOCOPY Copy from TLOGO objects

RSODSO_SQLTRACE SQL statements for MPP datastores

RSDS_ES_OBJMAINT Object maintenance for ES back end navigation



© 2012 SAP AG 59

RFOSCSFW5 Configure BI Business functions

RSOSCSW BI switch overview

RSPRECALCADMIN Precalculation server Administration

RSPSADEL_PATTERN Maintain source system pattern assignment

RSQSI QSI Maintenance

RSRD_RLP Administration broadcasting to RLP

RSRTE Analyzer test transaction

RSTC_XCLS Launch administration cockpit in Xcelcius

RSTCT_INST_BIAC Installation of BI AC Content

RSTCT_RRI Display object or process maintenance

RSTHRT_TEST_CCT Test CCT Basics

RSUSR_SYS_LIC Cross system license data info

RSWEWWDHSOSHOW Display work item deadline monitoring

RSWSP Workspace individual processing fully available in SP05

RSWSPW Workspace mass processing fully available only in SP05

General Guidelines and Notes

Netweaver BW 7.3 Online Help http://help.sap.com/saphelp_nw73/helpdata/en/ca/6fbd35746dbd2de10000009b38f889/frameset.htm

SAP NW 7.3 on Sap Developer Network

www.sdn.sap.com/irj/sdn/nw-73

SAP NW 7.3 Business Content

http://help.sap.com/saphelp_nw73/helpdata/en/ca/6fbd35746dbd2de10000009b38f889/frameset.htm

Useful Notes

Note 586648 - Invalid SID entries in /BI 0/SIOBJNM

Note 1022704 - Upgrade Phase EHP_INCLUSION und SPSTACK_REQUEST

Note 1088717 - Active services for Web Dynpro ABAP in transaction SICF

Note 1390477 - Additional info for upgrade to SAP NetWeaver 7.3 (using SUM)

Note 1403832 - Central Note: Upgrade Systems on SAP NetWeaver 7.3

Note 1539356 - Upgrade to NW 7.3 with SEM-BW, FINBASIS, SAP_BS_FND, WEBCUIF

Note 1405878 - SAP Solution Manager - Basic functions SP22 and higher

Note 1484437 - BI_CONT 7.35: Information about installation and upgrade

Note 1543092 - BI Administration Cockpit: Upgraded from 7.00 to 7.3x release

Note 1562522 - SAPINST aborts during central instance installation

Note 1603103 - SMSY: NetWeaver 7.3 upgrade



© 2012 SAP AG 60

Note 1636053 - Upgrade to SAP NetWeaver 7.3x: BW server: Useful note

Note 1627683 - SCWB/SNOTE/SPAU: Changed development package

Note 1528990 - SP Equivalence for update/upgrade to SAP NW 7.3x

Note 1636841 - Version management: Compatibility with SAP BASIS 7.x0

Note 1468349 - SAP Business Suite 7 for SAP NetWeaver 7.3 hub systems

Note 1081287 - Data extraction orders block the upgrade process

Note 1636053 - Upgrade to SAP NetWeaver 7.30: BW server: Useful note

Note 1636057 - Upgrade to SAP NetWeaver 7.30: BI Java: Useful note

Note 1390477 - Additional info about the upgrade to SAP NetWeaver 7.3

Note 1638319 - BEx Web 7.30: Web Session Timeout not working

Note 1636106 - Missing include/exclude button in selector dialog in 730

Note 1636053 - Upgrade to SAP NetWeaver 7.30: BW server: Useful note

Note 1629589 - INVALID_STATE:ATTRIBUTE_MISSING while loading query

Note 1629251 - BEx: Variant Catalogs are not correct assigned in NW 7.30

Note 1622746 - Standard images are exported to excel in 730

Note 1622596 - Items are not correctly exported to Excel in 730

Note 1619455 - Select All option missing in the selector dialog

Note 1618536 - Repeat column header does not work in Broadcast to PDF

Note 1617936 - Save query view missing template id in backend table

Note 1608398 - Default width of items with active tray has changed with 730

Note 1403832 - Central Note: Upgrade Systems on SAP NetWeaver 7.3

Note 1390477 - Additional info about the upgrade to SAP NetWeaver 7.3



© 2012 SAP AG 61

Related Content

http://scn.sap.com/docs/DOC-8683





© 2012 SAP AG 62

Copyright

© Copyright 2012 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, series, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Dorval‟s in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Oracle Corporation.

JavaScript is a registered trademark of Oracle Corporation, used under license for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.