OracleFree worksheetPDF, Excel, Word exportOracle E-Business Suite

Oracle EBS GL Journal Import Worksheet

Month-end journals often start life in a spreadsheet. This worksheet lays them out the way the GL_INTERFACE table expects them and proves that debits equal credits before anyone loads the file, so the Journal Import run does not come back with unbalanced or invalid account errors.

Download:
LineLedgerAccounting dateUser JE sourceUser JE categoryCurrencyCompany segmentNatural accountCost centerEntered DrEntered CrNet (Dr minus Cr)Line description
$18,500
-$18,500
$4,200
-$4,200
Total debits
$22,700
Total credits
$22,700
Out of balance
$0
Balance difference
$0
Must be zero for each journal before it is loaded.

Columns follow the idea of GL_INTERFACE (STATUS, LEDGER_ID, ACCOUNTING_DATE, CURRENCY_CODE, ACTUAL_FLAG, USER_JE_SOURCE_NAME, USER_JE_CATEGORY_NAME, SEGMENT1..n, ENTERED_DR, ENTERED_CR). Your load script must supply STATUS = NEW, ACTUAL_FLAG = A, ledger ID, created-by and date-created values, and your own segment layout.

Automate journal prep from ERP data

Optional conversation on generating and checking recurring journals from your ledger and subledger data.

Optional. The tool and every export work without this. No spam.

How to use the worksheet

Replace the example rows with your journal lines. Keep one journal per set of lines sharing the same ledger, accounting date, source, category and currency, because Journal Import groups on those values. The net column shows debit minus credit per line and the summary shows the total difference. Export to Excel or CSV, then hand the file to whoever runs your SQL*Loader or API based load.

How Journal Import consumes the rows

Rows are inserted into GL_INTERFACE with a status of NEW. The Journal Import program in the General Ledger responsibility reads them, validates the code combinations, periods and currencies, and creates journal batches in GL_JE_BATCHES, GL_JE_HEADERS and GL_JE_LINES. Rows that fail validation stay in the interface with an error status code, and you either correct them in place or delete them and reload.

  • Open period required for the accounting date
  • Segment values must form a valid, enabled code combination
  • Source name must exist in Journal Sources
  • Use a unique group ID to isolate a load

Common mistakes

Out of balance journals usually come from rounding in foreign currency or a forgotten offset line. Another frequent error is an accounting date in a closed period, which sends the whole set to an error state. Do not edit GL_INTERFACE directly in production without a controlled script and a backup of the rows, and always have a second person review the totals before submission.

Frequently Asked Questions

What table does Oracle EBS Journal Import read?

Journal Import reads GL_INTERFACE. After a successful run, the data moves into the GL_JE_BATCHES, GL_JE_HEADERS and GL_JE_LINES tables. Rows with problems remain in the interface with a status code describing the error.

Can I upload an Excel file straight into Oracle GL?

In EBS, the usual options are a load script into GL_INTERFACE, or the Applications Desktop Integrator (ADI) journal wizard. This worksheet helps you prepare and check the data first, whichever route you choose.

Why does Journal Import reject my rows?

Typical reasons are a closed accounting period, an invalid account combination, an unknown journal source or category, or an unbalanced set. Check the status column in GL_INTERFACE and the Journal Import execution report.

Do all journal lines need the same currency?

Each journal has a single currency, so group lines accordingly. Foreign currency journals also need conversion type and rate information, which this simple worksheet does not cover.

If month-end journal prep is eating your close, tell us what the data source is. We can discuss automating the extract and checks while keeping a human approval step.