Dimension Member Names - Renaming and Deleting
Attached is a 10 tab Excel file that shows which member names can be renamed, deleted or not changed at all. It also indicates if the member name is used in CV's, BR's, Dashboard objects or in Data Management. It looks at the following dimensions: Scenario Entities Accounts Flow UD1, UD2, UD3, UD4, UD7 and UD8Design Assumptions
The following has been taken from the Tax Provision Blueprint "Instruction Guide" starting at page 12. See KB article: "Tax Provision Blueprint Instruction Guide - PV7.3.0 SV100" See KB article: "Dimension Member Names - Renaming and Deleting" See KB article: "Dimension Text Fields - Summary" Tax Provision Blueprint Design Assumptions Tax Provision Blueprint has made several assumptions in order for this blueprint to function properly in all sorts of client environments. Below is a list of the key assumptions. Cube: The app comes with a pre-defined cube called “XFW_TXP” We have used the Standard calendar that is defined monthly from Jan (M1) to Dec (M12). Your application may use a different calendar and most likely will follow what has been used in the Finance cube/app. For purposes of this document, the Seed year is 2019 and the first tax provision that is calculated is in 2020. Application Properties: Application Properties are not packaged with the Tax Provision Blueprint app as it could conflict and overwrite existing application properties. OneStream Dimensions: Scenarios: The app comes with a set of tax scenarios. Two actual scenarios are used called “TXP_Actual” (holds Actuals data) and “TXP_ActualRTP” (holds return to provision data). These scenarios use the scenario type of “Tax”. Several forecast scenarios have been created. These current year Forecast scenarios use the scenario type of “ScenarioType8”. Multi-year forecast scenarios are set up as “ScenarioType7”. This release has not been tested for multi-year forecasts and these scenarios are there for future development. Entities: The app comes with a set of test entities. It is expected that these entities will be removed and replaced with client specific entities. Base entities use - UD1 Constraint / UD7 Constraint / UD1 Default / Text 7 / Text 8 Parent entities use - UD1 Constraint / UD7 Constraint / Text 7 / Text 8 An admin entity called TXP_GLTaxAdmin is required. Accounts: The app comes with a set of tax accounts. Text 1 is used on base and parent members to identify “Discrete” accounts. Text 1 is also used on base members to identify “Losses Not Benefitted”. Alternate hierarchies are used with Aggregation weights. Flow: The app comes with a set of tax flow members. Text 1 is used on base and parent members to identify “Discrete” flows. Alternate hierarchies are used with Aggregation weights. UD1 (Jurisdictions): The app comes with a set of tax UD1 members. Text 1 is used on all base and parent UD1 members. Text 2 is used on some base level UD1 National members for countries doing National group filing. Alternate hierarchies are used with Aggregation weights. UD2 (Data Type): The app comes with a set of tax UD2 members. Alternate hierarchies are used with Aggregation weights. UD3 (Reporting/Accounting Type): The app comes with a set of tax UD3 members. UD4 (Tax Type): The app comes with a set of tax UD4 members. UD5 and UD6: The UD5 and UD6 dimensions are not used. The default is None. If you use UD5 and/or UD6 or the other dimensions differently than the Tax Provision Blueprint setup, significant updates and testing will be required in all the BR's, CV's, Parameters, Data Management sequences and Dashboards. UD7 (Group Filing entities): The app comes with a set of tax UD7 members. Base level and country parent level UD7 members must be the same as the base level and parent level entity members. Only required for countries doing Local and/or National group filing. Minimum required members are: TXP_TopTax / TXP_GFEntities / None when no group filing is used. UD8 (Dynamic Reporting): The app comes with a set of tax UD8 members. Cube Views: The app comes with several cube view groups and profiles. Schedules: Schedules (Form templates) are rendered through Dashboards. Several schedules have linked CV’s to get at additional detail (i.e.: the UD7 group filer entity detail). Business Rules: Most of the Tax Provision Blueprint business rules reside in the main Finance BR called “TXP_BusinessRules”. It is attached to the tax cube (XFW_TXP) as Business Rule 1. Dashboards: Dashboards are used extensively throughout the Tax Provision Blueprint app. All the tax schedules and reports are rendered through a dashboard. Workflows: The app comes with a set of workflow profiles. All entities assigned to a workflow must be in the same tax country (National jurisdiction). Workflow Text 1, 2 and 3 apply to all base level workflows (at the Tax Schedule/Forms workflow and the immediate parent workflow.) The “Adj” base level workflow is not active. This can be adjusted in your application. We have used a workflow suffix naming convention for the different types of workflow profile names. This makes it easier to understand what each type of workflow represents. Examples are: Xxx_LocalGroupFiler Xxx_NatGroupFiler Xxx_LocalGF Xxx_NatPrep Xxx_Nat_LocalGF Xxx_NoLocalGF Workflow Types: National Group Filing: Only one National Group Filer workflow is allowed per country. This workflow must end with “NatGroupFiler”. UD7 is used to hold the entities being filed by country. The base level UD7 members must be defined exactly how the entities are defined. No exceptions. Local Group Filing: Only one Local Group Filer workflow is allowed per country. This workflow must end with “LocalGroupFiler”. UD7 is used to hold the entities being filed by country. The base level UD7 members must be defined exactly how the entities are defined. No exceptions. Workflow Entity: Multiple workflow filers can be created in a country. Confirmation Rules: There are a few confirmation rules that are supplied with the app for both Actual and Forecast scenarios. They do not have to be used. They serve as a starting point Security: There is no security setup in the Tax Provision Blueprint app. We only use the two supplied groups called “Everyone” and “Administrators”. Other Important System Design Information National and/or Local group filing is either “On” or “Off” per country. It cannot be on for some entities/workflows and off for others. All dimension member parents should have the word “Total” somewhere in the description. This will assist with formatting the CV’s. We strongly recommend that you install the Tax Provision Blueprint app as is in a development environment. We have also supplied a supplemental Excel file that shows more detailed setup that is difficult to show and explain in Word. It is strongly recommended to review this file and reference it during your client specific setup. It can be downloaded from the Global Setting dashboard. There is also a supplemental Excel file that shows which dimension members can be deleted or renamed. It can be downloaded from the Global Setting dashboard.Dimension - Entities
The following has been taken from the Tax Provision Blueprint "Instruction Guide" starting at page 49. See KB article: "Tax Provision Blueprint Instruction Guide - PV7.3.0 SV100" See KB article: "Dimension Member Names - Renaming and Deleting" See KB article: "Dimension Text Fields - Summary" Entities XFW_TXP_Entitiesis the Tax Provision Blueprint sample Entity Dimension. It is provided with sample entities to show Reporting and Forms. A Legal or Tax reporting structure should be built in the XFW_TXP_Entities Dimension if the desired entity structure is not available in the Financial Model Entities Dimension. If the design decision is made to use the XFW_TXP_Entities, we recommend that this structure share base entity members (through a linked cube setup) with an existing finance structure that is used for consolidation. If distinct base entities must be created for tax, we recommend adding a _TXP suffix to each Entity Member (Houston_TXP). This makes writing Business Rules and Entity mapping easier and consistent across solutions. The sample entities that are included in XFW_TXP_Entities should be used as a reference for how to set up the Text properties for various situations, including National and Local Jurisdictions. Prior to data entry, all sample entities should be removed, except the TXP_GLTaxAdmin – Global Tax Admin entity. If the XFW_TXP_Entities Dimension is replaced as the assigned Entity Dimension for the XFW_TXP Cube, the TXP_GLTaxAdmin – Global Tax Admin entity must be removed from XFW_TXP_Entities and created in the Legal/Tax Hierarchy in the Entity Dimension that is being used. Do not change the Member Properties that are initially assigned to TXP_GLTaxAdmin – Global Tax Admin. The Tax Provision Blueprint application will not function properly without the TXP_GLTaxAdmin entity in the assigned Financial Model Entity Dimension under the Tax/Legal Hierarchy that is used. The TXP_GLTaxAdmin entity should be a sibling to the main Tax Entity hierarchy (TXP_Legal_CTX in Tax Provision Blueprint). The Tax Provision Blueprint application uses the Entity / Jurisdiction (UD1) grouping to help drive the results. UD1 is the Tax Jurisdiction that corresponds with the National (country) and Local Jurisdictions (where applicable) in which the legal entity will be taxed. There can only be one national jurisdiction associated with an entity. Each Entity Member (includes all entities added to XFW_TXP_Entities or the current entities in the substituted Financial Model Entity Dimension for Tax/Legal hierarchy) must add the following Entity Member Properties. Follow the guidelines in the Entity / UD1 Table below for sample setups. Entity Notes: General Alternate hierarchies can be used. All parent members must have the word Total in the description. This will help in the formatting of Cube Views. If intercompany (IC) is needed in the app., then flag the appropriate base level entities as “Is IC Entity=True”. UD1 Constraint Used on all entities (base and parents) – this drives the Finance Business Rule to execute. Limit’s what is a valid intersection. UD7 Constraint Used on all base level entities and up to country level parent entities. Limit’s what is a valid intersection. UD1 Default Used on all base level entities but not required on parent entities. Text 7 Used on any base entity that calculates both a National and a Local tax provision and calculates a National Benefit for the Local data (such as U.S. Federal Benefit of State): NatBenefit=Yes. Also used to tell the app if an entity is a Filer (only used for group filing – either National or Local): NatFiler=Yes and / or LocalFiler=Yes – base entity only. If a base entity requires more than one setting, use a comma to separate the two settings. NatBenefit=Yes,NatFiler=Yes,LocalFiler=Yes All other base entities – leave the property blank. All sub-country/country level parent entities – leave the property blank. At parent entities above the country level, use SETR=No to stop the parent entity from appearing on the Statutory Waterfall reports. Text 8 Required for all Tax entities (base and parent level). This is used to help determine the UD1 members. UD1 member that will vary by entity: base entity that calculates both a National and a Local tax provision; base entity that calculates only a National tax provision; parent entity. Here is a more detailed list of what each entity setting represents: UD1 Constraint: This limits the valid UD1 jurisdictions available for the entity. This ensures that invalid jurisdictions are not available for data entry (i.e., using a Germany JD on a US entity). For entities that have local jurisdictions, this member should be a parent (i.e., Entity: TXP_US_101 -> UD1 Constraint: TXP_US_Total). If there are no local jurisdictions for the entity, then the UD1 Constraint should be the National JD (i.e.: Entity: TXP_UK_101 -> UD1 Constraint: TXP_UK). For entity parents above the country level, use the member TXP_TotalNational. Note: If Finance is using or planning to use UD7 Constraints, UD1 Defaults, Text 7, or Text 8 fields, then it’s suggested to use the “Tax” / “ScenarioType7” / “ScenarioType8” Scenario Types and any other scenario types that are utilized in the tax cube. UD7 Constraint: This limits the valid UD7 group filing entities available for the entity. This ensures that invalid group filing entities are not available to enter data into (i.e.: using a Canadian group filer entity on a US entity). The UD7 Constraint should be the parent country member (Entity: TXP_CA_115 -> UD7 Constraint: TXP_Canada_Total). If an entity is not part of a group filing country (either National or Local), then use “None”. Parent entities above the country level should also be “Root”. UD1 Default: For base level entities and parent country entities, use the National jurisdiction (i.e. Entity: TXP_UK_Total -> UD1 Default: TXP_UK). For parent entities above the country level, use the “None” member. Parameters that use UD1 Default: UD1_Default_TXP Text 7: This field is used for four purposes listed below: NatBenefit=Yes Tells the system whether to execute the National Benefit from Local JD’s for that entity. See CV: Schedule LP 05_06a National Process excl Local JD_TXP. BR: TXP_BusinessRules: Schedule5_6NationalBenefitLocalCurrency Schedule8LocalRateReconciliationETR Schedule9ConsolidatedRateReconciliationETR LocalFiler=Yes This tells the app that this entity will be a Local Filer entity (for Group Filing Countries only). Parameters that use this: Entity_FilerType_TXP Entity_FilerType_MFEntity_TXP WF_TaxEntities_WFText2_P1_TXP NatFiler=Yes This tells the app that this entity will be a National Filer entity (for Group Filing Countries only). Parameters that use this: WF_TaxEntities_WFText2_P1_TXP SETR=No Used in the Home Page dashboard waterfall report. Removes parent entities above the country level from the entity combo box. Parameters that use this: Tax_Entities_SETR_TXP Text 8: This is used to populate the UD1 jurisdictions for the entity. It is used in parameters, business rules and directly in CV’s. Here is an example from a CV: U1#XFMemberProperty(DimType=Entity, Member=|!WF_TaxEntities_WFText2_P1_TXP!|, Property=Text8) Some of the parameters that use Text 8: UD1_JD_Nat_LV_TXP UD1_JD_Nat_TXP UD1_JD_Nat_DM10aAdmin_TXP UD1_JD_Local_TXP UD1_JD_Local_FC_TXP UD1_JD_Local_TaxEntities_TXP Business Rules that use Text 8: TXP_BusinessRules: variable “Jurisdiction” TXP_Copy_Data EntityText8 TXP_Copy_Data_FCST EntityText8 TXP_MemberList TXP_ParamHelper: GetEntityText8 Some of the CV’s that use Text 8: Sch_05c_Review_NatGF_No_Local_TXP Sch_05cFC_Review_NatGF_No_Local_TXP Sch_05c_Review_NatGF_Yes_Local_TXP Sch_05cFC_Review_NatGF_Yes_Local_TXP Sch_DM20a_Data Copy Provision_TXP Sch_DM20aFC_Data Copy Provision_TXP Sch_DM20aAdmin_Data Copy Provision_TXP Sch_DM20aAdminFC_Data Copy Provision_TXP Sch_LP05_06_National Process excl Local JD_TXP Sch_LP05_06_FC_National Process excl Local JD_TXP 10d Sch 05 Local Consol_TXP 10d FC Sch 05 Local Consol_TXP 20d Sch 06 Local Consol_TXP 20d FC Sch 06 Local Consol_TXP 25d Sch 07 Local Consol_TXP 25d FC Sch 07 Local Consol_TXP 80a_Stat_ETR_Analytics_TXP 80b_Stat_ETR_Waterfall_TXP There MUST be a Text 8 on ALL Tax entities (all base entities and all parent entities). There is a section in the main BR (TXP_BusinessRules) that looks to see if there is something in the entity Text 8 field. If there is nothing, none of the Tax Provision Blueprint rules will be executed for that entity. If there is no Text 8, the message displayed below will get written to the Error Log. No indication will be rendered to the user during a calculation or consolidation. So, it is important that the admin review the Error Log on a regular basis. This is especially true during the development of the app. Note: US entities TXP_US_LegalEntityA, TXP_US_101 and TXP_US_107 have their entity attributes set at the “Tax” Cube Type and the “Tax” Scenario Type as an example. All other test entity attributes are set at the “Default” Cube or Scenario Type. There are a few CV’s that use the XFMemberProperty to get the UD1 default or the Text 8. In order to make this dynamic to the Scenario Type and WF time period associated to the Scenario, a parameter has been created called “WFScenarioType_TXP”. The XFBR rule dynamically gets the scenario type associated with the scenario. When referencing the UD1Default (notice it is VaryByCubeType), we use: VaryByCubeType=[Tax], VaryByTime=[WFTime] When referencing the Text 7 or Text 8 (use the new parameter – notice it is VaryByScenarioType): VaryByScenarioType=[|!WFScenarioType_TXP!|], VaryByTime=[WFTime] The following CVs are impacted by these two options: XFW_Tax Forms Actual (TXP) folder: Sch_DM10a_Data Copy Provision_TXP Sch_DM20a_Data Copy Provision_TXP Sch_DM20aAdmin_Data Copy Provision_TXP Sch_DM20b_Data Copy Return_TXP Sch_DM30a_Data Copy Provision_TXP Sch_DM30b_Data Copy Return_TXP Sch_LP05_06_National Process excl Local JD_TXP XFW_Tax Forms FCST (TXP) folder: Sch_DM10aFC_Data Copy Provision_TXP Sch_DM20aFC_Data Copy Provision_TXP Sch_DM20aAdminFC_Data Copy Provision_TXP Sch_DM30aFC_Data Copy Provision_TXP Sch_LP05_06_FC_National Process excl Local JD_TXP XFW_Tax Reports Actual (TXP) folder: 80a_Stat_ETR_Analytics_TXP 80b_Stat_ETR_Waterfall_TXP XFW_Tax CV’s All Workflows Actual (TXP) folder: Sch_05b_Review UD2 Gross and Tax_TXP Sch_05c_Review_NatGF_No_Local_TXP Sch_05c_Review_NatGF_Yes_Local_TXP Sch_06b_NatGF_No_DefLocal Review_TXP Sch_06b_NatGF_Yes_DefLocal Review_TXP XFW_Tax CV’s All Workflows FCST (TXP) folder: Sch_05bFC_Review UD2 Gross and Tax_TXP Sch_05cFC_Review_NatGF_No_Local_TXP Sch_05cFC_Review_NatGF_Yes_Local_TXP Sch_06bFC_NatGF_No_DefLocal Review_TXP Sch_06bFC_NatGF_Yes_DefLocal Review_TXP The following parameters uses these options: UD1_JD_Nat_TXP UD1_JD_Nat_LV_TXP UD1_JD_Nat_DM10aAdmin_TXP UD1_JD_Local_TXP UD1_JD_Local_FC_TXP UD1_JD_Local_TaxEntities_TXPTime Profiles
The following has been taken from the Tax Provision Blueprint "Instruction Guide" starting at page 40. See KB article: "Tax Provision Blueprint Instruction Guide - PV7.3.0 SV100" See KB article: "Application Properties" See KB article: "Using a Time Profile With Weeks" Time Profiles The XFW_TXP cube uses the “Standard” time profile. The Fiscal Year Start Date is set to 1/1/2019. These settings can be adjusted based on your application. Also, if you are sharing with other cubes (ie: Finance), this may have an earlier year than your seed Year (that is OK). Please also see the Dimensions tab in "Application Properties". This is where you set the start year that controls the list of years in your POV. Remember, that this is an application settings that will impact all Cubes.Tax Cube Setup - XFW_TXP
The following has been taken from the Tax Provision Blueprint "Instruction Guide" starting at page 41. See KB article: "Tax Provision Blueprint Instruction Guide - PV7.3.0 SV100" See KB article: "Can I Rename the "XFW_TXP Tax Cube?" The XFW_TXP Cube is the organizational structure that holds the Tax Provision Blueprint data. Related XFW_TXP Cubes may need to be created for OneStream Linked Cube application designs if entries are necessary on the Cube References tab of this Cube (depending on Entity Dimension assigned and if Extensible Dimensionality is in play). If you opt to not use the Cube name “XFW_TXP”, then extensive search and replace will be required on all objects in the Tax Provision Blueprint application. Therefore, changing the Cube name is NOT recommended. If you opt to rename the tax cube, we strongly recommend complete comprehensive testing ofALLfunctionality. Note: Cube setup changes to the original objects may impact calculations or data access. Cube Properties – General The following Cube Properties are core to the application: Description: Tax Provision Blueprint - May be changed. Cube Type: Tax - Do not change. Time Dimension Profile: Standard - May be changed but will require review and possible updates to Business Rules, Cube Views, reports, workflows, and other objects. Cube Properties - Security Security will need to be implemented for each application. The only change that was made here is with the Maintenance Group. Cube Properties - Workflow Workflow suffix for varying Workflow by Scenario type has been used. “NotUsed” has been attached to all the scenario types except for Tax, ScenarioType7 (attached to multi-year forecast scenarios) and ScenarioType8 (attached to current year Forecast scenarios). These should not be modified as scenario types are referenced throughout BR’s and parameters. Cube Properties - Calculation No changes from the default. Cube Properties - Business Rules TXP_BusinessRules is the primary Finance Business Rule assigned as Business Rule 1 to the XFW_TXP Cube. This Business Rule set provides most of the tax provision functionality for calculations in the Cube. Other Business Rules may be assigned, as necessary. This BR may need to be moved to Business Rule 3 if member formulas are required to execute first. See also: Data Unit Calculation Sequences (DUCS) in the OneStream Design and Reference Guide. Cube Properties - FX Rates In the FX Rates section, note the use of the TXP_YTDAverageRate type that was created earlier. Cube Dimensions The XFW_TXP_Entities dimension is provided based on the XFW_TXP_Entities Dimension included with Tax Provision Blueprint. The Cube Entity Dimension assignment may be changed if the customer’s design decision is to use an existing Entity Dimension for a Legal or Tax reporting structure that is actively used and maintained in the OneStream Financial Model. Changing the assigned entity dimension may require updates to any references for XFW_TXP_Entities Dimension in Business Rules, Cube Views, Dashboards or Parameters. The Scenario Dimension assigned may also be the same as the Finance Cube. The two required Tax Scenarios (TXP_Actual and TXP_ActualRTP) with their specific attributes would need to be added. Make sure that the Scenario Settings are set up appropriately. The (Default) scenario type option is only usedfor the Entity and Scenario dimensions. The remaining dimensions are defined at the “Tax”, “ScenarioType7” and “ScenarioType8” (if current year Forecast scenarios are used) scenario types: Below is a summary of the Cube Dimensions and their expected modification status. Note that UD5 and UD6 are not currently used. Cube References This section is currently not used for Tax Provision Blueprint. This area may need to be updated in the case of a Linked Cube Financial Model design. Data Access This section is currently not used for Tax Provision Blueprint. Integration This section controls the Dimensions that are updated with the Import Input Type in Workflow and the columns of data that appear in the Stage database when imported data is viewed. It determines the order of processing Dimensions and which Dimensions are turned on for data integration. If one Dimension must process before another (rare case), the transformation sequence can be changed. All integration settings are defined at the “Tax”, “ScenarioType7” and “ScenarioType8” scenario types.Using a Time Profile With Weeks
The following has been taken from the Tax Provision Blueprint "Instruction Guide" starting at page 453. See KB article: "Tax Provision Blueprint Instruction Guide - PV7.3.0 SV100" See KB article: "Time Profiles" This information is part of the "Instruction Guide" that comes with the Tax Provision Blueprint app as Appendix C. Using a Time Profile with Weeks Tax Provision Blueprint has been developed using the Standard Time Profile with “Months” being the lowest level of input. We have done minimal testing having “Weeks” in the time profile. Below are some key findings to be aware of. This is not an exhausted list and will continue to be added too. When weeks are the base level time period, please make sure that you have set up the Tax Provision Blueprint scenarios with the correct “Input Frequency”. You will notice that even though you have selected a correct Cube POV, the time selection will allow you to go down to the “weekly” level. This is normal OneStream behavior but could impact how cube views render. We have created a parameter called “Tax_BaseLevelTimePeriods_TXP”. It is a literal parameter that holds the lowest level time period that is used in Tax Provision Blueprint. This parameter would need to be updated if you are using an input frequency other than months. Possible time extensions are: Base (represents the base level time periods defined in the time profile) Weeks Months Quarters HalfYears Here is an example of how this parameter is used in a cube view. This eliminates the need to update several CV’s. Normally, we would use the extension “.Base”, however this will show the weekly time periods, which will result in invalid cells. Using “.Base” with a weekly time profile (scenario is defined as “Monthly” input): Using “.Months” or the parameter |! Tax_BaseLevelTimePeriods_TXP!| (scenario is defined as “Monthly” input): Another area to consider is BR’s syntax. Here is one specific syntax that needed to be updated when weeks was defined in the time profile:Activating the "In Use" Metadata Feature
Here we will show you how to inactivate an account as of a certain time period. This alleviates the need to delete or move an account, especially if there is historical data. Also, if you are unsure about deleting an account that could have BR’s impacts, the “In Use” feature could be a valid option. In Use applies to the following dimensions: Entity Account Flow UD1 - UD8 Entity - In Use If set to True, the Entity is in use, if set to False, this can turn off the ability to use an Entity based on Time. This keeps historical data available. This is designed to be used when an Entity becomes inactive or is sold. Once an Entity is no longer in use, it will be ignored during consolidation and all intersections including this Entity will be invalid. Account - In Use If set to True, the Account is in use, if set to False, this can turn off the ability to use an Account based on Time. This keeps historical data available but allows the ability to close the Account without having to have No Input rules. Flow – In Use If set to True, the Flow is in use, if set to False, this can turn off the ability to use a Flow based on Time. This keeps historical data available but allows the ability to close the Flow member without having to have No Input rules. UD1 – UD8 If set to True, the UD1-UD8 is in use, if set to False, this can turn off the ability to use a UD1-UD8 based on Time. This keeps historical data available but allows the ability to close the UD1-UD8 member without having to have No Input rules. Member Expansions - InUse A#Root.Children(InUse=True) filters the results to only the Members in use. Example: Let’s activate the “In Use” for account TXP_PD0005. So, starting in July 2020, we want this account to be inactive, meaning “In Use = False”. Starting in July 2020 and all future periods, this account is inactive (until it is re-activated at some future period). Here is how you would do that. Let’s look at schedule 5 for the June and July 2020 periods. June 2020: July 2020: Notice how the account shows with a pink background – meaning it is invalid. By right clicking and selecting Cell Status, you can review key stats for the POV: Now let’s say you do not want the invalid account to display. You can adjust the cube view account member filter by using the following syntax: .Where(InUse = True) So, in our example, adjust the account member filter as follows: Let’s look at schedule 5 again for the June and July 2020 periods. June 2020: Account TXP_PD0005 shows up in the schedule July 2020: Account TXP_PD0005 is removed from the schedule as it meets the “In Use = False” condition.Security
The following has been taken from the Tax Provision Blueprint "Instruction Guide" starting at page 215. See KB article: "Tax Provision Blueprint Instruction Guide - PV7.3.0 SV100" Security Tax Provision Blueprint will need to have additional Security Groups added to the OneStream Framework for each environment where Tax Provision Blueprint is used. The Security Groups are used to provide user access to Tax Provision Blueprint and the Workflow structure for the solution. The only place where standard security has been set up is in the Maintenance Group of objects. These are set to Administrators. All other security options are left at the “out-of-the-box” defaults. We have not created any security groups. Note: Creating and assigning security groups will be required for every implementation.Dimension - Flow
The following has been taken from the Tax Provision Blueprint "Instruction Guide" starting at page 84. See KB article: "Tax Provision Blueprint Instruction Guide - PV7.3.0 SV100" See KB article: "Dimension Member Names - Renaming and Deleting" See KB article: "Dimension Text Fields - Summary" Flow XFW_TXP_Flow is the Tax Provision Blueprint Flow Dimension that holds the flow structure for the tax provision calculations, including the Deferred Tax Roll Forward Gross Closing and Tax Closing rollups. Flow Notes Text 1 Property is used to identify Discrete flow members. Any base level flow member that is classified as Discrete must have the Text 1 property of Discrete=Yes. Parent flow members where all children are Discrete should also have Text 1 Discrete=Yes. This is used to drive Parameters, BR’s, etc. Switch Type for activity type data. Alternate hierarchies are used. Aggregation weights are used. No Member Formulas are used. See the Finance BR TXP_BusinessRules. All parent members must have the word Total in the description. This will help in the formatting of the Cube Views: When referencing TXP_TopTax for Flow, TXP_TaxClosing will be the subtotal that is displayed. TXP_GrossClosing and TXP_OtherFlow have an Aggregation Weight of zero assigned. The screen shot below is a partially collapsed view of the Flow Dimension with the Schedules listed that are associated with members. Do not change any of the Flow Member names included with Tax Provision Blueprint. TXP_GrossClosing & TXP_TaxClosing Setup Notes TXP_GrossClosing contains the Gross activity data for the Deferred Tax Roll Forward. TXP_TaxClosing contains the Tax Effected activity data for the Deferred Tax Roll Forward. This is also differentiated via the UD2 member. The only difference between the Gross and Tax Flow hierarchies is the TXP_RCTotal Parent and Children. These members hold the Rate Change Impact data which does not exist for Gross data. TXP_OtherOpenAdj_Dscr, TXP_TotalDefOther_NonDscr, TXP_TotalDefOther_Dscr and TXP_TotalDefBSO: Base members may be added. If the expected calculations for a new base member are the same as the siblings, no business rule modifications are required. A new base member for any of these parents will also require a similar member to be added to the TXP_TaxLCTotalCF hierarchy. E.g.: Add TXP_DefOther3 as a child of TXP_DefOther_NonDscr. Add TXP_TLCDefOther3 as a child of TXP_TLCDefOther_NonDscr. TXP_AdjOpeningBal_NonDscr: Add new base member (e.g., TXP_DiscAdj with a Non-Discrete classification) requires updates to metadata, BR’s CV’s, etc. New Flow Member required for TXP_TaxLCTotalCF Add TXP_TLCDiscAdj as a child of TXP_TLCOpeningAdj_NonDscr. Rules for Schedule 06 will need to be updated. Update alternate flow hierarchies referenced in Business Rules: Add TXP_DiscAdj as a child of TXP_ActivityTax, TXP_ETRNatBenOther, TXP_ETRLocalDefExpOther, TXP_ETRLocalVA. Add TXP_TLCDiscAdj as a child of TXP_ActivityTLC. No Input business rules may need to be modified. Update Business Rules in section Schedule05_06_PartB (this is related to the National Benefit and Schedule 6b TXP_DefLocal account tax calculation). New account required for Tax Account Reconciliation (TXP_TxRAccountRecon). Most likely this should be added as a child of TXP_TxRAdjustedOpeningBal (e.g., TXP_TxRDiscAdj). Rules for Schedule 07 will need to be updated. Add new account required in the alternate hierarchy TXP_ETRVATotal as a child of TXP_ETRVA_NonDscr (e.g., TXP_ETRVADiscAdj). Business Rules for Schedule 08 & Schedule 09 will need to be updated. Add new account required in the alternate hierarchy TXP_ETRDeferredTotal as a child of TXP_ETRDeferred_NonDscr (e.g., TXP_ETRDiscAdj). Business Rules for Schedule 08 & Schedule 09 will need to be updated. TXP_CYPL: Add new base member (e.g., TXP_CYOther with a non-discrete classification as a sibling to TXP_CYProvision). New Flow Member required for TXP_TaxLCTotalCF as a sibling of TXP_TLCExpiration (e.g., TXP_TLCCYOther). Business Rules for Schedule 06 will need to be updated. Update alternate flow hierarchies referenced in Business Rules: Add TXP_CYOther as a child of TXP_ETRNatBenOther, TXP_ETRLocalDefExpOther. Add TXP_TLCCYOther as a child of TXP_ActivityTLC. New account required for Tax Account Reconciliation (TXP_TxRAccountRecon). Most likely this should be added as a child of TXP_TxRDefProvision (e.g., TXP_TxRCYOther). The Business Rules for Schedule 07 will need to be updated. New account required in the alternate hierarchy TXP_ETRVATotal as a child of TXP_ETRVA_NonDscr (e.g., TXP_ETRVACYOther). Business Rules for Schedule 08 & Schedule 09 will need to be updated. New account required in the alternate hierarchy TXP_ETRDeferredTotal as a child of TXP_ETRVA_NonDscr (e.g., TXP_ETRCYOther). Business Rules for Schedule 08 & Schedule 09 will need to be updated. No Input business rules may need to be modified. Metadata, BR’s, CV’s, and other objects will need to be updated. Total Tax Loss/Credit Detail (TXP_TaxLCTotalCF) This alternate hierarchy contains data related to Tax Attributes: Losses and Credits. This data can be tracked by the year that the Attribute was created. The Total of each Loss and Credit account is copied to the TXP_GrossClosing equivalent member via Business Rules.