Importing Journals
Journal Import creates journal entries from accounting data you import from Oracle and non-Oracle feeder systems. You can review, change and post imported journal entries the same as any other journal entry. Journal Import supports multiple charts of accounts, as well as foreign currency, intercompany, statistical, budget, and encumbrance journals.
Journal Import creates journal entries from data in the GL_INTERFACE table. Oracle feeder systems automatically populate this table. If you are using a non-Oracle feeder system, you must populate this table yourself.
General Ledger validates all data in the interface table before creating journal entries.
Note: For increased security and faster processing, Journal Import only processes accounting data for the set of books that you are logged into when you submit your request.
Multiple Reporting Currencies
If you use Multiple Reporting Currencies and Oracle subledger systems, and have chosen not to run Journal Import automatically when posting amounts to General Ledger from your subledgers, you must run Journal Import manually in your primary set of books and in each of your reporting sets of books.
Note: When you post a batch that was imported from an Oracle subledger system to your primary set of books, General Ledger does not create a duplicate journal in the reporting sets of books as it does for manually entered journals.
Prerequisites
Populate the interface table if you are importing from non-Oracle feeder systems.
Define the Journal Import setup options to optimize performance for each set of books.
To import journal entries to General Ledger:
1. Navigate to the Import Journals window.
2. Enter the Source from which you want Journal Import to create journal entries.
3. You can import data for the same or different sources in parallel by specifying a unique Group ID for each request. General Ledger imports data with the journal entry source and group ID combination you specify.
If you do not specify a group ID, General Ledger imports data from the specified journal entry source with no corresponding group ID.
4. Define the Journal Import Run Options.
5. Choose whether to Import Descriptive Flexfields, and whether to import them with validation.
If you choose not to create summary journals, you can Import Descriptive Flexfields along with your journal information. You can import descriptive flexfields With Validation and generate journals only when validation succeeds. Or, you can import descriptive flexfields Without Validation and generate all journals.
Warning: Importing descriptive flexfields without validation may cause problems when modifying journal lines. If you import descriptive flexfields with errors, you may corrupt the journal lines to which they refer.
6. Enter a Date Range to have General Ledger import only journals with accounting dates in that range. If you do not specify a date range, General Ledger imports all journals data.
7. Choose Import to submit a concurrent process to import journals. General Ledger names the resulting batch as follows: <REFERENCE1> <Source> <Request ID>: <Actual Flag> <Group ID>; for example, 587-C Payables 18944: A 347.
8. Review the Journal Import Execution Report to determine the number of errors in the import data, and how to correct any Journal Import errors.
- If you have only a few Journal Import errors, correct the errors from the Correct Journal Import Data widow, then rerun Journal Import on the corrected data.
- If the number of Journal Import errors is high, delete all of the import data for your journal entry source and group ID. Correct the errors then repopulate the GL_INTERFACE table before rerunning Journal Import.
See Also
Integrating General Ledger Using Journal Import
Setting the Journal Import Run Options
Defining Journal Sources
Journal Import Execution Report
Correcting Journal Import Data
Deleting Journal Import Data
Setting Concurrent Program Controls
