steps for implementation of dso for purchase cube in sap bi 7 0

8/11/2019 Steps for Implementation of DSO for Purchase Cube in SAP BI 7 0

1/33

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX -bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

2010 SAP AG 1

Steps for Implementation ofStandard 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 theBusiness 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 fromone 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 SAPBI Developer. His expertise includes SAP BI 7.0 and ABAP.
http://www.sdn.sap.com/irj/scn/articles-bi-allhttp://www.sdn.sap.com/irj/scn/articles-bi-allhttp://www.sdn.sap.com/irj/scn/articles-bi-allhttp://www.sdn.sap.com/irj/scn/articles-bi-all


2/33

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


2010 SAP AG 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 ........................................................................................................................................... 26

Handling Summation & Delta Updates ......................................................................................................... 31

Related Content ................................................................................................................................................ 32

Disclaimer and Liability Notice .......................................................................................................................... 33


3/33



2010 SAP AG 3

Business Scenario

Sometimes it is desirable to combine data from different Data Sources before the same is stored into the InfoCubes. 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 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.

o 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, thisdata is aggregated. So data can be overwritten in DSO and this provides a significantcapability to BW.

Reporting

o Direct on document level data

o Drilldown from Info cube to document level

Architecture of Standard ODS / DSO (7.x)

ODS Objects consist of three tables as shown in the architectureSource: SAP Docs

Fig. A - ODS Architecture - Extracted from SAP Docs


4/33



2010 SAP AG 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 tosupport the document analysis. In the context of the DSO, the PSA makes up the first level and the DSOtable makes up the second level of the DSO. Therefore, the first level consists of the transaction data fromthe source system, and the second level consists of the consolidated data and data from several sourcesystems and Info Sources. You can run this analysis directly on the contents of the table, or run it from anInfo 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 Cubecan be less granular with data held for a longer period of time versus the DSO which can be very granularbut hold data for a shorter period of time. Data from the ODS can be updated into appropriate Info Cubes orother 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 (PersistentStaging Area) corresponds to DSO. From the PSA we have the possibility, via transfer rules, to upload datato DSO. The DSO is represented here as one layer, but depending on the business scenario, BI DSO can bestructured with multiple levels.

Thus, the ODS objects offer data that are subject oriented, consolidated and integrated with respect to sameprocess 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 de-normalized data structure.

Structure of ODS

While transferring data from PSA to ODS objects, rules (Transfer Rules) can be applied to clean records andtransform them to company-wide standards for characteristic values. If it is meaningful at this stage,business logic may also be applied (Update Rules).


5/33



2010 SAP AG 5

Sample Scenario for a Standard DSO

Consider an example involving a Standard DSO in SAP BI 7.0.

Lets check flat file records, the key fields are customer and material and we have a duplicate record (CheckRec.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. Its overwritten with most recentrecord. 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 ActiveQueue table. This is because we haven't activated request yet & that duplicate record for key in DSO getsoverwritten.

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 suitcertain scenarios and the characteristics will overwrite always.

Naming Conventions

Tech. Name of New data / Activation queue table is always for customer objects - /bic 140 and for SAP objects - /bio140.

Name of active data table /BIC/A100 and /BI0 for SAP(Click herefor more details).

Name of change log table -The technical name is always /BIC/.

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. DData 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.
http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/5049http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/5049http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/5049http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/5049


6/33



2010 SAP AG 6

Fig. EChanges 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 isuniquely identified by technical key (Request Number, Data packet number, Partition value of PSA and Datarecord number). With the second request the change log table puts the before and after Image for therelevant records.

Fig. FStudy 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 keyfigures 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.


7/33



2010 SAP AG 7

Fig. GFinal Change Log Output

Record modes

The record mode(s) that a particular data source uses for the delta mechanism largely depends on the typeof the extractor. Ref. OSS notes 399739 for more details.

Work ScenarioLets 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 wherematerial 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

Fig. HIllustrates the differentimages of the record modes inChange Log


8/33



2010 SAP AG 8

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

Fig. 1.1 -- Creation of an Info area in RSA1 -- An Info area is very similar to a folder for files (herein contextwe must think files to Info objects & catalogs). Go to Info Objects Right Click & Create Info area.

Fig. 1.2Naming the Info area: Give the short & long description for the Info Area.

Fig. 1.3 -- Creation of Info Object Catalog: Right-click on the Info area & choose "Create Info object catalog"


9/33



2010 SAP AG 9

Fig. 1.6 -- After creating the Info object catalog, we create IOs like Char Info Objects: [Customer ID, MaterialID, Status] & Key Figures: [Qty]

Fig. 1.4 -- Creating a Characteristic Infoobject Catalog. Give the tech name &description for the Info object Catalog.

Fig. 1.5 -- Creating a Key Figure Infoobject Catalog. Give the tech name &description for the Info object Catalog.


10/33



2010 SAP AG 10

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..... This creates an Application component area for DS.

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

Fig. 1.9 -- Now, right clicks the Application Component Area & chooses "Create Data Source", which createsthe DS for holding object components for transfer.

Fig. 1.10 -- Description about Data source, itsSource system & DTD must be specified. Here

we have chosen to use a flat file sourcesystem. The data type is Transactional Data,which is best suited when operated for Infoproviders like Cubes.


11/33



2010 SAP AG 11

Fig. 1.12 -- Now, that we have created the Data source, we need to set the parameters for the 'Extraction' tobe done. Here, we have the settings like 'Full upload', 1 Header lines to be ignored, Comma Data separator,Double hyphen Escape sign etc. Here we need to specify the name of the flat file which holds the data. Theinput file can be either loaded from a AL11 Common server or directly from the desktop / local NAS / localworkstation etc.

Fig. 1.11 -- This is sample CSV file. This

holds information about the different IOs[Customer ID, Material ID, Status, Quantity]etc. We need these details to be loaded intoour Info providers through sometransformation, which is done in next step.


12/33



2010 SAP AG 12

Fig. 1.13 -- 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. 1.14 -- The next tab is 'Fields', which displays a prompt if we must copy the field properties from the infoobject or not. Once done, we can move to the next screen tab called 'Preview' which generates a sampleoutput.

Fig. 1.15 -- The last tab is called 'Preview'. As, show the data from the CSV is as displayed here. We caneasily generate a small sample snap of the raw data from the source system at this level.


13/33



2010 SAP AG 13

Fig. 1.16 -- Creation of DSO

Now go to 'Info provider' & right click on Info provider to "Create Data store object"

Fig. 1.17 -- At this step, we'llname our DSO & give it atechnical name.

Fig. 1.18 -- Here, we need to

specify IOC to be selected.

Click OK & bypass this prompt

(default)


14/33



2010 SAP AG 14

Fig. 1.19 -- At the DSO level, we need to specify the Key fields, Data fields that constitute the DSO. We herespecify the [Customer ID, Mat ID] as the Key Fields.

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

Fig. 1.21 -- Also, before this step, we must also not forget the Key figure IO [Quantity]. We need this as aData field along with its unit of measure [0UNIT]. Now we can save the DSO & activate.


15/33



2010 SAP AG 15

Fig. 1.22 -- Further this step, we need to create a transformation for loading data. We now right click theDSO and choose "Create Transformation".

Fig. 1.23 -- Here at this step, we need to specify the Source & Targets of the transformation. Its evident that

every transformation will necessitate a source to target loading of data. Here the DSO is the target & theData Source [DS_TEST_MINE] forms the Source. Please note that Source system being a CSV is declaredas Flat file.


16/33



2010 SAP AG 16

Fig. 1.24 -- This is full view of transformation. We can see whole view of source DS and its target DSO. Wecan note that DSO has a counter for 0RECORDMODE which has the number of records the DSO contains.

Fig. 1.25 -- Once we collapse the structure, we can see the actual view without the rule groups.

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


17/33



2010 SAP AG 17

Fig. 1.27 -- As in transformation, here also we need to specify the source & the targets. We have the sourceas the Data source [DS_TEST_MINE] & the target DSO which was created in the previous steps. Once doneclick OK & proceed next step.

Fig. 1.29 -- Data flows from source to target PSA via the Info package, which triggers the transfer. Here, justspecify the description of the IP and proceed further.

Fig. 1.28 -- Now, Its necessary to create anInfo package. IP is a very essential interfacefor triggering the data from the Flat file to thePSA (Persistent Staging Area).


18/33



2010 SAP AG 18

Fig. 1.30 -- In the IP, Clicking the 'Start' with the option "Start Data Load immediately" will execute the datatransfer from flat file CSV to Persistent Staging Area. This can be scheduled as a background job also, butfor the time being we'll make it 'Immediate' start.

Fig. 1.31 -- Once done, we now click on the "Call Monitor for BI object".


19/33



2010 SAP AG 19

Fig. 1.32 -- This is just a monitor tohandle the requests / jobs from theuser. We can schedule immediateor later the execution of the IP, butonce done, the status of therecords loaded to the PSA isdisplayed here in green.

Fig. 1.33 -- Click on the'Display Data Flow' option toview the type of data flowstructure we have just created.


20/33



2010 SAP AG 20

Fig. 1.34 -- Now in this step we create a Infocube. Right click on the Info provider & clickon "Create Info Cube"

Fig. 1.35 -- Here, we enter the name of the Infocube & give its description for the same.


21/33



2010 SAP AG 21

Fig. 1.36 -- Click & drag the objects as dimensions. We have created Material, Customer & Status

dimensions in the Info cube.

Fig. 1.37 -- Saving & activating the Info cube

Fig. 1.38 -- Upon DSO now create transformation.

Fig. 1.39 -- Creation of transformation -- We now

specify source & targets of transformation. Here,

target is newly created Info Cube & source is DSO


22/33



2010 SAP AG 22

Fig. 1.40 -- At the transformation level, we can view the fields in the Info cube group are aggregated as one

for the Quantity. But its not like what it really looks like.

Fig. 1.41 -- Now expanding this group, we can not the bifurcation as explained for the Info cubes.

Fig. 1.42 -- Now clicking onRule group, we can note ruledetails for Quantity [QTY23].

Fig. 1.43 -- Creation of DTPWe now create a data transferprocess by right clicking on &choosin "Create DTP"


23/33



2010 SAP AG 23

Fig. 1.44 -- We now have tospecify the source DSO &target Info cube.

Fig. 1.45 -- We now have to 'Execute' the DTP.

Fig. 1.46 -- Now, that we have the data in the DSO, we cannow click on 'Info provider Administration' to further viewthe request status. The request being Green color is agood sign the data has been loaded.


24/33



2010 SAP AG 24

Fig. 1.47 -- 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. 1.49 -- Notice, the Active Queue data

[SID, DATAPID, REC, /BIC/CUSTID, /BIC/MATID, /BIC/STATS, /BIC/QTY, 0UNIT, 0RECMODE]

Fig. 1.48 -- Choose optionsin the data browser.


25/33



2010 SAP AG 25

Fig. 1.50 -- Now click on the "Change Log" (Display Change Log Tab) in the Info provider administration.

Fig. 1.51 -- Now, Click on 'Activate' which will Activate DS object data

Fig. 1.52 -- Here, we need to Startthe "Activation'.


26/33



2010 SAP AG 26

Trouble Shooting

Fig. 1.53 -- The 'Refresh' option here will enable the activation of data in the DSO. But, note that here wehave a small error, that we have the Yellow request ID. But, we must trouble shoot out this error.

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


27/33



2010 SAP AG 27

Fig. 1.55: Now that we have changed status, "Request available for reporting" as in Green.

Fig. 1.56 -- Further this, we display the data in the data browser.

Fig. 1.57 -- Here, as we click the Active Data button, we can view the data browser.


28/33



2010 SAP AG 28

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

Pl. check the status here, note it is [0].

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

Fig. 1.60 -- Its to be noted that the Change Log registers lot of parameters than the Active Log.


29/33



2010 SAP AG 29

Fig. 1.61 -- Right click on the DSO to display the data.

Fig. 1.62 -- Here we must choose the options necessary for data view. Click on 'Fld. Selection for Output' formore detailed options. In the Fld. Selection o/p, Choose the basic necessary details necessary for user view,like [Qty], [Cust.ID],[Material ID].

Fig. 1.63 -- The data is as displayed here in the listoutput for the DSO.


30/33



2010 SAP AG 30

Fig. 1.65 -- 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. 1.64 -- 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. 1.67 -- Successfully data is loadedperfectly from flat file to DSO to Info cube.


31/33



2010 SAP AG 31

Handling Summation & Delta Updates

Fig. 1.67 -- Note: Summation in the Rule Type > Aggregation: Summation.

Fig. 1.68 -- Note: To perform full or delta updates, we need to check these following options.


32/33



2010 SAP AG 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 theBusiness Intelligence homepage.
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/eb8f1895-0501-0010-73ad-e0bef4a2000ahttp://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/eb8f1895-0501-0010-73ad-e0bef4a2000ahttp://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/5049http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/5049http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/5049http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/5049http://wiki.sdn.sap.com/wiki/display/BI/Eliminate+redundant+data+in+the+consolidation+DSOhttp://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/5586d290-0201-0010-b19e-a8b8b91207b8http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/5586d290-0201-0010-b19e-a8b8b91207b8https://www.sdn.sap.com/irj/sdn/nw-bihttps://www.sdn.sap.com/irj/sdn/nw-bihttps://www.sdn.sap.com/irj/sdn/nw-bihttps://www.sdn.sap.com/irj/sdn/nw-bihttp://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/5586d290-0201-0010-b19e-a8b8b91207b8http://wiki.sdn.sap.com/wiki/display/BI/Eliminate+redundant+data+in+the+consolidation+DSOhttp://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/5049http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/5049http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/eb8f1895-0501-0010-73ad-e0bef4a2000a


33/33


Disclaimer and Liability Notice

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is notsupported 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 orcode sample, including any liability resulting from incompatibility between the content within this document and the materials andservices offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of thisdocument.

steps for implementation of dso for purchase cube in sap bi 7 0

Documents