Understand Approval Levels in Tolerance Related FAH Edit Tests

Roughly half of Control Center's edit tests have dynamic components, or tolerances, that the system applies when it triggers the test. Tolerance related edit test rules can have many rows with more complex rules. You can alter tolerances in the test rule editor. Edit test rules for tolerated related edit test allow you to identify approval levels needed for approval, along with multiple tolerances, if applicable.

For tolerance-related edit tests, you may have two, three, or four role levels with different tolerances assigned. For these tests, you identify the highest role level that breaks tolerance. The system uses this information to determine which level of user approval can clear a raised edit.

If you use a fund approval hierarchy, you must specify tolerance values for all approver role levels that participate in the edit test. If the test only warrants two levels of review, then place a tolerance value (equal to Parameter 2) in the Argument 2 For Role 2. If the test warrants four levels of review, with ascending role level tolerance values, then you need to enter the tolerances for each role accordingly. The following test rule examples provide clarification.

On this page

1 About the Examples
2 Example A
3 Example B
4 Example C
5 Example D

About the Examples

When you review the following examples, keep in mind that the Rule Operator column includes the following options:

< Less than

> Greater than

= Equal to,

<> Not equal to

<= Less than or equal to

>= Greater than or equal to

The following figure shows the test rules for the Unrealized per Share NAV Impact Test, which has an Edit Test Category value of Core-FAH. This is a tolerance related edit test with dynamic variables in the test rule.This edit test applies difference tolerances by investment type (for example, EQ, FI).For example, one row applies to equities where the NAV impact per share is greater than a defined tolerance value. Another row applies to equities where the NAV impact per share is less than a defined tolerance value. In the Argument 2 For Role 1 column, you see the tolerance thresholds defined for several investment types. By default, the edit test rules require one level of business review. If you use the fund approval hierarchy, the tolerance threshold defined for Argument 2 For Role 1 applies to approval role level 1, Preparer (Role 1).

Unrealized per Share NAV Impact Test - Core FAH

In the following figure for the non core edit test for the Unrealized per Share NAV Impact Test, you define tolerance values for all approval role levels that participate in the test. You can define tolerance values in the Argument 2 For Role 1 column, the Argument 2 For Role 2 column, the Argument 2 for Role 3 column, and the Argument 2 for Role 4 column.

Unrealized Per Share NAV Impact Test with Approval Levels

Example A

The test rule in this example requires a maximum of four levels of approval to clear a raised edit.

If the test produces a value of 0.006, then the system raises an edit requiring only role levels 1 and 2 (Preparer and Reviewer) to approve it. The error detail states NAV Impact per Share of 0.006 is outside the tolerance range of 0.005000 and -0.005000.

If the test produces a value of 0.008, then the system raises an edit requiring an Accounting Manager (role level 3) or above to approve it. The error detail states: NAV Impact per Share of 0.008 is outside the tolerance range of 0.0075000 and -0.0075000. The system populates the ROLE_LEVEL column in the ENTITY_VALIDATION_RESULT table with a value of 3, indicating that an approval at role level 3 is required to clear the edit.

Parameter 1	Rule Operator	Argument 2 For Role 1	Argument 2 for Role 2	Argument 2 for Role 3	Argument 2 for Role 4

Parameter 1	Rule Operator	Argument 2 For Role 1	Argument 2 for Role 2	Argument 2 for Role 3	Argument 2 for Role 4
EQ	>=	0.005	0.005	0.0075	0.01
EQ	<=	-0.005	-0.005	-0.0075	-0.01

The system assumes that you define higher role level tolerances that are equal to or greater then lower role level tolerances. Test rules that you do not configure in this manner result in an error.

Example B

The test rule in this example requires a maximum of three levels of approval to clear a raised edit. This edit test never requires role level four to approve an edit with this rule configuration.

Parameter 1	Rule Operator	Argument 2 For Role 1	Argument 2 for Role 2	Argument 2 for Role 3	Argument 2 for Role 4

Parameter 1	Rule Operator	Argument 2 For Role 1	Argument 2 for Role 2	Argument 2 for Role 3	Argument 2 for Role 4
EQ	>=	0.005	0.005	0.01	.
EQ	<=	-0.005	-0.005	-0.01

Example C

The test rule in this example requires a maximum of two levels of approval to clear a raised edit. The edit test never requires role levels three and four to approve an edit with this rule configuration. However, an Accounting Manager (role 3) or Unit Manager (role 4) can approve this edit because it only requires a Reviewer (role 2) to review and approve.

You can have different values for the Argument 2 for Role 2 column than you have for the Argument 2 for Role 1 column, provided that the role level 2 value is equal to or greater than the role level 1 value. The system determines the level of required approval (1 or 2) by the results generated from the test (see example A).

Parameter 1	Rule Operator	Argument 2 For Role 1	Argument 2 for Role 2	Argument 2 for Role 3	Argument 2 for Role 4

Parameter 1	Rule Operator	Argument 2 For Role 1	Argument 2 for Role 2	Argument 2 for Role 3	Argument 2 for Role 4
EQ	>=	0.005	0.005		.
EQ	<=	-0.005	-0.005	-

Example D

The test rule in this example performs with only one role level defined.

Parameter 1	Rule Operator	Argument 2 For Role 1	Argument 2 for Role 2	Argument 2 for Role 3	Argument 2 for Role 4

Parameter 1	Rule Operator	Argument 2 For Role 1	Argument 2 for Role 2	Argument 2 for Role 3	Argument 2 for Role 4
EQ	>=	0.005			.
EQ	<=	-0.005		-