Job Queues
General
- Can be defined for reports and codeunits
- The category code is used for filtering and for grouping tasks by schedule
- Further information:
- The “Maximum No. of Attempts to Run” is also important for notifications in case of error: a notification is only sent after all attempts have been carried out
Job Queue Entry Card, “Notifications” Tab
Notifications for the failure and/or success of a task can be set up here. For important job queue entries, notification on failure is recommended.
Setting up the notification code is described on the Notifications (Fashion) page. In addition, a scheduler for the error notification must be set up as a job queue entry:
Special Job Queue Entry for Sending Error Notifications
To send error notifications, a job queue entry must be created for CU 5232538 „BET FN Scheduler Error MGT“.
Job Queue Log Entries
The log entries of a job queue entry can be used to trace, among other things:
- whether the task completed without error
- when the task was last run
- how long the task took to run
- whether an error message and/or a success message was sent
Overview of Important Job Queues
Some commonly used job queues are listed here (not an exhaustive list):
General
- Job queue for sending error notifications
- Job queue for the “Item Correction” function (see Master Data, Item Correction)
EDI
- Job queue for EDI processing
Finance
- Job queue for warehouse posting invoice setup prices: Report 795
- Job queue for batch-posting purchase invoices: Report 497 (see Purchase Setup, automated posting of purchase invoices)
BE-terna Commerce Interface (Webshop)
- Job queue for webshop order import: CU 5594967 BET ECOM Doc. Import Mgt
- Job queue for new-contact import from the webshop: CU 5594968 BET ECOM WS Contact Import Mgt
- Job queue for sending webshop price updates: CU 5594970 BET ECOM WS Daily Sales Pr Mgt