Skip to main content

Operational Data Store (ODS) using SAP BW 3.5

Operational Data Store (ODS) using SAP BW 3.5

ODS consists of 'Key fields' and 'Data fields'. Data fields can also contain characteristics e.g. customer, product etc..

ODS is not used for multi-dimensional analysis like Infocube. The data from ODS can be updated with delta update into a Infocube. The data in ODS is stored in a transparent table. There is no fact or dimensional table created for ODS.

Following are the steps to create an ODS:

1) Execute transaction RSA1, select the InfoArea under which you would like to create ODS. Right click the InfoArea, select 'Create ODS Object'
2) Enter ODS Object 'Name' and 'Description', press 'Create'
3) Check the box against 'BEx Reporting' to enable ODS for BEx reporting, press 'InfoObject Catalog' button to get the InfoObjects which you would like to add to ODS

4) Select the characteristics (InfoObjects) which you would like to add as 'Key fields' or 'Data fields', drag and drop the InfoObjects in respective folders as shown below.
5) You can also insert an InfoObject into to fields folders by right clicking the folder
6) Add '0CALMONTH' as 'Key field'

7) Add Key Figures as 'Data fields' as shown below, check and activate the ODS, system will display message related to ODS activation


8) Press 'Back', you can see ODS as shown

Now define InfoSources, Transfer Rules, Update Rules, Info Package as discussed in Infocube Creation Steps.

9) Below is the Extraction Structure created based on ODS

Comments

Anonymous said…
Thank you for the useful and easy to understand presentation.
From an SAP student.
Keep following my Blog, you will find more helpful stuffs here

Popular posts from this blog

Step by Step guide on BADI with Filter implementation

Step 1 à Before implementing filter objects to a BADI. We need to deactivate all the implementation for that BADI. Go to SE18 (BADI definition) and from there navigate to all BADI implementation to view all the active implementations for that BADI Select the BADI implementations listed on the screen and deactivate the implementation. Once done, return back to the initial screen of SE18 and proceed with next step. Step 2 à go to SE18 – BADI Definition screen and change the existing BADI definition that we created in the earlier tutorial.   Select the FILTER –DEPENDENT check box under the TYPE section. This will open up the FILTER TYPE field for inputs. And do an F1 on the FILTER TYPE field. Click on the F4 on the FILTER TYPE field name and enter some search criteria to find a relevant data element. And click on the continue button   Select the data element from the list to set up your filter and hit enter. Click on the save butto...

Creating Hierarchies

Prerequisites In the InfoObject maintenance, the indicator with hierarchies is set for the relevant characteristic, meaning that the characteristic can have hierarchies. Procedure Step 1: Select the InfoObject tree in the Administrator Workbench. If you have assigned the characteristic to an InfoObject catalog, select the corresponding InfoObject catalog for an InfoArea. If the characteristic does not belong to an InfoObject catalog, select the Not Assigned Nodes InfoArea and the Not Assigned Characteristics InfoObject catalog. Step 2: Select the characteristic for which you want to create a hierarchy, choose the context menu with the right mouse button, and then Create hierarchy. Step 3: In the dialog box, enter the technical hierarchy name, or the hierarchy version if applicable, the time-reference, and at least one short description of the hierarchy. Confirm your entries. You come to the screen Maintain hierarchies. You can now define your hierarchy here. Creating Nodes and Leaves...

Introduction to SAP Hierarchies

Definition A hierarchy is a method of displaying a characteristic structured and groupedaccording to individual evaluation criteria.A BW hierarchy has the following properties: Hierarchies are created for basic characteristics (characteristics containing master data).The characteristic 0COSTCENTER is an example. Hierarchies are stored in master data tables. They are also similar to master data, and can therefore be used and modified in all InfoCubes. You can define several hierarchies for a single characteristic. A hierarchy can have a maximum of 98 levels. You can load hierarchies from the R/3 system, or from a flat file. You can also create andchange hierarchies manually in the BW system. Use: Hierarchies are used in two main ways: 1. Firstly, the structured display of characteristic values (tree display) in a presentation hierarchy. 2.Secondly, selecting a defined quantity of characteristic values as a selection of hierarchy nodes. Structure A hierarchy consists of nodes. A node can...