Handling of future events by PeopleSoft Adapter
Vinod_Valecha 270002HC72 Visits (1442)
Events having a timestamp of the future, i.e. timestamp greater than that of the system time are called as future events. Generally Adapters have a property called as FilterFutureEvents; this property is used by the adapter to control the processing of future events. If the property is set to true, Adapter will not poll the future events from the event table and if the property is set to false, Adapter will poll the future events as normal events. However in case of PeopleSoft Adapter this behavior does not apply due to a limitation from the PeopleSoft Enterprise Server end. This article will talk explain why this behavior does not apply to PeopleSoft Adapter and how PeopleSoft Adapter can handle the future events.
PeopleSoft has a limit of 300 records that can be retrieved
in any query. The issue is if the event store has all future dated events, and
you do not want to process future dated events, the Adapter will not have a way
to query based on the date for current or past set of events. This was the limitation
of the FilterFutureEvent Activation spec property. In order to overcome this
problem, a new event status - 99 is introduced. Adapter uses special handling
for events that have event status (99) to indicate that those events will occur
in the future.
During a poll cycle, when the Adapter retrieves events with
a future status, it compares the system time with the time stamp on each event.
If the timestamp on the event is earlier than, or equal to the system time, the
Adapter processes the event and changes the event status to Ready-for-Poll (0).
However if the event timestamp is later than the system time, the Adapter does
not process such events, and these events remain in the event table with their
status as 99.
Below Table shows all the events status and their
If you want the Adapter to process events with a future
status in the present time, use the function IBM_PUBLISH_EVENT instead of
Thus the processing of future events is governed by the future event status (99) and not by the FilterFutureEvent Activation specification property.