Suppression can apply at one of four entity levels - person, account, tax role or obligation. The base package provides common logic to determine if suppression is in effect for an entity. This logic considers all suppression records for the entity and its higher level entities.
Suppression scope can be summarized as follows:
A person-level suppression object will also cause suppression on all the accounts for which that person has financially responsibility, all tax roles for those accounts and all obligations for those accounts.
An account-level suppression object will also cause suppression on all tax roles for that account and all obligations for that account.
A tax role-level suppression object will also cause suppression on all obligations for that tax role.
An obligation-level suppression object will cause suppression only on that obligation.
It is possible for a given entity, such as an obligation, to be affected by suppressions with differing periods or at differing levels. For example, a suppression record may be manually added for an account with one or more obligations. A subsequent bankruptcy case may be created that includes one of those account's obligations. The system assumes that both suppressions are in effect for the obligation and that the period of suppression starts from the start of the earlier suppression record (for the account) until the later of the two release dates.
Note that the release date of a suppression event is the date on which the suppression ceases to have effect. Processes that are put on hold due to suppression will restart processing on the release date - for example, overdue events will be triggered on the day of release. For P&I calculations, P&I will be suppressed from the start date of the suppression until the day prior to the release date, inclusive.
Refer to the base business service C1-GetEffectiveSuppressions for more details on the common logic used to retrieve suppression details and periods.
Copyright © 2011, Oracle and/or its affiliates. All rights reserved.