Easy Excel Interface

ODBCFAce Challenge

With ERP systems, legacy databases or XML pages

The easiest ETL tool on the market

  Unleash The Power of Excel for your ERP implementation  

 

 

 

The Challenge

 

JD Edwards Upload exampleYou are getting ready to implement the procurement and inventory modules of your Enterprise Resource Planning system (best practice demands it).

 

All of a sudden you are facing tedious conversion tasks for numerous data elements (items, vendors, accounting instructions, etc.) that you need to upload into your system before the go live date.

 

How are you going to interface your information from your legacy system to the new JD EdwardsSAP, Oracle, BAAN, PeopleSoft or other ERP system you selected?

You could hire temporary help to manually input all of the information into the new system, screen after screen.

 

Alternatively, you could use programming resources to develop quick and dirty programs to populate your Data Base Management System from your Legacy System database.

 

On one hand, you are handing out your data to temporary help that are unfamiliar with your data or your Conference Room Pilot strategy.  On the other hand, you may jeopardize your implementation by counting on Information Technology resource availability (and we all know how plentiful they are) or on costly consultants.  No matter what, your go live date and the quality of your implementation are at risk.

Excel Upload to F4101 example

The real shame is that your super users have already prepared and organized all the information in the tool that they feel most comfortable with: Excel.

 

If only there was a way to transfer all that information into your ERP with a simple Excel upload...

 
Home | Product

Windows, Windows 98, Windows NT, Windows 2000, Windows XP, Excel, Excel 97, Excel 2000, Excel 2002, UDA, OLE DB and ODBC are registered trademarks of Microsoft Corporation in the U.S. and other countries used under license.
IBM, J.D. Edwards, SAP, Oracle, BAAN, PeopleSoft are registered trademarks of their respective owners.
All other trademarks are owned by their respective owners.

02/01/2003