1、 DEMO SCRIPT (INTERNAL DOCUMENT) MDG-M Create Material with Process Observer and Replication SCENARIO ID: 8593 General Information MDG Global Authors I813359 Date Last Updated July 2014 COPYRIGHT 2014 SAP AG. ALL RIGHTS RESERVED. No part of this publication may be reproduced or transmitted in any fo
2、rm or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook,
3、and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Para
4、llel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Infor
5、mix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United State
6、s and/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, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, In
7、c. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, 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 technology inv
8、ented and implemented by Netscape. SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countr
9、ies all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials
10、are provided by SAP AG and its affiliated companies (“SAP Group“) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are thos
11、e that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. 3 TABLE OF CONTENTS 1. Demo Script Overview 4 1.1. Demo Description Error! Bookmark not defined. 1.2. Intended audience
12、. Error! Bookmark not defined. 1.3. Protagonists Error! Bookmark not defined. 1.4. Business Pain Points Error! Bookmark not defined. 1.5. Key Messages and Value Proposition Error! Bookmark not defined. 1.6. Storyflow Summary . Error! Bookmark not defined. 2. Technical Requirements . 5 2.1. Prerequis
13、ites (If Any) . 5 2.2. System Access Information . 5 2.2.1. System Landscape 5 2.2.2. System Access Error! Bookmark not defined. 2.2.3. Users . 5 2.2.4. Languages Supported . 6 2.2.5. Data . Error! Bookmark not defined. 2.3. Release for Used Components . 6 3. Demo Script . 7 3.1. Story Flow . 7 3.2.
14、 Step-By Step Guide 7 3.2.1. Release order Proposals . Error! Bookmark not defined. 4. Appendix 21 4.1. Document Updates Notes . 23 SCENARIO ID: 8593 4 SAP AG 2014 / NTERNAL AND PARTNER 1. DEMO SCRIPT OVERVIEW 1.1. Demo Description introduction SAP Master Data Governance is a workflow-driven applica
15、tion introducing change-request based governance processes for master data management embedded in the SAP Business Suite. Master Data Governance comes with pre-delivered content across key domains and is extensible to meet specific business needs. Such extensions are available across such areas as t
16、he data model; user interface and workflow process. This online demo shows the simplest walk-through through the material creation!. It shows the creation of a new material with real-time duplicate detection capabilities during the creation master data record using SAP Master Data Governance. Also t
17、he corresponding review and approval steps are included in this demo and a check in the ERP backup to ensure the activation/ replication was done. It enables you to ensure the validity of material master data, facilitate master data changes with approval workflows, and reduce costs associated with d
18、ata management by streamlining maintenance processes. 1.2. Intended audience Existing customer base 1.3. Protagonists for this script Real Name Role User Name & Password Claire Thomas Master Data Requestor Claire / welcome Mike Scott Master Data Approver Mike / welcome 1.4. Business Pain Points Inco
19、nsistent Master Data across Enterprise Manual Efforts to update and maintain master data in local systems Risk of non-compliance to country specific standards Lack of transparency about changes High Master Data Maintenance costs Multiple Domain specific master data systems No clearly defined roles a
20、nd responsibilities for creating and approving master data 1.5. Key Messages and Value Proposition SAP Master Data Governance provides a central place to maintain master data used in business processes and provides consistent data throughout the enterprise. It enables automatic distribution of mater
21、ial master data and facilitates regulatory compliance by system integrated change and approval processes. Out of box native integration with SAP Business Suite and ERP Reduce maintenance efforts with high Data quality SCENARIO ID: 8593 5 SAP AG 2014 / NTERNAL AND PARTNER Delivers Consistent Definiti
22、on, Authorizations and replication of key master data entities for SAP Re use of SAP Data Model, UI and Existing business logic and configuration for creation and validation of Master Data Eliminates error prone manual maintenance across multiple systems Compliments and extends SAP Netweaver MDM Ena
23、bles governance, compliance and transparency through integrated staging, approval and central audit trail. Trusted Data Quality Information One source of truth Flexible and unified view of all information Data flow transparency 2. TECHNICAL REQUIREMENTS 2.1. PREREQUISITES 2.2. SYSTEM ACCESS INFORMAT
24、ION 2.2.1. System Landscape How to Access this scenario on SDC For any information specific to the Technology cluster, go to SDC Wiki to find all the useful information like Accessing SAP Demo Cloud directly at Setup Information What is this cluster all about Limitations and Know issues Contact inf
25、ormation to reach out to for any questions. etc Note: This Wiki is the single point of information which will be constantly updated on various topics. It is easy to update a single wiki link than updating these demo script each and every time a process is changed. So, please add this wiki link to yo
26、ur favorites and keep checking for latest updates. Simple steps: (Refer above WIKI link for Detailed information) Logon to SDC portal - Demo ID 9010 : Technology Cluster Edition 2014 V1/2 Overview : https:/ 2.2.2. Users/Login information (EC3 / 800 CLIENT): Predefined User (Role) Password Component
27、Claire welcome Requestor Mike welcome Approver SCENARIO ID: 8593 6 SAP AG 2014 / NTERNAL AND PARTNER 2.2.3. Languages Supported Please select the standard languages in which this demo is available (i.e. translated into). _ English _ German _ French _ Spanish _ Portuguese _ Japanese _ Simplified Chin
28、ese _ Korean 2.3. RELEASE FOR USED COMPONENTS Software Component Release Support Pack MDG 7.0 SP1 EIM 4.2 SP3 Chrome (not NWBC for IE or rich client) is RECOMMENDED SCENARIO ID: 8593 7 SAP AG 2014 / NTERNAL AND PARTNER 3. DEMO SCRIPT 3.1. STORY FLOW What To Say The following scenario illustrates how
29、 SAP Master Data Governance is utilized to centrally maintain material master data. In this example we are going to look at the ability in MDG to Create material. What To Do & What you should see The requestor Claire raises a new request (change request or CR) to create a new material. The approver
30、then checks the data. The approver can either: 1) Approve 2) Send back for revision Here the requestor can make the changes and resubmit the request or withdraw the same request. Demo Story Flow: 1) Material creation process (MDG CR Process using MAT01) happens in EC3/800. 2) After activation materi
31、al gets stored in EC3/800. 3) When you check under “Backend Access” you are actually viewing backend system EC3/800. 4) Next with the active replication model (drf model) periodically updating new records, the material is replicated the to EC3/811 (new client). This would, with an SAP environment wi
32、th other ERPs make the new material availalble for all (PLM etc) . 3.2. STEP-BY STEP GUIDE SCENARIO ID: 8593 8 SAP AG 2014 / NTERNAL AND PARTNER Step 1.0 - Access the System What To Say Please see section 2.2.1 in the prerequisite section of this demo script document. Step 2.0 Connect to NWBC What t
33、o say Connect to MDG using IE or Chrome with this URL: http:/ciec3.wdf.sap.corp:50080/nwbc/?sap-client=800&sap-language=EN&sap-nwbc-node=root&sap-theme=sap_corbu What To Do web access via Chrome What to Say (include necessary Screenshots) 1. Open this URL to get the Login screen: http:/ciec3.wdf.sap
34、.corp:50080/nwbc/?sap-client=800&sap-language=EN&sap-nwbc-node=root&sap-theme=sap_corbu Step 3.0: Create change request What to say Claires first step will be to create a Change request for creating a new Material. She will choose the Change Request Type and will enter the most important values for
35、the new material. She will also Submit the request. At the end of this step she will check in the system the next processors of her submitted request. What To Do What to Say (include necessary Screenshots) SCENARIO ID: 8593 9 SAP AG 2014 / NTERNAL AND PARTNER 1. Login as claire/welcome and click on
36、Log On System will log you on 2. Navigate to Material Governance and Click on Create Material A popup appears 3. Enter the name of the material (call it what you want, eg.: SC10000xx) and select the change request MAT01 WARNING avoid using special characters in material names as shown in the screen
37、shots (this is a known issue and will be allowed in future editions) CAUTION: If you get the error that you need to choose a valid change request type (so you cant The system displays the major form for entering values for the new material SCENARIO ID: 8593 10 SAP AG 2014 / NTERNAL AND PARTNER use M
38、AT01), try another unique material name. This message appears if theres something in the system similar or in staging. Click on Continue 4. Enter - the description (your choice, eg: CR for Demo001) WARNING the description is sometimes overwritten after its submitted so avoid exposing this later in t
39、he demo (will show a different desc in the CR approval queue. We will be patching the public showroom - Base Unit of Measure - Material Type - Industry Sector - Material group - Net Weight & Unit - Language Key & Description Remember the name of your Change Request because you will use this name lat
40、er on in this demo. Your Change Request Name: _ BTW: The system will show a message if a duplicate exists. SCENARIO ID: 8593 11 SAP AG 2014 / NTERNAL AND PARTNER 5. Click on Submit. The system will respond with a success message 6. Close this pop up 7. Go to “My Change Request” Page and select the c
41、hange request and click on workflow log. A new popup window will appear SCENARIO ID: 8593 12 SAP AG 2014 / NTERNAL AND PARTNER 8. In this workflow log you can click on “Current Processor(s)” to display all processers responsible for the next step in the workflow. 9. Close this window 10. Log off NWB
42、C as Claire OPTIONAL: if you would like to show what trying to create a duplicate material will do in the system, choose CR type: MAT01 and material (template) tp_chilled_02 NOTES: a. Fields relevant for duplicate check are now 2 fields: Description and Material Type (MATART) b. Classification is no
43、t taken into duplicate consideration because while possible, showing in the public (shared) democloud causes to many issues and possible negative side effects. As a talking point here you can explain that for this demo, “classification” is disabled but its possible via ESH in standard c. Scoring onl
44、y shows if 100% comes up. d. Showing the match score in the first column as a talking point is only SCENARIO ID: 8593 13 SAP AG 2014 / NTERNAL AND PARTNER possible for user “Claire” Step 4.0: Approve Change Request What to say The approver mike approves the request. Mike is responsible to review and
45、 approve change requests for new material. He will start his worklist in the system and recognizes that a new request has been send to him. He will check the new Change Request and will approve it. What To Do What to Say (include necessary Screenshots) SCENARIO ID: 8593 14 SAP AG 2014 / NTERNAL AND
46、PARTNER 1. Login in as mike/welcome System will log you on 2. Click on Change request System will display Change Request SCENARIO ID: 8593 15 SAP AG 2014 / NTERNAL AND PARTNER 3. Select the change request which you noted down in the last chapter (should be top of the list) and click on “Process Chan
47、ge Request”. (alternatively you can also click on the link in column Subject) The System will open a popup window to display the details of the change request. Additional Info: You canmention also the Substituion Concept: This list is fully integrated into SAPs POWL functionality. If a employee leav
48、es for vacation he can define a substiute etc. 4. Inspect the values transmitted by Claire from the last demo step and Click on activate. SCENARIO ID: 8593 16 SAP AG 2014 / NTERNAL AND PARTNER 5. The system will confirm the activation and you can close the popup Optional: Change Document Next steps
49、are optional steps: Show these steps if the customer is interested in the change document functionality 6. If you want to see the change document then: Click on Change requests-Display change documents Select entity type Material Enter the material created by Claire (SC100001) 7. Click continue 8. Inspect the table 9. In objects select -Attribute changes System shows a
