Transaction:
/EDGE/SII_SC
In this transaction the SAPScripts texts for header and body to be used in the alarms are parameterized. In this screen we find two blocks: General Data and Generated Sapscripts.
Generated SapScripts
This part shows the SapScripts that have been generated so far. The operation of the screen elements is as follows:
Field | Description |
|---|---|
SAPSCRIPT | SapScript Name |
Denomination | SapScript Description |
Object | Name of the application object |
Text Name | SapScript Text Name |
ID | Text ID |
Language | SapScript Language |
General Data
By double clicking on any of the generated SapScripts lines, the following fields are filled for editing and deletion.
Field | Description |
|---|---|
SAPSCRIPT | SapScript Name |
Denomination | SapScript Description |
Language | SapScript Language |
If for example click the edit icon
:
SapScript appears for editing:
Allowed Variables
The default implementation for reading SapScript text variables is at the header level for the BKPF table. The variables that you want to see reflected in a notification have to be indicated between && in the following way:
&BKPF-field_name&
For example:
&BKPF-BUKRS& → Company This text will be changed by the society in which you are working.
&BKPF-BLART& → Document type: This text will be changed by the document type in which the notification was created.
In this default implementation for the SapScript header text only a maximum of 50 characters can be entered including the name of the variable to be replaced. For example, for the SapScript header text:
And body:
We received the following notification via email (since this was the parameterization of the channel):
