Data Unit Calculation Sequence (DUCS)
The following has been taken from the OneStream XF Design and Reference Guide (September 2020) starting at page 31. Guidelines on Formula Passes There are 16 Formula Passes and one Dynamic Calculation Formula Type available on each Member. Formulas that do not depend on one another can exist in the same formula pass and will be calculated in parallel using OneStream’s advanced parallel formula processing engine. As a basic guideline, customers should think about organizing formulas by account/collection type across OneStream’s available formula passes using the following examples. All formulas in a pass are processed at the same time, so they cannot have dependencies on one another. Calculation Sequence of a Single Data Unit The items below detail the specific list of tasks executed for each Data Unit’s calculation process. As an example, the following steps are executed for a single Data Unit when a user selects Calculate for a single Entity, Scenario, and Time period. Data Unit Calculation Sequences (DUCS) Every time a data cell is written to the database, XF also includes information with the stored cell about how it was stored (e.g., manually entered, calculated, consolidated, etc.). If a number was calculated and stored as a result of a formula, it will always get cleared regardless of the metadata settings. The AllowInput property specifies whether a cell can be written to, and therefore if a formula stored a number, there would be information if the cell was calculated. If AllowInput is set to True, and a new number is typed over the same cell, it is stored as manually entered instead of a calculated cell. The following chart explains how the Consolidation Dimension works.How to Create a "Sort" Check Box in our Dashboards (used in schedules or reports)
Attached is a Word doc that shows you how to set up a check box to sort a “combo box” dashboard object populated with a list of members. These members can be a list of entities, accounts, flows, UD1’s… We do have several examples already set up in the Tax Provisioning Blueprint app, however this doc will walk you through using a new dynamic BR that can be used by any dimension.Confirmation Rules
The following has been taken from the Tax Provision Blueprint "Instruction Guide" starting at page 160. See KB article: "Tax Provision Blueprint Instruction Guide - PV7.3.0 SV100" See KB article: "Finance - TXP_SharedConfirmationRules" See KB article: "Finance - TXP_SharedConfirmationRules_FCST" Confirmation Rules The ability to create Confirmation Rules that are tailored to address customer specific controls is a powerful extension of the OneStream Platform. Tax Provision Blueprint has a few pre-built confirmation rules that you can use, modify, add on to, or remove if not necessary. There are nine confirmation rule groups that are then grouped into six confirmation rule profiles. All the confirmation rules are set up as “Warning (Pass)” and will not prevent the user from completing their workflow. This can be changed based on your application. TXP_FCST_Local_TaxRates Used for Forecast scenarios. Checks that a Filer Entity is using the same Local CY Apport Rates for all UD7 entities. This applies to any Filer Entity with the Tax Rates Used designation of “Filer Rates”. One rule is used for each of the 12 months. TXP_FCST_Monthly Used for Forecast scenario. Checks to see that there are monthly Current Tax Expense values - not derived data. One rule is used for each of the 12 months. TXP_FCST_Qtrly Used for Forecast scenarios. Checks to see that there are periodic values on the quarter end months for pretax income - specifically there should be no derived periodic data, blank data, or zeros. One rule is used for each of the 4 quarters. TXP_FCST_Yearly_GroupFilings Used for Forecast scenarios. Validate that there are the Group Filing Definitions and compare them to the GF definitions from the Actual scenario for period M12. One rule is used for period 12. TXP_GLTaxAdmin Used for the Actual scenario. Check that there is a value for the Interim Reporting ETR rate. Also checks to see if the Interim Reporting ETR rate is derived or manually entered. TXP_Local_JD_DM20a Used for the Actual scenario. Checks that the U4#National Data is the same for the U4#Local JD. Ensures that the DM20a copy dashboard rule has been executed since the last import of data. TXP_GF_Local_DM30a Used for the Actual scenario. Checks that the U4#National Data is the same for the U4#Local JD and U7# (Entity) base member. Ensures that the DM30a copy dashboard rule has been executed since the last import of data. TXP_Local_TaxRates Used for the Actual scenario. Checks that a Filer Entity is using the same Local CY Apport Rates / CY Stat Rates / Closing Deferred Apport Rates / Closing Deferred Stat Rates for all UD7 entities. This applies to any Filer Entity with the Tax Rates Used designation of “Filer Rates”. TXP_Nat_TaxRates Used for the Actual scenario. Checks that a Filer Entity is using the same National CY Stat Rates and Closing Deferred Stat Rates for all UD7 entities. The actual business rule syntax is not on each confirmation rule, but rather references a Finance Business rule called “TXP_SharedConfirmationRules” and “TXP_SharedConfirmationRules_FCST”. This allows for easier access to all the confirmation rules in one place, allows us to share common rules and provides additional functionality. TXP_SharedConfirmationRules:TXP_SharedConfirmationRules_FCST: The two main differences in the FCST rules are: We have one rule per month, as opposed to the Actual rules that has one rule that applies to all time periods We also need to indicate what month the rule needs to apply in (i.e.: 6).Business Rules - Overview
The following has been taken from the Tax Provision Blueprint "Instruction Guide" starting at page 103. See KB article: "Tax Provision Blueprint Instruction Guide - PV7.3.0 SV100" Business Rules There are several business rules that Tax Provision Blueprint uses. To understand how Business Rules (BR's) are processed: Data Unit Calculation Sequence (DUCS) Here are the links to all the Business Rules (BR's) that are used in the Tax Provision Blueprint solution. TXP_BusinessRules Execution Order Finance - TXP_BusinessRules Finance - TXP_Copy_Annotations Finance - TXP_Copy_Data Finance - TXP_Copy_Data_FCST Finance - TXP_CustomCalc Finance - TXP_CV_CompareAnnotation Finance - TXP_MemberList Finance - TXP_MemberListRanked Finance - TXP_NatFiler_Calc Finance - TXP_SharedConfirmationRules Finance - TXP_SharedConfirmationRules_FCST Cube View Extender - TXP_CV_ParentAccount_Bold Dashboard Data Set - TXP_HelperQueries Dashboard Extender - TXP_SolutionHelper Dashboard XFBR String - TXP_ParamHelper Extensibility Rules - SaveDataEventHandler SaveDataEventHandler BRDashboard XFBR String - TXP_ParamHelper
The following has been taken from the Tax Provision Blueprint "Instruction Guide" starting at page 122. See KB article: "Tax Provision Blueprint Instruction Guide - PV7.3.0 SV100" TXP_ParamHelper This BR is used extensively to format the CV’s, in parameters, in BR’s, as well as to determine the POV combo boxes that are used in dashboard. Understanding this BR is extremely important. Please take the time to review its contents. See the Reference Notes in the BR.SaveDataEventHandler BR
Attached is the SaveDataEventHandler business rule that is used in the Tax Provision Blueprint application. You can only have one SaveDataEventHandler BR per application. You will overwrite the existing Business Rule if loaded directly into the system. For this reason, it is not included in the “zip” Package and must be uploaded manually for the solution to work properly. The BR can be obtained in the Tax Provision Blueprint app in one of two ways. 1) On the Application Dashboards tab, click Dashboard Maintenance Units > XFW Tax Provision (TXP) > Files > 01 SaveDataEventHandler_BR_for_TXP.zip. In the General (File) pane, click the Download File icon in the Content File row and select a location to save the file locally. 2) The file can also be located on the Settings dashboard under Detailed Implementation Files:TXP_BusinessRules Execution Order
Attached is a one tab Excel file that shows the execution order of the main BR: "TXP_BusinessRules". It's important to remember that rules execute from the top of the file to the bottom (line by line). So, where you put additional rules for your specific application is very important. Order matters!!!Data Copy - What Happens When Different Entity Currencies are Involved?
Observations: OneStream will not copy a Local USD amount into a Local CAD cell. This is expected OS behavior. OneStream will not automatically translate prior to the Copy. The translate must be done prior to the Copy rule executing (either manually by the user or automated in a Data Management (DM) step). The CV does not re-render/refresh after the “Copy” or “Clear” is done (minor bug). So a manual “Refresh” is necessary in order to see the completed results. To fix this, the following two dashboard buttons need to be updated as follows - one is the "Clear" button and the other is the "Copy" button: This would hold true for the other Data Copy schedules / buttons. You can always add a Data Management step to first do a translations / consolidation prior to the Copy DM running. Testing Process: I first created a TXP_CA_102_US entity. It’s the same at TXP_CA_102 but with a USD currency. Also, this new entity has no Text 7 attributes. Next, I updated the UD7 hierarchy: Next, I updated the National GF definitions as follows: Next, I updated the workflow for the new entity. I put it in with the existing CA_102 entity. Next, I input a few pieces of data into Schedule 5. Save the data. Did a calculate to get a “OK” calc status. Next, open up “DM 10aAdmin”, set the POV and click on Refresh. Notice that you need to perform a “TR”. If you just run the “Copy” now, nothing will copy over. Right click on any cell in the “TR” column, and then do a Force Translate. Now you are ready to perform the “Copy”. After executing the “Copy”.Extensibility Rules - SaveDataEventHandler
The following has been taken from the Tax Provision Blueprint "Instruction Guide" starting at page 123. See KB article: "Tax Provision Blueprint Instruction Guide - PV7.3.0 SV100" See KB article: "SaveDataEventHandler BR" SaveDataEventHandler SaveDataEventHandler validates the year entered in Schedules 02, 03 and 04 on the “Save”. For Schedule 01f, it executes an “Impact Status” BR on the “Save”. You can only have one SaveDataEventHandler BR per application. You will overwrite the existing Business Rule if loaded directly into the system. For this reason, it is not included in the “zip” Package and must be uploaded manually for the solution to work properly. See the Reference Notes in the BR. The Tax Provision Blueprint section in this BR first tests the application. This prevents other apps (i.e., Finance cube…) from getting an error message.Cube View Extender - TXP_CV_ParentAccount_Bold
The following has been taken from the Tax Provision Blueprint "Instruction Guide" starting at page 117. See KB article: "Tax Provision Blueprint Instruction Guide - PV7.3.0 SV100" TXP_CV_ParentAccount_Bold We have a small CV Extender rule that will format account row headers as bold. It also formats the data rows as bold and puts in a top line.
