53 sap crm product

8/10/2019 53 Sap Crm Product

1/56

PRINT FROM SAP HELP PORTAL

Document:Products

URL:http://help.sap.com/saphelp_crm700_ehp02/helpdata/en/ed/bfb2ce6a6a46af92172c4ff901f125/frameset.ht

Date created:July 17, 2013

2013 SAP AG or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the expresspermission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary

software components of other software vendors. National product specifications m ay vary. These materials are provided by SAP AG and its affiliated companies (" SAP Group") for

informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only

warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein

should be construed as constituting an additional w arranty. SAP and other SAP products and services mentioned herein as wel l as their respective logos are trademarks or

registered trademarks of SAP AG in Germany and other countri es. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information

and notices.

Note

This PDF document contains the selec ted topic and its subtopics (max. 150) in the selec ted structure.Subtopics from other structures are not included.

PUBLIC 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 1 of 56
http://help.sap.com/saphelp_crm700_ehp02/helpdata/en/ed/bfb2ce6a6a46af92172c4ff901f125/frameset.htmhttp://help.sap.com/


2/56


3/56

In the documentation about set types and attributes, products includes both products and objects.

Set types enable groups of data fields to be assigned to a product, and the product to therefore be modeled in detail in the system.

Set types and attributes are used together with product hierarchies and categories. The combination of these elements enables the relevant set types to be made

available on the Productpage and therefore used to describe the product.

Structure

Set types are assigned to categories and not to products directly. By assigning set types to categories, and then in turn assigning the categories to products, you

can make available the data you require to describe your products.

The mechanism is illustrated below:

See also Product Hierarchies.

Standard Set Types

Set types and attributes can either be standard set types provided by SAP, or set types and attributes you have defined yourself to meet your own requirements.

SAP provides the following standard set types:

General Set Types

Technical Name Description

COMM_PR_SHTEXT Descriptions

COMM_PR_UNIT Units of Measure

COMM_PR_LGTEXT, COMM_PR_LGTEXT1, COMM_PR_LGTEXT2 Notes/Sales Notes

CRMM_PR_SALESA Sales: Control Fields, Quantities

CRMM_PR_SALESG Sales: Groupings

CRMM_PR_TAX Taxes

Set Types for Materials


COMM_PR_MAT Basic Data on Materials

COMM_PR_GTIN Gobal Trade Item Numbers

CRM_PR_RESIDVL Financing-Dependent Attributes

Set Types for Services


CRMM_PR_BTR Transaction Control Fields

CRMM_PR_SRVDUR Duration of Work

CRMM_PR_SRVRR Resource Requirement

CRMM_PR_SRVENT Default Values for Service Contracts

SERVICEPLAN Service Plan

CRM_SERIALNUM Serial Number Processing in Service

Set Types for Warranties

Note


Page 3 of 56
http://help.sap.com/saphelp_crm700_ehp02/helpdata/en/ba/ad5bed29fa4ce9a74e77884ba6785b/content.htmhttp://help.sap.com/saphelp_crm700_ehp02/helpdata/en/46/57672b01a208e7e10000000a114a6b/content.htmhttp://help.sap.com/saphelp_crm700_ehp02/helpdata/en/46/57672b01a208e7e10000000a114a6b/content.htmhttp://help.sap.com/saphelp_crm700_ehp02/helpdata/en/46/57672b01a208e7e10000000a114a6b/content.htmhttp://help.sap.com/saphelp_crm700_ehp02/helpdata/en/46/57672b01a208e7e10000000a114a6b/content.htmhttp://help.sap.com/saphelp_crm700_ehp02/helpdata/en/af/ec5984c75a4e3fad52c57e6612f23b/content.htmhttp://help.sap.com/saphelp_crm700_ehp02/helpdata/en/dc/ba073093ae42429905e9279ff3fd73/content.htmhttp://help.sap.com/saphelp_crm700_ehp02/helpdata/en/c3/2e420f87014444a5c7a33446ddbc8b/content.htmhttp://help.sap.com/saphelp_crm700_ehp02/helpdata/en/be/e0f56f54cd4c5aa1cc1c7b5fc2ddab/content.htmhttp://help.sap.com/saphelp_crm700_ehp02/helpdata/en/48/a13901011b4b578054999719c3e955/content.htmhttp://help.sap.com/saphelp_crm700_ehp02/helpdata/en/4f/35beabc7124e1089688138e646bcd1/content.htmhttp://help.sap.com/saphelp_crm700_ehp02/helpdata/en/76/c74eab0ef44aef89ddd48b15aa34fd/content.htmhttp://help.sap.com/saphelp_crm700_ehp02/helpdata/en/46/57447a01a208e7e10000000a114a6b/content.htmhttp://help.sap.com/saphelp_crm700_ehp02/helpdata/en/24/e441616a844bad8e01edcd34488aa8/content.htmhttp://help.sap.com/saphelp_crm700_ehp02/helpdata/en/66/6cdd6c1d044dedb645e497e7e59e68/content.htmhttp://help.sap.com/saphelp_crm700_ehp02/helpdata/en/46/5754c601a208e7e10000000a114a6b/content.htm


4/56


CRMM_PRWTY Warranty

CRMM_PRWTY_CAT Warranty Catalog Data

CRMM_PRWTY_SRV Warranty Services

CRMM_PRWTY_CNT Warranty Counter Data

Set Types for Other Product Types

Product Type Set Types

Financing Financing Set Types

Financial Service Set Types for Financial Service Products

Intellectual Property Management Set Types for Intellectual Property Management

Definition of Set Types and Attributes

Set types enable you to model the data required about your products in detail. There are various ways in which set types can be modeled. When a set type is

created or changed, the system generates all necessary system objects such as database tables and function groups automatically. Once you have defined aset type in a particular way and it is being used, it cannot simply be changed.

This functionality is designed for those responsible for modeling products in your system.

Features

Set Types

The table below outlines the options available to you when working with set types. Depending on which settings you make, other options may or may not be

available:

Set Type Key Fields Multiple-Value Attributes Organizational Dependency

Multiple use No Yes Can be organization-dependent

Yes No

No multiple use No No Organization-independentYes No

Multiple Use

This is a technical setting which does not directly affect the appearance of the set type. It does however influence which other options are available to you and the

performance of your system:

By setting the Multiple Useindicator, each data record of a set type is assigned indirectly to a product using an assignment table. This means you could

assign the attribute values of a set type to more than one product in future releases. For example, general data such as the units of measure for a product is

likely to be the same for several products.

By not setting the Multiple Useindicator, each data record is assigned directly to one product. This is beneficial for performance and data volume, particularly

where large numbers of products are expected. If you are expecting a large number of products, and it is not likely that the various data records of a set type

will be used by more than one product, you should not set this indicator. For example, the serial number of a technical device will probably not be used by

more than one product.

Key Fields

If at least one of the attributes of a set type is designated as a key field several entries can be made for each field of this set type when creating or changing

product data. The attributes of the set type are maintained in tabular form.Set types for which additional key fields are defined are known as multiline set types, whereas single-line set typesare those without additional key fields.

Example: Single-Line Set Type


Page 4 of 56
http://help.sap.com/saphelp_crm700_ehp02/helpdata/en/46/e9f535329372dde10000000a114a6b/frameset.htmhttp://help.sap.com/saphelp_crm700_ehp02/helpdata/en/4f/4cdad67fce0353e10000000a42189c/frameset.htmhttp://help.sap.com/saphelp_crm700_ehp02/helpdata/en/48/0feeb974424aa5e10000000a421937/frameset.htmhttp://help.sap.com/saphelp_crm700_ehp02/helpdata/en/46/5779d501a208e7e10000000a114a6b/content.htmhttp://help.sap.com/saphelp_crm700_ehp02/helpdata/en/46/5779d501a208e7e10000000a114a6b/content.htmhttp://help.sap.com/saphelp_crm700_ehp02/helpdata/en/46/5779d501a208e7e10000000a114a6b/content.htmhttp://help.sap.com/saphelp_crm700_ehp02/helpdata/en/46/5779d501a208e7e10000000a114a6b/content.htm


5/56

Example: Multiline Set Type

Multiple Values

Allows you to assign more than one value to an attribute in the relevant table when creating or changing product data.

Example: Single-Line Set Type with Multiple-Value Attributes

Org anizational Dependency

Allows you to generate set types either dependent on the distribution chain or independent of the distribution chain. This means that the values of all attributes in

distribution-chain-dependent set types are specified for a specific sales organization and distribution channel.

Set types designated for multiple use, whether single-line or multiline, can be organization-dependent, whereas set types not designated for multiple use,

irrespective of whether they are single-line or multiline, are always organization-independent.Template-Enabled

Templates allow you to predefine and therefore standardize data for set types. This data is referenced by the set types on the Productpage. The templates

themselves are defined in Customizing for Cross-Application Components, by choosing SAP Product Templates .

SAP NetWeaver Business Intelligence (BI)

To extract an attribute to SAP NetWeaver BI, you set the BW-Relevantindicator. The extraction structure will contain a field for the selected attribute.

By setting the Relevant for BW Selectionindicator, you can use this attribute for data selection in SAP NetWeaver BI.

Attributes

Attribute Type

An attribute is defined by either a combination of its data type (for example, integer, character string, or date), its length, and optionally its value range (for

example, single values or intervals), or a value table. If you enter a table name, the attribute type and length are filled by the system.

On the Value Rangetab page, you can specify either single values or value ranges for the attribute.

To describe a monitor, you define the attribute screen diagonalas follows:

Name ZSCREENDIAGONAL

Description Screen diagonal

Attribute type Integer

Length 3

Single values 17, 19, 21

Multiple Values

You can define an attribute with single values or multiple values.

You define the attribute Colorwith the values Red, Green, and Blue. A car can be either red, green, or blue. However, you define the attribute Optional Extraswith the values Radioand Sunroof. This is a multiple-value attribute, as a car can have both a radio and a sunroof.

To actually use the attribute as a multiple-value attribute, you must define it as such when assigning it to the set type. This involves setting the Multiple Values

indicator.

You cannot assign attributes you have defined to the standard set types delivered by SAP.

Creating UI Configuration for Set Types

After defining set types, the following steps are required to be able to use your set types on the CRM WebClient UI.

Example

Example

Note


Page 5 of 56


6/56

Prerequisites

1. You have already created an enhancement set.

For more information, see Enhancement Set.

2. You have created an enhancement for each overview page you want to extend.

For more information about how to do this, see Create Enhancements.

This has to be done for each overview page (for example, PRD01OV for product).

If the set type contains multiple-value attributes, you also have to create an enhancement for the component PRDGENSET.

Procedure

1. Assign Set Types to Overview Pages

1. Assign your set types to the relevant overview pages on the SAP Easy Accessscreen under Master Data Products Assign Set Types to Overview

Pages . This report (CRM_UIU_PROD_ REPOSITORY) generates the runtime repository for the set types so that they can be disp layed on the overview

page.

Execute the report for every set type and overview page in which the set type is to be included (PRD0xOV, where x = product type).

The standard overview pages are as follows:

Product Type Application Component Overview Page

01 Product PRD01OV PRD01OV/MaterialOV

01 Competitor Product PRDCPOV PRDCPOV/CompetitorProductOV

01 Object PRDIOOV PRDIOOV/ObjectOV

01 Distribution Chain View PRDDC PRDDC/DCOV

02 Service PRD02OV PRD02OV/ServiceOV


03 Financing PRD07OV PRD07OV/FSProdOV


05 Warranty PRD05OV PRD05OV/WarrantyOV

07 Financial Service PRD07OV PRD07OV/FSProdOV


04 IP PRD04OV PRD04OV/IPProdOV


For more information, see the documentation for the report CRM_UIU_PROD_REPOSITORY.

2. After generation, check in the transaction BSP_WD_ CMPWB that the runtime repository has been generated correctly in the relevant overview pages and the

component PRDGENSET.

Note that for multiple-value attributes, additional component usages are generated in the component PRDGENSET.

2. Generate UI Configuration for Set Types

1. Create the UI configuration for your set types on the SAP Easy Accessscreen under Master Data Products Create UI Configuration for Set Type .

You have to do this specifically for each set type. The type of set type involved determines on which view(s) of the component PRDGENSET the configuration

is created:

Type View

Single-Line Set Type SLSeteOV

Multiline Set Type MLSeteOV

Single-Line Set Type

Distribution-Chain-Specific

SLDCSetEF

Multiline Set Type


MLDCSetEL

Single-Line Set Type with Multiple-Value Attributes SLMVSeteOVVS

SLMVAttreOV

Single-Line Set Type with Multiple-Value Attributes


SLMVDCSetELVS

SLMVDCAttrEL

For more information, see the documentation for the report CRM_UIU_PROD_CONFIG.

2. In the transaction BSP_WD_CMPWB, check and adapt the configuration created in the component PRDGENSET.

The configuration has been created with the object = PRODUCT and object subtype = .

3. Add Set Types to Overview Pages

To add the set types to the overview pages as new assignment blocks, add your views to the relevant overview pages in transaction BSP_WD_CMPWB:

1. Select the relevant component and enhancement set, for example, PRD02OV, enhancement set ZPROD.

2. Select the relevant overview page view, for example, PRD02OV/Serv iceOV, and go to the tab Configuration.

Note


Page 6 of 56
http://help.sap.com/saphelp_crm700_ehp02/helpdata/en/31/33591017f24cb68ef6ebf2ff575c2d/frameset.htmhttp://help.sap.com/saphelp_crm700_ehp02/helpdata/en/51/dfdf460f464db1b483d9c2a1bcd488/frameset.htm


7/56

3. Choose Show Technical Detailsto display the technical view name.

4. Switch to change mode to move assignment blocks from the set of availab le assignment blocks to the set of displayed assignment blocks.

5. Make sure that the views are in the correct order and the relevant load option has been selected.

6. Change the title of the view, as app ropriate. This will be displayed on the overview page.

4. Remove Set Types from Overview Pages

1. To remove set types from the overview pages on which they have been included you have to first manually remove them from the relevant overview page

components in the transaction BSP_WD_CMPWB (see step 3).

2. The reports described above both provide a deletion option for deleting the data they generate:

CRM_UIU_PROD_CONFIG deletes the configuration of the set type from the view, as well as the configuration of mutiple-value attributes.

CRM_UIU_PROD_REPOSITORY removes the generated objects from the runtime repository of the specified overview page component.

The enhancements for multiple-value attributes made in the component PRDGENSET are only deleted if the Delete Set Type from All Overview Pages

action is performed.

Adding Fields to the UI Product Header View

You might want to make additional fields available on the UI in the product header data. These could be fields from your own set types, for example.

An empty view is provided for this purpose in the product header area, enabling you to include your own fields. An empty view is available for each application:

Application Component/View for Customer Enhancement

Product (PRD01) PRD01OV/CustomHeader

Service (PRD02) PRD02OV/CustomHeader

IP Product (PRD04) PRD04OV/CustomHeader

Warranty (PRD05) PRD05OV/CustomHeader

Financing Product (PRD07) PRD07OV/CustomHeader

Competitor Product (PRDCP) PRDCPOV/CustomHeader

Object (PRDIO) PRDIOOV/CustomHeader

The product header is the topmost assignment block displayed on the overview page, and is called, for example, Product Details for products and Service

Details for services.

Prerequisites

The additional field is available in the business object layer (BOL) as a dependent object of the root object Product. Customer set types are automatically

available in BOL since the table entries required are generated when the set type is created.

You can only include organization-independent, single-line set types in the product header.

You have created an enhancement set. For more information, see Enhancement Set.

Procedure

The steps below describe how to enhance the product application PRD01. You can enhance the other applications in the same way.

You want to add the attribute ZCOLOR from the set type ZSET1 to the application PRD01. In the database table ZSET1, the attribute ZCOLOR has the name

ZZ0010.

1. Use the transaction GENIL_MODEL_BROWSER (component set PROD_APPL) to check that there is a relevant BOL node which contains the new field. The

dependent object for the set type ZSET1 is called ZProdSetZSET1. The relationship between the product and ZProdSetZSET1 is called ZProdRelSetZSET1.

2. Execute transaction BSP_WD_CMPWB and enter the relevant component (for example, PRD01OV). Enter the enhancement set that you created.

3. If you have not created an enhancement for component PRD01OV, do so by choosing Enhance Component(for more information, see Create Enhancements).

You have to do this for each component that you want to enhance.

4. Enhance the view specified above (for example, PRD01OV/CustomHeader) by clicking Enhancewith the secondary mouse button. This copies the view

controller class and the context class so that you can enhance them.

5. Select the view (PRD01OV/CustomHeader) and, on the right-hand side of the screen, choose in the structure Context Context Node and click Create

with the secondary mouse button. Enter the following data in the wizard:

Name of context node: Set type ID ZSET1 (recommended)

As there are certain special characters that are not permitted in context node names, such as _, you cannot always use the set type ID as the name. If

this applies, choose a different name.BOL entity: BOL node of set type (for example, ZProdSetZSET1)

For the step "Define Dependency", choose PRODUCT as the superordinate node and enter the BOL relationship for the set type, for example,

ZProdRelSetZSET1.

On completion, a new context node is generated with an associated context node class (with the name ZL_PRD01OV_CUSTOMHEADER_CN01, for

Note

Example


Page 7 of 56
http://help.sap.com/saphelp_crm700_ehp02/helpdata/en/31/33591017f24cb68ef6ebf2ff575c2d/frameset.htmhttp://help.sap.com/saphelp_crm700_ehp02/helpdata/en/51/dfdf460f464db1b483d9c2a1bcd488/frameset.htm


8/56

example).

6. Go to the generated context node class and change the inheritance. Enter the class CL_PRD_HEADER_CONTEXT_NODE as the new superclass. This has

the following advantages:

Input helps are already implemented in the superclass (method GET_V_S_STRUCT). An attribute for which you have maintained fixed values or a value

table in the attribute definition therefore automatically has an input help.

The new fields are automatically set to ready for input or not ready for input (method GET_I_S_STRUCT of the superclass), if required. Description fields, for

example, are automatically set to not ready for input. If a set type is not assigned to a category or is referenced, the field is also not ready for input.

7. If you have changed the superc lass to CL_PRD_HEADER_CONTEXT_NODE, you must implement the following methods in the generated context class:

New instance method CONSTRUCTOR (Public)

Code:

1. METHOD constructor.

CALL METHOD super->constructor.

me->base_entity_name_inst = base_entity_name.

me->base_entity_relation = 'ZProdRelSetZSET1'.

ENDMETHOD.

Change the existing method ON_NEW_FOCUS

New code:

1. METHOD on_new_focus.

me->create_property( focus_bo ).ENDMETHOD.

8. Create a new configuration for the view PRD0 1OV/CustomHeader, or enhance the existing c onfiguration and add the new field (context node ZSET1, field

ZZ0010).

9. The superclass CL_PRD_ HEADER_CONTEXT_NODE provides a generic input help. If this generic solution does not meet your requirements, you can

implement your own getter methods for the specific field in the generated context node class and thus override the standard behavior.

Method GET_I_ZZ0010, to change the ready for input status of the field.

Method GET_V_ZZ0010 for your own input help.

Adding Fields to the Product Search

Procedure

To extend the product search to include attributes from your own set types or other set types perform the following steps:

1. Extend the search structure by adding the additional search attributes in an append to the following standard search structures:

CRMT_PRIL_QUERY_ADVSEARCH_PROD

CRMT_PRIL_QUERY_ADVSEARCH_IOBJ

2. If a search request contains the added attributes, the determination of the suitable search execution class is delegated to the method

GET_SEARCH_SCENARIO_OR_FILTER of the Business Add-In (BAdI) CRM_PRIL_SEARCHEXIT. A default implementation of this BAdI is active and is

executed automatically. It delegates the search to the search execution class CL_COM_PRSEARCHSCENARIO_ATTR (which consists of the search tool

class CL_COM_PRSEARCHTOOL_ATTR and suitable filter classes). You have the following options:

1. If you want to use this implementation the search tool class needs to know to which attribute of which set type a particular extension attribute belongs. You

make this setting in Customizing for Customer Relationship Managementunder Master Data Products Basic Settings Add Attributes to Search

Structure . After maintaining your entries you have to transport them manually.

2. If you want to use your own implementation of this BAdI, you can do this by p roviding, for example, a suitable search execution class derived from

CL_COM_PRSEARCHSCENARIO_BASE.

3. You can also just return a filter class (a class that implements the interface IF_COM_PRSEARCHFILTER). It is taken into account in the calling method.

The standard attributes are processed further by the calling method PREPARE_DB_RANGE_SEARCH. If you want, you can use CRMC_PRSEA_ATTR in

your own implementation.

You can also use this method to have full control over the search. To do this, you set the EV_READY indicator to true in your implementation. Only the search

execution class you return is then used in the search. This means that it should then be able to handle all criteria, but it also means that you have full

responsibility for the search.

3. For the UI, the search views are located in the BSP components PRD01QR and PRDIOQ R. These are PRD01QR/Search for the main search view,

PRD01QR/SearchHelp for the search help views (dialog boxes), and PRDIOQR/Search (used for main search view and in search help dialog boxes). After

you have added the appends to the search structure, the additional attributes are available in the configuration tool of the BSP component workbench and can

be set to visible.

Suitable value helps can be provided for the additional attributes using the method IF_CRM_PRIL_SEARCHEXIT~CHANGE_DQUERY_DEF_EXTENSION of

the BAdI CRM_PRIL_SEARCHEXIT. You can define your own implementations for this method in your own BAdI implementation.

If you just want to make small changes to the existing implementation, you can use the source code enhancement concept and enhance the method

IF_CRM_PRIL_SEARCHEXIT~CHANGE_DQUERY_DEF_EXTENSION of the default implementing class CL_CRM_PRIL_SEARCHEXIT_IMPL.

Syntax

Syntax

Example


Page 8 of 56


9/56

Also see Note 1026956.

Transporting Set Types to Production Systems

The system in which you create your set types and attributes depends on your system landscape. Transport functionality is available, enabling you to transport

your objects between systems. However, you should consider the following points to avoid errors and data inconsistency:

Attributes and set types should be created in the same system.

You are advised to create them in the development system and then transport them within your landscape to the quality and production systems.

You can also create these objects in the quality and production systems, however you must ensure that the users involved have the appropriate authorizations.

Set types are created as local objects and are therefore assigned to the package $TMP. To transport a set type to a production system, the set type needs to be

assigned to a transportable package and included in a transport request.

Once a set type has been transported to a production system, any modifications or enhancements have to be transported additionally. For example, you add

some values to an attribute definition. You have the following options:

Create a workbench transport directly for the domain definition of this attribute.

Take one set type where this attribute is used and transport the complete set type.

Transport all set types where this attribute is used.

Prerequisites

A transportable package exists.A transport request has been created.

The transport system has been set up correctly.

Procedure

1. On the SAP Easy Accessscreen, choose Maintain Set Types and Attributes.

2. Choose Set Types /Attributes Transport Set Type and enter the ID of the set type to be transported. Then choose Include in Transport Request.

If you set the Create API Appendindicator, it will also be possible to maintain the set type using APIs. The BDoc structure or API structure is extended

during this process, and the data included in data exchange and archiving.

3. Choose Execute.

4. In the dialog box that appears, choose Display/Change, specify the package to which you want to assign the set type, and choose Enter.5. In the dialog box that appears, sp ecify the transport request and choose Enter.

6. Release the transport request.

Once the transport request has been released and transported, the set type is transported to the given systems (for example, Development System

Consolidation System Quality/Test System Production System ).

Product Hierarchies

Product hierarchies provide a structuring mechanism for modeling purposes within the product master.

In the documentation about product hierarchies, products includes both products and objects.

Product hierarchies consist of categories and are used to group products according to different criteria. The purpose of a hierarchy depends on the business

criteria involved and your company's requirements.

A hierarchy can be multilevel and used for control or informative purposes.

Structure

The categories within a hierarchy are arranged hierarchically. All lower-level categories inherit the product type and set types from the higher-level category.

Additional set types can be assigned to lower-level categories.

An example is shown below (note that the set types shown are not standard set types, but examples of customer-defined set types):

Note

Note


Page 9 of 56


10/56

If a product type is assigned to a category, only products of this product type can be assigned to the category. Assigning a product type to a category makes it

possible to assign set types to the category. The set types themselves appear as assignment blocks on the Productand Objectpages.

To prevent a set type from being assigned to a product more than once based on different categories, the following rules apply when working with categories and

hierarchies:

A set type may be ass igned to more than one category within a hierarchy, but to only one hierarchy for each product type. Therefore even if two categories are

in different hierarchies but have the same product type, it is not possible to assign the set type to both categories.A product can be assigned to more than one category as long as the categories belong to different hierarchies. A product can therefore only be ass igned to one

category in each hierarchy.

The same rules apply to the assignment of relationship types.

Base Categories and Hierarchies

The base hierarchy used either for products in general or for specific product types.

A product can be assigned any number of categories. However, when you first create a product you must assign it to a base category. A base category is a

category belonging to the base hierarchy, which is the basic hierarchy defined for products in general or for a specific product type.

Defining Hierarchies as Base Hierarchies

Within the product master, assigning a hierarchy to the application Productenables it to be used as a base hierarchy, which is required to create products. Each

product created must be assigned to a category from this hierarchy. It is the starting point when you create a product.

You assign product hierarchies to applications in Customizing for Cross-Application Components, by choosing SAP Product Product Category Assign

Category Hierarchies to Applications :

You can assign a base hierarchy to a specific product type. This overrides the higher-level assignment between the hierarchy and application.

If a base hierarchy is not assigned to a product type, the hierarchy specified for the application serves as the base hierarchy for all product types.

The base category assigned to a product determines the product IDs allowed when a product is created.

You define the number ranges for internal and external number assignment in Customizing for Cross-Application Components, by choosing SAP Product

Settings for Product Type Number Assignment Define Number Ranges for t he Product Type "Material" /Define Number Ranges for t he Product Type"Service". Number ranges are defined for other product types in Customizing for Customer Relationship Management, by choosing Master Data Products

Settings for Product Type Number Assignment .

Base Hierarchies Replicated from SAP ECC

The main base hierarchy generally replicated from SAP ECC is the base hierarchy for Material/ServiceR3PRODSTYP. This hierarchy is assigned to the

application Product.

Base Hierarchies Created in SAP CRM

In the following cases the base hierarchies are created in SAP CRM:

The report CRM_PR_FIN_CREATE_HIERARCHY is used to create a base hierarchy for the product type Financing.

Base hierarchy for the product type Intellectual Property

Base hierarchy for the product type Warranty

Base hierarchy for the product type Service

If you are creating service products in SAP CRM and not replicating them from SAP ECC, do not use the hierarchy R3PRODSTYP as the base hierarchy forservices, b ut create a new hierarchy in SAP CRM.

Note


Page 10 of 56


11/56

Creation of Categories and Hierarchies

Product hierarchies are used to classify products and group them according to different criteria. They are used primarily to describe differences within a business

context, for example, you might categorize your products according to their technical properties or how they are used.

A hierarchy is constructed like a tree structure with a root category that includes all other categories.

Hierarchies comprise data specified at hierarchy level, which applies to the entire hierarchy, and data at category level, which applies to lower levels within the

hierarchy. Certain data is inherited within the hierarchy.

The root category is the highest-level node within the hierarchy and does not generally contain any control information.

Prerequisites

You have defined numbering schemes for your product hierarchies in Customizing for Cross-Application Components, by choosing SAP Product Product

Category Define Category Numbering Schemes .

You have defined authorization groups in Customizing for Cross-Application Components, by choosing SAP Product Basic Settings Define Authorization

Groups .

You have defined the partner determination procedures you require in Customizing for Customer Relationship Management, by choosing Basic Functions

Partner Processing Define Partner Determination Procedure .

You have defined the alternative ID types you require in Customizing for Cross-Application Components, by choosing SAP Product Alternative Product

IDs .

Features

Hierarchies

Certain features are available at hierarchy level and therefore apply to the entire hierarchy:

Numbering Scheme

You can assign category IDs yourself (alphanumeric or numeric), or they can be assigned automatically (numeric only). If you assign them yourself, the

system checks them against the numbering scheme.

Standard Schema

The entry you make indicates that the product schema (hierarchy) displayed is a standard schema.

You can transport categories and hierarchies to the relevant systems (for example, test system or production system) in Customizing for Cross-Application

Components , by choosing SAP Product Product Category Transport Categories .

Categories

Categories define which set types and relationship types are allowed for a product, thereby enabling you to structure the information you require on your products.

If a product is assigned to more than one category, all set types and relationship types for the categories to which the product is assigned can be used.Once a category has been assigned to a product and the data saved, the assignment cannot simply be deleted. You can reassign products on the SAP Easy

Accessscreen under Master Data Products Recategorize Products .

General Data and Control Data

You can specify the following:

Whether a user is authorized to display, change, or create products belonging to this category.

Who is responsible for the category. You may, for example, want to specify the brand manager as the person responsible for the highest-level category, and

the product manager for lower-level categories.

What options are available on the Productpage:

Whether products can be assigned; this should not be possible for root categories

Whether documents can be attached (this indicator can only be set for categories within the base hierarchy)

Whether prices can be specified (this indicator can only be set for categories within the base hierarchy)

Whether the category is restricted to objects and a certain object family. If so, you can specify a partner determination procedure to determine which parties can

be assigned to the object in the Parties Involvedassignment block on the Objectpage. This option is only available for categories within the base hierarchy.

Set Types and Relationship Types

Set types and relationship types are specified in the respective assignment blocks:Assigned Set Types

You can specify which set types should be assigned to the category concerned, and whether they should derive their data from a template. The system

indicates which set types have been inherited.

A Referenced indicator is an additional option available for objects for use in conjunction with reference products and is only visible for categories assigned an

object family.

Assigned Relationship Types

You can specify which relationship types should be assigned to the category, enabling these relationship types to be created for a product belonging to this

category. The system indicates which relationship types have been inherited.

Referenced Relationship Types Disp layed in Objects

An option available for objects, enabling the relationships of the reference product to be disp layed for the object concerned. Only certain relationship types can

be referenced, which are available for selection in the input help.

This assignment block is only visible if an object family has been specified for the category and referencing has been activated in Customizing for Cross-

Application Components, by choosing SAP Product Basic Settings Allow Product References for Individual Objects . For more information, see

Referencing Data from Products.

PricesPrices can be created for products at product or category level. For more information about creating prices, see Prices at Category Level.

Inheritance

Certain fields can be inherited by lower-level categories. For more information about inheritance, see Inheritance Within Hierarchies.


Page 11 of 56
http://help.sap.com/saphelp_crm700_ehp02/helpdata/en/46/57429b01a208e7e10000000a114a6b/content.htmhttp://help.sap.com/saphelp_crm700_ehp02/helpdata/en/46/5752e401a208e7e10000000a114a6b/content.htmhttp://help.sap.com/saphelp_crm700_ehp02/helpdata/en/92/f4543f65c83b28e10000000a114084/frameset.htm


12/56

Prices at Category Level

Pricing conditions are used to calculate prices in business transactions, such as sales orders and purchase contracts.

Pricing conditions can be specified for individual products on the Productpage and for an entire category of products at category level in the Assigned Prices

assignment block on the Product Hierarchypage. This is particularly advantageous when working with a large number of products, as pricing conditions, such asprices, discounts, and surcharges, can be defined at the category level for an entire category of products, instead of at the product level solely for individual

products.

Pricing conditions replicated from SAP ECC that are specific to a category with the sales hierarchy (generally R3PRODHIER) can be displayed at category level

in a product hierarchy.

Pricing is based on the condition technique. For more information, see Pricingand The Pricing Process.

Prerequisites

You have made the following Customizing settings:

Customer Relationship Management Master Data Products Product Category Pricing Define Pricing-Relevant Hierarchies

Two pricing-relevant hierarchies, PRCATHIER1 and PRCATHIER2, are supported and delivered in the standard system. The pricing-relevant hierarchy

R3PRODHIER is used to display pricing conditions replicated from SAP ECC.

Customer Relationship Management Master Data Products Product Category Pricing Assign Product Hierarchy to Pric ing-Relevant Hierarchy

Assign your product hierarchy to the pricing-relevant hierarchy. TheAssigned Prices assignment block is not available on the Product Hierarchypage if the

product hierarchy is not relevant for pricing.If you have downloaded pricing conditions from SAP ECC, assign the sales hierarchy downloaded from SAP ECC to R3PRODHIER.

Customer Relationship Management Basic Functions Pricing Define Settings for Pricing Create Pricing Procedure

If further hierarchies are required in addition to the standard two delivered, you also need to make the following Customizing settings:

Customer Relationship Management Basic Functions Pricing Define Settings for Pricing Maintain Field Catalog

Customer Relationship Management Master Data Products Product Category Pricing Assign Field Catalog Fields to Pricing-Relevant Hierarchy

Customer Relationship Management Basic Functions Pricing Define Settings for Pricing Create Access Sequences

Customer Relationship Management Basic Functions Pricing Define Settings for Pricing Create Condition Types

Customer Relationship Management Master Data Conditions and Condition Technique Condition Technique: Basics Create Maintenance Group

Customer Relationship Management Master Data Products Special Settings for Sales Operations Assign Condition Group to Application CRM

If you want to display pricing conditions replicated from SAP ECC at category level in a product hierarchy, check the Customizing for the pricing-relevant hierarchy

R3PRODHIER in the Customizing activityAssign Field Catalog Fields to Pricing-Relevant Hierarchy, by choosing Customer Relationship Management

Master Data Products Product Category Pricing .

Features

Pricing is based on the condition technique. Prices can be specified on the Product Hierarchypage for an entire category of products:

1. You specify prices for the relevant category in theAssigned Prices assignment block on the Product Hierarchypage. You can create, change, and delete

prices with the price types defined in the standard version. You can check which condition types apply in Customizing by choosing Customer Relationship

Management Master Data Conditions and Condition Technique Condition Technique: Basics Create Maintenance Group . The relevant maintenance

group delivered in the standard version is PRCAT_CRM. As with other conditions, you specify validity periods for the price records you create.

2. The condition types supported include, for example, price, surcharge, and discount. The access sequence maintained at the condition type level defines the

access steps required for condition determination.

3. Prices at category level are not inherited within the hierarchy, as the access sequence within the condition technique is used to determine which pricing

condition is relevant.

4. The pricing steps are processed when triggered by SAP CRM order management.

For more information about product prices, see Prices.


Page 12 of 56
http://help.sap.com/saphelp_crm700_ehp02/helpdata/en/46/57511801a208e7e10000000a114a6b/content.htmhttp://help.sap.com/saphelp_crm700_ehp02/helpdata/en/4a/8202f3e6425752e10000000a421937/frameset.htmhttp://help.sap.com/saphelp_crm700_ehp02/helpdata/en/86/06f837aea75351e10000009b38f8cf/frameset.htm


13/56

Inheritance Within Hierarchies

Certain fields within product hierarchies are inherited by lower-level categories. This means that this data does not have to be maintained for each category within

the hierarchy.

Features

The following fields are inherited by lower-level categories:

Product Type

Authorization Group

Object Family

Partner Determination Procedure

Alternative ID Type

Assigned set types and templates, including Referencedindicator

Assigned relationship types

Inherited fields cannot be changed for lower-level categories. Note however the following excep tions:

Inheritance can be interrupted for templates. The mechanism by which inheritance is interrupted is shown in the example below.

A set type can be assigned to a higher-level category (Referencedindicator not set), and the Referencedindicator then set for lower-level categories. The

Referencedindicator cannot however be deselected for lower-level categories.

Example

1. The value X is maintained for the highest-level category H1 and inherited by lower-level categories.

2. The value is changed for category H1211 to Y. This new value is inherited by the categories H12111 and H12112.

3. The value X is now changed to Z for category H1. This new value is inherited by H11, H12, and H121, but not by H12111 and the categories below it. This is

the point at which inheritance is interrupted.

4. Inheritance can be res tored by changing the value of category H12111 to the same value as the higher-level categories (from Y to Z).

5. Another change to the value of category H1 (new value W) is inherited throughout the hierarchy.

Template Framework

Definition

The template framework is a technical environment where you create and maintain mini-templates for the master data object SAP Product.

Use

The template framework simplifies master data maintenance by giving you access to mini-templates when you create or change products. For more information,

see Working with Mini-Templates.

This enables you to save time, and avoid data redundancy and errors because you no longer need to enter and maintain data that is commonly required in a large

number of products, in each of these products individually. Instead, you maintain this data once only in a mini-template, which the products then reference. Any

changes made subsequently to the mini-template are also reflected in the products that reference it, and in this way you can make mass changes quickly and


Page 13 of 56
http://help.sap.com/saphelp_crm700_ehp02/helpdata/en/25/05a6425a99b611e10000000a155106/content.htm


14/56

easily.

In order to avoid unwanted mass changes, a where-used listensures that you are aware of which products reference a mini-template, before you change or delete

the mini-template in question. In addition, an authorization concept ensures that only the appropriate users can change or delete mini-templates.

Read strategiesin the template framework define the sequence in which data is accessed for a product.

Structure

The template framework consists of the following parts:

Mini-temp late types

A mini-template type signifies the smallest set of attributes you can use to build a mini-template. It does not contain any values itself, but rather represents a

structure in the application that can be filled with values.

Mini-templates

A mini-template is a concrete occurrence of a particular mini-template type. Thus, a number of mini-templates, containing different values in each case, can

be based on one mini-template type. Mini-templates can either be differentiation key-dependent or -independent.

Integration

The template framework facilitates the transfer to external systems, such as SAP BI or SAP CRM, of changes made to mini-templates.

Working with Mini-Templates

Use

You use the template framework to maintain mini-templates, which can be reused by many product master records.

Mini-templates are defined in Customizing and assigned to product category hierarchies in the standard system. Which mini-templates are assigned to a specific

product is therefore determined implicitly when a product is assigned categories in product maintenance.

Mini-templates are used to maintain data for set types.

Prerequisites

Before you can work with mini-templates in product maintenance, you have to

Create set types in transaction COMM_ATTRSET

Activate these set types so that they can be used in mini-template maintenance by

Setting the flag Template-Enabledwhen you create a new set type, or maintain an existing set type

Choosing Set Type -> Activate Templatesin the menu for set types that have already been generated or delivered, and that can be called up only in the

display mode.

A differentiation key-independent mini-template anda differentiation key-dependent mini-template are then generated automatically for each set type.

Maintain the appropriate data for your mini-templates in Customizing for SAP Product, by choosing Cross-Application Components -> SAP Product ->

Templates -> Maintain Mini-Templates.

Features

Assignment of Mini-Templates to Products

You assign mini-templates to categories in category and hierarchy maintenance. Mini-templates are therefore not assigned directly to products, but only to product

categories.

Mini-templates can be inherited from higher-level categories within a hierarchy.

During product maintenance, the categories for the product in question are read at runtime. If a mini-template is found, its data is read to the corresponding

attributes of the product if this product does not already have its own data.

For more information, see Creation of Categories and Hierarchies.

Usage of Mini-Template Data

You use mini-template data in product maintenance. Here, mini-template-enabled product set types reference the data in mini-templates that are assigned to

product categories. The mini-template data is read at runtime into the corresponding set types fields, which are in display mode and therefore cannot be

maintained. A text is displayed, indicating from which mini-template and category the data has been derived for a particular product set type. Choose Information

to display technical data on the mini-template.

You can copy the mini-template data to the set type of a product by choosing Create Own Data. The set types fields then become ready for input and you can

overwrite the mini-template data with your own data.

You can switch back to the referenced data by choosing Delete Own Data. Your own data is deleted, and the mini-template data is once again displayed.

Distribution of Changes to Mini-Templates

When changes to mini-templates are transported, they are cascaded into all the relevant clients in the target system. However, this does not mean that the

changes are automatically distributed to external systems, such as BI or ERP systems.

If distribution is required, you should schedule a variant of report TFW_DX_TEMPLATE_CHANGES


Page 14 of 56
http://help.sap.com/saphelp_crm700_ehp02/helpdata/en/46/572ccf01a208e7e10000000a114a6b/content.htmhttp://help.sap.com/saphelp_crm700_ehp02/helpdata/en/de/5ea4423810c611e10000000a1550b0/content.htmhttp://help.sap.com/saphelp_crm700_ehp02/helpdata/en/f1/92a04270600d31e10000000a1550b0/content.htm


15/56

periodically

or once only, after an import

in the relevant clients of the target system.

You should carry out the scheduling using the view V_TFW_DX_JOB. In this way, an entry is made in the table TFW_DX_JOB, which prevents redundant

scheduling.

Where-Used List

Use

Many products can reference the same mini-template, and thus any changes made to a particular mini-template will be reflected in all the products that reference

it. The where-used list ensures that you are aware of the effect that changing mini-templates in Customizing would have on your product master records.

Features

The where-used list is triggered when you attempt to change or delete a mini-template. Checks are run to determine all the products that reference the mini-

template in question. The results are displayed in a dialog box. If the mini-template is being used, it is not possible for you to delete it.

If you are authorized to change mini-templates, a further dialog box gives you the option of scheduling a background job for the report

TFW_DX_TEMPLATE_CHANGES. This allows you to distribute changes made to mini-templates to external systems, such as ERP or SAP BI. If you cancel at

this point, the worklist is stored in the database table TFW_DX_MINITP, where you can process it later.

You should be aware that the where-used list is not triggered when you attempt to change or delete the assignment of a mini-template to a product category in

category and hierarchy maintenance. Thus, the dialog box mentioned above for scheduling report TFW_DX_TEMPLATE_CHANGES does not appear

automatically. If you want to distribute the changes to an external system, you must therefore schedule a job for this report manually.

You can schedule the distribution to external systems of mass changes caused by changing mini-templates, by choosing Templates -> Schedule Data

Exchange of Changes to Mini-Templatesin Customizing of the SAP Product.

Read Strategies

Use

Read strategies define the sequence in which the data in mini-templates is accessed for products that do not have their own data.

Features

Read strategies can consist of several read methods. SAP delivers read methods for the SAP Product ,describing different ways of reading data for your products.

Read strategies determine the sequence in which the read methods are called up, and thus, the sequence in which data is read for products that do not have their

own data. According to the active read strategy delivered for the SAP Product, the products own data is read before reference productdata, which in turn is read

before the data in mini-templates assigned to product categories.

You should note that you cannot define your own read strategies. You can either use the read strategy delivered by SAP, or you can deactivate it. However, in the

latter case, the data contained in the mini-templates is then no longer available for use in your products.

Integration in SAP NetWeaver Business Intelligence

The integration of Productsin SAP NetWeaver Business Intelligence (SAP NetWeaver BI) is divided into two essentially different areas.

SAP CRM Set Types (Standard)

Set types can be created as either distribution-chain-dependent or distribution-chain-independent. Where set types are distribution-chain-dependent, the attribute

values are only valid for a specific sales organization and a specific distribution channel.


Page 15 of 56
http://help.sap.com/saphelp_crm700_ehp02/helpdata/en/57/c93199ab68a54aa4b8b9fe5dde57d4/content.htm


16/56

Standard set types used in Productsare transferred to SAP NetWeaver BI using SAP CRM DataSources and mapped in SAP NetWeaver BI using one of the

following InfoObjects:

InfoObject 0CRM_PROD is used for distribution-chain-independent set types of type Materialor Service

InfoObject 0CRM_PRFI is used for distribution-chain-independent set types of type Financing

InfoObject 0CRM_PRODSL is used for distribution-chain-dependent set types of type Materialor Service

InfoObject 0CRM_PRFISL is used for distribution-chain-dependent set types of type Financing

There are several DataSources for the attributes of these InfoObjects, for which mapping rules are already available in the standard Business Content. This

standard Business Content only needs to be activated.

The following DataSources are provided for the InfoObject 0CRM_PROD (distribution-chain-independent, type Material/Service):

DataSource Use

0CRM_PRODUCT_ATTR Product: CRM Part

0CRM_PR_PRMAT_ATTR Product Material Data

0CRM_TR_CONTROL_ATTR Transaction Control Parameters

0CRM_PR_REST_IN_ATTR Handling Indicator

The following DataSources are provided for the InfoObject 0CRM_PRFI (distribution-chain-independent, type Financing):

DataSource Use

0CRM_PR_FIN01_ATTR Financing : Basic Data

The following DataSources are provided for the InfoObject 0CRM_PRODSL (distribution-chain-dependent, type Material/Service):

DataSource Use

0CRM_PR_SALESA_ATTR Product: Order Data

0CRM_PR_SALESG_ATTR Product: Sales Pricing

0CRM_PROD_STATUS_SALES_ATTR Product: Status (Sales View)

0CRM_CR_CONTROL_ATTR Control Parameters Claims/Returns

0CRM_EXCH_BUS_ATTR Entitlements

0CRM_PR_RESIDVL_ATTR Financing-Dependent Attributes

The following DataSources are provided for the InfoObject 0CRM_PRFISL (distribution-chain-dependent, type Financing):

DataSource Use

0CRM_PR_FIN02_ATTR Financing: Distribution-Chain-Dependent Data

0CRM_PR_FIN03_ATTR Financing: Classification and Views

The following text DataSources are provided for attributes belonging to the InfoObject 0CRM_PROD:

DataSource Use

0CRM_PROD_IDCMP_TEXT Texts for Compound Product ID

0CRM_SRV_ESCAL_TEXT Response Profile

0CRM_SRV_SERWI_TEXT Service Profile

0CRM_ITEM_INSP_TEXT Item Inspection

0CRM_PROD_HNDLCODE_TEXT Handling Code

The following text DataSource is provided for attributes belonging to the InfoObject 0CRM_PRFI:

DataSource Use

0CRM_CLASSIFICATION_TEXT CRM Contract Class

The following text DataSources are provided for attributes belonging to the InfoObject 0CRM_PRODSL:

DataSource Use

0CRM_REBATE_GROUP_TEXT Volume Rebate Group

0CRM_RESID_VALUE_GRP_TEXT Residual Value Curve

0CRM_RESID_VALUE_ST_TEXT Residual Value Strategy

0CRM_ACCTGRPPROD_TEXT Account Assignment Group Product

0CRM_COMM_GROUP_TEXT Commission Group

0CRM_RETURNABL_TEXT Returnable

0CRM_PROC_IND_TEXT Process Indicator

0CRM_COREPART_IND_TEXT Used Part Indicator

The following text DataSources are provided for attributes belonging to the InfoObject 0CRM_PRFISL:


Page 16 of 56


17/56

DataSource Use

0CRM_REFERENCE_INT_D_TEXT Interest Reference ID

0CRM_REFERENCE_INT_TEXT Reference Interest Rate

0CRM_TIMEUNIT_TEXT Time Unit

0CRM_INTERIM_PERIOD_TEXT Interim Period

0CRM_LOOKUP_FOR_INT_TEXT Interest Determination

0CRM_PAYMNT_FORM_TEXT Payment Form

0CRM_PAYMNT_FREQ_TEXT Type of Installment Payment

0CRM_LEAS_CLASS_TEXT Tax Pricing Strategy

0CRM_PRIC_FIMA_TEXT Process Indicator Financial Mathematics

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. The

SAP CRM DataSources generated for customer-defined set types allow all attributes in the set type designated as relevant to BW to be transferred to SAP

NetWeaver BI. If a field is also designated as relevant for selection, the data selection can be restricted later from SAP NetWeaver BI using this field. If the set

type contains attributes which require a text DataSource, these are also generated. However, the system does not generate any objects in SAP NetWeaver BI,

these must be made available by the application.

Before the DataSources generated in the application system can be transferred to SAP NetWeaver BI , and the missing meta data (InfoObjects and transfer rules)

created, the modeling must be specified within SAP NetWeaver BI. For SAP CRM distribution-chain-independent attributes for products, there are basically two

options:

Option 1: Include new attributes in existing InfoObjects

The attributes of type Materialor Servicethat need to be transferred to SAP NetWeaver BI can be transferred as attributes of the InfoObject 0CRM_PROD

(Product), the attributes of type Financingcan be transferred as attributes of the InfoObject 0CRM_PRFI (SAP CRM Financing Product). As a result, the total

number of attributes for these InfoObjects will increase considerably and may reach the technical limit of 249 attributes.

Option 2: Create new InfoObjects

If quite a large number of new attributes is anticipated or if the attributes are of a new type, you are advised to create a new InfoObject ZMY_PROD (or similar)

and append the attributes to it. This InfoObject must have the same data type and length as the InfoObject 0CRM_PROD or 0CRM_PRFI.

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 procedure is similar for SAP CRM distribution-chain-dependent attributes for products. There are basically two options:

Option 1: Include new distribution-chain-dependent attributes in existing InfoObjects

The distribution-chain-dependent attributes of type Materialor Servicethat need to be transferred to SAP NetWeaver BI can be transferred as attributes of the

InfoObject 0CRM_PRODSL (Product Sales View), the distribution-chain-dependent attributes of type Financingcan be transferred as attributes of the

InfoObject 0CRM_PRFISL (SAP CRM Financing Product Sales View). As a result, the total number of attributes for these InfoObjects will increase

considerably and may reach the technical limit of 249 attributes.

Option 2: Create new InfoObjects

If quite a large number of new attributes is anticipated or if the distribution-chain-dependent attributes are of a new type, you are advised to create a new

InfoObject ZMY_PRODSL (or similar), compounded with the InfoObjects 0CRM_SALORG and 0DISTR_CHAN, and append the attributes to it. This

InfoObject must have the same data type and length as the InfoObject 0CRM_PRODSL or 0CRM_PRFISL.

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 master data is very important for transaction data and queries.

When the transaction data is transferred, the product GUID (key in SAP NetWeaver BI) 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.

When distribution-chain-dependent transaction data is transferred, the product GUID, the SAP CRM sales organization and distribution channel (compound key in

SAP NetWeaver BI) contained in the transfer structure must be copied to the relevant fields (communication structure, transfer rules)

You should first replicate the generated master data and text DataSources from the application system to SAP NetWeaver BI from the administrator workbench.

Functions

Prices

Prices are used for pricing purposes in business transactions (quotations, sales orders, contracts). They are based on the condition technique and enable pricing

information to be determined from the pricing condition records you create for the product concerned. Prices are calculated using the pricing engine.

Integration

The following table explains how terminology differs between the WebClient UI and Customizing.


Page 17 of 56


18/56

WebClient UI Customizing Customizing Activity

Price

Maintenance

Group

Condition Maintenance Group Customer Relationship Management Master Data Conditions and Condition Technique Condition

Technique: Basics Create Maintenance Group

Price Type Condition Maintenance Group

Entry

(combination of condition type

and condition table)

Customer Relationship Management Master Data Conditions and Condition Technique Condition

Technique: Basics Create Maintenance Group

Price Element Condition Type Customer Relationship Management Basic Functions Pricing Define Settings for Pricing Create

Condition Type

Prerequisites

If you want to use the pricing functionality in the product master, you must assign the product-specific condition tables and types to the appropriate condition

group in Customizing for Customer Relationship Management, by choosing Master Data Conditions and Condition Technique Condition Technique:

Basics Create Maintenance Group .

If you want to use the pricing functionality in the product master, you must assign the condition group to the application SAP CRM in Customizing for Customer

Relationship Management, by choosing Master Data Products Special Settings for Sales Operations Assign Condition Group to Application CRM .

If you want to view details of price calculation, you must enter the user parameter PRC_CALC_TRACEand the parameter value Xin your user preferences

(transaction SU3).

Features

Pricing Procedure

The mechanism by which p rices are calculated is c omplex. It enables a number of prices to be calculated, such as gross price, discount, and surcharge, which

might be relevant for a certain customer or on a certain date.

The data required for calculating the price can be derived from the pricing information specified for the following:

Sales order, service order, quotation, or contract

Product

Business partner

This information is accessed and evaluated in a pricing procedure, which defines how the price is calculated, that is which condition types apply and the

sequence in which they are calculated.

For more information about pricing, see The Pricing Process.

Price C alculation

You can view price details for items. For example, you can analyze prices and determine how the following are calculated:User exits

If user exits are used, you can determine how the system uses user exits to calculate prices. For example, you can determine if condition values are changed

by condition value formulas.

Currency conversions

Scales

If scales are used, you can determine which condition rates are set by scales.

Condition exclusions

Quantity conversions

You can view sales unit to base unit conversions and condition unit to base unit conversions.

Price Type

The price type determines the type of price involved. This can be simply the price the product actually costs, or dependent on other factors such as distribution

chain or customer.

Technically the price type is an entry in the condition maintenance group. Each assigned combination of condition type and condition table constitutes a price

type. It determines which fields are available for specifying price information on the Productpage and what type of scale can be created for the specific price.

Normally you create a standard price for a product. This is currently defined as specific to a sales organization and distribution channel:

Product Price: Condition type 0PR0, condition table SAP004

Customer-Specific Product Price: Condition type 0PR0, condition table SAP005

You might also want to create discounts or surcharges. Although you can create these directly for the product concerned, you are more likely to want to create them

for the following or a combination of the following:

Customer

Customer group

Category of products (for more information, see Prices at Category Level)

Product group

These are generally defined directly on the Pricepage.

Taxes


Page 18 of 56
http://help.sap.com/saphelp_crm700_ehp02/helpdata/en/46/5752e401a208e7e10000000a114a6b/content.htmhttp://help.sap.com/saphelp_crm700_ehp02/helpdata/en/4a/8202f3e6425752e10000000a421937/frameset.htm


19/56

Technical name: CRMM_PR_TAX

Set type for assigning the data required for tax determination to a product.

By assigning sales taxes to a product, you determine how a product is taxed. This entails specifying the following:

Country and region

Specifies in what country and region the tax applies.

Tax type

Any form of sales tax or withholding tax, such as VAT or excise duty.

Tax group

This classifies the product according to the rate of tax charged on it.

The main form of tax on sales in Germany is VAT (value-added tax). Most products are subject to the full rate of VAT, certain products, such as basic

foodstuffs, are taxed at a reduced rate, and others are not taxed at all.

There are therefore three product tax groups: one for products taxed at the full rate; one for reduced-rate products; and one products that are not taxed.

Tax tariff code

For certain countries (for example, Brazil, Poland, and India), it is not sufficient to specify a tax group. To uniquely identify a product for tax purposes in these

countries, a tax tariff code is used.

Example 1

A product is to be taxed at full rate in Germany:

Product: 4711

Country: GermanyProduct tax group: Full

Example 2

A product is to be taxed at half rate in Brazil:

Product: 4712

Country: Brazil

Product tax group: Half

Tax tariff code: NBM1

Customizing

You make the settings required for product taxes in Customizing for Customer Relationship Management, by choosing Basic Functions Taxes Basic

Settings Tax Types and Tax Groups .

Units of Measure

Technical name: COMM_PR_UNIT

Set type containing a base unit of measure, alternative units of measure, and the conversion factors for these units, that is how the alternative unit of measure is

converted to the base unit of measure.

Products can be stored, sold, and delivered in various units of measure. The following units can be specified for products:

Base unit of measure

Alternative unit of measure

Sales unit (part of sales data)

Delivery unit (part of sales data)

The base unit of measure is the basic unit used for these processes. It is automatically used as the basis for calculations if no other unit is specified. To use other

units of measure, they must first be defined as alternative units of measure with conversion factors.

In business transactions, such as the sales order, you can replace the base unit of measure proposed by the system with an alternative unit of measure.

Quantities specified in alternative units of measure are automatically converted to the base unit of measure.

You can define any number of alternative units of measure. For materials (not for services), you can also enter weights, volumes, and dimensions for each unit of

measure.

When you change a unit of measure or conversion factor for a particular product, these changes will apply to any pricing records that exist for this particular

product.

You can only use base units of measure that have been defined in Customizing for SAP Web Application Server, by choosing General Settings Check Units

of Measurement

Example

Note


Page 19 of 56


20/56

Descriptions

Technical name: COMM_PR_SHTEXT

Set type containing the descriptions created for a product. You can create descriptions for a product for all languages defined in the system. However, you can

only create descriptions for those products that originate from a system with the same logical system name as the CRM Server.

When creating a product, you can enter a description in your logon language in the general data of the product, as well as in the Descriptionsassignment block

(set type) for all defined languages. When changing products however, a description can only be changed in the Descriptionsassignment block.

Products can be saved without a description. This is the standard setting in the system. This means that you can save a product even if it has no description. This

setting can be changed in Customizing for Cross-Application Components, by choosing SAP Product Basic Settings Define Characteristics of System

Messages . The default warning message that is issued in this situation can be changed to an error message.

When a product is uploaded to SAP ECC without a description, a description is created in the logon language, as an ERP material master record has to have a

description. The product ID is used as the description.

Notes and Attachments

Various sources of information available for products.

Notes and Sales Notes

Technical names: COMM_PR_LGTEXT, COMM_PR_LGTEXT1, COMM_PR_LGTEXT2

Various text types are available for products. They are divided into two main types:

Basic texts (not dependent on a distribution chain)

Sales texts (dependent on a distribution chain)

Each text type can be created once in each language for each product. Text types that are specific to a distribution chain can be created once in each distribution

chain and language for a particular product.

Three set types are available for texts:

All text types can be maintained on the set type COMM_PR_LGTEXT (Texts)

Only organization-independent text types can be maintained on the set type COMM_PR_LGTEXT1 (Basic Texts)

Only distribution-chain-dependent text types can be maintained on the set type COMM_PR_LGTEXT2 (Sales Texts)

Text Types

SAP delivers five organization-independent text types and five distribution-chain-specific text types:

Org.-Independent Text Types Distribution-Chain-Dependent Text Types

Basic Text Sales Text

Inspection Text Sales Inspection Text

Internal Note Internal Sales Indicator

Basic Eye-Catcher Text Sales Eye-Catcher Text

Basic Price Eye-Catcher Text Sales Price Eye-Catcher Text

Products fr om Other Systems

All text types can be used for products created in SAP CRM. However, where products have been created in an external system, you can only create and

change text types which are not downloaded to SAP CRM.

Text types which are exchanged between SAP ECC and SAP CRM are as follows:

SAP ECC SAP CRM

Basic data text (service) Basic TextBasic data text (material) Basic Text

Inspection text (material) Inspection Text

Internal note (material) Internal Note

Customizing

You can define your own text types, text determination procedures, and access sequences in Customizing for Customer Relationship Management, by choosing

Basic Functions Text Management .

You can also define which text types are allowed for a product type by choosing Customer Relationship Management Master Data Products Settings for

Product Type Assign Text Object and Text Determination Procedure . This is done indirectly us ing a text determination procedure.

Attachments and Thumbnail

You can attach different types of documents to a product using content management functionality.

For more information, see CRM Content Management.

You can also attach a thumbnail to a product, thus providing a picture of the product in its general data. The image is assigned in the normal manner as forattachments. However, the attachment must be designated as the default document in the document properties, and BDS_IMAGE selected as the document type.


Page 20 of 56
http://help.sap.com/saphelp_crm700_ehp02/helpdata/en/46/3ede33fddf2f91e10000000a1553f6/frameset.htm


21/56

Sales Data

You can create sales data for products in the Distribution Chainsassignment block. Sales data is created for a specific distribution chain, consisting of a sales

organization and distribution channel, which need to have been defined in the organizational model.

FeaturesThe Distribution Chainsassignment block shows all distribution chains for which sales data has already been created. To create sales data for a distribution chain

without any sales data as yet, you click Newand select the relevant distribution chain.

You can also create new sales data by copying the data from a specific distribution chain to another distribution chain. To do this, you select the distribution chain

from which you want to copy the data, click Copy, and select the relevant distribution chain from the entries displayed. Only those distribution chains are

displayed for which sales data can be created for the product.

If a product does not originate from SAP CRM, sales data cannot be created for new distribution chains, but only for those for which sales data has already been

created.

You have the option of changing this behavior in Customizing for Customer Relationship Management, by choosing Master Data Products Allow Changes to

Product Data . This involves making settings for the product types 01 (materials) and 02 (services) and the following set types:

CRMM_PR_SALESA (Sales: Control Fields, Quantities)

CRMM_PR_SALESG (Sales: Groupings)

More Information

For more information about sales notes, see Notes and Attachments.

Sales: Control Fields, Quantities

Technical name: CRMM_PR_SALESA

Set type containing sales data on a product. As this set type is dependent on a distribution chain, a distribution chain has to be selected before data can be

entered.

The set type is evaluated when an order is created and in pricing. You can specify:

The unit of measure in which the product is sold (sales unit).

A minimum order quantity in base units of measure, which is the minimum quantity a customer can specify during order entry.

The delivery unit in which the product is delivered. Only exact multiples of the delivery unit can be specified. For example, a delivery unit of 30 bottles means

that 30, 60, or 90 bottles can be delivered, but not 100.

A sales status, indicating whether the product can be used in an order in a specific distribution chain or whether it is blocked. If you set the status Blocked

(Warning), a warning message appears in the order when the product is used. An error message is issued for the status Blocked (Error).

An item category group. This is a grouping of products which is used by the system to determine item categories when processing business transactions.

A pricing reference product, which is used by the system as a reference for pricing.

Whether the product qualifies for a cash discount.

The tax location (delivering location) of the product, which is represented by an account.

Success R ate (CRMM_PR_SUCCESS)

The Success Ratefield is technically a set type that displays the success rate for a particular product and distribution chain. The figure indicates as a

percentage the number of quotations successfully converted into sales orders, as compared to the total quantity of quotations for this product.

The information displayed in the field is derived from SAP NetWeaver BI. If a sales history is available for a specific product, this value also serves as the default

value for the order probability (the likelihood that a sales order is initiated on the basis of the quotation).The field is display-only and the data cannot be changed. When a product is copied, the sales data is copied as well, with the exception of the success rate.

Similarly, when a distribution chain is copied in an existing product, the success rate is not copied.

You can however change the success rate value manually for a specific product using the report CRM_MAINTAIN_SUCCESS_RATE.

The Success Ratefield is delivered as a hidden field and is available in the configuration tool.

Sales: Groupings

Technical name: CRMM_PR_SALESG

Set type allowing you to group products for various purposes. As this set type is dependent on distribution chains, a distribution chain has to be selected before

data can be maintained.

The set type is evaluated when an order is created and in pricing.

It contains various fields for grouping purposes. They allow you to group together products in a simple manner and use them in various ways:

Pricing conditions (field Product Group)


Page 21 of 56
http://help.sap.com/saphelp_crm700_ehp02/helpdata/en/46/57447a01a208e7e10000000a114a6b/content.htm


22/56

Commission calculation (field Commission Group)

Volume rebate settlement (field Volume Rebate Group)

Revenue or sales deduction account determination (fieldAccount Assignment Group)

Your own analyses (product groups 1 5)

A sales category can be sp ecified for a particular distribution chain and used for specific purposes within applications such as pricing and trade promotions.

However, certain applications such as partner/product ranges (PPRs) only interpret the organization-independent product category assignment.

The sales category is not used in the same way as product categories, and does not influence the interface or other aspects of product maintenance.Settings made to this category on the Product Hierarchypage will not be effective on the Productpage.

You make the relevant Customizing settings as follows:

You define the groups you require in Customizing for Customer Relationship Management, by choosing Master Data Products Special Settings for Sales

Operations .

The sales category you use must belong to the hierarchy assigned to the application Sales. You can check these settings in Customizing for Cross-Application

Components , by choosing SAP Product Product Category Assign Category Hierarchies to Applications .

Material Data

Basic Data on Materials

Technical name: COMM_PR_MAT

Set type containing the item category group and division for materials.

Item Category Groups

An item category group represents the item categories allowed for a product. It enables products to be grouped together from a business p erspective and the

relevant item category to be determined when processing business transactions.During business transaction processing, the system determines the item category based on the item category group specified for the product, and the business

transaction type, and proposes it in the respective document. This determines how the item is processed in the business transaction, such as whether it is

subject to the availability check, whether standard pricing or free-of-charge pricing applies, and whether it is relevant for quotations.

When you enter a product in a sales order, for example, with a certain item category group, the system finds the relevant item category based on the item

categories assigned to the relevant transaction type of the item category group.

You define item category groups in Customizing for Customer Relationship Management, by choosing Transactions Basic Settings Define Item Category

Group .

You make the settings required for item category determination in Customizing for Customer Relationship Management, by choosing Transactions Basic

Settings Define Item Category Determination .

Divisions

A division is an attribute in organizational management. If a header division is not used in your system, the division exists only at item level and is derived from

the product data. You specify in Customizing whether a header division is being used.

Although a division is not required in SAP CRM and can be deactivated, a division is required for data transfer with SAP ECC, as SAP ECC can only process

documents and master data entered with a division. The division specified in SAP CRM must also be available in SAP ECC.

If you are not using divisions in SAP CRM you can set this function to inactive and use a dummy division instead for data transfer to SAP ECC. This enables the

data transferred to be processed further in SAP ECC.

You can set divisions to inactive and specify a dummy division to be used instead in Customizing for Customer Relationship Management, by choosing Master

Data Products Special Settings for Sales Operations Define Division Settings .

You define divisions in Customizing for Customer Relationship Management, by choosing Master Data Organizational Management Division Settings

Define Divisions .

Global Trade Item Number (GTIN)

Technical name: COMM_PR_GTIN

The Global Trade Item Number (GTIN) is a 14-digit number which includes various EAN/UCC numbering structures and is used to uniquely identify a product

worldwide. EAN/UCC product identification numbers allow a unique identifying GTIN number to be derived in the system. All EAN/UCC numbers are considered

as 14-digit numbers, right justified and zero filled where necessary.

Note


Page 22 of 56


23/56

A GTIN is assigned to the product together with a unit of measure. As more than one unit of measure can be specified for a product, this means a product can

have more than one GTIN.

During an initial or delta download, EANs can be transferred from SAP ECC to SAP CRM as follows:

Only the EANs corresponding to the EAN/UCC-8, UCC-12, EAN/UCC-13, and EAN/UCC-14 standards can be transferred from SAP ECC.

As more than one EAN can be assigned to a material in SAP ECC per unit of measure but only one GTIN per unit of measure in the product master in SAP

CRM, only the EAN with the Main EANindicator is transferred.

A GTIN can only be maintained for the product type Material, not for services.

53 sap crm product

Documents