We loaded/populated the following dimensions:
Time to 2012
AcademicOrgStruct fully loaded.
We created a couple of user entered measures linked to Time & AcademicOrgStruct.
When we choose the option to enter measure data, we receive the "No data found" message with "No matching records were found for your selection. Try again with different parameters."
Checking view source shows no errors, only the last hold result generated no records or lines.
Are we missing something, as there would be no previously created measure records, as we would now attempt to capture the first set.
Any pointers?

If the request for data at the final step isn't specifying the point in time, double-check the point in time at which the data was entered and compare it to the default Time setting in the Manage > Settings > System panel. If the currently selected time is something like "system clock time" and the data was entered only for another period of time, that could explain your mystery response. Try an Analysis Designer report against the measure specifying the widest possible time range to find your data.

Shoudl this not prove the answer, please open a case with customer support and we'll all help you further.

Thx for the response Bob.
It is a freshly created measure.
The time setting in the Manage > Settings > System panel is set to fixed time and the value chosen is 2011/10.
Now when I choose "Enter Measures" for the first time, I get the above mentioned "No Data" response...
Wait a minute...
Just double checked on my local laptop install, all working just fine.
Diffirence is, I'm running WebFOCUS 7703 64bit with PMF 5.2.3 HF3
The customer is on WebFOCUS 7702 (I'm not onsite to check if technical installed hotfixes, I suspect not).
Will double check 1st thing on Monday morning and will upgrade them to 7703.
Thank goodness this is not yet a production environment.
Will post an update on Monday.
Have a super weekend.
With kind regards from South Africa.

Today we upgraded WebFOCUS Server and Client from 7702 to 7703, as well as PMF 523 to HF3. The problem seems to be resolved as the enter measure data option now produces the expected input forms for each of the user entered measures.