CRM and CX Blogs by Members
Find insights on SAP customer relationship management and customer experience products in blog posts from community members. Post your own perspective today!
cancel
Showing results for 
Search instead for 
Did you mean: 
Former Member

Data related to a Product (Material, Individual Object, Service, IP, warranty), in CRM Product Master Data can exist either in product Reltypes or in product Settypes. Reltypes are nothing but product relations. It is also known as Product Interlinkages.

Settype or a reltype, will be visible in CRM Web UI, as a separate assignment block.

Product Interlinkages (Reltypes):

Product Interlinkages(Reltypes) can be of 2 different types:

  • Product to Product relation

          Example:

               Accessories of a product

               Warranty associated to a product

               Components of structured product

               Service parts of material etc.

  • Product to BP relation

           Example:

               Competitors of a product

               Suppliers of a product

               Involved Parties of an individual object (say Owner of the vehicle, Contact Person of an Individual Object etc)

More reltypes which are delivered in standard, can be found using table COMC_IL_TYPE and COMC_IL_TYPE_T, with Source = BUS1178 (Product) and Destination = BUS1178 (Product) or BUS1006 (Business Partner).Users can also create their own reltype, between Product to Product or Product to BP, using EEWB (Easy Enhancement Workbench).

SAP Note: 1139562  can be referred here to integrate Z* reltype in Web UI

SAP Note: 1418914  explains AET (Application Enhancement Tool) VS EEWB.

SAP Note: 1874824  Usage of EEWB in Product Master Data

Reltype table is COMM_IL_<reltype-id> for SAP delivered reltypes and ZOMM_IL_<reltype-id>, for customer specific reltypes.

Product Settypes:

Product settypes are nothing but group of related product attributes.

Examples for settypes include Unit of Measure (COMM_PR_UNIT), Product Tax (CRMM_PR_TAX), Sales area data (CRMM_PR_SALESA) etc.

Settype CRMM_PR_TAX, groups together tax related attributes like tax country, tax region, tax type, tax group, tax tariff code etc.

Settype COMM_PR_UNIT, groups together Unit of Measure related attributes like Base Unit, Alternate Unit, Numerator, Denominator, Gross Weight, Net Weight etc.

Table COMC_SETTYPE can be referred, to know more about settypes which are delivered in standard.

It is also possible to create our own product attributes and group them together in a new settype, using Transaction COMM_ATTRSET.

Below are the steps involved from settype creation to their availability in CRM Web UI:

StepDescriptionComments
1

Definition of Attributes and Set Types

Transaction COMM_ATTRSET
2

Assignment of the Settypes to the Category

Transaction COMM_HIERARCHY
3

Settype assignment to respective Overview Page

Transaction CRMM_UIU_PROD_GEN
4

Configure Settype as visible Assignment Block in the OVP

Using Configuration Tool in BSP workbench
5a

UI Configuration Creation of the Settype

Transaction CRMM_UIU_PROD_CONFIG
5b

UI Configuration Adaption of the Set Type

Optional (changing field label, field properties etc using configuration tool)
6

Assignment of the Category to the Product

Applications Products, Services, Warranties, Objects, Competitor Products, ...during creation process

Below are the respective Overview Pages for the respective applications:

ApplicationOVP
ProductsPRD01OV/MaterialOV
ServicesPRD02OV/ServiceOV
WarrantiesPRD05OV/WarrantyOV
ObjectsPRDIOOV/ObjectOV
Competitor ProductsPRDCPOV/CompetitorProductOV

Optionally, implementing data check routines for attributes of the set type can be done using BAdI PRODUCT_SET.

SAP Note: 1533208 How-to-guide for creating set types in SAP CRM,  can be referred here.

SAP Note: 1508557 Extensibility VS settype enhancement

Adding custom settype attributes into product search is also possible. SAP Note: 1026956 and 1430798 can be referred here.

Different kinds of settypes and their appearance in CRM Web UI:

For demonstration purpose, I have created 2 attributes 'Product Model Number', 'Date of Manufacture' without checking the checkbox 'Multiple Values Pos.' and attribute named 'Instructions' with checking the checkbox 'Multiple Values Pos.' during attribute creation.

In below scenarios, I have used attribute 'Instructions' within settypes as single value attribute field and multivalue attribute field. And for demonstration purpose, I have used PRD01OV as my overview page component.

1) Single line settype (without any multivalue(MV) attributes)

      Settype configuration is present in PRDGENSET/SLSeteOV, with Object Subtype = <Settype-ID>.

      

2) Single line settype which is Org Dependent (without any MV attributes)

     Settype configuration is present in PRDGENSET/SLDCSetEF, with Object Subtype = <Settype-ID>

   

      For Org Dependant settypes, Overview page: PRDDC/DCOV.

      

3) Single line settype with MV attribute

To use an attribute as a multivalue attribute, it is required to tick checkbox 'Multiple Values Pos.', during attribute creation using transaction COMM_ATTRSET. And this attribute can be used as again single value or multivalue attribute within a settype, during settype creation using transaction COMM_ATTRSET,tab 'Assinged Attributes', using check box 'Multiple Values'. Please note that, this check box is available only for attributes for which checkbox 'Multiple Values Pos.' is ticked, during attribute creation.

Do not get confused with check box 'Multiple Use' avaibale during settype creation, using transaction COMM_ATTRSET. This indicator is ticked, when this settype can be used by more than one products say general characteristics like Unit of Measure which can be re-used across several products and when unchecked, it means that settype is bound to single product, say serial number.

Settype configuration is present in PRDGENSET/SLMVAttreOV(for MV attribute) and PRDGENSET/SLSeteOV ( for non-MV attributes) , with   Object Subtype = <Settype-ID>.

     

4) Single line settype with MV attribute which is Org Dependent

Settype configuration is present in PRDGENSET/SLMVDCAttrEL (for MV atttribute) and PRDGENSET/SLDCSetEF( for non-MV attributes), , with Object Subtype = <Settype-ID>.

For Org Dependant settypes, Overview page: PRDDC/DCOV.

     

5) Multi line settype

Settype configuration is present in PRDGENSET/MLSeteOV, with Object Subtype = <Settype-ID>.

    

To qualify for multiline settype, 'Field is Key' should be ticked under 'Assigned Attributes' tab during settype creation in transaction: COMM_ATTRSET, for relevant attributes.

    

6) Multi line settype which is Org Dependent

    Settype configuration is present in PRDGENSET/MLDCSetEL, with Object Subtype = <Settype-ID>.

     For Org Dependant settypes, Overview page: PRDDC/DCOV.

Common mistakes performed due to which assignment block for the settype goes missing in Web UI:

  • Make sure that in Transaction CRMM_UIU_PROD_GEN, you provide the correct Enhancement Set for that client. This can be checked in table  BSPWD_EHSET_ASGN. Also, make sure to provide the right Overview Page Component.
  • Also, make sure that you add the settype AB from Displayed to Available AB, using Configuration Tool, for the correct configuration of that OVP.

        Hope you find this blog useful :smile:

44 Comments