Oracle® Insurance Rules Palette
This is a new feature for processing of allocation details in the transaction with the ability to fetch the context variable in the allocation screens and transaction math as a part of configuration. The Plan considered for the prototype is Model prototype plan, and by using the verification screen in the transaction, the prototype generates some warning messages to show how to use context variable in the screen math section. Clients number is used along with Relative GUID and Activity GUID.
PAS user should have access to "Model Prototype Plan". The Plan must have funds attached to it.
This prototype configuration showcases the access to allocation details and activity details in the screen math and regular math sections of configuration.
This configuration showcases the access to allocation details and activity details into screen math and regular math section. The transaction name is AllocationAndActivityDetailInScreenMath under the Model Prototype Plan.
Prototype Configuration
The configuration fetches the Allocation Detail in both the screen math and regular math configuration sections with the help of two math loops: FILLBY-ALLOCATIONFROM and FILLBY-ALLOCATIONTO.
Two warning messages were configured to satisfy the following cases:
The context below describes accessing the activity fields.The configuration will generate a warning message upon OnLoad of this transaction, based on the value of RelatedGUID.
Two different warning messages are configured. If the RelatedGUID is null then a warning message “This is a Natural Activity” will appear. Otherwise, if the RelatedGUID is not null, a warning message “This is an Undo/Redo Activity" will appear.
The RelatedGUID, which is generated when the activity is reprocessed, used in the above context, is retrieved in the GlobalScreenMath section. Like RelatedGUID, ActivityGUID is also retrieved in GlobalScreenMath section, and the system checks if it is empty.
Along with the warning message, an Assign operation is also configured, which will assign the TransactionName retrieved in the GlobalScreenMath section to the activity field TransactionName.
The Warning Message uses substitutions for ClientNumber & ClientName: “The Client $$$ClientNameSMV$$$ has ClientNumber $$$ClientNumberSMV$$$” is shown to the user.
The following activity data is being accessed within the ScreenMath and placed in the associated variable:
• RelatedGUID - RelatedGUIDSMV.
• ActivityGUID - ActivityGUIDSMV.
• TransactionName - TransactionNameSMV.
• ClientNumber - ClientNumberSMV.
• ClientNameSMV - Retrieves ClientName with the help of ClientNumber using SQL.
The context below describes the accessing of the AllocationFields.
As part of the Onsubmit event, the transaction will display a warning that shows the TotalAllocationAmount of the “From” Fund along with the message, “The Total Allocation amount of 'From' Fund is XXX”.
Database Configuration
The following allocation data being accessed within the ScreenMath to produce the variable SumOfFromFundValueSMV is “AllocationAmount.”
The AllocationAmounts of each of the “From” and “To” allocations are summed and assigned to transaction fields. These fields are displayed in the verification screen. The verification screen also displays the total of the “From” allocation from an activity math variable.
The screen math and activity math variables below were created in the math section.
ScreenMath:
• SumOfFromFundValueSMV
• SumOfToFundValueSMV
Activity Math:
• SumOfFromFundValueMV.
The fields that are displayed in these ScreenMath and Activity math variables in the Verification screen are "From AllocationAmount In Screenmath," "To AllocationAmount In Screenmath" and "From AllocationAmount In TransactionMath."
Business Rules:
The ValidateExpressions business rule will check whether the total allocation amount of the “From” fund is equal to the total allocation amount of the “To” fund. If the values are not equal, then a message "Allocation amount of FromFund should be equal to allocation amount of ToFund" will be displayed. Since the OVERRIDE attribute is set to ”Yes,” the user is able to override that error. If the values are equal, then this error message will not be displayed.
The following activity math variables were created to execute this feature rule:
• SumOfFromFundValueMV.
• SumOfToFundValueMV.
Copyright © 2009, 2015, Oracle and/or its affiliates. All rights reserved. Legal Notices