Publishing Incremental Messages of Current Effective Data

This section discusses how to:

  • Create service operations for publishing incremental messages of current effective data.

  • Create subscription processes that open the generic effective-dated delay function.

For incremental messages, use subscription PeopleCode to copy current effective rows to a current incremental message for immediate publication, to strip out historic data, and to store future effective rows in a delay table. A regularly scheduled Application Engine program uses the delay table data as a trigger to publish future data when that data becomes effective.

You must create a service operation and associate an incremental message definition with it.

Note: The name of the service operation must end with the suffix _EFF to be effective dated.

The incremental message definition must contain the necessary records in the publishing system. Specify the message version first, otherwise you can’t add the tables that compose the message. When the system requests a message channel, enter the queue definition that you previously selected.

The PeopleSoft system includes a function called PROCESS_EFFDT_MSG. This function reads through an incremental message and processes the past, current, future, or non-effective-dated information. PROCESS_EFFDT_MSG resides within the record FUNCLIB_EOEIP, in the EFFDT_MSG_PC field.

To create a subscription process that opens the generic effective-dated Delay function:

  1. Open the Process_Effdt_Msg generic function stored in record FUNCLIB_EOEIP.

  2. Pass it the name of the current effective-dated incremental message.

  3. Indicate whether only rows with Active effective status should be selected as the current effective-dated rows.

    If the &ACTIVE_EFFSTATUS parameter passed in is set to False, the current effective-dated row (whether active or inactive) is selected.

  4. Pass the parameter set to True if only active effective-dated rows should be sent to the other system.

    Note: The standard setting for the &ACTIVE_EFFSTATUS parameter is False.