Prior to importing an XML file, the system examines the file to confirm that the file is well formed. A well-formed file has no missing characters or extra characters. When the system finds missing or extra characters, it displays a detailed error message. To correct the problem, you need to fix the problem in the XML file, and attempt the import again.

Prior to importing, the system checks to see if the import will cause the creation of a duplicate JE number. When this event occurs, an exception report prints to inform the user of the issue and to offer information on how to correct the problem.

Prior to importing intercompany transactions, the system verifies that the source EntitiesCompanies have been set up on GL Intercompany Tab. If the system finds no setup, an exception report prints to inform the user of the issue and to offer information on how to correct the problem.

If the import is not successful, a report detailing errors displays in a PDF format and no records are imported. Use the print capabilities of PDF to print the report. The report lists the name of the field in the import file that is in error, the value of the field, and the action required to correct the problem. The report can include any of the following errors, depending on the report:

• Need to setup this EntityCompany in eFinancials.
• No blank accounts can be imported.
• Account does not exist for this EntityCompany/Account in eFinancials.
• Account is not currently active in eFinancials.
• Account must be set to a type of detail in eFinancials.
• Post Period does not exist in the calendar for this EntityCompany in eFinancials.
• Journal date cannot be used.  This date falls within a closed period.
• Journal date cannot be used.  This date falls within a inactive period.
• There is no period defined for the journal date.  Check your calendar setup.
• One or more EntitiesCompanies in this journal is missing a G/L calendar. Check the EntityCompany setup.
• Journal date is outside your allowable posting range (User Policy Setup).
• Next JE Number in Global Policies needs to be updated before importing
• Intercompany Setup not found for this Source EntityCompany.
• Debits must equal credits for all EntitiesCompanies (Select Create Intercompany Transactions or Change Global Policy to Allow Import of Incomplete JEs to process file)"
• Debits must equal credits for this EntityCompany, check GL Intercompany setup"
• At least one of the EntitiesCompanies in the import file is not valid for the Current Batch/EntityCompany Restriction. Select a different batch or create a new batch to import the file.
• AmtToGL must not have more than two digits to the right of the decimal.
• EntityCompany is set to not allow posting in EntityCompany Setup.
• Track Unit must be turned off for this Account No/EntityCompany in GL Account Setup to import this file.
• Cannot import a journal entry for a profit account type in eFinancials.

Note

GL transactions cannot be imported for accounts for which the totals are tracked by unit (the Track Unit check box is selected on the Account Maintenance Tab). When applicable, the GL Transactions Import Exception report lists any accounts which could not be imported for this reason.

 

Copyright © 2018 Infor. All rights reserved. www.infor.com.