Integration in SAP BW 

The integration of SAP Products in the SAP Business Information Warehouse (BW) is divided into two essentially different areas.

SAP Set Types (Standard)

The SAP set types of the SAP Product are transferred with DataSources to the BW and mapped using the InfoObjects 0CRM_PROD(Products Sales View) or 0BBP_PROD (Products Purchasing View). There are several DataSources for the attributes of these InfoObjects, for which there are already a mapping rules in the standard BW business content. This standard business content only needs to be activated.

The following DataSources are provided for SAP Product:

¡        DataSource	¡        Use
¡        0PRODUCT_ATTR	¡        General attributes of the product
¡        0PR_PROD_VAR_ATTR	¡        Attributes for product variants
¡        0PR_PROD_UNIT_ATTR	¡        Attributes for units of measure
¡        0PR_IL_PROREF_ATTR	¡        Attributes of the product references in individual objects
¡        0PRODUCT_HIE R	¡        Product Hierarchy
¡        0PR_CATEGORIES_ATTR	¡        Product category assignments
¡        0PR_GTIN_ATTR	¡        Attributes for Global Trade Item Number
¡        0PR_STATUS_ATTR	¡        Attributes for product status
¡        0PR_SALES_CATEG_ATTR	¡        Attributes for sales category
¡        0PR_PURCHASE_CATEG_ATTR	¡        Attributes for purchasing category
¡        0PRODUCT_TEXT	¡        Product texts
¡        0PR_GTIN_TYPE_TEXT	¡        Global Trade Item Number texts
¡        0PR_IL_RELDIR_TEXT	¡        Product relationship texts
¡        0PR_IL_RELTYPE_TEXT	¡        Relationship type texts
¡        0PR_OBJECT_FAMILY_TEXT	¡        Texts on the object family in individual objects
¡        0PR_TYPE_TEXT	¡        Product type texts
¡        0PR_ID_CMP_TEXT	¡        Texts on the combined product ID
¡        0PR_STAPROSYS0_TEXT	¡        Archiving status texts
¡        0PR_STAPROSYS1_TEXT	¡        Texts on the central lock of a product
¡        0PROD_CATEG_ATTR	¡        Category attributes
¡        0PROD_CATEG_HIER	¡        Hierarchy via categories
¡        0PROD_CATEG_TEXT	¡        Category texts

 

For more information, see Note 673053.

Customer-defined set types

A separate DataSource is generated in the application system for each customer-defined set type, if at least one attribute has been flagged as BW-relevant. A DataSource 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 DataSource, these are also generated. However, the system does not generate objects in BW; these must first be assigned by the application.

Before the DataSources generated in the application system can be transferred to BW, and the missing meta data (InfoObjects and transfer rules) created, the modeling must be specified within BW. There are basically two options:

·        Option 1: Transfer new attributes to existing InfoObjects

All generate DataSources return product master data. The attributes that are to be transferred to the BW system can therefore be transferred as attributes of the InfoObject 0CRM_PROD (Product Sales View) or 0BBP_PROD (Products Purchasing View) As a consequence, the total number of the attributes of this InfoObject increases considerably and may reach the technical limit of 249 attributes.

·        Option 2: Create a new InfoObject

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 attributes to it. This InfoObject must match the InfoObject 0CRM_PROD or 0BBP_PROD in data type and length.

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.

The modeling of the master data is very important for transaction data and queries.

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 application system to the BW System from the administrator workbench.