How Journals Are Imported
Oracle Fusion Cloud Financials reflect the traditional segregation between Oracle General Ledger and its associated subledgers. Detailed transactional information is captured in the subledgers and periodically imported and posted in summary or detail to General Ledger.
You import from the subledgers to the General Ledger in real time or you can import and post automatically based on a defined schedule. Once the data is posted in the General Ledger, the data is available for balance inquiry and reporting.
Use journal import to integrate transactions from other applications such as payroll, accounts receivable, accounts payable, and fixed assets with your General Ledger. You can import ledger currency and foreign currency encumbrance journals, if encumbrance accounting has been enabled for the ledger.
For each accounting period, you import accounting data from the subledger application, then review, update, and post the journal entries. You can also use journal import to import historical data from your previous accounting application. Import data from multiple interface tables by entering a particular source and group ID combination for the data in each interface table. Journal import processes data from one table at a time.
The following table lists the effect of security privileges on the journal import process.
|
Security Privilege |
Journal Import |
|---|---|
|
Control Accounts |
Not blocked. |
|
Segment Value Security |
If the account combination exists, then no check happens. If the journal import process creates an account combination, then segment value security is enforced. |
|
Cross-Validation Rules |
If the account combination exists, then no check happens. If the journal import process creates an account combination, then cross-validation rules are enforced. |
Settings That Affect Journal Import
Configure the following settings before running the Import Journals process.
-
Set up your General Ledger to accept journal import data by defining your ledger, currencies, accounts, journal sources, and categories.
-
Define your import process parameters and schedule, if using automatic processing.
-
Set the period status to either future enterable or open. Journals can be created by the journal import process in a future enterable period, but not posted. Posting requires an open period.
-
Export data from your subledgers and populate the General Ledger Interface table.
-
Optionally, enable encumbrance accounting.
Here's an additional consideration if you import journals in a foreign language. It's recommended that you enable the Import Using Key option on the Manage Journal Sources page for the source being used for import. The source key is a generic identifier that's language independent. This option lets you identify a particular journal source consistently across all languages.
How Journal Import Is Processed
Transactions can be imported into General Ledger from Oracle subledgers and legacy applications.
The flow of accounting data includes the following steps:
- The transaction data entered in both Oracle and legacy application subledgers is imported into the General Ledger Interface table. If the process completes successfully, journal entries are created. If the process fails, the error lines are loaded into the corrections spreadsheet or are deleted using the Delete Journal Import Data process. After correcting the errors or deleting the error lines, run the Import Journals process again.
- After the journal entries are created in the General Ledger from the imported data, post the journals. The posting process validates the data and records it in both the General Ledger Balances table and the balances cube. Posting errors are listed in the Posting Execution report and can also be viewed in the Journals dashboard and on the Manage Journals page. After correcting the errors, run the posting process again.
- After posting completes, the data is available for reporting and balance inquiry.
The following figure outlines the flow of accounting data between the subledgers and General Ledger.
