Administrators can use the Background Scheduler Dashboard to schedule background activities. The browser displays each of the background processes currently scheduled, including the process code and description, run frequency, next scheduled run date and time, last run date and time and result. You can modify the schedule for a background process using this screen.
The Background Scheduler Dashboard does not allow running a process unscheduled, changes to process execution, or disabling of the process which result in company overrides. Changes to a system-wide process require updating in the Meta>System Background Process FM program.
You can right-click on a line in the browser and display options for background processes.
Options for system-wide processes include:
The Disable for This Company option is available for non system-wide processes.
For a process that is system wide, the “Disable for This Company” option will be excluded from the right click menu.
For continuous system-wide processes, such as A- API Polling Directory Handler, you can select the "Disable for This System" option. Before disabling continuous system-wide background process A, you must ensure the API Polling directories/locations are empty and user logins are restricted in User Management F/M (SMF410) until this process is enabled again.
The Disable Background Process window displays the Process Code and Description to allow you to verify proper process is being edited. Specify the Disable Until date and Time for the background process to be enabled again.
To disable continuous system-wide background process, A- API Polling Directory Handler, two confirmation check boxes are also required before you can proceed with disabling:
• User Management F/M has been used to restrict user logins until this process is enabled again.
• API Polling directories/locations are empty.
These background processes are available:
API Polling Directory Handler (A), which is used to process API Polling directories/locations through to completion.
System Alert Miner (A1), which is used to process alert to facilitate any actions needed to feed into the Buyers Control Center and Exception Control Center.
Publish XML to destinations (I1-BKC201), which is used to publish XML content, both internally and for Infor OS.
Infor OS Database Output Writer (I2-BKC202), which is used to deliver the XML in the SMXOUT file to Infor OS.
Infor OS Database Inbox Handler (I3-BKC203), which is used to retrieve XML from the Infor OS inbox and deliver them to the polling directory.
Infor OS Database Inbox Cleaner (I4-BKC204), which is used to remove processed XML records from the Infor OS inbox and outbox.
Replenishment Calculations (R1-BKC600), which is used to process replenishment routines for usage rollup, warehouse rank, and warehouse item controls.
Replenishment Calculations (R2-BKC601), which is used to process replenishment routines for warehouse rank and warehouse item controls.
Replenishment Calculations (R3-BKC603), which is used to process replenishment routines for warehouse item controls only and auto-calculations in the Buyers Control Center (POE400).
Replenishment Calculations (R4-BKC604), which is used to process replenishment routines for seasonality analysis.
Usage Review and Update (R5-BKC606), which is used to process replenishment routines for usage.
Replenishment Calculations (R6-BKC607), which is used to process replenishment routines for auto-calculations in the Buyers Control Center (POE400).
System Clean Up (S1-BKC605), which is used to remove closed alerts and background processing history in the FACTS system.
Rebuild Sort Files (S2 – BKC608), which is used to rebuild the sort files in place, eliminating the need to lock the source files during a rebuild. S2 handles AP, AR, MC, PO, IC, SO and RM sort files. The default is to run this monthly on the 15th of the month, at 1AM.
System Data Updater (S3 – BKC609), which is used to make various direct updates to the FACTS data. The program updates the status of expired quotes once they are expired. By default, S3 is run at daily 12:30 AM.
Background Process (S4 – BKC610), which is used to notify the user when a service hold alert action or service hold release alert action is issued. The alert is raised, and users are directed to Order Review (SOE230) based on the type of alert being responded to. These alert types are available: Hold Status = N – Documents Not on Hold if alert is a release alert, Hold Status = H – All Documents On Hold if alert is a hold alert.
Jobstreams (BKC611) background process which is used to spawn unique and individual background processes for each job stream that is scheduled to run. The program raises the JOBSTREAM alert when it is run.
Click Detail to view the background process code and description, program that generated the alert, the last scheduled and non-scheduled run times, standard run method and retry time interval, as well as indicators for system Wide processes.
Click Run Unscheduled to start background processing at non-scheduled times. Note that you cannot run an unscheduled process execution for system-wide processes.
Click Show History to access the Background Processor Results screen to review results file details for the alert highlighted in the browser. For alerts, the display includes the background alert process code and description, start and completion dates/times for the alert, the alert result status, error code, run time and user code that generated the alert. For replenishment calculations and system clean up, the display includes the process code and description, program number, last scheduled and non-scheduled run date and time and the run frequency. For Job Streams, all background job stream process results in order, job stream name, then within the name by date recent-to-oldest. Click Jobstreams to display all background process job stream results in the JobStreams window.
See also
Changing the schedule for a background process