My intention in preparing this document is when I was searching for a detailed step by step guide for implementation of invoice document into BW and I couldn’t find such document anywhere apart from help.sap.com information.

Before I proceed further into steps I just want to provide some information about the extractor for invoice datasource from help.sap.com

There are 3 major criteria to be satisfied to invoice data into BW.

1. Datasource name has to be maintained in each invoicing processes (step1)
2. Required invoice source document category and invoice source item category in the custom FM.
3. The reconciliation key should be always closed.

Without satisfying any of the above conditions datasource cannot pull data for that particular invoicing process.

STEPS

There are few major steps which have to be carried out in source system before we extract data into BW.

Step 1: Maintain Datasource field in each invoicing processes in SPRO (IMG Customization)  in the below path

SPRO-->Financial Management (New) -->Contract Accounts Receivable and Payable-->Integration-->Invoicing in Contract Accounts Receivable and Payable-->Invoicing-->Invoicing processes

I want to provide little introduction for EVENT 2710 before we proceed to step 2.

          Once the above step is fulfilled then proceed with step 2:

Step 2: SPRO-->Financial Management (New) -->Contract Accounts Receivable and PayableàProgram EnhancementsàDefine Customer-Specific Function Modules

Copy the sample FM given by SAP “FKK_SAMPLE_2710” and make changes as per your requirement for example to pull different type of invoice source document category and invoice source item category (maintained in DFKKINVDOC_I table).

Even though if datasource is maintained in SPRO in each invoicing processes (look in Step 1) these changes in the custom FM can impact in extraction of data to BW.

For EX: I’ve added the below code in the custom FM “Y_BIFKK_SAMPLE_2710” to extract “C1” Collective invoices.

Step 3: Run the t-code “FKKINV_BW_MON” to check the relevant documents which are ready to extract into BW.

In the above screen lock symbol beside RECONCIL. KEY is OPEN those are not posted into BW.

For EX: Scenario 1 take the below record:

As per SAP standard invoicing process “C1” is not pulled into BW. But after I added my code in custom FM and maintained this custom FM in EVENT 2710 then this “C1” invoice document is pulled into BW.

Another condition for extraction reconciliation key is to be closed.

After the simulation, log will show whether the documents are able to pull into bw or any issues

Scenario 2 take the below record:

The above record shouldn’t be pulled as the reconciliation key is not closed.

After simulation:

Step 4: Go to t-code “FKKINV_BW_MA” to run the extraction job to DELTA tables (like MCEX jobs in LIS).

Look for completed status:

In RSA7:

Step 5:

If you are loading for the first time then run an Infopackage with option "INIT with DATA". After the run is successfully you won't get any record but a system record for the datasource.

Then you have run the delta infopackage to get the data into BW.

Run DELTA infopackage in BW to extract those delta invoice documents and look for the invoicing processes in PSA.

After my test changes in custom FM and closing reconciliation key, I could able to pull “C1” and “F4”.

The above steps will take you the whole kind of configurations and steps to extract invoicing data into BW.

Please find the below help.sap.com links for more information

Update of Invoicing Data to SAP NetWeaver BW - Integration with Other Components and Products - SAP Library

Following are two main reasons why it is important to prevent accidental migration of queries from 3.x to 7.x-

1) Some features (Formulas) might not work (or not work same way) in 7.x as compared to 3.x

2) Large number of users to be migrated to newer version of BEx Analyzer (time consuming)

Different Options

The first two options are preventive solutions while the third one is a reactive workaround.

Option 1 (Recommended Proactive Approach) - Enhancing standard function module

Enhancing standard function module (FM responsible for opening query and saving Query) in BW to prevent opening of 3.x query in 7.x query designer.

Notes:

1. Enhancing standard function module using implicit enhancement.

2. This will prevent opening of 3.x queries in 7.x query designer.

Note: Designer needs to be restarted to open any other query.

Step 1 (Implicit Enhancement)-

similar enhancement on "RSZ_X_COMPONENT_SET_NEW"

Step 2-

Tried to open ZTEST_3x 3.x query in 7.x query designer.

Step 3-

To allow specific users to migrate 3.x to 7.x, create a Z table and maintain list of allowed users. Code written above will be bypassed for these set of users.

Step 4-

To prevent accidental migration of 3.x to 7.x BEx Query when Query designer is launched from BEx Analyzer, logic has been put up in FM (RSZ_X_COMPONENT_SET_NEW) responsible for saving query.

Option 2- Create a different set of user-id’s in Production for BW super users. SAP OSS note 962530 can be used as a reference. Only new set of user id's will have access to 7.x designer tool.SAP OSS note 962530 (1686583 for BEx Analyzer) can be referenced.

Steps-

1. This new set of user ids will be created following a specific agreed naming convention. For instance Z7<*>, where <*> can be abbreviation of super user’s id.

2. This set of user ids will be shared amongst the 7.x toolkit users.

3. Using note 962530, an entry in t-code RS_FRONTEND_INIT  (Parameter- QD_EXCLUSIVE_USER) can be made with asterisk i.e. “Z7*”.

4.These new set of user’s will have following authorization-

a. Explicit display access to eCRM BW BEx queries.

b. Edit access to only those BEx queries whose name starts with- “Z7S_<*>”.  (7.x BEx queries by Super Users).

c. Super users will be able create and save query only if its name starts with “Z7S”.

5. It should be noted that nobody should create 3.x queries following above naming convention.

Option 3- Apply reactive workaround by doing reverse migration of queries which were migrated to 7.x

If query is migrated to 7.x accidentally, SAP notes 949330/1003481 can be used to apply reverse migration.

There are documents already published on how to restrict F4 help values in BI Report queries. But in case where you have to do this for more than one query we can make this dynamic and same BADI implementation can be called for all the reports for which this is required.

Business scenario

We were working on retail SAP BI implementation and we have a requirement of having different levels of article hierarchy in selection screen in most of the reports that we have developed. Now the requirement was to populate the second level of hierarchy based on the first level  and third level based on the second level.

So for example this first level of hierarchy is Department.

Department will have Values as below

1

2

3

4

Now if the next level is division it will have values like

101

102

103

201

202

2013

Now if the user enters Department 1, for division F4 help he should only see below values

101

102

103

Now this has to be done for many reports.

Solution:

We can create a parameter table in SAP BI and call it  “ZBI_F4_HELP”.

Below will be the fields in the table

I_Query = Technical Name of the Query

I_IOBJNM = Technical Name of the Info-Object

I_VNAM = Technical Name of the Variable by which the info-object is restricted

I_DESC = The level of the Info-object (In our scenario for Department it will be 1 for division it will be 2)

The screenshot below shows the sample entries.

So from above screenshot what we want is when Query ZRT_MP01_Q046_A is executed, we want the F4 values for variable for 0MATERIAL_0CM_CDT2 should populated based on value for variable for 0MATERIAL_0CM_CDT1 and value for 0MATERIAL_0CM_CDT3 should be populated based on the variable value for 0MATERIAL_0CM_CDT2.

The code in BADI will look something like below.

We first read entries from the parameter table ZBI_F4_help for the given query.

Now we have to read the relevant row for the given info-object and populate variable values accordingly.

Sample code is given below for 2 levels. The values for second level is read from material master.

Summary

The objective of the document is to give information on the activities performed during and after BI 7.4 upgrade.

System Information

Before Upgrade: SAP BI 7.0 SP 22 - SAPKW70022

After Upgrade: SAP BI 7.4 SP 7 - SAPKW74007

Introduction

This part involves few important activities of pre-upgrade.

Planning the upgrade is a significant task and should be in an organized manner. We have planned our SAP BI 7.4 upgrade in three different phases and with reasonable time difference between each to identify issues and resolving them.

• Hardware Upgrade which involves Oracle patching as well (This might not be happening in all systems. Based on the requirement, business will decide in doing this)
• Stack Split (ABAP and Java stacks)
• Application Upgrade

          Online Upgrade of ABAP stack

          Offline Upgrade of ABAP stack

          Online Upgrade of Java Stack

          Offline Upgrade of Java Stack

BI activities in first and second phase is all about testing the system after the activities. The actual activities starts before and after SAP Application upgrade.

Hardware Upgrade and Stack Split

As I have already mentioned, this is not mandatory for all systems. It is based on how old or how powerful your system is.

Our system is pretty old and so we have decided to do the hardware upgrade and stack split at the same time in order to reduce cut over

Basically from BI perspective, we don’t have to do much during this activity except for testing.

The common issues that we have faced in all environments are below. Again, this is particular to issues that we have faced in our system. There might be less or more than what we have listed.

• Source system connections will get affected which basis will correct in few minutes, but this has to be first in your checklist
• Since we have done the stack split, portal and bookmarks might not work which is also a basis configuration settings.
• Integrated planning function tcode RSPLAN might not work and will give an error saying "Cannot find a J2EE Engine”. The issue was during the split the WebDynpro RFCs get deleted and need to be recreated.

• Once the stack split is completed successfully, we have got a new portal link and it worked fine, but when we try to execute the reports from Query designer, the screen was as below. The reason for this issue is same as for No 3. WebDynpro RFCs get deleted during stack split and need to be recreated.

• Process chains/jobs scheduled will be in released state and will never start. Basis team has reset the parameter rdisp/btctime in RZ10 and RZ11 from 0 to 60 which resolved the issue

• We had few APD jobs which updates data from BI query to AL11. These jobs failed after the hardware upgrade and the reason for this failure is
  /interface (or the location in AL11 of your APD jobs) was not mounted on the BI servers. Basis has done this mounting activity and the issue was resolved.

Application Upgrade

The below is the rough information on different phases in SAP application upgrade.

Most of these are done by basis and a BI consultant’s involvement should be there in Checks phase, Pre-processing and Post processing phase.

Checks Phase – Pre upgrade Task

Basis will perform few activities from their end and before moving to the pre-processing phase, below activities should be performed from BI side

We can access this information using the Tcode /N/ASU/UPGRADE. Below is the screenshot and detailed information is also given. ***

Please note that we need to access this tcode 000 client and not in the default client. But the activities should be performed from the default client (which is 100, I believe this is same for all)

Below are the details of the activities which has to be performed based on your system.

1. Check some notes before upgrade (Basis):

Check OSS 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_CONTT 77.35: Information about installation and upgrade

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

     Note 1562522 - SAPINST aborts during central instance installation

     Note 1603103 - SMSY: NetWeaver 7.3 upgrade

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

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

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

     Note 1636841 - Version management: Compatibility with SAP BASIS 777.x00

2. Add-On Compatibility of SAP NetWeaver: (Basis)

Check OSS Notes:

     Note 1532805 - Add-On Compatibility of SAP NetWeaver 7.3

     Note 1826531 - Add-on compatibility of SAP NetWeaver 7.4 – ABAP

3. Deactivate the Real Time Data Acquisition (BI - Not Required)

Trans: RSRDA. Though this is not active in our system, the upgrade will perform this step and therefore nothing is required to be done, apart from for your information. This task is automated in the Database Migration Option (DMO) in SUM and also in the task list SAP_BW_BEFORE_UPGRADE.  You do not have to perform this task manually if you are using one of these tools.

4. Check activate of ODS objects: (BI)

Trans: SE38/SA38 -> RSAODSACTIVATE

Report RSAODSACTIVATE checks whether your ODS objects are actively
present. Before you can perform the upgrade, all requests must be activated in
all ODS objects or deleted from the M table.  Alternatively you can go to
RSA1 => Administration => DataStore Objects.   This check is
automated in the upgrade process. Make sure that it does not report errors
before you start the upgrade.

5. Upgrade Check Report RSUPGRCHECK, isn’t valid for our release.  Step needs to be confirmed (Basis)

6. Remove temporary BI tables, this deleted any temporary BI tables and is a Basis step.  (Basis)

7. Check/Repair Status of Info Objects: (BI)

To avoid a data loss, upgrade shutdown, and long runtimes, check the status of your InfoObjects before the upgrade.  

Proceed as follows:

Call transaction RSD1 -> All InfoObjects -> Update.

Activate all information objects that are not assigned with a green light.

Then choose Extras -> Reorganize InfoObject tables to reorganize the InfoObject tables.

For more information, see SAP Note 458363.

8. Check inconsistencies with RSZ* Tables: (BI)

Trans: SE38/SA38 -> ANALYZE_RSZ_TABLES

Report ANALYZE_RSZ_TABLES is designed as a check-tool for detecting and solving different types of inconsistencies in the main query definition database tables. Execute the report to check possible inconsistencies with RSZ* Tables. Please read SAP Note 792779 for more information.  The program is recommended for BW system administrators.

9. Activate Info Objects (BI)

Trans: SE38/SA38 -> RSDG_IOBJ_ACTIVATE:

Activate Info Objects without automatic transport connection.

10. Clean/delete the messages for error (BI)

Trans: SE38/SA38 ->RSB_ANALYZE_ERRORLOG/RSBM_ERRORLOG_DELETE

You can use the report RSB_ANALYZE_ERRORLOG to analyse which DTPs have created how many single record error messages, and to how many requests these messages are distributed. You can use the report RSBM_ERRORLOG_DELETE for single DTPs to delete the messages for requests up to a specified date.

If numerous single record errors are frequently created for specific DTPs, you should analyse the relevant requests in more detail and, if required, eliminate the error cause (for example, adjusting the transformation routines).

11. Clean-up entries from table RSIXWWW: (Not Required)

SE38/SA38 ->RSRA_CLUSTER_TABLE_REORG (Just for your information, and you might like to see what it says, as this step will
be run during the upgrade)

Cluster table RSIXWWW contains large datasets that you can no longer access. This results in bottlenecks with the disk space.  Use the report RSRA_CLUSTER_TABLE_REORG to delete the entries that are no longer required in table RSIXWWW.  This task is automated in the Database Migration Option (DMO) in SUM and also in the task list SAP_BW_BEFORE_UPGRADE.  You do not have to perform this task manually if you are using one of these tools. 

12. Check code pages setting (Basis)

SE38/SA38 -> RSCPINST

RSCPINST is a setup and diagnostic tool for NLS configurations. Specify the set of languages needed, and the tool determines the settings required for a consistent NLS configuration. Modifications to the application profile parameters must be carried out manually.

13. Check Master Data consistency (BI)

Check the consistency of master data by executing report RSDMD_CHECKPRG_ALL. Execute in background ('Execute in Background') in order to avoid timeout.  If the report returns errors run the report again with the 'Repair' option flagged.

14. Clean-up background jobs (Basis)

SE38/SA38 -> RSBTCDEL2

Clean unused jobs if possible - check especially logs from job BI_WRITE_PROT_TO_APPLLOG. 

Related Documents

http://scn.sap.com/docs/DOC-58813 - BI Activities involved in SAP BI 7.4 upgrade – Part 1

Author(s): Anil Kumar Puranam and Peesu Sudhakar

Company: Deloitte

Created on: 30th October, 2014

Authors Bio:

Sudhakar Reddy Peesu is an SAP Technology professional with more than 15 years of experience leading SAP BW/ABAP implementations, developing custom applications, and developing IT strategy. He is a PMP certified manager, has led BW/ABAP teams with hardware and landscape planning, design, installation and support, and development teams through all phases of the SDLC using the onsite/offshore delivery model.  He has strong communication, project management, and organization skills.  His industry project experience includes Banking, Consumer/Products, and Public Sector industries

Anil Kumar. Puranam is working as a Senior BW/BI Developer in Deloitte consulting. He has more than 10 years of SAP BW/BI/BO experience. He has worked on various support/implementation projects while working in consulting companies like Deloitte, IBM India, and TCS.

How to rebuild the BWA with BWA splits:

We generally build the BWA on the cube when we started the data loads.  And there is highly possible that the data in the cube is minimal at the time of BWA initial fill compare to the deltas that we receive. If we do BWA init fill with less data, we would endup reorgnize or rebuild due to large data roll up in the delta laods.

To aviod this proble, while creating the BA , we can give the instruction to system to build the BWA witht the estimated data in the cube. So that system will allocate the enough BWA index space to the  Info prociders by allocating space in different blades. The below screen shot shows how to rebuild BWA with splits.

Approach: When we index into BWA for first time i.e INITIAL FILL, we need to switch to “Own Setting” in “LOAD Admin” tab and go high value for the number of records . This will force the system to split BWA.

Estimate Runtime of Fact Table Indexing:

We can get this information from RSRV checks:

All Elementary Tests → BI Accelerator:

The system estimates the time required to fill the fact index. It uses the current parameter values for background and dialog parallel processing. The time taken is calculated from the processes available and the estimated maximal throughput of data records in the database, the application server, and the BIA server.

The calculated duration is an estimate; the load on the system, the distribution of data across block criteria and deviations during processing can all affect the actual time taken.

For ex:

Results after checking:

Estimate Memory Consumption of Fact Table Index

We can get this information from RSRV checks:

All Elementary Tests → BI Accelerator:

The system estimates the size of the fact table index of a BI accelerator index. In doing so, the system analyzes the data in the fact table and provides a projection.

For ex:

Results after checking:

BWA alert when the index size reaches 1billion.

• Program YBWA_ALERT_SEND
• Currently this program does, 2.1 billion limit check as well as Load Admin setting check (Own Setting Vs System Setting) from BWA end
• When there are exceptions in the above check the program, email sent out the exceptions to the email distribution entered.
• We can add the program to Process Chain to run them on daily basis to execute these checks.

Porgram is attached.

BWA overloaded alert:

Business Warehouse Accelerator (BWA) runs properly if we limit for the amount of data we can load into the BWA compare to thresh hold limit. The thresh hold limit is defined as below We should only load < “50% of the available blade memory” into the BWA.

• Report RSDDTZA_BIA_OVERLOAD_EMAIL can be used to check the availability
• We can create process chain to schedule a broadcast mail, for which we need to use report RSDDTREX_ADMIN_MAINTAIN to specify the e-mail
  addresses.
• Entry to maintain the email ids are BIA_NOTIFY_EMAIL_ADDRESS1 ,BIA_NOTIFY_EMAIL_ADDRESS2,… etc

Refer note 1767424 for more information.

Sample output:

BWA query performance metrics process

• BEx Query can be created as below on 0TCT_C03
• This query gives trend of BWA Read Time in Seconds per Million records.
• You can provide a date range and Multi providers as selection.
• In Addition to Time to read 1 M records, there are other measures such as time to read hierarchy, Time to Prepare Read, No of records
  Read etc are available for display in this query

We can also use one of the Analysis from ZBWA_TOOLKIT program. We can select Index Usage Analysis and we can go with different selections provided there.

This document will guide through the steps to implement for extraction of invoice in FI-CA.

Introduction to FI-CA flow

There are 3 main areas in FI-CA, Invoicing, Posting and Payment. Below is a small diagram illustrating the overall data flow of the SD & FI-CA, FI-CO.

Explanation above illustration:

After SD billing has taken into place then the document created is Invoice. When Invoice is saved at the same time Posting document is also generated. Invoice is related to AR accounting where as Posting is related to GL Accounting.

Then afterwards when customer does the payment then Payment document is generated when payment is done via payment run or payment transaction (FPCJ, Cash journal, T-code).

BW Part:

As highlighted in red box in the above screen, I will go through extractors which are used for FI-CA data extraction.

Below are the extractors for each area:

Invoice – 0FC_INVDOC_00 (FICA Extraction of Invoicing Document Data)

Posting - 0FC_BP_ITEMS (FI-CA Business Partner Items) or 0FC_CI_01 (FICA Cleared Items for Interval) or 0FC_OP_01 (FI-CA Open Items at Key Date)

Payment - 0FC_PAY (Payments)

Invoice Extraction (FI-CA)

Below are the brief steps for Invoicing  Extraction:

1. Datasource name has to be maintained in each invoicing processes (step1)
2. Required invoice source document category and invoice source item category in the custom FM.
3. The reconciliation key should be always closed.

Without satisfying any of the above conditions datasource cannot pull data for that particular invoicing process.

STEPS

There are few major steps which have to be carried out in source system before we extract data into BW.

Step 1> Maintain Datasource field in each invoicing processes in SPRO (IMG Customization)  in the below path

SPRO-->Financial Management (New) -->Contract Accounts Receivable and Payable-->Integration-->Invoicing in Contract Accounts Receivable and Payable-->Invoicing-->Invoicing processes

Below is the little introduction from help.sap.com on event 2710

Step 2>SPRO-->Financial Management (New) -->Contract Accounts Receivable and PayableàProgram EnhancementsàDefine Customer-Specific Function Modules

Copy the sample FM given by SAP “FKK_SAMPLE_2710” and make changes as per your requirement for example to pull different type of invoice source document category and invoice source item category (maintained in DFKKINVDOC_I table).

Even though if datasource is maintained in SPRO in each invoicing processes (look in Step 1) these changes in the custom FM can impact in extraction of data to BW.

For EX: I’ve added the below code in the custom FM “Y_BIFKK_SAMPLE_2710” to extract “C1” Collective invoices.

Step 3> Run the t-code “FKKINV_BW_MON” to check the relevant documents which are ready to extract into BW.

In the above screen lock symbol beside RECONCIL. KEY is OPEN those are not posted into BW.

For EX: Scenario 1 take the below record:

As per SAP standard invoicing process “C1” is not pulled into BW. But after I added my code in custom FM and maintained this custom FM in EVENT 2710 then this “C1” invoice document is pulled into BW.

Another condition for extraction reconciliation key is to be closed.

After the simulation, log will show whether the documents are able to pull into bw or any issues

Scenario 2 take the below record:

The above record shouldn’t be pulled as the reconciliation key is not closed.

After simulation:

Step 4> Go to t-code “FKKINV_BW_MA” to run the extraction job to DELTA tables (like MCEX jobs in LIS).

Look for completed status:

In RSA7:

Step 5>

If you are loading for the first time then run an Infopackage with option "INIT with DATA". After the run is successfully you won't get any record but a system record for the datasource.

Then you have run the delta infopackage to get the data into BW.

Run DELTA infopackage in BW to extract those delta invoice documents and look for the invoicing processes in PSA.

After my test changes in custom FM and closing reconciliation key, I could able to pull “C1” and “F4”.

The above detailed steps will go through detailed extraction of Invoice.

Please find the below help.sap.com links for more information

Update of Invoicing Data to SAP NetWeaver BW - Integration with Other Components and Products - SAP Library

Kindly provide your valuable feedback.

Other documents from my knowledge base:

Scheduling FI-CA related Delta Extraction

Triggering Process chain after completion of ECC Delta Extraction Job

Golden rules/Tips & Tricks for BW/BI Designing

Automation of the Data Load from SAP R/3 to BI

Design Solutions for BI/BOBJ Reporting (Part 1)

Data Extraction from data services(BODS) to BI

Data from data services cannot be loaded to BW,If data source is BI 7.1 compatible.In such situations we need to create 3.x data source by following steps
to do data load from Business objects data services into BI 7.1 data flow.

Goto RSA1 -> select infosources in Modeling of Administrative work bench

Right click on Application Component and select Additional Functions - > Create InfoSources 3.x

Technical name and Long description of the info source needs to be given as below

The fields needs to be loaded into BW data source from Data services needs to be given as an infosource fields

After entering fields that needs to loaded from Data services click enter and Activate

After creating Info source, Right click on info source and select Additional functions -> Create Transfer Rules

Give the source system as Data services source system name

Clicks enter and activate the Transfer rules and data source created.

Once data source is created from BI side, the structure needs to be replicated in Data services to load data from Data services.

SAP Business Warehouse (SAP BW) offers a complete solution for all enterprise data warehouse needs. It tightly integrates data warehousing capabilities on a comprehensive and scalable platform while leveraging best practices to enable the provisioning of all information needed to drive business intelligence predicated on a single version of the truth.

Videos

Live from the SAPinsider Studio: Dan Kearnan Moderates a Panel on SAP BW 7.4 on HANA Launch:

Dan Kearnan of SAP (far right) moderates a panel at SAPinsider's BI-HANA 2014 event on the launch of SAP NetWeaver BW 7.4 powered by SAP HANA. Joining Kearnan are (from L to R) Lothar Henkes of SAP, John Appleby of Bluefin Solutions, and David Théroux-Bénoni and Pawel Mierski of Molson Coors. April 2014

Presentations:

Overview SAP BW 7.4 SP5 on SAP HANA and further Roadmap

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

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

SAP EDW PositioningCheck out this presentation that is positioning EDW based on the SAP Real-Time data platform

Scale Out - Best PracticesCheck out this l  comprehensive overview on the delta information for scale out implementations

The HANA EDWRead the  blog from Thomas Zurek about the HANA EDW

SAP HANA-Native Reporting on BW Data in SAP  BW powered by SAP HANA  – Positioning

An important part of the whole SAP BW powered by SAP HANA story is the option to create scenarios with interaction between data owned and modeled in SAP BW and data owned and modeled in native SAP HANA tools. These are what we call mixed scenarios. The interaction can take place in both directions, from SAP HANA to SAP BW and vice-versa, and there are options to physically move the data or to virtually expose it. Read more in this position by Klaus Nagel and Thomas Zurek

Demo - Failover Scenario SAP BW Powered by SAP HANA

This demo shows business continuity of SAP BW 7.3 powered by SAP HANA in a failover scenario. The technical demo shows the continuous operation of the BW application server when one of the HANA DB high availability nodes goes out of service (due to a hardware failure, etc.).

Documentation

• SAP Help Library / the SAP Help Portal and read about the
  SAP Business Warehouse 7.3, powered by SAP HANA
  • Concept of Data Flow in Business Warehouse
  • Overview of the Architecture of SAP NetWeaver BW

SCN Pages

• Stay tuned on the SAP BW 7.4 - Powered by SAP HANA  page and the SAP BW on SAP HANA Space
• Find out more about the Application livecycle management of SAP BW   SAP  BW ALM in detail.
• Get technical deep dives on the SAP BW on SAP HANA First Guidance and SAP BW How-to Guides page
• Stay informed on the maintenance of the SAP BW releases and visit the SAP BW Support Packages pages
• See release specific information listet on the according pages

  • SAP BW 7.4

  • SAP BW 7.31

  • SAP BW 7.3

  • SAP BW 7.0 & EHPs

Hi All,

There are couple of steps to perform data archiving into NLS.

As i was unable to find any specific doucment with my requirement when i was performing Data archiving on NLS

Run the transaction RSA1

Select the Cube under info provider

Select the archiving tab

At the bottom of the screen select the Archving request button

A new popup will be coming up select the date range as per the requirement

Provide the date range criteria

Execute the job in background mode

Click the refresh screen to display the updated status for the archiving request.

Double click on the status button to continue performing other steps

Select the verification phase as per the requirement

Select the deletion phase to 70

Execute the job in Background mode.

Refresh the screen to get the update details

Once the data archiving is done sucessfully all the status will turn into Green, It means that all the data has been copied and verified and set

the data to deletion from BW

Hope you all understand the concept of archiving clearly.

But make sure of couple of things - the object which you have planned to archive check the number of records.

As time varies during archiving and some time it may take to run for couple of days, Depending on the scenario and requirement.

In my case it ran for couple of days.

Regards

Mohammed

Hi All,

Today ill share BW tips which is help full for those in AMS project  which reduces their effort spent on displaying the same cube data each and every time during their analysis,

This simple method will help you to reduce your time on the same, just give a try if you feel comfortable with this method.

LISTCUBE tcode which you can make use of this

Have you ever thought of how to save selection screen and output fields in tcode LISTCUBE? (an alternate way to view your cube data)If not below are the steps to be followed to make use of it.

Advantages:

•   This will help in  reusability like avoiding the LISTCUBE tcode again and again for the same selections.
•   This will also helps you to  reduce certain amount of your manual work.

Here is the steps to be followed.

     1.Go to the TCODE LISTCUBE.

     2.Select your needed info provider to be displayed.

3. Same time give the program name starting with Z or Y ( This is the program which is going to be reused) and please make a note of it.

4. Now execute the screen , which displays  your selection screen and select your needed field for the selection, later also select your needed fields for the output using field selection for output tab

5. After selecting it, kindly select the Save button which is there on the top of the screen to save it as variant.

6. You will get the popup screen in which it will ask you to update with Variant name and its Description, enter the needed info and save it again through the save button or through the file menu Variant --->Save.

7. Use can make use of options check box which is available in the screen  like Protect Variant, which protects others to changes this variant on the same program, means it can be changed only by the created user, other is not certainly required, still if you need to know its purpose kindly press F1 on corresponding check box for its use.

8. Now go to TCODE SE38 and give the program name as the one which you gave it in the LISTCUBE transaction and execute it.

9. Once you execute it you will get the screen as you decided in listcube, click on variant button for save variants or click on field selection for output tab for your changes like to save another variant or to make the changes in the current variant.

10. Here if you want to view the save variants from list cube you can use the variant button and select your variants to display it which has been stored already.

11. Select the need variant and execute the program to get your desired outputs.

Note: you can also store ‘N’ number of variants from this program itself.

Now instead of going LISTCUBE again and again to make your selection you can make use of this program when you want to make use of the same info provider to display your output for n number of times, this will reduce your time in selecting your selection option, and your desired output screen.

Dependencies: If the structure of the Info Provider changes, a program generated once is not adapted automatically. The program has to be manually deleted and generated again to enable selections of new fields.

Thanks,

Siva

Objective:

To provide overview of SAP Standard utilities useful for BW Operations and Production support.

During regular operations often there are situation where following information is required:

1) Analysis of Background Job : What the job was doing, where did it spent what amount of time, what memory did it consumed etc

2) BW- Accelerator                  : How often BWA indexes were used, BWA overall summary, Which infocube lies on which blade to judge impact during issues

3) Query Usage Analysis          : How often the query was executed and by whom

4) BW- Process Chain Analysis: Basic need to monitor chain and observe several aspects like run time of steps in a chain etc

Often consultant has to spent lot of time to find the information and has to apply various tricks to find the relevant information.

However this document provides an overview of some standard utilities those support consultant to derive the information:

Analysis of Background Job:

Step 1: Execute Trnx: St13 and select the program: BACKGROUND_JOB_ANALYSIS and execute

Step 2: Enter the job name /user and time frame for which you would need information and execute:

Step 3:  Execution will provide the list of jobs running in the system based on the selections entered.

Step 4: Select the job you would like to analyze from the results and select the button "STAD" as displayed in following image:

Step 5: Execution of STAD button will display the statistical information of job like displayed in following image:

Step 6: In case further details are required double click on the result row, this will lead you to a transaction providing tabular view of detailed statistical data

BW Accelerator:

Step 1: Execute Trnx: St13 and select the program: BWATOOLS and execute

Step 2: Execution displays a Cockpit to perform various analysis on  BWA as displayed in following image:

Index Usage Analysis

Step 3: Select button "Index Usage Analysis" to analyze the frequency of the index used to judge the quality

Step 4: Provide the selections for which you need to perform analysis and execute as displayed in following image:

Step 5: Execution will provide the statistical information of the selected infocube or the cube based on the time frames

BWA Index Attributes: To get the details of indexes like, Size of Indexes, No. of Records in Indexes,Which blade host which index etc

Step 1: Select button "Index Properties" and select execute:

Step 2: Select the appropriate selection for which you need to perform analysis like displayed in following and execute:

Step 3: Execution provides the statistical information about the indexes to be used for further analysis as displayed in following image:

Step 4: Further details can be obtained by selecting the particular records.

Query Usage Analysis

Step 1: Execute Trnx: St13 and select the program: BW_QUERY_USAGE and execute

Step 2: Execution displays following image to enter the selections for analysis:

Step 3: Uncheck the option "All Queries" if you want to analyze for any specific query (Currently I will uncheck to analyze one particular query) and execute

Step 4: Execution will display an additional window asking to select the relevant query:

Step 5: Expand the relevant infoarea and select the query to analyze:

Step 6: Select query and select button "Open" located at the bottom of window:

Step 7: This will display the information who executed the query and how many times:

Same exercise can be performed for all queries, for a specific time frame or for any specific user in the system.

However this utility has limitation to not provide the information about the time stamp of its usage although you can use the time frame field in selection window to narrow down the findings.

BW Process Chain Analysis

Step 1: Execute Trnx: St13 and select the program: BW-TOOLS and execute

Step 2: This program provides range of options to perform various BW analysis, for our example select option: "Process Chain Analysis" and execute

Step 3: Next window provides option to analyze complete chain or particular process types in the system for specific time range as displayed in respective images:

Step 4: Enter the name of chain if you need to analyze particular chain else leave it blank and execute

Step 5: This will display a tabular view of the chains those were running/completed/aborted in the system during the mentioned time frame

Step 6: The tabular view provides two views of data as following:

               i) Tree View: This view is displayed when you select the column: "Log Id" of chain and displays the tree shaped view of the progress of chain.

              ii) Hierarchy View: This is more analytical view providing the information of runtime of each step in process chain,displayed by selecting column "Chain"

This transaction provides lots of useful utilities this would highly recommend to use and explore further options based on your need.

Hope it helps !!

There are documents already published on how to restrict F4 help values in BI Report queries. But in case where you have to do this for more than one query we can make this dynamic and same BADI implementation can be called for all the reports for which this is required.

Business scenario

We were working on retail SAP BI implementation and we have a requirement of having different levels of article hierarchy in selection screen in most of the reports that we have developed. Now the requirement was to populate the second level of hierarchy based on the first level  and third level based on the second level.

So for example this first level of hierarchy is Department.

Department will have Values as below

1

2

3

4

Now if the next level is division it will have values like

101

102

103

201

202

2013

Now if the user enters Department 1, for division F4 help he should only see below values

101

102

103

Now this has to be done for many reports.

Solution:

We can create a parameter table in SAP BI and call it  “ZBI_F4_HELP”.

Below will be the fields in the table

I_Query = Technical Name of the Query

I_IOBJNM = Technical Name of the Info-Object

I_VNAM = Technical Name of the Variable by which the info-object is restricted

I_DESC = The level of the Info-object (In our scenario for Department it will be 1 for division it will be 2)

The screenshot below shows the sample entries.

So from above screenshot what we want is when Query ZRT_MP01_Q046_A is executed, we want the F4 values for variable for 0MATERIAL_0CM_CDT2 should populated based on value for variable for 0MATERIAL_0CM_CDT1 and value for 0MATERIAL_0CM_CDT3 should be populated based on the variable value for 0MATERIAL_0CM_CDT2.

The code in BADI will look something like below.

We first read entries from the parameter table ZBI_F4_help for the given query.

Now we have to read the relevant row for the given info-object and populate variable values accordingly.

Sample code is given below for 2 levels. The values for second level is read from material master.

Data Extraction from data services(BODS) to BI

Data from data services cannot be loaded to BW,If data source is BI 7.1 compatible.In such situations we need to create 3.x data source by following steps
to do data load from Business objects data services into BI 7.1 data flow.

Goto RSA1 -> select infosources in Modeling of Administrative work bench

Right click on Application Component and select Additional Functions - > Create InfoSources 3.x

Technical name and Long description of the info source needs to be given as below

The fields needs to be loaded into BW data source from Data services needs to be given as an infosource fields

After entering fields that needs to loaded from Data services click enter and Activate

After creating Info source, Right click on info source and select Additional functions -> Create Transfer Rules

Give the source system as Data services source system name

Clicks enter and activate the Transfer rules and data source created.

Once data source is created from BI side, the structure needs to be replicated in Data services to load data from Data services.

SAP Business Warehouse (SAP BW) offers a complete solution for all enterprise data warehouse needs. It tightly integrates data warehousing capabilities on a comprehensive and scalable platform while leveraging best practices to enable the provisioning of all information needed to drive business intelligence predicated on a single version of the truth.

Videos

Live from the SAPinsider Studio: Dan Kearnan Moderates a Panel on SAP BW 7.4 on HANA Launch:

Dan Kearnan of SAP (far right) moderates a panel at SAPinsider's BI-HANA 2014 event on the launch of SAP NetWeaver BW 7.4 powered by SAP HANA. Joining Kearnan are (from L to R) Lothar Henkes of SAP, John Appleby of Bluefin Solutions, and David Théroux-Bénoni and Pawel Mierski of Molson Coors. April 2014

Presentations:

Overview SAP BW 7.4 SP5 on SAP HANA and further Roadmap

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

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

SAP EDW PositioningCheck out this presentation that is positioning EDW based on the SAP Real-Time data platform

Scale Out - Best PracticesCheck out this l  comprehensive overview on the delta information for scale out implementations

The HANA EDWRead the  blog from Thomas Zurek about the HANA EDW

SAP HANA-Native Reporting on BW Data in SAP  BW powered by SAP HANA  – Positioning

An important part of the whole SAP BW powered by SAP HANA story is the option to create scenarios with interaction between data owned and modeled in SAP BW and data owned and modeled in native SAP HANA tools. These are what we call mixed scenarios. The interaction can take place in both directions, from SAP HANA to SAP BW and vice-versa, and there are options to physically move the data or to virtually expose it. Read more in this position by Klaus Nagel and Thomas Zurek

Demo - Failover Scenario SAP BW Powered by SAP HANA

This demo shows business continuity of SAP BW 7.3 powered by SAP HANA in a failover scenario. The technical demo shows the continuous operation of the BW application server when one of the HANA DB high availability nodes goes out of service (due to a hardware failure, etc.).

Documentation

• SAP Help Library / the SAP Help Portal and read about the
  SAP Business Warehouse 7.3, powered by SAP HANA
  • Concept of Data Flow in Business Warehouse
  • Overview of the Architecture of SAP NetWeaver BW

SCN Pages

• Stay tuned on the SAP BW 7.4 - Powered by SAP HANA  page and the SAP BW on SAP HANA Space
• Find out more about the Application livecycle management of SAP BW   SAP  BW ALM in detail.
• Get technical deep dives on the SAP BW on SAP HANA First Guidance and SAP BW How-to Guides page
• Stay informed on the maintenance of the SAP BW releases and visit the SAP BW Support Packages pages
• See release specific information listet on the according pages

  • SAP BW 7.4

  • SAP BW 7.31

  • SAP BW 7.3

  • SAP BW 7.0 & EHPs

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

Release of SAP BW 7.4 SP8

SAP BW 7.4 SP8 powered by SAP HANA is the next milestone for enterprise data warehousing with BW on HANA and provides  the next level of simplification for BW .In addition, SAP BW on Hana’s Virtual Data Warehouse capabilities have been enhanced for even more flexibility.

The further push down of transformations and OLAP capabilities  are next steps for excellent data Load –  and Analysis performance.

Customers focusing on the planning capabilities will benefit from the enhanced Planning application Kit  and FOX usability.

You can register for the openSAP SAP Business Warehouse powered by SAP HANA course now!

Listen to Marc Hartz and Ulrich Christ introducing the renewed concepts and possibilities when SAP BW 7.4 SP8  is powered by SAP HANA. They’ll introduce the major guiding points and semantics of a data warehouse and demonstrate them in a business scenario, directly in the system. You will learn and experience the latest developments, with SAP BW 7.4 SP 8 powered by SAP HANA, as well as opportunities for real-time data integration and agile data modelling. You will see what it means to consume the data via a data warehouse and how SAP HANA helps to speed up data analysis. Enjoy!

Highlights of SAP BW 7.4 SP8 powered by SAP HANA

Virtual Data Warehouse

• Next level Open ODS Views

• Additional CompositeProvider scenarios

Simplification

• Advanced DataStore Object consolidating DataStore Objects and InfoCubes

• HANA model generation for BW Queries

• Common user experience for data modeling

Big Data

• SAP HANA dynamic tiering for SAP BW

• Enhanced operations and Query optimization for NLS

Performance

• Next level of performance in data staging for BW on HANA

• Further push down of OLAP capabilities

Planning

• Planning application Kit (PAK) feature complete with BW-IP

• Enhanced FOX productivity and usability

Additional Information:

• Upgrade to SAP Business Warehouse 7.40

  SAP NetWeaver Business Warehouse (not only on SAP HANA) continues to be the  cornerstone of SAP's strategic vision for enterprise data warehousing providing organizations a solid data foundation to capture, store, transform and manage data in a scalable, enterprise-ready data warehouse. See this presentation to understand the mayor steps for a successful upgrade to SAP Business Warehouse 7.40 SP06 and higher
  

• BW-IP/PAK Enhancements with SAP NetWeaver 7.40 SP8

This presentation mainly lists the removed limitations of the PAK by revision, explains the FOX enhancements for IP, shows how the support of the CompositeProvider in addition to the MultiProvider works, and describes the new master data maintenance UI based on WebDynpro.

• SAP Business Warehouse Demo Video Page

• SAP First Guidance Collection for SAP BW powered by SAP HANA

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

• SAP BW 7.4 ABAP Support PackagesSchedule and Implications

• Simplified Real-Time Replication

• SAP BW NLS Solution

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

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

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.

 

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

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.

 

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: What’s the Difference Between a Classic #SAPBW and #BWonHANA?

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

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

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

 

TechEd 2013 Las Vegas/Amsterdam - ITM204

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

 

TechEd 2014 Las Vegas/Berlin - ITM206

 

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

 

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

• top