To improve efficiency and accuracy, you can set up your system to automate activities when specific trigger parameters are met. For example set up a trigger, so the system sends an e-mail message to your customer when an order is placed through the web. You can also set up these activity triggers to respect the e-mail address of the contact attached to the order. To do this, set the Validate Name In "Ordered By" Field Against Customer Contact control maintenance record.
From the Files menu, select Customer to display the Customer Maintenance screen or Vendor to display the Vendor Maintenance screen.
Enter the customer or vendor's name to display the entity record.
In the Inherit field, enter Y if the entity can inherit triggers from another entity in the corporate hierarchy, otherwise, enter N. This setting overrides the setting in the Activity Trigger Default Inherit control maintenance record.
Use the Add'l Info/Add'l Data hot key, then use the Activity Trigger hot key to display the Activity Trigger Maintenance screen.
The system populates the Customer/Vendor field with the entity name.
In the Trigger Description field, enter one of the following triggers:
This item... |
Triggers an event ... |
Backorder Acknowledgement |
when an order is closed from an RF branch. A backorder acknowledgement is faxed or printed depending on the customer setup. A backorder acknowledgement is a ship ticket that lists only backordered items. |
Batch Invs in Lieu of Prt |
when the batch invoice printing program is run. Instead of printing the invoices, the program e-mails them to the customer. The Eclipse Outbound E-mail companion product is required. |
BC-XML Submit Order |
when the system receives an order in XML format from the Business Connect XML companion product. |
Calling Queue - All Orders |
when the Calling Queue - All Orders Report runs, the system checks for customers with the activity trigger set and pulls all the orders in the Customer Calling Queue for that customer that have a Call status and are open as of the run date. These orders include backorders, new orders not yet available, and available orders as of the run date. Note: To set up the report to run when you want and in the format you want, see Sending Customers Calling Queue Data. |
Calling Queue - Available Orders |
when the Calling Queue - Available Orders Report runs, the system checks for customers with the activity trigger set and pulls all the orders in the Customer Calling Queue for that customer that have a Call status and are complete (available) as of the run date. Note: To set up the report to run when you want and in the format you want, see Sending Customers Calling Queue Data. |
EDI Order Entry |
when an Eclipse Electronic Data Interchange (EDI) order is received. This option requires the Eclipse EDI companion product. |
EFT Remittance Advice |
after a successful electronic funds transmission. This trigger is available in Vendor Maintenance only. |
E-mail Stmts in lieu of Prt |
when the batch statement printing program is run. Instead of printing the statements, the program will send them to the customer using e-mail. |
E-mail Stmt-Invs lieu of Prt |
when the batch statement program is run. Instead of printing the statements and invoices, the program sends them to the customer using e-mail. This trigger works only if you set the Also Print Invoices field on the Print Statements screen (A/R > Print Statements) to anything but No. If you set the print statements program to also print invoices and have this trigger set for the customer, the system sends both the statement and the invoice to the customer through e-mail. The Eclipse Outbound E-mail companion product is required. |
Invoice Order |
when an order is invoiced. |
Invoice Print |
when an invoice is printed. |
Manifest Lock |
when a manifest is locked on the manifest queue. |
when a new direct order is completed. Use this trigger to route sales orders to another vendor, or to source sales orders through another branch. This trigger is available in Vendor Maintenance only. This option requires the Eclipse Outbound E-mail companion product. |
|
New Purchase Order |
when exiting a manually created purchase order. This trigger is available in Vendor Maintenance only. This option requires the Eclipse Outbound E-mail companion product. |
New Purchase Order Bid |
upon exiting a purchase order bid. This trigger is available in Vendor Maintenance only. |
New Sales Order |
when a new sales order is completed. |
New Sales Order Bid |
upon exiting a sales order bid. |
Order in Calling Queue |
when the Order in Calling Queue Notification runs, the system checks for customers with the activity trigger set, and pulls copies of the sales acknowledgements for all the orders in the Customer Calling Queue that meet the criteria you have set up in the trigger. For example, you can set up the system to send a notification when orders with a specific ship via are added to the queue. The system sends the sales acknowledgement per the information set up in the customer's activity trigger. Set up your preferences as follow:
Note: To setup how you want the information sent to you for this trigger, see the Running the Order In Calling Queue Notification Report. |
Order in Trouble |
when the Trouble Order Notify process runs, the system checks for orders for this customer that have a ship date that has slips and sends an updated sales document by e-mail or by fax. |
when the number of days an invoice is overdue is reached. This number is determined by the number entered using the Trig Props hot key. This activity trigger notifies the system to send an e-mail notification once per generation. Multi-generation orders get a notification per generation. If a process is re-run and an e-mail has already been sent for a generation, the system does not send a second e-mail. To enable this trigger, schedule the Overdue Invoice Notification utility in Accounts Receivable (AR). Note: To set triggers for additional numbers of late days, assign the number of days overdue to additional triggers. |
|
Pick Ticket Print |
when a pick ticket prints. This option requires the Eclipse Outbound Email companion product. |
PO Ack Received on Direct |
when an 855 purchase order acknowledgement is received in response to a direct order. This option requires the Eclipse Outbound E-mail and the EDI companion products. |
RDC Order Entry |
after an order has been created through Remote Data Collection (RDC). This option requires the Palm SFA companion product. |
Received Purchase Order |
when a purchase order is received. This trigger is available in Vendor Maintenance only. |
RF Order Close |
after an entire order has been picked through RF and is ready to ship. This option requires the Eclipse RF Sales Order Entry companion product. |
Shipment Notification |
when StarShip sends shipping information back to the system. This option requires the Eclipse Electronic Shipping with StarShip companion product. |
Ship Ticket Print |
when a ship ticket prints. |
Transfer Received |
when a transfer is received. |
Web Integration Submit Order |
when an order is submitted through Web Order Entry. This option requires the Eclipse Web Commerce companion product. |
From the Activity Description field, enter one of the following activities to occur as a result of the event selected in the Trigger Description field. Selections vary depending on your entry in the Trigger Description field:
Activity |
Description |
B2B Adv Ship Notice |
Sends an advanced shipping notice in XML format by way of B2B Commerce or Business Connect XML. |
B2B Purchasing Document |
Sends a purchase order in XML format by way of B2B Commerce or Business Connect XML. |
B2B Sales Doc |
Sends a sales document in XML format by way of B2B Commerce or Business Connect XML. |
Create ASN and Product Labels |
Creates and prints advanced shipment notification product labels for each item on an order. |
EDI Adv Shipping Notification |
Sends an EDI 856 advanced shipping notice. |
EDI Doc for Remit Advice |
Generates an EDI 820 document on the EDI outgoing status queue. |
EDI Purchasing Document |
Generates an EDI 850 document on the EDI outgoing status queue. |
EDI Sales Document |
Sends an e-mail containing a message and the EDI sales document. |
EDI Single Adv Shipping Not |
Generates an EDI document for each stop on a manifest. |
E-mail Message |
Sends an e-mail containing only a message. |
E-mails a purchasing document. |
|
E-mail Purchasing Doc HTML |
E-mails a purchasing document in HTML format. |
E-mail Remittance Advice |
Sends email with remittance advice. |
E-mail Remittance Advice HTML |
Sends email of remittance advice in HTML format. |
E-Mail Sales Doc HTML |
Sends an e-mail containing a message and the sales document in HTML format. |
Sends an e-mail containing a message and the sales document. |
|
E-mail Shipment Tracking Info |
E-mails order shipment information, such as order shipment numbers and ship vias. |
E-mail Statement |
Sends an e-mail containing a message and the statement associated with the trigger event. |
E-mail Statement HTML |
Sends an e-mail in HTML format. |
Fax Purchasing Doc |
Faxes a purchasing document. |
Fax Remittance Advice |
Sends fax with remittance advice. |
Sends a message and sales document by fax. |
|
Fax SOE Report |
Faxes a Sales Order Entry report. |
FTP Tibersoft Adv Ship Notice |
Creates and sends the advanced shipment header information to Tibersoft by FTP (file transfer protocol). |
FTP Tradepowers PO Ack |
Adds order to a Tradepowers purchase order acknowledgement that is sent by FTP at a future date. |
New Sales Order |
Creates a new sales order. |
Single ASN and Product Labels |
Creates and prints advanced shipping notification product labels for each stop on a manifest. |
The Typ field displays the type of activity assigned.
In the F field, enter one of the following options to determine how the system performs the activity when the event that triggers the activity occurs as a result of a program running in the system's foreground:
P The system performs the process.
C The system prompts the user for confirmation before performing the activity.
X The system does not perform the activity.
Q The system transfers the activity to a queue, from which it will be performed after being reviewed. This option is currently not implemented.
In the B (background) field, enter one of the following options to determine how the system responds to the trigger as a result of a program being scheduled to run in the Phantom processor in the system's background:
P Performs the activity.
X Does not perform the activity.
Q Transfers the activity to a queue from which it will be performed after being reviewed. This option is currently not implemented.
In the D field, enter an asterisk (*) to disable this activity trigger for this customer or vendor. This activity will not take place for the entity, even if inherited triggers in branches above it in the hierarchy would have executed that activity. Once an activity is disabled, it may not be executed by any inherited triggers.
For example, Email Sales Doc HTML on a new order is enabled at the ship-to level, disabled at the bill-to level, and enabled at the branch level. The ship-to executes the e-mail, the bill-to will not because it is flagged as disabled. The branch will not execute the e-mail because the lower, bill-to, entity has disabled it.
Use the following hot keys, as needed:
Hot Key |
Description |
Trig Props |
Displays a screen to set specific criteria for the trigger selected in the Trigger Description field. The screen that displays depends on your trigger selection. For more information on these options, see the following: |
Activity Props |
Displays the a screen to set specific criteria for the activity selected in the Activity Description field. The screen that displays depends on your activity selection. For more information on these options, see the following: |
Dollar Entity Triggers |
This hot key is active if you assign triggers to a ship-to only customer. Use this hot key to duplicate these triggers for the bill-to customer. |
Press Esc to save the trigger and activity settings.
See Also:
Overriding Activities Assigned to Triggers