Forum Discussion

mjohnson's avatar
mjohnson
New Contributor III
2 years ago

Cube Suffix and moving workflows

We are setting up TXM/RCM and would like to have the workflows in a separate Cube View Workflow Profile.  We have added a suffix to the appropriate scenario types on the cube setup and created the de...
Workflow
  • T_Kress's avatar
    T_Kress
    4 months ago

    If I am understanding your ask correctly, you have a cube where only the Actual scenario type has been used so far.  And there is no suffix on the Actual scenario type.

    Now you want to utilize the forecast scenario type, which is net new and no data so far.  Yes, you can add the suffix for Forecast/Budget scenario type to the cube, assuming they have not been used before.  They will appear under a different cube root workflow profile from Actuals, which I think is what you want.

    That should work.

mjohnson's avatar
mjohnson
New Contributor III

Thanks!  We'll do some testing in our sandbox and try this out.

Gaurav's avatar
Gaurav
New Contributor III
4 months ago

Hey,

I know it's an old post, but did it worked out for you?
We've similar situation where there are no suffix added to cube and we're using existing workflow profiles for Actuals only so far.

Now, we want to expand this cube so that we can have separate cube root workflow profiles for forecast. There's no data activity to any other scenario until now.
Can we just add suffix for Forecast/Budget type scenario now and create cuberoot WF profiles?  

Thanks,
Gaurav

  • T_Kress's avatar
    T_Kress
    Contributor III
    4 months ago

    If I am understanding your ask correctly, you have a cube where only the Actual scenario type has been used so far.  And there is no suffix on the Actual scenario type.

    Now you want to utilize the forecast scenario type, which is net new and no data so far.  Yes, you can add the suffix for Forecast/Budget scenario type to the cube, assuming they have not been used before.  They will appear under a different cube root workflow profile from Actuals, which I think is what you want.

    That should work.

    • Gaurav's avatar
      Gaurav
      New Contributor III
      4 months ago

      Thank you Teresa,
      I tried in lower environment and it worked fine! 🙂

      I was wondering if it'll impact anything in our existing process of Actuals?
      I read somewhere in documentation that cube suffixes should be added at the time of creating cube.

      Regards,
      Gaurav

      • T_Kress's avatar
        T_Kress
        Contributor III
        4 months ago

        It should not create any issues with the Actual scenario type.

        Ideally, the cube setup should look like this, Default having assigned just Entity and Scenario.

         

        Then if you click on Actual it should have the dimensions that Actuals uses assigned for Account through U8.

        Then you will go down to "Forecast" scenario type and pick the dimensions you want that scenario type to use, and assign them for that specific scenario type.  It should let you do this because Forecast scenario type has no data.

        Then assign your suffix for Forecast and you should be good to go.