Do you have any question about this t-code?
Transaction Code: MC/Z
Description: Schedule Jobs: Exceptions SIS
Release: S/4HANA and ECC 6
Menu Path:
Program: SAPMMCY1
Screen: 4000
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
Overview: The SAP transaction code MC/Z - Schedule Jobs Exceptions SIS is used to schedule jobs in the SAP system. It allows users to set up and manage job scheduling, including setting up job exceptions and monitoring job execution. Functionality: This transaction code enables users to create, modify, and delete job scheduling tasks. It also allows users to view the status of jobs, set up job exceptions, and monitor job execution. Additionally, it provides a graphical overview of the job scheduling tasks and their associated parameters. Step-by-step How to Use: 1. Enter the transaction code MC/Z - Schedule Jobs Exceptions SIS in the command field. 2. Select the “Create” button to create a new job scheduling task. 3. Enter the necessary parameters for the task, such as the start date and time, end date and time, frequency of execution, etc. 4. Select “Save” to save the task. 5. Select “Execute” to execute the task immediately or “Schedule” to schedule it for later execution. 6. To view the status of a job, select “Status” from the menu bar and enter the job name or ID in the search field. 7. To set up job exceptions, select “Exceptions” from the menu bar and enter the necessary parameters for each exception type (e.g., start date and time, end date and time). 8. To monitor job execution, select “Monitor” from the menu bar and enter the necessary parameters for each job (e.g., start date and time, end date and time). 9. Select “Save” to save any changes made to the task or “Delete” to delete it from the system. Other Recommendations: It is recommended that users familiarize themselves with all of the features available in this transaction code before using it in order to ensure that they are able to use it effectively and efficiently. Additionally, users should ensure that they have sufficient authorization before attempting to use this transaction code as some features may require additional authorization levels.