This chapter describes Static Table Driver functionality.
Topics:
· Static Table Driver Summary and Detail Screens
· Navigation within the Summary Screen
· Navigation within the Detail Screen
Upon initially navigating to Profitability Management > Rule Specification > Static Table Driver, a summary screen is displayed showing a set of Static Table Driver rules. Using search criteria, you can control the set of rules that are displayed. When you Add, Edit, or View a rule, a detailed screen is displayed.
Figure 103: Static Table Driver Summary Screen
When you first navigate to the Static Table Driver summary screen, the rules stored within your current default Folder are presented in a summary grid. The Static Table Driver summary screen has two containers: Search and Static Table Driver.
Your default Folder functions as a search constraint. The value of your default Folder is set in Application Preferences for Oracle Insurance Allocation Manager for Enterprise Profitability. You may select a different Folder or you may remove the Folder constraint entirely by selecting the “blank” Folder, that is, no Folder. You may also search by a rule's Name or Description.
· Search Control: You may search for Static Table Driver rules by Folder, Name, or Description. Enter your desired search criteria and click on the Search control.
· Reset Control: Restores the default Folder, removes any Name or Description constraint you may have specified, and refreshes the screen.
The Static Table Driver container presents a grid containing all of the Static Table Driver rules that meet your search criteria. The Static Table Driver summary grid offers several controls that allow you to perform different functions when a rule is selected.
To select a rule, click on a check box in the first column of the grid. More than one rule can be selected at a time but this will cause some of the controls to become disabled. Clicking on a checkbox a second time de-selects the rule.
You may select or deselect all of the Static Table Driver rules in the summary grid by clicking on the check box in the upper left-hand corner of the summary grid directly to the left of the Name column header.
· Add: Clicking on the Add control begins the process of building a new Static Table Driver rule. The Add control is disabled if any rows in the grid have been selected.
· View: Selecting a single row out of the grid enables the View control. Clicking on the View control allows you to view the contents of a Static Table Driver rule on a read-only basis. The View control is only enabled when a single rule has been selected.
· Edit: Selecting a single row out of the grid enables the Edit control. Clicking on the Edit control allows you to modify a previously saved Static Table Driver rule. The Edit control is only enabled when a single rule has been selected.
· Delete: Selecting one or more rows out of the grid enables the Delete control. Clicking on the Delete control deletes the Static Table Driver(s) you have selected. OFSAAI will not allow you to delete Static Table Driver rules which have any dependencies (see View Dependencies below). When you click on Delete, a message is displayed: Are you sure you want to delete this record
· Copy: Selecting a single row out of the grid enables the Copy control. Clicking the Copy control allows you to create a copy of an existing Static Table Driver rule. The Copy control is only enabled when a single Static Table Driver rule has been selected. When you click on Copy, a Save As pop window will appear. Click Save after entering the Name, Description, Folder, and Access Type Details.
· View Dependencies: Clicking on the View Dependencies control generates a report on any Allocation rule that depends on the Static Table Driver rule you have selected. The View Dependencies control is only enabled when a single rule has been selected.
· Refresh: Click the Refresh control to refresh the Static Table Driver rule summary grid, including updates to the Last Modified Date.
The following columns categorize each allocation rule in the summary pane:
Figure 104: Static Table Driver Summary Pane
· Name: Displays the rule's short name. Performing a “mouse-over” on a Name displays the Static Table Driver rule's description and system identifier.
· Creation Date: Displays the date and time at which a rule was created.
· Created By: Displays the name of the user who created a rule.
· Description: Displays the rule's Description.
· Last Modified Date: Displays the date and time at which a rule was last modified.
· Modified By: Displays the name of the user who last modified a rule.
· Access Type: Displays the “Read/Write” or “Read Only” property of a Static Table Driver rule. Only the creator of a rule may change its Access Type.
· Folder: Displays the name of the Folder in which a Static Table Driver rule is stored.
When you Add, Edit, or View a Static Table Driver rule, the Static Table Driver Detail screen is displayed.
In addition to Name, Description, Folder, and Access Type, the definition of a Static Table Driver includes Key Leaves, a Target Leaf, and coefficients values. Once a Static Table Driver has been defined and saved, you will generally only edit an existing rule to update your driver coefficients (addition or deletion of Key and Target dimensions are not possible).
The Audit Trail container is a standard footer container for every OFSAA rule type. It displays Created By, Creation Date, Last Modified By, and Modification Date on the Audit Trail tab. The User Comments tab may be used to add comments to any rule, subject to a maximum of 4000 characters.
Static Table Driver Functionality
Static Table Drivers are used in conjunction with Allocation rules for two purposes:
· To distribute balances at the Management Ledger-level
· To perform a lookup table function against instrument tables
Static Driver Table Allocation rules that distribute balances at the Management Ledger-level function similarly to Dynamic Driver allocation rules. In your Debit or Credit outputs
· Key Leaves function similarly to Dynamic Driver allocation rules that utilize < Match Source & Driver >
· Target Leaves function similarly to Dynamic Driver allocation rules that utilize < Match Driver >
Static Driver Table Allocation rules perform a lookup table function against an instrument table to match dimension values for each instrument row against the Key Leaf values you define in your Static Table Driver rule. When matching rows are found, the allocation performs an arithmetic operation combining source balance columns and a coefficient value you specify to update a result column.
Specify the Static Table Driver rule's Name and Description, select a Folder in which the Static Table Driver rule is to be stored, and specify whether you want the Static Table Driver rule to be “Read/Write” or “Read Only” (Access Type). Naming your Static Table Driver rule is required before it can be saved. Static Table Driver rule Name does not accept Special characters (&, @, ~, +, Single quote). Default values for Folder and Access Type are stored in Application Preferences for Oracle Insurance Allocation Manager for Enterprise Profitability.
The first thing you must do when creating a new Static Table Driver is to define its structure. Once a Static Table Driver has been defined, typical maintenance is usually limited to updating driver coefficients. The most critical aspects of a Static Table Driver's structural definition are its:
· Key dimension
· Key Leaf values for each Key Leaf
· Target dimension
· Target Leaf values for each Target Leaf
· Defining Key Leaf values and Target Leaf values
· Static Table Driver Coefficients
You need not specify both a Key Leaf and a Target Leaf, but you must specify at least one or the other. That is, you should select a Key or Target dimension while defining a new Static Table rule.
NOTE:
You cannot add or delete the Key/Target dimensions after defining the Static Table Driver (edit mode). You can add or delete the dimension members.
For both Management Ledger-level and Instrument allocations, Key Leaves perform a lookup function. Rows from the Source of the Allocation rule are joined with the Key Leaf values from the Static Table Driver. If an input row leaf value matches a Key Leaf value for the first Key Leaf dimension specified in the Static Table Driver, the row is then checked against the second Key Leaf values, and so on. If a match is found for every Key Leaf dimension, the row is processed by the Allocation rule. Oracle Insurance Allocation Manager for Enterprise Profitability supports a maximum of 3 Key Leaf dimensions.
Target leaves are used only in allocations that distribute to the Management Ledger level. Distribution allocations can be viewed as first performing a lookup on one or more Key Leaves. When a match is found for each Key Leaf dimension, the matching input row's amount is distributed to all dimension values specified as Target Leaf values. This means that data is added to the Management Ledger for each dimension member value specified as a Target Leaf value. The leaf values specified in the Allocation rule's Debit typically use the < Same As Source > macro for all Key leaf dimensions and use the < Same As Table > macro for the Target Leaf dimension (very similar to the < Same as Driver > macro used in Dynamic Driver allocation rules).
You must specify coefficient values for every Static Table Driver rule. A part of the coefficient specification process is to enter the values for each distinct combination of each of your Key Leaves and your Target Leaves. Where only Key Leaves are used, you must enter values for each distinct combination of each of your Key Leaves.
For Static Table Drivers with a Target Leaf Dimension
For a Static Table Driver that uses a Target Leaf dimension, you must supply one coefficient value for each distinct combination of each of your Key Leaves and your Target Leaves. Again, Static Table Drivers that use a Target Leaf dimension are only supported for Management Ledger allocation rules.
Target Leaf coefficient values represent distribution statistics. You would typically use these statistics on a Percent-to-Total basis. Static Table Drivers support both the Percent-to-Total method and the Simple method.
The definition of the Target Leaf dimension may be preceded by the definition of one or more Key Leaf dimensions. Key Leaves are never required unless there is no Target Leaf defined. When Key Leaves are present, they operate as lookup keys as described above. For a Static Table Driver that uses a Target Leaf dimension, the Key leaves function analogously to the Dynamic Driver allocation function of < Match Source & Driver > and the Target Leaf functions analogously to the Dynamic Driver allocation function of < Match Driver >.
For Static Table Drivers with Key Leaf Dimensions But No Target Leaf
For Static Table Drivers that do not use a Target Leaf dimension, you must supply one coefficient value for each distinct combination of each of your Key Leaves. Static Table Drivers that use Key Leaves but do not use a Target Leaf can support both distributive Management Ledger allocation rules and Instrument-level update rules.
For an Instrument-level update rule using a Static Table Driver, the Key Leaves function as lookup keys, and the coefficients are used as arithmetic factors in updating a target column in an instrument table. For Management Ledger allocation rules, the Key Leaves function analogously to the Dynamic Driver allocation function of < Match Source & Driver >.
This section describes a typical workflow for defining a Static Table Driver rule.
To define a Key Leaf dimension:
1. Choose the dimension you want to define as a Key Leaf from the Add Leaf drop-down list.
2. Click on the Key radio button.
3. Click on the Add control. The Key Leaf dimension will be added to the Key Dimension section.
Figure 105: Static Table Driver (New) – Definition Mode
4. Click the Hierarchy Browser ellipses (…) that appear next to your Key Leaf. The Hierarchy Browser defaults to a list of leaves for the Key Leaf dimension you have chosen (the radio button selector near the top of the browser window defaults to Dimension Leaf Member). You may scroll up and down to find the leaf member or leaf member you want. You may also search for a dimension member's name (short description) using the binoculars at the bottom of the browser window. Additional search functionality is provided by the Search control within the browser. This additional functionality allows you to search by Dimension Member, Name, or Code. Once you have selected the Key Leaf values you want, click OK.
5. You may also define Key Leaf values to be rollup members within a hierarchy. To select hierarchy rollup point members, click the Hierarchy radio button near the top of the browser window and then search for the hierarchy you wish to use. Once your chosen hierarchy is displayed within the browser window, navigate into the hierarchy until you have found the rollup points you want. Select the value or values you want and then click OK.
Figure 106: Hierarchy Browser
6. After you click OK within the Hierarchy Browser window, that window closes and you will be directed back to the Static Table Driver Definition tab. If you again open the Hierarchy Browser of dimension, it will show the members as checked which were already selected while defining a key leaf.
You may now repeat this process to add a second or third Key Leaf if desired. If no additional Key Leaves are needed, you may proceed to either (1) adding a Target Leaf dimension or (2) providing coefficients for your chosen Key Leaf value(s).
NOTE:
When you select hierarchy rollup points, all of the members, you select must come from the same level within the underlying hierarchy. Hierarchy Filters, which may include leaves and rollup nodes from different levels within a hierarchy, are not supported in Static Table Driver rules.
Target leaves are used only in allocations that distribute to the Management Ledger.
Continuing with the typical setup workflow, the following narrative assumes that you have added only one Key Leaf dimension.
1. Choose the dimension you want to define as a Target Leaf from the Add Leaf drop-down list.
2. Click on the Target radio button.
3. Click on the Add control.
4. The Target Leaf dimension will be added under the Target Dimension section.
Figure 107: Static Table Driver (New) – Definition Screen
5. Click on the Hierarchy Browser ellipses (…) that appear on your Target Leaf.
6. Select the Target Leaf values (the selection process is identical to the process of selecting Key Leaf values described above) from Hierarchy Browser and click OK.
Figure 108: Hierarchy Browser
7. After you click on OK within the Hierarchy Browser window, that window closes and you will be directed back to the Static Table Driver detail screen However, while the screen still displays your Key Leaf values under the Key Dimension section as rows, it now displays your Target Leaf values under the Target Dimension section as rows.
Navigate to the Coefficient tab to assign coefficients to combinations of Key leaf (or node) values and Target leaf values. Continuing with the typical setup workflow, the following narrative assumes that you have now added one Key Leaf dimension and one Target Leaf dimension, have chosen your Key leaf dimension values and your Target Leaf dimension values. These steps are the normal setup steps required when building a new rule.
1. Click on Coefficient to navigate to the Coefficient tab.
2. Enter the coefficient values.
Figure 109: Static Table Driver (New) – Definition Screen
3. Click Apply. Click the Definition button to view or edit the Key Leaf and Target Leaf dimensions' definition.
4. Select the Delete control to remove any Key Leaf or Target Leaf dimension. When you click Delete, a message box is displayed: Are you sure you want to delete this record? Click OK to continue.
Select either “Yes” or “No” for the value of the “Force to 100%” allocation method (see radio buttons near the bottom of the detail screen). The default value for “Force to 100%” is “Yes”.
Static Driver Table rules are similar in many ways to Dynamic Driver rules. Select “Yes” for the value of Force to 100% when you want to perform a distribution using non-normalized statistics such as headcount, square footage of occupancy, and so on. If you are using a normalized set of driver statistics (statistics that sum to 1.00 or 100%) or if you are combining activity counts with activity rates, you need not use Force to 100%.
When you use Force to 100% in a Static Table Driver rule, balances will be distributed on a percent-to-total basis within each row visible on your Coefficient data entry grid.
For example, for the above coefficient values, balances would be distributed from Company A to Cost Center 1 and Cost Center 2 in proportions of 10% and 90%; and balances would be distributed from Company B to Cost Center 2 and Cost Center 3 in proportions of 40% and 60%.
· Save: Click on Save to validate and save your rule.
· Cancel: Click on Cancel to close the rule without saving any changes you may have made. This control is only active when you are in Edit mode.
· Excel Export: Use this feature to export your Static Table Driver data to a spreadsheet. Within the spreadsheet, you can update the coefficient values for any existing Key ' Target combination and you can add new Key ' Target combinations and their coefficient values. Afterward, you can import your spreadsheet back into Oracle Insurance Allocation Manager for Enterprise Profitability.
Figure 110: Static Table Driver (New) – Definition Screen
To export to a spreadsheet:
1. Click on Export.
2. Open using Excel or save the file to the name & location of your choice.
Excel import functionality is used for adding / editing leaf data in static table drivers.
To import a file, follow these steps:
1. Click Import to trigger an Upload File dialog.
Figure 111: Static Table Driver (New) – Definition Screen
2. Browse for the spreadsheet that you want to import.
3. Select the file and click Open.
4. Click Upload File.
The Search option allows you to search the Leaf values that have coefficient values defined on the Static Table Driver Definition page. This functionality works only if the Only Coefficient option is enabled. You can export this extracted list using the Export functionality.
To perform the search, follow these steps:
1. Enable the Only Coefficient using the corresponding check-box.
Figure 112: Static Table Driver (New) – Definition Screen
2. Click Search.
It shows the list of Leaf values that have coefficient defined. Also, a red dot (.) will be added next to the Only Coefficient option. You can also export this list using the Export functionality.
3. Use the Reset button to remove the filter.
The Search option allows you to search for specific Leaf.
4. Click ellipses (...) that are available next to Key Leaf or Target Leaf dimension, a list of defined Key Leaf values or Target Leaf values will display. Select the required Leaf values using the corresponding check-boxes.
Figure 113: Static Table Driver (New) – Definition Screen
5. Click Search. Only selected Leaf values will be displayed. You can also export this list using the Export functionality.
You can also use the Search option to search the specific leaf with coefficients defined using the Only Coefficient check box. You can also export this list using the Export functionality.
The Reset option on the Static Table Driver Definition page removes any coefficient you may have specified and refreshes the screen. It also allows you to reset the Search on the Static Table Driver Definition page.
Example
For other uses, you may want only a subset of all possible combinations of Key Leaf values and Target Leaf values. For example, you may wish to allocate a series of Management Ledger balances from a cost center to a cost center. If you wanted to allocate balances from Company A to Cost Centers 1 and 2; and if you wanted to allocate balances from Company B to Cost Centers 2 and 3, then your
· Key Leaf dimension would be Organizational Unit
· Key Leaf values would be Company A and Company B
· Target Leaf dimension would also be Organizational Unit
· Target Leaf values would be Cost Centers 1, 2, & 3
· Enabled combinations would be A-1, A-2, B-2, and B-3
Click on the Coefficient control. The detail screen now displays a data entry grid. Enter the values for valid Key Leaf value and Target Leaf value combinations.
You may toggle back and forth between the specification of valid combinations and the entry of coefficient values (Coefficient / Map). You may also return to your Key Leaf dimension tab and modify its definition by adding or removing values. More generally, you are free to navigate at any time between any of your Key Leaf definitions, your Target Leaf definition, your “enabled combinations” definitions, and your coefficient values.
At the time of initial set up on the Definition tab, a Static Table Driver rule will have a set of possible Key ' Target combinations equal to the cross product of each of the Key and Target leaves you have defined for your rule. For example, a Static Table Driver rule having one Key leaf dimension with 10 defined members and one Target leaf dimension with defined 100 members will have a total of 1,000 possible Key ' Target combinations. Of these 1,000 possible combinations, you may have defined 75, or 125, or any number coefficient values up to 1,000.
The Excel Export feature exports "active" Key ' Target combinations, i.e., combinations for which you have already established coefficients.
The structure of your exported Static Table Driver depends on how many Key dimensions and Target dimensions are used in your rule. The following example shows an exported data a Static Table Driver having one Key leaf dimension and one Target leaf dimension with 11 defined coefficients.
Figure 114: Sample Illustration of Exported Static Table Driver Definitions
In this example, the first two columns (F0_ID and F0_Desc) contain the leaf identifiers and descriptions for the Key leaf dimension. For a Static Table Driver having a 2nd and 3rd Key leaf dimension, the exported spreadsheet would include ID's and descriptions for each Key leaf dimension (F0, F1, and F2 represent "from" dimensions, i.e., Key leaf dimensions, while T1, T2, and T3 represent your first, second, and third Target leaf dimensions).
You may update the coefficient value for any combination in the spreadsheet (yellow cells in the example above).
To add a new combination to your data, follow these steps:
1. Enter a new leaf ID value for each Key leaf dimension you have defined in your rule
2. Enter a new leaf ID value for each Target leaf dimension you have defined in your rule
3. Assign a coefficient to the new combination
The example below (yellow cells) highlights a new combination for Key leaf =8200, Target leaf = 8400, and Coefficient = 285.
NOTE:
Descriptions are included in the download for convenience. You are not required to provide Descriptions for any Key or Target leaves. Any description values you provide will be ignored when Import into Oracle Insurance Allocation Manager for Enterprise Profitability.
Figure 115: Adding New Combinations to Exported Data
After Import, the system validates each row in your spreadsheet. Rows failing validation will not be imported. The validation requirements are as follows:
1. The spreadsheet structure must match the definition of the rule to which it is being imported. This is not an important restriction because the typical workflow for maintaining a Static Driver Table in a spreadsheet begins with an Export of the rule that you want to edit.
2. Each Key leaf value and each Target leaf value must be part of the definition of your Static Table Driver rule. In the case of the example above, the Key leaf value of 8200 and the Target leaf value of 8400 must have been included in the initial setup of the Static Table Driver rule (on the Definition tab).
NOTE:
You must define a Key ' Target combination on the Static Table Driver Definition tab before you can add that combination to your spreadsheet.
Static Table Drivers are generally used in a distributive fashion, and the Static Table Driver user interface is engineered for this typical use case. Some features of the user interface are limited for Static Table Drivers having large numbers of Key leaf values (or node values) in conjunction with large numbers of Target leaf values. For these cases, you must maintain your large Static Table Driver rules using Excel Export/Import functionality.
The Static Table Driver user interface is designed to allow you to specify coefficient values for any combination - or even for every combination - of your Key leaves and Target leaves. For example, a simple Static Table Driver having 50 Key Leaf values (in one Key Leaf dimension) and 100 Target Leaf values (in one Target Leaf dimension) could have as many as 5,000 "active" combinations (i.e., combinations for which coefficients are defined). Typically, the number of defined combinations is a small fraction of the number of possible combinations.
The number of possible combinations is determined by the Cartesian product of the number of leaf values in each dimension in your Static Table Driver rule. For example, a Static Table Driver rule having 5,000 Key Leaf values (in one Key Leaf dimension) and 5,000 Target Leaf values (in one Target Leaf dimension) has a cross product of 25 million. The performance and response time of the Static Table Driver user interface can become degraded with extremely large cross products. For this reason, the application applies a limit of 20 million on the size of the cross product. You may modify the default limit by manually updating SETUP_PARAMETERS_MASTER.STATIC_TABLEID_TEMP_TABLE_CROSS_JOIN_LIMIT.
When you are working with a Static Table Driver whose cross-product exceeds the cross join limit, the Coefficients tab of the Static Table Driver user interface will display only "defined" combinations, i.e., combinations for which coefficients have previously been established.
To build a Static Table Driver that will have a very large cross product, follow the normal steps of building out your Key leaf (or node) values and your Target leaf values on the Static Table Driver Definition tab. If you start with a modest number of defined Key and Target leaves, the Coefficients tab will operate normally and you may save coefficients for any possible combination of Key and Target leaves that you have defined on the Definition tab.
If you navigate to the Definition tab and add more Key leaves and more Target leaves and then return to the Coefficients tab, the Coefficients tab will again allow you to edit coefficients for any possible combination of your selected Key & Target leaves so long as you have not yet exceeded the cross product limit. Once you have added enough combinations on the Definition tab for the rule to exceed to cross-product limit, the Coefficients tab will no longer show unmapped combinations. In this state, you can edit the coefficient values for any previously mapped combination but you can no longer establish new combinations & coefficient values within the Coefficients tab.
NOTE:
Instead of starting the build process with a modest number of Key leaves and Target leaves, you might also begin by specifying a very large number of Key and Target leaf values. If you specify enough values in the Definition tab to exceed the cross product limit, then when you initially transition to the Coefficients tab it will appear blank.
Regardless of whether your Static Table Driver rule begins as a small rule and evolves into a large cross product rule or your Static Table Driver rule was "large" at the time it was initially defined, the Coefficients tab will only display "defined" combinations once you have exceeded the cross product limit.
You can edit the coefficient value for any defined combination within the user interface. Alternatively, you can also export your data and edit coefficient values offline.
1. Navigate to the Definition tab and add new Key & Target leaf values.
2. Navigate to the Coefficient tab and export your rule to a spreadsheet.
3. Add your new combinations and their coefficients to the spreadsheet.
4. Save and import the spreadsheet.
You can remove coefficients within the Coefficient tab by deleting the coefficient and saving the rule. Once you have removed the coefficient for a combination of Key ' Target leaves, that combination will no longer be updatable within the Coefficient tab, but the combination remains defined (i.e., you could still add a coefficient to this combination offline).
To completely remove defined Key and Target leaf values, navigate to the Definition tab and remove the leaves that are no longer required.
Static Table Drivers are declared as drivers in the Driver process tab for allocation rules of the type Static Driver Table (see Allocation Specification).
Static Drivers Table allocation rules are similar in many ways to Dynamic Driver allocation rules. Both are used to distribute balances, but while Dynamic Driver allocation rules obtain their driver data directly from your business data, Static Driver Table allocation rules obtain their driver data from a Static Table Driver rule.
In the example that follows, your goal is to “product align” your Management Ledger data (your initial General Ledger data is aligned to Organizational Unit and General Ledger Account, but not to Product). You need to write allocation rules that distribute expenses within each cost center to the Product. In this example, you are focusing on expenses incurred in two rollup points within your Organizational Unit hierarchy: Mortgage Origination (a rollup point of multiple regional origination centers) and Statement Processing (a rollup point of multiple statement processing centers).
Figure 116: Static Table Driver (New)
Your cost studies have told you that 55% of mortgage origination expense is attributable to your 30 Year Fixed Mortgage product, and 45% to your 15 Year Fixed product. At the same time, historical balance reports tell you that 55% of your retail deposits are Savings, and 55% are Time Deposits. On the assumption that balance ratios are a good way to distribute Statement Processing expense, you decide to use a 45-55 split.
To build this allocation, start by constructing a Static Table Driver rule that uses an Organizational Unit Key Leaf and a Product Target Leaf. Select the Mortgage Origination and Statement Processing rollup points from your organizational hierarchy for your Key Leaf values. Select the 3 mortgage products plus the Checking, Savings, and Time Deposits products as your Target Leaf values. Finally, enable the appropriate combinations of Key Leaf and Target Leaf and enter your coefficient values.
Figure 117: Allocation Specification (Edit)
Next, build a new Static Driver Table allocation rule. In the Driver tab, select the Static Table Driver you just built. In the Source tab, constrain the General Ledger Account dimension with a rollup point whose meaning is Total Non-Interest Expense; alternatively, you might specify Financial Element leaf value 457 – Non-Interest Expense.
Note that you could specify an Organizational Unit constraint in your Source specification narrowing the source data down to just the Mortgage Origination and Statement Processing rollup points. Doing so is not strictly necessary as the allocation rule will insist on the matching of Source cost centers and Driver cost centers and you have already constrained the Driver cost centers in your Static Table Driver rule.
In your allocation Output Debit, specify < Same as Table > for the Organizational Unit dimension and specify < Same as Source > for every other dimension.
Figure 118: Allocation Specification (Edit)
Note the similarity between the Static Driver Table allocation rule defined above and a very similar allocation built using dynamic drivers. If the statistics we used in the Static Table Driver were available from an external source that we could load every month to the data model, we could achieve the same results with a Dynamic Driver allocation rule. The Output Debits in the table below show the values you would use for the two rule types.
Dimension |
Dynamic Driver Allocation Debit Definition |
Static Table Driver Leaf Type |
Static Driver Table Allocation Debit Definition |
|---|---|---|---|
Organizational Unit |
< Match Source & Driver > |
Key Leaf |
< Same as Source > |
General Ledger Account |
< Same as Source > |
Not defined |
< Same as Source > |
Product |
< Match Driver > |
Target Leaf |
< Same as Table > |