You use this program to configure events that you want to monitor within SYSPRO as they occur. It enables you to invoke third-party applications (developed in an appropriate language) when a particular event occurs in SYSPRO (e.g. stock falls below zero).
The actions that can be associated to an event include launching programs (i.e. SYSPRO, NetExpress, or third party applications) and sending e-mail messages to specified persons. For example: Whenever the quantity on hand for a particular stock item falls below zero in a specific warehouse, SYSPRO can automatically notify the Stock Controller via e-mail that the event has occurred. The action of e-mailing the Stock Controller takes place within a few seconds of the event occurring.
Field | Description |
---|---|
Edit | |
Add | Select this to add a new event. |
Change | Select this to maintain the currently highlighted event. |
Delete | Select this to delete the currently highlighted event.
If you selected the option: Confirm Deletions, then you are prompted to confirm the deletion of the selected event. |
Functions | |
View Log File | Select this to use the Event Management Log View program to view and/or report on the log file created from transactions generated by the Event Management program. |
When you select the Event Management program, a listview displays the events currently configured.
You use the Add option from the Edit menu to configure a new event.
Field | Description |
---|---|
Event details | |
Name |
Indicate a unique 20-character description for the event. |
Event | |
Select Event |
Indicate the event you want to monitor.
|
Parameter |
Indicate the parameter you want to assign to the event. This field is displayed only for events containing a parameter entry. For example: If you select the event: Supplier balance > parameter then an action would be triggered when the supplier's balance exceeds the amount entered at the parameter field). |
Type |
Indicate the mechanism that you want to activate when the event occurs in SYSPRO. |
Select this to send an e-mail message when the event occurs in SYSPRO (see Email ). |
|
Run a SYSPRO program |
Select this to run a SYSPRO program when the event occurs in SYSPRO Run a SYSPRO program. |
Run any NetExpress program |
Select this to run a NetExpress program when the event occurs in SYSPRO Run any NetExpress program. |
Run an application |
Select this to run an application when the event occurs in SYSPRO Run an application. |
Write to log only |
Select this to only write to the log file when the event occurs in SYSPRO. |
Write to message inbox |
Select this to send a message to a specific operator's inbox when the event occurs in SYSPRO Write to message inbox. The message could be used to notify the operator of a task to be actioned or it could merely be informational. The Message Inbox is accessed from the Main SYSPRO menu by selecting the Message Inbox option from the Window menu. The system can be set to check for messages automatically on startup by selecting the Check for messages option from the Messages tab of the Customize screen (see Messages). |
Description |
Describe the type of event being configured. This description is displayed as a listview column when you select to view the log file. |
Options | |
Write to log |
Select this to record the triggered event in a log file. You can view and report on the log file from within the Event Management Editor by selecting View Log File from the Functions menu. The name of the log file is xADMEVL and is located in your working directory. |
Active |
Select this to specify a range of inclusive dates within which the event must be activated. |
From |
Indicate the earliest date in the range. |
To |
Indicate the latest date in the range. |
Save |
Add the new event to the event management file. The name of the file is xADMEVT and is located in your working directory. |
Check Names |
Verify that the e-mail address of the recipient is valid. This applies only to the E-mail type. |
Cancel |
Ignore any details you entered and to return to the listview. |
This screen is displayed if you selected to send an e-mail message when the event occurs in SYSPRO.
Field | Description | ||||
---|---|---|---|---|---|
Select this to associate an event with the sending of e-mail to selected recipients. This applies only to the E-mail type. |
|||||
To |
You use this field to indicate one or more recipients of the e-mail. Use the semi-colon (;) to separate recipients. |
||||
Subject |
You use this field to indicate the wording that must be displayed in the subject field of the e-mail message.
|
||||
Message |
You use the message area of the e-mail window to optionally indicate the text that you want to send to the recipient (e.g. The stock on hand has fallen to below zero).
|
||||
Notify buyer |
Select this to notify the buyer who placed the purchase order, when the goods arrive. The e-mail address associated with the buyer is added to the e-mail list.
|
||||
Notify user |
Select this to send an email to the requisition user as well as to the recipients listed in the To field. At least one recipient must be listed in the To field. When you select this option, the e-mail defined against the requisition user is used (see User Maintenance), so ensure that this is defined.
|
||||
No default E-mail recipient |
Select this to only send e-mail to the recipients configured within the Conditional E-mail by List function. In this scenario, e-mail is sent only when the defined criteria are matched.
|
||||
Conditional E-mail by list |
Select this to send e-mail to specific recipients based on a conditional expression (see Event Management Mail Selections) that includes the warehouse. For example: The stock controller can be notified when a specific stock code goes negative in a specific warehouse. This function applies only for specific Inventory events. |
This screen is displayed if you selected to run a SYSPRO program when the event occurs in SYSPRO.
Field | Description | ||||
---|---|---|---|---|---|
SYSPRO program |
You use this option to associate the event to the running of a standard SYSPRO program.
|
||||
Program name |
Indicate the program that you want to load when the event occurs. |
||||
Description |
Indicate a description of the program that is being run. This defaults to the description assigned to SYSPRO program. |
This screen is displayed if you selected to run a NetExpress program when the event occurs in SYSPRO.
Field | Description | ||||
---|---|---|---|---|---|
NetExpress program |
Select this to associate the event to the running of a NetExpress program. |
||||
Description |
Optionally indicate a description of the program that is being run. |
||||
Program |
Indicate the NetExpress program (including the full path) that you want to load when the event occurs. The NetExpress program that is executed is written automatically to SYSPRO's Job Logging system.
|
This screen is displayed if you selected to run an application when the event occurs in SYSPRO.
Field | Description |
---|---|
Application |
Select this to associate the event to the running of third party application software. |
Description |
Optionally indicate a description of the application that you want to run. |
Command line |
Indicate the executable file together with parameters that will launch the selected application when the event occurs. To reduce the number of characters used on the command line, you can specify the path to the executable at the Start in field. You can use reserved words in the command line (see Reserved words in the command line). |
Start in |
Indicate the full path to the executable that will launch the designated application software. |
This screen is displayed if you selected to write to the message inbox when the event occurs in SYSPRO.
Field | Description |
---|---|
Message inbox details | |
Subject text |
Enter the message text you want to display in the message inbox. You can use the Explain function from the Select Event function to view the keywords you can use in the subject text field. |
Send to operator |
Enter the operator to whom the message must be sent. The operator code you enter must exist and be valid. |
Program to run |
Enter a program that you want to run from the message inbox. This field is optional. |
Post message with today's date |
If you select this option, then the message is written to the Message Inbox regardless of the number of times the event is activated on the same date. If you do not select this option, then a single message is written to the Message Inbox irrespective of the number of times the event is activated on the same day. |
Prevent duplicate message being displayed |
If you select this option, then duplicate messages are not displayed in the target operator's inbox. Duplicate messages are those where the subject text and the program to run are identical. |
This screen is displayed when you select the Select Event function.
Field | Description | ||||
---|---|---|---|---|---|
AP events | |||||
New supplier added | |||||
Supplier balance > parameter | |||||
AR events | |||||
New customer added | |||||
Customer balance > % of credit limit |
Activation point
You would typically use this trigger to alert you when customers are nearing their credit limit.
|
||||
Customer now within credit limit | |||||
Customer balance > parameter | |||||
Customer placed on hold |
Activation point:
|
||||
Customer released from hold |
Activation point:
|
||||
Asset events |
. |
||||
Minimum book value reached | |||||
Capex budget exceeded on line addition |
Activation point:
|
||||
Capex budget exceeded on line approval |
Activation point:
|
||||
Capex budget exceeded on line spending |
Activation point:
|
||||
Capex spending on line not approved |
Activation point:
|
||||
Capex spending on closed line | |||||
Cash Book events | |||||
Bank balance < parameter | |||||
GL events | |||||
G/L Ytd actual > Ytd budget by % parameter | |||||
Inventory events | |||||
New stock item added | |||||
Stock on hand negative | |||||
Stock less than safety | |||||
Stock less than minimum |
This event is executed only on the first instance that the condition occurs for a specific stock item. The event is not triggered if the stock on hand for the item is already below minimum and a transaction is processed that further reduces the stock on hand. |
||||
Stock above maximum | |||||
Allocation exceeds quantity on hand |
This event is executed only on the first instance that the condition occurs for a specific stock item. Activation points:
|
||||
Allocation + minimum exceeds on hand |
This event is executed only on the first instance that the condition occurs for a specific stock item. Activation points:
|
||||
Goods receipt | |||||
Goods in Transit under receipt | |||||
Goods in Transit over receipt | |||||
Lot quantity on hand falls to zero | |||||
Physical cost change | |||||
Cost modification | |||||
List price or code changed | |||||
PO events | |||||
Requisition routed to another user (req & receipt) |
Activation point:
|
||||
Requisition routed to another user (req only) | This event is essentially the same as the event:
Requisition routed to another user (req &
receipt), except that it is only activated for
Requisitions and not for Purchase Order Receipts. The activation point is therefore:
|
||||
Goods receipt from purchase order |
Activation point:
|
||||
SO events | |||||
Sales order released from credit check | |||||
New sales order fails credit check |
This event is triggered when a sales order causes a customer's credit limit to be exceeded and the order is placed in suspense. Activation points:
|
||||
Credit note issued | |||||
Sales order line into backorder | |||||
Price overridden by operator |
Activation point:
|
||||
Purchase order raised from sales order |
Activation point:
|
||||
Purchase order receipt from sales order |
Activation point:
|
||||
Invoice process failed during document print |
Activation point:
|
||||
BOM events | |||||
ECC status change event | |||||
WIP events | |||||
Job costs exceed expected | |||||
Run hours of operation exceed expected | |||||
Job receipted into stock | |||||
Quotation events | |||||
Quotation ready for printing | |||||
Estimate available for use | |||||
Non-stocked pricing available for use | |||||
System Admin events | |||||
'File in use' message | |||||
Access security breach attempt |
Activation point:
|
||||
AR Business Objects | |||||
New customer added by ARSSCS | |||||
Customer placed on hold by ARSSCS | |||||
Customer released from hold by ARSSCS | |||||
PO Business Objects | |||||
Explain | Select this to view additional information for the highlighted event. | ||||
Select | Select the highlighted event as the event type. | ||||
Close | Select this to return to the previous screen. |
Reserved words must be entered in lowercase, as indicated in the table.
The content of the variable %desc (or %name) varies according to the type of event being triggered. Usually it contains the description of the bank, or stock code, or customer etc. In some cases, however, there is no obvious description and the table below indicates the text that will be used:
|
Field | Description |
---|---|
%key |
This indicates the main key field that caused the event (e.g. stock code). |
%other |
This indicates the secondary or other key that caused the event. In the case of purchase order receipt events it will contain the warehouse code in positions 1-2, the purchase order number in positions 4-9, a hyphen (-) in position 10 and the purchase order line number in positions 11-14). For requisition routing, this variable will contain the user from whom the requisition was routed. For the credit limit event, this variable will contain the following data depending on the program that caused the event to occur:
|
%wh |
This indicates the warehouse (for inventory events) in which the warehouse is used. |
%desc |
This indicates the description of the main key (e.g. stock description). The contents of this field will vary according to the event being triggered. |
%name |
This reserved word is interchangeable with %desc. |
%oper |
This indicates the operator who was running the system at the time the event occurred. |
%prog |
This indicates the name of the program that was running at the time the event occurred (e.g. IMP010 would be inserted if the Inventory Movements program caused the event to occur). |
%prgdesc |
This indicates the description of the program running at the time the event occurred (e.g. Inventory Movements would be inserted if the program IMP010 caused the event to occur). |
%balance |
This indicates the balance of the main key after the event (e.g. if the event is Bank balance < parameter then %balance would contain the balance of the bank after the event has occurred. This reserved word is applicable only to events for which this makes any sense (i.e. the Bank balance event). For the credit limit events, %balance refers to the percentage of the customer's balance versus the credit limit. Therefore, if the balance of the customer (including outstanding order value) after the event, is standing at 56% of the credit limit, then %balance would contain 56. |
%onhand |
This works in a similar way to the %balance reserved word, but applies to stock warehouse events only. Therefore, %onhand will contain the stock on hand after the stock warehouse event has occurred. |
%value |
This indicates the value of the transaction that caused the event (e.g. if event is Bank balance < parameter and the withdrawal value is $1000 then %value would contain 1000). This reserved word is applicable only to events for which this is appropriate. |
%qty |
This indicates the quantity of the transaction that caused the event (e.g. if the stock on hand falls to below safety, then %qty would contain the quantity of the transaction that caused the on hand to fall below safety. This reserved word is applicable only to events for which this is appropriate. |
%coid |
This indicates the company id being currently processed. |
Field | Description |
---|---|
%key |
This indicates the main key field that caused the event (e.g. stock code). |
%other |
This indicates the secondary or other key that caused the event (e.g. warehouse in the case of events relating to the stock warehouse file). |
%desc |
This indicates the description of the main key (e.g. stock description). |
%name |
This reserved word is interchangeable with %desc. |
%oper |
This indicates the operator who was running the system at the time the event occurred. |
%coid |
This indicates the company id being currently processed. |
%log |
This indicates the key to the log record just written (i.e. the application can read directly onto the event log file and retrieve the information required about the event). |
%qty |
This indicates the transaction quantity (inventory-related events). |
%wh |
This indicates the warehouse code (inventory-related events). |
%onhand |
This indicates the quantity on hand balance (inventory-related events). |
Example 1:
The following example describes how you would set up an event to email a specific person if the quantity of stock item A113 in warehouse 'S' falls below the minimum quantity.
From the listview pane of the Event Management program, select Add from the Edit menu. Alternatively, select the Add icon from the toolbar.
Enter a name for the event (for example Stock A113 Below Minimum).
At the Event field, select the option: Stock less than minimum.
At the Type field, select Email.
Optionally enter a description for the event.
At the email Subject field, enter %key below minimum.
In the email body, enter: For warehouse %wh
Select the option: No default Email recipient
Select the function: Conditional Email by List
From the Event Mail Selection Maintenance listview, select Add from the Edit menu. Alternatively, select the Add icon from the toolbar.
Accept the default line number displayed.
At the Expression field, enter %key = "A113" AND %wh = "S"
At the Recipient List field enter the name of the person the email must be sent to when the event occurs.
Select the Save function from the Event Mail Selection Maintenance screen.
Select the Save function from the Add Event screen.
The Office Automation and Messaging module must be installed as part of your registration license before you can use this program (Company Maintenance).
If you intend using the e-mail facility of this program, you must have either Microsoft Exchange or Microsoft Outlook installed on your workstation.
Events of type SYSPRO are only triggered when the specified condition is met from within a SYSPRO program and not when the transaction is processed via e.Net.
For example, a trigger will fire when a sales order is created using the IMP040 program, but the same trigger will not fire when the order is created using the SORTOI business object.
Add an event
From the Event Management program select Add from the Edit menu.
Alternatively, select the Add icon from the toolbar.
Change an event
From the Event Management program select Change from the Edit menu.
Alternatively, select the Change icon from the toolbar.
Delete an event
From the Event Management program select Delete from the Edit menu.
Alternatively, select the Edit icon from the toolbar.
View log file
This task enables you to view and/or report on the log file created from transactions generated by the Event Management program.
From the Event Management program select View Log File from the Functions menu.
The listview pane of the Event Management Log View program is displayed.