SAP How-To Guide Master Data Governance for Material How To... Master Data Governance for Material: File Down- and Upload Applicable Releases: EhP5 Version 1.0 November 2011
Copyright 2011 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form 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, Outlook, and PowerPoint are registered trademarks 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, i5/os, POWER, POWER5, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States 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, Inc. 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 invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mysap, mysap.com, xapps, xapp, SAP NetWeaver, 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 countries 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 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 those 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. These materials are provided as is without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these materials. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third party web pages nor provide any warranty whatsoever relating to third party web pages. SAP NetWeaver How-to Guides are intended to simplify the product implementation. While specific product features and procedures typically are explained in a practical business context, it is not implied that those features and procedures are the only approach in solving a specific business problem using SAP NetWeaver. Should you wish to receive additional information, clarification or support, please refer to SAP Consulting. Any software coding and/or code lines / strings ( Code ) included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or grossly negligent. Disclaimer Some components of this product are based on Java. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components. Any Java Source Code delivered with this product is only to be used by SAP s Support Services and may not be modified or altered in any way.
Document History Document Version Description 1.00 First official release of this guide
Typographic Conventions Type Style Example Text Description Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Cross-references to other documentation Icons Icon Description Caution Note or Important Example Recommendation or Tip Example text Example text Example text <Example text> EXAMPLE TEXT Emphasized words or phrases in body text, graphic titles, and table titles File and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools. User entry texts. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. Keys on the keyboard, for example, F2 or ENTER.
Table of Contents 1. Business Scenario... 2 2. Background Information... 3 3. Prerequisites... 3 4. Step-by-Step Procedure... 4 4.1 Role... 4 4.1.1 Add Web Dynpro Applications to Role... 4 4.1.2 Test the Role... 6 5. Process... 7 5.1 File Download... 7 5.1.1 Determine Entity Type... 7 5.1.2 Define Selection... 7 5.1.3 Define File Structure... 7 5.1.4 Determine Download Settings... 8 5.1.5 Check and Execute... 8 5.1.6 Optional: Save Variant... 8 5.1.7 Confirmation... 9 5.1.8 Save File... 9 5.1.9 Possible Entities for Download... 10 5.2 File Upload... 11 5.2.1 Save Changes in File... 11 5.2.2 Create Mass Change Request... 12 5.2.3 File upload: Determine Entity Type... 14 5.2.4 Define File Structure... 14 5.2.5 Determine Upload Settings... 15 5.2.6 Possible Entities for Upload... 16
1. Business Scenario SAP Master Data Governance for Material (MDG-M) provides business processes to find, create, change, and mark material master data for deletion. It supports the governance of material master data in a central hub and the distribution to connected operational and business intelligence systems. The processes are workflow-driven and can include several approval and revision phases, and the collaboration of all users participating in the master data maintenance. MDG also support mass processing for create and change materials. There are different possible approaches: Mass change (WebDynproApplication USMD_MASS_CHANGE) You can use this Web Dynpro application to change the value of attributes to a common value for multiple selected material. This Web Dynpro application can be only used for the attributes of the type 1 entity material. UI for Mass CR (WebDynproApplication USMD_CREQUEST_CREATE, CR Type MAT0A) You can create a CR for process multiple materials. With this you can create new materials and/or add existing material to change these materials. File Upload (CSV; WebDynproApplication USMD_FILE_UPLOAD) You can use this Web Dynpro application to upload a CSV-file per entity. You can create and change materials. File Import (IDOC XML; WebDynproApplication MDG_FILE_UPLOAD_CMP) You can use this Web Dynpro application to upload a IDOC XML-file per material. You can create and change materials. This How To Guide shows how the CSV file download and upload functionality can be used for materials. The file download and upload functionality was delivered in the SAP_FIN_MDM Role for Financial. But the Web Dynpro Applications can also be used for Material.
2. Background Information Comparison File Import (IDOC-XML) and File Upload (CSV-File) File Import (IDOC-XML) File Upload (CSV) Activity Create and Change Create and Change Files Multiple Materials with complete data per File Multiple Materials per Entity Staging Reuse entities Flex entities not out-of-the-box; need to: Enhance IDoc with segments containing the flex data implement an IDoc BAdI to write flex data via CL_USMD_CREQUEST_API into the staging Active Area Only reuse entities; Not flex entities n/a Reuse and flex entities 3. Prerequisites Notes 1588446, 1628540, Note 1633315, 1653259, 1608950, 1623262, 1620037 Note 1571467 Functional restrictions in MDG-M
4. Step-by-Step Procedure 4.1 Role 4.1.1 Add Web Dynpro Applications to Role Transaction PFCG, select your Role: Choose Web Dynpro Application : Assign USMD_FILE_UPLOAD and USMD_FILE_DOWNLOAD.
Test the Transaction: Set Model to MM. Save.
4.1.2 Test the Role
5. Process 5.1 File Download http://help.sap.com/erp2005_ehp_05/helpdata/en/d8/5dc9fd46294fa596c71d5fc14a7913/frameset.htm 5.1.1 Determine Entity Type 5.1.2 Define Selection I want to change all P-89* Materials. Some are active and some are already in a CR. I m the processor of the open CR s. 5.1.3 Define File Structure
5.1.4 Determine Download Settings 5.1.5 Check and Execute 5.1.6 Optional: Save Variant
5.1.7 Confirmation 5.1.8 Save File Save file as *.CSV, then you can open it with Excel.
5.1.9 Possible Entities for Download Material (Attributes and Language-Dependent Texts) Basic Data Text Internal Comment Class Assignment Characteristic Valuation International Article Numbers (EANs) Units of Measure for Material Customer entities and fields
5.2 File Upload http://help.sap.com/erp2005_ehp_05/helpdata/en/d8/5dc9fd46294fa596c71d5fc14a7913/frameset.htm You can use this Web Dynpro application (USMD_FILE_UPLOAD) to copy master data from a file to the database tables defined in the data model for Master Data Governance. You can also specify how the existing master data is to be handled during the upload process. Upload Mode: Delete all The system deletes all existing master data. It then recreates the data records contained in the upload file. Upload Mode: Delete Uploaded Data The system deletes only the existing master data for which the upload file contains data records. It then recreates the data records contained in the upload file. Upload Mode: Overwrite or Add The system overwrites only those attributes in the existing master data that are contained in the upload file. All other attributes are retained. 5.2.1 Save Changes in File Change Data in Excel and save as *.CSV The file that is to be uploaded must be a text file (for example, a CSV file). Binary files are not supported. Field values can be separated by a semi-colon, tab, comma, or other printable character. With the exception of the tab, the system does not support hidden characters. You have saved the file that is to be uploaded on either the presentation server (that is, your local PC) or the application server. Is the Material already used in an open CR then you must be the processor, otherwise the upload does not work.
5.2.2 Create Mass Change Request To upload the file, you require a change request, which is used to approve and track changes. You must also be the current processor.
5.2.3 File upload: Determine Entity Type Use the same variant as for the download. 5.2.4 Define File Structure File structure from variant EM_P_89
5.2.5 Determine Upload Settings You can also specify how the existing master data is to be handled during the upload process with the upload mode. The system deletes all existing master data. It then recreates the data records contained in the upload file. The system deletes only the existing master data for which the upload file contains data records. It then recreates the data records contained in the upload file. The system overwrites only those attributes in the existing master data that are contained in the upload file. All other attributes are retained.
5.2.6 Possible Entities for Upload Material (Attributes and Language-Dependent Texts) Units of Measure for Material International Article Numbers (EANs) Basic Data Text Internal Comment Customer entities and fields SAP does not support the upload of Entity Class Assignment and Entity Characteristic Valuation. If you upload not existing Classes, Characteristics or Characteristic Values to the Material the Change Request will become corrupt. It is not possible to correct the data in the Change Request UI. See also note 1571467.
www.sdn.sap.com/irj/sdn/howtoguides