53 Sap Crm Product

PRINT FROM SAP HELP PORTALDocument: Products URL: http://help.sap.com/saphelp_crm700_ehp02/helpdata/en/ed/bfb2ce6a6a46af92172c4ff901f125/frameset.htm 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 express permission 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 may 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 warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices. Note This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included. PUBLIC © 2013 SAP AG or an SAP affiliate company. All rights reserved. Page 1 of 56 Products Products are goods which are the object of a company's business activities. Products can be tangible, such as a PC, or intangible, such as services like PC maintenance. The product master provides you with all information on the products that your company purchases and sells. It is the central source from which product-specific data can be retrieved. Product information is used in marketing, sales, and service processes. The product master functionality is integrated into various business roles and therefore provides all functionality you require for working with products within the relevant business context. Product data includes the information required for specific business processes (such as customer inquiries, sales orders, service processes, contracts), and other basic data that essentially describes and categorizes the product. For example: Data of a descriptive nature such as size and weight Data with a control function such as the item category group for determining the item category for each item in an SAP CRM order This information is stored in individual product master records. The integration of such data in a single database object eliminates redundant data storage. Features Product Types The product type describes the basic characteristics of a product. It also determines to which product categories a product can be assigned, thus defining the structure of the product and how it can be used. The following product types are available: Material Service Warranty Financing Financial Service Intellectual Property (IP) Attributes and Set Types Attributes are used to describe products and are grouped together into set types. The use of set types make it possible to model a product in a detailed manner in your system. For more information, see Set Types and Attributes. Categories and Hierarchies Categories and hierarchies are used for structuring purposes, and allow you to group together products according to different criteria. 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 through the assignment of categories. For more information, see Product Hierarchies. Relationships Relationships can be created between products and other products or objects to represent certain product information. For example, service parts, services, or accessories might be available for a particular product, or products may contain or belong to other products, such as sets and prepacks. Alternative IDs Alternative ID types can be defined in the product master and used in business processes instead of the product ID. Alternative IDs therefore allow you to use an identification in your business processes that conforms to industry standards, for example ISBN, serial number, vehicle identification number. You define alternative IDs in Customizing for Cross-Application Components, by choosing UI configuration on the SAP Easy Access screen under SAP Product Alternative Product IDs , and create the necessary Master Data Products Create UI Configuration for ID Type (see report documentation). Competitor Products Competitor products allow you to record information about products sold by your competitors and therefore in direct competition with your company's own products. Competitor products are technically products with the product type Material, and are created on the Competitor Product page. More Information Specifics for Mobile Sales/Service (Laptop): Product Maintenance Concepts Set Types and Attributes Set types are groups of attributes that are used to describe products. They are stored in the system as database tables. PUBLIC © 2013 SAP AG or an SAP affiliate company. All rights reserved. Page 2 of 56 Note 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 Product page 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 Technical Name Description COMM_PR_MAT Basic Data on Materials COMM_PR_GTIN Gobal Trade Item Numbers CRM_PR_RESIDVL Financing-Dependent Attributes Set Types for Services Technical Name Description 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 PUBLIC © 2013 SAP AG or an SAP affiliate company. All rights reserved. Page 3 of 56 Technical Name Description 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 a set 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 No Yes No No multiple use Organization-independent 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 Use indicator, 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 Use indicator, 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 types are those without additional key fields. Example: Single-Line Set Type PUBLIC © 2013 SAP AG or an SAP affiliate company. All rights reserved. Page 4 of 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 Organizational 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 Product page. 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-Relevant indicator. The extraction structure will contain a field for the selected attribute. By setting the Relevant for BW Selection indicator, 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 Range tab page, you can specify either single values or value ranges for the attribute. Example To describe a monitor, you define the attribute screen diagonal as 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. Example You define the attribute Color with the values Red, Green, and Blue. A car can be either red, green, or blue. However, you define the attribute Optional Extras with the values Radio and 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. Note 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. PUBLIC © 2013 SAP AG or an SAP affiliate company. All rights reserved. Page 5 of 56 add your views to the relevant overview pages in transaction BSP_WD_CMPWB: 1. where x = product type). 2. for example. For more information about how to do this. check and adapt the configuration created in the component PRDGENSET. Generate UI Configuration for Set Types 1. The configuration has been created with the object = PRODUCT and object subtype = <set type ID>. for example. see the documentation for the report CRM_UIU_PROD_REPOSITORY. 3. Page 6 of 56 . Create the UI configuration for your set types on the SAP Easy Access screen under Master Data Products Create UI Configuration for Set Type . After generation. see Enhancement Set. Assign your set types to the relevant overview pages on the SAP Easy Access screen under Master Data Products Assign Set Types to Overview Pages . You have created an enhancement for each overview page you want to extend. PUBLIC © 2013 SAP AG or an SAP affiliate company. PRD02OV. 2. enhancement set ZPROD. PRD01OV for product). Procedure 1. In the transaction BSP_WD_CMPWB. check in the transaction BSP_WD_CMPWB that the runtime repository has been generated correctly in the relevant overview pages and the component PRDGENSET. see the documentation for the report CRM_UIU_PROD_CONFIG. 2. Note that for multiple-value attributes. see Create Enhancements. and go to the tab Configuration. Add Set Types to Overview Pages To add the set types to the overview pages as new assignment blocks.Prerequisites 1. You have to do this specifically for each set type. 2. You have already created an enhancement set. This has to be done for each overview page (for example. Execute the report for every set type and overview page in which the set type is to be included (PRD0xOV. 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 02 Distribution Chain View PRDDC PRDDC/DCOV 03 Financing PRD07OV PRD07OV/FSProdOV 03 Distribution Chain View PRDDC PRDDC/DCOV 05 Warranty PRD05OV PRD05OV/WarrantyOV 07 Financial Service PRD07OV PRD07OV/FSProdOV 07 Distribution Chain View PRDDC PRDDC/DCOV 04 IP PRD04OV PRD04OV/IPProdOV 04 Distribution Chain View PRDDC PRDDC/DCOV For more information. For more information. Select the relevant component and enhancement set. 2. Select the relevant overview page view. you also have to create an enhancement for the component PRDGENSET. All rights reserved. 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 SLDCSetEF Distribution-Chain-Specific Multiline Set Type MLDCSetEL Distribution-Chain-Specific Single-Line Set Type with Multiple-Value Attributes SLMVSeteOVVS SLMVAttreOV Single-Line Set Type with Multiple-Value Attributes SLMVDCSetELVS Distribution-Chain-Specific SLMVDCAttrEL For more information. PRD02OV/ServiceOV. Note If the set type contains multiple-value attributes. Assign Set Types to Overview Pages 1. additional component usages are generated in the component PRDGENSET. This report (CRM_UIU_PROD_REPOSITORY) generates the runtime repository for the set types so that they can be displayed on the overview page. you cannot always use the set type ID as the name. 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. Select the view (PRD01OV/CustomHeader) and. Make sure that the views are in the correct order and the relevant load option has been selected. 5. For more information. as appropriate. do so by choosing Enhance Component (for more information. for example. the attribute ZCOLOR has the name ZZ0010. choose a different name. Choose Show Technical Details to display the technical view name. This copies the view controller class and the context class so that you can enhance them. Prerequisites The additional field is available in the business object layer (BOL) as a dependent object of the root object “Product”. You can enhance the other applications in the same way. On completion. CRM_UIU_PROD_REPOSITORY removes the generated objects from the runtime repository of the specified overview page component. PRD01OV). These could be fields from your own set types. 6. Execute transaction BSP_WD_CMPWB and enter the relevant component (for example. An empty view is provided for this purpose in the product header area. Customer set types are automatically available in BOL since the table entries required are generated when the set type is created. for example. Procedure The steps below describe how to enhance the product application PRD01. Enter the enhancement set that you created. 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. 1. You have created an enhancement set. 4. 4. In the database table ZSET1. single-line set types in the product header. This will be displayed on the overview page. ZProdSetZSET1) For the step "Define Dependency". see Enhancement Set. Enhance the view specified above (for example. 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. see Create Enhancements). Remove Set Types from Overview Pages 1.3. 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). If this applies. Change the title of the view. If you have not created an enhancement for component PRD01OV. choose PRODUCT as the superordinate node and enter the BOL relationship for the set type. BOL entity: BOL node of set type (for example. and is called. ZProdRelSetZSET1. Example You want to add the attribute ZCOLOR from the set type ZSET1 to the application PRD01. Switch to change mode to move assignment blocks from the set of available assignment blocks to the set of displayed assignment blocks. Use the transaction GENIL_MODEL_BROWSER (component set PROD_APPL) to check that there is a relevant BOL node which contains the new field. You have to do this for each component that you want to enhance. for PUBLIC © 2013 SAP AG or an SAP affiliate company. “Product Details” for products and “Service Details” for services. Page 7 of 56 . 2. a new context node is generated with an associated context node class (with the name ZL_PRD01OV_CUSTOMHEADER_CN01. choose in the structure Context Context Node and click Create with the secondary mouse button. 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 Note The product header is the topmost assignment block displayed on the overview page. The relationship between the product and ZProdSetZSET1 is called ZProdRelSetZSET1. 5. on the right-hand side of the screen. Adding Fields to the UI Product Header View You might want to make additional fields available on the UI in the product header data. 2. All rights reserved. 4. enabling you to include your own fields. as well as the configuration of mutiple-value attributes. such as “_”. PRD01OV/CustomHeader) by clicking Enhance with the secondary mouse button. You can only include organization-independent. The dependent object for the set type ZSET1 is called ZProdSetZSET1. for example. 3. If you want to use your own implementation of this BAdI. 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. 2. you can implement your own getter methods for the specific field in the generated context node class and thus override the standard behavior. 3. me->create_property( focus_bo ). Method GET_V_ZZ0010 for your own input help. The superclass CL_PRD_HEADER_CONTEXT_NODE provides a generic input help. METHOD constructor. ENDMETHOD. you can use CRMC_PRSEA_ATTR in your own implementation. 6. PUBLIC © 2013 SAP AG or an SAP affiliate company. the search views are located in the BSP components PRD01QR and PRDIOQR. 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. to change the ready for input status of the field. 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). the additional attributes are available in the configuration tool of the BSP component workbench and can be set to visible. CALL METHOD super->constructor. are automatically set to not ready for input. You make this setting in Customizing for Customer Relationship Management under Master Data Products Basic Settings Add Attributes to Search Structure . If a set type is not assigned to a category or is referenced. All rights reserved. if required. Create a new configuration for the view PRD01OV/CustomHeader. You can define your own implementations for this method in your own BAdI implementation. If this generic solution does not meet your requirements. 8. me->base_entity_relation = 'ZProdRelSetZSET1'. Go to the generated context node class and change the inheritance. 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.example). 3. You can also use this method to have full control over the search. a suitable search execution class derived from CL_COM_PRSEARCHSCENARIO_BASE. for example. The standard attributes are processed further by the calling method PREPARE_DB_RANGE_SEARCH. These are PRD01QR/Search for the main search view. 9. and PRDIOQR/Search (used for main search view and in search help dialog boxes). Only the search execution class you return is then used in the search. you set the EV_READY indicator to true in your implementation. If you have changed the superclass to CL_PRD_HEADER_CONTEXT_NODE. or enhance the existing configuration and add the new field (context node ZSET1. After maintaining your entries you have to transport them manually. Change the existing method ON_NEW_FOCUS New code: Syntax 1. Description fields. To do this. METHOD on_new_focus. You have the following options: 1. field ZZ0010). you must implement the following methods in the generated context class: New instance method CONSTRUCTOR (Public) Code: Syntax 1. 7. If you want. A default implementation of this BAdI is active and is executed automatically. For the UI. This means that it should then be able to handle all criteria. Example Method GET_I_ZZ0010. After you have added the appends to the search structure. If a search request contains the added attributes. You can also just return a filter class (a class that implements the interface IF_COM_PRSEARCHFILTER). Page 8 of 56 . The new fields are automatically set to ready for input or not ready for input (method GET_I_S_STRUCT of the superclass). me->base_entity_name_inst = base_entity_name. Enter the class CL_PRD_HEADER_CONTEXT_NODE as the new superclass. It is taken into account in the calling method. PRD01QR/SearchHelp for the search help views (dialog boxes). An attribute for which you have maintained fixed values or a value table in the attribute definition therefore automatically has an input help. 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. you can do this by providing. the field is also not ready for input. but it also means that you have full responsibility for the search. 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. for example. If you just want to make small changes to the existing implementation. 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. This has the following advantages: Input helps are already implemented in the superclass (method GET_V_S_STRUCT). ENDMETHOD. Development System Consolidation System Quality/Test System Production System ). Set types are created as local objects and are therefore assigned to the package $TMP. You are advised to create them in the development system and then transport them within your landscape to the quality and production systems. Choose Execute. 6. 5. The purpose of a hierarchy depends on the business criteria involved and your company's requirements. the set type is transported to the given systems (for example. Prerequisites A transportable package exists. Take one set type where this attribute is used and transport the complete set type. Once the transport request has been released and transported. A transport request has been created. 4. All rights reserved. enabling you to transport your objects between systems. choose Display/Change. The transport system has been set up correctly. Product Hierarchies Product hierarchies provide a structuring mechanism for modeling purposes within the product master. any modifications or enhancements have to be transported additionally. For example. “products” includes both products and objects. Additional set types can be assigned to lower-level categories. choose Maintain Set Types and Attributes. and the data included in data exchange and archiving. it will also be possible to maintain the set type using APIs. the set type needs to be assigned to a transportable package and included in a transport request. Choose Set Types /Attributes Transport Set Type and enter the ID of the set type to be transported.Also see Note 1026956. You can also create these objects in the quality and production systems. 2. specify the package to which you want to assign the set type. Note In the documentation about product hierarchies. An example is shown below (note that the set types shown are not standard set types. Structure The categories within a hierarchy are arranged hierarchically. however you must ensure that the users involved have the appropriate authorizations. However. The BDoc structure or API structure is extended during this process. All lower-level categories inherit the product type and set types from the higher-level category. On the SAP Easy Access screen. To transport a set type to a production system. Transport all set types where this attribute is used. In the dialog box that appears. Then choose Include in Transport Request. and choose Enter. specify the transport request and choose Enter. Page 9 of 56 . A hierarchy can be multilevel and used for control or informative purposes. Procedure 1. but examples of customer-defined set types): PUBLIC © 2013 SAP AG or an SAP affiliate company. Note If you set the Create API Append indicator. 3. Product hierarchies consist of categories and are used to group products according to different criteria. you should consider the following points to avoid errors and data inconsistency: Attributes and set types should be created in the same system. Transport functionality is available. In the dialog box that appears. you add some values to an attribute definition. Release the transport request. Once a set type has been transported to a production system. Transporting Set Types to Production Systems The system in which you create your set types and attributes depends on your system landscape. You have the following options: Create a workbench transport directly for the domain definition of this attribute. This overrides the higher-level assignment between the hierarchy and application. only products of this product type can be assigned to the category. by choosing SAP Product Product Category Assign Category Hierarchies to Applications : You can assign a base hierarchy to a specific product type. but to only one hierarchy for each product type. A base category is a category belonging to the base hierarchy. it is not possible to assign the set type to both categories. Base Categories and Hierarchies The base hierarchy used either for products in general or for specific product types. Note The same rules apply to the assignment of relationship types. by choosing SAP Product Settings for Product Type Number Assignment Define Number Ranges for the Product Type "Material" /Define Number Ranges for the Product Type "Service". The base category assigned to a product determines the product IDs allowed when a product is created. The set types themselves appear as assignment blocks on the Product and Object pages. You define the number ranges for internal and external number assignment in Customizing for Cross-Application Components. do not use the hierarchy R3PRODSTYP as the base hierarchy for services. Assigning a product type to a category makes it possible to assign set types to the category. A product can therefore only be assigned to one category in each hierarchy. 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 assigned to more than one category within a hierarchy. Each product created must be assigned to a category from this hierarchy. This hierarchy is assigned to the application Product. A product can be assigned any number of categories. Therefore even if two categories are in different hierarchies but have the same product type. All rights reserved. Page 10 of 56 . A product can be assigned to more than one category as long as the categories belong to different hierarchies. 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. Base Hierarchies Replicated from SAP ECC The main base hierarchy generally replicated from SAP ECC is the base hierarchy for Material/Service R3PRODSTYP. which is the basic hierarchy defined for products in general or for a specific product type. when you first create a product you must assign it to a base category. which is required to create products. but create a new hierarchy in SAP CRM. 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.If a product type is assigned to a category. assigning a hierarchy to the application Product enables it to be used as a base hierarchy. Number ranges are defined for other product types in Customizing for Customer Relationship Management. However. It is the starting point when you create a product. If a base hierarchy is not assigned to a product type. You assign product hierarchies to applications in Customizing for Cross-Application Components. by choosing Settings for Product Type Master Data Products Number Assignment . Defining Hierarchies as Base Hierarchies Within the product master. the hierarchy specified for the application serves as the base hierarchy for all product types. PUBLIC © 2013 SAP AG or an SAP affiliate company. see Prices at Category Level. You can reassign products on the SAP Easy Access screen under Master Data Products Recategorize Products . PUBLIC © 2013 SAP AG or an SAP affiliate company. for example. You have defined the partner determination procedures you require in Customizing for Customer Relationship Management. A hierarchy is constructed like a tree structure with a root category that includes all other categories. Referenced Relationship Types Displayed in Objects An option available for objects. Certain data is inherited within the hierarchy. Only certain relationship types can be referenced. Inheritance Certain fields can be inherited by lower-level categories. The system indicates which relationship types have been inherited. which are available for selection in the input help. If a product is assigned to more than one category. General Data and Control Data You can specify the following: Whether a user is authorized to display. by choosing Basic Functions Partner Processing Define Partner Determination Procedure . For more information. enabling these relationship types to be created for a product belonging to this category. test system or production system) in Customizing for Cross-Application Components. You have defined authorization groups in Customizing for Cross-Application Components. by choosing SAP Product Product Category Transport Categories . see Inheritance Within Hierarchies. You may. and data at category level. Who is responsible for the category. You can transport categories and hierarchies to the relevant systems (for example. change. If you assign them yourself. you can specify a partner determination procedure to determine which parties can be assigned to the object in the Parties Involved assignment block on the Object page. The system indicates which set types have been inherited. thereby enabling you to structure the information you require on your products. Hierarchies comprise data specified at hierarchy level. which applies to the entire hierarchy. enabling the relationships of the reference product to be displayed for the object concerned. by choosing SAP Product Basic Settings Allow Product References for Individual Objects .Creation of Categories and Hierarchies Product hierarchies are used to classify products and group them according to different criteria. 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). the system checks them against the numbering scheme. see Referencing Data from Products. or create products belonging to this category. or they can be assigned automatically (numeric only). What options are available on the Product page: Whether products can be assigned. by choosing SAP Product Product Category Define Category Numbering Schemes . Categories Categories define which set types and relationship types are allowed for a product. 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. Assigned Relationship Types You can specify which relationship types should be assigned to the category. Standard Schema The entry you make indicates that the product schema (hierarchy) displayed is a standard schema. and the product manager for lower-level categories. the assignment cannot simply be deleted. Prices Prices can be created for products at product or category level. For more information about inheritance. For more information about creating prices. If so. for example. all set types and relationship types for the categories to which the product is assigned can be used. This assignment block is only visible if an object family has been specified for the category and referencing has been activated in Customizing for CrossApplication Components. 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. This option is only available for categories within the base hierarchy. All rights reserved. want to specify the brand manager as the person responsible for the highest-level category. which applies to lower levels within the hierarchy. They are used primarily to describe differences within a business context. Once a category has been assigned to a product and the data saved. The root category is the highest-level node within the hierarchy and does not generally contain any control information. you might categorize your products according to their technical properties or how they are used. Prerequisites You have defined numbering schemes for your product hierarchies in Customizing for Cross-Application Components. by choosing SAP Product Basic Settings Define Authorization Groups . 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. and whether they should derive their data from a template. Page 11 of 56 . You have defined the alternative ID types you require in Customizing for Cross-Application Components. 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. 2. 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. The relevant maintenance group delivered in the standard version is PRCAT_CRM. You specify prices for the relevant category in the Assigned Prices assignment block on the Product Hierarchy page. You can create. PRCATHIER1 and PRCATHIER2. PUBLIC © 2013 SAP AG or an SAP affiliate company. see Pricing and The Pricing Process. by choosing Customer Relationship Management Master Data Products Product Category Pricing . 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. Prices can be specified on the Product Hierarchy page for an entire category of products: 1. The access sequence maintained at the condition type level defines the access steps required for condition determination. as the access sequence within the condition technique is used to determine which pricing condition is relevant. and delete prices with the price types defined in the standard version. are supported and delivered in the standard system. 4. Customer Relationship Management Master Data Products Product Category Pricing Assign Product Hierarchy to Pricing-Relevant Hierarchy Assign your product hierarchy to the pricing-relevant hierarchy. surcharge. you specify validity periods for the price records you create. As with other conditions.Prices at Category Level Pricing conditions are used to calculate prices in business transactions. The pricing steps are processed when triggered by SAP CRM order management. The Assigned Prices assignment block is not available on the Product Hierarchy page if the product hierarchy is not relevant for pricing. 3. and surcharges. The condition types supported include. check the Customizing for the pricing-relevant hierarchy R3PRODHIER in the Customizing activity Assign Field Catalog Fields to Pricing-Relevant Hierarchy. instead of at the product level solely for individual products. assign the sales hierarchy downloaded from SAP ECC to R3PRODHIER. such as prices. This is particularly advantageous when working with a large number of products. see Prices. Prices at category level are not inherited within the hierarchy. and discount. as pricing conditions. Page 12 of 56 . Pricing is based on the condition technique. If you have downloaded pricing conditions from SAP ECC. can be defined at the category level for an entire category of products. For more information. for example. such as sales orders and purchase contracts. For more information about product prices. discounts. price. 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. Pricing conditions can be specified for individual products on the Product page and for an entire category of products at category level in the Assigned Prices assignment block on the Product Hierarchy page. Features Pricing is based on the condition technique. The pricing-relevant hierarchy R3PRODHIER is used to display pricing conditions replicated from SAP ECC. change. All rights reserved. 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 . 3. and the Referenced indicator then set for lower-level categories.Inheritance Within Hierarchies Certain fields within product hierarchies are inherited by lower-level categories. Inheritance can be restored by changing the value of category H12111 to the same value as the higher-level categories (from Y to Z). 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. The value is changed for category H1211 to Y. 4. in each of these products individually. The Referenced indicator cannot however be deselected for lower-level categories. The value X is now changed to Z for category H1. This enables you to save time. The value X is maintained for the highest-level category H1 and inherited by lower-level categories. Example 1. H12. Template Framework Definition The template framework is a technical environment where you create and maintain mini-templates for the master data object SAP Product. This new value is inherited by H11. This means that this data does not have to be maintained for each category within the hierarchy. Any changes made subsequently to the mini-template are also reflected in the products that reference it. 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. which the products then reference. Note however the following exceptions: Inheritance can be interrupted for templates. The mechanism by which inheritance is interrupted is shown in the example below. This is the point at which inheritance is interrupted. 5. you maintain this data once only in a mini-template. but not by H12111 and the categories below it. This new value is inherited by the categories H12111 and H12112. Page 13 of 56 . Instead. including Referenced indicator Assigned relationship types Inherited fields cannot be changed for lower-level categories. 2. All rights reserved. A set type can be assigned to a higher-level category (Referenced indicator not set). and in this way you can make mass changes quickly and PUBLIC © 2013 SAP AG or an SAP affiliate company. see Working with Mini-Templates. Another change to the value of category H1 (new value W) is inherited throughout the hierarchy. and H121. For more information. Use The template framework simplifies master data maintenance by giving you access to mini-templates when you create or change products. 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-Enabled when you create a new set type. but rather represents a structure in the application that can be filled with values. of changes made to mini-templates. A text is displayed. Mini-templates are defined in Customizing and assigned to product category hierarchies in the standard system. Mini-templates are therefore not assigned directly to products. In order to avoid unwanted mass changes. which are in display mode and therefore cannot be maintained. such as SAP BI or SAP CRM. Mini-templates can either be differentiation key-dependent or -independent. mini-template-enabled product set types reference the data in mini-templates that are assigned to product categories. Features Assignment of Mini-Templates to Products You assign mini-templates to categories in category and hierarchy maintenance. they are cascaded into all the relevant clients in the target system. Usage of Mini-Template Data You use mini-template data in product maintenance. Here. an authorization concept ensures that only the appropriate users can change or delete mini-templates. Working with Mini-Templates Use You use the template framework to maintain mini-templates. see Creation of Categories and Hierarchies. During product maintenance. indicating from which mini-template and category the data has been derived for a particular product set type. If a mini-template is found. and the mini-template data is once again displayed. Mini-templates can be inherited from higher-level categories within a hierarchy. Mini-templates are used to maintain data for set types. 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 mini-template data is read at runtime into the corresponding set type’s fields. It does not contain any values itself. The set type’s fields then become ready for input and you can overwrite the mini-template data with your own data. Read strategies in the template framework define the sequence in which data is accessed for a product. containing different values in each case. such as BI or ERP systems. Distribution of Changes to Mini-Templates When changes to mini-templates are transported. or maintain an existing set type ○ Choosing Set Type -> Activate Templates in the menu for set types that have already been generated or delivered. Which mini-templates are assigned to a specific product is therefore determined implicitly when a product is assigned categories in product maintenance.easily. its data is read to the corresponding attributes of the product if this product does not already have its own data. a where-used list ensures that you are aware of which products reference a mini-template. If distribution is required. Page 14 of 56 . Prerequisites Before you can work with mini-templates in product maintenance. can be based on one mini-template type. Structure The template framework consists of the following parts: · Mini-template types A mini-template type signifies the smallest set of attributes you can use to build a mini-template. However. by choosing Cross-Application Components -> SAP Product -> Templates -> Maintain Mini-Templates. which can be reused by many product master records. a number of mini-templates. You can switch back to the referenced data by choosing Delete Own Data. Thus. the categories for the product in question are read at runtime. before you change or delete the mini-template in question. Integration The template framework facilitates the transfer to external systems. and that can be called up only in the display mode. ● Maintain the appropriate data for your mini-templates in Customizing for SAP Product. In addition. All rights reserved. this does not mean that the changes are automatically distributed to external systems. For more information. you should schedule a variant of report TFW_DX_TEMPLATE_CHANGES PUBLIC © 2013 SAP AG or an SAP affiliate company. · Mini-templates A mini-template is a concrete occurrence of a particular mini-template type. Your own data is deleted. A differentiation key-independent mini-template and a differentiation key-dependent mini-template are then generated automatically for each set type. but only to product categories. If you want to distribute the changes to an external system. it is not possible for you to delete it. Thus. and thus any changes made to a particular mini-template will be reflected in all the products that reference it. In this way. or you can deactivate it. the worklist is stored in the database table TFW_DX_MINITP. by choosing Templates -> Schedule Data Exchange of Changes to Mini-Templates in Customizing of the SAP Product. This allows you to distribute changes made to mini-templates to external systems. Integration in SAP NetWeaver Business Intelligence The integration of Products in SAP NetWeaver Business Intelligence (SAP NetWeaver BI) is divided into two essentially different areas. According to the active read strategy delivered for the SAP Product. Page 15 of 56 . If you cancel at this point. You should note that you cannot define your own read strategies. If you are authorized to change mini-templates. All rights reserved. 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. The results are displayed in a dialog box. Where-Used List Use Many products can reference the same mini-template. However. You can either use the read strategy delivered by SAP. the data contained in the mini-templates is then no longer available for use in your products. SAP delivers read methods for the SAP Product. where you can process it later. the sequence in which data is read for products that do not have their own data. an entry is made in the table TFW_DX_JOB. PUBLIC © 2013 SAP AG or an SAP affiliate company. the product’s own data is read before reference product data. the attribute values are only valid for a specific sales organization and a specific distribution channel. Features The where-used list is triggered when you attempt to change or delete a mini-template. the dialog box mentioned above for scheduling report TFW_DX_TEMPLATE_CHANGES does not appear automatically. You can schedule the distribution to external systems of mass changes caused by changing mini-templates. Features Read strategies can consist of several read methods. You should carry out the scheduling using the view V_TFW_DX_JOB. in the latter case. 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. and thus. Checks are run to determine all the products that reference the minitemplate in question. 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. which prevents redundant scheduling. SAP CRM Set Types (Standard) Set types can be created as either distribution-chain-dependent or distribution-chain-independent. If the mini-template is being used. Where set types are distribution-chain-dependent. which in turn is read before the data in mini-templates assigned to product categories. describing different ways of reading data for your products. a further dialog box gives you the option of scheduling a background job for the report TFW_DX_TEMPLATE_CHANGES.● periodically ● or once only. such as ERP or SAP BI. you must therefore schedule a job for this report manually. after an import in the relevant clients of the target system. Read strategies determine the sequence in which the read methods are called up. for which mapping rules are already available in the standard Business Content. 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 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. The following DataSources are provided for the InfoObject 0CRM_PROD (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. This standard Business Content only needs to be activated. Page 16 of 56 . 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: PUBLIC © 2013 SAP AG or an SAP affiliate company.Standard set types used in Products are 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 Material or 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 Material or 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. All rights reserved. the data selection can be restricted later from SAP NetWeaver BI using this field. The individual InfoObjects will therefore remain compact and the number of attributes required later in a query can be better restricted. If the number of attributes is very high. the product GUID. the total number of attributes for these InfoObjects will increase considerably and may reach the technical limit of 249 attributes. When the transaction data is transferred. PUBLIC © 2013 SAP AG or an SAP affiliate company. you may want to create several of these InfoObjects and group the attributes thematically. Option 2: Create new InfoObjects If quite a large number of new attributes is anticipated or if the attributes are of a new type. update rules). you are advised to create a new InfoObject ZMY_PROD (or similar) and append the attributes to it. contracts). If the set type contains attributes which require a text DataSource. there are basically two options: Option 1: Include new attributes in existing InfoObjects The attributes of type Material or Service that need to be transferred to SAP NetWeaver BI can be transferred as attributes of the InfoObject 0CRM_PROD (Product).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 system does not generate any objects in SAP NetWeaver BI. Integration The following table explains how terminology differs between the WebClient UI and Customizing. these must be made available by the application. these are also generated. and the missing meta data (InfoObjects and transfer rules) created. This InfoObject must have the same data type and length as the InfoObject 0CRM_PROD or 0CRM_PRFI. the attributes of type Financing can be transferred as attributes of the InfoObject 0CRM_PRFI (SAP CRM Financing Product). the distribution-chain-dependent attributes of type Financing can be transferred as attributes of the InfoObject 0CRM_PRFISL (SAP CRM Financing Product Sales View). the total number of attributes for these InfoObjects will increase considerably and may reach the technical limit of 249 attributes. and append the attributes to it. sales orders. 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. Prices are calculated using the pricing engine. the product GUID (key in SAP NetWeaver BI) contained in the transfer structure must be copied to the relevant fields (communication structure. compounded with the InfoObjects 0CRM_SALORG and 0DISTR_CHAN. There are basically two options: Option 1: Include new distribution-chain-dependent attributes in existing InfoObjects The distribution-chain-dependent attributes of type Material or Service that need to be transferred to SAP NetWeaver BI can be transferred as attributes of the InfoObject 0CRM_PRODSL (Product Sales View). For SAP CRM distribution-chain-independent attributes for products. Page 17 of 56 . 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. If the number of attributes is very high. The modeling of master data is very important for transaction data and queries. The procedure is similar for SAP CRM distribution-chain-dependent attributes for products. This InfoObject must have the same data type and length as the InfoObject 0CRM_PRODSL or 0CRM_PRFISL. 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. As a result. Functions Prices Prices are used for pricing purposes in business transactions (quotations. Before the DataSources generated in the application system can be transferred to SAP NetWeaver BI . As a result. you are advised to create a new InfoObject ZMY_PRODSL (or similar). This is possible because all InfoObjects for the product have the same data type and length. 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. 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. you may want to create several of these InfoObjects and group the attributes thematically. the modeling must be specified within SAP NetWeaver BI. If a field is also designated as relevant for selection. The individual InfoObjects will therefore remain compact and the number of attributes required later in a query can be better restricted. All rights reserved. However. When distribution-chain-dependent transaction data is transferred. by choosing Master Data Conditions and Condition Technique Condition Technique: Basics Create Maintenance Group .WebClient UI Customizing Price Condition Maintenance Group Customizing Activity Maintenance Customer Relationship Management Master Data Conditions and Condition Technique Condition Technique: Basics Create Maintenance Group Group Price Type Condition Maintenance Group Entry Customer Relationship Management Master Data Conditions and Condition Technique Condition Technique: Basics Create Maintenance Group (combination of condition type and condition table) 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. or dependent on other factors such as distribution chain or customer. you must assign the condition group to the application SAP CRM in Customizing for Customer Relationship Management. Each assigned combination of condition type and condition table constitutes a price type. 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. All rights reserved. discount. see Prices at Category Level) Product group These are generally defined directly on the Price page. It determines which fields are available for specifying price information on the Product page and what type of scale can be created for the specific price. This is currently defined as specific to a sales organization and distribution channel: Product Price: Condition type 0PR0. which defines how the price is calculated. you must enter the user parameter PRC_CALC_TRACE and the parameter value X in your user preferences (transaction SU3). Technically the price type is an entry in the condition maintenance group. Features Pricing Procedure The mechanism by which prices are calculated is complex. condition table SAP005 You might also want to create discounts or surcharges. Normally you create a standard price for a product. Price Type The price type determines the type of price involved. The data required for calculating the price can be derived from the pricing information specified for the following: Sales order. If you want to use the pricing functionality in the product master. and surcharge. For example. you can determine if condition values are changed by condition value formulas. If you want to view details of price calculation. you must assign the product-specific condition tables and types to the appropriate condition group in Customizing for Customer Relationship Management. Page 18 of 56 . For example. you can determine how the system uses user exits to calculate prices. see The Pricing Process. condition table SAP004 Customer-Specific Product Price: Condition type 0PR0. by choosing Master Data Products Special Settings for Sales Operations Assign Condition Group to Application CRM . such as gross price. that is which condition types apply and the sequence in which they are calculated. which might be relevant for a certain customer or on a certain date. you can determine which condition rates are set by scales. service order. Although you can create these directly for the product concerned. Currency conversions Scales If scales are used. Taxes PUBLIC © 2013 SAP AG or an SAP affiliate company. For more information about pricing. quotation. Price Calculation You can view price details for items. you can analyze prices and determine how the following are calculated: User exits If user exits are used. Condition exclusions Quantity conversions You can view sales unit to base unit conversions and condition unit to base unit conversions. This can be simply the price the product actually costs. It enables a number of prices to be calculated. or contract Product Business partner This information is accessed and evaluated in a pricing procedure. To use other units of measure. you can replace the base unit of measure proposed by the system with an alternative unit of measure. by choosing Basic Functions Taxes Basic Settings Tax Types and Tax Groups . and one products that are not taxed. It is automatically used as the basis for calculations if no other unit is specified. that is how the alternative unit of measure is converted to the base unit of measure. and dimensions for each unit of measure. Most products are subject to the full rate of VAT. and delivered in various units of measure. and India). you determine how a product is taxed. are taxed at a reduced rate. You can define any number of alternative units of measure. Brazil. All rights reserved. You can only use base units of measure that have been defined in Customizing for SAP Web Application Server. certain products. it is not sufficient to specify a tax group. To uniquely identify a product for tax purposes in these countries. Example The main form of tax on sales in Germany is VAT (value-added tax). Example 1 A product is to be taxed at full rate in Germany: Product: 4711 Country: Germany Product 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. Tax type Any form of sales tax or withholding tax. Note When you change a unit of measure or conversion factor for a particular product. such as VAT or excise duty. and others are not taxed at all. these changes will apply to any pricing records that exist for this particular product. Units of Measure Technical name: COMM_PR_UNIT Set type containing a base unit of measure. volumes. you can also enter weights. Poland. Quantities specified in alternative units of measure are automatically converted to the base unit of measure. and the conversion factors for these units. alternative units of measure. Tax group This classifies the product according to the rate of tax charged on it. Page 19 of 56 . 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. There are therefore three product tax groups: one for products taxed at the full rate. they must first be defined as alternative units of measure with conversion factors. Products can be stored. In business transactions. This entails specifying the following: Country and region Specifies in what country and region the tax applies. by choosing General Settings Check Units of Measurement PUBLIC © 2013 SAP AG or an SAP affiliate company. sold. For materials (not for services).Technical name: CRMM_PR_TAX Set type for assigning the data required for tax determination to a product. a tax tariff code is used. such as the sales order. such as basic foodstuffs. Tax tariff code For certain countries (for example. one for reduced-rate products. By assigning sales taxes to a product. The product ID is used as the description. You can create descriptions for a product for all languages defined in the system. Products can be saved without a description. This means that you can save a product even if it has no description. thus providing a picture of the product in its general data. When changing products however. Text types which are exchanged between SAP ECC and SAP CRM are as follows: SAP ECC SAP CRM Basic data text (service) Basic Text Basic data text (material) Basic Text Inspection text (material) Inspection Text Internal note (material) Internal Note Customizing You can define your own text types. When a product is uploaded to SAP ECC without a description. as well as in the Descriptions assignment block (set type) for all defined languages. the attachment must be designated as the default document in the document properties. where products have been created in an external system. PUBLIC © 2013 SAP AG or an SAP affiliate company. Notes and Attachments Various sources of information available for products. and access sequences in Customizing for Customer Relationship Management.-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 from Other Systems All text types can be used for products created in SAP CRM. You can also attach a thumbnail to a product. you can only create and change text types which are not downloaded to SAP CRM. you can only create descriptions for those products that originate from a system with the same logical system name as the CRM Server. This is done indirectly using a text determination procedure. 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. you can enter a description in your logon language in the general data of the product. The image is assigned in the normal manner as for attachments. Attachments and Thumbnail You can attach different types of documents to a product using content management functionality. However.Descriptions Technical name: COMM_PR_SHTEXT Set type containing the descriptions created for a product. a description can only be changed in the Descriptions assignment block. by choosing SAP Product Basic Settings Define Characteristics of System Messages . as an ERP material master record has to have a description. Page 20 of 56 . This is the standard setting in the system. COMM_PR_LGTEXT2 Various text types are available for products. 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. This setting can be changed in Customizing for Cross-Application Components. For more information. All rights reserved. COMM_PR_LGTEXT1. and BDS_IMAGE selected as the document type. 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 . text determination procedures. The default warning message that is issued in this situation can be changed to an error message. Notes and Sales Notes Technical names: COMM_PR_LGTEXT. When creating a product. by choosing Basic Functions Text Management . However. However. Text types that are specific to a distribution chain can be created once in each distribution chain and language for a particular product. see CRM Content Management. a description is created in the logon language. which is used by the system as a reference for pricing. 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). Sales: Groupings Technical name: CRMM_PR_SALESG Set type allowing you to group products for various purposes. when a distribution chain is copied in an existing product. which is represented by an account. A minimum order quantity in base units of measure. The set type is evaluated when an order is created and in pricing. you select the distribution chain from which you want to copy the data. the success rate is not copied. a distribution chain has to be selected before data can be entered. consisting of a sales organization and distribution channel. click Copy. To do this. a delivery unit of 30 bottles means that 30. Similarly. but not 100. If you set the status Blocked (Warning). An item category group. Features The Distribution Chains assignment block shows all distribution chains for which sales data has already been created. The figure indicates as a percentage the number of quotations successfully converted into sales orders. To create sales data for a distribution chain without any sales data as yet.Sales Data You can create sales data for products in the Distribution Chains assignment block. see Notes and Attachments. An error message is issued for the status Blocked (Error). you click New and select the relevant distribution chain. which need to have been defined in the organizational model. Whether the product qualifies for a cash discount. Page 21 of 56 . Only exact multiples of the delivery unit can be specified. Sales: Control Fields. or 90 bottles can be delivered. As this set type is dependent on a distribution chain. The delivery unit in which the product is delivered. You can however change the success rate value manually for a specific product using the report CRM_MAINTAIN_SUCCESS_RATE. indicating whether the product can be used in an order in a specific distribution chain or whether it is blocked. This involves making settings for the product types 01 (materials) and 02 (services) and the following set types: CRMM_PR_SALESA (Sales: Control Fields. with the exception of the success rate. For example. The Success Rate field is delivered as a hidden field and is available in the configuration tool. Quantities) CRMM_PR_SALESG (Sales: Groupings) More Information For more information about sales notes. You can specify: The unit of measure in which the product is sold (sales unit). Sales data is created for a specific distribution chain. All rights reserved. A pricing reference product. You can also create new sales data by copying the data from a specific distribution chain to another distribution chain. as compared to the total quantity of quotations for this product. The tax location (delivering location) of the product. a warning message appears in the order when the product is used. the sales data is copied as well. 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. and select the relevant distribution chain from the entries displayed. As this set type is dependent on distribution chains. A sales status. but only for those for which sales data has already been created. Only those distribution chains are displayed for which sales data can be created for the product. 60. They allow you to group together products in a simple manner and use them in various ways: Pricing conditions (field Product Group) PUBLIC © 2013 SAP AG or an SAP affiliate company. by choosing Master Data Products Allow Changes to Product Data . Quantities Technical name: CRMM_PR_SALESA Set type containing sales data on a product. If a sales history is available for a specific product. which is the minimum quantity a customer can specify during order entry. This is a grouping of products which is used by the system to determine item categories when processing business transactions. You have the option of changing this behavior in Customizing for Customer Relationship Management. Success Rate (CRMM_PR_SUCCESS) The Success Rate field is technically a set type that displays the success rate for a particular product and distribution chain. It contains various fields for grouping purposes. When a product is copied. sales data cannot be created for new distribution chains. The information displayed in the field is derived from SAP NetWeaver BI. If a product does not originate from SAP CRM. The field is display-only and the data cannot be changed. PUBLIC © 2013 SAP AG or an SAP affiliate company. All rights reserved. You can check these settings in Customizing for Cross-Application Components. a division is required for data transfer with SAP ECC. by choosing Master Data Products Special Settings for Sales Operations Define Division Settings . EAN/UCC product identification numbers allow a unique identifying GTIN number to be derived in the system. as SAP ECC can only process documents and master data entered with a division. This enables the data transferred to be processed further in SAP ECC. The sales category you use must belong to the hierarchy assigned to the application Sales. and whether it is relevant for quotations. and the business transaction type. by choosing Transactions Basic Settings Define Item Category Determination . by choosing SAP Product Product Category Assign Category Hierarchies to Applications . If a header division is not used in your system. When you enter a product in a sales order. 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. with a certain item category group. Settings made to this category on the Product Hierarchy page will not be effective on the Product page. This determines how the item is processed in the business transaction. by choosing Master Data Organizational Management Division Settings Define Divisions . You define item category groups in Customizing for Customer Relationship Management. During business transaction processing. Although a division is not required in SAP CRM and can be deactivated. such as whether it is subject to the availability check. Item Category Groups An item category group represents the item categories allowed for a product. by choosing Master Data Products Special Settings for Sales Operations . All EAN/UCC numbers are considered as 14-digit numbers.Commission calculation (field Commission Group) Volume rebate settlement (field Volume Rebate Group) Revenue or sales deduction account determination (field Account Assignment Group) Your own analyses (product groups 1 – 5) A sales category can be specified for a particular distribution chain and used for specific purposes within applications such as pricing and trade promotions. It enables products to be grouped together from a business perspective and the relevant item category to be determined when processing business transactions. The division specified in SAP CRM must also be available in SAP ECC. certain applications such as partner/product ranges (PPRs) only interpret the organization-independent product category assignment. right justified and zero filled where necessary. 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. Note The sales category is not used in the same way as product categories. the system finds the relevant item category based on the item categories assigned to the relevant transaction type of the item category group. Page 22 of 56 . You make the settings required for item category determination in Customizing for Customer Relationship Management. However. and proposes it in the respective document. You specify in Customizing whether a header division is being used. the system determines the item category based on the item category group specified for the product. and does not influence the interface or other aspects of product maintenance. for example. Divisions A division is an attribute in organizational management. whether standard pricing or free-of-charge pricing applies. the division exists only at item level and is derived from the product data. Material Data Basic Data on Materials Technical name: COMM_PR_MAT Set type containing the item category group and division for materials. by choosing Transactions Basic Settings Define Item Category Group . You define divisions in Customizing for Customer Relationship Management. You make the relevant Customizing settings as follows: You define the groups you require in Customizing for Customer Relationship Management. You can set divisions to inactive and specify a dummy division to be used instead in Customizing for Customer Relationship Management. This means there is a relationship to a physical product. and specify which type of message should be output in the fields Online and Batchl. The data that you enter for the physical object is distribution-chain-specific. All rights reserved. Batchl = E Financing-Dependent Attributes Technical name: CRM_PR_RESIDVL During the course of a leasing process. The residual value curve can be overridden by the residual value curve specified for the related financing product. rented. This data controls the residual value calculation that is performed on the financing product in pricing. However. It includes the residual value strategy. Service Plan (SERVICEPLAN) Set type for specifying a service interval template for the service plan. You make the relevant settings in Customizing for Cross-Application Components. The response profile is used to generate date and time intervals for the performance of service tasks. 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. or financed by a loan. For more information. Example You do not want the same GTIN to be assigned more than once. During an initial or delta download. Page 23 of 56 . This set type is available for service products with resources. PUBLIC © 2013 SAP AG or an SAP affiliate company. you can specify how the system should respond if a GTIN is assigned twice. This set type is available for service products for contracts. This set type is available for service products with resources. The system calculates the time interval within which a predefined task must be performed with reference to the service profile. device class. You enter the following data: Message number = 001. You can define the profiles on the SAP Easy Access screen under Service Maintain Availability and Response Times . a leasing contract is created for the financing product for the lessee concerned. and is available as information in subsequent resource planning. EANs can be transferred from SAP ECC to SAP CRM as follows: Only the EANs corresponding to the EAN/UCC-8. and EAN/UCC-14 standards can be transferred from SAP ECC. this means a product can have more than one GTIN. Service Data Set type data for service processes. only the EAN with the Main EAN indicator is transferred. It is used as a default value in the service item of a business transaction. a warning is output by default if the user attempts to assign a GTIN that has already been assigned. not for services. EAN/UCC-13. As more than one unit of measure can be specified for a product. see Service Level Agreements (SLA). Online = E. The service profile defines the times when a customer is entitled to a service. If no entry is made for the message. enter 001 (GTIN has already been assigned) in the MsgNo field. to which the response profile is assigned. Note A GTIN can only be maintained for the product type Material. A GTIN should generally only be assigned once. with specified availability times. The set types available specifically for services include the following and those described below: Transaction Control Fields Serial Number Processing in Service Duration of Work (CRMM_PR_SRVDUR) Set type for specifying the duration of work and time unit for a product representing the service which is to be performed. that is the object that is to be leased. Default Values for Service Contracts (CRMM_PR_SRVENT) Set type containing the default service profile and response profile to be used in service contracts in which the service is stipulated. Resource Requirement (CRMM_PR_SRVRR) Set type containing a rule as the default value specifying how the executing service organization which is to perform the service is determined automatically in the service item of the business transaction. You create a new entry. UCC-12. and the residual value curve.A GTIN is assigned to the product together with a unit of measure. by choosing SAP Product Basic Settings Define Characteristics of System Messages . You define service interval templates on the SAP Easy Access screen under Service Maintain Service Interval Templates . Warranty Data Set type data for warranties.For periodic services. and is used in service orders. You can define templates for the different interval types. for example. This set type is available for both service products for contracts and service products with resources. The indicator value 2 is suitable for situations where individual parts exist in SAP CRM as objects. If serial numbers are also transferred from SAP ECC to SAP CRM. You define item category groups in Customizing for Customer Relationship Management. the system finds the relevant item category based on the item categories assigned to the relevant transaction type of the item category group. The indicator value 1 allows you to record individual parts involved in the processes. All rights reserved. It enables products to be grouped together from a business perspective and the relevant item category to be determined when processing business transactions. When you enter a product in a service order. contracts and confirmations. once. which determine how serial number processing is handled in SAP CRM: 0 Default Value 1 Entries Possible. see Note 824780. and where such processes are triggered in SAP CRM and occur in SAP ECC. The set type CRM_SERIALNUM contains the attribute SERIALNO_PROCESSING (Serial Number Processing). whether a service item is relevant for resource planning. The set type CRM_SERIALNUM is not assigned to a category when material categories (DNL_CUST_PROD1) are downloaded. When materials are downloaded from SAP ECC. with a certain item category group. by choosing Transactions Basic Settings Define Item Category Determination . This determines how the item is processed in the business transaction. but without any further checks. the system determines the item category based on the item category group specified for the product. PUBLIC © 2013 SAP AG or an SAP affiliate company. In this case it is advisable to change the value from 4 to 3. During business transaction processing. If any of them require serial numbers as mandatory information in material movements. More Information Make the necessary settings for working with service products in Customizing for Customer Relationship Management. This set type is used for serial number processing in service processes. but no Check Against Master Data 2 Check in CRM Against Object 3 Check in CRM Against Object and Serial Number 4 Check in ERP Against Serial Number The value can be entered manually or downloaded from SAP ECC. A manual step is therefore required prior to the download in which this set type is assigned explicitly to the relevant categories. For more information. An item category group represents the item categories allowed for a product. but a possible integration with SAP ECC is not taken into consideration. Serial Number Processing in Service Technical name: CRM_SERIALNUM Set type containing a control indicator for serial number processing. for example. a check is performed to see if serial number profiles are assigned to the material/plant combination. intervals are available with different plan types (time-based or counter-based. or a combination of both plan types) and with different scheduling types (cyclical. It can have the following values. or scheduling with fixed values). and proposes it in the respective document. see Templates for Service Intervals. You make the settings required for item category determination in Customizing for Customer Relationship Management. and the business transaction type. the indicator value is set to 4. The item category group SRVP is provided for service products as part of standard Customizing. by choosing Transactions Basic Settings Define Item Category Group . the initial check can be made against objects. Page 24 of 56 . by choosing Master Data Products Special Settings for Service Processes Define Service Products . for example MAT_HAWA. The control indicator is used to ensure consistent material movements where serial numbers are involved. alternating. Transaction Control Fields Technical name: CRMM_PR_BTR Set type containing the item category group. For more information. or both). Warranty Catalog Data (CRMM_PRWTY_CAT) Set type specifying the type of complaint. counter reading. warranty basis (based on a period. The accounting indicator allows you to specify the procedure for price determination. By setting a status for a product. The details are specified in the form of codes. see Product Status. You can specify the type of counter involved. “Released by Department Y”. More Information Warranty Management Status Management Enables you to control the processing of a product based on the statuses assigned to it. System statuses are predefined in the system and delivered by SAP. that is the physical device that is used to record the measurements. PUBLIC © 2013 SAP AG or an SAP affiliate company. This gives you control over the costs incurred by warranties. Any warranty master record created without this set type cannot be used in warranty management. and constitute a list in which the items are either all included or all excluded. The date profile you select determines which date types and date rules you can use.The set types available specifically for warranties are described below. such as car mileage or electricity readings. service parts. as well as the dates for a time-based warranty. You make the necessary settings for working with warranties in Customizing for Customer Relationship Management. you determine its current processing status and the actions that can be performed subsequently by the system or user. All rights reserved. by choosing Master Data Products Special Settings for Warranties Define Warranties . but has no effect on standard functionality. This set type is mandatory for warranties. and even specific subjects to be fully covered or partially covered by the warranty. It informs you that a particular transaction was performed. For counter-based warranties. User Status These are additional statuses you can define to describe aspects not covered by the system status or to describe certain states in more detail. and the limit to apply in each case. User status This is a status you define yourself. or defect that is covered by the warranty. It serves as an indicator. and the procedure for billing and transferring costs to controlling. such as “Released by Department X”. Two types of status are available: System status A system status controls or regulates a process. Warranty Services (CRMM_PRWTY_SRV) Set type detailing particular services. Warranty Counter Data (CRMM_PRWTY_CNT) Set type containing data for counter-based warranties. Features The product status consists of the following: System Status You can set the following system statuses: To Archive Locked The following statuses are also available but are set by the system: Deleted Archived Can Be Archived For more information. and so on. These are specified as a list in which the items are either all included or all excluded. Page 25 of 56 . You can define flexible date rules to calculate the start date of a warranty and therefore its period of validity. A sequence of states can be specified in the status profile. damage. Note The user status function is available in the configuration tool and has to be activated. validity is defined by a limit set for usage or wear. There are two types of user status available: With a status number This means that only one state is allowed at a time. Warranty (CRMM_PRWTY) Set type containing general information such as customer or vendor warranty. Without a status number More than one state can be assigned at a time. You can define the user statuses and status profiles you require in Customizing by choosing Customer Relationship Management Master Data Products Status Management . display. The statuses shown are both system statuses and user statuses (if activated). Structured Products Structured products consist of a header product and any number of component products. If you set the status Locked for a product. being used. see Archiving the SAP Product. All rights reserved. see the document CRM Products: Customer Enhancements for Downloading and Uploading Product Master Data. you first select the relevant status profile in the Status Profile field. Technically you are creating a relationship (relationship type Component) between the header product and other products. Integration When a material is downloaded from SAP ECC. the product will not be checked again until a certain amount of time (customizable) has passed. You also specify the type of component you want to create. To enter a user status. you can implement the appropriate mapping in a user exit.Note The sales status set at distribution chain level applies only within the distribution chain and has a lower priority than the overall object status. The deletion flag MVKE-LVORM is transferred as the sales status Blocked (Warning) provided a higher sales status is not already set. Activities The product status is specified in the product details on the Product page by selecting the relevant status in the dropdown box of the New Status field. displays. For example: No new sales orders can be created for the product. The sales status cannot be transferred to SAP ECC automatically. The sales status is set according to the ERP sales status (MVKE-VMSTA) and the ERP deletion flag at distribution chain level. If you want to transfer the sales status to SAP ECC. Archived. If the product is. Page 26 of 56 . such as sales orders. and Archivable can only be set by the archiving programs. however. For more information about statuses. It should not be used for the time being. and the product quantity. The statuses Deleted. The product you are working with serves as the header product. In addition. the ERP deletion flag is set in the material header (MARA-LVORM). and prepacks) can be downloaded from Retail systems and represented in SAP CRM as structured products. You want to complete and release it at a later point in time. Features Creating structured products involves creating a product in the normal manner and then assigning components to it. You select the component products in the Components assignment block. together with the system statuses. They are used to represent a group of products as a distinct unit in certain logistics processes. For more information about archiving. structured articles (sets. The product has been downloaded to SAP CRM and contains errors. which is available as an attachment in Note 428989. this being either a set. The unit of measure is derived from the base unit of measure specified for the product. should already have been created. The product catalog is informed that the product is locked and the product no longer appears in the catalog. the status is set to Archivable if archiving has been activated in the system and the product is not used in any applications. Note the following points: All products required. For more information. this means the product can no longer be accessed by other applications. Note PUBLIC © 2013 SAP AG or an SAP affiliate company. Note The status Locked is set for configurable materials. When a product is uploaded with the product status To Archive. that is the header product and its component products. Product Status The statuses available for products are Locked and To Archive. If you set the status To Archive. During the archiving process. You might want to prevent a product from being used by other applications for the following reasons: You have created a product in SAP CRM but have not yet finished working on it. The “+” or “-” indicates adding or removing a status. or prepack. the product status is set to To Archive if the material has a deletion flag at material header level (MARA-LVORM). Structured products can be created in SAP CRM on the Product page in the same manner as other products. The dropdown box of the New Status field displays for selection any user statuses from your status profile that are selectable. as these products cannot currently be archived in SAP CRM. You should not create configurable or financing products as they cannot be used as the header or component of a structured product. The product is a seasonal product. see Status Management. the product is flagged for archiving. The variant condition key (price key) is used to create a relationship between characteristic values and the price of the configurable product. Configurable products are products for which different options are available. A list of product variants which exist for the product and were downloaded from SAP ECC is displayed in the assignment block. Constraints A number of restrictions apply when working with structured products: Component lists cannot be created in SAP CRM for header products downloaded from an ERP system. component lists can be created and changed in SAP CRM. The product model is a container for modeling data. which you can use in Product Configuration. When creating a price. The configurable materials have to be downloaded first. by choosing Master Data Products Settings for Configurable Products Allow Configurable Products for a Product Type . such as the product catalog. Multilevel structured products are not allowed. A request load can be performed if it is necessary to repeat an initial load. Select a model and click Edit to change the configuration.If a product has already been uploaded to a Retail system. Configurable Products Products for which different options are available. Product Variants A product variant is a product that has already been configured and has its own product master record in which the configuration is stored. the component list cannot be changed in SAP CRM. Bills of material (for example. a PC can have different types of monitors or keyboards. since they do not apply to the delta load. you link the price key with the associated price. Click Insert to create a new configuration model. where component information is not displayed. It contains or references all master data that is needed PUBLIC © 2013 SAP AG or an SAP affiliate company. For example. but the SAP CRM system is regarded as the master system and the changes ignored. but merely displayed. Prices Prices can be created for configurable products using the variant condition keys (price keys) created in the PME. If the header product originated in SAP CRM. Prerequisites You have specified that configurable products can be created in SAP CRM in Customizing for Customer Relationship Management. They can be displayed but not changed. The following functions are available: Select a model and click Simulation to simulate the configuration. Structured products are not supported in certain logistic processes in SAP CRM. Variant conditions are pricing conditions that depend on characteristic values. This restriction was implemented for data consistency reasons and is handled as follows: If the header product originated in the ERP system. More Information Modeling Configurable Products Importing Knowledge Bases Modeling Configurable Products You can use this function to create product models for configurable products. All rights reserved. Data can also be maintained in the ERP system. The configuration data is contained in the Configuration assignment block. Page 27 of 56 . components can only be assigned if the material category allows this. no components can be assigned to it. the appropriate relationship type is defaulted by the system. a customer can see which options are available and simulate configurations before making a selection. Features Configuration data for a product and other data related to configuration is available in the following assignment blocks on the Product page: Product Models Displays a list of configuration models in which the product is used. Integration You can download configurable materials from SAP ECC to SAP CRM. or different memory sizes. sales BOMs) cannot be downloaded from a standard ERP system as they are generally plant-specific and therefore cannot be represented in SAP CRM due to the fact that structured products currently apply to the whole company. You download the configuration models using the load object SCE. When configurable products are used in applications. the Web catalog for example. You should not make any filter settings for this object. If the header product is already the component of another structured product. If this is the case. The price of the product is recalculated depending on the options selected. before the configuration models are downloaded. Product master data is bundled in a product model. sap. see SAP Service Marketplace at http://service. Maintenance Functions: List of Product Models If you choose Edit List. inactive version after you PUBLIC © 2013 SAP AG or an SAP affiliate company. This new active version then overwrites the old active version. Change a product model When you change a product model. You can build a product structure that contains all possible components. characteristics. Creating and Maintaining a Product Model You can use this function to create and maintain a product model from product maintenance of a configurable product. the following editing functions are available: Create a new product model You can use the following fields in when you create a new product model: Name Version You enter the version number yourself. For example. The product from which you started this function is automatically in your new product model. you can make changes in an inactive version. Features You start product modeling from product maintenance of a configurable product in the SAP WebClient user interface (UI). For more information. classes. Maintenance includes various steps in product modeling. Transporting product models between customer relationship management (CRM) systems You can transport product models between different CRM systems. For more information. you can use the Apply Changes or Discard Changes buttons. you can start the configurator with a single click. More Information For information about modelling configurable materials in SAP ERP. Features Create and maintain product models You can create and maintain one or more product models right from a Configurable Product (Configurable indicator is set). characteristics. you can apply the changes. Note This function in the WebClient user interface (UI) replaces the Product Modeling Environment (PME) application. If a product model contains many products on the topmost level.during the configuration process. which had to be installed separately. All rights reserved. you could create a product model in a test system and transport it into a productive system later on. For information about installing Java. such as dependencies. as well as product structures and their relationships to one another in a hierarchical tree. Prerequisites You have installed the Configuration Engine. test the new.com/erp SAP ERP Central Component Logistics Logistics . it becomes inactive initially.General (LO) Variant Configuration (LO-VC) . You can define rules that dictate the conditions that must be met for the system to select a component in the configuration. a Java application. the value Pending appears in the Changes column. To avoid defective or incomplete product models. see Creating and Maintaining a Product Model and Editing Dependencies. This means that you can create products. In the list of product models. see Importing the Knowledge Base.com/crm-inst in the following document: Installation Guide SAP CRM Java on AIX: Oracle. Prerequisites You have made the settings for product models in Customizing for Customer Relationship Management by choosing Master Data Products Settings for Configurable Products . Testing product models To test the current configuration. classes. and use assignment block Product Models. Page 28 of 56 . it can be accessed by using any one of those products. You can work with active and inactive versions. Status Only product models with status Released are available in the product configuration. characteristic values. A component can be configurable and can have its own product structure. Products with components can inherit characteristic values from one another (both directions of inheritance are possible). and products. To accept or reject the changes.sap. To avoid defective product models. When you are finished making changes and you have tested the version. which generates a new active version from the modified version. see SAP Library for SAP ERP on SAP Help Portal at http://help. and values. From Date Product configuration always selects the latest version that is valid. Characteristics and Their Parameters You use parameters for characteristics to define product attributes for your configurable product. change the status of your product model to Released. All rights reserved. you can start a simulation to test your configuration. Creating classes and subclasses You can create classes with subclasses and assign products of the product model and components to a class and subclass. Delete a product model Maintenance Functions: Product Model The following maintenance functions are available for a product model: Create products with components You can add new configurable products to a product model. creating a product structure. You can define rules that dictate the conditions that must be met for a component to be selected. you can assign different products to one class. You can exclude values on class or product level. that characteristic changes for all the products assigned to that class. Note You use classes to group characteristics that are relevant for multiple products. If you apply the changes. If you use classes. If products have the same characteristics. choose Simulation. classes. If you discard the changes. Simulate a product model Regardless of the status and regardless of whether the product model is active or inactive. You can also assign characteristics to multiple classes (see SAP Note 1683551 and SAP Note 1695337). Page 29 of 56 . Simulation You can check the behavior of your product model in configuration. You can also create characteristics for classes and subclasses. This enables users of the product configuration to select one of several product options. can also be configurable products.make the change. components. see Editing Dependencies. though they can also be non-configurable. in turn. the new version. Status change If you have finished maintaining the product model. you activate your model for use in product configuration. The components. becomes the active version and replaces the previous active version. If you change a characteristic that is assigned to a class. or product. Characteristic Parameters The following table shows the parameters available for characteristics: PUBLIC © 2013 SAP AG or an SAP affiliate company. You can assign components to these main products (first-level products). Create a new version of an existing product model Create a new version of a product model by selecting a product model from the list and choosing Insert New Version. Assign a new version number and then open this copy of your original version to make your changes. This way. Prerequisites You have created a product model. class. which makes reuse easier. which was inactive until now. and subclasses For more information on characteristics. Create characteristics for products. Define dependencies You can save dependencies as a table or in custom functions. To do this. the inactive version is deleted and no changes are made to the active version. you create an inheritance structure: a lower-level class inherits the characteristics of the higher-level class. For more information about dependencies. Features Characteristic Assignment You can assign characteristics directly to a product or to a class. see Characteristics and Their Parameters. maximum length. The characteristic Type of processor in a PC not set The characteristic can only accept one value at any one time. (several cables with different lengths can be selected). the characteristics are characteristic inherited by the subclass. Places value. Values are not selected. For more information. Then enter the parameters for the characteristic. Data Types in Connection with the Multiple-Value Indicator Data Multiple Type Values Explanation Example Indicator The values of the characteristic can contain any alphanumerical characters. during product configuration. See table below. Decimal Number of decimal places in a numeric This field is available for data type Numeric. Invisible Characteristics can be classified as Use this parameter for product options that are not relevant for the user. Case Characteristic values can only be Sensitive entered in capital letters for fields that This field is available for data type String. required. For more information. fields for additional customized value Values value entries entries are offered in the configuration. you can select several characteristic values at the same a PC Field String String time. Value Range: Values that the characteristic can have These fields are only available for data types Numeric and Date. ID Technical name of the characteristic The name is language-independent and cannot be changed later. Default Value Characteristic value that is initially If you have defined a value range (see row Value Range: Value From. Values multiple values. Long Text In-depth. Reference Option to assign object references Calls up a selection list for available table reference fields. see Temporary explanation for the characteristic UI Settings. The default length is 30. see Creating Characteristic Description Data Type Reference Characteristics. For The characteristic Accessories in the configuration of set the characteristic. configuration Indicator The values of the characteristic can contain any alphanumerical characters. which is also the Digits/Number number of characters in a string. Language-dependent characteristic This short description can be translated by choosing Texts and creating a language-dependent name text. Display Determines whether characteristic See SAP Note 1712658. rather than the customer. After the values are entered. All rights reserved. Use this parameter for product options that the system. Allows Other Enables fields for additional customized If you set this indicator. may select. select a value displayed as the assigned value in the that falls within the defined range as the default value. PUBLIC © 2013 SAP AG or an SAP affiliate company. you can select several characteristic values at the same time. in addition to the default values. Option values are displayed as radio buttons of Characters or dropdown lists. interactive configuration. fields are no longer available for entry. Numeric Numeric Indicator The values of the characteristic can only contain numbers. Page 30 of 56 . Value To). the Value From. The characteristic The characteristic Number of processors in a server not set can only accept one value at any one time. For the The characteristic Cable length in a PC configuration set characteristic. configuration Indicator The values of the characteristic can only contain numbers.Parameter Description Comment Superclass ID of the class is inherited from the If you create a subclass for a class and assign characteristics to the class. hidden (invisible). In the lower-level classes. Read Only Characteristics can only be displayed. language-dependent You see the long text in the product configuration or simulation. Required Characteristics can be classified as Use this parameter when the characteristic must contain a value. Activities Select the class or the product to which you want to assign the characteristic and choose New. the ID of the class appears in the field for the superclass. The following data types are available: String Numeric Date Multiple Characteristics can have one value or See table below. choose Value To Delete Value From/To and enter new values. Number of Number of digits in a numeric field or This field is available for data types Numeric and String. If you want to change the contents of these fields. currency. which is represented by the characteristic values) variant condition key BLUEMETALLIC. Select price type Surcharge or Discount Variant. Prerequisites You have created a product model. select a variant condition key. unexpected interactions between the reference characteristics and user entries can be avoided. This way. Use in dependencies (setting a Use the variant condition key in formula The characteristic value Color: Blue in combination with the characteristic value key depending on several dependencies. Create values for the new characteristic. amount. you can name the variant condition keys COLOR: RED and COLOR: BLACK. In product modeling. 1. 1. The values of the characteristic are the allowed variant condition keys. In product processing. Select value VARIANT_CONDITION for the Reference Characteristic parameter. reference characteristics are used above all to transfer movement/transaction data and master data from SAP CRM to the product configuration. choose the product for which you defined variant condition keys. You enable pricing for a configurable product during the configuration process. You can use PAINT as the ID. price unit. for example. Process the formula as follows:: If: PAINT = "BLUEMETALLIC" Then: COLOR="BLUE" and "FINISH=METALLIC" Create Variant Condition Records (Product Processing) When you create condition records in product processing. PUBLIC © 2013 SAP AG or an SAP affiliate company. 2. The variant condition keys used in condition maintenance must be unique. Prerequisites You have created a configurable product and a product model. you link the variant condition key with the associated prices. Create a new characteristic for a product or class. the variant condition key that was created in the product modeling environment. if you want to link the selection of the colors red and black for a configurable car with an additional price. Enter the necessary data: sales organization. Activities Create Variant Condition Key You create variant condition keys and the corresponding value range restrictions at product or class level in product modeling. Example For example. The main data. 2. 5. Creating Reference Characteristics A reference characteristic is a characteristic that you create with a reference to a table field. In the Price Key field. You use variant condition keys to create dependencies between characteristic values and the price of the configurable product.) 4. is taken from the referenced table field. for the relevant characteristic. You use dependencies or a one-toone assignment to characteristic values to define the prerequisites that cause a variant condition key to be applied. Recommendation We recommend defining characteristics as hidden and defining dependencies with other characteristics as dependencies. You therefore characteristic value assignment in characteristic processing create variant condition keys COLOR: RED and COLOR: BLACK. such as format or length. A table field is an attribute of an object in SAP Customer Relationship Management (SAP CRM). 3. Page 31 of 56 . distribution channel.Variant Conditions Variant conditions are pricing conditions that depend on the values of configurable characteristics. A variant condition key is a multiple-value characteristic in string format. 3. choose New. (Condition type 0VA0 — Variant Price is assigned to this price type. and product unit. All rights reserved. You can use variant condition keys in your model in two different ways: Use Model Example One-to-one assignment to a Use the 1:1 variant condition key Product colors red and black are associated with a surcharge. Finish: Metallic includes a surcharge for a product. In the Prices assignment block. This value cannot be changed. see the documentation for product configuration: Reference Characteristics in SAP CRM.Features A predefined list of defined table fields is available in product modeling. Recommendation We recommend defining reference characteristics as hidden and defining dependencies with other characteristics as dependencies. Page 32 of 56 . Dependencies are used to assign the supply voltage used in Germany to the personal computer. Function Formula is available at product level and class level if you have created a function with status Released in the product model. see Dependency Syntax. for example. To derive values for characteristics. For example. you can go a step further and describe dependencies between a product and one of its components. To assign variable condition keys that then influence product pricing. All rights reserved. or display only. With dependencies as component formulas. Activities As you edit the parameters of a characteristic. To do so. Component Conditions You use component conditions to define the conditions under which a component can be selected in the configuration. For more information on dependency syntax. depending on the sold-to party: If sold-to party XY company's headquarters are in Germany. Component Formula is available at product level for a product to which you have assigned a configurable component. the value in characteristic Country of Sold-To Party should be Germany. you create a reference characteristic Country of Sold-To Party with reference to ITEM_SOLD_TO_COUNTRY. to assign various supply voltages (such as 220 V for Germany. such as a convertible with a sunroof. select a value in the Reference Characteristic field. For more information about the available table fields. you want the characteristic Country of Sold-To Party to be filled automatically. unexpected interactions between the reference characteristics and user entries can be avoided. Features Types of Dependencies There are six different types of dependencies: Dependencies as Formulas You can use dependencies as formulas to describe the dependencies that exist between different configurable characteristics and their values. To guide the user through interactive product configuration by making attributes hidden. 110 V for US) to various supplying countries in the configuration of a personal computer. This way. not allowed. and call the configuration from the order. Condition is available at product level or class level. based on selection of other characteristics. Dependencies as Component Formulas The functions in dependencies as component formulas have the same functional scope as "Dependencies as Formulas". Dependencies as Tables You can use dependencies as tables to store valid combinations of values for different characteristics and to restrict domains. Dependency Status PUBLIC © 2013 SAP AG or an SAP affiliate company. you can use dependencies as follows: To exclude combinations of characteristic values that are not allowed. Instead of technical names of the table fields or structure fields. To define rules that dictate the conditions that must be met for a component in the product structure to be selected. required. the price could increase automatically by EUR 1000 if you choose a sunroof during configuration. Component Condition is available at product level for a product to which you have assigned a component. Table Formula is available at product level and class level if you have created a table with status Released in the product model. Formula is available at product level or class level. or display only. Conditions for Characteristics You can use conditions for characteristics to guide end users through interactive product configuration. Editing Dependencies In product modeling. The result of modeling is as follows: If you create an order for a personal computer for company XY in the SAP CRM system. You can define the circumstances under which characteristics are visible. You can then use the reference characteristic when editing dependencies. this list contains alias names. selectable (allowed). required. Example During configuration. the reference characteristic Country of Sold-To Party is filled with the value Germany. Dependencies as Functions You can use dependencies as functions to create custom functions. you can make it easier to enter the syntax by using the Suggest button. Features Invisible A characteristic that you define as invisible is only visible in the configuration if the condition that was entered is not met. Read Only A characteristic that you define as read only appears in the configuration only if the condition that was entered is met. and an Explanation (optional) for the condition for the characteristic. 4. Enter an ID. You can make it easier to enter the syntax by using the Suggest button and then test the syntax that was entered by using the Check Syntax button. Display dependencies for products For products. Page 33 of 56 . see Dependency Syntax. Required. Display of dependencies for objects: Tables. Save your entries. Required A characteristic that you define as required must have an assigned value in the configuration if the condition entered in the conditions area is met. you see the characteristics that you have assigned to the current class or the current product in a table. To use the dependency in the interactive configuration. unless you have marked a spot in your coding where you want the system to offer a suggestion with the placeholder /#. Read Only. Activities 1. the system runs a syntax check. and Not Allowed. 5. Check the syntax. functions. Formula Conditions Component Formula Component Conditions If you choose the Suggest button. characteristics. In Preparation Dependencies with this status are neither available in product configuration nor in the simulation. Blocked Dependencies with this status are neither available in product configuration nor in the simulation. PUBLIC © 2013 SAP AG or an SAP affiliate company. You can then test the syntax that was entered by using the Check Syntax button. the system offers a valid text for the end of a coding line. Read Only. functions. or if you change released dependencies. or Not Allowed. choose Simulation. enter a new Condition for a product or class. this status is set automatically. you can see the released and unreleased dependencies that were defined at this level. For more information about syntax. or hidden under certain circumstances. When you change the status from In Preparation to Released. You can also see the dependencies that were defined at the class level that the product has inherited. under certain defined conditions. Conditions for characteristics are listed in a conditions area (screen areas Condition and If) and an entry area (screen area Then). not allowed. a Description. a characteristic that is assigned to a class or product is Invisible. 3. the structure of this released table or function cannot be changed. you can see the dependencies that you have used in the corresponding object and that have status Released under Dependency Types. Configuration Test To check the functions of the conditions for the characteristics. Required. it marks these errors by surrounding them with placeholders as follows: /#syntax error/#. 7. You can also set the status yourself. In screen area Dependencies. In screen area Then. products. Conditions for Characteristics Conditions for characteristics are used to make characteristics required. Not Allowed A characteristic that you define as not allowed may only be considered in the configuration if the condition that was entered is not met. characteristics. You can change the statuses of "Dependencies as Formulas" and "Dependencies as Tables" to Released if the table or function was also released. All rights reserved. and components cannot be deleted if they are used in released dependencies.You can set the following statuses: Released Dependencies with this status are available in product configuration and in the simulation. For each characteristic. and components For objects. in which you indicate that. 8. If this check fails. the system sets the status to Blocked. 6. Define a condition in the If field. set the status Released. Classes. If there is a released dependency that uses a table or function. tables. Displaying Dependencies Display dependencies for classes For classes. 2. read only. set the following indicators according to your needs: Invisible. Default Values for Syntax and Checking the Syntax in Dependencies When you enter dependencies of the following types. you can see the released and unreleased dependencies that were defined at this level. If the system finds errors in the syntax. When you create dependencies. Use the suggestion help. As opposed to a formula or a condition. Check the syntax. 5. enter a new Formula for a product. 3. if a multiple-value characteristic (mvChar) has values "red" and "green". 6. In the Explanation. if you select a color other than black. If the condition for the characteristic from the dependency is fulfilled. even though the conditions seem to be exclusionary. set the status Released. otherwise the configuration is incomplete. Example If COLOR <> 'black'. you enter the conditions under which the formula is to be applied. Activities 1.Note In the configuration test. In addition. The characteristics can be single-value or multi-value. component. Save your entries. Enter a condition (If field) and a formula (Then field). all released dependencies are taken into consideration. Dependencies as Tables You use a table to store permitted combinations of values for various characteristics. You can make it easier to enter the syntax for the formula part and the condition part by using the Suggest button. Note Characteristics with multiple values can lead to unexpected conflicts. To use the dependency editor in the interactive configuration. In interactive product configuration. or class. enter a language-dependent text. Then MODEL = 'Standard' In the configuration. PUBLIC © 2013 SAP AG or an SAP affiliate company. Characteristics defined as allowed or visible are only not allowed or hidden if the related condition is valued and false. Note When saving a product model. Characteristics defined as allowed or visible are only allowed or visible if the related condition is valued and true. 2. the system removes identical value combinations that occur more than once from the tables. 4. value combinations from tables are valid. All rights reserved. Page 34 of 56 . 7. In screen area Dependencies. For example. Dependencies as Formulas You use formula dependencies to do the following: Describe dependencies between different characteristics of an object Calculate and set values Restrict value ranges Set default values Features Dependencies as formulas are made up of two entry areas: a formula and a condition. You can then test the syntax that was entered by using the Check Syntax button. regardless of the sequence of characteristic valuation. the conditions mvChar = "red" and mvChar <> "red" are both met. a table can be used to map dependencies between a large number of characteristics and their values. the system automatically selects model "Standard". In the condition part (If field). this enables the following: Domain restriction Consistency check Set default values Inference of values You can infer a value for a required characteristic if the domain of this characteristic consists of one value. the following applies: Characteristics defined as required must have values assigned to them. Enter an ID and a description. you can edit the table contents. Choose Table Contents and then Import. choose New and open the input help for Characteristic. 3.csv). You can further process imported tables in the product modeling environment. You cannot enter interval values. Enter a name and a description. To be able to assign the table to a class or product. 5. Caution Use unique technical names for the characteristics and characteristic values. 7. In other words. 4. 4. In section Table Columns. Create a table with the desired table contents and save it (file format: *. Caution Assign exactly those characteristics that you have created in the table that you want to import. Note You can directly enter values that you did not enter explicitly for the characteristic. choose Tables and then choose New. All rights reserved. Note that or contain the combinations of characteristics. 2. Confirm your entries by using the enter key. 8. you can edit the table structure and its contents.Features Use this function to: Create and maintain tables Import tables Export tables for further uses Use tables in table formulas Table Maintenance Status Status Use Comment In In this status. this action cannot be undone. Select the table row where you want to enter information. Restrictions A table field may only contain exactly one characteristic value. In the product model. Use the correct case (uppercase or lowercase letters). Choose Table Contents and then Export. Create a table structure in the product modeling environment. which are the characteristic value Do not edit tables with no contents in this status. Page 35 of 56 . set the status to Released. you can only use the correct value combination in the configuration if you enhance the characteristic domain accordingly. because combinations. Blocked Released Tables with this status are evaluated in the configuration. PUBLIC © 2013 SAP AG or an SAP affiliate company. Activities Maintaining Tables 1. At this point. Set the status of the table to Blocked or Released. this can cause problems in product configuration. Enter the characteristic names in the first row of the table. the table contents are deleted. 3. However. 6. Exporting Tables You can export tables from the product modeling environment to a table-based program for further processing. Enter a name and the desired characteristics. A dialog box opens. Set the Key indicator for one or more rows in the table. 1. 1. Note The meaning of this key is described in section "Assigning a Table to a Class or Product". Choose Table Contents and then New. Enter all permitted value combinations. If you set an already filled table with this status and change Preparation you can edit the characteristics/columns that appear in the table and that the table structure. the status of the table is In Preparation. In this status. 2. Choose the desired file and where you want to save it. Importing Tables You can maintain tables in table-based programs and import them for use in your product model. A window opens in which you can select the characteristics that you want to use in the table. however. and that characteristic is available in the current class or product. as the Key. the upholstery material is derived. Example A table lists the characteristics of cars as follows: Model Transmission Drive Basis Manual transmission Front-wheel drive Silver Manual transmission All-wheel drive Gold Automatic transmission All-wheel drive The "model" characteristic is marked as the key. Set Value. in the Mapping section. Assigning a Table to a Class or Product When you have processed a table and released it. In the Type field. For characteristics that are not flagged as key characteristics. Restrict Value The effect on configuration is that when a characteristic is selected. the value for the upholstery material is automatically limited to "cloth". you can select the following as actions for the characteristics: No Value or Restrict Value. Choose your desired data here. If you select Restrict Value as both the Type and for both characteristics. PUBLIC © 2013 SAP AG or an SAP affiliate company. Read Value You cannot change this setting. If you choose "light gray" as the color. You cannot change this value. however. If you select action Set Value for characteristic "transmission". You can change this value to "all-wheel drive". When you select this value. but not all columns. and you must select a value in configuration. the system automatically selects the value "manual transmission" according to the "Basis" model in the configuration. No Value The table has no effect on this characteristic in the configuration. To do this. or Set Default. you must have entered all valid combinations in the table. Set Default The effect on configuration is that the system selects an appropriate value according to the table and the key field. it would not be valid later in the configuration. you can select No Value. If you failed to enter a combination in the table. You can change this value. you can also create a new file. you must only enter the desired derivations. which is then to be exported into the table contents (file format *. create a Table Formula for a class or product and select a table.csv). If you select action Set Default for the "Drive" characteristic. the system suggests the value "front-wheel drive" according to the "Basis" model in the configuration. All rights reserved. Example A table lists the characteristics of car seats as follows: Color Upholstery Material Light gray Cloth Anthracite Cloth Anthracite Leather Beige Leather You have set the Key indicator for both characteristics. the values of other characteristics are restricted. the system automatically selects Read Value as an action for characteristics for which you have assigned a key in the table column in section Mapping. You cannot change this value. and vice versa. the table in the configuration will read as follows in any direction: When the color is selected. Note With the table export. choose the storage location and enter the desired file name in the dialog box. If you first choose "leather" as the upholstery material. Note If you choose Restrict Value as the type. A dialog box opens. the color selection is limited to "anthracite" and "beige". This means that the assigned action is automatically Read Value.2. If this value is selected. Set Value The effect on configuration is that the system selects an appropriate value according to the table and the key field. The effect on configuration is that this value must be chosen by the user and cannot be deduced from other combinations of characteristics. Note You do not have to enter all possible combinations in the table. Page 36 of 56 . define the goal of the table formula: Restrict values This option is selected automatically and cannot be changed if you have set the Key indicator either for all table columns or for none of the table columns. in section Dependencies. Set values and defaults This option is available if you have set at least one table column (one characteristic). No Value The table has no effect on this characteristic in the configuration. You cannot change this value. the system automatically selects the Read Value action. Activities PUBLIC © 2013 SAP AG or an SAP affiliate company. 4. 2. To do so. set the status to Released. In the Mapping section. create a Function Formula for a class or product and select a function. Set the Key indicator for one or more characteristics. Note Only functions with status Released appear in the selection list. All rights reserved. The effect on configuration is that this value must be chosen by the user and cannot be determined by the function. You can then test the syntax that was entered by using the Check Syntax button. create a function with the same name as the Java function and then define which characteristics you will use as parameters in that function. Features Component conditions consist of a condition area (screen areas Component Condition and If) and an entry area (screen area Then).To be able to assign the function to a class or product. For characteristics that you have defined as key characteristics. You can make it easier to enter the syntax by using the Suggest button. If you select No Value. choose New and open the input help for Characteristic. which cannot be changed. if you created them for the selected class or product. You can assign functions to classes and products as dependency type Function Formula. the formula determines a value during the configuration.Dependencies as Functions You can create custom functions in Java and use them in product modeling. A dialog box appears in which you can select the characteristics of the product model that you want to use in the function. Component conditions are available at product level for a product to which you have assigned a component. you can select from the following actions: No Value The system uses this option as the default. At this point. Note The meaning of this key is described in section "Assigning Functions as a Dependency Type to a Class or Product". Enter a function name and a description. 5. 3. choose Functions and then choose New. Component Conditions Component conditions define the conditions under which a component is selected in product configuration. set the Select indicator for each component that you want to be selectable. Activities Editing Functions 1. Page 37 of 56 . in section Dependencies. You define the specified conditions under which the components that are assigned to the product should be selected during configuration. Assigning Functions as a Dependency Type to a Class or Product When you have edited a function and released it. Set Value If you select Set Value. Features To be able to use a Java function in product modeling. the status of the function is In Preparation. Conversely. More Information Also refer to SAP Note 870201: Implementing variant functions in Java. you see the characteristics that you selected before. under Functions. the function has no effect on this characteristic in the configuration. In section Function Parameters. For characteristics that you did not indicate as key characteristics. In the product model. you should not set this indicator for components that should not be able to be selected under the same conditions. 2. If: Upholstery material = "leather". Use the Suggest button to have the system propose the syntax. Component formulas are available at product level for a product to which you have assigned a configurable component. enter a language-dependent text. 7. To use the dependency in the interactive configuration. Example You have assigned component "sport seat" to product "car". Enter an ID and a description. 8. In screen area Dependencies. Check the syntax. Features Dependencies as component formulas are made up of two entry areas: a formula and a condition. you see the components that you have assigned to the current product in a table. and operators. you enter the conditions under which the component formula is to be applied. you can go a step further and describe dependencies between a product and one of its components. key word component is also available in the suggestion help. enter a new Component Formula for a product at the topmost level. Define a condition in the If field. Save your entries. Enter a condition (If field) and a formula (Then field). You can make it easier to enter the syntax for the formula part and the condition part by using the Suggest button. Use the suggestion help. set the status Released. To use the dependency editor in the interactive configuration. Save your entries. Dependency Syntax For the syntax in dependency processing. 4. In screen area Dependencies. The following operators and functions are available: Operators PUBLIC © 2013 SAP AG or an SAP affiliate company.1. In screen area Then. You can then test the syntax that was entered by using the Check Syntax button. Enter an ID. 6. according to your needs. the system does not differentiate between uppercase and lowercase for characteristic names. 7.RKT_MAIL_SPAM_FILTER = "N" 6. set the status Released.RKT_MAIL_BOX_SIZE = "10" component. 4. Similar to Formula. 5. With dependencies as component formulas. a Description. select a component to which the formula should refer. In the condition part (If field). object variables. All rights reserved. 3. 3. Set the Select indicator for each component. the system only selects "sport seat" in the product configuration (bill of material) if you select "leather" as the upholstery material. Use this word as a prefix of a characteristic in the component. Example If RKT_EMAIL_ACCOUNT = "STD" Then component. Then: Set Select indicator for "sport seat". Check the syntax. Activities 1. In the Component field. When you enter the following component condition. 8. 5. In the Explanation field. and an Explanation (optional) for the component condition. Dependencies as Component Formulas The functions in dependencies as component formulas have the same functional scope as Dependencies as Formulas. Page 38 of 56 . enter a new Component Condition for a product at the topmost level. 2. Length = 300 AND Width = 200 OR Two statements that have an OR relationship are linked using OR. COLOR3 = 'GREEN' String Operators Lowercase (LC) All letters are converted to lowercase. || 'bus driver' || 'driving exam' = 'bus driver driving exam' List of Built-in Conditions Expression Implied Condition IN One of the specified values must be set: Color IN ['red'. but the assigned statement may contain lowercase letters. individual elements are separated by commas. 'blue'] SPECIFIED Attribute has a value: SPECIFIED COLOR Note You cannot negate SPECIFIED. NOT (COLOR = 'blue') NOT (COLOR = 'red' AND BASIC MATERIAL = 'wood') Features Sequence of Statements In lists. COLOR2 = 'BLUE'. Page 39 of 56 .Operators Use in Dependencies AND Two statements that have an AND relationship are linked using AND. Leather seat = LC('Alpha') = 'alpha' Uppercase All letters are converted to uppercase. COLOR = 'red' OR BASIC MATERIAL = 'wood' NOT One or more statements can be negated using NOT. (UC) Leather seat = UC('Alpha') = 'ALPHA' The function is important if the assigned characteristic does not allow lowercase letters. 'green'. All rights reserved. Concatenation: The string is cut off at a maximum of 30 characters. Relational Operators = Equal to <= Less than or equal to >= Greater than or equal to < Less than > Greater than <> Unequal Operators for Values and Value Ranges = Equal to <= Less than or equal to >= Greater than or equal to < Less than > Greater than <> Unequal ?= Assignment of a default value PUBLIC © 2013 SAP AG or an SAP affiliate company. COLOR1 = 'RED'. You have created a product model. CEIL. if the decimal value is greater than or equal to five In the case of negative numbers: CEIL. +3 -4 ROUND In the case of positive numbers: +3 -3 FLOOR. no distinction is made between uppercase and lowercase. if the decimal value is greater than or equal to five User-Interface Settings Specific to Product Model You can link your product model knowledge base profile with fixed user interface parameters for use in the Web-based interactive configuration. if the decimal value is less than five. if the decimal value is less than five. Page 40 of 56 . Three predefined parameters (UINAMEs) are available: PUBLIC © 2013 SAP AG or an SAP affiliate company. Precision and Rounding for Numeric Characteristics You can use the following commands to round a value that was calculated using dependencies: Function Description X = 3.1 CEIL Lowest integer that is not less than x.1 X = -3.Subtraction / Division * Multiplication Example: CHAR_WIDTH = CHAR_LENGTH / 4 Standard Functions sin Sine cos Cosine tan Tangent exp Exponent for base e In Natural logarithm abs Absolute value sqrt Square root log10 Logarithm for base 10 arcsin Arcsine (inverse function of sine) arccos Arccosine (inverse function of cosine) arctan Arctangent (inverse function of tangent) sign Sign (plus or minus sign) of x frac Decimal part of x Example: SIN (2*3. the default settings for the relevant scenario apply. All rights reserved.14 * ANGLE /360) In functions. +3 -3 FLOOR Greatest integer that is not greater than x. If you do not set up a UI name for your knowledge-base profile. It overwrites the standard settings of the scenario. A UI name corresponds to exactly one record of configuration parameters. You do not have to change your existing knowledge-base profile. This function allows you to specifically activate or deactivate certain product-model-specific user interface functions. FLOOR. Features You edit parameter records in component uiname of Extended Configuration Management (XCM) and assign them to your knowledge-base profile by using the attribute UI Name. Function names are automatically converted to uppercase letters. Prerequisites You are using the Configuration Engine for interactive configuration. such as conflict handling.Using Arithmetic Operations Basic Arithmetic Operations You can use the following basic arithmetic operations in dependencies to perform calculations: + Addition . +4 -3 TRUNC Part of x that is an integer. Open the list of knowledge-base profiles (Profiles button). This also includes product models that you model using product modeling. conflict handling is deactivated. The history is sorted chronologically. units of measure. Page 41 of 56 . the parameters that you specified are read and the interface is displayed accordingly.SIMPLE The parameter settings of this UI name are for easy-to-configure products for which you want to use all the functions of conflict handling. The technical key. For more information about UINAME parameters. Select the desired profile. 5. 2. The old and new value. NOCONFLICTEXPL The parameter settings of this UI name are for easy-to-configure products for which you want to use conflict resolution but not conflict explanation. with the most recent change shown first. 4. see the XCM documentation. for multiline set types it indicates the line of the table. 2. for example. Enter the UI name in field User Interface Settings. it gives the distribution chain ID. and are generally separate assignment blocks. Open the knowledge base (CU33). or for product descriptions it gives the language. see Creating or Changing Knowledge-Base Objects. In the case of sales data. Here. The organizational unit for changes to sales area data. with the exception of basic data. 3. COMPLEX The parameter settings of this UI name are for complex products. For more information. Enter the UI name in field UI Name. Select a product. This is additional information identifying the product changed. It provides the following information: The area in which the change was made. All rights reserved. or descriptions. Result When you call your product in the interactive configuration with the JSP UI of the Configuration Engine. Open a product model. These are technically set types such as basic data. 3. which is incorporated in the header data. Activities Entering UI Names in Product Models in Product Modeling 1. More Information Product That Is Easy to Configure Conflict Handling Change History Enables you to see the changes made to the product data. Note You can manipulate the change history using the Business Add-Ins BAdI: Addition/Removal of History Blocks and BAdI: Changes to History Data in Customizing for Customer Relationship Management under Master Data Products Business Add-Ins PUBLIC © 2013 SAP AG or an SAP affiliate company. When the change was made and the user who made it. Entering UI Names for Product Models in SAP ERP Variant Configuration 1. Open the basic data view. The name of the field to which the change applies. You can also define your own UI names. Features The change history is a separate assignment block displaying a list of all changes that have been made to the attributes of the product. This can also be a hierarchy that was created in SAP CRM. the ERP categories will be created in the existing SAP CRM hierarchies. If a hierarchy has already been assigned. All rights reserved. 3. At the start of the download using the object DNL_CUST_PROD1. such as shopping baskets. as these will be created automatically during the initial download.Data Exchange Replicating Product Hierarchies from SAP ERP to SAP CRM Hierarchy data is replicated from SAP ERP to SAP CRM using middleware. However. Prerequisites If a product hierarchy is used in SAP ERP. If the entries do not yet exist. These are the material type. This numbering scheme is essential for the data to be created correctly. Replication of Material Types The hierarchy R3PRODSTYP has two levels: The first level contains the categories MAT_ for materials and SRV_ for services. when the hierarchies are created and assigned. and 03. The replication of hierarchy data is performed as part of the Customizing download and uses the download object DNL_CUST_PROD1. you have created the numbering scheme R3PRODHIER in SAP CRM for the product hierarchy from SAP ERP. purchase orders. the ERP material type HAWA (trading goods) is created as the category MAT_HAWA. the second level is a sublevel of MAT_ and contains the material types imported from SAP ERP. the following steps are performed during the download: 1. in orders and opportunities) Purchasing (used in Enterprise Buyer functions. for example. Page 42 of 56 . The number of levels in the numbering scheme must be the same as the number of fields in structure PRODHS. If a hierarchy has not been assigned. The data from SAP ERP that is replicated as categories is derived from fields in the material master which have grouping characteristics and are used for classification purposes. For example. material group. bid invitations. You do not generally have to make any entries manually. 02. you should generally not make any entries. and product hierarchy. a new hierarchy is created with the ID R3PRODHIER. each with the prefix MAT_. 2. A delta download is not available for Customizing objects. R3PRODSTYP. For materials. the system checks whether a hierarchy is already assigned to the applications 01. and goods receipts) Products The grouping fields from the material master are mapped to the hierarchies in SAP CRM as follows: SAP ERP SAP CRM Material type Hierarchy assigned to Product application (03): Typically R3PRODSTYP Material group Hierarchy assigned to Purchasing application (02): Typically R3MATCLASS Product hierarchy Hierarchy assigned to Sales application (01): Typically R3PRODHIER To do this. and quantities) CRMM_PR_SALESG (sales: groupings) CRMM_PR_LGTEXT2 (sales: texts) PUBLIC © 2013 SAP AG or an SAP affiliate company. The standard SAP CRM set types are assigned to the categories of the hierarchy R3PRODSTYP as follows: The following set types are assigned to the category MAT_. The relevant settings can be checked in Customizing for Cross-Application Components SAP Product Product Category Assign Category Hierarchies to Applications . or R3MATCLASS. units of measure. The following applications are relevant for the mapping processes: Sales (used. In Customizing for Cross-Application Components. and therefore inherited by all material types: COMM_PR_MAT (basic data on materials) COMM_PR_SHTEXT (descriptions) COMM_PR_UNIT (conversion of units of measure) COMM_PR_LGTEXT1 (basic texts) COMM_PR_GTIN (GTINs) The following set types are also assigned to the category MAT_ if the status Sales is assigned to the material type in SAP ERP: CRMM_PR_SALESA (sales: control fields. if you deactivate this message in Customizing ( Customer Relationship Management Master Data Products Basic Settings Define System Message Characteristics ). choose SAP Product Product Category Define Category Numbering Schemes . the categories are created in the respective hierarchy. a warning is issued. This download has to be performed before the material download. making sure that the numbering scheme corresponds precisely to the structure of the product hierarchy in SAP ERP (structure PRODHS). Note If you have created hierarchies in SAP CRM and assigned them to applications before the download is performed. Features The hierarchy to which data is mapped is determined automatically during the initial download. and the number of digits for each level must be the same as the length of the corresponding field in structure PRODHS. The initial download therefore has to be repeated for DNL_CUST_PROD1 if data is changed in SAP ERP after the initial download. However.Subsequent Changes Once you have replicated a hierarchy from SAP ERP you should not change the assignment to an application. Where the sales product hierarchy is downloaded from multiple backends. You should delete this setting and. as this will cause the material types to be imported into this hierarchy. German name “Auto” ERP1 has category 02. An initial download has to be repeated in the following cases: There are new categories in SAP ERP or existing categories have been changed Repeat the initial download to replicate the changes. leave your settings as they are and deactivate the error message in Customizing ( Customer Relationship Management Master Data Products Basic Settings Define System Message Characteristics ). by choosing SAP Product Product Category Define Category Numbering Schemes . for example. All rights reserved. The material types will then be created in this hierarchy. However. German name “Fahrrad” ERP2 has category 02. Category 02 is extended. Material types cannot be imported into given hierarchy You have specified that the given hierarchy is to be used for the application Product (03) and product type Material( Product Cross-Application Components SAP Product Category Assign Category Hierarchies to Applications ). Page 43 of 56 . Material groups cannot be imported into given hierarchy You have specified that the given hierarchy is to be used for the application Purchasing (02) ( Cross-Application Components SAP Product Product Category Assign Category Hierarchies to Applications ). The behavior described above applies equally to material groups. assign this hierarchy to the Sales application. You should delete this setting and. You should check your entries in table T179 in SAP ERP. an additional language is created and the existing language is overwritten. In Customizing for Customer Relationship Management. if you want to import the material groups into the given hierarchy. it is important that the numbering schemes in both ERP systems are the same. Note however that you are generally not advised to import material types into a customer-defined hierarchy. the entries should read as follows: Application Sales (01) Hierarchy R3PRODHIER Application Purchasing (02) Hierarchy R3MATCLASS Application Product (03) Hierarchy R3PRODSTYP If you want to use a hierarchy other than R3PRODSTYP as the base hierarchy for the product type Financing or Service. This means that the material types would be created in this hierarchy. English name “Motorbike” A download is performed firstly from ERP1. English name “Cycle” ERP2 has category 03. You should delete this setting and. you should not do this for the product type Material. if hierarchy R3MATCLASS already exists. as it is not contained in ERP2. but only if it is not being used. Multiple Backends If material types or the sales product hierarchy are replicated from several backends. and then perform a material download. This is not allowed when downloading categories from SAP ERP. Sales or Product. if you want to import the ERP product hierarchies into the given hierarchy. leave your settings as they are and deactivate the error message in Customizing ( Customer Relationship Management Master Data Products Basic Settings Define System Message Characteristics ). if you want to import the material types into the given hierarchy. the SAP CRM hierarchy is extended with the new data. However. if hierarchy R3PRODSTYP already exists. Given category ID is not suitable for numbering scheme This refers to the download of product hierarchies. This means that the material groups would be created in this hierarchy. This means that the ERP product hierarchies would be created in this hierarchy. Categories have been deleted in SAP ERP By repeating the initial download the category will be deleted in SAP CRM. If you change the hierarchy assigned to an application. leave your settings as they are and deactivate the error message in Customizing ( Customer Relationship Management Master Data Products Basic Settings Define System Message Characteristics ). The material groups will then be created in this hierarchy. This numbering scheme must correspond to the structure PRODHS in SAP ERP. As a result of downloading the category. the IDs are merged. Product hierarchy cannot be imported into given hierarchy You have specified that the given hierarchy is to be used for the application Sales (01) ( Cross-Application Components SAP Product Product Category Assign Category Hierarchies to Applications ). Example ERP1 has category 01. Category 03 is created. if hierarchy R3PRODHIER already exists. The ERP product hierarchies will then be created in this hierarchy. The result is as follows: Category 01 is not changed. choose Master Data Products Product Category Define Settings for Downloading Product Categories from SAP ERP . Typical situations in which you might need to check your data and make certain corrections are as follows: Hierarchy is used for more than one application You have probably specified in Customizing ( Cross-Application Components SAP Product Product Category Assign Category Hierarchies to Applications ) that the same hierarchy is to be used for two applications. this causes an error. then from ERP2. If a download has been performed. Note however that you are generally not advised to import ERP product hierarchies into a customer-defined hierarchy. you can assign it specifically for the product type concerned. assign this hierarchy to the Product application. You do this in Customizing for Cross-Application Components. Delta Download A delta download is not available for Customizing objects. However. this can be changed in Customizing. However. assign this hierarchy to the Purchasing application. Activities During the download the system performs the following checks and issues error messages in certain cases. The given product hierarchy does not comply with PUBLIC © 2013 SAP AG or an SAP affiliate company. Numbering scheme R3PRODHIER not maintained To import product hierarchies from SAP ERP you have to define the numbering scheme R3PRODHIER in SAP CRM. Note You cannot download SAP ERP products with the product type Material as products with the product type Service in SAP CRM. Check in Customizing for Cross-Application Components whether the storage form (lexicographical or not) is correct for the material number transferred. After doing this. All rights reserved. languages. Prerequisites Before the initial download can take place. enabling the material status to be mapped during the product download. check whether the corresponding hierarchies have been created in SAP CRM. This specifies whether the material number is stored lexicographically in SAP ERP and the length of the product ID in the ERP database. for example. which are triggered automatically when the initial download has been completed. by choosing SAP Product Basic Settings Define Output Format and Storage Format of Product IDs . how product IDs are stored in the product master and which product data can be created. You should correct either the entry in table T179 or the R3PRODHIER numbering scheme. transferred the product groups. Using transaction R3AS.the R3PRODHIER numbering scheme defined in SAP CRM. and DNL_CUST_PROD3. We recommended that you use the same settings in both systems. Transferred the middleware object CUSTOMER Transferred the following middleware objects for the class CUSTOMIZING: PUBLIC © 2013 SAP AG or an SAP affiliate company. 2. choose Basic Functions Taxes Basic Settings Tax Types and Tax Groups Assign Tax Groups to SAP ERP Tax Classifications (Product) . The relevant middleware object is MATERIAL. Activities 1. DNL_CUST_PROD1 (material types. Retail users are requested to substitute: Article for material Merchandise category for material group Features The Customizing download for materials involves the three middleware objects DNL_CUST_PROD0. The data is transferred using middleware. using middleware objects beginning with DNL_CUST_BASIS) Transferred Customizing for organizational management (for example. and product hierarchy) See Replicating Product Hierarchies from SAP ERP to SAP CRM. Subsequent changes and any new materials created in SAP ERP after this point are transferred by delta downloads. and countries. Note Unless indicated otherwise. Transferred Customizing for sales (for example. The Customizing information transferred determines. you must have: Transferred Customizing for general settings (in particular. transfer the three middleware objects for the class CUSTOMIZING. 3. Page 44 of 56 . the information contained in this info object is relevant to the ERP material master for industries and to the ERP article master for retail. material groups. The following information is transferred: DNL_CUST_PROD0 (storage form of material numbers in sending system) Information for converting the ERP material number to the product ID. transferred the units of measure. certain Customizing information must be transferred. the material master records can be downloaded. choose SAP Product Basic Settings Define Output Format and Storage Format of Product IDs . DNL_CUST_PROD3 (material statuses in sales and distribution) The Customizing settings for the material status are replicated to SAP CRM. you restart the download for object DNL_CUST_PROD1 so that the new data is selected. Defined how the product ID is stored In Customizing for Cross-Application Components. choose Master Data Organizational Management Data Transfer . A single initial download is used to download the materials required and to create them as products in SAP CRM. Replicating Material Master Data from SAP ERP to SAP CRM Material master data is transferred from SAP ERP to SAP CRM using middleware. transferred the sales offices) In Customizing for Customer Relationship Management. See the documentation for this Customizing activity for more information. On the Product Hierarchy page. Once this has been performed correctly without any errors occurring. DNL_CUST_PROD1. using middleware object DNL_CUST_SPROD) Defined the mapping of sales tax data from the SAP ERP to the SAP CRM format In Customizing for Customer Relationship Management. Replicating Customizing for Materials from SAP ERP to SAP CRM Before data can be downloaded from the material master to the product master. each with the prefix SRV_. It determines which data can be created for a product. For more information. Features The material data downloaded from SAP ERP includes the following data in particular: General material data such as the base unit of measure. There is no general sales status for the product. If you want to set up new systems with product master data or change or create a connection between existing systems. For example. certain Customizing information must be transferred. 3.DNL_CUST_PROD0 DNL_CUST_PROD1 DNL_CUST_PROD3 For more information. see Replicating Product Hierarchies from SAP ERP to SAP CRM and. For services. Activities 1. See SAP Note 515706 for information about potential problems. check whether the corresponding hierarchies have been created in SAP CRM. which has two levels: The first level contains the categories MAT_ for materials and SRV_ for services. and material type Sales data and sales texts The SAP ERP sales statuses are created in SAP CRM as statuses of the status object Sales Product (PRS). This takes approximately 1 minute. the ERP service category GRND (basic service) is created as the category SRV_GRND. numeric material numbers must have 18 positions and include leading zeros (unless you have specified the lexicographical storage format for material numbers). the information about the assignment of applications to hierarchies. the second level is a sublevel of SRV_ and contains the service categories imported from SAP ERP. On the Product Hierarchy page. Activities 1. Define which materials you want to download. The Customizing information transferred contains the ERP service category. and therefore inherited by all service categories: COMM_PR_SRV (basic data on services) COMM_PR_SHTEXT (descriptions) COMM_PR_UNIT (conversion of units of measure) COMM_PR_LGTEXT1 (basic texts) The service category download works in the same way as the category download using DNL_CUST_PROD1. Features The Customizing download for services involves the middleware object DNL_CUST_SRVMAS. This information is transferred to the hierarchy R3PRODSTYP (product subtype). Replicating Service Master Data from SAP ERP to SAP CRM PUBLIC © 2013 SAP AG or an SAP affiliate company. Using transaction R3AS. This SAP Note contains important information about how to avoid inconsistencies at database level. You do this in the filter conditions in middleware object management for the object MATERIAL using transaction R3AC1. transfer the middleware object DNL_CUST_SRVMAS for the class CUSTOMIZING. since modules are generated automatically. in particular the product hierarchy. The following standard SAP CRM set types are assigned to the category SRV_ of the hierarchy R3PRODSTYP. see Initial Load of Customizing Objects (Solution Manager: SAP CRM Configuration Structures SAP CRM Basic Settings for SAP CRM Data Replication Replication of Customizing Objects ). The following system statuses are available: I1001 (created) I1050 (blocked with warning) I1051 (blocked with error message) Only one sales status is defined at distribution chain level (combination of sales organization and distribution channel). alternative units of measure. Replicating Customizing for Services from SAP ERP to SAP CRM Before data can be downloaded from the service master to the product master. Start the data transfer for the object MATERIAL using transaction R3AS. Save your entries in the initial screen. and material descriptions and general texts (such as basic texts) Grouping characteristics. in particular. Use transaction CRMM_PRPROD to check whether problems have occurred in the assignment of pricing reference materials during the transfer. The filter conditions must be specified appropriately for the database format of the corresponding fields in the backend system. the service master records can be downloaded. see SAP Note 418886 (and related notes). material group. Note Do not create a product master using a client copy or similar procedure either in SAP CRM or SAP ERP. 2. 2. Once this has been performed correctly without any errors occurring. and the delta download. All rights reserved. The data is transferred using middleware. In particular. Page 45 of 56 . Service master data is transferred from SAP ERP to SAP CRM using middleware. Only group BOMs or BOMs from a specific plant are downloaded. If you want to set up new systems with product master data or change or create a connection between existing systems. see Initial Load of Customizing Objects (Solution Manager: CRM SAP CRM Configuration Structures SAP CRM Basic Settings for SAP Data Replication Replication of Customizing Objects) . Replication of Sales Bills of Material from SAP ERP (Structured Products) to SAP CRM You can use this function to replicate sales bills of materials (for example. More Information For more information. are not downloaded. and then select an SAP ERP system as the source site and an SAP CRM system as the destination site. Page 46 of 56 . transferred the units of measure. such as time. Prerequisites Before the initial download can take place. such as multiple BOMs. Subsequent changes and any new services created in SAP ERP after this point are transferred automatically by delta downloads. Note Do not create a product master using a client copy or similar procedure either in SAP CRM or SAP ERP. structured articles) from an SAP ERP system for retail to SAP CRM. PUBLIC © 2013 SAP AG or an SAP affiliate company. You do this in the filter conditions in middleware object management for the object SERVICE_MASTER using transaction R3AC1. you must have: Transferred Customizing for general settings (for example. start transaction R3AS. BOMs in which a configurable product is used as a header product or component are not downloaded. The reference quantity at header level is always 1 base unit of measure. see Note 418886 (and related notes) first. work unit. The only attribute at component level is the quantity (in the component base unit of measure). It contains important information about how to avoid inconsistencies at database level. This is because structured products cannot be defined for a specific organization. Activities To run the initial download. Delta downloads take place automatically when BOM data is changed in SAP ERP. BOMs in which a material is used multiple times as a component are not downloaded. Define which services are to be transferred. using the adapter object BOM. but are always valid across clients. You cannot upload bills of materials from SAP CRM to SAP ERP. these bills of material are stored as structured products. Start the transfer of data for the object SERVICE_MASTER using transaction R3AS. Alternative BOMs or different BOM usages. A single initial download is used to download the services required and create them as products in SAP CRM. specify the load object BOM. 2. and also service descriptions and texts Grouping characteristics. The relevant middleware object is SERVICE_MASTER. in particular the material group and service category Activities 1. Note that the following restrictions apply to the download: Multilevel BOMs are not downloaded. to a BOM. Also note the following restrictions in the target system: It is not possible to assign any type of validity parameters. see SAP Note 1156808. Header-level attributes of a BOM are not stored. In SAP CRM. All rights reserved. Integration The initial download is triggered in SAP CRM and is executed by middleware. Features The service data downloaded from SAP ERP that is necessary for functions within SAP CRM includes the following data in particular: General service data such as the base unit of measure. using middleware objects beginning with DNL_CUST_BASIS) Transferred the middleware object DNL_CUST_SRVMAS for the class CUSTOMIZING For more information. and conversion factors. Prerequisites You are using the following releases. You can replicate BOMs that are defined for the following types of master data in SAP ERP: Material Equipment Functional location A BOM is a list of materials that are constituent components of the above entities. such as time. Restrictions for Replication of BOMs The following restrictions apply to the download: Only BOM items of the following item categories are downloaded: I (PM structure element) L (stock item) N (non-stock item) Only group BOMs or BOMs from a specific plant are downloaded. for example. If a BOM exists for this material in SAP ERP. Integration The initial download is triggered in SAP CRM and is executed by middleware. you can also specify for each category whether you want BOM products for the reference product to be included in the product proposal.0 (with active middleware) SAP enhancement package 4 for SAP ERP 6. Assign relationship types to categories for the products/objects to which BOMs are linked. service order (and quotation). Bill of Materials for Reference Product A material that is assigned to a piece of equipment in SAP ERP as a construction type is represented as the reference product in the corresponding equipment object in SAP CRM. Choose the In-/Active pushbutton to display inactive objects. It is not possible to assign any type of validity parameters. assign the relationship types BOMHEDS and BOMITMS to the following categories: Material categories that you have downloaded from SAP ERP Your category for equipment Your category for functional locations Note: On the Product Hierarchy page. You cannot change BOM data in SAP CRM. These materials are. In the CRM WebClient UI on the Product Hierarchy page. BOMs are represented as lists of products. this is shown in the Referenced Service Parts . All rights reserved. Activities 1. BOMs in which a material is used multiple times as a component are not downloaded. the products from the BOM are included in the product proposal for transaction items. but are always valid across clients. linked by means of relationship types with the following: Products representing materials replicated from SAP ERP Objects representing equipment and functional locations replicated from SAP ERP The entries in a BOM are displayed in the Service Parts . This is because structured products cannot be defined for a specific organization. included in the product proposal in service transactions. thereby providing your service employees with more accurate. Header-level attributes of a BOM are not stored in SAP CRM.0 You have ensured that the objects to which BOMs are assigned have been downloaded from SAP ERP. If this reference product has a BOM assigned to it in SAP ERP. PUBLIC © 2013 SAP AG or an SAP affiliate company. You can use transaction R3AM1 to check whether the objects have been downloaded. Activate and set filters for the adapter object BOM_ERP in transaction R3AC1. Delta downloads take place automatically when BOM data is changed in SAP ERP. Bills of Materials in Transactions You can assign a product or object from SAP ERP as a reference product for a service contract (and quotation). Page 47 of 56 .Replication of Bills of Material from SAP ERP to SAP CRM You can use this function to replicate bills of material (BOMs) to SAP CRM from SAP ERP. Note You cannot change BOM data in SAP CRM. BOMs in which a configurable product is used as a header product or component are not downloaded. or service confirmation in SAP CRM. transaction-specific information.ERP assignment block in the equipment object in SAP CRM. or higher: SAP CRM 7. Features BOMs in SAP CRM When replicated to SAP CRM. then deselect the Inactive checkbox for the object. 2.ERP assignment block in product and object data. using the adapter object BOM_ERP. EQST (equipment). according to the product type: Set types for materials Product header data (COMM_PRODUCT) Basic data on materials (COMM_PR_MAT) Descriptions (COMM_PR_SHTEXT) Long texts (COMM_PR_LGTEXT) Units of measure (COMM_PR_UNIT) Tax data (CRMM_PR_TAX) Purchasing data (BBPM_PR_GENERAL) Sales data – order (CRMM_PR_SALESA) Sales data – pricing (CRMM_PR_SALESG) Set types for services Product header data (COMM_PRODUCT) Descriptions (COMM_PR_SHTEXT) Long texts (COMM_PR_LGTEXT) Units of measure (COMM_PR_UNIT) Tax data (CRMM_PR_TAX) Purchasing data (BBPM_PR_GENERAL) Business transaction parameters (CRMM_PR_BTR) Sales data – order (CRMM_PR_SALESA) Sales data – pricing (CRMM_PR_SALESG) Creation of Product as Material/Article in SAP ERP When a product is uploaded to SAP ERP. and in the ERP system there is no material/article whose material/article number corresponds to the product ID. this is recorded in SAP CRM in a mapping table. This may be necessary because the data is required in SAP ERP for a number of logistical processes such as procurement. Once all the necessary data has been entered. the data is processed using the ALE interface available (materials using the message type MATMAS. the product ID is used as the material/article number. it can be created as a material or article. 3. In SAP ERP. specify the load object BOM_ERP. Page 48 of 56 . 2. see Settings for Product Upload.Set a filter for a combination of the fields WERKS (plant) and STLAN (usage type) and tables MAST (material). If this is the case. the product data is transferred to the specified system using synchronous RFC (Remote Function Call). The mapping table does not contain an entry for the product and the selected ERP system. but the product data is made available in IDoc format and passed directly to the ALE inbound module. 2. but in the ERP system there is already a material/article with a material/article number corresponding to the product ID. A material/article is created in SAP ERP without internal number assignment If the material/article number is not assigned internally. No physical IDocs are generated in the IDoc database. One material or article can be created for a product for each logical system. Features You start the upload of product data to SAP ERP manually from the Product page by clicking Send to ERP. you are informed about the situation in a dialog box. controlling. or whether a material/article number derived from the product ID is already being used in SAP ERP: 1. and TPST (functional location). A material/article is created in SAP ERP with internal number assignment PUBLIC © 2013 SAP AG or an SAP affiliate company. the system uses the RFC destination to check whether the product involved has already been transferred to the system concerned. This means that the missing data needs to be entered in the upload dialog box. start transaction R3AS. 1. To run the initial download. You can decide whether the data of the material/article in SAP ERP should be overridden by the product data. and then select an SAP ERP system as the source site and an SAP CRM system as the destination site. and material category with which the article was created in SAP ERP Flag indicating whether another upload is necessary Checks Performed Before the Upload Before the upload can take place. The material/article can be created in SAP ERP without any difficulty. material group. or whether a new material/article should be created in SAP ERP using internal number assignment. Uploading Products to SAP ERP The upload function allows you to upload SAP CRM product data to SAP ERP. Data Relevant for the Upload The data relevant for the upload is derived from the following set types. For more information. Prerequisites You have specified for each product type whether products of this type can be transferred to SAP ERP in Customizing for Customer Relationship Management. and the product ID is used as the material/article number. depending on whether the SAP ERP component is being used as a retail system. by choosing Master Data Products Settings for Product Type Allow Upload for a Product Type . respectively. You can also enter a base unit of measure in case a base unit of measure was not specified in the product data. If financing products are to be uploaded. articles using the message type ARTMAS). This is the usual case when materials/articles are created. All rights reserved. Note You can only set one active filter per table for each of these fields. as a base unit of measure cannot be specified in the product data for financing products. billing. and material group with which the material was created in SAP ERP The material type. If the upload was performed successfully. financial accounting. If you do not define a filter for a particular entity. Not all data required to create materials or articles in SAP ERP is available in SAP CRM. This mapping table contains the following information: Which product was transferred to SAP ERP To which ERP system the product was transferred Under which material/article number the product was created in SAP ERP The material type. you must enter a base unit of measure. The mapping table does not contain an entry for the product and the selected ERP system. BOMs are not downloaded for that entity. industry sector. inventory management. If this is the case. the data in the mapping table in SAP CRM is updated on the basis of the current material/article data. The mapping table contains an entry for the product and the selected ERP system. see Note 495764). Delta Uploads and Downloads Any materials or articles created or changed in SAP ERP are downloaded directly to SAP CRM if the delta download is activated or an initial download takes place subsequently. The mapping table does not contain an entry for the product and the selected ERP system. 1. material group. products imported into SAP CRM using the catalog interface can also be transferred to SAP ERP. for example. Settings for Product Upload Certain information is required to be able to upload product data to SAP ERP. these products can only be uploaded individually to SAP ERP. You can also perform a manual upload at any time. For service and financing products therefore. For example. If products were created in SAP CRM as the result of a mass import. However. The messages issued in SAP ERP during the upload processing are stored in the application log in SAP ERP. 2. PUBLIC © 2013 SAP AG or an SAP affiliate company. The mapping table contains an entry for the product and the selected ERP system. you are informed about the situation in a dialog box. So that this data is not imported into CRM Middleware or SAP CRM. but in the ERP system there is already a material/article with a material/article number corresponding to the product ID. in the case of service and financing products. This function cannot be used to transfer several products at once to SAP ERP. either schedule the report COM_PRODUCT_UPLOAD_BATCH periodically in the background or start it manually. This is the usual case when a product is changed. and texts such as sales texts. The mapping table contains an entry for the product and the selected ERP system. Since all the necessary data might not be available in the system. These data segments include set types such as units of measure. but there is no longer a material/article in the ERP system with the material/article number contained in the mapping table. and overwrite the existing material/article in SAP ERP. If a particular product could not be uploaded automatically to SAP ERP without errors occurring. it may be necessary to modify or extend a material/article in SAP ERP so that processes such as procurement and inventory management can take place. and the data contained in the mapping table (material type. the CRM product data must not be affected by any changes to the material/article data in SAP ERP. conditions. using the catalog interface for example. is not uploaded. the changed product data is automatically transferred to all ERP systems to which the product was uploaded manually. you should note that they are created as service materials/articles in SAP ERP and not in the form of service or financing master data. Page 49 of 56 . If an automatic upload needs to be performed due to data having been changed. the indicator UPLOAD_NECESSARY is set in the mapping table. The material/article can be changed in SAP ERP without any difficulty. You are informed about this situation in a dialog box. when necessary. The material/article data is changed in SAP ERP on the basis of this product data. This means that the data in SAP ERP does not have to be adjusted by a manual upload. Once the errors have been corrected. relationships. The upload only applies to products which were created in SAP CRM. You will not be able to derive the product ID used in SAP CRM from the material/article number generated in SAP ERP. the entry still exists in the mapping table. To do this. the material/article is created in SAP ERP with a material/article number assigned internally. This means the original system must be the SAP CRM system. but the data contained in the mapping table no longer corresponds to the data of the material/article in SAP ERP. such as classifications. As SAP CRM is the main system for creating CRM-specific data. an automatic upload is not performed. In addition. The downloaded material/article data is not passed to the flow logic or mobile clients. industry sector. material category) corresponds to the data of the material/article in SAP ERP. If the material/article was reorganized in SAP ERP. The mapping table does not contain an entry for the product and the selected ERP system. and therefore deleted from the system. If product data is changed using the API interface. 3. and in the ERP system there is no material/article with a material/article number corresponding to the product ID. If you decide not to use the product ID as the material/article number. You are informed about the situation in a dialog box and have the option of creating the material/article again in SAP ERP. the data is discarded in CRM inbound processing if the mapping table indicates that this material already exists as a product in SAP CRM and was uploaded to the specified ERP system. the upload should be repeated for all the upload processes that failed. The sales statuses are also not uploaded (for more information. All rights reserved. the system knows to which ERP system the product data should be transferred. Constraints Only the product data itself is transferred to SAP ERP. 3. individual changes to data segments containing more than one data record are not automatically uploaded to SAP ERP. Additional data. the system attempts to find this information as follows: RFC Destination of ERP System The RFC destination is used for data exchange with SAP ERP. if you prefer. a dialog box is displayed in which you can enter the missing data. the product ID is ignored as a potential material/article number. only the material type DIEN and material types derived from this are allowed when new material/article master data is created. If a product is changed in SAP CRM after the initial upload. However. instead of internal number assignment. Provided the SAP CRM system was defined as the original system during a catalog import. meaning that this screen does not have to be processed. A material/article is changed in SAP ERP 1. Once an RFC destination has been selected. A status message in SAP CRM indicates which application log number contains the relevant message data in SAP ERP. If a product is changed in SAP CRM after the initial upload. The upload can be performed for all product types currently available. The indicator UPLOAD_NECESSARY is merely set in the mapping table and the upload can be performed later using the report COM_PRODUCT_UPLOAD_BATCH. You can decide whether you do want to use the product ID as the material/article number. the mapping table is used to derive the data required for the upload dialog box. A material/article created by an upload may be changed in SAP ERP. Each system has its own RFC destination. The mapping table containing all the material/article numbers created for the products is used to trigger the upload. 2. The first time the product is uploaded to SAP ERP.If the material/article number is assigned internally. the material type or material group has been changed. It is only in the mapping table (see Uploading Products to SAP ERP) that you can find out which material/article number was assigned internally for a particular product. Possible entries are obtained from SAP ERP using the specified RFC destination. the product ID and the generated material/article number can no longer be derived from each other on a 1:1 basis. Note To be able to derive accurate default values. this RFC destination will be displayed by default in the upload dialog box. This enables you to use product IDs on a 1:1 basis. this will not cause any problems for materials because when data is transferred. It also means that products can be more easily identified in SAP ERP. the following data is required: The material type and industry sector must be known (these are required entry fields on the initial screen of material master maintenance). The material group must be specified if purchasing data has been created for the product. the field selection options set at transaction PUBLIC © 2013 SAP AG or an SAP affiliate company. An input help is available for the fields in the dialog box. All rights reserved. if you are using retail. Only the material type DIEN and material types derived from this are allowed for service and financing products. Possible entries are obtained from SAP ERP using the specified RFC destination. Materials are created by default. Page 50 of 56 . by choosing SAP Product Basic Settings Define Output Format and Storage Format of Product IDs . If the input help lists several RFC destinations. When internal number assignment is used. If more than one RFC destination is determined. If none of the relevant ERP systems have been assigned an RFC destination using transaction SMOEAC. Note The upload function does not support all material categories at present. A value for the material group can be displayed by default in the dialog box due to the assignment of the product to an EBP material group hierarchy. the first RFC destination found is displayed by default in the upload dialog box. the following data is required: The material type. Type of Object to Be Created in ERP System (Material or Article) You can specify in the upload dialog box what type of object should be created in SAP ERP. Provided the required entry field attribute is set at transaction level (MM01/MM02). Data Required for Creating Materials When materials are created. The value 01 is the default setting for creating materials. you can set a default RFC destination by choosing System User Profile Own Data Parameters . you are advised to download the Customizing object DNL_CUST_PROD0. Internal Assignment of Material/Article Number You can indicate whether the material or article number should be assigned internally or the product ID used as the number. can be used as the article description. An input help is available for the fields in the dialog box. A value for the material group can be displayed by default in the dialog box due to the assignment of the product to an EBP material group hierarchy. you can specify that articles should be created by default by choosing System User Profile Own Data Parameters . For example. Note To make sure that the number settings are known in SAP CRM and SAP ERP. The product description can be used as the material description. to an EBP material group hierarchy. You do this in Customizing for Cross-Application Components. The system attempts by default to use the product ID as the material/article number. or the product ID if this is missing. Data Required for Creating Articles When articles are created. the only option you have is to use internal number assignment. Only the material type DIEN and material types derived from this are allowed for service and financing products. meaning that a default value cannot be determined for the material type. and material category must be known (these are required entry fields on the initial screen of article master maintenance). you can define any fields as required entry fields using the field selection options in SAP ERP. by choosing SAP Product Basic Settings Define Characteristics of System Messages . This means that whenever you log onto the system. all RFC destinations defined in the system using transaction SM59 can be selected using the input help. generic articles and variants cannot be created. In this case. In the case of purely numerical product IDs. you need to ensure that the length of the product ID was restricted to 18 characters in SAP CRM. as there is otherwise no information available in SAP ERP indicating from which product a material/article was derived. this can cause problems. However. You can change this behaviour in Customizing for Cross-Application Components. This will make the number settings defined in SAP ERP known in SAP CRM. Service and financing products are not assigned to material types. as the product ID can have up to 40 characters and the material/article number a maximum of 18 characters. A value for the material type can be displayed by default in the dialog box due to the assignment of the product to a material type product hierarchy (= product subtype hierarchy). However. the 40-character numerical product ID with leading zeros is converted to an 18-character numerical material number with leading zeros. You assign the parameter ID CRM_OLTP_OBJ_TYPE the value 02. you are advised to assign products to a material type product hierarchy and. Service and financing products are not assigned to material types. Defining Required Entry Fields For materials. Enter the parameter ID CRM_DESTINATION and the name of your RFC destination as the value.The default RFC destination and the possible RFC destinations which can be selected using the input help are determined as follows: If an RFC destination was assigned to each relevant ERP system in the Administration Console using transaction SMOEAC. You can display the valid material categories using the input help. A value for the material type can be displayed by default in the dialog box due to the assignment of the product to a material type product hierarchy (= product subtype hierarchy). As the description is not a mandatory entry in SAP CRM. The product description. material group. these RFC destinations can be selected using the input help. To avoid using internal number assignment. meaning that a default value cannot be determined for the material type. the product ID is used as the description for the material if the product description is missing. Archiving Phase . and lock these products for archiving. Features You can compare the following: Product data in the ERP back-end database and CRM database Product data in the CRM database and CDB (except customer material number) The comparison detects the following: Data that differs between the two systems Data that only exists in SAP CRM Data that only exists in SAP ERP The following DIMa objects are available for products: MATERIAL for comparing material/product data between the ERP back-end database and CRM database SERVICE_MASTER for comparing service data between the ERP back-end database and CRM database PRODUCT_MAT for comparing product data between the CRM database and CDB PRODUCT_SRV for comparing service data between the CRM database and CDB BOM for comparing bills of material between the ERP back-end database and CRM database PRODUCT_IL_MAT for comparing bills of material between the CRM database and CDB CUST_MAT_INFO for comparing the customer material number between the ERP back-end database and CRM database Note For general information about DIMa. Problems will only arise if the required entry field attribute is set at material type level. Prerequisites You have activated the archiving. in the case of articles a material group reference article is available. The status of these products is changed by the usage check to Archivable. This means that the data uploaded will not contain all required entry fields. used to detect and repair inconsistencies between objects in different systems. The usage check is dependent on the selected archiving object.Write: Writing Data to the Archive PUBLIC © 2013 SAP AG or an SAP affiliate company. see Checking Cross-Component Data Integrity (DIMa) in the middleware documentation. Process Flow The archiving and deletion of SAP Product Data must be started separately: Preparatory phase: Flagging the product for archiving A product can be selected for archiving directly from product maintenance (transaction COMMPR01) by setting the status To Be Archived. Page 51 of 56 . You can also define any fields as required entry fields for articles. Archiving the SAP Product Purpose Using archiving you can store product master data that is no longer required and subsequently delete if physically from the database. see the SAP Note 642767. The data stored in the mapping table after the first upload is displayed in the dialog box. the input fields in the upload dialog box become display fields. This allows the missing required entry field data to be added automatically. The products are deleted after preprocessing. More Information Uploading Products to SAP ERP Using DIMa for Products The Data Integrity Manager (transaction SDIMA). but not at transaction level MAL1/MAL2. but that the data can be uploaded. Archiving Phase – Preprocessing: Execute usage check for products to be archived. The archiving object for SAP Product is called PRODUCT_MD. The SAP Product Archiving Environment is completely controlled by status and is connected to the SAP Archive Information System. All rights reserved. can also be used to compare product data. For more information about using DIMa for products. Only those products that are no longer used by any application and have no reference to other objects can be archived and subsequently deleted from the database.level MAL1/MAL2 (allowing fewer required entry fields) are used. For articles. If the product has already been uploaded to SAP ERP and if a manual upload is started again. However. The required entry fields without entries can be filled later in SAP ERP in material master maintenance (transaction MM02) once the upload has been completed. this can only be done at transaction level MM01/MM02 as for materials. see Introduction to Data Archiving (CA_CARC). Restrictions The following constraints apply when archiving products in the CRM System: · Archived products cannot be reloaded into the CRM System · Products can only be deleted if they have been archived · Archived products can only be displayed in a technical view in the Archive Information System · Inactive products cannot be archived · Configurable products cannot be archived · Contents of documents are not archived. All rights reserved. has been physically deleted from the database. Display Archived Objects in Product Maintenance To display archived products in product maintenance. Locked Incomplete Archive file and database To be deleted Deletion (can be scheduled to be Archivable periodic).The product data with the status Archivable is written to an archive file. Additional Information For more information on archiving. Archiving Phase .Delete: Check Archived Data The system compares the data in the local archive with the data in the local database and sets the product status Archived for those objects that are in both the archive and the database. Archiving Phase . Page 52 of 56 .Postprocessing: The system deletes the products that have the status Archived including the associated dependent data from the database. choose Environment → Archived Products or use the transaction COMM_PRDARC. Complete Archive file Programs and Functions The following programs and functions are used for archiving SAP Products: PUBLIC © 2013 SAP AG or an SAP affiliate company. There is no status change in the product. Locked customer-specific programs) To be deleted Writing (can be scheduled to be Archivable periodic). only the URL is archived · Documents and condition records cannot be archived or deleted Technical Details for Archiving Overview of the Status When Archiving Archiving Status Archiving Steps Resulting Product Status Status of the Archiving Run in the Physical Archive Administration (ADK) Location of Data Archiving flag (either manually or via To archive Database Preprocessing (can be scheduled to Archivable Database be periodic). Locked Complete Archive file and database To be deleted Postprocessing (can be scheduled to Product status no longer visible in product maintenance as it be periodic). Field Catalog SAP_PRODUCT_MD Structure of an archive index that is maintained in the SAP Archiving Information System. you can define your own deletion checks for SAP Product. An archiving information structure always belongs to an archiving object. Page 53 of 56 . Structures for the Archiving Object of the SAP Product The following structures are used to define the archiving object: Structures PRODUCT_MD Archiving Object Defines the product archiving framework. However. A field catalog always belongs to an archiving information structure. Archiving information structure SAP_PRODUCT_AIS Defines the amount of all those fields that can be indexed that can used in field catalogs and thus in product archives. see the Customizing of the Cross-Application Components under SAP Products → Enhancements. PUBLIC © 2013 SAP AG or an SAP affiliate company. Using the method VERIFY_EXTRA_DATA. you can define your own usage checks for SAP Product. this is automatically integrated in archiving during generation. you do not use this BAdI to delete the data of customer-defined set types. you can include additional table structures for the SAP Product in the archiving.Archiving Function Program User Interface / Execution Type Use Archive administration preprocessing COM_PRODUCT_ SELECTIONS Transaction SARA Job Archive administration writing COM_PRODUCT_ARC_WRITE Transaction SARA Job Archive administration deletion COM_PRODUCT_ARC_CHECKBACK Transaction SARA Job Archive administration COM_PRODUCT_ARC_DELETE Transaction SARA Job Function BOR Method Implicit Use BOR Method Implicit Use BOR Method Implicit Use postprocessing Select product GUIDs to be archived COM_PRD_PRESELECT_FOR_ARCDEL Usage check Function COM_PRD_VERIFY_FOR_ARCDEL Delete products Function COM_PRD_DELETE_FOR_ARCDEL Display products from the archive Transaction COMM_PRDARC Customer-defined deletion checks Implementation of Business Add-In BAdI Method PRODUCT_ARCHIVE Implicit use: Calling point in program COM_PRODUCT_ARC_CHECKBACK Method VERIFY_EXTRA_DATA Customer-defined usage checks Implementation of Business Add-In BAdI Method Implicit use: Calling point in preprocessing program PRODUCT_ARCHIVE in function module Method CHECK_ARCHIVABLE COM_PRD_VERIFY_FOR_ARCDEL Customer-defined extension for Implementation of Business Add-In archiving additional data PRODUCT_ARCHIVE BAdI Method Implicit use: Calling point in program COM_PRODUCT_ARC_ WRITE Method ARCHIVE_EXTRA_DATA Customer-defined extension for Implementation of Business Add-In archiving additional data in structures PRODUCT_ARCHIVE BAdI Method Implicit use: Calling point in program COM_PRODUCT_ARC_ WRITE Method EXPAND_EXTRA_STRUCTURE Customer-defined extension for Implementation of the Business Add-In deleting additional data COM_PRODUCT_DELETE BAdI Method Implicit use: Calling point in program COM_PRODUCT_ARC_ DELETE Method DELETE_EXTRA_DATA Business Add-Ins for the Extension of Archiving The archiving of SAP Products can be extended using the following Business Add-Ins: Business Add-In Method / Use PRODUCT_ARCHIVE Using the method CHECK_ARCHIVABLE. Using the method EXPAND_EXTRA_STRUCTURE. you can write additional data per product to the archive file. For more information. see Archive Information System. Using the method ARCHIVE_EXTRA_DATA. COM_PRODUCT_DELETE Using the method DELETE_EXTRA_DATA. All rights reserved. you can define other data that is to be deleted when deleting a product and that does not directly belong to product master. For more information on Business Add-Ins. Adapt the Name and Path of the Archive File (Mandatory) Before you carry out archiving you must adapt the definition of the archive file to your system landscape. In the archiving administration (transaction SARA). Check in particular the settings for Logical File Names. Activating the Archiving Functionality Archiving must first be activated. Check the settings for Settings for Delete Program. In the screen Customizing for Cross. To adjust the definition of the archive file PRODUCT_MD. choose Basis Customizing → Cross-Client File Names/Paths 4. In the archiving administration (transaction SARA). 5. Check the system setting for Archive File Size. product IDs or products from a particular logical system). Page 54 of 56 . choose Application-Specific Customizing →Cross-Object Check/Delete. choose Save. 5. 2. Adapt the Runtime Settings for the Archiving Object PRODUCT_MD (Mandatory) Before you carry out archiving. 3. 2. In the archiving administration (transaction SARA). set types and multi-value attributes) are archived and deleted. PUBLIC © 2013 SAP AG or an SAP affiliate company. The archive files for the archiving object PRODUCT_MD are created with the logical file name ARCHIVE_DATA_FILE in the logical path ARCHIVE_GLOBAL_PATH. you need to carry out various steps for SAP Product: 1. Choose Customizing. select the archiving object PRODUCT_MD. choose Attributes. To save the attributes. carry out the following steps: 1. select the archiving object PRODUCT_MD. Check the system settings for Place File in Storage System.Archiving-Object Programs.Tables for the Archiving Object PRODUCT_MD The data archived and deleted in the archiving object PRODUCT_MD comes from the following fixed tables. carry out the following steps: 1. This data is determined dynamically in the archiving write program. Create Program Variants for the Program COM_PRODUCT_SELECTIONS (optional) We recommend that you create a variant (for example with the name PRODUCT_SEL) for the program COM_PRODUCT_SELECTIONS with which you can restrict archiving to certain products (various product types. To specify attributes for these variants. 4. see Defining Logical Paths and File Names. 2. 3. Enter data as required. To check the technical data of the archiving object PRODUCT_MD. For more information. select the archiving object PRODUCT_MD. since it is specified here where the data will be archived. In the screen Maintain Variant: Report COM_PRODUCT_SELECTIONS. Check the system settings for Logical File Names. To do so. Variant <Variant Name>. choose Archiving Object-Specific Customizing → Technical Settings 4. In the screen Data Archiving Customizing. 6. 3. enter a variant name and choose Create. 6. choose Save. In the screen Data Archiving Customizing. 2. choose Create Variant. 8. When you have adjusted the data. 7. To create a program variant. All of the table structures that are to be archived (such as customer-defined set types) are determined when the archiving write program is run: Tables Table Description COMM_PRODUCT Product header data COMM_PRODUCTH History of the product header data CRM_JCDO Change documents for the status object CRM_JCDS Change documents for the system /user status CRM_JEST Individual status per object STXB SAPscript texts: Texts not in SAPscript format STXH SAPscript texts: Header STXL SAPscript texts: Lines Additional data for the product (for example. enter data as required. you must check the runtime settings for the archiving object PRODUCT_MD and adapt them to your system requirements if necessary. 8. All rights reserved. carry out the following steps: 1. You can select these variants as variants for checking objects. In the screen Data Archiving Customizing. In the screen ABAP: Variants –Initial Screen. 7. Choose Customizing. Choose Customizing. 3. In the archive administration of the ADK (transaction SARA). 3. 5. 1. the system simultaneously sets the status Locked and Deleted. The objects are no longer displayed in product maintenance: 1. 4. You must enter an output device in the spool parameters. 2. Using this may result in objects unintentionally being archived and being deleted in the database. Choose Delete. 4. start date and the spool parameters. Enter the archive selection. Then choose Archive Infostructure → Activate. the system flags these as read. You must enter an output device in the spool parameters. We recommend that you do not execute the cross-object usage check using Check/Delete for SAP Product. Archiving 1. Choose Write. Enter the archiving object PRODUCT_MD. (transaction SARA). Start the deletion of data from the database using the archiving administration. (transaction SARA). 1. 3. 11. 2. Choose Execute. Activate Archiving Information Structure SAP_PRODUCT_AIS (Optional) The archive information structure SAP_PRODUCT_AIS is delivered inactive with a field catalog SAP_PRODUCT_MD. choose this variant in the field Active Variant. Choose Save. and deletes these objects from the database. 2. The information structure must be activated before the first archive read. Enter the archiving object PRODUCT_MD. 1. 5. Start the data-write to the archive using the archiving administration. Page 55 of 56 . 3. Choose Execute. All rights reserved. Locked and Deleted. the system sets the status of the archiving run to Incomplete. Choose Postprocessing. For objects that were successfully read in the archive. the system sets the product status is to Archivable. You can also create the index for archiving specifically for the PRODUCT_MD archive when archiving is complete. PUBLIC © 2013 SAP AG or an SAP affiliate company.9. To set a variant as active for archiving. 4. (transaction SARA). archived objects cannot be retrieved. 4. 3. Locked and Deleted is set. 3. 3. The information structure can (if active) be automatically updated during the archiving deletion run and is required for displaying archived products through the archive explorer of the SAP Archive Information System. the system sets the product status Archived. 2. carry out the following steps: 1. (transaction SARA). 10. Choose Execute. start date and the spool parameters. 2. 4. Writing Object Data to the Archive The write program writes the data of all objects that have the status Archivable to the archive files defined for the appropriate archiving object. as a general rule.Archiving-Object Check/Delete. Choose archiving administration. Normally there is the output device LP01 in the system (virtual printer). choose Save. Choose Preprocessing. 2. You must enter an output device in the spool parameters. Enter the archive selection. Normally there is the output device LP01 in the system (virtual printer). using the incorrect procedure could cause a loss of data. Normally there is the output device LP01 in the system (virtual printer). To avoid data inconsistencies when archiving a product. Choose Goto → Information System. Enter the start date and the spool parameters. To save the variants. Archiving-Object-Specific Usage Check The archive-object-specific usage check checks all products with the status To Be Archived. Enter the archiving object PRODUCT_MD. To avoid the archive files being read several times. To activate the archiving information structure. Enter the archiving object PRODUCT_MD. Start the archive-object-specific usage check using the archiving administration. Archiving-Object-Specific Postprocessing The archiving-object-specific postprocessing selects all SAP products for which the status Archived. Choose Customizing. If the checks confirm that a product can be archived. as this usage check includes all objects for which the status To Be Archived was set. 4. In the archive administration of the ADK (transaction SARA). 5. 5. Releasing Objects for Physical Deletion in the Database The delete program opens the archive files that the write program previously created and then reads them there. Since. In the field Archive Infostructure. in the screen Customizing for Cross. enter SAP_PRODUCT_AIS. the system sets the status of the archiving run to Complete. (transaction SARA). Start the postprocessing of the data using the archiving administration. f. Monitoring 1. enter PRODUCT_MD. Archive File Execute transaction SARA and choose Goto → Statistics to display the status of the archive files. (transaction SARI). Page 56 of 56 . In the field Archive Infostructure. a. choose Environment → Archived Products. To evaluate these logs. All of the data created for a product is visible in the technical view. b. d. All rights reserved. Choose Activate. use transaction SLG1 and enter subobject PRODUCT_MD. Usage Check During the usage check.5. e. select the desired archive. After activating archive information structure SAP_PRODUCT_AIS and creating the index. You can execute the creation of the index structure in the dialog or in the background. enter SAP_PRODUCT_AIS. Archive Information System Use the archive information system to display the archive files of SAP Product. In the field Archiving Object. To display archived products in product maintenance. c. d. Choose Customizing. Choose Status. you can display the archived products in product maintenance via Environment → Display Archived Products. The following prerequisites must be fulfilled to be able to display data in the archive information system: · Check if the archiving information structure SAP_PRODUCT_AIS has already been activated. 2. If the structure status is incomplete. the field catalog SAP_PRODUCT_MD and corresponding archive information structure SAP_PRODUCT_AIS are delivered in the archive information system. 4. b. Display Archived SAP Products in Product Maintenance There is a technical view in product maintenance for archived products that allows you to read all the archived data and drill-down reporting of SAP Products through the archive explorer of the archive information system. For the archiving object PRODUCT_MD. a. PUBLIC © 2013 SAP AG or an SAP affiliate company. You can activate the archive information structure either at the start of archiving or at a later date. Choose the archiving information system (transaction SARI). Choose Status per Archive. Archive Job Execute transaction SARA and choose Goto → Job Overview to see the status of the jobs generated in SARA for writing or deleting the archive 3. You have to activate the archive information structure just once so that the archive for the SAP Product can be read. products that could not be archived are logged in the application log. You are advised to also specify the date and time of the usage check. c. Choose the archiving information system. e. Check the system message. · Check if index structures were set up for the archive files. Choose Build Structures.