!--a11y-->
Integration of CRM Products in the Business
Information Warehouse 
The integration of CRM Products in the SAP Business Information Warehouse (BW) is divided into two essentially different areas. The standard part of CRM Products is transferred to the BW System using standard extractors. Set types created by customers are treated differently. In these cases, an extractor is generated in the CRM Server for each customer-defined set type.
SAP set types are mapped to the BW System using the InfoObjects CRM or BBP Product (0CRM_PROD/0BBP_PROD), CRM Product Sales View (0CRM_PRODSL), CRM Financing Product (0CRM_PRFI), CRM Financing Product Sales View (0CRM_PRFISL), and IP (0IPM_PROD). There are several DataSources for the attributes of these InfoObjects, for which there is already a mapping in the delivered BW business content. This delivered business content only needs to be activated.
An extractor is generated for customer-defined set types, allowing all attributes in the set type designated as relevant to BW to be transferred to the BW System. If a field is also designated as relevant for selection, the data selection can be restricted later from the BW system using this field. If the set type contains attributes which require a text extractor these are also generated, if necessary. No action is taken on the BW side.
Before the DataSources generated in CRM can be transferred to the BW System and the missing meta data (InfoObjects and transfer rules) created, the modeling must be specified within BW. There are basically two options.
All DataSources generated provide master data on products or the sales view of the product (see above). The attributes that need to be transferred to the BW System can therefore be transferred as attributes of the InfoObjects 0CRM_PROD etc. As a result, the total number of attributes of these InfoObjects will increase considerably and may reach the technical limit (249). It is also worth bearing in mind that the number of attributes provided in the SAP standard version of CRM Products may increase in future releases.
If quite a large number of new attributes is anticipated, you are advised to create a new InfoObject ZMY_PROD (or similar) and append the generated attributes to it. If the number of attributes is very high, you may want to create several of these InfoObjects and group the attributes thematically. The individual InfoObjects will therefore remain compact and the number of attributes required later in a query can be better restricted.
This has already been done in the standard part of CRM Products, for example, by introducing the InfoObjects 0CRM_PRFI and 0CRM_PRFISL for the financing product, which resembles an industry solution in character and has a large number of attributes of its own.
The business scenario Intellectual Property Management uses the InfoObject 0IPM_PROD for attributes specific to intellectual properties.
The modeling of the master data is very important for transaction data and queries. A query for financing products, for example, must contain the InfoObject 0CRM_PRFI (for accessing attributes specific to the financing product) and the InfoObject 0CRM_PROD (for attributes of the standard part of the product). This will enable both the attributes specific to the financing product as well as the general product attributes to be accessed. Each new (customer-defined) InfoObject such as ZMY_PROD may also need to be included.
When the transaction data is transferred, the product GUID (key in BW) contained in the transfer structure must be copied to the relevant fields (communication structure, update rules). This is possible because all InfoObjects for the product have the same data type and length.
You should first replicate the generated master data and text DataSources from the CRM Server to the BW System from the Administrator Workbench.
To create the required InfoObjects and transfer rules, you can also use the meta data generator (transaction CTBW_META). It allows you to both extend an existing InfoObject/InfoSource as well as create a new InfoObject for CRM Products (for example, ZMY_PROD).
