This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BA - boc.sap.com | UAC - uac.sap.com
This article applies to SAP_BW 3.X and SAP_BW 7.0. For more information, visit the EDW homepage
Summary
This article explains how to create Infoset using InfoObject (Characteristic master data) and DSO which also explains steps to create InfoObject (Characteristic with master data) and DSO.
Author: K Venu Gopal
Company: YASH Technologies Pvt Ltd
Created on: 25th July 2011
Author Bio
K Venu Gopal is presently working for YASH Technologies Pvt Ltd, India as SAP BI ABAP consultant.
Step 1: Creating InfoObject (Characteristics with master data) ...................................................................... 3
Step 2: Steps to create Data Store Object. ..................................................................................................... 7
Step 3: Steps to create Infoset using InfoObject (characteristic master data) and DSO. ............................. 10
Step 4: Building Query on Infoset. ................................................................................................................ 12
Related Content ................................................................................................................................................ 14
Disclaimer and Liability Notice .......................................................................................................................... 15
Steps to Create Infoset using InfoObject and DSO
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BA - boc.sap.com | UAC - uac.sap.com
Infoset is described as a specific kind of InfoProvider which do not store data physically.Infoset collects data from the tables of InfoProviders used to build it.InfoSet describes data sources that are defined as a rule of join on DataStore objects, standard InfoCubes and/or InfoObjects (characteristics with master data).
Note: A join can contain objects of the same object type, or objects of different object types. We can include individual objects in a join condition as many times as we want. Default join condition is inner join, we can also use left outer
join by right clicking on choosing left outer join from the context menu.
Requirement:
Some times we come across the scenarios where we have to build a report on two/more different data targets.In this cases we can use Infosets which joins two/more data targets,and we can bulid Query on Infoset,which gets data from tables of Infoproviders used to build it(Infoset).
Now we will create an Infoset on both custom DSO and InfoObjects (characteristics with master
data).Prerequisites to create Infoset is at least two data targets should be ready.
The following are the steps to be followed to create Infoset.
1) Creating InfoObject (Characteristics with master data).
2) Creating a DSO.
3) Creating an Infoset using the above InfoObject and DSO.
4) Creating a Query using this Infoset.
Step 1: Creating InfoObject (Characteristics with master data)
Goto transaction RSA1 and select Infoarea and choose InfoObject catalog, right click on it and choose Create InfoObject from context menu.
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.