Hi,

in FDMEE you have the functionality to load multi-period files.

Multi-period files can be text files or Excel Files

I haven't tested with Excel file yet so I cannot provide detailed feedback.

It's working fine with txt files having multiple columns for periods.

Unlike FDM classic, multi-period files loading is configured in import format and data load rule. You have all details in the admin guide.

The details that Francisco mentioned are definitely there. If you search for 'multiple period' in http://docs.oracle.com/cd/E40248_01/epm.1112/erpi_admin_11123510.pdf (or the older http://docs.oracle.com/cd/E40248_01/epm.1112/erpi_admin.pdf) you will find the details on setting up loads for multiple periods from flat files.

Regards

Craig

What I see here is that your import format is named "Multi" but the import format you assigned to your DLR is "Import" which I don't know how is configured.

You can see how you don't have amount columns in Source Periods panel. You should see them so you can select period for each column or leave them empty if periods are contiguous.

The SQL error you get is 99% related to this issue.

Did you review ERPIntegrator0.log?

The SQL is related to issue converting varchar to datetime.

What do you see if you run the following queries in SQL tool (i.e: SQL Management Studio)

SELECT PERIODESC, PERIODKEY, PRIORPERIODKEY FROM TPOVPERIOD

SELECT * FROM TPOVPERIODADAPTOR

Please use the FDMEE database user to run the queries.

Hi,

tables are not really saying anything.

Please, go to data load rule so you see the error.

Then attach the ERPIntegrator0.log (which is the FDMEE Server).

Also, did you run the queries I posted?

SELECT PERIODESC, PERIODKEY, PRIORPERIODKEY FROM TPOVPERIOD

SELECT * FROM TPOVPERIODADAPTOR