Activities in Customizing BI ICM Interface in SAP CRM 
Use this procedure to perform the CRM configuration activities necessary to transfer BI data to ICM through a general BI interface.
You have defined your BI InfoSources.
Define RFC Destination Definitions
In Customizing for the CRM system, you set up an RFC destination for ICM, by choosing:
When you create the RFC destination for the ICM engine (ERP system), ensure that you enter the required information for the process, including the description, target system, message server, group, logon, and so on.
Note
This is a standard SAP procedure for setting up any other RFC destination within CRM. You perform this step in this procedure only if you have not already set the RFC destination to support any other processing.
In Customizing for the CRM system, you set up the RFC destination for the ICM engine and the BI logical system, by choosing:
On the RFC Destination for ICM Engine and BI System page, enter the following:
The ICM RFC destination.
The BI system destination.
This is client-specific. You can connect to more than one BI system by entering multiple BI system destinations, separated by a comma or space.
The queries selected from the BI system(s) provide the DataSource for the transfer interface generated in a later step.
Define Transfer Application
In Customizing for the CRM system, you define a BI-ICM transfer application, by choosing:
You use this step to specify the name of a new transfer application. A transfer application is a generated application that transfers extracted BI query results to the ICM commission case interface to drive the commission process in ICM. Whereas you can define only one transfer application per ICM application, one transfer application can support multiple queries.
Although you enter an ICM application name, the purpose at this stage is to create the map between the applications and, in most cases, the application does not yet exist.
On the BI-ICM Transfer Application page:
Choose New Entries.
Enter the BI-ICM Transfer Application.
Enter the ICM Commission Application.
Enter short and long descriptions to help you identify the Transfer Application.
Save your entries.
Note
After you have completed other steps in the procedure, you return to this activity to make it productive, by choosing Transfer Application productive? .
Select Query and Customize Query Results
In Customizing for the CRM system, you identify the BI ODS or InfoCube and Query, by choosing: .
You can specify one or more BI Queries and Infoproviders (InfoCube or ODS tables) as sources of data for a BI-ICM Transfer Application. The BI interface relies on the query as its data source for ICM.
On the Identify Infoprovider and BI Query page:
Choose New Entries.
Choose the BI-ICM Transfer Application.
Choose the BI query.
Choose Get Query Text to complete the remainder of the field entries
Save your entries.
In Customizing for the CRM system, you populate the CRM selection table with all fields available for selection from the BI query, by choosing: .
You select the BI query fields that you want to include in the field offering structure which is ultimately available to ICM. The choices you make during this activity determine the data that is passed on to the ICM Commission Case interface.
On the BI-ICM BI Query Field Customizing page:
Choose the BI-ICM Transfer Application.
Choose the BI query
Choose Get Query Metadata.
This populates the table BI-ICM with data from the selected query.
Choose Used in ICM App next to each field that you want to include in the extract.
Within the BI-ICM BI Query Field Customizing table:
Field type is the type of info object from the BI query. InfoObjects are subdivided into characteristics, key figures, units, time characteristics, and technical characteristics. This is a read-only field.
Data type is the data type of the field in the ABAP data dictionary. Although it is retrieved from the data definition in BI, it can be modified. When objects are generated in CRM for this BI field, the data type specified here is used. Example data types include currency field stored as DEC, floating point number, and character string (this is the technical definition of the field).
Ref. field (reference field) must contain the appropriate currency and unit of measure values to ensure that the structure is generated correctly.
Group by allows you to group multiple BI records into a single commission case. For example, if your BI data is comprised of header records of an order and separate line item records of an order, the header records and line item records can be grouped together into a single commission case.
ChooseDisplay for each key figure field that you want to make available in the BI Extraction Log tab generated in a later process. The Commission Clerk sees this tab when executing the transaction, by choosing: .
Caution
Unless you choose Used in ICM App for a field, it is not included in the data extracted for use with ICM (not all data may be transferred directly, in some cases the extracted data may be used in a user exit or with the function module to derive the value(s) for fields in the ICM commission case interface.)
In Customizing for the CRM system, you specify a subset from query result fields, by choosing:
This generates the query result structure corresponding to the BI query within the transfer application.
On the Generate Query Result Structurepage:
Choose the BI-ICM Transfer Application.
Choose the technical name of the BI Query providing the ICM data.
Choose Execute.
For more information about verifying this activity, see Trouble Shooting.
In Customizing for the CRM system, you identify commission case grouping criteria, by choosing:
This generates the field offering structure in the ERP Data Dictionary. After you generate the field offering structure, you can select it within the ICM application construction tool.
After ICM generates a field offering structure, you can place it into a development class, which is used to contain all development objects that must be developed, maintained, and transported together. Typically, the objects that make up a transaction belong to one development class. Customer development classes begin with Y or Z. This field is a placeholder for that class. Currently, you can create the objects in the $TMP class, which cannot be transported.
Note
This is a client-dependent activity.
On the Generate Field Offering in ICM page:
Choose the BI-ICM Transfer Application.
Choose the Technical name of the BI query.
Enter the ICM Package/Development Class (or use the temporary package $TMP.
Choose Execute.
Note
This generates the field offering only within the ERP system. The field offering within CRM is generated in a previous step.
For more information about verifying this activity, see Trouble Shooting.
Caution
When you review the Application Log (as described in Troubleshooting) check the last line of the log for the field offering structure name because you use the name during activities in Activities in Customizing BI ICM Interface in ERP (ICM). Note the field offering structure name because it is possible that this log can be deleted.
In Customizing for the CRM system, you set up number ranges unless the business object ID in the query exists, by choosing:
You use this activity only when you must establish the number range limit when relying on the interface to assign values to the field business object ID. This typically occurs when the query you are using to transfer data to CRM-ICM returns aggregated data. Unless the business object ID exists, the BI-ICM Interface generates a business object ID using the number range intervals.
You have completed the CRM configuration activities required prior to generating or regenerating your ICM application. These are the initial steps required for CRM Customizing. You typically complete the remaining CRM configuration steps after you have completed setting up your ICM application.