Determine the data source for the Open Hub

Define the Open Hub Destination

In the Destination tab Define the properties for the Open Hub, such as the server and file name, as well as the format

In the Field Definition tab, include the field names for the Open Hub Destination

Create the corresponding Transformation

Map each InfoObject to their corresponding field

It is possible to add regular formulas

Use the End Routine to define the name for the fields in the Open Hub, but consider a counter only for the first line.

Execute the DTP

Once the Data Transfer is complete, the file is generated and it can be viewed through AL11

ABAP Routine

*$*$ begin of routine - insert your code only below this line        *-*

... "insert your code here

   DATA: t_rs TYPE TABLE OF _ty_s_TG_1,
          wa_rs TYPE _ty_s_TG_1.

wa_rs-account ='ACCOUNT'.
wa_rs-flow ='FLOW'.
wa_rs-cat_code ='CAT_CODE'.
wa_rs-company ='COMPANY'.
wa_rs-currency ='CURRENCY'.
wa_rs-data_source ='DATA_SOURCE'.
wa_rs-interco ='INTERCO'.
wa_rs-profit_center ='PROFIT_CENTER'.
wa_rs-ri_code ='RI_CODE'.
wa_rs-scenario ='SCENARIO'.
wa_rs-scope ='SCOPE'.
wa_rs-time ='TIME'.
wa_rs-signeddata ='SIGNEDDATA'.
wa_rs-createdate ='CREATEDATE'.

ZCOUNTER = ZCOUNTER + 1.
IF ZCOUNTER = 1.
  APPEND wa_rs TO t_rs.
ENDIF.
LOOP AT RESULT_PACKAGE INTO wa_rs.
  APPEND wa_rs TO t_rs.
  DELETE RESULT_PACKAGE.
ENDLOOP.

RESULT_PACKAGE[] = t_rs[].

*$*$ end of routine - insert your code only before this line         *-*

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

Applies to: SAP BW/BI

Summary : This Article demonstrates the step by step process to upload multiple flat files into a Infoprovider. This reduces the manual effort.

Author: Mayuri Swarna

Created on: 23 Apr 2014

Author Bio : Mayuri Swarna has experience in SAP BI Implementation and Production Support projects

Introduction

Some times in an implementation project or in the production Support environment, we would have come across a situation where we need to load/reload multiple flat files (ex: daily historical data) received from other source system in a sequence into a data target. This loading process involves manual effort and is cumbersome. So I thought of automation of this process so that it will reduce the manual effort.

Solution Approach

Assuming that all the flat files to be loaded are residing in a predefined folder path in the SAP BW application Server, An event triggered process chain with and infopackage and DTP and at the end an ABAP will be created. In the infopackage file name routine, write the code to sort the flat files with the given mask and will take the first file and identified dynamically. In the last step of the process chain, ABAP program will move already processed flat file from the main folder to the predefined back up folder so that remaining flat files will be available for the infopackage and will trigger the same process chain by raising the same event which is used in the start variant of the same process chain.

Step by Step Approach

Infopackage

Create an infopackage and write a routine for a file name so that it will sort all the flat files with the given mask in the predefined main folder where all the flat files are residing and dynamically picks the first one and process.

The sample code as follows:

DATA: v_dir   TYPE epsf-epsdirnam VALUE '/sapdownload/FL/main/',
v_mask TYPE epsf-epsfilnam VALUE 'FLA_201403*',
it_dir_list TYPE STANDARD TABLE OF zeps2file,
wa_dir_list TYPE zeps2file.

CALL FUNCTION 'Z_GET_FILE_NAME_FOR_DIRECTORI'
EXPORTING
dir_name               = v_dir
file_mask              = v_mask
TABLES
dir_list               = it_dir_list
EXCEPTIONS
invalid_eps_subdir     = 1
sapgparam_failed       = 2
build_directory_failed = 3
no_authorization       = 4
read_directory_failed  = 5
too_many_read_errors   = 6
empty_directory_list   = 7
OTHERS                 = 8.
IF sy-subrc <> 0 .

ELSE.
SORT it_dir_list by name.
LOOP AT it_dir_list INTO wa_dir_list WHERE name CS 'FLA_201403'.
CONCATENATE v_dir wa_dir_list-name INTO p_filename.
exit.
ENDLOOP.
ENDIF.

DTP

Create a normal DTP which loads the data from PSA which is loaded by previous infopackage to the data target. Here is nothing new.

ABAP Program

Create and ABAP program which will sort all the flat files with the given mask (which is defined in the program variant) in the predefined main folder and moves the already processed flat file to another predefined backup folder. After this program will  trigger the same event which is used in the start process of the same process chain if the flat files exist in the main folder.

Sample code as follows:

  REPORT  ZBW_FILE_UP.

TYPE-POOLS : ABAP.

TYPES:TT_RESULTS          TYPE STANDARD TABLE OF BTCXPM,
TT_DIR_LIST         TYPE STANDARD TABLE OF ZEPS2FILE.

DATA: IT_DIR_LIST         TYPE STANDARD TABLE OF ZEPS2FILE,
IT_RESULTS          TYPE STANDARD TABLE OF BTCXPM,
WA_DIR_LIST         TYPE ZEPS2FILE,
V_COMMAND           TYPE SXPGCOLIST-NAME,
V_PARAMETER         TYPE SXPGCOLIST-PARAMETERS,
V_STATUS            TYPE EXTCMDEXEX-STATUS,
V_EXITCODE          TYPE EXTCMDEXEX-EXITCODE,
V_FILE_NAME         TYPE CHAR100,
V_BFILE             TYPE CHAR100,
V_MFILE             TYPE CHAR100,
V_DIR               TYPE EPSF-EPSDIRNAM,
V_MASK              TYPE EPSF-EPSFILNAM,
V_DEL_MASK          TYPE EPSF-EPSFILNAM,
lv_event TYPE string VALUE 'BW_FU',
lv_para  TYPE string VALUE 'BW_FU',
lv_inst  TYPE msxxlist-name.

SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-000.
PARAMETERS:P_FILE    TYPE EPSF-EPSFILNAM.
SELECTION-SCREEN END OF BLOCK B1.

DATA:C_INMAIN_FILE_PATH TYPE  CHAR1024          VALUE '/sapdownload/FL/main/',
C_INMAIN_FILE_BPATH TYPE  CHAR1024          VALUE '/sapdownload/FL/backup/',
C_FILE_MOVE_CMD    TYPE  SXPGCOLIST-NAME   VALUE 'Z_FILE_MOVE',
C_STAR             TYPE  CHAR1             VALUE '*'.

START-OF-SELECTION.

V_DIR = C_INMAIN_FILE_PATH.
V_MASK = P_FILE.

*-- Get file list from directory using the mask entered in the selection screen
PERFORM GET_DIR USING V_DIR
V_MASK
CHANGING IT_DIR_LIST.

*-- Remove the wildcard to get the file name from the list of files
REPLACE ALL OCCURRENCES OF c_star IN V_MASK WITH space.

SORT IT_DIR_LIST BY NAME.

LOOP AT IT_DIR_LIST INTO WA_DIR_LIST WHERE NAME CS V_MASK.
V_FILE_NAME = WA_DIR_LIST-NAME.
EXIT.
ENDLOOP.

CONCATENATE C_INMAIN_FILE_PATH
V_FILE_NAME INTO V_MFILE.
CONCATENATE C_INMAIN_FILE_BPATH
V_FILE_NAME INTO V_BFILE.

V_COMMAND = C_FILE_MOVE_CMD.
CONCATENATE V_MFILE V_BFILE INTO V_PARAMETER SEPARATED BY SPACE.

*Move file from main folder to backup folder
PERFORM CHNG_FILE USING V_COMMAND
V_PARAMETER
CHANGING V_STATUS
V_EXITCODE
IT_RESULTS.

*Raise the event
CALL FUNCTION 'BP_EVENT_RAISE'
EXPORTING
eventid                = lv_event
eventparm              = lv_para
target_instance        = lv_inst
EXCEPTIONS
bad_eventid            = 1
eventid_does_not_exist = 2
eventid_missing        = 3
raise_failed           = 4
OTHERS                 = 5.
IF sy-subrc <> 0.
MESSAGE s000(z1) WITH 'Event does not exist' DISPLAY LIKE 'E'.
ENDIF.

*----------------------------------------------------------------------*
FORM GET_DIR  USING    IM_DIR  TYPE EPSF-EPSDIRNAM
IM_MASK TYPE EPSF-EPSFILNAM
CHANGING CH_IT_DIR_LIST TYPE TT_DIR_LIST.

CALL FUNCTION 'Z_GET_FILE_NAME_FOR_DIRECTORI'
EXPORTING
DIR_NAME               = IM_DIR
FILE_MASK              = IM_MASK
TABLES
DIR_LIST               = CH_IT_DIR_LIST
EXCEPTIONS
INVALID_EPS_SUBDIR     = 1
SAPGPARAM_FAILED       = 2
BUILD_DIRECTORY_FAILED = 3
NO_AUTHORIZATION       = 4
READ_DIRECTORY_FAILED  = 5
TOO_MANY_READ_ERRORS   = 6
EMPTY_DIRECTORY_LIST   = 7
OTHERS                 = 8.
IF SY-SUBRC NE 0 .
MESSAGE E001(Z1).
ENDIF.

ENDFORM.                    " GET_DIR

*&---------------------------------------------------------------------*
*&      FORM  CHNG_FILE

*&---------------------------------------------------------------------*
FORM CHNG_FILE  USING    IM_COMMAND   TYPE SXPGCOLIST-NAME
IM_PARAMETER TYPE SXPGCOLIST-PARAMETERS
CHANGING CH_STATUS    TYPE EXTCMDEXEX-STATUS
CH_EXITCODE  TYPE EXTCMDEXEX-EXITCODE
CH_IT_RESULTS TYPE TT_RESULTS.

CALL FUNCTION 'SXPG_CALL_SYSTEM'
EXPORTING
COMMANDNAME                = IM_COMMAND
ADDITIONAL_PARAMETERS      = IM_PARAMETER
IMPORTING
STATUS                     = CH_STATUS
EXITCODE                   = CH_EXITCODE
TABLES
EXEC_PROTOCOL              = CH_IT_RESULTS
EXCEPTIONS
NO_PERMISSION              = 1
COMMAND_NOT_FOUND          = 2
PARAMETERS_TOO_LONG        = 3
SECURITY_RISK              = 4
WRONG_CHECK_CALL_INTERFACE = 5
PROGRAM_START_ERROR        = 6
PROGRAM_TERMINATION_ERROR  = 7
X_ERROR                    = 8
PARAMETER_EXPECTED         = 9
TOO_MANY_PARAMETERS        = 10
ILLEGAL_COMMAND            = 11
OTHERS                     = 12.
IF SY-SUBRC <> 0.
MESSAGE E002(Z1).
ENDIF.

ENDFORM. 

Process Chain

Create an event and event triggered triggered process chain as follows.

Execution Process

Just trigger the process chain by executing the event which is defined in the start variant of the process chain. It will automatically take the first file in the main folder and process it till data target and moves to the backup folder and repeats until no more files exist in the folder.

Before Execution:

Main Folder

Backup folder

After Execution:

Main Folder

Backup Folder

Advantages

• Reduces the manual effort when we have huge no of files to load

Assumptions/Limitations

• All the flat files data is already validated. We can also include a new data validation step just before infopackage execution.

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

5. We select the required time characteristic using the button as shown below(for example Cal. Year /month).

 

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.

Requirement:

Delta for pricing tables like A004, A005, A006, A581 etc. In the pricing tables there are two date fields DATAB and DATBI. When a new record for condition record is created the record has date for the validity date for that condition record. The condition record when first created has the end date (DATBI) as 31/12/9999 and the start date can be anything. When the condition record validity is define the DATBI date is updated from 31/12/9999 to the date till which the date is valid and a new condition record is created with a new valid from date (DATAB i.e last DATBI+1 date)  and the valid to date DATBI is 31/12/9999. Now the delta for these condition record tables is of two types delta based on DATAB and DATBI both needs to be captured.

Problem:

No field to mark the change records.

Solution:

There are two date fields DATAB (from date) and DATBI (to date) for condition records.

Based on the changes based on these fields delta needs to be loaded.

We have created two Full IP’s  (one to capture change w.r.t DATAB and the other w.r.t DATBI).

Written an ABAP Routine in IP which will fetch the data from the range when the last record was loaded till sy-datum w.r.t DATAB and DATBI accordingly.

Pre-requisite:

Create a table entry for variable which will store the date of last load w.r.t DATAB (high) and DATBI (low).

ABAP routine w.r.t DATAB.

TABLES: TVARVC.
TYPES: BEGINOF y_tvarvc,
name LIKE tvarvc-name,
low  LIKE tvarvc-low,
high LIKE tvarvc-high,
ENDOF y_tvarvc.

DATA: e_l_itab TYPE y_tvarvc.

CONSTANTS: c_ds_nm(10) typecvalue'DS_A581_F5'.


data: l_idx like sy-tabix.


readtable l_t_range withkey
fieldname = 'DATAB'.
l_idx = sy-tabix.
*....

* clear work area
CLEAR e_l_itab.

selectSINGLE low
high
from tvarvc into CORRESPONDING FIELDSOF e_l_itab
where name = c_ds_nm.

if e_l_itab-high ISINITIALand e_l_itab-low ISINITIAL.
* when doing full load for the first time (no range defined)

CLEAR: L_T_RANGE.
l_t_range-option = 'EQ'.
l_t_range-sign   = 'I'.


*when doing delta load after first full load (range defined from last
*loaded delta to sy-datum)
elseif e_l_itab-high ISINITIAL.
l_t_range-HIGH   = sy-datum.
l_t_range-low    = e_l_itab-low.
l_t_range-option = 'BT'.
l_t_range-sign   = 'I'.

else.
*when doing delta load after first full load (range defined from last
*loaded delta to sy-datum)

l_t_range-HIGH   = sy-datum.
l_t_range-low    = e_l_itab-high.
l_t_range-option = 'BT'.
l_t_range-sign   = 'I'.

endif.

modify l_t_range index l_idx.



p_subrc = 0.
* clear work area
CLEAR e_l_itab.

ABAP routine w.r.t DATBI.

TABLES: TVARVC.
TYPES: BEGINOF y_tvarvc,
name LIKE tvarvc-name,
low  LIKE tvarvc-low,
high LIKE tvarvc-high,
ENDOF y_tvarvc.

DATA: e_l_itab TYPE y_tvarvc.

CONSTANTS: c_ds_nm(10) typecvalue'DS_A581_F5'.


data: l_idx like sy-tabix.


readtable l_t_range withkey
fieldname = 'DATBI'.
l_idx = sy-tabix.
*....

* clear work area
CLEAR e_l_itab.

selectSINGLE low
high
from tvarvc into CORRESPONDING FIELDSOF e_l_itab
where name = c_ds_nm.

if e_l_itab-high ISINITIALand e_l_itab-low ISINITIAL.
* when doing full load for the first time (no range defined).
CLEAR:   l_t_range.
l_t_range-option = 'EQ'.
l_t_range-sign   = 'I'.

*when doing delta load after first full load (range defined from last
*loaded delta to sy-datum)
elseif e_l_itab-low ISINITIALAND e_l_itab-high isnotINITIAL.
l_t_range-HIGH   = sy-datum.
l_t_range-low    = e_l_itab-high.
l_t_range-option = 'BT'.
l_t_range-sign   = 'I'.
else.
*when doing delta load after first full load (range defined from last
*loaded delta to sy-datum)

l_t_range-HIGH   = sy-datum.
l_t_range-low    = e_l_itab-low.
l_t_range-option = 'BT'.
l_t_range-sign   = 'I'.

endif.

modify l_t_range index l_idx.



p_subrc = 0.
* clear work area
CLEAR e_l_itab.

……

Please find the above code which you need to add in IP’s. This code will check if the data is been loaded for the first time(the variant has a blank value if we are loading the data for the first time).

• It will check the condition if it is been loaded before this so the date which will maintain the latest dates for change where the variable low value is for DATBI and high is for DATAB. If it is initial then it will do a full load and the last load date will get updated in the tvarvc table for the corresponding variable for eg.DS_A581_F5.

• If the data load is already done then only the data which is present in the range from last load and todays system date will be fetched and the variable value date will be updated (DS_A581_F5) value to today’s system date when the data load is done.

Below is the program to update the TVARVC table entries for variables.

Program to update variable values in TVARVC Table.

REPORT ZT_TAVRVC_VAR_UPDT.

PARAMETERS: p_varnm(10) typec OBLIGATORY,
p_delta(5)  typec OBLIGATORY.

CONSTANTS: c_datab(5) typecvalue'DATAB',
c_datbi(5) typecvalue'DATBI'.

If p_delta EQ c_datbi.

update tvarvc
set low = sy-datum
where name = p_varnm.

else.

update tvarvc
set high = sy-datum
where name = p_varnm.

endif.

We have a kept this program separate as it should update TVARVC variable entry only if the IP runs successfully.

The Flow for data loading in process chain is as follow:

(unable to upload the image...)

A BW Workspace is a dedicated area in a BW system where new models can be created based on central BW and local data (e.g. flat files). Workspaces can be maintained and controlled by IT and used by local departments to react quickly to new and changing requirements. Workspaces can bridge the gap between central governance requirements and local flexibility needs.

SAP BW Workspaces are available with SAP BW 7.3 SP 5:

• With SAP BW Accelerator 7.2 or
• With SAP HANA 1.0 running as a database for SAP BW 7.3 SP 5

The following article series appeals to different user types. This will be mentioned in the summary of each article.

As a first introduction please watch the video BW Workspaces Demo Video(approx.11 minutes).

For real life customer scenarios please read the article BW Workspaces - Use Cases.

1. Introduction and Standard Practices

• What is a BW Workspace?
• What is a CompositeProvider?
• How can Central Providers and Local Providers be easily combined in a new data model?
• How can I quickly familiarize the BW Workspaces?

2. Tips and Tricks for the Advanced Scenario

• How can a Reference Query be used?
• What are specifics concerning the upload of a file to a Local Provider?
• Why does the new data model not deliver any results?
• What are Specifics Concerning the Creation of New Master Data?
• What are Specifics Concerning the Authorizations of a CompositeProvider?
• How can restricted and calculated key figures, defined on a Central Provider, be reused for the CompositeProvider?

3. Best Practices and Recommendations

• How can data be cleansed during flat file upload?
• Is there any help in finding the correct field links/join conditions during modeling?
• How could a Query-EndToEnd scenario look alike?
• How can BW Workspaces be monitored and administered?

Online Documentation

• BW Workspaces
• BW Workspaces Configuration
• BW Workspaces Authorizations

In this area the available SAP Business Warehouse How-to-Guides (HTG) from various release are linked for convienience.

The latest information you will find on the  Business Warehouse enabeled by SAP HANA HTGs. For generell information about How-to-Guides and a list of SAP NetWeaver HTGs visit the SAP How to Guides page.

For additional topics don't miss to read the SAP First Guidance Collection for SAP BW powered by SAP HANA

How-To Guides by Business Warehouse Release

• Business Warehouse powered by SAP HANA

• SAP Business Warehouse  7.0

• SAP Business WArehouse 3.5

HI All,

Process of Creating Data Source in APO: -

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

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

II.Then Administration screen will come as below

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

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

IV. Then below screen will come

Here select Generate Data Source option.

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

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

VII. Settings will do as per below.

No Extraction of Data Records Without Key Fig Value:-

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

VIII. Block Size For BW Transfer:-

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

IX. Parallel Processing Profile:-

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

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

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

In this select fields which you want.

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

XIII. Then below window will come.

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

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

XIV. Then SNP data extraction window will appear.

In this click on Replicate Data Source option.

XV. Then below window will appear.

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

XVI. Transport data source.

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

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

Regards,

Mithun

Exploring InfoSet

InfoSets are logical InfoProviders that logically join data and provide this data for BI queries. This can be created based on InfoCube, DSO and Master Data InfoObject.  All the BEx and OLAP services are available (authorizations, texts, variables, hierarchies, calculated key figures) except navigational attributes of InfoSet characteristics.  The base concept behind InfoSet is join condition wherein data from different InfoProviders are collected at run time and produced in a single row.

When to use InfoSet:

·         To join required data from basic InfoProviders

·         To allow BEx Reporting on a DataStore object without turning the BEx Reporting indicator on

·         To evaluate time dependencies (for example, join time dependent master data InfoObjects)

·         To be able to create self joins and left outer joins

·         To  be able to create Antijoin (Functionality provided in version 731)

Join concepts:

·         Inner join: A record can only be in the selected result set if there are entries in both joined tables

·         Left outer join: If there is no corresponding record in the right table, the record is part of the result set (fields belonging to the right table have initial values)

·         Antijoin: Only those results are displayed which are present in other InfoProvider.

·         Temporal join: A join is called temporal if at least one member is time-dependent.

·         Self join: The same object is joined together

I have explained below the joins available in version 731. In the following example, I have taken an InfoCube and a DSO to create an InfoSet.

InfoCube contains Employee Number, Name of Employee and Salary of Employee. The data in InfoCube is as follows:

DSO contains Employee Number, Name of Employee and Age of Employee. The data in DSO is as follows:

Steps to create an InfoSet:

1.    1.  Right click on InfoArea. Select ‘Create InfoSet’.

1.   2.   Enter the required entries.  Select the InfoProvider to start with. Press ENTER. Here we have selected InfoCube as first InfoProvider for InfoSet.

1.  3.    We get the following screen. Here we can decide to choose the fields that have to be included in InfoSet. We have included all fields of InfoCube for InfoSet.

1.   4.   Now we have to choose the second InfoProvider for InfoSet.  Search for the required DSO.

1.  5.    After selecting the DSO, select only the required fields from DSO and connect InfoCube and DSO based on Employee Number. Connect both with inner join.

1.   6.   Check, Save and Activate InfoSet. Now check data of InfoSet. We get the following result set:

Since the above created InfoSet is having Inner join, it contains the record only for those employee number (Common field) which are present in InfoCube and DSO both.

InfoSet with Left Outer Join:

1.       Now we edit the InfoSet and change the join type to ‘Left Outer Join’ as given below:

2.       Select Left Outer Join. Check, Save and Activate InfoSet. Now check the data. We get the following result set:

Since it is Left Outer join, so all the data from left entity i.e. InfoCube is displayed here.  Employee Number 4 is present in cube, so it's salary is displayed. Since Age is coming from DSO and employee number 4 is not present in DSO, so, Age is not displayed.

InfoSet with Antijoin:

Case 1: Antijoin applied at DSO

1.   1.   Now we edit the InfoSet and change the join type to ‘Antijoin’ at DSO side as given below:

1.    

1.  2.    After selecting join type as Antijoin at DSO side, all the fields at DSO side become inactive as shown below:

1.   3.   Check, Save and Activate InfoSet. Now check data of InfoSet. We get the following result set:

Important point to note here is that only those records are displayed which are present only InfoCube.

Case 2: Antijoin applied at InfoCube

1.    1.  Now we edit the InfoSet and change the join type to ‘Antijoin’ at InfoCube side as given below:

1. 

1.   2.   After selecting join type as Antijoin at DSO side, all the fields at DSO side become inactive as shown below:

1.   3.   Further we have an option to select unchecked fields of DSO. We select all fields here. Now activate InfoSet and display data. We find following Result set.

We find that only those records are displayed which are present only in DSO.

Order of InfoProviders matters in InfoSet in case of Left Outer Join:

If we create an InfoSet starting with DSO and connecting to InfoCube using inner join or Antijoin, then results are similar to the above scenario. But if we use join type as ‘Left Outer Join’ then we counter some different result. I am going to explain this scenario below:

1.   1.  Create an another InfoSet taking same InfoCube and DSO but starting with DSO, and join type is left outer join, we get below screen.

Our expected output would be like below:

1.    2.    Check, Save and Activate InfoSet. Now check data of InfoSet.

We expect the above result because employee number 1, 2 and 3 are common in InfoCube and DSO both, and employee number 5 is present in DSO (Left entity).

But we get the following result set:

Here we find the results only from InfoCube. Whichever fields are selected in InfoSet design from InfoCube, those get displayed. No data from DSO is displayed.

1.    3.  Select all fields of InfoCube as shown below:

1.   4.   Check, Save and Activate InfoSet. Now check data of InfoSet.

Reason for this is left outer join cannot be applied at InfoCube side. At InfoCube side, we can apply either inner join or Antijoin.

Important points to remember:

           1. If we want to apply Antijoin on an InfoProvider, second InfoProvider must have Inner join.

           2. At least one InfoProvider must have Inner join.

                 3. At InfoCube side, left outer join cannot be applied.

                 4. We should avoid taking many InfoProviders in a single InfoSet.

                 5. We should avoid Left outer type as it degrades the performance.

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

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

References LIVE - SAP BW on HANA, EPM suite 10.0, MDM and BI 4.0 @ Shell, 3rd June 2014

Shell is going to present their experience of SAP BW on HANA, EPM suite 10.0, MDM and BI 4.0 on 3rd June via a ReferencesLive webinar.
WHEN: 3rd June 2014
15:30 – 16:30 (CET) 
LANGUAGE:  English  
Discover how Shell Achieved faster integrated Financial Close, Consolidation, and Enhanced Cross-Divisional Financial and Management Reporting.

Shell is one of the largest BI/BW customers live today who will share their experience about their implementation of the EPM suite together with BI4, supported BW on HANA during this call. The EPM suite relates to Shell’s Top Quartile Finance MI (Insight to Win) program where components are implemented such as BOFC, BPC Netweaver, FIM, and EPM Add-in. BW on HANA is a key component of Shell’s Group Enterprise Data warehouse supporting Shell’s longer term MI strategy. In this call you can listen to the main benefits of this implementation like Real-time data replication capabilities using SLT, improved data volume handling with less solution optimization. SAP BI4  is established as the main MI reporting platform at Shell with multiple tools being deployed such as Webi, Crystal, Analysis for Office and OLAP, Lumira, and Design Studio. In summary, there are many reasons to join this call to obtain key insights and best practices.
ABOUT REFERENCESLIVE
ReferencesLive calls are one-to-few reference calls with up to 20 participating companies. The host company provides a 30-minute overview of their successful SAP project, and then the phone lines are opened for each participating company to ask questions. Please kontact yout local account executive or assigned sales person to register.

Workshop - Migrate your BW System database to SAP HANA

Don't miss our new offering WDEUMH - Workshop - Migration SAP BW to SAP HANA!

Roland Kramer will be your host for that 4 day workshop. The participants will learn to migration an existing SAP BW System to SAP BW powered by SAPHANA using the BW-PCA Method and the database migration option (DMO).

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

See also  the Recently Featured Content for SAP BW..

Applies to

SAP BI 7.0 version and higher

For more information, for more information, visit the EDW homepage.

Summary

This document will provide information regarding implementing multi-dimensional authorization concept in BW reports. Also it contains the information regarding analysis Authorization and customer exit variable etc

Author: Arvind Tekra     

Company: Infosys Technologies.

Created on: 4^th June 2014

Author Bio

Arvind Tekra has been working in various technologies in SAP BI. He is mainly responsible for implementing SAP BI/BO projects and has worked extensively on SAP BI Modeling.

Introduction

Whenever the analysis authorization of a user is combined, the authorization variable implemented in the report is not able to restrict the data at the appropriate combination which might lead to user getting message of “No appropriate authorization” when executing the report. This is explained better with the scenario explained below:

Objective

In the below example is a requirement from the user that the user should be able to see all the Sales Org for a particular Sales Division (as part of the global team) and for a specific Sales Org he should see all Sales Divisions (as per his role of a regional manager).  As per the requirement two analysis authorization objects were created and assigned to the user. The analysis authorizations would make sure at the database level that the users see the appropriate data as per the user’s access, however the BW query is not able to read it appropriately and it throws an error message to the user.

Both the analysis authorization are assigned to the TESTUSER1.

A simple BW query is built for the demo purpose, it has authorization variables in the selection screen.

If we execute this report in Tcode-RSRT with a user with all access we get the below data.

Selection Screen:

Output:

From the above output we can see the  combination for which TESTUSER1 is authorized for has data available in the report.

If we now run the report with TESTUSER1:

Selection screen:

The values are not populated as for individual charactersitics, it reads as * access from the authorizations.

If we execute the report, then we get the error message that no authorization is there as he only has access for combinations of data and not all the data.

The above example takes into consideration only two characteristics and in other business scenario we may have scenarios where the access can be defined on combination of 3-4 characteristics.

Solution

The solution can be divided into two parts:

·         Automatic generation of analysis authorization for the user for the desired combination.

·         Introduction of a concatenated object which is a combination of Sales Org/Division, this object can be used to restrict the output of the BW report as per the users authorization.

The following design can be implemented for the solution. The user access matrix can be maintained in an ECC table by the business itself. The business team can enter the user and the combination matrix on which the users should have access.

ECC table:

In ECC a customized extractor (data source) can be built which fetches this information and passes it to BW system. The below data model can be built to fetch the user access matrix in BW.

In DSO1 we need to add an additional object which is concatenation of the two objects with a differentiator in between. The differentiator will help in distinguishing the values of the Sales Org/ Sales Division. In the below example we have used “/” as the differentiator, the differentiator can be any special symbol which is allowed in the BW and is not used in the value of the characteristics used for the combination. The concatenated object can be populated in the DSO by writing this logic in the transformation.

DSO1 sample entries:

The concatenated object is also added to the cube and the data is populated by defining the logic in transformation same as the DSO1 transformation.

DSO entries:

Cube entries:

To fully automate this solution the following design can be used.

Copy DSO’s for authorization can be created

DSO2: copy of Authorization data (values) (0TCA_DS01)

DSO3: copy of Description texts for authorizations (0TCA_DS03)

The authorization DSO’s are used to generate the authorizations on Sales Org and Sales Division

1. In the transformation from DSO1 (ZUSER_1) à DSO2 (Z_DS01) the below expert routine can be used, this would convert the entries into the format of authorization generation.

Data: WA_SOURCE_PACKAGE LIKE LINE OF SOURCE_PACKAGE.

    SORT SOURCE_PACKAGE BY TCTUSERNM.

    LOOP AT SOURCE_PACKAGE INTO WA_SOURCE_PACKAGE.

      RESULT_FIELDS-tctusernm = WA_SOURCE_PACKAGE-TCTUSERNM.

      RESULT_FIELDS-tctobjvers = 'A'.

      RESULT_FIELDS-tctoption = 'EQ'.

      RESULT_FIELDS-tctsign   = 'I'.

      RESULT_FIELDS-tctadfrom = '19000101'.

      RESULT_FIELDS-tctadto   = '99991231'.

      RESULT_FIELDS-tctauth = 'SALESDIV'.
      RESULT_FIELDS-tctiobjnm = '0TCAACTVT'.
      RESULT_FIELDS-tctlow = '03'.
      APPEND RESULT_FIELDS TO RESULT_PACKAGE.

      RESULT_FIELDS-tctiobjnm = '0TCAVALID'.
      RESULT_FIELDS-tctlow = '*'.
      APPEND RESULT_FIELDS TO RESULT_PACKAGE.
      RESULT_FIELDS-tctiobjnm = '0TCAIPROV'.
      RESULT_FIELDS-tctlow = 'ZSALES_M1'.
      "Mention the cube on which the report is built
      APPEND RESULT_FIELDS TO RESULT_PACKAGE.
"This name can be changed as per the description you require for the aut"horization
      RESULT_FIELDS-tctiobjnm = 'ZSA_DIV'."Sales Division object
      RESULT_FIELDS-tctlow = WA_SOURCE_PACKAGE-/BIC/ZSA_DIV.
      APPEND RESULT_FIELDS TO RESULT_PACKAGE.

          CLEAR RESULT_FIELDS.
      ENDLOOP.

The entries of DSO after loading.

The text for the TCTAUTH (authorizations) defined above can be loaded in copy of DSO 0TCA_DS03, this text appears in the user profile for the authorization. After loading the DSO1 and DSO3 execute the report “RSEC_GENERATE_AUTHORIZATIONS” with the DSO’s and generate the profile.

Screenshot of user profile in RSECADMIN:

The loading and generation of the analysis authorization can be done using a Process chain.

The BW query is enhanced and the concatenated object is added in the filter selection, the variable used is of type “customer exit”. In the customer exit code the DSO ZUSER_1 can be read for the allowed concatenated values. This way the overall report would be restricted to the allowed values only and the report will not throw any error message for authorization.

Sample code for the exit.

DATA:   l_s_range TYPE rsr_s_rangesid,

             lv_user TYPE sy-uname,

            lv_zconcobj TYPE STRING,

             L_S_VAR_RANGE LIKE LINE OF I_T_VAr_RANGE.

Data: I_ZUSER_1 type STANDARD TABLE OF /BIC/AZUSER_100,"INTERNAL TABLE TO DETERMINE AUTH VALUES

         WA_ZUSER_1 like line of I_ZUSER_1.

CASE I_STEP.

        WHEN  '01'. "BEFORE USER INPUT

************FUNCTION TO DETERMINE THE USER NAME********

          CALL FUNCTION 'RSEC_GET_USERNAME'
            IMPORTING

                e_username = lv_user.

*******************************************************
          "SELECT FROM ZUSER_1 FOR USER
          SELECT *
          FROM /BIC/AZUSER_100
          INTO TABLE I_ZUSER_1
          WHERE TCTUSERNM = LV_USER.

          if sy-subrc eq '0'. ”AUTH VALUES ARE MAINTAINED IN MATRIX TABLE
            "LOOP AT THE INTERNAL TABLE
            LOOP AT I_ZUSER_1 INTO WA_ZUSER_1.

              l_s_range-SIGN = 'I'.
              L_S_RANGE-OPT = 'CP'.
              L_s_RANGE-LOW = WA_ZUSER_1-/BIC/ZSA_ORDI.
              APPEND l_s_range TO e_t_range.
              CLEAR L_S_RANGE.

              CLEAR WA_ZUSER_1.
            ENDLOOP.

          else. ”STOP THE PROCESSING AND DISPLAY MESSAGE
            CALL FUNCTION 'RRMS_MESSAGE_HANDLING'
              EXPORTING
                I_CLASS  = 'RSBBS'
                I_TYPE   = 'E'
                I_NUMBER = '000'
                I_MSGV1  = 'No Authorization'
              EXCEPTIONS
                DUMMY    = 1
                OTHERS   = 2.
            raise no_processing.

          endif.

        WHEN '02'. "AFTER USER INPUT

        WHEN '03'.”FOR CHECKING EXCEPTIONS

      ENDCASE.

Now when the query is executed with the test user, the variable restricts the access

Note: This solution does not uses concatenated object as authorization relevant as the values which can be passed into the authorization is restricted, we cannot maintain value wildcard entry (*) with pattern */10. This entry would generate authorization with ‘*’ access only. More details about the valid interval and patterns for authorization is given in the below mentioned SAP note.

1053989 - Intervals and Patterns [(*),(+)] in Analysis Authorizations

The authorizations are generated individually i.e. Sales org independently and Sales Division independently so that it does not give error message in the BW report when the report checks for * access. With this design the Customer exit variable becomes mandatory with all the queries on top of that MultiCube, if the variable is not used then the users might get access to data they are not authorized for. The analysis authorization generated individually would make sense in scenarios where the user not authorized for * access. An example is shown below.

In the above scenario the authorizations would be generated for Sales Org: 1000,2000 and Sales Division 10,20 and these values would appear in the selection screen in authorization variable.

This solution is only 100% correct if the customer exit on concatenated object is used in all the queries.

Related Content

Combining Authorizations

Generation of Analysis Authorizations

SAP Note 1053989 - Intervals and Patterns [(*),(+)] in Analysis Authorizations

Variable Customer exit

Authorization variable

Disclaimer and Liability Notice

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.

SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk.

SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document.

Communication Setting between BW and R/3

Step 1: Define Logical System in R/3

Step 2: Assigning Logical System to Client

Step 3: Setting Up an RFC Destination

Step 4: Distributing Data Model

Message Types Involved in Process of Data Loading

Step 5: Generating Partner Profile

Step 6: Maintaining Message types in T-Code WE20

Creating Source System (SALE): This step creates source systems which are to be connected.

1. 1. Assigning Source System to Client (SALE): This step gives a logical name to a SAP Client from which the communication is to be established.
2. 2. Setting up RFC Destination (SM59): This step is required to establish remote connection to the partner with which Source system is trying to communicate. Here one has to maintain the logon and IP details of the target system.
3. 3. Distributing Data Model (BD64): A distribution model is used to model a distributed environment in which you specify messages exchanged between sending and receiving systems. Here one has to define the message protocols with which the two systems will communicate.
4. 4. Generating Partner Profile (BD82): This process generates a partner profile for each system with which your system communicates. Outbound records are created in the partner profile for each outgoing message, and inbound records are created for each incoming message.

Note: If one distributes Data Model before generating partner profile then one has to redefine partner profile in other system also (repeat step in both system). In this document we are generating partner profile after Distribution of data model so as to demonstrate how to maintain inbound and outbound message types in WE20.

1. 5.Maintaining Message Types (WE20): This process is optional. Generally while generating partner profiles we automatically get the respective Outbound and Inbound messages, which can be checked in T-Code WE20. If the message types are not defined then one can manually do it by following this process.

Step 1: Define Logical System in R/3.

1. Log into R/3 and then go to transaction SALE. Here under IDoc Interface / Application Link Enabling (ALE)    Basic Settings    Logical Systems    Define logical system. Here one can define the source systems one wants to connect. Make entries for both R/3 and BW system.

T-Code: SALE

Defining the Logical Systems

Repeat the same steps in BW

Create ALEREMOTE User in both the clients with following profiles

The ALEREMOTE user needs the following authorization profiles:

* In the Business Information Warehouse:

S_BI-WHM_RFC (Business Information Warehouse: RFC users in the Warehouse)

* In the source system:

S_BI-WX_RFC (Business Information Warehouse: RFC users in extraction)

Define the RFC connections in SM59.Test the connections on the same..make sure you are connecting as the background user you created.

General checks in trouble shooting...
check table RSBASIDOC in SE16...on both the sides (R/3 and BW)
to mirror each other..and the entries are active in both the sides.

Step 3: Setting Up an RFC Destination.

create an RFC destination on the local system for each remote SAP system with which you want to communicate. In the RFC destination, you specify all the information necessary to log on to the remote system to execute functions remotely, including the host name, the user ID, the password, the client, the system number, and additional communication settings.

So after creating a new entry of type ABAP Connection (The ALE process uses type R/ 3 connections to communicate with a remote SAP system, and the EDI process uses type TCP/IP connections to communicate with the EDI subsystem), one is expected to fill in details in Technical tab. Fill the Target Host Id (this should be same as defined in SALE) and give System No. and IP Address of the target system or the Alias for the system as shown below:

Please repeat the same step in BI also but select source system as R/3 in SM59.

Step 4: Distributing Data Model:

You begin by clicking the Create Model View button on the main screen of transaction BD64.

Then add Message type

Having created the Distribution model, let’s distribute this model. This process will replicate a similar setting in BW side automatically.

Please note that Distribution of data model is not needed to be repeated in BW side as this step automatically replicates settings in BW.

1. Go to Edit   Model View   Distribute.

Next, one is taken to following screen where one can define the partner system id and the user that communicates.

After this Execute and wait for the system messages which inform whether partner profile was successfully created or not.

Hence the partner profile was successfully generated…

Now logon on to the BW system and go to T-Code BD64 and test the partner profile settings, whether they are correctly transmitted or not. We can execute it here (in BW) also and get our settings tested.

Step 6: Maintaining Message types in T-Code WE20:

  Again we need to follow this activity both in BW and R/3. When in R/3 systems WE20, then click on BW system id, and check whether Outbound and Inbound parameters are correctly filled if not then fill it manually as below

Depending on your client settings one can define different message types for eg:

Now test once again for Partner profile setting and we are ready to have data transfer between BW and R/3 (this can be done directly using T-Code BD82).

Now go to RSA1 in BI System

1. Click On Replicate As Well -à here BI will fetch the data from R3 and it takes 10 to 15 min time.

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

 

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.