Launch the Transaction SCMA:

In order to create a task or make any adjustment in SAP SM , please access the change mode function by clicking in the button “change the tasklist”.

Prior to start inserting the tasks, a main folder (node) must be created having as reference the following codification: Country Code: Country + Closing Tasklist. Example: 

The only exception for this rule is SAP SM created at Business Level (Solexis Example: 

Click on the icon  to insert a task group or  to insert a task. In case of selecting:

• A task group (folder): it is only necessary to insert the description of the task

  The description of all folders must differ taking into account that when two folders are created with the same description the transactions of the first folder will be automatically transferred to the second one. The first folder becomes empty

  
  

• A task: there is the need to choose the type of task (see below).

The description must obey to a specific codification:

• If it is run at a company level, the description has to start by the four digits of the company code, then “: ” and finally the description of the task itself.
• If it is run at a country level, the description has to start by the country code, then “:” and finally the description of the task itself.
• The tasks which are common to several countries have to obey to the same description. Therefore, please copy the descriptions used to the other countries.

The task owner is a non mandatory field to define who is responsible for the execution of task. It can be finance operation or service units ().

Choosing the more suitable type of task:

• Program  - transaction programmed in advance based on a relative time and which will run automatically on the scheduled day and hour. It can be used for cycles run, settlements, depreciation run, etc. There is always a variant assigned to a program.

• Transaction  - it is used when the user intervention is needed or an automatic program is not the most suitable option. (Ex: checks, close and open of MMRV, etc).

• Notes  - it is used as an additional information, a reminder or for procedure.

• Flow Definition  - can be split into 2 Groups of Flow Definitions:

  • Validation WorkFlows: automatic and standard messages sent to a distribution list in order to ensure the validation of certain task (e.g. Validation of the Product Costing + Material Ledger).

  • Execution WorkFlows:

    • With Validation: includes a Validation Workflow plus a sequence of automatic programs with variants (which are launched autonomously after the validation considering the interdependency between them).
    • Without Validation: Sequence of Automatic Programs with variants which are launched automatically based on the relative time. 

A) Programs:

After inserting a new task, insert its description, task owner (search inserting *WF* if needed), flag the option “program” and click on the match code .

In the field ‘Program name’ insert the transaction in between two asterisks and press F4. (E.g. entering *KSU5* the following screen will be accessed) or check the information list of available programs in the information box below.

Double click on the row and the field program will be automatically updated.

The program also needs to have a variant assigned. First, check through the match code button, on the variant field, whether it already exists for that task.
If not, proceed as described as following on the point a), if yes, skip to point b).

a) Click on the icon  to create the variant, name it and click on “create” and after in “continue”:

• • A screen will be launched similar to the transaction inserted
  • Fulfill the fields required (the ones related to the period, posting date and year are mandatory but not relevant)

b) Click on the icon  or in 

• • Flag the options required, usually the ones related with document date, posting date or year are the most common ones:

• • For all the fields there is a need to have a variable selection choose in the column the option "T” for Table Variable from TVARVC or “D” for "Dynamic date calculation”
  • Depending on what was chosen previously the column  will have to be filled accordingly:

    Click on the arrows to check your options according to the fields you have chosen as variables.

    For selection criteria "T - Table Variable from TVARVC”:

• • • Period and Year

If the program should run in the current period, choose:

• • SAP_SCMA_PERIOD (for from_p and to_p)
  • SAP_SCMA_FISC_YEAR (GJAHR)

If the program should run in the previous period, choose

• • SCMA_PERIO (for from_p and and to_p) and SCMA_GJAHR (GJAHR)

If the program should run in the next period, choose

• • SCMA_PERIOM+1 and SCMA_GJAHRM+1

If the program should run in the 2,3 or 4 periods in advance, choose

• • SCMA_PERIOM+2, SCMA_PERIOM+3 or SCMA_PERIOM+4 and SCMA_GJAHRM+2, SCMA_GJAHRM+3 or SCMA_GJAHRM+4

• • • Cumulative Period:

In order to choose a cumulative period (currently used for the Matcheops program only) please follow the next steps:

Click on the arrow, finding the option 

For selection criteria "D - Dynamic date calculation”:

• • • Dates:

Click on the arrows to choose one of the following options:

Save

B) Transactions

Flag the option ‘Transaction’ and insert the transaction code.

C) Notes

Flag the option ‘Note’. In this case the description will be the task to be executed (example: procedure Clearing Payroll Accounts in the image below).

All SAP SM tasks have predefined a Type of Day and Start time.

Generically SCMA allows 2 Types of days definition (image below), namely:

• Offset in work days – defines the foreseen working day (relative time) of a task execution (strongly recommended one);

• Offset in calendar days – defines the real date for a task run.

SAP SM in Solvay does not work on calendar days. The majority of SAP SM tasks have defined a Working Day relative time (Exception release Cost estimate).

Check other options:

• Delete a task, you just need to select it and to click on the icon 

• Insert a notein a task by clicking with the right button of the mouse
  Additional comments added to support the run of a certain transaction (variants, reminders, etc...). Only locally accessible in EN login. 

• Insert a office document by clicking on the button 
  It is used to complement the transaction to be launched with an office document (e.g. MS Word, Excel, etc). Normally, it is used to include the link to the correspondent procedure. It has the advantage of combining the notes mentioned above with an office document. Only locally accessible in EN login. Locally accessible in different logins.

It is possible to combine both types of documents with the same task in the same column. The icon will assume the format of an office document. When clicking on it, you will be able to choose the one you want via the box below: