Using InfoSets and BW Queries in Segmentation
InfoSets enable you to access CRM data, for example business partner tables (business partner master data).
BW queries enable you to access transaction data in SAP NetWeaver Business Warehouse (BW) as well as BW attributes from sales data or contact data that may be stored in an ERP system, for example.
Note
You can use BW queries in classic segmentation only.
To create InfoSets, from the area menu choose .
Any InfoSets you create for use in segmentation must be created in a cross-client work area. Therefore, on the interface for creating InfoSets, you should first choose , and choose Global area (cross-client)
. This setting ensures that your InfoSets appear for selection in the input help for the InfoSet
field.
The InfoSets mentioned here originate from SAP NetWeaver (Classic InfoSet) and should not be confused with the InfoSets from SAP Business Warehouse, which as of SAP BW 3.0 can be created in the Administrator Workbench.
For information on how to create InfoSets, see SAP Library under .
Note the following when working with InfoSets:
Since the target groups contain business partners, 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 is in a system in which the GUID is not known, such as an SAP NetWeaver BW or an SAP ERP 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 Function Module
field. 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.
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).
The InfoSet should be constructed so that it contains every field that is required in segmentation and only these fields. When you create an InfoSet, the system displays the dialog box InfoSet: Title and Database
. On this dialog box, ensure that you select the No automatic text recognition
field (under Options
) since otherwise the system generates the texts for all the fields in the InfoSet behind which text fields are defined. These fields are then written to the InfoSet, which may impair performance.
Do not build one large InfoSet containing a large number of joins. Instead, build InfoSets that join only those tables required for the selection attribute to be created. For example, if you want to create the 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 that joins the BUT000 with the address table ADRC.
Note the following points regarding the definition of BW queries:
In the Business Explorer Analyzer, ensure that you select the Release for OLE DB for OLAP
checkbox for the query (in the query properties).
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 NetWeaver BW and SAP CRM). To check this setting, in the BW system choose . Under the Logon Data
for the relevant user, ensure that Dialog
is selected as the user type.
Do not specify any variables as being required.
Ensure that the query has the InfoObject Business Partner
.
Ensure that the business partner is in the row and the key figures are in the columns.
Do not define any conditions for the key figures in the query itself. Instead define conditions during segmentation by specifying filter values for the relevant attributes.
Only use queries that are based on InfoCubes. Queries that are based on ODS objects and BW InfoSets are only partially supported.
To ensure the best possible system performance, try where possible to avoid:
Unnecessary attributes or key figures
Superfluous conditions or variables
Complex key figures
Large cubes
Complex hierarchies
Extensive code in variables filled by means of user exits
In addition, specify for attributes either variables or restrictions but not both together.