Tasks to be completed when documenting an SAP Transaction, Report or Message code.

 1. Title of the page = SAP Transaction code, SAP Report or SAP Message

2. Add the following Labels, respectively : 

    • SAP Transaction => "sap_transaction"

    • SAP Report => "sap_report"

    • SAP Message => "sap_msg"


3. On the left section, describe the steps. On the right section, insert respective print screens and additional guidelines, if needed (e.g. Main selections of the transaction...)




Check the different possibilities for this transaction:









There are different overviews for this transaction:








1) The SCMA tool updates the status of a task even if this one is ran on a test mode: in a technical point of view the success of some tasks executed (namely SM35) depends on run of the transaction itself. The quality of the information executed (Test mode/Real mode; Period; CCode, etc.) needs a user analysis and assurance that the input to this type of programs are reliable.

2) Even if it has errors, the performance of the batch-inputs is always reflected with the status “Processing completed without errors” – green status: for the same reason as the one mentioned above.

3) To have the most recent Analysis of the Status Update we must use refresh button so that the SCMA can provide us the most updated status possible.

4) It is important, from service center point of view, to work with SCMA and Z_SCMO_TASKLIST in parallel, since sometimes some status in the second transaction is not updated accordingly, above all with notes and workflows.

5) When this exception is applicable, if the changes implies workflows, these one must be deleted from SAP SM and rescheduled with the new information.

6) All the assigned members to the companies is responsible for:

    • The consistency (sequence of the tasks, variants, recurrent errors, etc) of his company in the SAP SM;
    • Give feedback related to the consistency of the SAP SM;
    • Provide information about the updates needed, to the team Specialists, to improve the consistency and reliability of the tool right after the closure;
    • Update always the status of the companies which are assigned to;
    • Update the global operations file  of the Country which complements the SCMA data.

7) When running Programs which tasks are in advanced or postponed we must always be aware if the programs concerns to the range time [D-5 till D-1] or [D+1 till D+4]. For instance a program which has the variants defined to run in the range [D-5 till D-1] can’t be run in the range time [D+1 till D+4]. and vice-versa.

8) ­After having a status defined, the task cannot be deleted anymore.




As alternative, you can use other schedule manager transactions to monitor the tasks: