Importing Journal Entries

Importing Journal
We can import journal entries from subledger such as Oracle Receivables and Oracle Payables, Loans etc. Importing journal entries is a function performed by the Journal Import Program.
Most Oracle Financials subledgers post their accounting journals into an interface table called GL_INTERFACE. The Journal Import program reads the records in this interface table and processes them into GL's production tables, creating journal entries with batches, Journals and Journal lines. There are two exceptions to this ;

Oracle Assets posts its accounting journals directly into GL's production tables bypassing the interface tables.
Oracle Purchasing Encumbrance journals also post directly into GL's production tables bypassing the interface tables.

The other subledgers all go through the interface table, and they generally provide an option to run the Journal Import program automatically after posting the accounting entries to Oracle General Ledger. If Journal Import is not set to run automatically after the subledger transfer, we must run Journal Import manually. We can do this by navigation path
Journals/Import/Run
This will call up the import journal form, in this form we start by selecting the journal source we want to import. One easy way to do this is to execute the Edit/List of Values menu command, which will produce a list of valid journal sources. We can select a source and then click on the OK button to have it placed into the Source column in the Import Journals form.
Some Journal sources, such as Oracle Receivables, send journals to Oracle GL in groups. When importing Journals from such sources, we must select the group id.(Group IDs are assigned automatically by subledger and are used to subdivide ther interface journals into separate batches. Different subledgers have different rules in deriving group IDs some subledgers do not even use a group, and just send the journals as a single large batch). The import journals from include checkboxes offering two different run options:

Post Errors to Suspense-Causes the Journal Import program to balance journals by posting the difference between debit and credit amounts to a suspense account. We can only select the post errors to suspense option if suspense accounting is allowed at the set of books level. Suspense accounts can defined at the Set of Books level or overridden by the Journal source and Journal Category combinations. If post Errors to Suspense is not enabled the Journal Import will reject any unbalanced journals.
Create Summary Journals- the Journal import program to add journal lines together (summarize them ) by accounting combination, currency, and accounting period. The detailed journal lines are retained in our journal source if it has been configured to keep import journal references. Selecting the Create Summary Journal option disable to import of descriptive flexfield information.

Correcting Journals
If the Journal Import Program report import errors, we can correct data in the interface table and rerun journal import. This will require one of two different approaches, depending on where the erroneous data came from :
If the problem data cam from Oracle Subledgers, we must fix the problem in two places: their source and the interface table. This is because Oracle Subledgers wil not retransfer journals to the interface table. So after we fix the source and essential step because the problem is likely to occur again next accounting period if the subledger is not fixed we must still correct data in the interface table and rerun journal import.

If the problem is related to how Oracle GL is set up for instance a segment value being disabled or an accounting period not opened you can simply fix the GL setup and rerun Journal import.

If we do need to correct records in the interface table directly , we can do so by following the navigation path
Journals/Import/Correct
This causes two forms to appear: the Correct Journal Import data form is in the background, while the find Journal Import Data form opens in the foreground. Using the find journal import data window, we can specify a wide variety of search criteria; the desired status (the error code error or corrected), Journal source application, transaction category , accounting date range, journal type (actual, budget, encumbrance), currency, and group IDs range.
Once we have specified the Journal Import data we wish to find, we are returned to the Correct Journal Import Data Form. The bottom portion of this form is capable of displaying five different sets, or regions of data : batches/Journals, accounts journal lines, descriptive flexfields, and references. We select the region we want by choosing it from a drop down list. Select appropriate region from list, correct the problem save.

Deleting Journals- We can delete journals using the delete/journal/import data form , which is available via the navigation path journals /import/delete. We can specify the journal source application, the concurrent request that corresponds to a journal import run, or a group ID.

************IMP**********
This procedure must be used with extreme caution: remember that Oracle Sub ledgers Will no re transfer. We should use this step only if the data is from a source that be required, such as a data conversion or another interface that can regenerate and reinterface the accounting entries.