Filter Conditions for BODs

Dependent applications such as Infor EAM require different information to be supplied at different times, based on what the application needs to perform or monitor. Create a filter for the BOD on the Replication Document Outbound Cross References form to supply only the needed information. When you create a filter, consider the application-generated events that trigger a BOD.

For example, a ProductionOrder BOD is automatically generated when a job is created, when a status changes, or when a quantity changes while the job is in "released" status.

A dependent application might not require a production forecast over the next year. External application-dependent conditions such as this can significantly affect the filtering. If the BOD supports several external dependent applications, you can create several different outbound cross reference definitions with application-specific filters.

For example, to support an application reporting on work in process, you could set up the ProductionOrder BOD with a filter to show released jobs and a schedule to generate the BOD once a month.

Filters are based on the Data Key Source that supplies the Key Column List. You can change the key source to a view or to a table that supplies the required Key Column List elements. This allows you to create a complex relation and to filter out other elements based on the view or table, and not be restricted by the current view or table.

For example, the key source for the ProductionOrder BOD is the ESBProductionOrderView.

If filters are based on conditional data that can change over time, and the data changes outside of that filter range, the information will never be updated when that filter changes. This is particular to dates.

To address this condition, the published_start_date field was added to the job_sch table to indicate the last start date used in the ProductionOrder BOD. In the ESBProductionOrderView the field is LastStartDate.

Filters are cumulative in the form of Line 1 AND Line 2.