This problem can occur if the sequence number is duplicated in the data model. Check if any two aggregate tables have same sequence number and provide them with unique numbers. This should resolve the problem.
All aggregate tables specified in the 'dbmodel.xml' have to be given a unique sequence number in order to apply the order of execution. And sequence is not just the running number for all tables; it has to be grouped by data mart. Please contact ARC ...
Once store Hierarchy is selected, then select the levels/attributes of the store hierarchy. Now click on 'save' that appears at the bottom of the page (scroll down). With this, you can view the levels/attributes within the selected hierarchy. This is ...