Steps for Implementation of Standard Data Store Object (DSO) for Purchase Cube in SAP BI 7.0

Size: px

Start display at page:

Download "Steps for Implementation of Standard Data Store Object (DSO) for Purchase Cube in SAP BI 7.0"

Rosemary Atkinson
5 years ago
Views:

1 Steps for Implementation of Standard Data Store Object (DSO) for Purchase Cube in SAP BI 7.0 Applies to: SAP BI 7.0 Also works on SAP BW 3.5.For more information, visit the Business Intelligence Homepage. Summary Data Store Object (DSO/ODS object) is used to store consolidated & cleansed data (both master & transaction data) on a Document level (i.e. Atomic level). It can be perceived as a Data set consolidated from one or more Info Sources or Transformations (BI 7.0) Author: Arun Bala Ganesan Company: Wipro Technologies Created on: 15 January 2010 Author Bio The author currently works for Wipro Technologies (Bangalore, India) as an Associate SAP BI Developer. His expertise includes SAP BI 7.0 and ABAP SAP AG 1

2 Table of Contents Business Scenario... 3 Types of DSO... 3 Motivation for DSO... 3 Architecture of Standard ODS / DSO (7.x)... 3 The Transition: ODS Objects (3.X) to DSO (BI 7.0)... 4 Structure of ODS... 4 Sample Scenario for a Standard DSO... 5 Naming Conventions... 5 Change Log... 5 Detailed Study on Change Logs... 6 Record modes... 7 Work Scenario... 7 Trouble Shooting Handling Summation & Delta Updates Related Content Disclaimer and Liability Notice SAP AG 2

3 Business Scenario Sometimes it is desirable to combine data from different Data Sources before the same is stored into the Info Cubes. Also, there are analyses that need access to the detailed data than that found in the Cubes. Types of DSO Standard Data Store Object (Ref. Fig. A) Data Store Object with Direct Update (Transactional ODS using 3.x) Write Optimized Data Store - BI 7.0 o Contains only active data table used to manage huge data loads Motivation for DSO Consolidation & Cleansing o o A further motivation is the need for a place where data can be consolidated and cleansed. This is important when we upload data from completely different Source Systems. After consolidation and cleansing, data can be uploaded to Info Cubes. To store data on document level Overwrite capability of characteristics o Not possible to overwrite data in Info Cube as whenever data is added to Info Cube, this data is aggregated. So data can be overwritten in DSO and this provides a significant capability to BW. Reporting o o Direct on document level data Drilldown from Info cube to document level Architecture of Standard ODS / DSO (7.x) ODS Objects consist of three tables as shown in the architecture Source: SAP Docs Fig. A - ODS Architecture - Extracted from SAP Docs 2010 SAP AG 3

The Transition: ODS Objects (3.X) to DSO (BI 7.0) The ODS consists of consolidated data from several Info Sources on a detailed (document) level, in order to support the document analysis.

4 The Transition: ODS Objects (3.X) to DSO (BI 7.0) The ODS consists of consolidated data from several Info Sources on a detailed (document) level, in order to support the document analysis. In the context of the DSO, the PSA makes up the first level and the DSO table makes up the second level of the DSO. Therefore, the first level consists of the transaction data from the source system, and the second level consists of the consolidated data and data from several source systems and Info Sources. You can run this analysis directly on the contents of the table, or run it from an Info Cube query into a query by means of a drilldown. Fig. B. Sample schema for Reporting using ODS Objects (using Update Rules & Transfer Rules) * Note: UR refers to Update Rules Prior to existence of DSO, decisions on granularity were based solely on data in Info Cube. Now Info Cube can be less granular with data held for a longer period of time versus the DSO which can be very granular but hold data for a shorter period of time. Data from the ODS can be updated into appropriate Info Cubes or other ODS Objects. Reporting on ODS can be done with the OLAP processor or directly with an ODS query. In this Fig. B, data from Data Source A and Data Source B is uploaded to a PSA. The PSA (Persistent Staging Area) corresponds to DSO. From the PSA we have the possibility, via transfer rules, to upload data to DSO. The DSO is represented here as one layer, but depending on the business scenario, BI DSO can be structured with multiple levels. Thus, the ODS objects offer data that are subject oriented, consolidated and integrated with respect to same process on different source systems. After data has been stored, or while the data is updated in the ODS, we have option of making technical changes as well as data changes. In the ODS, data is stored in a denormalized data structure. Structure of ODS While transferring data from PSA to ODS objects, rules (Transfer Rules) can be applied to clean records and transform them to company-wide standards for characteristic values. If it is meaningful at this stage, business logic may also be applied (Update Rules) SAP AG 4

The 'Unique Data Records option is unchecked which means it can expect duplicate records. Figure C.

5 Sample Scenario for a Standard DSO Consider an example involving a Standard DSO in SAP BI 7.0. Let s check flat file records, the key fields are customer and material and we have a duplicate record (Check Rec.2). The 'Unique Data Records option is unchecked which means it can expect duplicate records. Figure C. Explains how records are captured in a DSO (Refer selected options below) After update rule, Record 2 in PSA is overwritten as it has got same keys. It s overwritten with most recent record. The key here is [M1000 Customer A]. If we note the monitor entries, 3 records are transferred to update rules & two records are loaded in to Active Queue table. This is because we haven't activated request yet & that duplicate record for key in DSO gets overwritten. Note: Activation Queue can also be expressed as 'New Data' table The key figures will have the overwrite option by default, additionally we have the summation option to suit certain scenarios and the characteristics will overwrite always. Naming Conventions Tech. Name of New data / Activation queue table is always for customer objects - /bic <name of ODS>140 and for SAP objects - /bio<dso_name>140. Name of active data table /BIC/A<DSO_Name>100 and /BI0 for SAP (Click here for more details). Name of change log table - The technical name is always /BIC/<internal generated number>. Once we activate we will have two records in DSO's Active Data table. The Active Data table always has contains the semantic key (E.g. Customer & Material for instance) Change Log The Change Log table has 2 entries with the image N (stands for New ). The technical key (REQID, DATAPACKETID, RECORDNUMBER) will be part of change log table. (Refer Fig. D) Fig. D Data is loaded to CL & ADT (Pl. refer Fig. A for more details) Introducing a few changes, we get the following result as in Fig. E SAP AG 5

Fig. E Changes Introduced from the Flat file is reflected on PSA ADT & PSA CL Detailed Study on Change Logs We will check Change log table to see how the deltas are handled.

With the second request the change log table puts the before and after Image for the relevant records. Fig.

6 Fig. E Changes Introduced from the Flat file is reflected on PSA ADT & PSA CL Detailed Study on Change Logs We will check Change log table to see how the deltas are handled. The records are from first request that is uniquely identified by technical key (Request Number, Data packet number, Partition value of PSA and Data record number). With the second request the change log table puts the before and after Image for the relevant records. Fig. F Study on the Change Log on how the Deltas are handled In this example Customer and Material has the before image with record mode "X". And also note that all key figures will be having "-" sign if we opted to overwrite option & characteristics will be overwritten always. A new record (last row in the Fig. F) is added is with the status "N" as it's a new record SAP AG 6

Record modes Fig. G Final Change Log Output The record mode(s) that a particular data source uses for the delta mechanism largely depends on the type of the extractor. Ref.

In this example we will take the Master data object Customer, Material with a few attributes for the demonstration purpose.

7 Record modes Fig. G Final Change Log Output The record mode(s) that a particular data source uses for the delta mechanism largely depends on the type of the extractor. Ref. OSS notes for more details. Fig. H Illustrates the different images of the record modes in Change Log Work Scenario Let s go through a sample real time scenario. In this example we will take the Master data object Customer, Material with a few attributes for the demonstration purpose. Here we define a ODS / DSO as below where material and customer is a key and the corresponding attributes as data fields. ODS / DSO definition Definition of the transformation Flat file Loading Monitoring the Entries Monitoring Activation Queue Monitoring PSA data for comparison Checking Active Data Table Monitoring Change Log Table Displaying data in suitable Info provider (E.g. Flat File PSA DSO Info Cube) Note: In SAP BI 7.0 the status data is written to active data table in parallel while writing to Change log. This is an advantage of parallel processes which can be customized globally or at object level in system 2010 SAP AG 7

Start transaction RSA1 in SAP BI 7.0 and follow the following steps as illustrated.

1 -- Creation of an Info area in RSA1 -- An Info area is very similar to a folder

Go to Info Objects Right Click & Create Info area.

8 Start transaction RSA1 in SAP BI 7.0 and follow the following steps as illustrated. Fig Creation of an Info area in RSA1 -- An Info area is very similar to a folder for files (herein context we must think files to Info objects & catalogs). Go to Info Objects Right Click & Create Info area. Fig. 1.2 Naming the Info area: Give the short & long description for the Info Area. Fig Creation of Info Object Catalog: Right-click on the Info area & choose "Create Info object catalog" 2010 SAP AG 8

Fig. 1.4 -- Creating a Characteristic Info object Catalog.

1.5 -- Creating a Key Figure Info object Catalog. 1.

Char Info Objects: [Customer ID, Material ID, Status] & Key

9 Fig Creating a Characteristic Info object Catalog. Give the tech name & description for the Info object Catalog. Fig Creating a Key Figure Info object Catalog. Give the tech name & description for the Info object Catalog. Fig After creating the Info object catalog, we create IOs like Char Info Objects: [Customer ID, Material ID, Status] & Key Figures: [Qty] 2010 SAP AG 9

Fig. 1.7 -- Now, we must create AC Areas. For this go to "Data source" & right click on the top bar choosing "Create Application Component.

8 -- The technical names & long description for Application Component Area must be enlisted here. Fig. 1.

10 Fig Now, we must create AC Areas. For this go to "Data source" & right click on the top bar choosing "Create Application Component... This creates an Application component area for DS. Fig The technical names & long description for Application Component Area must be enlisted here. Fig Now, right clicks the Application Component Area & chooses "Create Data Source", which creates the DS for holding object components for transfer. Fig Description about Data source, its Source system & DTD must be specified. Here we have chosen to use a flat file source system. The data type is Transactional Data, which is best suited when operated for Info providers like Cubes SAP AG 10

Fig. 1.13 -- The next tab here elicits the 'Proposal' methods that need to be taken care of while transforming.

14 -- The next tab is 'Fields', which displays a prompt if we must copy the field properties from the info object or not.

12 Fig The next tab here elicits the 'Proposal' methods that need to be taken care of while transforming. Here we need to key in the fields one by one (editable) or generate the field proposal as stated (by default). We can also load some of the example data here. Fig The next tab is 'Fields', which displays a prompt if we must copy the field properties from the info object or not. Once done, we can move to the next screen tab called 'Preview' which generates a sample output. Fig The last tab is called 'Preview'. As, show the data from the CSV is as displayed here. We can easily generate a small sample snap of the raw data from the source system at this level SAP AG 12

13 Fig Creation of DSO Now go to 'Info provider' & right click on Info provider to "Create Data store object" Fig At this step, we'll name our DSO & give it a technical name. Fig Here, we need to specify IOC to be selected. Click OK & bypass this prompt (default) 2010 SAP AG 13

Fig. 1.19 -- At the DSO level, we need to specify the Key fields, Data fields that constitute the DSO.

20 -- Note that [Stats] is assigned as a Data fields -- We now need to Save this and activate further. Fig. 1.

14 Fig At the DSO level, we need to specify the Key fields, Data fields that constitute the DSO. We here specify the [Customer ID, Mat ID] as the Key Fields. Fig Note that [Stats] is assigned as a Data fields -- We now need to Save this and activate further. Fig Also, before this step, we must also not forget the Key figure IO [Quantity]. We need this as a Data field along with its unit of measure [0UNIT]. Now we can save the DSO & activate SAP AG 14

Fig. 1.22 -- Further this step, we need to create a transformation for loading data.

23 -- Here at this step, we need to specify the Source & Targets of the transformation.

15 Fig Further this step, we need to create a transformation for loading data. We now right click the DSO and choose "Create Transformation". Fig Here at this step, we need to specify the Source & Targets of the transformation. It s evident that every transformation will necessitate a source to target loading of data. Here the DSO is the target & the Data Source [DS_TEST_MINE] forms the Source. Please note that Source system being a CSV is declared as Flat file SAP AG 15

Fig. 1.24 -- This is full view of transformation.

We can note that DSO has a counter for 0RECORDMODE which has the number of records the

25 -- Once we collapse the structure, we can see the actual view without the rule

16 Fig This is full view of transformation. We can see whole view of source DS and its target DSO. We can note that DSO has a counter for 0RECORDMODE which has the number of records the DSO contains. Fig Once we collapse the structure, we can see the actual view without the rule groups. Fig Now we must create DTP. Now, right click on and choose the option "Create Data Transfer Process". A DTP is very important interface / bridge for transfer of data from the PSA to Info provider SAP AG 16

Fig. 1.27 -- As in transformation, here also we need to specify the source & the targets.

previous steps. Once done click OK & proceed next step. Fig. 1.

IP is a very essential interface for triggering the data from the Flat file to the PSA (Persistent

17 Fig As in transformation, here also we need to specify the source & the targets. We have the source as the Data source [DS_TEST_MINE] & the target DSO which was created in the previous steps. Once done click OK & proceed next step. Fig Now, It s necessary to create an Info package. IP is a very essential interface for triggering the data from the Flat file to the PSA (Persistent Staging Area). Fig Data flows from source to target PSA via the Info package, which triggers the transfer. Here, just specify the description of the IP and proceed further SAP AG 17

execute the data transfer from flat file CSV to Persistent Staging Area.

18 Fig In the IP, Clicking the 'Start' with the option "Start Data Load immediately" will execute the data transfer from flat file CSV to Persistent Staging Area. This can be scheduled as a background job also, but for the time being we'll make it 'Immediate' start. Fig Once done, we now click on the "Call Monitor for BI object" SAP AG 18

Fig. 1.32 -- This is just a monitor to handle the requests / jobs from the user.

the records loaded to the PSA is displayed here in green. Fig. 1.

19 Fig This is just a monitor to handle the requests / jobs from the user. We can schedule immediate or later the execution of the IP, but once done, the status of the records loaded to the PSA is displayed here in green. Fig Click on the 'Display Data Flow' option to view the type of data flow structure we have just created SAP AG 19

Fig. 1.34 -- Now in this step we create a Info cube.

20 Fig Now in this step we create a Info cube. Right click on the Info provider & click on "Create Info Cube" Fig Here, we enter the name of the Info cube & give its description for the same SAP AG 20

Fig. 1.36 -- Click & drag the objects as dimensions.

Info cube. Fig. 1.37 -- Saving & activating the Info cube Fig. 1.38 -- Upon DSO now create transformation.

39 -- Creation of transformation -- We now specify source &

21 Fig Click & drag the objects as dimensions. We have created Material, Customer & Status dimensions in the Info cube. Fig Saving & activating the Info cube Fig Upon DSO now create transformation. Fig Creation of transformation -- We now specify source & targets of transformation. Here, target is newly created Info Cube & source is DSO 2010 SAP AG 21

41 -- Now expanding this group, we can not the bifurcation as explained for the

22 Fig At the transformation level, we can view the fields in the Info cube group are aggregated as one for the Quantity. But it s not like what it really looks like. Fig Now expanding this group, we can not the bifurcation as explained for the Info cubes. Fig Now clicking on Rule group, we can note rule details for Quantity [QTY23]. Fig Creation of DTP We now create a data transfer process by right clicking on & choosing "Create DTP" 2010 SAP AG 22

Info cube. 45 -- We now have to 'Execute' the DTP.

click on 'Info provider Administration' to further view

23 Fig We now have to specify the source DSO & target Info cube. Fig We now have to 'Execute' the DTP. Fig Now, that we have the data in the DSO, we can now click on 'Info provider Administration' to further view the request status. The request being Green color is a good sign the data has been loaded SAP AG 23

Fig. 1.47 -- As we know the DSO has 2 parts to hold data.

Now click on the display data to view in data browser. Fig. 1.

24 Fig As we know the DSO has 2 parts to hold data. One the activation queue & the other the change log. Now click on the display data to view in data browser. Fig Choose options in the data browser. Fig Notice, the Active Queue data [SID, DATAPID, REC, /BIC/CUSTID, /BIC/MATID, /BIC/STATS, /BIC/QTY, 0UNIT, 0RECMODE] 2010 SAP AG 24

25 Fig Now click on the "Change Log" (Display Change Log Tab) in the Info provider administration. Fig Now, Click on 'Activate' which will Activate DS object data Fig Here, we need to Start the "Activation' SAP AG 25

Trouble Shooting Fig. 1.53 -- The 'Refresh' option here will enable the activation of data in the DSO.

But, we must trouble shoot out this error. Fig. 1.

26 Trouble Shooting Fig The 'Refresh' option here will enable the activation of data in the DSO. But, note that here we have a small error, that we have the Yellow request ID. But, we must trouble shoot out this error. Fig So, what meant error is like we have Status [o], but we need to have Status as [O] (P.S. Kindly note that the status here is mostly mistaken & is sometimes case sensitive) It should be as above in CSV SAP AG 26

56 -- Further this, we display the data in

27 Fig. 1.55: Now that we have changed status, "Request available for reporting" as in Green. Fig Further this, we display the data in the data browser. Fig Here, as we click the Active Data button, we can view the data browser SAP AG 27

Fig. 1.58 -- Now, note that the data here is as [M1000, C1000,"0", 100000, KG].

59 -- Now we click on CL (Change Log) & display the data in the data browser

28 Fig Now, note that the data here is as [M1000, C1000,"0", , KG]. Pl. check the status here, note it is [0]. Fig Now we click on CL (Change Log) & display the data in the data browser Fig Its to be noted that the Change Log registers lot of parameters than the Active Log SAP AG 28

62 -- Here we must choose the options necessary for data view.

29 Fig Right click on the DSO to display the data. Fig Here we must choose the options necessary for data view. Click on 'Fld. Selection for Output' for more detailed options. In the Fld. Selection o/p, Choose the basic necessary details necessary for user view, like [Qty], [Cust.ID],[Material ID]. Fig The data is as displayed here in the list output for the DSO SAP AG 29

65 -- Here once data is loaded, we check the display data option in the Info

30 Fig Now that we are sure there's data in the DSO, we need to trigger the DTP for data transfer from DSO to Info Cube. Press Execute to start the loading. Fig Here once data is loaded, we check the display data option in the Info cube. Perform a right click on the Info provider and check the transferred data. Choose the necessary options. Fig Successfully data is loaded perfectly from flat file to DSO to Info cube SAP AG 30

Handling Summation & Delta Updates Fig. 1.

31 Handling Summation & Delta Updates Fig Note: Summation in the Rule Type > Aggregation: Summation. Fig Note: To perform full or delta updates, we need to check these following options SAP AG 31

32 Related Content ODS Objects in BW 3.0 The Tech details of Standard ODS / DSO in SAP DWH Write-Optimized Data Store Objects Eliminate Redundant Data in the Consolidation DSO Enterprise wide Data Warehousing with SAP BW For more information, visit the Business Intelligence homepage SAP AG 32

33 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 SAP AG 33

Step by Step Procedure for DSO Creation

Step by Step Procedure for DSO Creation Applies to: SAP BI 7.0. For more information, visit the EDW homepage. Summary This article discusses about the step by step procedure for creating a DSO. Author: