MCYH - Analyse de l'exception SIA

SAP Transaction Code - Details

• Transaction Code: MCYH

  Description: Analyse de l'exception SIA

  Release: S/4HANA and ECC 6

  Menu Path:

  • Logistics > Materials Management > Purchasing > Purchase Order > Reporting > Purchasing Information System > Standard Analyses > Exception Analysis
  • Logistics > Materials Management > Purchasing > Purchase Order > Reporting > Purchasing Information System > Early Warning System > Exception Analysis
  • Logistics > Materials Management > Purchasing > Outline Agreement > Reporting > Purchasing Information System > Standard Analyses > Exception Analysis
  • Logistics > Materials Management > Purchasing > Outline Agreement > Reporting > Purchasing Information System > Early Warning System > Exception Analysis
  • Logistics > Materials Management > Purchasing > RFQ/Quotation > Request for Quotation > Reporting > Purchasing Information System > Standard Analyses > Exception Analysis
  • Logistics > Materials Management > Purchasing > RFQ/Quotation > Request for Quotation > Reporting > Purchasing Information System > Early Warning System > Exception Analysis
  • Logistics > Logistics Execution > JIT Outbound > Environment > Purchasing > Purchase Order > Reporting > Purchasing Information System > Standard Analyses > Exception Analysis
  • Logistics > Logistics Execution > JIT Outbound > Environment > Purchasing > Purchase Order > Reporting > Purchasing Information System > Early Warning System > Exception Analysis
  • Logistics > Logistics Execution > JIT Outbound > Environment > Purchasing > Outline Agreement > Reporting > Purchasing Information System > Standard Analyses > Exception Analysis
  • Logistics > Logistics Execution > JIT Outbound > Environment > Purchasing > Outline Agreement > Reporting > Purchasing Information System > Early Warning System > Exception Analysis
  • Logistics > Logistics Execution > JIT Outbound > Environment > Purchasing > RFQ/Quotation > Request for Quotation > Reporting > Purchasing Information System > Standard Analyses > Exception Analysis
  • Logistics > Logistics Execution > JIT Outbound > Environment > Purchasing > RFQ/Quotation > Request for Quotation > Reporting > Purchasing Information System > Early Warning System > Exception Analysis
  • Logistics > Logistics Execution > JIT Inbound > Environment > Purchasing > Purchase Order > Reporting > Purchasing Information System > Standard Analyses > Exception Analysis
  • Logistics > Logistics Execution > JIT Inbound > Environment > Purchasing > Purchase Order > Reporting > Purchasing Information System > Early Warning System > Exception Analysis
  • Logistics > Logistics Execution > JIT Inbound > Environment > Purchasing > Outline Agreement > Reporting > Purchasing Information System > Standard Analyses > Exception Analysis
  • Logistics > Logistics Execution > JIT Inbound > Environment > Purchasing > Outline Agreement > Reporting > Purchasing Information System > Early Warning System > Exception Analysis
  • Logistics > Logistics Execution > JIT Inbound > Environment > Purchasing > RFQ/Quotation > Request for Quotation > Reporting > Purchasing Information System > Standard Analyses > Exception Analysis
  • Logistics > Logistics Execution > JIT Inbound > Environment > Purchasing > RFQ/Quotation > Request for Quotation > Reporting > Purchasing Information System > Early Warning System > Exception Analysis
  • Logistics > Logistics Execution > Information System > Goods receipt > Standard Analyses > Exception Analysis
  • Logistics > Production > Kanban > Environment > Purchasing > Purchase Order > Reporting > Purchasing Information System > Standard Analyses > Exception Analysis
  • Logistics > Production > Kanban > Environment > Purchasing > Purchase Order > Reporting > Purchasing Information System > Early Warning System > Exception Analysis
  • Logistics > Production > Kanban > Environment > Purchasing > Outline Agreement > Reporting > Purchasing Information System > Standard Analyses > Exception Analysis
  • Logistics > Production > Kanban > Environment > Purchasing > Outline Agreement > Reporting > Purchasing Information System > Early Warning System > Exception Analysis
  • Logistics > Production > Kanban > Environment > Purchasing > RFQ/Quotation > Request for Quotation > Reporting > Purchasing Information System > Standard Analyses > Exception Analysis
  • Logistics > Production > Kanban > Environment > Purchasing > RFQ/Quotation > Request for Quotation > Reporting > Purchasing Information System > Early Warning System > Exception Analysis
  • Logistics > Production > Kanban > Environment > Warehouse Management > Environment > Rough workload estimate > Logistics Information System > Standard Analyses > Purchasing > Exception Analysis
  • Logistics > Logistics Controlling > Logistics Information System > Standard Analyses > Purchasing > Exception Analysis
  • Logistics > Logistics Controlling > Purchasing Information System > Standard Analyses > Exception Analysis
  • Logistics > Logistics Controlling > Purchasing Information System > Early Warning System > Exception Analysis
  • Information Systems > Logistics > Purchasing > Tools > Early Warning System > Exception Analysis

• • Program: SAPMMCY1

    Screen: 5000

    Authorization Object:

  • 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: MCYH - Analyse de l'exception SIA

  
  Overview:
  The SAP transaction code MCYH is used to perform an exception analysis for the Purchasing Information System (PURCHIS). This code allows users to analyze and identify any exceptions that may have occurred in the purchasing process. It also provides a detailed overview of the purchasing process, including the purchase order, goods receipt, invoice verification, and payment. 
  
  Functionality: 
  The MCYH transaction code provides users with a comprehensive overview of the purchasing process. It allows users to identify any exceptions that may have occurred in the purchasing process, such as incorrect pricing or incorrect delivery dates. The code also provides users with detailed information about the purchase order, goods receipt, invoice verification, and payment. Additionally, it allows users to analyze the data and identify any potential issues or discrepancies. 
  
  Step-by-step How to Use: 
  To use the MCYH transaction code, users must first enter the Purchasing Information System (PURCHIS) and select the “Exception Analysis” option. This will open up a window where users can enter the relevant information for their analysis. Once all of the necessary information has been entered, users can click “Execute” to begin their analysis. The results of the analysis will be displayed in a table format, which can be used to identify any exceptions that may have occurred in the purchasing process. 
  
  Other Recommendations: 
  It is recommended that users regularly use the MCYH transaction code to analyze their purchasing process and identify any potential issues or discrepancies. Additionally, it is important for users to ensure that all of their data is accurate and up-to-date before performing an exception analysis. This will help ensure that any exceptions identified are accurate and can be addressed quickly and efficiently.