Date
Reviewed/Approved by
Contents
1 Creating Attributes and Set Types _________________________________________ 3
1.1 Implementing a check routine (optional) ________________________________________ 5
4 Custom-defined context nodes (optional)___________________________________ 6 5 Maintain Design Layer___________________________________________________ 6 6 Assigning the set type to the product header (optional) _______________________ 7 7 Assigning the set type to the different product applications ___________________ 7
7.1 7.2 8.1 8.2 8.2.1 8.2.2 8.3 8.4 8.5 8.6 8.7 Assigning the set type to a product application __________________________________ 7 Add the assignment block to the list of visible views ______________________________ 7 Add fields to search query structures via appends _______________________________ 9 Add fields to Design Layer (see also step 5) ____________________________________ 10 Determine the actual used design layer object __________________________________ 10 Maintain the design object __________________________________________________ 11 Add fields to configuration of search views ____________________________________ 11 Add a special search value help to the search field ______________________________ 11 Add fields to CRMC_PRSEA_ATTR ____________________________________________ 12 Add field to search result list _________________________________________________ 12 Add fields of search result list to design layer __________________________________ 13
8 Adding the set types attributes to the product search (optional) _______________ 9
Page 2 of 14
Multiple Use (Product:Set Type: 1:1 - Extensions,n:1 - 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 object. Set types with technical details are often also only valid for one product. Key Fields If at least one of the attributes of a set type is marked as a key field several entries can be made for each field of this set type when creating or changing product data. The attributes data of such set types 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.
Page 3 of 14
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 dependent or independent of distribution chains. This means that the values of all attributes for distribution-chain-dependent set types are specified for a specific combination of sales organization and distribution channel. Set types designated for multiple use - be it single-line or multiline - can be organization-dependent. On the other hand, set types not designated for multiple use, irrespective of whether they are singleline or multiline, are always organization-independent. Template-Enabled Templates allow you to predefine and therefore standardize data for set types. This data is referenced Copyright SAP AG 2010 Page 4 of 14
by the set types on the Product page. The templates themselves are defined in Customizing for CrossApplication 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.
3 UI configuration
3.1 Creating a customer enhancement
Unless not already done, create a customer enhancement set. An enhancement set is a Customer Relationship Management (CRM) concept to group several UI component enhancements together. It is a required logical bracket for more advanced enhancements. The actual client has to have an active enhancement set. For more information how to create a customer enhancement, please refer to external documentation: http://help.sap.com/saphelp_crm70/helpdata/en/51/dfdf460f464db1b483d9c2a1bcd488/frameset.htm
Page 5 of 14
Set Type Kind Single Line Set Types Single Line Set Types with Multi Value Attributes
View PRDGENSET/SLSeteOV PRDGENSET/SLMVSeteOVVS PRDGENSET/SLSeteOV PRDGENSET/SLMVAttreOV PRDGENSET/MLSeteOV PRDGENSET/SLSetEF PRDGENSET/SLDCSetEF PRDGENSET/SLMVDCSetELVS PRDGENSET/SLMVDCAttrEL PRDGENSET/SLSetEF PRDGENSET/MLDCSetEL
Multi Line Set Types Single Line Set Types (Distribution Chain Dependent) Single Line Set Types with Multi Value Attributes (Distribution Chain Dependent) Multi Line Set Types (Distribution Chain Dependent)
The sub object type of the generated configuration will correspond to your set type ID.
Page 6 of 14
Product Type 01 01 01 01 02 02 03 03 04 04 05 07 07
Application Product Competitor Product Object Distribution Chain View Service Distribution Chain View Financing Distribution Chain View IP Distribution Chain View Warranty Financial Service Distribution Chain View
Component PRD01OV PRDCPOV PRDIOOV PRDDC PRD02OV PRDDC PRD07OV PRDDC PRD04OV PRDDC PRD05OV PRD07OV PRDDC
Overview Page PRD01OV/MaterialOV PRDCPOV/CompetitorProductOV PRDIOOV/ObjectOV PRDDC/DCOV PRD02OV/ServiceOV PRDDC/DCOV PRD07OV/FSProdOV PRDDC/DCOV PRD04OV/IPProdOV PRDDC/DCOV PRD05OV/WarrantyOV PRD07OV/FSProdOV PRDDC/DCOV
set type in the list of available assignment blocks. Switch to edit mode and move the entry to the list of displayed assignment blocks. Please provide an appropriate description for the assignment block and save the configuration.
Page 8 of 14
Extend the search attribute structure of the corresponding search with a new field (data type of your attribute. Proceed with the following steps:
Advanced Search for Competitor Products Advanced Search for Products for Enterprise Search Advanced Search for Individual Objects Advanced Search for Products Advanced Search for Products with Territories Advanced Searches for Products/Warranties
Please also refer to notes 1026956 and 1430798 for more specific information on this topic.
Page 9 of 14
Page 10 of 14
8.2.2
Use the transaction BSP_DLC_SDESIGN_DISP and the UI object type/design object from the previous stept. Copy the corresponding design object and modify it.
Page 11 of 14
Page 12 of 14
Page 13 of 14
Page 14 of 14