Skip navigation

Month-end financial processing has until now involved running batch jobs to reconcile account information from numerous related tables in the General Accounting, Accounts Payable, and Accounts Receivable systems. These batch jobs typically run for hours and require significant additional time to manually review the PDF output.

The new interactive Financial Reconciliation applications perform the same function in real time and allow users to work with exceptions interactively. Real-time Financial Reconciliation provides users with immediate feedback and enables them to address exceptions immediately instead of having to wait for reconciliation processing at the end of a month or a quarter.

Find below the 7 new applications and the corresponding BUGs (minimum Application Release of 9.1 and require a minimum Tools Release of 9.1 Update 5):



Batch Out of Balance

ESU via 19932473


Header & Detail Batch Out of Balance

ESU via 19932473


Companies in Balance

ESU via 19932473


Transactions without Account Master

ESU via 19932473


Account Balance without Account Master

ESU via 19932473


Accounts without Business Units

ESU via 19932473


Company by Batch Out of Balance

ESU via 19932473

For additional details and instructions please see: Frequently Asked Questions for JD Edwards EnterpriseOne Real-Time Financial Reconciliation and Oracle Database In-Memory (Doc ID 1965857.1).

Recently, we announced the availability of Active Content Pages for three industries:

  • Maintenance Technician and Maintenance Scheduler in the Natural Resources industry
  • Farm Manager and Field Manager in the Agribusiness industry
  • Lot Start Coordinator in the Homebuilder industry


For a detailed technical review of the industry content delivered, please review this


You can also access the slide deck from these LearnJDE pages:

Looking for information to help with the migration from JD Edwards World to JD Edwards EnterpriseOne? LearnJDE now has an entire page dedicated to resources supporting migration from World to EnterpriseOne.

Find the following presentation: Migration Momentum and Mechanics: Making the Move from JD Edwards World to JD Edwards EnterpriseOne.

. . .and many other resources on the World Migration Overview page on LearnJDE.

EnterpriseOne Page Composer

JD Edwards just released a series of new tutorials on EnterpriseOne Page Composer. EnterpriseOne Page Composer lets any citizen developer create and deploy EnterpriseOne Pages.

Review the tutorials that demonstrate how you can configure Composed Pages into dynamic, personalized layouts to include JD Edwards EnterpriseOne applications, reports, and Watchlists delivered by Oracle, as well as external information.

Access the new tutorials here or navigate to > My App interest is > Cross Applications > EnterpriseOne Pages.

IoT Orchestrator Studio


The recently released JD Edwards EnterpriseOne Internet of Things (IoT) Orchestrator Studio empowers citizen developers to build and deploy orchestrations unique to their business processes—without requiring programming skills.

Watch this new video to learn about IoT Orchestrator Studio as well as IoT Cloud Service integration.

The video is also available from: > New Releases and Initiatives > Applications 9.2 > Internet of Things

COLLABORATE 16 offers the perfect opportunity for JD Edwards customers to explore new product releases and trends including Cloud, Big Data, security IoT, and mobility. JD Edwards customers should attend to hear more on these topics and discover solutions through knowledge sharing and networking with customers facing the same challenges in their organizations.

Financial Integrity reports are an integral part of the JD Edwards EnterpriseOne General Accounting system. Running integrity reports helps you: 

  • To supplement your internal balancing procedures. 
  • To locate potential balancing problems and data inconsistencies. 
  • Ensure that your system functions correctly and that tables remain in balance. 
  • Enables you to correct any problems in a timely and efficient manner. 


You should run integrity reports at these times: 

  • During new Software Installation. 
  • During Data Conversion. 
  • Daily, if necessary. 
  • At the end of the fiscal period. 
  • At the end of the fiscal year.


The more often you run integrity reports, the easier it is to determine when a problem occurred. Consequently, this provides huge benefits to business, reduces downtime and assists with growing audit, compliance and regulatory pressures.


The General Accounting Integrity Reports can be classified into four categories: 

  • Batch Header Reports - Identify discrepancies between the Batch Control Records table (F0011) and the Account Ledger (F0911) table. 
  • Out-of-Balance Reports - Identify whether transactions within a company are in balance, whether Accounts Balance (F0902) match with Account Ledger (F0911) on a period-by-period basis and if Intercompany settlement accounts are in balance. 
  • Chart of Account Reports – Locate inconsistencies within chart of accounts. 
  • Multicurrency – Identify discrepancies within Foreign Account Balances (F0902).



For more information on how to run and troubleshoot the General Accounting Integrities, you may refer to  How To Troubleshoot EnterpriseOne General Ledger Integrity Issues (Doc ID 1541001.1).

Have you seen the new Give Feedback link that has been added in our community space?  Located on the right hand side of the community Overview tab look for:

This is your chance to tell us what you think!  Clicking on the link will bring up a quick survey to fill in:


Why are we doing this? We want to continue improving the communities and your feedback matters! The survey is specific to each community, because not all communities are created equal. We can learn from the ones you rate as doing well and improve the ones that are not. Your comments are always valued.


The My Oracle Support Community team is looking forward to hearing from you soon!

You have come to the right place, if you are facing either of the following situations:

  • Do you see an increasing number of Account Master (F0901) records in your system?
  • Is the Next Number for Account ID is nearing its limit (99,999,999)?
  • Did you notice an increasing number of Account Ledger (F0911) and Account Balances (F0902) transactions in your system?
  • You realized that you are keeping many more years of data in the system than is necessary for business or statutory reasons?


  Since Model Chart of Accounts are used as a basis for creating accounts for Business Units, Projects, and Jobs:

  • These models often contain every possible account for a Business Unit, Project, or Job.
  • Many of these accounts are unused by the Business Unit, Project, or Job.
  • These unused accounts are not removed from the system.


  • Evaluate your Business Units, Projects, and Jobs for best fit into Model Chart of Accounts.
    • Determine if there are distinct categories of Business Units, Projects, or Jobs that have different account needs.
    • Consider creating separate models for these variations to optimize the number of accounts in a model.
  • Define a process for purging unused accounts after Projects or Jobs close.
  • Define and implement a Financial Purge and Archive Strategy so that your live system is not carrying unnecessary data.  This data includes but is not limited to Account Master, G/L Transactions, Account Balances, A/R transactions, and A/P transactions.


  • Customers have been able to dramatically reduce the number of accounts and the volume of financial data in their production environments.
  • Customers have found their Financial Reporting performance improves with the reduction of transactions and accounts.
  • Customers have found they are no longer in danger of running out of Account IDs.
Farahd -Oracle

Manual Reconciliation

Posted by Farahd -Oracle Mar 2, 2016

Bank accounts, selected expense accounts, and other general ledger accounts in the General Accounting system can be reconcile by the system. After performing the initial setup requirements, the accounts can easily reconcile on a periodic basis.


Manual reconciling of the accounts consists of the following steps:

  • Reconciling voided payment or receipts with zero amounts automatically (optional).
  • Creating or refreshing the reconciliations worktable for unreconciled transactions.
  • Performing the manual reconciliation for bank accounts, transit accounts, or clearing accounts.


Instead of manually reconcile voided payments and receipts, time can be save during the account reconciliation by running a program to automatically reconcile voided payments and those with zero amounts. The system selects payments that were voided manually or during automatic payment processing.


The Auto Reconcile Void Payment Program and Auto Reconcile Void Receipts marks voided payments and receipts as reconciled and updates the Account Ledger table (F0911). The program should be run before the Refresh Reconciliation File program to create the reconciliation worktable so that zero- amount and voided payments are not included in the worktable.


The Refresh Reconciliation program copies the unreconcile transaction detail from all reconcilable accounts from the Account Ledger table (F0911) into the Account Ledger Reconciliation worktable (F0911R).


Each time a new reconciliations worktable is created, the system removes all previous reconciled in the table and replaces them with new transactions that were entered since the last table was created.


When the reconciliation is completed, the system updates the reconciled transactions in the Account Ledger Reconciliation worktable (F0911R) and the Account Ledger table (F0911).


You can read more about the manual reconciliation process in document Overview of Clearing Account Reconciliation (Doc ID 1461344.1).

Filter Blog

By date: By tag:

Welcome to the My Oracle Support Community! We highly encourage you to personalize your community display name to make your activity more memorable. Please see for instructions.