This article provides details on the business rules that Solver provides. Review these rules to see if they complete business processes you need. Additional business rules can be created with the help of your partner or Solver Consulting.
These rules require the SolverDW database to be updated to SQL2019+
| Rule Name | Description | Cloud | 4x | Private Host |
|---|---|---|---|---|
| CleanDim | Removes unused codes dependant on chosen dimension. Creates DimstoDelete Dimension if you set Debug Flag = Y | ✅ | ||
| CopyVersion | Allows the user to move data from one set of parameters to another. Typically this is used to move data from one scenario to another. | ✅ | ✅ | ✅ |
| CopyVersion_MultiYear | use this rule when you want to copy data based on a Scenario and not Period(s). This rule is typically used by customers on a Fiscal Calendar that does not begin at the beginning of the year. | ✅ | ✅ | ✅ |
| Rules_CurrencyTranslation_Rlng | This rule assumes that the source data contains monthly activity for all accounts within General Ledger. The Value2 field is used for YTD balances. This rule includes Rolling Periods in a Job. | ✅ | ||
| Rules_Currency_Translation_US_Flexible | Removes unused codes depending on chosen dimension. Creates DimstoDelete Dimension if you set Debug Flag = Y | ✅ | ✅ | ✅ |
| Rules_Currency_Translation | Similar to prior but not rolling enabled | ✅ | ✅ | ✅ |
| GenerateGLSummary | this business rule creates summary data off of GL_Detail data. It has the following assumptions. The Source Data is the GL_Detail module. The Destination is the GLThe Transactional Amount is found in Value1 and the summed value for GL can go into Value 1. All other attribute data is null at the GL level.NOTE: This does not work for selecting non-sequential periods | ✅ | ✅ | ✅ |
| GenerateGLSummaryDataRlling | ConsolidationsMinority Interest: Create minority interest transactions based on user-defined percent ownershipIntercompany: Create inter-company transactions based on user-defined percent ownership | ✅ | ||
| DeleteData | Delete data for a selected ModuleScenario PeriodStart & Period End Range | ✅ | ✅ | ✅ |
| Delete Data – Rolling | Delete Data as above but allows Rolling Periods. | ✅ | ||
| DeleteData – With Entity | Delete data rule + a selected Entity | ✅ | ✅ | ✅ |
| DeleteData – With Entity Rolling | Delete Data + Entity but allows Rolling Periods | ✅ | ||
| D365 DimUpdater | This rule populates into Value 3 the Opening Balance Amount for the beginning of the Period Chosen. Edits may be necessary if you need them to be more granular such as by department, location, etc. | ✅ | ✅ | |
| DimensionSets | Business Central specific: This rule is for D365BC customers to populate dimension codes based on DimensionSetID. | ✅ | ✅ | |
| Calc_OBA | Similar to the prior one but has a destination Scenario | ✅ | ✅ | ✅ |
| LoadRates | Loads Rates into Currency tables. For more information on how to do this, please go to this link: Load Rates Post | |||
| DeleteReclass | Allows users to remove duplicate transactions in the event of a reclassification or change in dimensions. Used with Delta Loads. | ✅ | ||
| GenerateOBAv2 & GenerateREOBAv4 – Retained Earnings | Populates OBA into Value3 for the beginning of the Period chosen. Edits may be necessary if it needs to be more granular such as by Department, Location, etc. GenerateREOBAv4 to be run right after GenerateOBAv2. | ✅ | ✅ | ✅ |
| DeleteDataNoScenario | Deletes data from any QuickStart that’s not GL and does not use Scenario as a parameter. | ✅ |