Generating a BOD as a Background Task
In this application, a BOD is generated automatically by the appropriate application events - for example, a change in status or receipt of an item - as defined in the Replication Document forms. In certain cases, a BOD must also be generated by a scheduled event rather than an application event.
For example, ProductionOrder BOD generation is triggered by a change of status, but is not triggered by changes in the production schedule. Generating a ProductionOrder BOD each time a date change event occurred would generate so many BODs during a single day that it could overwhelm the system. Thus, using an application event to trigger ProductionOrder BODs on schedule changes is not a good choice. Instead, use a scheduled event that runs as a background task. The generated BOD includes all schedule changes since the last time the BOD generation was run.
- In the
Replication Document Outbound Cross References
form, set up a definition for the BOD that requires a scheduled event.
- In the Replication Categories form, create a new category that contains the method you created in Step 1, or use the existing ESB category.
- In the
Replication Document Manual Request Utility,
create a background task that will generate the selected BODs:
The background task selects the outbound cross reference definition and generates the BOD at the scheduled time. Settings and filters used in the outbound cross reference definition are not saved within the background task, so that you can adjust them and use them for the next scheduled run.