In my Project, this issue was encountered while transporting 3.x Update Rule of Cube

There were several Routines, Formulas and Constants in the Update Rule.

When the TR was moved, it ended in Error code 8 and failed. When the logs were checked there was no proper message to find out the exact error.

I tried to capture the Update Rule in TR from transport connection and also from RSA1 and tried to transport again but yet it ended in error.

The syntax check was done for each of the routines and there was no errors reported for the Routines and the formulas yet the TR failed.

Finally, the issue was found. Please find below the easy method to find out the issue.

In the Production system, I double clicked on the Update Rule, clicked on Edit and then clicked on the Syntax button highlighted below and the details of the error was clearly shown which was very helpful in resolving the Error.

The error was in one of the Routines which was resolved and TR ended in Success.

Old or Pre BW 7.4 Database-Tables for Hierarchy Entries within Authorizations

RSECHIE                        Status of Authorization Hierarchies

RSECHIE_CL                  Authorization Hierarchies Changes Change Log

Database-Table after Upgrade to BW 7.4:

All newly created Hierarchy Authorizations will be saved within this new table.

RSECHIE_STRING         Status of Authorization Hierarchies

Old or Pre BW 7.4 Database-Tables for Value Entries within Authorizations

RSECVAL                        Authorization Value Status

RSECVAL_CL                  Authorization Value Change (Change Log)

New Database-Table after Upgrade to BW 7.4:

All newly created Value Authorizations will be saved within this new table.

RSECVAL_STRING         Authorization Value Status

As seen from the screenshots there is a new Infoobject within both tables called: AUTH_HASH.

With BW 7.4 a hash value is created for every entry within an authorization. Depending if its a hierarchy node authorization or a value authorization the hash value is saved to the respective table. For every entry combination there is one hash value. Not to mistake with the entire authorization. An authorization contains different hash values but there is one hash value for one compination.

For example:

This hash value can be used for comparing entries within authorizations and furthermore for cleaning purposes within the authorization-concept.

The Infoobject is also used for Database-Tables:

RSECVALVIEW                      Join of USERAUTH, RSECVAL and RSECBIAU: All ACT & A-Versions

and

RSECHIEVIEW

Scenario:  There is a requirement to create a  workbook where multiple query outputs (analysis grids) are displayed in a single excel sheet and one below the other.

Issue: There is no control on the number of rows of these queries as for certain variable selections there may be just one row displayed and for other selections there may be multiple rows, so aligning the analysis grid one below another too close might lead to one query output overlapping the other and aligning the grids with lots of blank rows might lead to huge gaps between the query results.

Two query results overlapping:

Two query results with too many blank lines in between them:

Solution: To get the excel behave dynamically according to the number of rows and overcome the rigidity VB approach could be adopted, but this demands a sound knowledge in VB. The workbook can also be rendered dynamic without VB coding by just using an excel formula and custom views. This paper intends to explain the same.

Step 1: Create a workbook with Analysis Grids in a single sheet one below another. Ensure to maintain a gap of 50 to 100 rows from one grid to another so that there is sufficient room for the analysis grid to stretch.

Step2:  To retain the actual blank rows which are necessary to maintain the spacing between two analysis grids or headers enter a formula in column "A" for these corresponding rows as =” ”.

Step 3: Key in a formula to identify the blank rows (based on the value in column A) on a different column, which will be hidden.

Step 4: Create a filter on the column with the formula. Filtering out the value “False” will provide all the rows which are non-blanks.

Step 5: Hide the column with the formula (ie., column Z in this example) and create Custom View from the View tab on the ribbon as highlighted.

Click on Add and name it as “Formatted”:

Step 6: Now un-hide the column with formula (column Z) and filter on “True” and hide it back again.

The output is formatted now with only blank rows:

Step 7: Hide the column with formula again and create a new custom view.

Step 8: Testing

Run the workbook to find the result display with the blank rows between query results post variable entry:

Click on “Custom Views” under tab – “View”. Double click on “Formatted” and the workbook with the blank rows trimmed should show up:  

Again click on “Custom Views” and choose “Unformatted” to return back to the initial view with blank rows.

Buttons could be inserted to assist the users with switching of the view and small macros can be recorded and assigned to these buttons, if done so the simple macro for each button appears as below:

Hierarchy Loads using Transformation from Version BW 7.3 onwards.

Here I am trying to load hierarchies from one object to another Info provider specific object in BW 7.4

I have covered below 2 scenarios in the below example :

Scenario 1 : If the Source Object has NO External Hierarchy object.

Scenario 2 : If the Source Object has an External Hierarchy object.

Scenario 1 : If the Source Object has NO External Hierarchy object.

Source Info object : Y_ACC

Target Info Object : Z_ACC

LOOP AT SOURCE_PACKAGE_3 ASSIGNING <SOURCE_FIELDS_3>.
if <SOURCE_FIELDS_3>-H_IOBJNM <> '0HIER_NODE'.
<SOURCE_FIELDS_3>-H_IOBJNM =’Z_ACC'.
endif.
ENDLOOP.

Note : SOURCE_FIELDS_3 represents segement 3 ( Hierarchy Structure )

Provide the Application component and InfoArea name where you need this Characteristics to be displayed as Infoprovider.

Once the characteristic is defined as info provider specific you can see the same object in the Info provider under the specified Info area ( under Infoprovider ) and Application component ( under infosources )

In the above screen shot we have attributes, Hierarchies and Texts because we have enabled them in the infoobject Properties under Master Data/Texts tab ( with Master Data and With Text ) and in the Hierarchy tab ( With Hierarchy )

Now we connect Target object with Source object using Transformation.

Right click on the Hierarchy Target Object ( Z_ACC ) and select Create Transformation from the context menu as specified below :

Any Hierarchy has the following segments 5 Segments :

1. 1.  Hierarchy Header
2. 2.  Hierarchy Description
3. 3.  Hierarchy Structure
4. 4.  Texts for Text Node
5. 5.  Texts for Hierarchy Level

Under each segment the mapping between Source and Target is Direct assignment. Please check the below screen shots for the mapping under each segement.

1.  Hierarchy Header

2.  Hierarchy Description

3.  Hierarchy Structure

4.  Texts for Text Node

5.  Texts for Hierarchy Level

Scenario 2 : If the Source Object has an External Hierarchy object.

Note : Y_SET is an external object for Source Object Y_AUD.

            Z_SET is an external object for Target Object Z_AUD.

Steps are same as specified above except in the start routine you need to also map external BW Target Object to Source Object. 

Please check below for the Start routine code and also the screen shot of source and Target Objects.

The Start routine code is as follows :

LOOP AT SOURCE_PACKAGE_3 ASSIGNING <SOURCE_FIELDS_3>.
if <SOURCE_FIELDS_3>-H_IOBJNM EQ 'Y_AUD'.
<SOURCE_FIELDS_3>-H_IOBJNM ='Z_AUD'.
else.
if <SOURCE_FIELDS_3>-H_IOBJNM EQ 'Y_SET'.
<SOURCE_FIELDS_3>-H_IOBJNM ='Z_SET'.
endif.
endif.
ENDLOOP.

In my next document I will update the details of how to upload hierarchies from DSO which has Node id and Parent id.

HI All,

Process of Creating Data Source in APO: -

For loading data in BW we need to create a data source in APO system.

1. Login to APO system and Go to SAP menu àGo to ‘Administration of Demand Planning and Supply’ as below

II.Then Administration screen will come as below

Here in planning area column you will find all the planning areas, double click on planning area for which you want to create data source.

III.  After selecting a planning area below screen will comeà Go to Extra à Data Extraction Tools tab.

IV. Then below screen will come

Here select Generate Data Source option.

V. Then system will ask for the Data Source name and settings as below.

The Data Source generated is by default having name starting with 9A, as per standard naming convention.

VII. Settings will do as per below.

No Extraction of Data Records Without Key Fig Value:-

Select this option if you want to prevent the system from transferring data records to Info Objects in the BW if all key figures in the data record have the value zero. Depending on data it will reduce the volume of records which the system transfers, and it will improve performance.

VIII. Block Size For BW Transfer:-

In this Box you have to mention how many records are transferred in one package. While transferring large no of data, it is required that the data need to split into multiple packages to avoid memory problems. Once source system will finish reading the data packages, it will transfer to BW.  With this option it is possible to change the default for all data extraction in the system.

IX. Parallel Processing Profile:-

You can ad a parallel processing profile which you have previously created in Customizing (Demand Planning -> Profiles -> Maintain Parallel Processing Profile). This determines how and if the reading and transfer of the packages is split into parallel processes. As such the block sizes that you enter in the parallel processing profile should be significantly smaller than the package sizes above.

X. Give the Name of Data Source and click on Execute option as highlighted below.

XI. When you click on execute option below window will appear

In this select fields which you want.

XII. Click on save option, then below window will appear. Click on Test Data Source

XIII. Then below window will come.

1. Uncheck the Debug option; otherwise it will go to ABAP Debugger. But if you want to debug then you can check this option.
2. Provide Planning version value.
3. If you want to execute with above selection, click on execution.
4. If you want to display click on display option.

Check above options and if you are getting desired output then click on back.

XIV. Then SNP data extraction window will appear.

In this click on Replicate Data Source option.

XV. Then below window will appear.

  In this select as Data Source option and click on tick. . It will replicate your this new data source with BW system.

XVI. Transport data source.

Click on this option then it will create a data package for your Data source.

XVII. Your Data source is ready as shown in below screen.

Regards,

Mithun

SAP BWNews Notes

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

1846493 - Important SAP Notes for SAP BW 7.3x powered by HANA

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

Generell Information

• SAP always recommends to apply the latest Support Package
• For all SAP 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  Business Warehouse (SAP 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 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.

.

SAP Modernizes Data Warehousing with the Launch of SAP BW/4HANA

- Our latest SAP SAP HANA platform innovation will future-proof data warehousing landscapes and unleash new ways to analyze data in real time.

We are proud to announce SAP BW/4HANA, a next-generation data warehouse application for running a real-time digital enterprise!
In addition to traditional on-premise deployment, the new solution will soon be available on Amazon Web Services (AWS) and the SAP HANA® Enterprise Cloud service so companies can conveniently modernize their data warehousing environments and accelerate their digital journey into the cloud.

SAP BW/4HANA was released to customers on September 7, 2016. For more information, visit  SAP BW/4HANA on SCN, SAP BW/4HANA on www.sap.com   and the SAP News Center. Follow SAP on Twitter at@sapnews.

See the recently featured content.

Check out the listed SAP BWNews notes to see what is delivered with the according Support Package.

SAP BWNews Notes

• 1949273 - Important SAP Notes for SAP BW 7.40 powered by SAP HANA
• Simplified: SAP BW 7.4 Release Notes Read this blog from Marc Bernard to find out about the  changes with a new SAP BW release or what features were introduced with certain support packages
• See the releasenotes for the support packages. Documentation/Release note information will be provived short before release of the according Support Package
• The release dates for the  Support Package Stacks can be found in the Support Package Stack Schedule (SMP login required)
• For generell Information about SAP NetWeaver BW 7.4 please visit SAP NetWeaver Business Warehouse 7.4
• 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.

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

SAP BW/4HANA

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

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

BLOG:DMO: optimizing system downtime ...

BLOG:Increasing the SAP-NLS Performance

Content

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

SAP BW Technical and Functional Upgrade

BLOG:Downtime minimization when upgrading BW systems

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

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

Upgrade was never been easier ...

SAP BW 7.40 - Feature Overview and Platform Availability

SUM for ABAP - Troubleshooting Guide

New:Get an overview about the BW specific upgrade steps here:

Upgrade to SAP NetWeaver BW 7.3x

Upgrade to SAP BW 7.40

Maintenance Planner – The Next Generation Experience for Landscape Maintenance with SAP Solution Manager

Update to SAP BW 7.50
     Information for the Upgrade to SAP BW 7.50

 

See also the changes to the existing BEx Versions 3.5 and 7.x after Upgrade to 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 BW Installation/Configuration (also on HANA). This document also includes the complete SAP 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!

     SAP HANA Blog - SAP BW on HANA on one server

    

See all SAP First Guidance Documents here -SAP 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 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).

Technical configuration is an elementary part of setting up and operating SAP system landscapes. For example, you have to perform initial technical configuration to bring a newly installed system into operation. But also during the lifecycle of an SAP system, technical parameters have to be set and adapted.

BLOG: BI-JAVA, BEx Web and EP: the real connection ...

 

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

The separation of the dualstack (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 de-installation 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, de-installation 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 (SP05). 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 de-installation 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

BLOG: SAP NetWeaver BW 7.0x Dual Stack split using SAPinst export/import method

BLOG: SAP NetWeaver Portal Upgrade 7.0 to 7.4

• top

 

Migration to SAP BW on SAP HANA

Database Migration Option (DMO) of SUM - Introduction

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.

Migration to SAP HANA made easy with DMO

New Version 1.7x available using the latest SUM/DMO SP13/14 Features and the new UI

SAP First Guidance - Using the new DMO to Migra... | SCN

 

 

SAP BW Near Line Storage solution (NLS) based on Sybase IQ

Improve decision-making capabilities by bringing unprecedented performance to SAP NetWeaver Business Warehouse with SAP HANA for current data and SAP Sybase IQ for historical data— achieving the perfect balance of cost and performance. The adapter for Sybase IQ as a near-line solution is delivered with the BW system. Integration of Sybase IQ makes it possible for you to separate data that you access frequently from data that you access rarely, thus making fewer demands on the resources in the BW system. The near-line data is stored in compressed form. You can thus reduce the costs incurred by data that is accessed less frequently.

 

More flexibility with  SAP 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.

 

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 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 BW (BW PCA) in the migration process of SAP BW to SAP 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 SAP BW on SAP HANA from an end-to-end perspective.

Please Note that since Q1/2014 the Presentation - Migration to BW on HANA - First Guidance concludes all of these manual efforts now.

 

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

BLOG: 3 Major Reasons To Migrate To SAP BW 7.4 on SAP HANA

BLOG: What’s the Difference Between a Classic #SAPBW and #BWonHANA?

BLOG: Upgrade and Migration - SAP BW on SAP HANA

BLOG:Migration of SAP Systems to SAP HANA

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

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

BLOG: The SAP HANA Reference for NetWeaver Basis Administrators

BLOG:

Migration to SAP HANA: Latest News about SAP Note 1775293

 

• top

 

SAP BW System Copy

 

SAP  BW 7.30  - Systemcopy ABAP

Since Release 7.30 SP05, it is now possible to perform a heterogenous system copy (including unicode migration) to migrate existing systems based on SAP  BW 7.30 SP05 and higher to SAP BW on SAP 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.
You can also refer to the SAP FIrst Guidance Document - Implementation - BW on HANA Export/Import | SCN

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 from NetWeaver 7.0x

 

Visit the SCN Page - System Copy Automation for SAP Business Warehouse System Landscapes

 

BLOG: New Note Analyzer for SAP BW PCA and Housekeeping

 

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

 

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

 

 

SAP BW Housekeeping Tasks

 

Important Housekeeping Principles for keeping your SAP 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 - SAP 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

BLOG: SAP BW-Performance Tuning through System Tables

 

• top

 

Event Presentations

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

 

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

 

TechEd 2014 Las Vegas/Berlin - ITM206 - Presentation Recording

 

• top

 

 

References/Experiences/DSAG/JAM

This is a collection of resources from the SAP SCN Network and it´s content is not reflecting the findings from this document of future upgrade and enhancements.

See how the german customer Kärcher upgraded their SAP 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 how another german Customer Stihl upgraded their BW on HANA Landscape from 7.30 SP09 to 7.40 SP12 including the BI-JAVA Landscape update.

 

BLOG:SAP BW Upgrade: Pre and Post upgrade activities with answer to why?

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

BLOG:SAP BW 7.4 Powered by HANA -- Promising Features (Part 1)

BLOG:What’s new in SAP NW BW 7.4 SP8

BLOG:Migrating to BW on HANA - Real Life Lessons - ASUG Webcast

 

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

SAP JAM site: "DSAG - Upgrade BW 7.x" => (By Group Invitation only) exchange with SAP and DSAG as interested customers.

• top

 

Sometimes we may need to generate hierarchies manually, in that case if you know Node id and it’s Parent ID then we can generate hierarchies successfully. you can also add root node if our requirement demands. Please check below for the details :

Source : Any source with fields Node Id and Parent ID

Target : Info provider specific Info object with hierarchy option enabled.

Please check below for the hierarchy which is already loaded using Node ID and Parent ID

In the above generated hierarchy the node ALL is not coming from Source and we need this to be added to our hierarchy. Please check below code written in the BW Start Routine

DATA : WA_SOURCE_PACKAGE like LINE OF SOURCE_PACKAGE.

WA_SOURCE_PACKAGE-ID = '1'.
WA_SOURCE_PACKAGE-NAME = 'ALL'.
WA_SOURCE_PACKAGE-CT_MGMT =''.

APPEND WA_SOURCE_PACKAGE TO SOURCE_PACKAGE.

Note : Here assume CT_MGMT represents Parent Id for a management Hierarchy which is coming from source object.

In the above Start Routine code we have created a new record (node id) with parent as blank which represents Root Node ( ALL ).

In the above screen shot we have a Field Level Routine for 0H_PARENTID which maps all child nodes to its respective parent node.

Please check below for the ABAP code :

IF SOURCE_FIELDS-CT_MGMT is INITIAL AND SOURCE_FIELDS-ID NE'1'.

RESULT ='1'.
else.
RESULT = SOURCE_FIELDS-CT_MGMT.
ENDIF.

Output :