Richard_Mayo - Here we Go!
When you are setting the unrelated entities to true then you are opening for all the entities to load. So I would recommed to use WF channel.
1. You can Set WF Channel with combination of UD's & Account dimension or just UD's
2. Create a Tax_Overlay as import step vs separate WF Profile. This way you can control the load using entity assignment and also tag the WF channel. It will be independent from your TB load, ex- When you lock the import step then tax will not be locked and still available for load. It can be controlled by WF security for accessing the group.
3. Step 2 will be applicable for Forms and ADJ as well.
Note: In OS there are multiple ways to solution it. One of the way to create a separate WF Profile and you utilize the entity Mapping to control the entity load. BTW if you create another scenario Type then you have to copy the data between the scenario's and it is more maintenance. Hope this helps.
Hi Krishna,
Thanks so much for your quick and detailed response!
Could I check a couple of things to ensure I've understood your suggestion:
So I would include a second import step in each of the "normal" workflows, and this second import step would be set to the "tax" workflow channels so it's differentiated from the standard import step - is that what you had in mind?
ie. a bit like the following screenshot where the first import step is the normal import and the second one is the tax import (the latter set to the tax workflow channel to keep separate from the first).
If that is the case could you just confirm how this would work in practice - wouldn't we still have the same issue of having to unlock/uncertify many "normal" workflows in order to utilise this additional import step? Also, would this methodology mean that the tax department would continue to load all their numbers in batch to a central workflow?
I do like the idea of having it contained in a workflow which can reference assigned entities as that would give us more control but I'm just not quite understanding how it would make the overall process easier. I am very interested to hear your thoughts!
Thanks for taking the time to share your ideas.
Regards,
Richard
Richard_Mayo - Yes the screenshot is correct. You will have two WF Import one for Normal Import and other one for Tax. Each has its own WF Channel. You can set the WF name either Import/Load or you can include Certify process. Now if you lock the import step it will not lock your Tax Import Step because of the WF Channel.
