Recent Content
Sample Excel Formulas
Attached is a 4 tab Excel file that has many sample Excel formulas. It shows you how to reference the 18 dimensions in order to pull or push data as well as pull in metadata attributes. Areas of examples include: XFSetCell / XFGetCell / XFGetMemberProperty / XFGetRelationshipProperty / XFGetMemberInfo. This is an excellent file to help you get up and running quickly using Excel formulas.0likes1CommentData 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.0likes0CommentsDimension 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 UD80likes2CommentsWorkflow Profiles
The following has been taken from the Tax Provision Blueprint "Instruction Guide" starting at page 149. See KB article: "Tax Provision Blueprint Instruction Guide - PV7.3.0 SV100" See KB article: "Workflow Templates" Tax Provision Blueprint includes several Workflow Profiles related to the included Tax Provision Blueprint Cube. OneStream Workflows are a key benefit of building a tax provision process using Tax Provision Blueprint. The ability to create Workflows that tailor the users experience to their specific responsibilities and show the status of the completed Workflow task is a key differentiator of Tax Provision Blueprint. Workflow is expected to be customized to address individual customer requirements. Workflow Profiles XFW_TXP is the Root Workflow Profile for Tax Provision Blueprint. Workflows are set up by country. You can have several workflows within a country, however, entities assigned to a workflow MUST be in the same country. Only one Local Group Filer workflow profile can exist per country. Only one National Group Filer workflow profile can exist per country. Naming conventions are key to understanding what each workflow is supposed to represent. We have used suffixes on our workflows. Review the supplied Excel supplemental file that has a very informative matrix about the workflow setup. Please see KB article: "Workflow Profile setup - Actual & Forecast". Here is a screenshot of the supplied workflows: Profile Properties All settings should be applied to the “Tax” scenario type. If you are using current year Forecast scenarios, use the scenario type “ScenarioType8”. If you are using multi-year Forecast scenarios, use the scenario type “ScenarioType7”. They should be applied to both the base level parent workflow and at the base level Tax Schedules workflow. The following areas in workflows have been used in Tax Provision Blueprint: Base Level parent workflow: Workflow Name Cube View Profile Name Confirmation Profile Name Text 1 Text 2 Text 3 Base Level “Tax Schedules” workflow: Workflow Name Profile Active Input Forms Profile Name Cube View Profile Name Text 1 Text 2 Text 3 Tax Provision Blueprint makes use of the Substitution Text Settings Text 1, Text 2, and Text 3. These three text fields are used to drive the tax schedules POV, combo boxes parameters and business rules. Text 4 is left blank intentionally for possible non-Tax use or future Tax use. Workflow Text Field Notes Text 1 is only required when using group filing (either national or Local): GroupFiler can be either: National NatGroupFiler=Yes Local LocalGroupFiler=Yes Entity WF are specific workflow profiles to allow certain schedules for specific entities. There are 5 types of entity workflows: Nat_LocalGF see: XFW_TXP_US_107_Nat_LocalGF / XFW_TXP_US_117_Nat_LocalGF Used for countries that do not do National group filing but do Local group filing The entities in these workflows are filer entities (Text7: LocalFiler=Yes) The entities in these workflows can process the National and Local JD’s NatPrep_LocalGF see: XFW_TXP_CA_101_LocalGF / XFW_TXP_CA_102_LocalGF Used for countries that do National group filing and Local group filing The entities in these workflows are filer entities (Text7: LocalFiler=Yes and/or NatFiler=Yes) The entities in these workflows can only process the Local JD’s For the National JD only Schedules 05 and 06a are available and only the sections required for national preparation NatPrep see: XFW_TXP_CA_103_NatPrep / XFW_TXP_AE_101_NatPrep Used for countries that do National group filing Only Schedules 05 and 06a are available and only for the National JD NatPrep_Local see: XFW_TXP_LU_101_NoLocalGF / XFW_TXP_LU_102_NoLocalGF Used for countries that do National group filing The entities in these workflows can only process the Local JD’s For the National JD only Schedules 05 and 06a are available and only the sections required for national preparation <Blank> see: XFW_TXP_US_Eastern / XFW_TXP_DE_101 Used for countries that do not do either National and/or Local group filing Text 2 and Text 3 positions must be separated by a comma ( , ). No exceptions. You need to put in the dimension identifier (E#, U1#, U7#). This helps the admin to understand what dimension each text field represents. In BR’s, we remove the dimension identifier and the # where necessary. Do not Use Text 4. Leave open for non-Tax usage or for future Tax expansion. It is required to have an identifier on the workflow profile names (i.e., xxx_LocalGroupFiler, xxx_NatGroupFiler, xxx_Nat_LocalGF …). Confirmation rules looks to see if the profile name contains “LocalGroupFiler”, “NatGroupFiler”... Group Filing workflows will not have any entities associated too them. For Text 2, position one, you can specify one entity (i.e., E#TXP_US_107). The schedules will only display this entity in the POV combo box. So, if other entities are added to this workflow by mistake, they will not show up in the POV. The following are some sample screen shots of the different types of workflow profiles and the Text 1, 2 & 3 setup. XFW_TXP_Total This is the top-level workflow and is used to consolidate all entities. You are free to rename this workflow. Only one of these workflows is required per application. XFW_TXP_GLTaxAdmin This is the admin workflow and is used to perform monthly setup work including data copies and allows access to multiple jurisdictions in one workflow. Only one of these workflows is required per application. There are 9 base level workflows that are meant more for the Admin: Copy Definitions: TXP_Actual scenario – Dashboards to facilitate copying of group filing definitions. Forecast scenarios – Dashboards to facilitate the initialization and data copy steps for source (actuals) data copy to forecast. Schedules: TXP_Actual scenario – Dashboards to process bulk tax rates, manage by period the Interim Reporting Run Rate, set the return year, and set Losses not Benefited entities. Forecast scenarios – Dashboards to set Losses not Benefited entities and National Benefit excluded local jurisdictions. The next 7 country workflows enable an Admin user (1) enter tax rates, (2) set the RTP year (TXP_Actual only), (3) copy the Provision or Return data (TXP_Actual only) and (4) copy source data to forecast (forecast scenarios only). These 7 country specific workflows allow a user (i.e.: Admin or power user) to perform the monthly setup work from one workflow rather than going to several different workflows. Most of these same schedules are also available in each country’s workflow – so you can process the data in either area. Note: The Workflow Profiles for US (United States) in Tax Provision Blueprint are based on: National group filing: No Local group filing: Yes XFW_TXP_US_LocalGroupFiler This workflow is used to set up the Local group filing definitions for the country (US in this example). Only one of these workflows is required per country doing Local group filing. No entities are associated with this workflow. Only Local Jurisdiction data is entered for this workflow. Can Load Unrelated Entities = True. The words “GroupFiler” must be included in this profile name. XFW_TXP_US_107_Nat_LocalGF This workflow is used to do both Local Jurisdiction and National tax provisioning. You can have more than one of these types of workflows per country (US in this example). An entity is associated with this workflow. XFW_TXP_US_108 This workflow is used for National tax provisioning only (No National Group Filing). You can have more than one of these types of workflows per country (US in this example). An entity is associated with this workflow. The second position on Text 2 is not used, but we still include “,E#”. Note: The Workflow Profiles for CA (Canada) in Tax Provision Blueprint are based on: National group filing: Yes Local group filing: Yes XFW_TXP_CA_NatGroupFiler This workflow is used to set up the National group filing definitions for the country (CA in this example). Only one of these workflows is required per country doing National group filing. No entities are associated with this workflow. Only the National Jurisdiction data is entered for this workflow. Can Load Unrelated Entities = True. The words “GroupFiler” must be included in this profile name. XFW_TXP_CA_101_LocalGF This workflow is used to do Local Jurisdiction tax provisioning and National Jurisdiction preparation. You can have more than one of these types of workflows per country (CA in this example). An entity is associated with this workflow. XFW_TXP_CA_Eastern_NatPrep This workflow is used to enter data for schedule 05, 06a and 06a1 FC (FCST only) for National tax preparation. The country also has Local jurisdictions, but no Local jurisdiction provisioning is handled in this Workflow. You can have more than one of these types of workflows per country (CA in this example). An entity is associated with this workflow. Note: The Workflow Profiles for AE (United Arab Emirates) in Tax Provision Blueprint are based on: National group filing: Yes Local: No local tax provisioning XFW_TXP_AE_101_NatPrep This workflow is used to enter data for schedule 05, 06a and 06a1 FC (FCST only) for National tax preparation. The country also has No Local jurisdictions. You can have more than one of these types of workflows per country (AE in this example). An entity is associated with this workflow. Note: The Workflow Profiles for LU (Luxembourg) in Tax Provision Blueprint are based on: National group filing: Yes Local group filing: No XFW_TXP_LU_101_NoLocalGF This workflow is used to do Local Jurisdiction tax provisioning and National Jurisdiction preparation. You can have more than one of these types of workflows per country (LU – Luxembourg in this example). An entity is associated with this workflow. The second position on Text 2 is not used, but we still include “,E#”. Note: The Workflow Profiles for DE (Germany) in Tax Provision Blueprint are based on: National group filing: No Local group filing: No XFW_TXP_DE_101 This workflow is used to do both Local Jurisdiction and National tax provisioning but has no Group Filing requirements. You can have more than one of these types of workflows per country (DE – Germany in this example). An entity is associated with this workflow. The second position on Text 2 is not used, but we still include “,E#”. Note: The Workflow Profiles for UK (United Kingdom) in Tax Provision Blueprint are based on: National group filing: No Local: No local tax provisioning XFW_TXP_UK_101 This workflow is used for National tax provisioning only and has no Group Filing requirements. The country also has No Local jurisdictions. You can have more than one of these types of workflows per country (UK in this example). An entity is associated with this workflow. The second position on Text 2 is not used, but we still include “,E#”.0likes0CommentsSample Workflow Upload Template
Attached is a one tab Excel file that has a sample Workflow Upload template. It is OneStream's "Workflow Hierarchy Builder" that has been updated with sample Tax Provision Blueprint metadata. If you have a lot of WF's to create, this may be a good solution to assist you with creating workflows. Please test a small sample in a Dev app to make sure you are filling in all the proper fields based on your specific application.0likes0CommentsForm Templates
The following has been taken from the Tax Provision Blueprint "Instruction Guide" starting at page 147. See KB article: "Tax Provision Blueprint Instruction Guide - PV7.3.0 SV100" See KB article: "Form Template Groups & Profiles" Form Templates The Tax Provision Blueprint Form Templates are used for Tax Forms/Schedules and are used in the Workflow Profiles. Several Form Template Groups are used to break down the schedules into smaller groups so that several specific Form Template Profiles can be created and attached to the different types of workflows that are possible. All the Form Templates are of the Form Type “Dashboard”. Dashboards allow greater flexibility in how the schedules are rendered to the user.0likes2CommentsDimension - 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_Entities is 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_TXP0likes0CommentsConfirmation 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).0likes0CommentsParameters
The following has been taken from the Tax Provision Blueprint "Instruction Guide" starting at page 174. See KB article: "Tax Provision Blueprint Instruction Guide - PV7.3.0 SV100" See KB article: "Parameters - Manual Updates Required" Parameters As we mentioned at the beginning of the document, we use parameters extensively – in cube views, dashboards, reports, business rules, data management jobs to name a few. Extreme care should be used when making any modifications to the parameters. Parameters do not appear in alpha/numeric order. We have used the “Sort Order” to arrange them in a logical order. You can adjust the order of the parameters as you like. All parameters should be reviewed to make sure that the cube dimension, the entity dimension, and the entity name, the UDx dimension names represent what you have created in your application. If you use the exact same dimension names, then no changes are necessary. Here are the Dimension names that are used in Tax Provision Blueprint: Examples of things to look for and possibly change based on individual application set ups: The Cube name is used throughout the entire application. We recommend that you also use the cube name “XFW_TXP” in your application. The dimension names are used through the parameters. We recommend that you also use the dimension names that come with the Tax Provision Blueprint app. The Settings options that are selected and saved on the Setup dashboard are written and stored to several Literal Value parameters. These parameters are then used in BR’s and CV’s. The following literal value parameters are used throughout business rules, cube views and in other parameters. The following parameters have the return to provision scenario (TXP_ActualRTP) hard coded in the member filter: NationalFiler_ActualRTP_DM30b1_TXP NationalFiler_ActualRTP_DM20b2_TXP UD1_JD_20b2_TXP UD1_JD_30b1_TXP UD1_JD_MASTER_30b_TXP UD7_Sch30b_ML_All_TXP UD7_Sch30b1_ML_All_TXP There is a parameter called “Tax_Entities_SETR_TXP” that uses the “Where” clause. There is currently no option to use VaryByScenarioType or VaryByTime. It only looks at the “Default” scenario type. If you use the “Default” scenario type for this setting, then no modification to this parameter is required. If you cannot use the “Default” scenario type, then you will need to redefine the member list. We could have defined the member list as follows, but it is then hard coded to the application’s specific entities: E#TXP_Domestic_Total.TreeDescendants, E#TXP_Intl_Total.TreeDescendants.Remove(TXP_Europe_Total)0likes0Comments