experience sap bw data provisioning from sap and non-sap sources - exercise

SAP BW 7.40 DATA PROVISIONING FROM SAP AND NON-SAP SOURCES DMM360

Exercises/Solutions

DMM360

2

TABLE OF CONTENTS

1. Before you start ...................................................................................................................................... 3

2. 1 - Setup of Data Replication into SAP BW with SAP LT Replication Server ........................................ 4

2.1. Create an SLT configuration ............................................................................................................. 4

2.2. Create the Logical System in SAP BW ............................................................................................. 9

2.3. Prepare the View for Replication ....................................................................................................... 11

2.4. Create the Data Source in SAP BW .................................................................................................. 15

3. 2 - Create an advanced DataStore Object and load data ...................................................................... 19

3.1. Create an advanced DataStore Object for Actuals ........................................................................... 19

3.2. Create data flow and load actuals ..................................................................................................... 33

3.3. Create and load delta records ........................................................................................................... 41

4. 3a - Create an ADSO for History data and a CompositeProvider (Long Option) ................................... 44

4.1. Create a Advanced DataStore Object for historic data ..................................................................... 44

4.2. Create data flow and load history data .............................................................................................. 51

4.3. Create a CompositeProvider ............................................................................................................. 59

5. 3b - Create CompositeProvider to join with existing history ADSO (Short Option) ................................ 63

5.1. Create CompositeProvider ................................................................................................................ 63

5.2. Summary ........................................................................................................................................... 67

DMM360

3

1. BEFORE YOU START

In the Hands-on session DMM360 you have the opportunity to walk through an end-to-end process of loading data into SAP BW 7.40 completely based on new technologies. Exercise 1 & 2 are mandatory to complete after each other, Exercise 3 is split into two pieces: 3a as a long version and 3b as shorter version depending on your experience and speed during the exercise. Exercise 1: Setup of Data Replication into SAP BW with SAP LT Replication Server Estimated Duration: 20 minutes Exercise 2: Create an advanced DataStore Object and load data Estimated Duration: 35 minutes Exercise 3a: Create an ADSO for History data and a CompositeProvider Estimated Duration: 35 minutes OR Exercise 3b: Create a CompositeProvider to join with existing history ADSO Estimated Duration: 15 minutes

DMM360

4

2. 1 - SETUP OF DATA REPLICATION INTO SAP BW WITH SAP LT

REPLICATION SERVER

Overview

Estimated time: 20 minutes Objective In the following exercise you will learn how to create an SLT configuration for the Operational Data Provisioning scenario and how to prepare the subscription to the ODP with SAP Business Warehouse. You will assign a database view that combines data of two different tables to the leading table in the SLT system and prepare the replication of this table creating the DataSource the SAP BW system. (The replication of the table will be part of exercise 2.) Exercise Description

Create an SLT configuration

Create the logical System in SAP BW

Prepare a Database View for source tables for the replication

Create the DataSource in SAP BW

Roadmap for the exercise "Setup of Data Replication into SAP BW with SAP LT Replication Server"

2.1. Create an SLT configuration

Explanation Screenshot

1. Enter client, user and the password. Confirm your entry by pressing the Enter key.

DMM360

5


2. To create a new SLT configuration, go to the Configuration an Monitoring Dashboard.Enter transaction code LTR in the tcode field. Confirm your entry by pressing the Enter key.

3. If a login screen opens, enter your credentials and your password. In the Configuration and Monitoring Dashboard, select New to create a new configuration.

4. Enter the Configuration Name. As Description, enter ODP scenario.

Click Next .

DMM360

6


5. Select the RFC Destination HBD_SLT from the dropdown list. Check the checkbox for "Allow Multiple Usage". Click Next to proceed to step 3.

6. For the Target System, select the radio button fir RFC Connection. Again select the RFC Destination HBD_SLT. As scenario for the RFC communication, select "ODP replication scenario" from the dropdown list. As Queue Alias, enter xx. Click Next.

7. Enter 001 in the No. of Data Transfer Jobs box. Leave the Replication Options setting on Real Time. Click Next. 8. Click Next.

DMM360

7


9. Review your entries and create the configuration.

10. We now have to check if the BADI for ODP is activated. This is done in the LT Replication Server Cockpit. Enter LTRC in the tcode box. Confirm your entry by pressing the Enter key.

11. From the dropdown list of the Mass Transfer ID, select your new configuration xx. Note: The Mass Transfer ID counts the number of configurations in the system and is the identifier of your configuration.

12. Open the

tab .

DMM360

8


13. Double-clicking

runs the checking report and returns if the BAdI implementation is active.

DMM360

9

2.2. Create the Logical System in SAP BW


1. Open the Data Warehousing Workbench, transaction RSA1. 2. Open the Source Systems

structure. Click on with the right mouse button.

3. Right-click on the ODP-SLT Queue folder to create a new Source System.

4. Enter the Logical System name xx and the Source System Name xx. Click Continue.

DMM360

10


5. Make the following entries: on tab Technical Settings: Target host / instance. on tab Logon & Security: Check the Current User checkbox. 6. An RFC Destination with the Source System name is created. Click Save and navigate back.

7. Select the correct ODP context from the dropdown list (your xx). The system automatically creates an additional RFC connection HBDCLNT001 for the Real-time Data Acquisition from SLT system to BW system. Enter user and password.

8. Click Save settings .

9. In the next popup, click Now to update the generated content versions (you could also select Later).

10. You have created your new Logical System.

DMM360

11

2.3. Prepare the View for Replication


1. Open transaction se80. Select Package ZDCODE14. Open the Dictionary Objects -> Views folder. Select your View ZSO_V_xx. Look at the Table Join Conditions: we join the tables ZCUSTOMERSxx and ZSO_HEADERxx via the Field ID/CUSTOMERID.

2. On the View Flds tab, you see which fields are selected for the view. This can be a subset of the fields of the joined tables.

3. Right-click on the View entry to open the context menu of the view. Select Display Table Contents.

DMM360

12


4. Click Number of Entries to show the amount of data sets in the view.

5. The number of entries is displayed.

6. Click Execute to show the contents of the view.

DMM360

13


7. Go to transaction LTRS. 8. Select your Configuration xx (double-click).

9. Open the context menu of the

folder and choose Add Table.

10. Add the table ZSO_HEADERxx which is the leading table of your view.

DMM360

14


11. Add your view ZSO_V_xx as

Structure template

View for Initial Load

View for Replication Save your changes.

12. Click on with the right mouse button.

13. Click the Add Table menu item to execute it.

14. In the pop-up, add the ZSO_HEADERxx table.

DMM360

15


15. Select the entry 5 INDX CLUSTER with FULL TABLE SCAN as Reading Type. This type ie always used for views. Save your entry. Now the view is correctly assigned to the leading table and you can start the replication.

Summary You have completed the exercise! You are now able to:

Create an SLT configuration

Create the logical System in SAP BW

Prepare a Database View for source tables for the replication

Create the DataSource in SAP BW

2.4. Create the DataSource in SAP BW


1. In the Data Warehousing Workbench (RSA1), double-click on your logical system xx to open the DataSources display for the logical system.

DMM360

16


2. Click . 3. Right-click on the application component to open the context menu.

4. Click the Create DataSource... menu item.

DMM360

17


5. Enter your leading table ZSO_HEADERxx as Operational Data Provider and DataSource. For DataSource Data Type, select Transaction Data.

Click Create DataSource .

6. Enter a Long Description like ZSO_HEADERxx with View. Then go to the Extraction tab.

7. On the Extraction tab, check that the Delta Process is set to AIMD the ODP context is correct the right Operational Data Provider is selected.

Click .

8. Check the fields in the Proposal - all fields of the view should be visible, plus 2 fields containing ODP information.

Click Activate .

DMM360

18


9. Now the DataSource is active and executable.

DMM360

19

3. 2 - CREATE AN ADVANCED DATASTORE OBJECT AND LOAD DATA

Overview

Estimated time: 35 minutes Objective In the following exercise you will create a new advanced DataStore Object, which is the new data persistence object in SAP BW 7.40 powered by SAP HANA. This will be a new modelling experience since it is eclipse based. In addition you'll load actual data out of the ODQ which is filled by SLT. After creating delta records you'll fetch the changes. Exercise Description

3.1. Create an advanced DataStore Object for Actuals


1. Enter xx, in the box. 2. Enter password. Confirm your entry by pressing the Enter key.

DMM360

20


3. Enter RSA1 as transaction. Confirm your entry by pressing the Enter key.

4. Search for the common session

InfoArea: Click .

5. Enter ZDCODE_2014 in the text box to search for the predefined InfoArea Confirm your entry by pressing the Enter key.

6. Expand the InfoArea.

7. Click on the InfoArea

with the right mouse button to call the context menu to create your own InfoArea by selecting "Create InfoArea".

8. Enter XX as technical name for your InfoArea. 9. Enter Group XX in the

DMM360

21


10. Click Continue .

11. Click on the Project Explorer (in an empty space) with the right mouse to start a new BW modelling project.

Your InfoArea is created and you are done for now in the BW ABAP perspective. Since we are bringing more modelling steps into SAP HANA Studio we will switch to the eclipse based BW modelling to create the new advanced DataStore Object. Call HANA Studio via the provided path/folder and open the BWMT (BW modelling Tool) perspective.

12. The Overview page of the HANA Studio opens.

DMM360

22


13. To start BW Modeling, click Open Modeler. 14. The Welcome page closes.

15. The HANA Administration Console contains several Perspectives. Click Open

Perspective .

16. Select the entry BW Modeling and click OK.

DMM360

23


17. The BW Modeling Perspective is displayed and you see the Project Explorer.

18. Click the Project...

menu item to create your own project.

DMM360

24


19. Click &Next . You can also press Alt+n.

20. Click Browse... . to search for a BW connection. You can also press Alt+o. Note: You are now connecting to a standard BW on HANA system. These are the connections maintained in the SAP Logon, that means you need a BW User to connect of course.

DMM360

25


21. Select the entry [lt5086.wdf.sap.corp]

and press "Ok".

22. Click &Next .

DMM360

26


23. Enter in Client, User and Password box. Confirm your entry by pressing the Enter key.

24. Click to expand the object tree.

DMM360

27


25. Click on the InfoProvider tree.

26. Search for our common InfoArea ZDCODE_2014 and expand it by clicking . Note: You are now seeing the BW defined InfoAreas as folders with all the corresponding object underneath.

27. Click .

28. Search your InfoArea and click on it, guide example with the right mouse button to call the context menu.

29. Choose via New: Advanced DataStore Object

to create an ADSO.

DMM360

28


30. Enter ZADSAXX as Name .

31. Enter SalesOrder Actuals XX as the Description .

32. Click Finish .

DMM360

29


33. The Overview tab is showing you different options and settings how the Advanced DataStoreObject can be designed. Please leave them by default and click on the

Details tab to maintain the fields of the ADSO.

34. Click Add

Field .

35. Enter SO_ID as Name box. Leave data Type CHAR 10 as shown by default.

36. Click Add

Field .

DMM360

30


37. Enter QUARTER as the Name .

38. Enter 2 characters as Length. 39. Click Add

Field .

40. Enter SO_YEAR as Name.Leave CHAR 10 as data type. 41. Click Add

InfoObject .

42. Enter InfoObject 0AMOUNT as search term

.

43. Click OK .

44. Click Add

InfoObject .

DMM360

31


45. Search for the InfoObject [ZSAREP] Sales Representative

and select it.

Please go ahead and maintain the following further field definitions (FINANCIALCOD to ORDERDATE) like shown in the screenshot.

46. Click Key

Components to define the keys of the DataStore Object

47. Expand

to see the field and InfoObject definitions.

DMM360

32


48. Mark SO_ID, QUARTER and SO_YEAR as keys and click Add to

Keys .

49. Click OK .

50. Click Activate BW Object .

DMM360

33

3.2. Create data flow and load actuals


1. Switch back to BW ABAP and RSA1 in the InfoProvider Area and search for your InfoArea. Expand your InfoArea and find your Advanced DataStore Objected created recently. Click on with the right mouse button and choose "Create Transformation". (If the session was still open, please refresh the InfoProvider tree)

2. Select the source object type with the drop down box:

.

3. Select DataSource

4. Enter ZSO_HEADER99 as the .

5. Enter xx as the .

DMM360

34


6. Press Create Transformation .

7. Check the proposed mappings which should be fine and map the open source fields to the target structure. Start with Source field SALESREPRESE and map it with ZSAREP of the DSO target structure by drag and drop.

8. Map with SURENAME of the DSO target structure by drag and drop.

9. Map with GIVENNAME.

10. Maintain a transformation rule (constant) for currency by clicking on

with the right mouse button.

DMM360

35


11. Choose Rule Details

. You can also press r.

12. Expand the drop down box "Rule Type" .

13. Select the entry Constant

DMM360

36


14. Enter EUR as .

15. Click .

16. Click Activate .


18. Go back.

19. Click on "Data Transfer Process" with the right mouse button.

DMM360

37


20. Create Data Transfer Process...

21. Enter ZSO_HEADERXX as

22. Enter XX in the box.


24. Click Activate Data Transfer

Process .

Your Data Transfer Process should now be activated and ready for "Delta" Extractions.

DMM360

38


25. Go to the tab .

26. Click to start data loading. Note: With this step you are loading data via ODP into BW. The persistency of ODP the ODQ (Operational Delta Queue) is in our scenario filled by SLT. With started the DTP the creation of all necessary SLT objects like triggers etc. is been done. Afterwards SLT will push an initial load into the ODQ and BW fetches the data from there. This could also be done in real-time via an scheduled job. In our scenario we will execute it manually.

27. Click and wait until the log indicates the success of the data loading. You can press the refresh button to update the view.

28. Click on with the right mouse button. Note: Please wait until "all lights are green", which means that data loading ended successfully.

DMM360

39


29. Click on Manage

.

30. Double-click on the grouping data which is an aggregated view of all loaded requests. Note: The next steps might differ from the UI perspective between this guide and your system. However the process and steps are similar. Please ask in case of any questions.

31. Mark your load request.


33. Click Refresh until the Status shows that the request is being activated.

DMM360

40


34. Click on with the right mouse button.

35. Click Display Data

. Verify the data is available and active for reporting by displaying it.

In case the data is active you should now receive some records. If the data wouldn't be active no data would be available. This is because the "Display data" selects the data from the "active table" of our DSO. This table is by design only filled by the activation process.

DMM360

41

3.3. Create and load delta records


1. Enter se38 in the transaction field. Confirm your entry by pressing the Enter key.

2. Enter ZDCODE_UPDATE_SIMULATOR as Program name.

3. Click Execute .

4. Click Execute .

DMM360

42


5. Click Continue .

6. Switch to transaction RSA1.

7. Expand

.

8. Expand your DTP

folder .

9. Double click on your DTP.

DMM360

43


10. Click on Execute to load the create delta records. Note: The delta records have been pushed via SLT in real-time to the ODQ. We have "just" fetch them from there. They will be available immediately. For this we could also create a RDA (real-time data acquisition process), but in this scenario we do it manually. The new ADSO allows us furthermore to schedule the DTP manually in a high frequency to achieve near-real time reporting. This was not possible in the past with the Standard DSO and the traditional request handling.


To work and create data models in eclipse via the BWMT

create a new advanced DataStore object

Explain how SAP BW work and interacts with SLT via the ODP framework

DMM360

44

4. 3A - CREATE AN ADSO FOR HISTORY DATA AND A

COMPOSITEPROVIDER (LONG OPTION)

Overview

Estimated time: 35 minutes Objective In addition to the actuals data you will create a second advanced DataStore Object and load history data via your own source system. Afterwards you'll combine the actuals ADSO with the history ADSO in a new CompositeProvider. Also the CompositeProvider with SAP BW 7.40 has been renewed, further optimized and introduced for eclipse based modelling. Exercise Description

4.1. Create a Advanced DataStore Object for historic data


DMM360

45


1. Click on DataStore Object

(Advanced) with the right mouse button.

2. Click New Advanced DataStore Object

to create a second ADSO.

3. Enter ZADSH99 as the Name .

DMM360

46


4. Enter SalesOrder History 99 as Description .

5. Click Finish .

Switch to tab "Details"

DMM360

47


Please maintain the fields and InfoObject definitions like shown in the screenshot. This is similar to the first ADSO and you can use your recently learned knowledge.

6. Click Key

Components .

DMM360

48


7. Expand the fields.

DMM360

49


8. Mark SO_ID, QUARTER, SO_YEAR and click Add to

Keys .

DMM360

50


9. Click OK .

10. Click Activate BW Object

(Ctrl+F3) .

DMM360

51

4.2. Create data flow and load history data


1. Call transaction RSA1.

2. Click .

3. Expand . 4. Double-click on

.

5. Click on XX with the right mouse button.

DMM360

52


6. Click the Create DataSource...

menu item to execute it. You can also press e.

7. Enter ZSO_HIST_99 in the box.

8. Click on the Drop Down Box of DataSource Data Type.

9. Select the entry Transaction Data

by clicking it.

10. Click Transfer .

DMM360

53


11. Click .

12. Enter ZSO_V_HIST in the

box. Confirm your entry by pressing the Enter key.

Click on the Proposal tab.

13. Take over the Prosopal by

clicking on the Tab .


DMM360

54


15. Click on on your created DataSource ZSO_HIST_XX with the right mouse button.

16. Click .

17. Select the entry DataStore Object (advanced)

by clicking it.

18. Enter ZADSHXX in the box.

19. Click Create Transformation .

DMM360

55


20. Drag and drop the following fields from source to target: SALESREPRESE - ZSAREP SURENAME - SURENAME GIVENNAME - GIVENAME And maintain as currency in the Target Transformation EUR (Context menu on currency -> Rule Details -> Rule Type "Constant" -> EUR) 21. Drop on .



24. Click on with the right mouse button and create a DataTransfer Process.

25. Click .

DMM360

56


26. Select the entry Datastore Object (advanced)

by clicking it.

27. Enter Zadsh99 in the box. Confirm your entry by pressing the Enter key.

28. Click .

29. Change the "Extraction Mode" by selecting the entry Full

30. Select the entry Directly from source system. PSA not used (for small amounts of data)

by clicking it.

31. Click Activate Data Transfer

Proces .

DMM360

57


32. Click .

33. Click .

34. Click .

35. Wait until all lights are green (refresh until this happens) and if the

load was successful click .

36. Click .

37. Expand the transformation flow

and click . (Or simply search for your ADSO) Click on your ADSO in the context menu and choose "Manage"

38. Click on with the right mouse button and choose "manage".

DMM360

58


39. Double-click on the grouping data.


DMM360

59

4.3. Create a CompositeProvider


1. Go to your InfoArea and click on it with the right mouse button.

2. Choose New - CompositeProvider

3. Enter ZCPXX in the Name.

4. Enter Sales Order Actuals & History in the Description.

DMM360

60


5. Click Finish .

6. Leave the BW related properties like Query Mode, Caching etc. by default and choose the

Scenario tab

7. Click to add the first InfoProvider for the Union.

DMM360

61


8. Search for your ADSO with Actuals: ZADSAXX

9. Select your ADSO

10. Add your ADSO with History data, ZADSH99 via search again.

DMM360

62


11. Click on the Union Node

. You will see the Source Structure containing both ADSO for creating a Target Structure of the Union.

12. Mark both of them and Drag and Drop them to the Target Structure. 13. Drop on .


(Ctrl+F3) .

15. Click Show Preview .


Create a source system and load data

To load data without using the PSA table in SAP BW 7.40

Create a CompositeProvider with SAP BW 7.40

DMM360

63

5. 3B - CREATE COMPOSITEPROVIDER TO JOIN WITH EXISTING

HISTORY ADSO (SHORT OPTION)

Overview

Estimated time: 15 minutes Objective You'll combine the actuals ADSO with the history ADSO in a new CompositeProvider. Also the CompositeProvider with SAP BW 7.40 has been renewed, further optimized and introduced for eclipse based modelling. Difference to Exercise 3a is that you'll reference on an existing ADSO with history data to save time.

5.1. Create CompositeProvider


1. Click on your Group with the right mouse button to open the context menu.

2. Choose CompositeProvider

to create a new CompositeProvider. You can also press c.

3. Enter ZCP99 as Name .

DMM360

64


4. Enter "Sales Order Actuals & History - 99" as Description

5. The Overview Tab shows you various BW properties for e.g. Query Mode, Caching, etc. Click the

Scenario .

6. Press the "Add" button and enter

Zadsa99 in the box.

DMM360

65


7. Click OK .

8. Enter ZADS_HIST in the box. Note: In this case please enter the name like shown and work with the given object.

9. Click OK .

DMM360

66


10. Click .

11. Click .

12. Click [ZADS_HIST] Sales Order History (ADSO)

(13+0) . Press Shift key while performing the action.

13. Drag [ZADSA99] SalesOrder Actuals 99

(13+0) . 14. Drop on .


(Ctrl+F3) .

16. Click Show Preview .

DMM360

67

5.2. Summary You have completed the exercise! You are now able to:

Create a CompositeProvider with SAP BW 7.40

© 2014 SAP AG or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG or an SAP affiliate company. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG (or an SAP affiliate company) in Germany and other countries. Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

experience sap bw data provisioning from sap and non-sap sources - exercise

Documents

load data

sap bw

data flow

load history data

data provisioning

historic data

data source

setup of data replication