" /> Data Transfer Problem in WFM - Genesys CTI User Forum

Author Topic: Data Transfer Problem in WFM  (Read 3573 times)

David Sharon

  • Guest
Data Transfer Problem in WFM
« on: January 01, 1970, 12:00:00 AM »
Advertisement
Hi to board...

We have installed and completed to configure the WFM ver5.1.6x.
Up to this point, there was nothing wrong with WFM. After
collecting data about a week, we tried to forecast, but it
has failed!

Well, I have checked and confirmed that WFM StatServer and
DataAggragator working propery. Plus, using the Oracle
monitoring and reporting tools, it was also verified that
the data has been collected through the DataAggregator.
Namely, we have no problem either with the data collected
in the database, or our applications.

So good, so far...

I could get the two or threedays forecasts, but -despite
of having collected data for 10 days- I couldn't do it
for a week! It yields in the following error:

"There is no enough data, or error in opening hours".

To check and verify that our WFM configuration was okay, or
not, the related data has been imported from our PBX, and
we have tried and observed that it worked!

So, here is the question: what is the point at which we made
a mistake? (or, why me worry!)

Huh! Any comment?

David.

Nick

  • Guest
Data Transfer Problem in WFM
« Reply #1 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • Hi David,

    I seem to be suffering from exactly the same problem, although I have been able to get a forecast displaying AHT for a given period, but not for call volume. I have imported an entire year's worth of historical data for call volume & AHT for each of the four activities registered on our switch, but cannot get WFM to produce a forecast for call volume for any period, for any activity. I receive exactly the same error message as yourself.

    Did you ever get to the bottom of this?

    Regards

    Nick Tadd

    Vic

    • Guest
    Data Transfer Problem in WFM
    « Reply #2 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • Nick, David
    There could be several reasons... Instead of listing all of them here, why not try the most obvious one!

    The most obvious one is timezone. Have you made sure that you have the correct timezone setup? My initial guess would be that...

    Tell me if it worked!
    Vic