Cube Suffix and moving workflows

[mjohnson]

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 default Cube View Workflow Profile for this new cube suffix.  However, the customer already has some workflows that are being used in the original cube.  Is there any way to move these to the new profile?  We know we can get it to work if starting clean, just not sure if it's possible to do anything with what they already have set up.

[SamRichards]

Hey MJohnson,

I am assuming you are meaning the Cube Root workflow profile not the Cube View workflow profile is that correct? Are you setting up RCM/TXM in a new cube or adding them onto an existing cube? The workflows profiles that already exist are they on the suffix you have created or is the ask if you can move all of them over to the new suffix. I apologize, I am not sure I am understanding your question.

Thanks,

[mjohnson]

Yes, sorry Cube Root workflow profile.  We have not set up the suffix yet and they have workflows they are already using for TXM (including a data splitter).  This is in an existing cube.  We were hoping to be able to add the suffix to these scenario types and then move the existing workflows.  We did some testing and it looks like we won't be able to, but wanted to see if anyone else ran across this and had a solution.

[SamRichards]

Ok, yea I understand now. Yea it is always better to setup the suffix when the cube is first spun up.  One way around it would be If you created a new scenario in the cube as assigned it an unused scenario type then create the suffix on the cube, you should be able to single out TXM on that workflow. When you go to move the workflow, you will probably have to do it in the XML to expedite the process or you could recreate it. You would really want to test this to make sure TXM would still be functioning like you wanted but I am not sure if this is a viable solution for you.

[mjohnson]

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

[Gaurav]

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 · Accepted solution]

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]

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]

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.