Forum Discussion

yashsolanki910's avatar
yashsolanki910
New Contributor
2 months ago

Scenario Type - Tax

Hi,

What are the major considerations that need to be looked at before making a design decision for implementing "Tax" Scenario Type? What are the pros and cons of using this Scenario Type vis-a-vis "Actual" Scenario Type? Is there any guidance/ knowledge post on the same?

Use Case: Want to integrate an erstwhile Tax application into OneStream Application where actuals are already available. The tax application has some additional tax related dimensions, rules, etc. which need to be used in OneStream. 

Cubes
Metadata
  • KarlT's avatar
    KarlT
    Contributor III
    2 months ago

    Hi, the naming of the Scenario Types are simply for organisation purposes (tax, actual, scenario type1 etc.) They are all "equal" in terms of what they offer.

    Some advantages of using a different scenario type to you Actual process would be:

    1. Allows different & extended dimensionality to be assigned.
    2. Can vary certain member settings by scenario type (i.e. the In Use property on the members)
    3. Can create completely different workflow hierarchies (in combination with workflow suffixes on the cube)
    4. Can easily vary member formula logic by scenario type.

    So for the high level tax requirements you mention above, it sounds like it could make sense to use a different scenario type.

    One thing that a different scenario type in the existing cube wouldn't allow, is a different entity dimension. So when that is a requirement you may need to look at separate cubes.

    This is a pretty high level summary and you should find plenty more information throughout the design and reference guide and our training materials.