In txn S_ALR_87013532

Project PS-ACA

WBS Element    PS-ACA-G-E1-F6-M035-L030

Actuals 2014

Another txnS_ALR_87013535

Project PS-ACA

WBS Element    PS-ACA-G-E1-F6-M035-L030

Object currency               MXN

Transaction currency     MXN

Project PS-ACA

In BW, activate both data sources:

0CO_OM_NWA_1          Network Activity: Costs

0CO_OM_WBS_1           WBS elements: Costs

Load the data into the 0PS_C041 cube

Browse the data in the 0PS_C041 cube

BEx Query

Hi,

this is a instruction manual to find inconsistent transformations in a Business Warehouse System.

First open the transaction se38 and run the programm "ZRSTRAN_CHECK_STEP_CONSTANTS". Chose the object version and check the option "check" or "repair". Then let it run.

Data Load failure due to No SID found for value 'xxxxx' of characteristic YYYYY.

For resolving such issues, we need to follow the below steps:

Consider your error to be No SID found for value '1020ZSOBPEDA_BABY TEST.

•      Go to RSD1, enter the name of your characteristic. We will take the example of 0MAT_PLANT here. Now go to "Compounding" tab and check if there is any characteristic with which it is compounded. We can see here that it has 0PLANT as a compounded characteristic. This means that the value for which our load has failed, has entry for MATERIAL and PLANT.

By looking at the value for which your load has failed, you should find out a fragment of it belongs to the compounded characteristic.

• Go to RSA1, search for 0MAT_PLANT. Right click and go to "Maintain Master Data".

• Now, enter the values in the fields - PLANT and MATERIAL in our case by bifurcating what you got in the error message. Excute. You will receive a pop - up saying that Data with specified selection does not exist. This is a method for confirming that the value for which our load has failed is not present in the required combination.

• Now remove the values from selection screen and click on execute. In the next screen, click on "Create" icon.

• You will now get a pop-up for entering values. Enter the value in the same combination as what you saw in your error message. Click on continue. Now save and come back.

You will now have to "Activate" your master data. Right click on your characteristic, click on Activate Master Data. You can now manually update the failed data package. It will resolve the no SID found issue.

Hi,

This document tells how to turn off starting process chain and turn it on again after some time.

Lets suppose the process chain is set to start everyday at 00:01 am and its ready for the next time to run.

It can be checked in RSPC / Process chains / <your PC> / Start process / Displaying Scheduled job(s):

it should look like this

or here:

(Status "release" means it is active but not running (=waiting for time to start).

Jobs that run in the past and ended have the status "Finished")

When we have to stop running job or when we are not sure it's running or not we should terminate selected job.

When a job has been terminated we can delete the job.

after deleting the job it should look like this:

To turn the process chain on again we use / Execution / Schedule (F8)

we should set priority

information in a status line can be seen

Now we may expect the process chain will start as usuall.

What can be checked as above.

Hope it will help,

Regards, Leszek

I am sharing my experience with a client system (Client a fortune 500 company, Runs a beverage (Soft) business in 140 Countries). Using the SAP BW solutions and capabilities since Year 2002 now currently with SAP BI 7.3 SP7 version.

Problem Statement

6 Months ago project team took decision to enhance the DB size to accommodate the DB growth for next 24 months. Implemented the DB size enhancement considering it would cater the enterprise needs for next 24 months. Unfortunately 50% of the expansion DB size is consumed in 5 months. So I started examining the reasons, root cause and solutions.

Current Solution

Periodically the experts from BW team (couple of service providers) use following techniques to improve the performance of DB and SYS (EDW).

1. 1. BW/BI Data housekeeping tasks
   1. Pros:
      • Able to manage all the table data growing places like 1) PSA. 2) DSO 3) Statistics 4) Infocubes
   2. Cons:
      • Unable to concentrate on the system level tables across all areas (Ex: FI, CO, MM, PP, HR, CRM...etc.)
2. 2. BW/BI Performance tuning techniques.
   1. Pros:
      • Able to manage all the table data growing places like 1) Aggregates. 2) Request Compression 3) Infocubes Compression 4) Partitioning 5) Indexing 6)BIA
   2. Cons:
      • Unable to concentrate on the system level tables across all areas (Ex: FI, CO, MM, PP, HR, CRM...etc.)

New Solution

Now I used a different technique to identify various tables in the System which are collecting the information and storing the data in the tables from time to time.

I have searched all the EDW (Enterprise data warehouse) and found 200+ tables. Performed a thorough analysis with respect to their

1. Information / Table / Data / usage (Where & When used).

2. Number of records / Size of the table and its growth.

3. Index creation (Active/Inactive-Last creation date).

4. Needed data retention duration with respect to Client’s expectations.

After a thorough I could Identify 43 tables satisfying my above rules (Four).

Analysis

I am really surprised to know that they are

1. 50 % of tables are never used in any place

2. Few are used hardly once in a quarter. Actually the usage is for Data administration need by the administrator.

3. The transaction / data older than 2years is stored in the tables.

Needed checks

1. Checked with the client team to move the data (older than 90 days) to near line storage
2. Basis team for validation for tables and schedule of data archive jobs.

          Tables         (Records found in Millions)

1. RSMONMESS                     (334.5 Million)

• Messages for the monitor

2. RSDDSTATAGGRDEF        (241 Million)

• BW statistics data

3. RSIXWWW                          (29 Million)

• Cluster Table for Storing Web Reporting Components

4. RSDDSTATEVDATA          (18.48 Million) 

• BW statistics data

5. RSDDSTATCOND               (17.8 Million)

• BW statistics data

6. RSZWOBJ                             (16 Million)

• Storage of the Web Objects

7. RSDDSTATHEADER           (11.5 Million)

• BW statistics data

8. RSZWBOOKMARK             (11.1 Million)

• Header Table of the Bookmarks

9. DDLOG                  (15 Million)       

• Buffer Synchronization

10. RSDDSTATAGGR               (12.5 Million)

• BW statistics data

11. RSERRORHEAD                  (10.4 Million)

• Incorrect Records (Header Table) (PSA error logs)

12. RSDDSTATLOGGING        (9.5 Million)

• BW statistics data

13. RSDDSTATDM                    (8.5 Million)

• BW statistics data

14. RSRWBTEMPLATE            (8.5 Million)

• Assignment of Excel workbooks as personal templates

15. RSRWORKBOOK               (7.1 Million)

• Where-used list for reports in workbooks

16. RSDDSTATINFO (777 K) (6.9 Million)

1. BW statistics data

17. RSDDSTATDELE                 (5.9 Million)

• BW statistics data

18. RSERRORHEAD (4.1 Million)

• Incorrect Records (Header Table)

19. RSERRORLOG                     (2.7 Million)

• Logs for Incorrect Records (PSA error logs)

20. RSBERRORLOG (2.36 Million)

• Logs for Incorrect Records
• Stores error handling logs due to following and other reasons:
• Warnings that are created during master data uploads for duplicate records
• Single record error messages in customer-specific transformation routines
• Table is accumulated a numerous error messages records for a DTP requests. In most cases this is due to many errors while BW is processing data and Info Package (IP) or Data Transfer Package (DTP) is setup in way that data duplicity needs to be recorded.

21. RSZWOBJTXT                     (1.1 Million)

• Texts for Templates/Items/Views

22. RSZWOBJXREF   (0.76 Million)

• Structure of the BW Objects in a Template

23. RSZWBOOKMARK            (1.18 Million)

• Header Table of the Bookmarks

24. RSZWVIEW                         (1.1 Million)

• Header Table for BW Views

25. RSZWITEM                          (2.1 Million)

• Header Table for BW Web Items

26. RSZWITEMATTR                (1.6 Million)

• Attribute Table of the Items (Contains Search Attributes) –

27. RSZWITEMDATA               (2.5 Million)

• BW Web Item Data (7.0)+

28. RSZWITEMXREF                (3.1 Million)

• Cross-Reference Table of the Items

29. RSZWBITMDATA               (1.2 Million)

• BW Web Item Data (7.0)+

30. RSZWBITMHEAD               (0.68 Million)

• Header Table for BW Web Items

31. RSZWBITMHEADTXT       (1.2 Million)

• Texts for BI Web Items (7.0+)

32. RSZWBITMTEXT                (0.7 Million)

• BW Web Templates: Language Texts

33. RSZWBITMXREF                (0.8 Million)

• BI Template Cross references to TLOGO Objects

34. RSZWBTMPDATA             (0.5 Million)

• BW Web Template Data

35. RSZWBTMPHEAD             (0.5 Million)

• Header Table for BW HTML Templates

36. RSZWBTMPHEADTXT  (0.8 Million)

• Texts for Templates/Items/Views

37. RSZWBTMPTEXT               (0.2 Million)

• BW Web Templates: Language Texts

38. RSZWBTMPXREF                (1.2 Million)

• BI Template Cross references to TLOGO Objects

39. RSRWBSTORE                    (2.1 Million)

• Storage for binary large objects (BW workbook tables -Excel workbooks)

40. RSSELDONE                        (1.5 Million)

• BW staging engine tables:

41. RSRWBINDEX                     (2.0 Million)

• List of binary large objects (Excel workbooks)

42. RSRWBINDEXT (1.8 Million)

• Titles of binary objects (Excel workbooks)

43. RSBMNODES                      (1.5 Million)

• “Hierarchical Log: Nodes”; If e.g. it takes a long time to set a DTP request to 'green' after it has been processed it is caused by large volume of data in this table. Since BI system in production a quite long time you got a lot of logs in it then you have a huge amount of entries in this table.

Assumption: The no-of records is a cumulative result of all the above 43 tables. It is subjected to change as it is dependent on the EDW System (Client's business , Reporting tools on EDW, etc,..)

Lesson Learned/Achievement: With the above analysis I could find 1,100 million records are there in the EDW which do not have any potential benefit to the client’s business or EDW system. After removing 1,100 Million records from EDW I could save 350 GB of disc space to my client.

Introduction

This document contains the Configuration steps which are to be performed after installing SAP BW system.

Step1: Maintain the logical Systems

After installation, login to the 000 client and add the logical system entry.

Transaction BD54: Add all Logical systems which are in use

Step2: Defining Client in transaction code SCC4 or use below path to configure client

It will take you to below screen

Create new entries

• Enter client number, name, logical system name, std currency, client role.

           For development system selects customizing

Changes and transports for client-specific objects

           For development system: “select Automatic recording of changes”

           For Quality/Production system: “No changes allowed”

Cross-client Object changes

           For development system: Changes to repository and cross-client Customizing allowed.

After creating the standard client, add the parameter login/no_automatic_user_sapstar in the instance profile and restart the system for the parameter to take effect. After the restart, you will be able to login to the standard client using the sap* user id   with the standard password.

Perform a client copy from 000 client to the standard client which you have created

T-code SCCL.

Schedule a background job to by giving the above input values.

Once the client copy is completed, perform a kernel upgrade to the latest level and then support pack upgrade.

Step3: RSADMINC (Customizing Table General BW) table configuration

Update the Table with below values:

INFOIDOCFRQ update with the value10

IDOCPACKSIZE update with the value 30000

PSAPARTSIZE update with the value 1000000      

File name: BW_OLAP_CACHE

File name span: BW_OLAP_CACHE_SPAN

UOM_BUFF_SIZE: 500

SPLT_QRY_TAB_THR: 50

SPLT_DM_TAB_THR: 20

ORA_PARALLEL_DEG: 4

TMPLID_ANALYZER: ANALYSIS_PATTERN_SPECIAL

RSER_TMPL_ID: 0REPORT_DEFAULT_SPECIAL

This table should have updated with User in source system for ALE communication – ALEREMOTE

Step4:ALEREMOTE settings for Background users

Set ALEREMOTE as the default setting for background users (table entry RSADMINA)

Step5:
Activating the Software Component SAP_BW in the CVERS_ACT Table

You can use Function module "RS_SET_ACTIVE_COMPONENT_FLAG" in SE37 to set flag I_ACTIVE_FLAG = 'X'

Step6: Preparing the BW System

Go to transaction code RSA1:

Start the Data Warehousing Workbench (transaction RSA1). When starting for the first time, the ‘myself source system’ is created automatically and table RSLOGSYSDEST is modified.

Step7: Activate Technical Content

When starting the Data Warehousing Workbench (transaction RSA1) for the first time, the content is activated automatically.

Step8: Set the BW Transport System as Default

Field TADIRPOPUP in table RSADMINS (System Settings) is set to “x”. With this entry, you define that the BW transport system is activated in the default system

In case of blank value the dialog prompting the user to enter a transport request does not appear when editing the objects.

Development system: As we need to record changes and collect into transport request, Field TADIRPOPUP in table RSADMINS should not
be blank.

This setting will work on top of SCC4 transport settings.

Step9: Defining the Recording Time for Transports

Go to->transaction code RSA1, click on transport connection.

Then Edit -> Transport -> Switch-on Standard.

Step10:

Create job and schedules weekly once

Job name: ZBW_OLAP_CACHE_CLEAR

Program name: RSR_CACHE_RSRV_CHECK

Step11:

Schedule report to clear the DTP buffer

Job: ZBW_DTP_CACHE_CLEAR

Program: RSBKCHECKBUFFER

Step12:

Deleting Messages and Parameters of the BW Background

Job: BI_DELETE_OLD_MSG_PARM_DTPTEMP on daily basis

Program: RSBATCH_DEL_MSG_PARM_DTPTEMP.

Step13:Metadata repository configuration

Prerequisite: The HTTP or HTTP(s) port needs to be open based on the usage. By default, metadata repository will open using HTTP protocol. In case if you want to launch metadata repository using HTTPS protocol, you can add the below ICM parameter in the instance profile using RZ10 T-code and restart the ICM in SMICM transaction.

Icm/HTTP/redirect_0            = PREFIX=/, FROM=*, FROMPROT=http,
PROT=https, HOST=logicalsystem.FQDN, PORT=XXXX (HTTPS PORT NO)

Transaction code: STRUST

Activate SSL server Standard

SPRO -> Maintain web protocol HTTP/HTTPS.

Transaction code SICF: Activate service “rso_metadata_repository”

Metadata repository then launches fine in RSA1transaction.

Step14: Activate personalization content:

Create Development package with project specific naming convention using T-code SE21 or SE80.

Then activate the personalization content using SPRO transaction

Please refer the below link for Part 2 of this Configuration Process.

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

Introduction

This document will contain the basic BW Configuration steps after installation of SAP BW system. The configurations mentioned here are to be performed after system installation and basis configurations mentioned in SAP BW 7.3 Configurations part1 document. Here is the link http://scn.sap.com/docs/DOC-55967

Step1: Set Analysis authorizations in transaction code RSCUSTV23

Set “Current Procedure with Analysis Authorizations“.

Step2: Hide 3.x Functions of Data Warehousing Workbench.

Path->SPRO->Display IMG-> Hide 3.x Functions of Data Warehousing Workbench.

Selecting below option can hide all 3.x functions of the DW Workbench for which there is a new functionality available.

Note: If the indicator is set, you are no longer asked if the old or new Data Sources should be transferred when they are replicated; they are always transferred as new Data Sources.

If you want to use old 3.x functionalities, don’t hide this function

Step3: Set Traffic Light Color in the below path of IMG

If no data available then status would be green

Incase of warnings ,status would be in yellow

Step3: Change source system name after transport in RSLGMP transaction or below path .

Path->SPRO-> IMG

Below settings needs to be done in quality and production systems. Which will convert  original source system name to target source
system name .

If we are transporting objects to quality system, target would be quality system .Original source system will be your development system where you have developed objects and moving to further landscape.

Step 4: Create Destination for Import Post-Processing in RSTPRFC or below path

Below setting needs to be done in target system (quality system and production system) before moving transports.

Process chain transport will fail ,in case of unavailability of below setting or ALEREMOTE password issue or RFC destination unavailability between BW development system to further landscape (TBD<->TBQ, TBP).

Step5: Display of Numeric Values in the Business Explorer in RSCUSTV4 transaction code below path

Set “X” in case of ‘value division by zero’

‘does not exist’

‘number overflow’.

Any of above mentioned scenario in BEx report will give out put as “X”

In case of mixed currency or UOM ,report will show * value.

Step6: Activate Personalization in BEx

Path->SPRO->IMG

It will allow you to personalize BEx variables, webapplication variable and BEx history.

Step7: Set BEx Analyzer Version in RRMX_CUST or below path

Path->SPRO->IMG

Set BEx analyzer version to be called from RRMX

You can select either 3.x version or Sap Netweaver version.

Step8: Maintain Web Protocol (HTTP/HTTPS)

Path->SPRO->IMG.

Specify HTTP or HTTPS as per requirement,

By default HTTP protocol will be called by web application designer or query designer.

Step9:Set Standard Web Templates

Path->SPRO->IMG

Specified web Templates will be called for broadcasting, query pre calculation, EP reporting, adhoc analysis.

Step10: Determine Settings for Web Templates

Path->SPRO->IMG

Below specified Web template needs to be activate from business content

Step11: Maintain Source system ID’s in RSA1 transaction code

Path->

RSA1->TOOLS->Assignment of Source Syst.To Source Syst. ID.

Thank You for reading !

SAP BW 7.4 on SAP HANA / The  In-Memory Data Fabric

SAP BW? - Three Things to Know ...
Read this bog by Roland Kramer.

Overview SAP BW 7.4 SP05 on SAP HANA and further Roadmap

Key Features

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

SP5 and above is highly recommended for running SAP BW 7.4  on SAP HANA!

Background

Initially, when SAP NetWeaver 7.4 got released in early 2013, it was meant to be the foundation for taking SAP's Business Suite on to the HANA platform. At that time it was made transparent that BW – as part of SAP NetWeaver 7.4 – would be ready to run to support such a scenario as an embedded component for the Business Suite. However, for a stand-alone SAP BW as an EDW application on SAP HANA it has been recommended to wait for SAP NW 7.4 SP5 or above. SAP BW 7.4 SP4 (and below) is  to a large extent identical with SAP BW 7.3 and 7.31. However, SAP BW 7.4 SP5 and above holds a significant set of new features– and thus new code – especially in the context of SAP HANA.

Recommendation

As outlined since the advent of SAP NetWeaver 7.4, it is highly recommended to run SAP BW 7.4 on SP5 or above, preferably SP6 which is available at the time of writing – more details on the availbility of higher SPs can be foundhere. The reasons are the following:

• A significant set of new features.
• Many OSS notes and their underlying corrections are based on SP5 as the minimum SP level. A downport of such corrections is not viable due to the significant differences between SP4 and SP5 (and above).
• At the time of writing, there are 100+ customers on SAP BW 7.4 SP5 or above. Experience so far is
  excellent. SAP's own productive SAP BW 7.4 system has been updated to SP6 recently w/o hick-ups and even ahead of schedule.

Please see OSS note 1600929 ("SAP BW powered by SAP HANA DB: Information") for further details. Especially note that it is required to run SAP BW 7.4 SP5 and above on top of SAP HANA SP7. Future SPs of SAP BW 7.4 might require higher versions of SAP HANA.

Further Recommendations

• Check the presentationUpgrade to SAP BW 7.40 for SAP BW specific upgrade steps
• For EDW use case scenarios: Start only with SAP BW 7.4 SP05 or higher
• If you plan to upgrade your ERP to EhP7 (based on NetWeaver 7.40) first, you have to upgrade your corresponding BW System at least to 7.30 or higher (e.g.7.31) first, to stay compatible with the ERP Backend, check the Information attached to the following SAP Notes
  • Note 1388258 - Version Interoperability within the SAP Business Suite
  • Note 1951805 - Adjusted Version Interoperability for Business Suite 7i2013

• If you are running  SAP BusinessObjects BI Suite on SAP NetWeaver 7.4, please be aware of the following:
  • SAP BusinessObjects BI Suite 4.1 Support Pack 1  or BusinessObjects BI Suite 4.0 Support Pack 6 is mandatory! Lower SP levels do not incorporate the enhancements delivered with SAP NetWeaver 7.4
  • See more in the SAP BusinessObjects BI Suite release restriction e.g. SAP BusinessObjects BI Suite  4.1 Support Pack 1 Release Restrictions
• If you are still running Query Designer 3.x on your BW system, please note the following:
  • The BEx tools from SAP BW 3.5 are not available in SAP NetWeaver 7.40. Whereas the Analytic Engine of BW 7.4 can still execute queries which were  with the defined with the BEx 3.5 Query Desginer, the workbooks  created with the BEx Analyzer or WEB Templates need to be migrated . Please read “Cookbook for Migration to BEx 7.0” in SAP Note 1807522 - BEx 3.5 Objects Migration to BEx 7.0
    • You can find a list of obsolete functions and proposed workarounds in the SAP Help Library
    • The detailed maintenance strategy for the SAP BW 3.5 front-end add-ons is described  in SAP Note 1932461
  • SAP strongly advises you to read the available documentation thoroughly in order to benefit from the support SAP offers now and in the future, and to make it easier for the customer to make the transition away from the obsolete reporting tools.
  • More information can also be found on the SAP BEx Spaceand SAP Note 1729988 
• If the SEM Add-On is applied on the NetWeaver system, you can change the modeling in the Solution Manager for better handling at any time,  see the blog "Good News - Easier Modeling of the SEM Add-On in Solution Manager"

Additional Information:

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

  Roadmap for SAP BW on SAP HANA - One slider

  SAP BW 7.4 ABAP Support Packages Schedule and Implications

   Simplified Real-Time Replication

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

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

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

Content

• SAP Business Intelligence Architecture
• 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 Business Intelligence Architecture

• top

SAP BW Technical and Functional Upgrade

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

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

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

Upgrade to SAP NetWeaver BW 7.3x

Upgrade to SAP BW 7.40

New:

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

 

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

• top

 

BW ABAP and BI-JAVA Installation

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

See the details of the Software Logistics Toolset 1.0 here.

 

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

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

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

 

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

 

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

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

 

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

 

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

 

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

 

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

• top

 

Migration to SAP BW on SAP HANA

Migration to SAP HANA made easy with DMO

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

 

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

Database Migration Option (DMO) of SUM - Introduction

 

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.

 

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

 

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

You can also enable SAP 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.

 

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: Upgrade and Migration - SAP BW on 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 (incuding 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.

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

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

 

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

 

 

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

 

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

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

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

(contains manual steps znote_1767420 which has to be applied and executed beforehand.

Note 1810570 - Task Manager for Technical Configuration (7. Improvements)

Contains the attachment znote_1810570 which has to be applied and executed beforehand.

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

Note 1880465 - SAP_BW_HOUSEKEEPING not terminating

• top

 

Event Presentations

TechEd 2012 Las Vegas/Madrid

TechEd 2013 Las Vegas/Amsterdam

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

 

• top

 

 

References/Experiences/DSAG

This is a collection of ressources from the SAP SCN Network and it´s content is not reflecting the findings from this document of future upgrade and 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 Dr. Berg's Upgade to 7.30 Experience. This is a overview presentation based on 2011 findings.

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

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

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

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

 

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

• top

 

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

Support Package 7 for SAP  BW 7.4  is released!

We are pleased to announce the release of SAP BW 7.4, SP7, a SP release that builds upon your investment in SAP  BW 7.4 by adding even more capabilities and functionality in various areas. Read more on the SAPBWNews page for SAP BW 7.4 Support Packages and in the according Release Notes.June 2014

Simplified Real-Time Replication using Operational Data Provisioning

Check out this new page to get a summmary of the Simplified Real-Time Replication using Operational Data Provisioning with  SAP BW 7.40. June 2014

SAP BWNews Notes

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

Release Notes for the SAP NetWeaver 7.31 Support Package Stacks

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

News

•   Support Package 9: (Logon to SAP Help Library is required)

  • The SAP HANA-optimized DataStore object is now obsolete. See documentation

  • The integration of SAP BW and the SAP Landscape Transformation Replication Server (SAP LT Replication Server) allows real-time replication of data in BW and provides two options: You can use the SAP LT Replication Server for delta procedures for tables that do not contain any fields that are capable of producing delta figures. This makes it possible to use delta procedures for extractors that do not have delta logic.

    The trigger-based replication approach allows you to significantly reduce the administrative load if you have frequent master data updates.

    For futher information see "Data Transfer with SAP Landscape Transformation Replication Server (New)"

  • A planning function type is a procedure that can be parameterized and that change transaction data in BW Integrated Planning and in the Planning Application Kit. You can also implement customer-specific planning function types, in order to implement specific procedures and apply them to transaction data.

    • If you implement an SQLScript procedure, you can run a customer-specific planning function type optimized on the SAP HANA database. For futher information see "Implementing Business Logic for Planning Function Types on the SAP HANA Database (New)"

    • If you want to reuse a customer-specific planning function type and you only want to make slight modifications, you can copy the function type and modify it as required. This process is often quicker than creating all the parameters again as new parameters. For futher information see Copying Planning Functions (New)

  •   Details on Logging Saved Values (Enhanced)

• Support Package 8: (Logon to SAP Help Library is required)

  • Data Transfer with SAP Landscape Transformation Replication Server (New)

    The integration of SAP BW and the SAP Landscape Transformation Replication Server (SAP LT Replication Server) allows real-time replication of data from non-SAP sources and SAP sources to and provides the following options:

    You can use the SAP LT Replication Server for delta procedures for tables that do not contain any fields that are capable of producing delta figures. This makes it possible to use delta procedures for extractors that do not have delta logic.

    The trigger-based replication approach allows you to significantly reduce the administrative load if you have frequent master data updates.

    Note that complex extractors should generally not be replaced by replication with the SAP LT Replication Server.
    
    Learn more about the present possibilities to achieve real-time replication into SAP BW 7.30 powered by SAP HANA and read the presentation "Real-time Data Warehousing with SAP LT Replication Server (SLT) for SAP NetWeaver BW" by Marc Hartz.

• SAP HANA-Optimized DataStore Object: With the next Support Package, or when SAP Note 1849497 is implemented, SAP HANA-optimized activation will be performed for all standard DataStore objects. Conversion of DataStore Objects to SAP HANA-optimized objects will then be obsolete. This conversion will no longer be necessary, since all standard DataStore objects will be optimized for SAP HANA automatically. You can still use existing SAP HANA-optimized DataStore objects, but there will also be a new transaction for reconversion. Related Information.

• Enhanced ODP Source System:  For sources that offer Operational Data Providers (ODP) hierarchically, you can now select the ODP via the source hierarchy in DataSource maintenance. You can select ODPs for SAP HANA for example via the package hierarchy.You can now change the field names for the DataSource in the Proposal tab. If you do not make any changes to the field names, these are adapted automatically as before if they are not suitable as PSA field names.

• Support Package 7: (Logon to SAP Help Library is required)
  • The structure of the documentation is enhanced.Some topics were bundeled others expanded and revised to make the documentation structure more clearly represented.See details.
  • The tool for editing the runtime parameters for DataStore objects has been revised and enhanced. It is now more user-friendly and offers users the option of changing the settings for MPP databases and the SAP HANA database.

  • The data flow documentation now contains more details about data transfer processes. Information has been added about the fields used in the filter and the key fields in the error stack: Saving Data Flow Documentation as an HTML File

  • Sybase IQ as a Near-Line Storage Solution 
    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 less demands on the resources in the BW system. The near-line data is stored in compressed form and needs to be backed up less frequently. You can thus reduce the costs incurred by data that is accessed less frequently.

• Support Package 6: (Logon to SAP Help Library is required)

• SP6 introduces the concept for handling Inactive Data with SAP HANA Database:
  To optimize the use of the main memory in SAP HANA, we introduced the concept of inactive data in the BW system. Optimization is supported as of SAP HANA Support Package 5. Implementing this concept results in higher priority displacement of data from Persistent Staging Area tables and from tables of write-optimized DataStore objects from the main memory, in the event of main memory bottlenecks. This has a positive effect on hardware sizing when dealing with a large quantity of inactive data of these object types.
• SAP HANA-Optimized DataStore Object: Change Log Compression
  As of SAP HANA Revision 38, you have the option of having a change log created for every activated record in SAP HANA-optimized DataStore objects.

• 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.31 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.31.
• 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.

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

SAP BWNews Notes

What comes with the Support Packages?

Support Package 07

Transfer of Reporting Objects and Reporting Data with SDATA: Using the new SDATA tool, you can transfer reporting objects and data from a source location to a target location - for test and demo purposes. This enables you for example, to transfer reporting objects and data - for test purposes - to BW trial versions in the cloud. Note that the RSDATA is intended exclusively for test and demo purposes and is not suitable for transporting BW objects or transferring data in a productive system landscape!

In expert mode in the SAP HANA analysis process, the Maintenance Execution function is now available. This function allows support to simulate execution of the SAP HANA analysis process for troubleshooting purposes.

CompositeProvider:The function for setting cardinality has been changed. Conversion routins are now taken into account if you enter constants. The external display is now shown

.

In the transformation, you can now use the new rule type Calculation 0RECORDMODE for ODP.

Various interface changes and user-friendliness enhancements have been introduced in the data transfer process (DTP):

For detailed information visit the  Release Notes for SAP BW 7.4 SP7

Support Package 06

• Find the details of the enhanncements delivered in the Release Notes for SAP BW SP 6

Support Package 05

• Find the details of  the features enabeled with SP 5 in the SAP NetWeaver BW 7.4 on SAP HANA - Overview and Roadmap
• Investigate the features for SP5 implemented in a SAP BW 7.4  SP5 for non-HANA use case  environment.
• Please see the according  Release notes with new functions, enhancements and changes in SAP NetWeaver Business Warehouse (BW), Support Package Stack 05.

• Exception implementation SPS 05 for NetWeaver 7.40

  This SPS is not applied via the SPAM procedure due to fundamental changes in the SP05 Basis Support Package.

  Instead this update is scheduled via the software update manager (SUM).

  Find additional informationen in the blog - Software Update Manager (SUM): introducing the tool for software maintenance.

  The creation of a stack.xml via the Solution Manager and the usage of the ASU toolbox and/or the Upgrade tasks lists are mandantory. (SP05 requires the new 7.41 UC Kernel, which is not available on 32-Bit OS)

Further Information:

• 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.

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

Last update: Feb 2014.

For a complete picture please visit our  Partner Information Center

Find application development partners easily in the Application Development Partner Directory

Integration Scenario BW-OBI - OLAP BAPI

Integration Scenario BW-ODB- Reporting for OLAP

Integration Scenario BW-OHS Open Hub Service

Integration Scenario BW-SCH Job Scheduling

Integration Scenario BW-STA Data Staging

Integration Scenario BW-UDC-JDBC Universal Data Connect JDBC

Integration Scenario BW-XMLA XML for Analysis

Integration Scenario NW-BI-NLS  Nearline Storage

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

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

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

Partner Integration:

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

In txn S_ALR_87013532

Project PS-ACA

WBS Element    PS-ACA-G-E1-F6-M035-L030

Actuals 2014

Another txnS_ALR_87013535

Project PS-ACA

WBS Element    PS-ACA-G-E1-F6-M035-L030

Object currency               MXN

Transaction currency     MXN

Project PS-ACA

In BW, activate both data sources:

0CO_OM_NWA_1          Network Activity: Costs

0CO_OM_WBS_1           WBS elements: Costs

Load the data into the 0PS_C041 cube

Browse the data in the 0PS_C041 cube

BEx Query

Hi,

this is a instruction manual to find inconsistent transformations in a Business Warehouse System.

First open the transaction se38 and run the programm "ZRSTRAN_CHECK_STEP_CONSTANTS". Chose the object version and check the option "check" or "repair". Then let it run.

Data Load failure due to No SID found for value 'xxxxx' of characteristic YYYYY.

For resolving such issues, we need to follow the below steps:

Consider your error to be No SID found for value '1020ZSOBPEDA_BABY TEST.

•      Go to RSD1, enter the name of your characteristic. We will take the example of 0MAT_PLANT here. Now go to "Compounding" tab and check if there is any characteristic with which it is compounded. We can see here that it has 0PLANT as a compounded characteristic. This means that the value for which our load has failed, has entry for MATERIAL and PLANT.

By looking at the value for which your load has failed, you should find out a fragment of it belongs to the compounded characteristic.

• Go to RSA1, search for 0MAT_PLANT. Right click and go to "Maintain Master Data".

• Now, enter the values in the fields - PLANT and MATERIAL in our case by bifurcating what you got in the error message. Excute. You will receive a pop - up saying that Data with specified selection does not exist. This is a method for confirming that the value for which our load has failed is not present in the required combination.

• Now remove the values from selection screen and click on execute. In the next screen, click on "Create" icon.

• You will now get a pop-up for entering values. Enter the value in the same combination as what you saw in your error message. Click on continue. Now save and come back.

You will now have to "Activate" your master data. Right click on your characteristic, click on Activate Master Data. You can now manually update the failed data package. It will resolve the no SID found issue.

Hi,

This document tells how to turn off starting process chain and turn it on again after some time.

Lets suppose the process chain is set to start everyday at 00:01 am and its ready for the next time to run.

It can be checked in RSPC / Process chains / <your PC> / Start process / Displaying Scheduled job(s):

it should look like this

or here:

(Status "release" means it is active but not running (=waiting for time to start).

Jobs that run in the past and ended have the status "Finished")

When we have to stop running job or when we are not sure it's running or not we should terminate selected job.

When a job has been terminated we can delete the job.

after deleting the job it should look like this:

To turn the process chain on again we use / Execution / Schedule (F8)

we should set priority

information in a status line can be seen

Now we may expect the process chain will start as usuall.

What can be checked as above.

Hope it will help,

Regards, Leszek