Mapping in Infoset

Hi All,
I have to create an infoset where I need to create a link between two infobjects.
Data length of two infoobjects differs from each other.
So, it doesn't allow me to create a link between the two objects.
One way is to change the data length for any of the infoobject and go ahead to create the infoset.
Can any suggest a better way to solve this, where I need not change the data length?
Thanks
Vandana

Hai..
An InfoSet mapping is not based on the Length of the InfoObject.
We can only able to map(Because InfoSet performs only Intersection) the Common attributes of InfoObjects.
Balajee Kannan

Similar Messages

How to map ECC Infoset Query to Crystal Report

Hi All,
I am using 25 standard SAP crystal reports which have been mapped on the top of ECC system. Some of reports are working well but some are not working due to unable to find query. The name of the report is Controlling Dashboard report and it has CO_OM_CA_20_Q1 query which I was unable to map on ECC using Crystal Report. I do not knw how to map ECC table infoset to Crystal report.
Can anybody assist me to get solution?

Hi Efstratios,
Hope you are well!
I am experiencing the same issue:
unable to get this infoset query CO_OM_CA_20_Q1 in Crystal Report which is made on the top of ECC
I followed the BI quick guide as well, I am on EPH 4 and I am able to see both the Query Infoset CO_OM_CA_20_Q1 and its related Infoset /SREP/CO_OM_CCA_20.
But unfortunately, it wouldn't let me update the connection approprietaly.
Is this something you can assist me with?
Thanks in advance
Yann

All the char not available in Bex for an DSO

Hi
I am using a standard DSO for reporting. In DSO data fields contains 25 characteristics and i can see the records in all the characteristics. However when i try to do reportng in the BEx it shows only 20 characteristics.
Other 5 char are missing. Please advice on this.
Regards
sapbi

I'm confused can you please explain in more detail steps whats are u trying to do.
Once you said you are building report on DSO later you said you are using infoset. be specific with the query that you want to ask.
1) Are you able to see the info objects in DSO.?
2) Are you building the report on top of DSO or Infoset?
3) i asked you to check property "authorization relevant" is ticked or not for the info object which are not seen while building the Report on DSO
in the info objects -- display screen -- business explorer tab -- is the option "auth relevant" is ticked or not?
4) if you are using infoset what is the other target that you used to map and what are the keys that u had mapped in infoset?
please provide all the details after checking again properly.... so that you can get some solution for your issue.

Loading data from one master data attr.to another master data in production

Hi all,
I have two two masterdata attr info objects A and B( have time dependent attr.).
according to businees requirement i have included 8 objects of A TO B to make them as time dependent.
all reports are designed on infosets only having these A and B ,some other ods objects.
I have done mapping in infosets and made changes in queries according to changes.i when moved from dev to quality and checked all infosets and queries all changes are reflecting in infosets and queries in quality.
*QUETIONS * :
1. while executing queries i am getting 'no data' in the reult of query output.
2. How can get 8 fields data from A to B, because A has lot of data for that 8 fields in A in production
Regards,
Chinna.

Hi chinna
first of all maintain the master data to attributes and these attribute converted into Navigational Attributes
in this way u can get master data at query output
thanks
Muralidhar Reddy.P
Edited by: Muralidhar Reddy P on Dec 24, 2008 9:31 PM

Dates are not mapped as the Date data type in Universe created on Infoset

Hi,
When i try to create the universe on top of Infoset query, the date fields present as the variables in SAP BI Query are not mapped as date data type in Universe, instead they are considered as Characters, hence the prompts related to those variables are coming s List of values instead of Calendar in WebI.
Can any one pls help me to find the solution on how to map date variables as calendar in Webi Prompts.(For SAP BI Queries created on Infoset)
Edited by: Nisha Makhija on Jul 20, 2009 5:59 PM

Hi Ingo,
Thanks for your response!!
The I Query is built on Top of BW MultiProvider and the InfoObject is of Type DATS.
Actually our Modeling on the BI is as follows :
DSOs> Infoset>Multiprovider->BI query>Universe.
Since we were not able to get the prompts as Calander so We tried Debugging on different Data targets to find the root cause. Please find our observations as follows:
When I tested the same date infoobject(of Type DATS) by creating a BI Query on top of DSO, Infocube & Multiprovider ,the Prompts are working fine as a calander in WEBI Report.
But when the BI Query is built on Infoset data target, In WEBI Report I am getting list of values rather a Calender prompt .
I tested in the Universe that field is appearing as Character instead of Date.
Please guide to resolve this issue.
Thanks,
Nisha.

InfoSet to DSO Transformation

Hi all,
I am trying to transfer data from an infoset to a DSO, the infoset is composed of a DSO and an InfoObject, and data from the DSO shows up but data from the InfoObject does not show up in the final DSO
My infoset which combines these two:
DSO: Sales Transaction data
Key field: Transaction id
Data fields: Material ID, Price of material , Sales Quantity, etc
InfoObject: Material Id
Attributes: MAterial Manufacturing Cost
Now I want to calculte Profit, and I am trying to integrate the data from these two and store in in ProfitDSO
So I created my Infoset with these 2, and mapped Material Id (from the sales Transaction Data DSO) to the material ID key (in the materialId infobject).
Then I created a transformtion from my Infoset to a new dso storing the transacion id, material id, price, sales quant, cost of manufacturing.
Upon running the transformation, the coz of manufacture is showing up as 0.00 for all the fields.
EDIT: Data when I query the InfoSet is not showing up either. So it is an issue with the Infoset.
Is t because I have linked my DSO and IO with MaterialId, which is not a keyfield for the DSO?
Any ideas how to fix this?
Edited by: nikhil_sap on Jul 28, 2010 1:52 PM

Hi All,
The problem has been solved. Actually I had forgotten to Activate the Master Data after making changes to the Master Data Table (in which I had included the Manucost) .
I was of the opinion that once master data is activated, one does not need to activate it again after making changes, as the tables are created in the first activation itself.
Also, on using "Maintain Master Data" it shows the new data, not the activated master data for InfoObjects. Whereas for DSOs, using "Display Data" it shows the Active data. That caused my assumption that it shows the Active data for InfoObjects too and hence this problem.
Thanks all!
Nikhil

Mapping between Sales Order-Schedule-Line and Delivery-item

Hi together,
I want to extend the Datasource 2LIS_12_VCITM (Delivery-number, -item, Order-number,-item is available) by Sales Order Schedule Line.
Could not find any ERP table (VBEP and LIPS allow a mapping only on item level) for the mapping between Sales Order Schedule Line and Delivery item yet. The use of the extractor 2LIS_12_VCSCL for the extention (e.g. infoset) afterwards is no option.
Thanks for your help in advance!!
Assign full points!!
Sven

Hi Reddy,
thanks for your answer.
I know that I have to add this field.. but the problem is, how to fill this field. I don't know how to map the delivery-item with the schedule line-item.

Navigational Attributes in InfoSets[based on InfoCubes] - BI 7.0

Hi Gurus,
I am using BI 7.0. We tried creating a MultiProvider based on three SD Cubes[Orders/Billing & Delivery] but since the result was being displayed in 3 rows instead of 1, we tried using an InfoSet to see if this would get the results to be displayed in a single line.
In the MultiProvider, we had mapped some of the 'Navigational Attributes' from the underlying InfoCubes after turning them 'ON', but in the InfoSet, I am not able to view the Navigational Attributes of the Cube anywhere.
Are we not able to add 'Navigational Attributes' to InfoSets? Is there a work around for this?
Thanks
Arvind

Hi Arvind,
Check note 1124036 @ www.service.sap.com . Check if you need to apply this.
Also you can add infoobjects themselves in the infoset and join them by keys.
Regards,
Sunmit.

How to add an infoobject in a DSO ,on which Infoset is built

Hi,
How to add an infoobject to a DSO,on which an infoset is build.
In general common infoobjects can be for reporting purpose right?
Do I need to add the new infoobject in all the DSOs.My infoset consists of 6 DSOs.
If my concept is wrong.what is the correct method of extracting infoobjects from DSOs to Infoset.
Regards
Lucky

Hi,
You need to add these two fields in the DSO only. Make sure that you are mapping these two fields in the transformation. After that, drop the data and reload the DSO. Then make changes to the infoset.
By Component, what I mean:
I'll take your example only...
Say, for Material_Group, this data is not coming to DSo data Source. In this case, even if you will add this object to your DSO, you wont be able to map this in the transformation as R3 filed is not available. Ultimately, you wont be able to load data for this. So, its worthless.
But, you have a master data called 0Material. and Material_Group is an attribute of this 0Material.In this case, you will add 0Material to the infoset directly, as a component of infoset(from the tab infoobject), and you will select Material group. In this way, we generally aceess the master data attributes.
Revert for more clarification.
Thanks...
Shambhu

What is Infoset and How to create

HI Experts
Can any one please explain me what is the purpose of INFOSET in BW
and how to create a info Set between A Info Object and Cube
Thanks

Dear bw user,
Check the below link
http://help.sap.com/saphelp_nw04s/helpdata/en/ed/084e3ce0f9fe3fe10000000a114084/content.htm
Purpose is,
1.To join required data from basic InfoProviders
2.This allows building a relational BI data model with unified views for reporting (seeveral InfoProviders,but only one view). Therefore, we recommend keeping data in smaller, basic InfoProviders that can be flexibly joined for reporting purposes.
3. To allow BEx Reporting on a DataStore object without turning the BEx Reporting indicator on
4. To evaluate time dependencies (for example, join time dependent master data InfoObjects)
5. To be able to create self joins and left outer joins
Creatind in simple steps
Infoset is a Virtual Infoprovider.
Click on InfoProvider under modeling in RSA1 > Select InfoArea > right click Create Infoset > give name and description.
Select the ODS / Master Data Object or more than one ODS and maintain the link.
Infoset works on Join operation.
you can include Infocube if it is BI 7.
chk this link...
http://help.sap.com/saphelp_nw70/helpdata/en/a3/96663bd194a978e10000000a11402f/frameset.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2f5aa43f-0c01-0010-a990-9641d3d4eef7
Aslo see this link contents
Creating InfoSets
Prerequisites
Make sure that the objects for which you want to define the InfoSet are active. Create any required InfoObjects that do not
exist already and activate them.
Instead of creating a new InfoSet, you can transfer one of the InfoSets that are delivered with SAP Business Content.
Procedure
1. You are in the InfoProvider tree of the Modeling function area in the Administrator Workbench.
Choose the Create InfoSet function from the context menu (right mouse-click) of the InfoArea in which you want to create an
InfoSet. You get to the Create InfoSet dialog box.
2. Type in the following information for your new InfoSet:
¡ technical name
¡ long description
¡ short description
3. In the Start with InfoProvider section, you determine which InfoProvider you want to use to start defining the InfoSet.
¡ Select one of the object types that the system offers you:
ODS Object
InfoObject
Choose an object.
If you want to choose an InfoObject, it must be a characteristic with master data. The system provides you with the
corresponding input help.
4. Choose Continue. You get to the Change InfoSet screen. For more information on editing InfoSets see Editing InfoSets.
When you create an InfoSet, the system generates a corresponding entry for this InfoSet in the subtree of the InfoArea. The
following functions are available from the context menu (right mouse-click) of this entry:
Change
Delete
Object overview
Editing InfoSets
Prerequisites
Before you can get to the screen where you edit InfoSets, the following prerequisites have to be met:
You have created a new InfoSet.
You have selected the Change function from the context menu of an InfoSet entry in the InfoProvider tree of the Modeling
function area in the Administrator Workbench.
You have called the InfoSet Builder transaction, and selected the Change function. You can find additional information
under Additional Functions in the InfoSet Builder .
Procedure
1. You are in the Change InfoSet screen.
Choose a layout for the InfoProvider tree:
InfoArea
InfoProviders Used
All ODS Objects
All InfoObjects
For more information on the screen layout, particularly the layout of the InfoProvider tree, see Screen Layout: Changing
InfoSets.
2. Use the function Where-Used List via AWB to determine which BW objects use the InfoSet that you have selected. You get to
the Administrator Workbench: Where-Used List screen. You are able to work out what would happen in the system if you made
changes to the InfoSet. This helps you to decide whether or not it is sensible to make these changes at this particular point
in time.
3. You define the InfoSet by inserting one or more InfoProviders into the join.
There are several ways of inserting an InfoProvider into the join control:
¡ From the InfoProvider tree:
§ In the InfoProvider tree, double-click on the entry that corresponds to the InfoProvider that you want to add to the join
control.
§ Use the drag-and-drop function to move the InfoProvider into position.
¡ Choose the Add InfoProvider function, to add a particular ODS object or a particular InfoObject independently of the
current layout of the InfoProvider tree. You get to the dialog box of the same name. Enter the data that the system asks you
for.
If you know the technical name of the InfoProvider that you want to add, this method is quicker than switching the layout of
the InfoProvider tree.
When this function is complete, the InfoProvider that you selected is displayed in the join control. For more information on
the structure of the join control, see Join Control.
4. Define the join conditions. For more information see Defining Join Conditions.
5. You can get general information such as object version, date created and date changed via Goto ® Global Settings. You can
also set the indicator Most recent Reporting for InfoObjects from here. You can find additional information under Most recent
Reporting for InfoObjects.
6. Via the button Documents, which appears on the pushbutton bar, you can access document editing for this InfoSet.
7. You can use Check to check the correctness of the InfoSet definition. The log display is shown in the screen area under
the join control.
8. Save the InfoSet. The log display is shown in the screen area under the join control.
9. Activate the InfoSet. After activation, the system executes the checks. The result of the activation is displayed in the
log in the screen area under the join control.
Additional Functions in the InfoSet Builder
You can also use transaction RSISET to call up the InfoSet Builder when you want to edit an InfoSet. Select the InfoSet that
you want to edit. Value help is available for this. Additional functions are also available to help you edit and manage your
InfoSet.
Compare
You use this function from the main menu to check if the InfoProviders used in the InfoSet have been changed and the InfoSet
needs to be adjusted as a result. For more information, see Matching InfoSets.
Jump to object maintenance
You use the InfoObjects and ODS Objects functions to jump to the maintenance screen for the InfoProviders included in the
InfoSet definition.
Info functions
There are various info functions on the status of the InfoSets:
The Object Catalog Entry
The log display for the save, activate, and delete runs of the InfoSet.
Display in tree
You use this function to display in a tree structure all the properties of the A version (active) of the selected InfoSet.
Header data
InfoProvider and its fields
On condition
Wherecondition
The display is empty, if no active version is available.
Version comparison
You use this function to compare the following InfoSet versions:
The active (A version) and modified (M version) versions of an InfoSet
The active (A version) and content (D version) versions of an InfoSet
The modified (M version) and content (D version) versions of an InfoSet
The Display InfoSet screen appears. Depending on which option you choose, the system displays either all of the differences
between the two versions of the selected InfoSet or all of the properties of both versions in a tree structure.
Transport connection using AWB
You use this function to transport an InfoSet into another system.
The Administrator Workbench: Transport Connection screen appears.
The system has already collected all the BW objects that are needed to guarantee the consistency of the target system.
InfoSet data display
You use this function to access the data target browser. If you have already loaded data into the InfoProviders included in
the InfoSet, you can display this data.
Delete
You use this function to delete an existing InfoSet.
Copy
You use this function to copy an existing InfoSet and, if necessary, edit it further.
Show/hide technical names
You can use this function to show alias names for fields. These alias names are necessary in InfoSets, for example to be able
to map self joins. Field alias names start with F, followed by a five-digit number.
Defining Join Conditions
Use
A join condition determines the combination of records from the individual objects that are included in the resulting set.
Before an InfoSet can be activated, the join conditions have to be defined in such a way (as equal join condition) that all
the available objects are connected to one another either directly or indirectly.
Usually, however, only rows containing a common InfoObject or rows containing InfoObjects that share the same basic
characteristic are connected to one another.
Connect tables T1 and T2 using a join and set as a join condition that the F1 field from T1 must have the same value as F2
from T2. For a record from table T1, the system determines all records from T2 for which F2(T2) = F1(T1) is true. In
principle, as many records from T2 can be found as required. If one or more records are found, the corresponding number of
records is included in the result set, whereby the fields from T1 contain the values from the record from T1 under
consideration, and the fields from T2 contain the values of the records found from T2.
Procedure
There are various ways of defining join conditions:
Using a mouse-click
Position the cursor over a row in an InfoObject. Press the left mouse-button and, keeping the left mouse-button pressed down,
trace a line between this row and a row in another object. Providing that the join condition between the two rows that you
have indicated is a valid join condition, the system confirms the join condition by displaying a connecting line between the
two rows.
Using the Link Maintenance pushbutton
You get to the Link Maintenance dialog box.
In a tree structure on the left-hand side of the screen, all of the InfoProviders that are already included in the join are
displayed along with their fields or attributes. If you double-click on one of these fields or attributes, the system
displays on the right-hand side of the screen all of the fields or attributes with which you are able to create a join
condition.
In the Selection column, set one or more of the indicators for the fields or attributes for which you want to create a join
condition. The system generates valid join conditions between the fields or attributes that you specify.
You use the Delete Links pushbutton to undo all of the join conditions.
You use the All Characteristics or the Basic Characteristics Only pushbutton to choose between the corresponding display
variants.
We recommend that you use the Basic Characteristics Only option. The All Characteristics setting displays all of the
technical options involved in a join. If you are not able to find a join condition on the basic characteristic level, then
the All Characteristics setting is useful, but this is an exceptional case.
When you have finished making your settings, click on the Continue icon.
We recommend this method, because the system searches for all the possible join conditions for any field or attribute that
the user specifies, ensuring that the join conditions are defined without errors.
Using the Context Menu Left Outer Join Inner Join
Usually inner-join operators connect all the objects in a join to one another. You can also connect each object with any of
the many other objects by using a left outer join operator.
You can find additional information about usage and special features under Left Outer Join.
If you want to use a left-outer join operator to connect an object, select the object and choose the corresponding function
from the context menu.
The system displays all of the valid join conditions that originate from this object. The connecting lines that represent
these join conditions are labeled as Left Outer Join . InfoProviders, on which a left outer join condition is affixed, are
differentiated by color from the InfoProviders that are connected using an inner join operator.
If you used a left outer join operator to connect two objects, you have to make sure that all on conditions are linked except
for these two objects with the formulation of join conditions.
Note that you cannot add an object, which you have already connected by using the left outer join operator, to another
object.
If you want to use an inner-join operator instead of the left-outer join operator, select the object that you want to
connect, and choose the Inner Join option from the context menu. Again the system displays all the valid join conditions that
originate from this object, and labels the connecting lines accordingly.
Result
Once the join conditions have been defined in such a way as to connect all the available objects to one another, either
directly or indirectly, the InfoSet is ready to be activated.
You click on the Check pushbutton in the pushbutton toolbar to find out if these preconditions for the activation have been
met.
For objects that are joined by a left-outer join operator, there is one extra condition that has to be met, namely that all
the other objects have to be connected to one another either directly or indirectly.
http://help.sap.com/saphelp_erp2004/helpdata/en/ed/084e3ce0f9fe3fe10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/ed/084e3ce0f9fe3fe10000000a114084/content.htm
http://help.sap.com/saphelp_nw70/helpdata/en/a3/96663bd194a978e10000000a11402f/frameset.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2f5aa43f-0c01-0010-a990-9641d3d4eef7
Hope itr helps
Regards
Bala
Also

Infoset resulting multiple results at query level

Hi,
I have joined 1 DSO and 1 Infocube in Infoset.. Mapped Plant, Material and Batch
DSO
Plant     Material      Batch      Caldate         Qty
P1          M1          B101          01/02/2014     1000
P2          M2          B102          05/02/2014     2000
Infocube
Plant          Material         Batch     Caldate               %
P1               M1               B101          02/02/2014          20
P1               M1               B101          05/01/2014          20
P2               M2               B102          07/02/2014           15
I'm considering date only on DSO and ignoring Infocube date. When I execute the report for the month of February, report output is as follows.
Plant   Material     Batch     DSODate         Qty           %
P1          M1               B101     01/02/2014          1000          40 (Summing up with January Date)
P2          M2               B102     05/02/2014          2000          15
I want data % value to be 20%.
Is there any possibility to change at query level or join level.
If we have one line item, data is correct but not the case with multiple line items.
Kindly do the needful!
Thanks
SS

Hi,
When you join the two infoproviders in the infoset ignoring infocube date, you are creating as many records for each record in DSO. That means for the first record the infoset creates :
Plant     Material      Batch      Caldate         Qty     %
P1          M1          B101          01/02/2014     1000 20   (for first row in infocube)
P1          M1          B101          01/02/2014     1000   20 (for second row in infocube)
I also think same as Anshu, you have all the common characteristics, you can as well use a multiprovider.
regards
Yasemin...

Multiprovider Mapping Issue # Values in the query output

Q . I am getting # values for the free chars and no values for some of the KPIs
I have created this report on top of a multiprovider which has a huge number of cubes ( exceeding 10 ) , four DSOs and a couple of infosets , and the query which i am creating should get values from 3 cubes only .
1.I have placed Global Restrictions ( Char Restrictions ) on top of the query with 3 cubes
2.had restricted the KPIs with the relevent infoproviders .
3.I have mapped all the chars and key figures used in this query with relevent infoprovider restrictions
But Still when i execute the Query i see the following formatt of my Output
Free Char          KPI1            KPI2
       filed3                                  10
       field2                                  09
       field1                                  07
       field0                                  06
Not assigned       12.00              0
Not assigned       12.00              0
Not assigned       12.00              0
Please provide me input for why i am getting this kind of out put with Not assigned values and indifferent values for KPIs and what should be done to solve this problem .

Hi,
You mention that there are several InfoProviders underlying your MultiProvider. Check the characteristics and free chars you are using in your query - all of these should be present in all the underlying InfoProviders. For example, if you are using 0COMP_CODE in your query, and 0COMP_CODE is not present in one of the underlying DSOs, then they Key Figure values coming from that DSO will be shown against # (Not Assigned) value for 0COMP_CODE.
Easy way to find out - go to LISTCUBE and enter your MP name. Display all the chars and free chars that are present in your query. Also display the INFOPROVIDER field. Look at the data, and see if there are any characteristics that are blank for all records for any particular InfoProvider. If you find any such chars, then that may be the reason behind your problem.
To avoid this sort of problem, you can use Constant Selection http://help.sap.com/saphelp_nw70/helpdata/en/46/91f0f090ea13e8e10000000a155369/content.htm
Regards,
suhas

Mapping table for the hierarchies in bw & R3

Hello,
We have a requirement of createing a mapping table for the hierarchies of one of the BW-object and the corresponding R/3-Hierarchies.
sturucture on table should be as given below,
BW-Hierarchy Name | R/3- Hierarchy Name | Frequency of loading |
please advice.
Thanks
NM

Hi,
Product Group is master data for material master. It is part of Matreial Clssification data in R/3.
Please check if you are having the same already loaded as attribute of Material master. I guess it will be there, if it s not there then you should try to load the same in material master object which you are using in all the cubes.
If the maintinenece in master data is nopt possible then you got to populate the same in cube.
There will be a combination of keys (materail/plant/prduct family etc.. ( for which Product group will be unique). then load product with the help of these key combinations in all the cubes via update routine.
There is one more way to have this but which is performance intensive.
You may create one master data object called Product Group and keep material number as attribute (with compunding all other key fileds to get the unique combination). Then you may create an infoset using cubes and this master data object. Join the materail numbers in all. Display this object in report.
I hope it will help.
Thanks,
S

Selfjoin in Infoset and it's use?

Hi All,
I want to know what is a selfjion in Infoset,and when we need this particular join. Can someone help me with one example.
Regards,
G S Ramanjaneyulu.

I think that he was talking about C-like structures (Struct), rather than Struts, the framework.
Anyway, the way to mimic a C-Struct in Java is to make a class with all public members and no methods. There is no equivalent in Java of a Union, however, so if you have to deal with Structs that have Unions within them, you're out of luck. Also, I'm not sure how the sizes will map from a C Struct to a Java class. You'll probably have a mismatch.
Paul

Mapping BW TO CRM?

Hi Gurus
How to Map BW info cube and BW info set to CRM
Cheers
Mahi

hi
Using InfoSets and BW Queries in the Segment Builder
InfoSets and BW queries are used to access business partner master data (stored for example in the R/3 System) and transactional data stored in the SAP BW System respectively.
The attributes used within these InfoSets and BW queries can be fields belonging to:
·         Business partner tables (business partner master data)
·         Key figures determined in SAP BW
·         Marketing attributes
InfoSets
To create InfoSets, from the SAP Easy Access menu, choose Architecture and Technology ® ABAP Workbench ® Utilities ® SAP Query ® InfoSets.
Any InfoSets you create for use in the Segment Builder must be created in a cross-client work area. Therefore, on the interface for creating InfoSets, you should first choose Environment ® Query Areas, and select Global Area (Cross-Client). This setting ensures that your InfoSets appear for selection in the input help for the field InfoSet when creating data sources (Marketing ® Segmentation of Business Partners ® Marketing Segments ® Maintain Data Sources for Segment Builder).
For information on how to create InfoSets, see the SAP Library under mySAP Technology Components ® ABAP Workbench (BC-DWB) ® SAP Query (BC-SRV-QUE).
Tips for InfoSets
       1.      The most important and simplest point is that the Segment Builder creates target groups containing business partners. Therefore the InfoSet must make its selections using fields relating to the business partner and must be able to return business partner keys. Ideally these keys are GUIDs. If this is not possible (for example because this InfoSet lies in a system in which the GUID is not known, such as an SAP BW or an SAP R/3 System) then it must be a key that can be converted into a GUID in CRM. If this is the case, you must specify a function module in data source maintenance to perform the conversion in the field Function Module). For InfoSet queries, for example, we recommend function module CRM_MKTTG_PF_BP_TAB_TO_GUID, and for other data sources, CRM_MKTTG_PF_CONV_ID_TO_GUID is available.
If the InfoSet is a table join, then it is safest to use BUT000 as the basis table.
       2.      If you are using a report program, then the structure belonging to this report must contain the business partner GUID (or a field that can be converted into the GUID).
       3.      The InfoSet should be constructed so that it contains every field that is required for selection in the Segment Builder and these fields only! When you create an InfoSet, the system displays the dialog box InfoSet: Title and Database. On this dialog box, ensure that you select the field No automatic text recognition (under Options) since otherwise the system will generate the texts for all the fields in the InfoSet behind which text fields are defined. These fields are then written into the InfoSet which may lower performance.
       4.      Do not build one large InfoSet containing a large number of joins. Instead, build InfoSets which join only those tables required for the selection attribute to be created. For example, if you want to create the selection attribute Date of Birth your InfoSet should use table BUT000 only (because Date of Birth is one of the fields in this table). It is not advisable to read the date of birth from an InfoSet which joins the BUT000 with the address table ADRC.
Tips for BW Queries
Query Definition
       1.      In the Business Explorer Analyzer (Business Explorer ®Analyzer) ensure that you set the indicator "Release for OLE DB for OLAP" for the query (under Properties).
       2.      Ensure that your BW user is a dialog user, since otherwise the input field for queries in data source maintenance will not work (RFC connection between SAP BW and SAP CRM). To check this setting, in the BW system choose Tools ® Administration ® User Maintenance ® Users. Under the Logon Data for the relevant user, ensure that Dialog is selected as User type.
       3.      Do not specify any variables as "required".
       4.      Ensure that the query has business partner as info object.
       5.      Ensure that the business partner is in the row, the key figures in the column(s).
       6.      Do not define any conditions for the key figures in the query itself. Instead define conditions in the Segment Builder by specifying filter values for the relevant attributes.
Performance Points:
To ensure the best possible system performance, try where possible to avoid:
       1.      Unnecessary characteristics, attributes, or key figures
       2.      Superfluous conditions or variables
       3.      Complex key figures
       4.      Large cubes
       5.      Complex hierarchies
       6.      A lot of coding in variables filled by means of user exits
In addition, specify for characteristics either variables or restrictions but not both together.
best regards
ashish

Mapping in Infoset

Similar Messages

Maybe you are looking for