It is my understanding that in a loaded measure the target information to be loaded must be in the same table as the actual data. The exception would be if the target is fixed and input during the measure creation.

unfortunately, in our ERP environment most tables do not contain targets. Therefore, what we have been doing is creating a duplicate or subset of a table from ERP and then uploading target values from Excel so that we have a data source containing both. This is time consuming and error-prone.

If would really be a nice enhancement to allow fixed target entry manually on a by-month basis, so that I could put in measure targets for the entire year, and then hit the ERP table just to get the actual value only. I don't know if this is in development or is even possible.

Any other suggestions for handling this situation in a more efficient way would be greatly appreciated.

Thanks in advance.

PMF 5.1.1

Targets are currently stored period by period. If your lowest level for a measure is months, they are stored month by month.

As for the fact that actuals and targets have to be "from the same table," they actually don't; they could come from separate sources; you'd JOIN the two sources together for a load. Or you could put them into an ODS.

Future PMF will allow separate sourcing of actuals and targets, but this is many months away.