Configuration Controls Obligation Management

The processing described in the previous sections is carried out by a number of algorithms, which in turn invoke algorithms in other plug-in spots. The key elements are as follows:

A Business Object Post Processing algorithm is responsible for the logic that cancels or adjusts any obligations whose periods are affected by changes to the tax role start date, end date or effective calendars.
A second Business Object Post Processing algorithm is responsible for the logic that creates obligations to bring the tax role's obligations up to date for the current business date. This algorithm caters for the processing required when a tax role is added for the first time and also for the processing required to recreate obligations for a new filing frequency, in circumstances where a change to the tax role effective calendar has been back dated. This algorithm should be configured to execute after the algorithm that cancels unwanted obligations, described above.
An Obligation Type - Generate Obligations algorithm is required for each obligation type linked to a tax type that is configured to maintain obligations. The base post processing algorithm that creates current and historic obligations for a tax role will invoke this plug in for each obligation type associated with the tax role's tax type. A base algorithm is supplied to generated filing period obligations based on the associated tax role's effective filing calendars.
A Business Object Status Monitor algorithm is responsible for the logic that periodically creates the next obligation for the tax role when the prior obligation end date is reached. It should be plugged in on the Active state of the tax role business object. The base tax role monitor algorithm invokes the same logic as the post processing algorithm that creates obligations real time. It therefore also relies on the Obligation Type - Generate Obligations plug-in spot.
A second Business Object Status Monitor algorithm is responsible for the logic that transitions a tax role to the Expired state when the tax role end date is reached. It should be plugged in on the Active state of the tax role business object.
A Business Object Status Enter algorithm is responsible for the logic that cancels all obligations for a tax role when the tax role is canceled. It should be plugged in on the Canceled state of the tax role business object.
Various Business Object Validation algorithms are supplied to enforce rules related to obligation maintenance that are governed by tax type controls. Refer to Configuring Tax Types for more information on tax role related configuration and other tax role validations controlled by tax type settings.

Refer to the base Variable Calendar Tax Role business object for an example of how to configure the base algorithms that are supplied for the business object plug-in spots described above.

Refer to Setting Up Obligation Types for more information on the Generate Obligations plug-in spot and the available algorithms.