Event Management

Add a new event.

Delete the currently highlighted event.

If you selected the Confirm Deletions option from the Options menu, then you are prompted to confirm the deletion of the selected event.

Indicates the event that you want to monitor.

The corresponding Select Event function will open a list of available events (displayed by module) from which you can select your required event.

Indicate the action that you want invoked when the event occurs in SYSPRO. These actions take place within a few seconds of an event occurring.

Select this to specify a range of dates within which the event must be activated.

The From and To dates specify a date range within which the event can be fired.

These dates are inclusive.

Verify that the e-mail addresses of the recipients are valid. This applies only to the E-mail type action.

You would typically use this trigger to alert you when customers are nearing their credit limit.

Activation Point: When the customer's balances are greater than (the customer's credit limit multiplied by the parameter value divided by 100).

For example: Parameter value entered = 90. Customer's credit limit = 10 000. The trigger is then activated when the customer's balance exceeds 9 000(i.e. 10 000 x 90/100).

If you are using master/sub accounts, then the credit check is performed against the customer (master or sub account) to which invoices are linked.

This event is only fired when the customer's credit limit is exceeded the first time.

Activation point: When the on-hold status against a customer is lifted.

Activation point: When a capex requisition line is approved and the value of the requisition line causes the budget value of the capex item to be exceeded.

Activation point: When using the Purchase Order Receipts or Part Billings program to process a second or subsequent receipt for a capex requisition line and the requisition line is still in a status of Closed from the previous receipt.

This event is executed only on the first instance that the condition occurs for a specific stock item.

Activation points:

• Sales Order Entry

  When the warehouse is being updated from a new line or from a changed line.

• SO Single Level BOM

  When updating the warehouse on validating an optional line and when allocating stock.

• Sales Order Import

  When the warehouse is updated as the lines are being checked.

• Order Purge

  When updating the warehouse after allocating a scheduled order line.

• Import Back Order Releases

  When the warehouse is updated from an accepted line and when a kit component is updated.

• Blanket SO Review & Confirmation

  When the warehouse is updated because of added lines.

Activation points:

• Purchase Order Receipts

  When a purchase order line linked to a requisition is receipted.

• Requisition Entry Maintenance

  When a requisition line is routed to another user.

  Within the Requisition Entry Maintenance program you can enable the preference: Trigger event once only when routing consecutive requisition lines to activate this event for each requisition routed to another user, regardless of the number of lines held against the requisition.

Activation point: When receipting a purchase order item.

When using this event to trigger an email, the keywords %wh and %other are interchangeable within the email body.

If, however, you are defining a conditional email, then the %wh keyword must be used to make the mail conditional on the actual warehouse.

This is because the %other keyword can contain up to 30 characters and will always evaluate the condition on the full 30-characters of the variable.

To make the mail conditional on the stock code, use the %key keyword.

Activation point: When the price (or price code) is overridden at the time of adding a line in Sales Order Entry.

The event is not activated if maintaining an existing line for which the price has already been overridden and the price is changed again. However, the event is activated if the price code is changed.

Activation point: When receipting a purchase order line that is linked to a sales order line.

If an item is receipted into inspection, then the event is activated only when the item is accepted.

This indicates the main key field that caused the event (e.g. stock code).

This indicates the warehouse (for inventory events) in which the warehouse is used.

This reserved word is interchangeable with %desc.

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).

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.

This indicates the value of the transaction that caused the event (e.g. if the 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.

This indicates the main key field that caused the event (e.g. stock code).

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.

This indicates the operator who performed the transaction that caused the event/trigger to be invoked.

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).

This indicates the warehouse code (applicable to Inventory-related events).