You are here: Global Explorer Folders > System Rules > Overview of System Rules

 

Overview of System Rules

System rules are used to control processing in OIPA. System rules exist as global rules but can be overridden to meet the needs of individual plans. Plan overrides are on both the Global and Main Explorer. Company overrides are only accessable via the Global Explorer pane.  

 

System rules are configured using the XML Source pane. Visual editing is not available for these rules at this time. An explanation of each rule is provided below.  

 

Please see the XML Configuration Guide topic in this help system for a list of all elements, attributes and values needed for System rule configuration. View Business Rules | System Rules. 

 

System Rules

AutomaticPolicyNumber:  This business rule is a system rule that is located in the Global Explorer tab in the Business Rules | System folder. This business rule generates the policy number when a new policy is created.  

 

AutoProcess: This business rule determines whether activities should process as soon as they are added or when specifically executed. If set to Yes, the AutoProcess button is checked on the Activity screen. 

 

CalculateNetAssetValues: This business rule calculates net asset values. It calculates the Bid and Offer price based upon the Bare price and returns the values. Refer to the Calculate Net Asset Values section for additional details.   

 

ChartofAccountsCriteria: This business rule is used to filter or pinpoint the account/account entry details where the accounting should be performed, since a transaction can have more than one account and account entry details. Multiple suspense accounts can also exist, which in turn can have multiple account entry details. Using this business rule, criteria information for each (dynamic) field on the ChartOfAccountsScreen business rule can be defined. For additional information on the configuration of this rule, refer to Steps to Set-up CoA Criteria.     

 

ChartofAccountsResults: This business rule is used to write results to the AsAccountingDetailField table. This additional information is client specific and is used for various accounting purposes. For additional information on the configuration of this rule, refer to Steps to Set-up CoA Results.  

 

DataDictionaryEnforcement: This business rule can force users to use the Data Dictionary. 

 

DisbursementNumber: This business rule is used to configure the disbursement number format and sequence. 

 

EligibleSegmentNamesByPolicyStatus: This business rule is used to make segments selectively available to policies based on the policy status. If a particular policy status is included in the rule only the segment names referenced are available for entry for that policy status. If a policy status is not included in this business rule then all of the plan's segments are available.  

 

GainLossCalculation: Gain/Loss is the gain or loss incurred by a company when a financial activity buys and/or sells variable fund units. This business rule determines whether or not the system should calculate Gain/Loss for the back-dated transactions. For example, if a transaction processed on a date that is a few days after the effective date of the transaction, the difference in price would be calculated as a gain or loss to the company.  

 

There are two columns in AsValuation table that are used to store Gain/Loss information.

 

InterestRateCalculation: This business rule defines the type of interest calculation as well as the specific details of the calculation for fixed funds. Methods of interest rate calculation can be assigned to fixed funds using this rule. In most cases, this rule is overridden on a specific fund level.    

 

PoinInTimeValuation: This business rule can be configured to value the policy back to the last valued date rather than the start of the policy. 

 

PrecisionValues: This business rule is configured to control the display of unit values. 

 

TransactionTimes:  The TransactionTimes business rule controls how an activity behaves based on the time of day it is processed. The rule is attached to transactions and any portion of the rule may be configured as a CopyBook overridden at the Company or Plan levels. TransactionTimes also exists as a System Rule at the Global, Company, and Plan level.

 

TransactionTimes provides two primary elements for controlling whether or not a transaction may process when added or updated: UpdateDate and Allow. Both elements have a common optional attribute called MESSAGE that displays a configured message if any of the validation criteria fail for the primary element. If the value of the message attribute is equal to an entry found on the translation table, the localized (translated) version of the message is displayed to the user; otherwise, the literal value of the message attribute is displayed. If no message attribute exists, then a system message displays a default error message: Screen alert message is not defined. Unless otherwise indicated, the message appears at the top of the Activity Detail screen. To control the messages that display, the system processes in the order UpdateDate and Allow. Failure alert messages are displayed in the order that the associated validations are processed.        

 

The TYPE attribute for the Allow and UpdateDate elements determines when the associated validation is applied based on the screen action being performed.

 

  • Only one Allow element and one UpdateDate may be added for each action type attribute.    

    •  

    Security group Override buttons for the Allow and UpdateDate elements determine which user security groups are exempt from processing the validation. Override buttons are available for Add, Delete, Process, Reverse, and Update. The system checks permissions for the current user’s security group and the list. If the group has the proper override permission checked, then the timing validation is not executed. 

     

    Override Buttons in Transaction Security

    Override Buttons in Transaction Security

     

    The UpdateDate element always targets the EffectiveDate field on the activity. The VALUE attribute identifies the source date value. The source date is always derived from the system date record for the Plan’s MarketMaker calendar. Custom values are not supported. The available date values are:      

     

    Another attribute on UpdateDate is AUTO, which allows a value of Yes or No (the default being No). If the attribute is set to Yes and the validation fails, the failure alert message is displayed and the effective date is changed to the VALUE attribute’s date reference. Clicking OK again on the activity’s detail screen saves the activity and closes the detail screen if there are no alert messages from other timing validations. If the AUTO attribute value is set to No and the validation fails, the failure alert message displays as a confirmation with an OK and Cancel option. Selecting the confirmation’s OK sets the effective date to the VALUE attribute’s date and closes the alert message. If there are no more alert messages, the system saves the activity and closes the activity detail screen. Selecting the confirmation’s Cancel closes the alert message and if there are no more alert messages, returns to the Activity Detail screen for more editing without changing the effective date.      

     

    The Allow element controls whether or not the activity can be saved based on the time date validation criteria. If all the criteria are true, the activity is saved. 

     

    UnitValuePrecision: This rule allows the configuror to set the number of digits to display after the decimal point. It can be used to calculate the units precision at accumulation and benefit levels by attaching this rule to transactions that affect benefit. These values are ultimately stored as units in AsValuation and AsBenefitSplit tables. If this business rule is not configured, the system reverts to the default setting, which is to display ten digits after the decimal point.     

     

    ValuationDetails: This rule allows the configuror to set the proper rounding in valuation calculations for deposits.  

     

    WriteValuationElements: This business rule limits the amount of valuation information that is written. Existing valuation fields can be written to the system and are divided into sections: Policy, Fund, Deposit, and PolicyValues. Inside of these sections the available elements are from a set list. The only exception is the Policy Values section, which can be configured to access any variables from the Policy Values business rule. CopyBooks may be used in this rule. The rule must be overridden by Plan or Transaction.     

     

    Copyright © 2009, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices