Oracle® Insurance Rules Palette
The MaintainSuspense business rule supports the following activity features (Plan and Policy levels):
This configuration document deals with items (1) and (2): ability to update one or multiple StatusCode and/or EffectiveToDate Suspense record fields, within multiple (or single) Suspense records.
Two transactions are configured to test CopyToSuspenseFields feature: Policy level ”r;SuspenseCopyTo4945”, and Plan level ”r;SuspenseCopyToPlan4945” (configuration files attached to the JIRA are ”r;SuspenseCopyTo”, and ”r;SuspenseCopyToPlan”, respectively). Although there are minor configuration differences, both transactions perform essentially the same task: gather Suspense Record GUIDs, and then pass new StatusCode and EffectiveToDate values to the corresponding Suspense records. The following three MathVariables are contained within each of the two transactions:
A suspense record with a StatusCode of 05 ("MakeUp") must exist in order for SuspenseCollection3 to process successfully.
Copyright © 2009, 2015, Oracle and/or its affiliates. All rights reserved. Legal Notices