Skip to end of metadata
Go to start of metadata

The Product Master Data Management ES bundle makes it easier to access and manage product data in SAP Customer Relationship Management (SAP CRM) from an external application. It allows customers in practically all industries to integrate SAP CRM with third-party master data management solutions and to access the product information in SAP CRM from an external application.

SAP CRM supports several different product types: Material, Individual Material, Service Product, and Warranty. This ES bundle service-enables these product types and allows product managers and product administrators to manage product master data in SAP CRM using a master data management solution or external application. It also allows applications such as internet stores to access information about products that is stored in CRM.

The Product Master Data Management ES bundle leverages enterprise SOA through communications between SAP CRM and third-party master data management systems using enterprise services and by service-enabling product data in SAP CRM.

Audience

The Product Master Data Management ES bundle is applicable to all industries. The persons most likely to use the services in this bundle are IT and business analysts whoare interested in using enterprise SOA to manage product information.

Product Master Data Management (click to enlarge)


For details on Service Operations, Business Objects and Process Components, please check the ES Workplace.


How To Use This ES Bundle

Prior to this ES bundle, industries had to build custom integration between systems that contain product data. With SAP CRM, there is now no need for this custom integration because the enterprise services in this ES bundle can be used to handle the integration. This helps streamline the master data management process for industries, helping to speed things up and to cut costs.

This section will explore a series of use cases for the Product Master Data Management ES bundle. Each use case will show how different outcomes can be achieved by using the enterprise services in different combinations. While these examples illustrate a few of the ways that this ES bundle could be used, the intention is to show the flexibility and re-usability of these business objects and enterprise service operations so that you will have a clearer understanding of how to best deploy them in your own environment. This wiki is also a space for you to share knowledge and collaborate with others who are implementing the Product Master Data Management ES bundle.

Use Case 1: Integrate SAP CRM with external product master data systems

A product manager creates a new product in an external product master data management system; in this use case, the external product master data management system is the leading system for product data. That product is then replicated to SAP CRM using the Create Material enterprise service operation, which uses the Material business object. SAP CRM then sends back a confirmation message by invoking Confirm Material*, which also uses the Material business object.

Note: This use case describes propagating creation and changes to two product types, Material and Service Product, from the product master data management system to SAP CRM. It can be applied to any of the product types offered in this ES bundle.

Later, the product manager comes back and changes some details about the product. These changes are also propagated to SAP CRM, this time via the Change Material enterprise service operation. Again, SAP CRM sends a confirmation message back using the Confirm Material enterprise service operation.

The following table summarizes these steps and the associated enterprise services:

Step

Enterprise Service Invoked

Step 1: A new product is created in the product master data management system. The product master data management system triggers creation of a Material in SAP CRM.

Create Material

Step 2: SAP CRM confirms that the product was created

Confirm Material

Step 3: A product is changed in the product master data management system. The product master data management system triggers a corresponding change to the Material in SAP CRM.

Change Material

Step 4: SAP CRM confirms that the product was changed

Confirm Material

Creating Products in Bulk

Now the product manager wants to create an entirely new product line, as opposed to a single product, so it makes sense to create many products at once using bulk services. For the sake of an example, let's say that the new product line is for a group of industrial dishwashers.

The first step the product manager would take is to trigger the creation of multiple new products in the external product master data system. Those products are then replicated to SAP CRM using the Create Material as Bulk enterprise service operation, which uses the *Material business object. SAP CRM then sends back a confirmation message by invoking the Confirm Material as Bulk service, which uses the also uses the Material business object.

The following table summarizes these steps and the associated enterprise services:

Step

Enterprise Service Invoked

Step 1: A new product line is created in the product master data management system. The product master data management system triggers creation of all the Materials in that product line in SAP CRM.

Create Material as Bulk

Step 2: SAP CRM confirms that it created all the products in that product line.

Confirm Material as Bulk

Creating a Service Product

Now the product manager needs to create a new Service Product that will cover installation for the dishwasher line he just created. In these next steps, he will create one Service Product, Installation, that can be used to install all the models of dishwashers in this line. (If desired, a bulk service could be used to create a separate installation service product for each product created earlier.)

The first step the product manager would take is to trigger the creation of the new Service Product (Installation) in the external product master data system. That Service Product is then replicated to SAP CRM using the Create Service Product enterprise service operation. SAP CRM then sends a confirmation message by invoking the Confirm Service Product enterprise service.

The following table summarizes these steps and the associated enterprise services:

Step

Enterprise Service Invoked

Step 1: A Service Product is created in the product master data management system. The product master data management in turn triggers creation of the Service Product in SAP CRM.

Create Service Product

Step 2: SAP CRM sends back confirmation that the Service Product was created.

Confirm Service Product

Use Case 2: Maintain CRM Product Data from Custom UI or Composite Application

In this use case, unlike Use Case 1, SAP CRM acts as the leading system for product data. Let's say that the product manager in this case works for a company that buys products. With this use case, he is able to find and read information about a product, view a document attached to a product, such as a product manual, and create and modify products. As in Use Case 1, we will use the example of an industrial dishwasher.

In the first step, the product manager uses the custom UI or composite application to find basic data about the dishwasher. This triggers the Find Material Basic Data by Elements enterprise service in SAP CRM. The search returns a list of results and the product manager selects an item from that list, which invokes the Read Material Basic Data service operation, which also uses the Material business object.

Now the product manager decides he wants to view additional data about the dishwasher. Selecting an option in the composite application for further product details invokes the Read Material service operation.

Now the product manager wants to view the product manual for the dishwasher. Using the composite application, clicking on the link for the product manual invokes the Read Material Attachment Folder service operation.

The product manager needs to add a Service Product for the dishwasher in SAP CRM. He selects an option to do so in his UI, which triggers the Create Service Product enterprise service, which uses the Service Product business object. Now that this specific Service Product is created, the product manager realizes he needs to add information to the new Service Product he has created. He does this by triggering the Change Service Product enterprise service, which uses the Service Product business object.

The following table summarizes these steps and the associated enterprise services:

Step

Enterprise Service Invoked

Step 1: User wants to find a Material

Find Material Basic Data by Elements

Step 2: Users want to view basic data for a Material

Read Material Basic Data

Step 3: User wants to view complete data for a Material

Read Material

Step 4: User wants to view a document attached to a Material (such as a product manual)

Read Material Attachment Folder

Step 5: User wants to create a Service Product

Create Service Product

Step 6: User wants to modify a Service Product

Change Service Product

Use Case 3: A Web Store User Finds and Reads Information about a Product

Use case 3 involves a scenario where a custom-developed web store displays product master data stored in SAP CRM. Web store users select products to create Internet orders that are then processed using SAP CRM or SAP ERP systems. With SAP CRM, customers no longer need to replicate all product master data from SAP CRM to their custom-developed web stores.

Let's say a user on a custom developed web store wants to look up information about a laptop computer. On the Web store home page, she would type in the name of the laptop brand or other search criteria to find laptops with features that interest her. When she does this, the Find Material Basic Data by Elements service is invoked behind the scenes in SAP CRM to return a list of matching laptop models. The service uses the Material business object.

Next, the user wants to simply review the basic data for a laptop she likes. This invokes the Read Material Basic Data service operation, which also uses the Material business object.

The user then decides that she wants to read the complete data available on the particular laptop, such as all of the technical specifications. This invokes the Read Material service operation, which uses the Material business object.

The final step happens when the user notices that there is a file attached to the product information. Let's say this file is a video that describes the laptop. When she clicks on the attachment, this triggers the Read Material Attachment Folder service operation, which also uses the Material business object.

The following table summarizes these steps and the associated enterprise services:

Step

Enterprise Service Invoked

Step 1: User looks up a Material in a web store

Find Material Basic Data by Elements

Step 2: User wants to view basic data for the Material she finds in Step 1.

Read Material Basic Data

Step 3: User wants to view complete data for this Material

Read Material

Step 4: User wants to view a document attached to this Material (such as a product diagram or video)

Read Material Attachment Folder


Use Case 4: Create, update and find SAP CRM objects from an external application - by Novell

A user creates an object in an external application. The user replicates that object to SAP CRM using the Create Individual Material enterprise service operation.
Later, the user comes back and changes some details about the object. The user initiates a propagation of these changes to the SAP CRM.  This time the Change Individual Material enterprise service operation is invoked.
Later, the user has determined that he/she needs to read the material information from SAP CRM. The user initiates a retrieve of the object in the external application. This time, the Read Individual Material enterprise service operation is invoked.

Finally, the user is interested in finding and viewing similar objects in the SAP CRM.  The user initiates a search against the SAP CRM system and the results are displayed in the external application.  This time, the Find Individual Material Basic Data by Elements enterprise service operation is invoked.
The following table summarizes these steps and the associated enterprise services:               

Step

Enterprise Service Invoked

Step 1: An object is created in the external application. The user initiates the creation of the object in the SAP CRM system.

Create Individual Material

Step 2: The object is updated in the external application. The user initiates a propagation of these changes to the SAP CRM system.

Change Individual Material

Step 3: The object can be retrieved from SAP CRM. The user initiates a retrieve of the object from the external application to read material information.

Read Individual Material

Step 4: The user initiates a search against the SAP CRM system to find similar objects.

Find Individual Material Basic Data by Elements

  

Using the Services in This ES Bundle with SAP Applications

Used This Bundle with SAP Apps?

If you've had experience integrating this bundle with SAP applications, please edit this page and share your experiences.

Certified Partner Applications implementing this ES Bundle

Certified Partner Applications for Product Master Data Management


 

Partner Company

Novell

Name and Version of the Certified Product

Novell CMDB360 4.6

Validity of the certification

Oct.8th, 2012

Brief Description of the Certified Product

Novell CMDB360 4.6 combines Web 2.0 and social networking principles into
a simple community-based environment where users can more easily
interact with CMDB data---and other CMDB users as well. Using
Facebook™ like interactivity along with a Google™ like context-based
search mechanism, Novell CMDB360 4.6 transforms the CMDB into a more
valuable, user-friendly environment.

Implemented Use case(s)

Use Case 4 Create, update and find SAP CRM objects from
an external application - by Novell


Certified Partner Applications for Product Master Data Management

Partner Company

Novell, Inc.

Name and Version of the Certified Product

Novell CMDB360 4.6

Validity of the certification

October 8, 2012

Brief Description of the Certified Product

CMDB360 combines Web 2.0 and social networking principles into a simple community-based environment where users can more easily interact with CMDB data---and other CMDB users as well.

Implemented Use case(s)

Use Case 4: Create, update and find SAP CRM objects from an external application - by Novell

Future Directions

Some possible future directions for this bundle could include adding a new product type for intellectual property, adding product configuration rules, and adding data elements for specialized scenarios.

System Requirements

Related ES Bundles

  • Interactive Selling
  • Sales Incentive and Commission Management
  • Lead Management

SOA Homepage on SDN
CRM BPX Community