Event activities are defined in this window.
PATH: Administration > Utilities > Events "Open" an event.
Window system_event_setup_edit.psr
Field descriptions
|
|
Event
|
The event of the activity.
|
ID
|
Unique ID of this definition.
|
Description
|
Description of this definition.
|
Tabs
|
|
Message
|
Setup the type of message to be created and what to display.
|
Event
|
Under which conditions the activity is created.
|
Button 1...3
|
Up to three buttons can be defined which is displayed in the message/activity.
|
Acceptor
|
The person to receive the message.
|
Message tab
|
|
Save as
|
Which kind of message is created? For further information see separate table "Message types" below.
|
Title
|
Message title (Email, activity...)
|
Message
|
Message text. Place holders are allowed. If the event is linked to a window, all information from this window can be accessed. Available variables are displayed at the bottom of the window.
|
Business partner
|
If an SAP Business One-activity is to be created, enter the business partner ID.
|
Script (return cardcode)
|
Business partner can also be determined per script, and it is returned in variable ls_cardcode
Example: Update customer order.
setvar=ls_carcode=<select cardcode from ordr where docentry={documentparams_docentry}>
|
Bitmap
|
If the message is saved as "beas event with decision" a bitmap can be displayed.
|
Send report
|
Access to macro system, select the macro to be executed.
|
Send as
|
Determines how the macro is executed; select from email, fax, excel, pdf, preview, print.
|
Script to create subject and long text
|
The title and long text can be created by using script.
Title is returned in Variable ls_subject
Message is returned in Variable ls_longtext
Per default these variables are loaded with the text stored in "Title" and "Message"
Example:
setvar=ls_subject=hello world
|
Message types
|
|
Beas event with decision
|
A Beas-message with up to three buttons (decision). It can be processed in the message window quickly.
|
SAP Business One-activity with decision
|
SAP Business One-activity with up to three buttons. Advantage: integrated into the SAP Business One-activity system. Disadvantage: no quick processing. In parallel this message is also displayed in the Beas-message screen. If the message is closed there, the SAP Business One-activity will also be closed.
|
Command
|
Only the script entered in command-tab is executed.
|
Message without decision
|
Only a pure Beas-message is created without decision criteria
|
Event tab
|
|
Event Script
|
Script checks if the activity shall be executed.
Use "return false" to block the creation of an activity.
Example: (itemchange): the activity shall be created only for material group "A500"
select u_gruppe from oitm where itemcode='<e_itemcode>'
if <wert1> <> A500 then
return false
end if
|
From, To
|
The period to create the activity
Example: if during late shift (from 18:00 - 23:59) only a message shall be created: Entering a period exceeding midnight (e.g. 18:00–6:00) is not possible. In that case, two activities are required (e.g.: 18:00–23:59 and 0:00–6:00)
|
Sunday ... Saturday
|
Select the day(s) to create this activity.
Example:
Daily event: the message shall be created only on Wednesday. Remove the check mark for all other days.
|
Do not send messages to yourself
|
If you create an event which causes an activity, you can select not to receive the message.
Example itemchange: create message only if item was changed by someone else.
|
Show every message only once
|
If for example 20 changes are made for one item, this would lead to 20 messages. Activate this option to create only one message (if there are no other unconfirmed messages).
|
Button tab
If the message is defined as "Beas-message with decision" or "SAP Business One-activity with decision" up to three buttons can be displayed.
There, these buttons are defined and filled with functions.
|
|
Name
|
Button name (displayed in activity).
|
Visible
|
Select button to be visible.
|
Activity close
|
If enabled, the activity is closed after clicking this button.
|
Execution Script
|
Important:
There is no reference to the event or the affected window.
For this reason only variables
basenr1, basenr2 and basenr3 are available. basenr1 is of type "Char", basenr2 and 3 of type "Integer"
The content of these variables depends on the event.
Example:
Event with reference to work order.
In variables the work order document number is stored.
Task: Call work order document.
openwindow=fert_fthaupt_edit.psr=belnr_id:<basenr1>
|
|
Bitmap
|
If the message is saved as "Beas event with decision" a bitmap can be displayed.
|
Visibility Script
|
Define the button visibility. The script is executed at the moment the activity is created. All variables and reference to the current window are available.
If the script is ended with "return false" the button is not visible any more.
|
Recipient tab
|
|
Recipient 1...3
|
Not all selected recipients get the message. Beas decides over the recipients according to the following principle:
1. is recipient 1 currently logged on in Beas (program registration, not attendance) If yes, then he is the recipient.
If no:
2. is recipient 2 logged on ?
If yes, then he is the recipient.
If no:
3. is recipient 2 logged on ?
If yes, then he is the recipient
If not, message is sent to recipient 1, even if not logged on.
|
|
Recipient-Script
|
Use script to determine who will get the message. ousr.internal_k is returned in variable "value".
Example: manager to get the message (User_code=manger)
select internal_k from ousr where user_code='<manager>'
setvar=value=<wert1>
|
Command tab
This tab is only visible if in Message > Save as "Command" was selected. Upon the selection, the Button tabs + Acceptor tab disappear.
|
|
Script
|
Window to enter any script.
|
Help URL: https://help.beascloud.com/beas202304/index.html?aktivitt_erstellen.htm
|