Best Practice to combine two or more model data into one output model

AdamSayyad
edited August 14 in Modeling

Hello Team

As project requirement I need to combine information from two different model (i.e. Actual Payroll information and Plan Payroll Information)

In different model have calculated this information since calculation is different and in plan payroll end user will make the changes. List used in both models are number list.

Module No 1 - STP05 I Payroll Planning (Actual)

Module No 2 - STP06 I Staff Planning (Plan)

Output Module - REP02 I Sal Combined

To combine Model, I have followed below steps.

1. Cratered Code in both source model

2. Loaded this Code into New Sal_Comb list

3. In source module added one line item which is finding list item from this new list using FINDITEM function.

4. In output model updated formula for Amount line item based on version (Actual or Plan)

I am getting correct result for Amount in output model. Similarly, I am thinking to update formula for rest of column to get the result from both source model.

Is it right approach, which is followed above, or we can simply crate action to update number directly from Both Source Module, using Sal_Comb list into output model? .

Could you please advise which option is best practice, any other suggestion apart from mentioned above is also welcome 😊

Regards,

Adam S.

Answers

  • Hi AdamSayyad,

    The current solution you have implemented is correct. However, the second solution you suggested, which involves importing data instead of using formulas, would be more efficient in this case, under certain assumptions.

    Assumption 1: If the data changes infrequently in this use case, importing would be the best solution. This eliminates the need to write formulas, which would increase the processing power of Anaplan and make the model less resource-intensive.

    Assumption 2: If the data changes frequently for both actual and plan, and the output needs to be highly dynamic, I would recommend sticking with the current solution. Running the process every time would add an extra burden for the user.

    Hope this help!

    Thanks,

    Arnab