Convert Message Types in Purchase Order: Warning Message into Error Message

Summary
Converting Warning Messages in Purchase order to Error messages for some validations.While trying to create a PO in ME21 N,if the delivery date is unrealistic, the SAP system just issues a warning Message and allows us to proceed which ideally should not be the case. For example ,if a PO is created today and the delivery date is 23.10.2005 , the system stills allows us to proceed with the creation of the PO.In such cases,the system must throw an error message in such cases and stop proceeding until this is corrected.This document explains in detail with screenshots how to achieve the mentioned issue. Author: Swarna.S

Company: Tata Consultancy Services Created on: 6 November 2008

Author Bio
Swarna is a SAP Techno Functional Consultant working for Tata Consultancy Services for more than two years.

SAP COMMUNITY NETWORK 2008 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 1

Convert Message Types in Purchase Order: Warning Message into Error Message

Table of Contents
Converting Warning Messages in Purchase order to Error messages ..............................................................3 Steps involved in Changing the message type...............................................................................................3 Step 1 : Message Information .........................................................................................................................3 Step 2 : System Messages for Purchasing in SPRO......................................................................................4 Step 3 : Changing the system message from Warning to Error. ....................................................................4 Step 4 : Transport request ..............................................................................................................................5 Step 5: Warning message changed to Error Message while creating the PO................................................6 Copyright.............................................................................................................................................................7

SAP COMMUNITY NETWORK 2008 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 2

Convert Message Types in Purchase Order: Warning Message into Error Message

Converting Warning Messages in Purchase order to Error messages

In the example given below, while trying to create a PO in ME21 N,the delivery date is showing23.10.2005. This is an unrealistic delivery date as of today. But the SAP system just issues a warning Message and allows us to proceed which ideally should not be the case. The system must throw an error message in such cases and stop proceeding until this is corrected.

Steps involved in Changing the message type

Step 1 : Message Information The message number of the warning message is obtained by double clicking the yellow mark where we get the Performance assistant. In that click the technical informationF1). We get : Now the message number is 040 and application area is ME.

SAP COMMUNITY NETWORK 2008 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 3

Convert Message Types in Purchase Order: Warning Message into Error Message

Step 2 : System Messages for Purchasing in SPRO With message information we go to the Transaction code SPRO. Go to SPRO materials management Purchasing messages system messages. Environment data Define attributes of system

Step 3 : Changing the system message from Warning to Error. Double click the system messages. We get the below screen.

SAP COMMUNITY NETWORK 2008 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 4

Convert Message Types in Purchase Order: Warning Message into Error Message

For this particular message type we find W which means a warning message is issues by the system. To change this message type to Error message type, we change the W to E.

Step 4 : Transport request

SAP COMMUNITY NETWORK 2008 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 5

Convert Message Types in Purchase Order: Warning Message into Error Message

Step 5: Warning message changed to Error Message while creating the PO

SAP COMMUNITY NETWORK 2008 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 6

Convert Message Types in Purchase Order: Warning Message into Error Message

Copyright
2008 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, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, 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. 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.

SAP COMMUNITY NETWORK 2008 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 7