Indicate here the code of a function that will be executed when the user carries out the corresponding choice.
Some functions accept an additional parameter, namely:
- MENU : this signifies that the menu line calls a sub-menu, where the code must be entered in the options column.
- AIMP: this signifies that the menu line calls a report, whose code must be entered in the options columns. if the report code is not entered, the menu line makes it possible for the user to choose the report that when it is launched, by displaying the list of all the reports that the user has access to.
- all the functions that correspond to the object management with transactions that can be parameterised (that is to say the majority of the movements). It is then possible to give as an argument the transaction code to be used ( this is not mandatory : if this is not done, there will be the choice of transaction (if a choice is possible) from amongst the different transactions for which the user is authorised.
- all the functions that correspond to the parameterizable standard inquiries. It is then possible to give an argument for the enquiry screen code to be used (this is not mandatory : if this is not done, a default enquiry screen will be used) and it will then be possible to change the screen by selection (if a choice is possible) from amongst the different screens for which the user is authorised.
- SYSTEME (execution of a system order): The order is given in the form of a command line, entetered in a specific window and whose syntax is specified in an annex ocumentation.
- AMIEXE (execution of a system transaction): The transaction code can be specified.
- the ADPVAL function, which is used to modify the basis of the parameters in the software, can be called with an argument defining the chapter (for instance SUP), or an argument defining the chapter and a template of parameter names in the form CHAPITER_TEMPLATE (for instance SUP_USR*), or even a template without chapter (for instance USR*).