Entering content frame!--a11y-->

Component documentation Master Data Templates in SAP IS-U 


Master data templates (MDTs) and the master data generator (MDG) are tools used in SAP IS-U to automatically create master data.

Business processes necessitate the creation of new utility services or changes to existing ones. Examples are:

·  Registration of a new customer with a service provider

·  Rate change that affects an existing customer

These utility services require you to create new data for objects from the data model or change existing data.

You can handle these business processes using IS-U transactions. These enable you to enter data in all the fields of the affected objects individually. This is often a lengthy and complex task.

You can accelerate this process by using a template application that allocates fixed values to fields in a given object. This restricts the number of fields that can be individually maintained. The system determines the fixed values from the context or type of utility service.

Examples of possible applications are:

·  Sales processes in Sales and Distribution (SD) or CRM

·  Internet Self Service functions

·  Exchange of data between a service provider and a distributor during a supplier change

·  Import of utility contracts concluded by a sales partner

This restricted view is supported by MDTs. If you want to use MDTs, you must execute the following steps:


  1.  Choose an autonomous standard SAP MDT category (MDT category) that matches the current business process. The MDT category determines what objects the system creates or changes.

  2.  Create an MDT for the MDT category. In the definition of the MDT, specify which fields are assigned a fixed value by the system and which fields you maintain yourself.

  3.  Integrate the MDG into your application. When the MDG is called, you transfer the individually entered values. The MDG adds the fixed values from the definition of the MDT to your values. It then uses all the values to maintain the corresponding objects of the IS-U data model.

When you execute a MDT, the system does not enter a master data key in the business partner object. Rather, the MDT and MDG enable you to make wide-ranging changes to objects from the IS-U data model with a minimum of data entry.  You can also use MDTs for initial data creation.


You want to run an application to change a customer’s rate. To do this, proceed as follows:


  1.  Choose a suitable MDT category- in this case RATECHANGE. This MDT category is used to change data in the utility installation.

  2.  Create an MDT with this MDT category. In the definition of the MDT category, specify that the rate category of the utility installation is a fixed value. This means that all the installations to which this product is allocated receive this rate category. The system defines the changed date as a value that you maintain yourself.

  3.  From your application, call the MDG (ISU_PRODUCT_IMPLEMENT function module). Transfer both the key of the MDT and the values you entered to this function module. The function module then changes the utility installation in background.

The MDG is integrated in several IS-U applications, for example IS‑U Sales Processing. You can find further information in the documentation for SAP for Utilities in the Help Portal, under http://help.sap.com ® SAP Industry Solutions ® SAP for Utilities ®Customer Service ® IS-U Sales Processing.
As of Release 4.63, the MDG is used in the IS-U/CRM integration solution.
For more information see the Help Portal, under http://help.sap.com ® SAP Cross-Industry Solutions ® SAP Customer Relationship Mgmt ® SAP CRM 4.0 ® Industry-Specific CRM ® Service Industries ® Utilities ® Sales Processing for Residential Customers ® IS-U/CRM Integration: Sales Process for Residential Customers ® Enhancements to the MDG for IS-U/CRM integration. This integration solution uses special MDT categories that are not described here.


To use IS-U sales processing you only need to create MDTs. The system calls the MDG automatically. If you are using applications that do not contain the MDG by default, you must integrate the ISU_PRODUCT_IMPLEMENT (process MDT) function module. This is very quick and simple to do. Use the ISU_MDATA_TEMPLATE_TEST (execute MDT) report for reference. The maintenance transaction for MDTs uses this report for testing purposes.


The graphic below shows you how to use the MDG in one of your own applications.

This graphic is explained in the accompanying text



·  The application calls the ISU_PRODUCT_IMPLEMENT function module. It transfers the key of the MDT and a list of values (name, address and so on) to the function module. These are used as the parameters of the MDT.

·  From the MDT and MDT category, the MDG infers the following:

o  Information on the IS-U master data to be changed/created.

o  Constant values with which the master data must be created.

o  Programs (scripts) for changing the master data.

If an error should occur, the master data generator terminates the template processing, and generates a workflow. The following documentation does not go into further details regarding the scenarios that use the master data generator. Instead, it describes the technical details of the MDT categories. This description should answer the following questions:

·  How do MDT categories and MDTs interact?

·  What master data can you create and change using the MDG?

·  What do I need to bear in mind when creating MDTs?




Leaving content frame