Cookbook IS-U Master Data Templates - SAP
Stammdatenvorlagen zu Release 4.64CookbookIS-U Master Data Templates
Cookbook Master Data TemplatesSAP AG Copyright 2003 SAP AG. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose withoutthe express permission of SAP AG. The information contained herein may be changed without priornotice.Some software products marketed by SAP AG and its distributors contain proprietary softwarecomponents of other software vendors.Microsoft , WINDOWS , NT , EXCEL , Word , PowerPoint and SQL Server are registeredtrademarks of Microsoft Corporation.IBM , DB2 , DB2 Universal Database, OS/2 , Parallel Sysplex , MVS/ESA, AIX , S/390 , AS/400 ,OS/390 , OS/400 , iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere ,Netfinity , Tivoli , Informix and Informix Dynamic ServerTM are trademarks of IBM Corporation in USAand/or other countries.ORACLE is a registered trademark of ORACLE Corporation.UNIX , X/Open , OSF/1 , and Motif are registered trademarks of the Open Group.Citrix , the Citrix logo, ICA , Program Neighborhood , MetaFrame , WinFrame , VideoFrame ,MultiWin and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C , World Wide WebConsortium, Massachusetts Institute of Technology.JAVA is a registered trademark of Sun Microsystems, Inc.JAVASCRIPT is a registered trademark of Sun Microsystems, Inc., used under license for technologyinvented and implemented by Netscape.MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com, and other SAP products and services mentionedherein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world. All other product and service namesmentioned are the trademarks of their respective companies.-2-
SAP AGCookbook Master Data TemplatesIconsIconMeaningCautionExampleNote-3-
Cookbook Master Data TemplatesSAP AGMaster Data Templates CookbookContentsIcons .31 Master Data Templates.61.1 Overview.61.2 What Are Master Data Template Categories?.91.2.1 MDTs and MDT Categories . 91.2.2 MDT Category Hierarchy. 91.2.3 Cardinality . 101.2.4 Autonomous MDT Categories. 111.2.5 Create or Change. 111.2.6 Virtual Attributes . 121.2.7 User-Defined Fields . 131.3 Environment Determination.13ISU ENVIRONMENT PREMISE. 14General Information. 14Environment for Technical Master Data. 14Identifying Constants . 141.4 Master Data Templates .151.4.1 Example. 151.4.2 Create and Test Master Data Templates. 171.4 3 Notes on the Parameters . 191.5 Master Data Generator. 211.5.1 Customer Contact. 211.5.2 Key for New Master Data. 221.6 Error Handling in the Master Data Generator .221.7 Description of Master Data Template Categories .221.7.1 NEWCUSTPOD . 221.7.2 NEWCUST . 231.7.3 RATECHANGE . 231.7.4 BPARTNER and CONTRACT ACCOUNT. 24- BP PAYMENT . 26- BP CCARD . 26- BP TAXNUM. 26- BP IND SECTOR . 26- BP COPY PREM ADDR . 26- BP ADDRESS . 27- BP PHONE. 27- BP FAX . 28- BP EMAIL . 281.7.4.1 CONTRACT ACCOUNT. 281.7.5 DEVICE INFO and REGISTER INFO. 28-4-
SAP AGCookbook Master Data Templates- DEVICE INFO as of Release 4.64 . 29- DEVICE INFO until IS-U Release 4.63. 331.7.5.1 REGISTER INFO as of IS-U-Release 4.64. 331.7.6 QPRICE. 361.7.7. QPRICE HIST . 36Meaning of the Quantity Base . 40QPRICE . 41CRM Prices . 41LPRICE . 41TPRICE . 411.7.7 CONNOBJ. 421.7.8 DEVICE LOCATION. 421.7.9.1 DEVICE TECH INSTALL and REG TECH INSTALL. 421.7.9.2 SERV FREQ SERV LOC. 431.7.10 POD STAND ALONE . 451.7.11 PREMISE . 451.7.11.1 MOVE IN . 46- MOVE IN BBP. 47- MOVE IN MR. 48- MOVE IN SEC. 491.7.11.2 INSTALLATION. 51- INSTALLATION HISTORY. 51Normal Installation Facts . 51Reference Values . 58- LPROF INST ASSIGN and LPROF INST FACTOR. 59DEVICE BILL INSTALL and REG BILL INSTALL . 61- LPROF REG ASSIGN. 64- POINT OF DELIVERY. 65- CONTRACT . 65- BCONTACT . 662 Master Data Templates in Release 4.64.672 Master Data Templates in Release 4.63.673 Master Data Templates in Release 4.62.684 Master Data Templates in Release 4.61.69Master Data Template Categories . 69Test Master Data Templates. 69-5-
Cookbook Master Data TemplatesSAP AG1 Master Data Templates1.1 OverviewMaster data templates (MDTs) and the master data generator (MDG) are tools used in IS-U toautomatically 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 providerRate change that affects an existing customerThese utility services require you to create new data for objects from the data model orchange existing data.You can handle these business processes using IS-U transactions. These enable you to enterdata in all the fields of the affected objects individually. This is often a lengthy and complextask.You can accelerate this process by using a template application that allocates fixed values tofields 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 CRMInternet Self Service functionsExchange of data between a service provider and distributor during asupplier changeImport of utility contracts concluded by a sales partnerThis restricted view is supported by MDTs. If you want to use MDTs, you must execute thefollowing steps:Choose an autonomous standard SAP MDT category (MDT category)that matches the current business process. The MDT categorydetermines what objects the system creates or changes.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 whichfields you maintain yourself.Integrate the MDG into your application. When the MDG is called, youtransfer the individually entered values. The MDG adds the fixed valuesfrom the definition of the MDT to your values. It then uses all thevalues 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 partnerobject. Rather, the MDT and MDG enable you to make wide-ranging changes to objects fromthe IS-U data model with a minimum of data entry. You can also use MDTs for initial datacreation.-6-
SAP AGCookbook Master Data TemplatesExampleYou want to run an application to change a customer’s rate. To do this, proceed asfollows:1.Choose a suitable MDT category- in this case RATECHANGE. This MDTcategory is used to change data in the utility installation.2.Create an MDT with this MDT category. In the definition of the MDTcategory, 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 thisrate category. The system defines the changed date as a value that you maintainyourself.3.From your application, call the MDG (ISU PRODUCT IMPLEMENT functionmodule). Transfer both the key of the MDT and the values you entered to thisfunction module. The function module then changes the utility installation inbackground.The MDG is integrated in several IS-U applications, for example IS-U sales processing. Youcan find further information in the documentation for SAP for Utilities in the Help Portal,under http://help.sap.com SAP Industry SolutionsSAP for Utilities CustomerService IS-U Sales Processing. As of Release 4.63, the MDG is used in the IS-U/CRMintegration solution. For more information see the Help Portal, under http://help.sap.comSAP Cross-Industry Solutions SAP Customer Relationship MgmtSAP CRM 4.0Industry-Specific CRMService Industries Utilities Sales Processing for ResidentialCustomers IS-U/CRM Integration: Sales Process for Residential CustomersEnhancements to the MDG for IS-U/CRM integration. This integration solution uses specialMDT categories that are not described in this cookbook.To use IS-U sales processing you only need to create MDTs. The system calls the MDGautomatically. If you are using applications that do not contain the MDG by default, you mustintegrate the ISU PRODUCT IMPLEMENT (process MDT) function module. This is veryquick and simple to do. Use the ISU MDATA TEMPLATE TEST (execute MDT) report forreference. The maintenance transaction for MDTs uses this report for testing purposes.-7-
Cookbook Master Data TemplatesSAP AGThe graphic below shows you how to use the MDG in one of your own applications.The IS-U Master Data GeneratorMasterdatatemplateMasterdatatemp. cat.Master datageneratorScriptsExecutingprogramTemplate IDObjectMethodsParameterIS-UmasterdataWorkflowSAP AG 2000 filename (author) / 1Figure 1: Operation of the IS-U Master Data GeneratorNotes:The application calls the ISU PRODUCT IMPLEMENT functionmodule. 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 theparameters 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.The scripts use OO methods to create and change IS-U master data.If an error occurs, the MDG cancels processing of the template and generates a workflow. Theinformation below does not describe any scenarios involving the MDG. Instead, it describesthe technical details of the MDT categories. It answers 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?-8-
SAP AGCookbook Master Data Templates1.2 What Are Master Data Template Categories?1.2.1 MDTs and MDT CategoriesMDT categories determine the structure of MDTs. The MDT enables you to create andchange IS-U master data using the MDG.Each MDT (hereafter called templates) is allocated to a MDT category (hereafter calledtemplate categories). The template category defines the following aspects of a template:What master data the template can create (for example businesspartner, utility installation and so on)What attributes (master data fields) can be maintained in the template(for example division or billing class of the utility installation and soon)In what order the MDTs are created (for example connection objectfirst, followed by premise and so on)What programs are processedWhat foreign key dependencies exist between individual items ofmaster data, for example whether the premise adopts the key of thepreviously created connection object.In contrast, the user maintains the following information in the template itself:The values with which the master data is created. Amongst otherthings, constants and parameters are differentiated here.Whether to use the optional elements of the template (for examplewhether to create a connection object with or without a devicelocation)What parts of the template can be used more than once (for examplewhether business partners can be created with one or two addresses)SAP supplies predefined MDT categories. They are stored in the EPDTYPE viewcluster (ISU MDG: MDT category)1.2.2 MDT Category HierarchyTemplate categories generally consist of several nodes. A node corresponds to a master dataobject, such as a premise, or to the characteristics of an object, such as the address of thebusiness partner.A hierarchy shows how the template category is divided into several nodes.NoteAs of Release 4.63, you can use transaction EPDHIER to display the hierarchyof a template category. As of Release 4.64 this display function is integrated inthe master data maintenance transaction.You can find this transaction in the IMG under SAP UtilitiesCustomer ServiceMDGDefine MDT. On the initial screen enter the required MDT category and chooseDisplayHierarchy.-9-
Cookbook Master Data TemplatesSAP AGFigure 2: Hierarchy of the BPARTNER (business partner) template categoryThe above template category contains the sub-node BP PAYMENT (business partner bankdetails). The sub-nodes are indented, indicating the different hierarchy levels. The definitionof the template category specifies that this node is optional. This means that when you createa template with this category, you can deactivate the node BP PAYMENT. . If you do this,all the fields in the business partner relating to bank details remain empty. You can alsoreplicate the node. You now have two of each bank details field to maintain. The systemcreates the business partner with two sets of bank details.The BPARTNER template category also has the BP ADDRESS sub-node (business partneraddress). BP ADDRESS, in turn, has its own sub-nodes. Their position in the node hierarchyis indicated by a further indentation. If you activate BP ADDRESS in the template then thesub-nodes of BP ADDRESS are also activated. If you replicate BP ADDRESS then the subnodes, such as BP PHONE, are also replicated. The maintenance transaction for templatecategories displays the hierarchy by means of indentation, as explained above. The transactionalso displays whether a node is active or inactive. You must make clear the templatecategories control these properties during maintenance.1.2.3 CardinalityThe cardinality of a MDT category determines whether the nodes in the template category canbe activated and deactivated. The cardinality of a template category can have one of thefollowing values:0-1: The template category does not contain the node/the templatecategory contains the node once. It can be deactivated but not replicated.-10-
SAP AGCookbook Master Data Templates0-n: The template category does not contain the node/the node can bereplicated any number of times. You can deactivate and replicate the node.1:The template category can contain the node once only. The nodeis always active.1-n: The template category can contain the node once, or replicatedany number of times. The node(s) can be replicated but not deactivated.ExampleIn the BPARTNER template category, the BP PAYMENT sub-node hascardinality 0-n. This means you can create a template with this category thathas a business partner with more than one set of bank details, or, alternatively,with no bank details.NoteTo increase flexibility you mark the address nodes as dynamic. This means thatthe system only decides at the runtime whether to actually execute the node. Ifthe application calling the MDG can only supply one street and city asparameters then the system creates the business partner with only one address.For more information, see the field help of the Dynamic node category andDynamic execution-relevant attribute fields.1.2.4 Autonomous MDT CategoriesYou can set an indicator that marks nodes as autonomous. Autonomous MDT categories areof particular importance since they can only be used in creating templates. They describe oneor more master data changes that can be executed in their own right. Non-autonomoustemplate categories form sub-nodes of other, autonomous template categories.1.2.5 Create or ChangeEach template category contains programs for processing the template. The system calls theseprograms by means of the MDG. Most of these programs can create new master data andchange existing master data. Note that some template categories do not support a changemode.ExampleThe template category used to install a device in an installation forbilling purposes does not have a change mode. This is appropriate sincethe corresponding dialog transaction cannot change data either.Below, in the descriptions of the individual template categories, you can see whether aparticular category enables you to change master data objects. Use the attribute that containsthe key of the object to define whether you can execute the template in change or createmode.-11-
Cookbook Master Data TemplatesSAP AGExampleThe BPARTNER template category (business partner) contains thePARTNER attribute (business partner number). With this field you cando one of the following:In the template for the PARTNER attribute, choose the evaluationcategory Constant. Do not enter a value (the field remains empty).Result: Each time you execute the template, the system creates abusiness partner. The system allocates a key to the business partner.In the template for the PARTNER attribute, choose the evaluationcategory Parameter. The application that calls the MDG allocates avalue to the parameter.Result: The system changes the business partner with the transferredkey value.In the template for the PARTNER attribute, choose the evaluationcategory Parameter. The application that calls the MDG does notallocate a value to the parameter.Result: When you execute the template, the system creates a newbusiness partner.NoteThe system does not support external number assignment .If you use a template that can process several prices of master data then you cancreate and change master data objects simultaneously.ExampleFor a new installation you change an existing utility installation (forexample, by allocating a new rate category) and create a new contract.NoteThe master data generator does not support the deletion of objects. This alsoapplies for subobjects.For example: You can create or change one or more addresses for a businesspartner. However, you cannot delete an existing address.1.2.6 Virtual AttributesUse the Virtual evaluation category for virtual attributes. The value is then determined at runtime. This task is executed by a user-defined function module, which you enter as an attributevalue in the template.Function modules for virtual attributes must have a pre-defined interface. For example, youcan use the function module ISU VIRT ATTR REGIO DEMO (demo solution: meter-12-
SAP AGCookbook Master Data Templatesreading unit as a virtual attribute) for your own solution. Note the documentation in the codefor this sample solution.1.2.7 User-Defined FieldsSeveral template categories use an attribute beginning with #CI . These attributes representuser-defined enhancement in the master data tables.ExampleThe PREMISE template category contains the #CI EVBS attribute. Itrepresents the CI EVBS append-structure included in the EVBS table(premise).If you do not create the CI EVBS structure, the CI EVBS attribute is inactive. This is not thecase if you include customer-defined fields for the premise in CI EVBS. If you now create atemplate with the PREMISE category, the system offers the fields of the CI EVBS structureas additional fields. This feature enables you to use the MDG to maintain user-defined fields.1.3 Environment DeterminationOne MDT can be used for simultaneously creating and changing objects. This flexibility isimportant in sales processes, for example. You can use an MDT for initial data creation (tocreate premises, installations and so on), or to change existing objects for a customer (to enterthe rate category from a product sold to the customer in the installation, for example).The key transferred to the MDT determines whether the template creates an object (forexample a utility installation). If the ANLAGE attribute (key for the utility installation) in theINSTALLATION node is assigned a value at runtime, the installation in question is changed.If not, the system creates a new installation.The application that calls the master data generator can use the MDT parameters to definewhat is to be changed or created. However, MDTs can contain many objects: the connectionobject, premise, installations, devices and so on. The application called does not always knowall the objects. Furthermore, some objects may be replicated; there may be two devices (onand off-peak meters), two installations (one for the supplier and one for the distributor) and soon.This situation requires a function that identifies existing objects and allocates them to therespective nodes. We call this function environment determination.Example:The MDT is only called with the key of the premise. If the premisealready has utility installations then the keys of these installations aredetermined.The key is to be automatically allocated to the ANLAGE parameter ofthe INSTALLATION node.It must be ensured that the existing installation of the distributor can bedistinguished from the existing installation of the supplier andallocated to the correct node. This is made possible by comparing-13-
Cookbook Master Data TemplatesSAP AGidentifying constants in the MDT with the values in the respectiveinstallation.There is no universal solution for this task. However, SAP provides two environmentdetermination functions that fulfill the above tasks in special applications:ISU ENVIRONMENT PREMISE is run in the MDT categoriesNEWCUST, NEWCUSTPOD and RATECHANGE. It is only activeif you keep to the conventions of IS-U sales processing for Release4.62 on the SD platform.ISU MDG READ ENV UI is run in the MDT categoryCRMNEWCONTRACT. It is used in the IS-U/CRM integrationsolution. For more information, see the cookbook Integration of SalesProcesses Between IS-U 4.63 and CRM 3.0 in the Servicehttp://service.sap.com. The information below is restricted toISU ENVIRONMENT PREMISE.ISU ENVIRONMENT PREMISEGeneral InformationA utility product references a point of delivery, thereby referring to a utility installation. Thisis defined by the Influence master data field in the definition of the utility product.The MDT defines the modeling of a product in the IS-U data model. In the MDT, there is acomplete interface from which you can choose a subset. You can enter data in the subset. Youcan also refer to existing structures. To do this, ensure you specify the key of the affectedobject and that it is transferred to the corresponding key field.Environment for Technical Master DataThe environment determination function is used in generating quotations and for the sale ofutility products. It finds existing structures and enters key from the corresponding parameterfields in the MDG. This ensures that existing objects are re-used.The NEWCUST, NEWCUSTPOD and RATECHANGE product categories contain theISU ENVIRONMENT PREMISE function module. This function module can search forobjects in the technical master data (such as installation, installation facts, devices, andregisters) belonging to a business partner or contract account.This module operates on two levels and can be used to define a device or register in the IS-Uinstallation found on the first level.Identifying ConstantsIn the MDT, you can, after activating the environment determination function, create aparameter of the identifying constants category. This value defines the criteria by whichdifferent objects of the same category can be selected. Without this parameter, the systemcannot search for the objects.-14-
SAP AGCookbook Master Data TemplatesFigure 3: Identifying constants in MDT maintenanceWhen you create the NEWCUSTOMER MDT, the system examines the data in the SERVICEfield and compares it with the entries in the technical master data for the business partner. Ifthere is a utility installation with the value 002 then the key of that installation isautomatically entered in the VSTELLE field.If there is more than one installation with this value then the system asynchronously proposesa dialog. This dialog allows the user to choose one of the objects found and resume theprocess at the point where it was interrupted.1.4 Master Data Templates1.4.1 ExampleBelow is an example of a MDT. Following this example is a description of the individualMDT categories. The example explains the links between template categories and templates.The NEW PARTNER MDT was created with the BPARTNER template category. Thistemplate creates a business partner and a contract account.-15-
Cookbook Master Data TemplatesSAP AGFigure 4: Create NEW PARTNER master data templateNote the upper left side of the screen. Using the Activate node and Double node (replicate node)pushbuttons, as well as the cardinality of the template category, the following hierarchy hasbeen created:The optional Bank details node was not activated. This means that thebusiness partner was created without a set of bank details.The Address node was activated once.The Telephone number sub-node was replicated. The system createsthe business partner with two telephone numbers. If these nodes
Cookbook Master Data Templates SAP AG-6-1 Master Data Templates 1.1 Overview Master data templates (MDTs) and the master data generator (MDG) are tools used in IS-U to automatically create master data. Business processes necessitate the creation of new utility services or changes to existing ones. Examples are:
SAP has developed a new radio frequency (RF) concept. This RF cookbook helps developers to begin working in the RF framework. It answers frequently asked questions and helps to avoid common errors. This RF cookbook also provides some useful tips about the standard layout and screen structure that should be applied in the standard transactions.File Size: 299KBPage Count: 59Explore further[PDF] SAP EWM RF Cookbook - Free Download PDFdlscrib.comEWM RF Cookbook SAP blog of John Kristensenjksap.wordpress.comRF Cookbook - Part I Description - SAP Communityarchive.sap.comRF Cookbook - Part I Descriptiondocshare01.docshare.tipsSAP EWM RF Framework - SlideSharewww.slideshare.netRecommended to you based on what's popular Feedback
Active Filter Cookbook, CMOS Cookbook, TTL Cook book, RTL Cookbook (out of print), TVT Cookbook, Cheap Video Cookbook, Son of Cheap Video, The Hex adecimal Chronicles, The Incredible Secret M
Naked Persian Turkey Burgers The Skinnytaste Cookbook Perfect Poultry 156 6 6 6 Orecchiette with Sausage, Baby Kale, and Bell Pepper The Skinnytaste Cookbook Perfect Poultry 181 11 11 4. RECIPE COOKBOOK CHAPTER PG SP Roasted Poblanos Rellenos with Chicken The Skinnytaste Cookbook Perfect Poultry 173 7 10 5
How To Cook (use this Arduino cookbook) What Is This Cookbook? This Arduino circuits and programming instruction guide is organized into a "cookbook" style layout. The cookbook illustrates how to create and write various arduino based circuits and programs. These instructions are organized into "Recipes" or instruction guides that can be
cookbook. Eternal gratitude is expressed to all who have contributed to this educational cookbook to include urologists, dietitians and staff. A sincere thank you is extended to the seven celebrity chefs who so graciously shared recipes for use in Living Healthy Cookbook with Information about Urologic Cancers. Nutrition and Cancer
Explain: Cookbook vs. Inquiry We gave you a mystery card and the card’s content should have either the characteristics of a cookbook lesson or an inquiry lesson. Our room will be divided in half. The left side of room will be cookbook, and the right side of the room will be inquiry. Your task is to determine which side of
rudimental cookbook method to my madness 3.2 rudimental lynch, mike rudimental cookbook odyssey ii 3.2 rudimental freytag, edward rudimental cookbook pratfalls 3.2 rudimental whitlock, jon rudimental cookbook tuo kaerf 3.2 concert unknown #32 3.05 concert unknown #47 3.05 .
Nom de l'Additif Alimentaire Fonction(s) Technologique(s) 340(iii) Phosphate tripotassique Adjuvant, antiagglomérant, antioxydant, régulateur de l'acidité, agent de rétention de la couleur, émulsifiant, affermissant, exaltateur d'arôme, agent de traitement des farines, humectant, agent de conservation, agent levant, séquestrant, stabilisant et épaississant 341 Phosphates de calcium .
