How to use MC=R - Maintain exception: EWS/QMIS

SAP Transaction Code - Details

• Transaction Code: MC=R

  Description: Maintain exception: EWS/QMIS

  Release: S/4HANA and ECC 6

  Menu Path:

  • Logistics > Quality Management > Quality Control > Key Figures > Tools > Early Warning System > Exception > Change
  • Logistics > Logistics Controlling > QM Information System > Early Warning System > Exception > Change
  • Information Systems > Logistics > Quality management > Key Figures > Tools > Early Warning System > Exception > Change
  • Information Systems > General Report Selection > Quality Management > Quality Control > KeyFigures > Tools > Early Warning System > Exception > Change

• • Program: SAPMMCY1

    Screen: 200

    Authorization Object: M_MCYA_EWS

  • Development Package: MCY

    Package Description: Application development R/3 Early Warning System LIS

    Parent Package: APPL

  • Module/Component: LO-LIS-EWS

    Description: Early Warning System

Smart SAP Assistant

• SAP Tcode: MC=R - Maintain exception: EWS/QMIS

  
  Overview:
  The SAP transaction code MC=R is used to maintain exceptions for the Early Warning System (EWS) and Quality Management Information System (QMIS). This code allows users to set up and manage exceptions for these two systems, which are used to monitor and control the quality of products. 
  
  Functionality: 
  The MC=R transaction code allows users to set up and manage exceptions for the Early Warning System (EWS) and Quality Management Information System (QMIS). This code enables users to define the criteria for when an exception should be triggered, as well as the actions that should be taken when an exception is triggered. Additionally, users can view and edit existing exceptions, as well as delete them if necessary. 
  
  Step-by-step How to Use: 
  1. Enter the transaction code MC=R in the command field. 
  2. Select the system you want to maintain exceptions for (EWS or QMIS). 
  3. Select the type of exception you want to create or edit (e.g., warning, error, etc.). 
  4. Enter the criteria for when an exception should be triggered. 
  5. Enter the actions that should be taken when an exception is triggered. 
  6. Save your changes. 
  7. Repeat steps 3-6 for any additional exceptions you want to create or edit. 
  
  Other Recommendations: 
  It is important to note that any changes made using this transaction code will only take effect after a system restart. Additionally, it is recommended that users test any new or edited exceptions before implementing them in a production environment.