Sie sind auf Seite 1von 5

How To Guide

X3-F9 Interface

Overview ......................................................................................................................................... 2
Executing the X3 to F9 Interface .................................................................................................... 2
Executing the Datapump to move data into F9. .............................................................................. 4
X3 to Datapump Common Errors ................................................................................................... 5

May 2010 Sage Page 1 of 5


X3-F9 Interface

Overview
The F9 Interface creates the ability to take GL data and populate the necessary tables read by F9. When
journals are updated in X3, the F9 interface must be executed to refresh the F9 tables.

Note: Please refer to document INS-X3-F9-Interface-XA09-Vx for questions about the installation
process. This is required if you create new folders and want to use F9 in that folder.

Executing the X3 to F9 Interface


The F9 Interface function can be found on the ADMIN menu under Financials > F9 Interface > F9
Interface V6. The purpose of the F9 interface is to collect data into a set of tables accessible by the F9
Datapump.

May 2010 Sage Page 2 of 5


X3-F9 Interface

After selecting the F9 Interface-V6, you have the ability to select which ledger will be processed from X3
to F9. By default and generally this is the legal ledger type as shown below.

Select Ledger Type

Once the F9 interface runs, data is written to the F9 tables, which is then read by the Datapump. The
interface log if successful with journals will look like the following:

Database server specific. It is


either Sql Server or Oracle
information.

X3 Information on the database


X3 is using.

The X3 Interface run


information. There are 3 main
information transfers:
a) Actual financial data
b) Budget data
c) Reference data, e.g. account
segment descriptions
Note: errors are highlighted in
red if they occur.

May 2010 Sage Page 3 of 5


X3-F9 Interface

Executing the Datapump to move data into F9.


Under the Windows Start/Programs/F9 menu will be an application called Datapump. Select the
Datapump application to start and information similar to the following should appear on your screen. The
differences between what is shown below and what your datapump is displaying should be related to
setup. For example, TESTV6 will be replaced with your folder information.

If the information does not look correct, then selecting the Edit option, as shown above, will allow you to
individually change values related to the datapump.ini file.
Select Start and it should run to completion with no errors and the following message will be shown.

If errors have occurred, these errors must be resolved. Rather than seeing the message below, a
message that says, "There has been an error running the DataPump". These errors must be resolved
prior to continuing with the F9 Financial reporting. Some causes of common errors are shown at the end
of this document.

May 2010 Sage Page 4 of 5


X3-F9 Interface

X3 to Datapump Common Errors


Symptom Possible Solution

Cannot find Datapump program F9 not installed or incorrect version of F9 installed.

No valid datapump profile exists on the PC The F9 Reset Parameters and F9 Copy Setup to
PC utilities have not been run. Generally, re-
running these applications for the folder that you
are trying to interface to F9, will correct the issues
shown here. However, if you have manually made
changes to the datapump.ini or X3V6.ldi file, these
files should be copied to other filenames prior to re-
running these applications as these applications
will create new datapump.ini and X3V6.ldi files.
Please refer to the INS-X3-F9-Interface-XA09-Vx
on how to execute these functions.

Datapump log has message "Login failed for user" Connecting to a new or incorrect folder.
ODBC connection not defined correctly for X3
New X3 Runtime installed with new database and
new odbc connections.

Datapump log has message "Invalid object name" Connecting to a new or incorrect folder. The owner
name is defined incorrectly the data source section
of the profile.

GL Numbers incorrectly formatted in Excel The Account Code structure is not correctly defined
in the datapump.

Datapump completes but log shows that no records Note, the table XBF9TXNV6 does not include any
have been written to the F9 tables. records in the X3V6 of the F9 interface. The value
of written records will always be zero for this table.
For the other two tables XBF9BALV6 and
XBF9SGDV6, there will be records written to F9. If
these two tables show zero records, re-run the F9
Interface application (GESXBF9) and verify there
are no errors that occur in that process.

Balances in F9 are missing certain journals. Make sure journals are not waiting to be posted
through the journal status monitor.

Unable to read account This message is given for asset accounts when
beginning balances are missing. Run Year End
simulation to rectify situation

Current Fiscal year not defined For legal companies, the current fiscal year must
be defined and opened.

May 2010 Sage Page 5 of 5