INTERACTIVE GENERAL LEDGER INTEGRITY REPORTING
New features available to users with the JD Edwards Orchestrator mean that you may no longer need to continually check batch integrity reports; you can instead automate the process and simply get a notification if there is an issue that needs to be addressed.
Interactive versions of many of the standard batch General Ledger integrity reports are available from Apps release 9.1, Tools release 9.1.5.
The following pre-configured integrities are available as interactive applications:
- Transactions to Batch Headers
- Batches Out of Balance
- Companies by Batch Out of Balance
- Companies Out of Balance
- Accounts to Business Units
- Account Balance to Account Master
- Account Ledger to Account Master
Not only can you run the integrities interactively, but there are also form exits to help resolve any issues.
These integrities are available in ESU JN18742
Oracle have tested these integrities over 100 million rows and have found that the response is acceptable. In fact, Oracle have found them to be much faster than the batch jobs.
AUTOMATE GENERAL LEDGER INTEGRITY REPORTING
In addition, Oracle have delivered the following preconfigured notifications for integrities:
|UDO Name||Description||Bug #|
|JDE_NOTIFY_09_Account_Balance_Errors||Notifies subscribers of the number of Account Balances that do not have a valid Account Master based upon Account Balance to Account Master (P097031). This notification runs every weekday at 8:00.||27472789|
|JDE_NOTIFY_09_Batches_Awaiting_Approval||Notifies subscribers of the number of batches awaiting approval based upon the subscriptions batch type. This notification runs every weekday at 8:00 am.||27472789|
|JDE_NOTIFY_09_Batches_in_Error||Notifies subscribers of the number of batches in error based upon the subscriptions batch type. This notification runs every weekday at 8:00 am.||27472789|
|JDE_NOTIFY_09_Batches_Out_of_Balance||Notifies subscribers that there are batches that are out of balance based upon the batch type in the subscription. This notification runs every weekday at 8:00 am.||27472789|
|JDE_NOTIFY_09_Transactions_WO_Acct_Master_Records||Uses the P097021 application to determine if there are any transactions without account master records.||28313885|
|JDE_NOTIFY_09_Companies_Out_of_Balance||Notifies subscribers that there are companies out of balance. This notification runs every Monday at 8:00 am.||28313885|
|JDE_NOTIFY_09_Account_Balances_WO_BU||Notifies subscriber that there are account balances without a business unit based upon the Business Unit in the subscription. This notification runs every weekday at 8:00 am.||28313885|
|JDE_NOTIFY_09_Batch_Header_Errors||Notifies subscribers that there are Batch Header to Transaction errors. This notification runs every Monday at 8:00 am.||28313885|
So basically, the above notifications can replace the batch integrities. These notifications call orchestrations which run over the interactive integrity applications.
While these notifications and orchestrations are pre-configured, you can modify them as required. Instead of running the batch integrities, the user can subscribe to the relevant notification and be notified if there is a problem. They would no longer need to check the integrities but would rather be told when there is a problem.
G/L BATCH STATUS HISTORY
A handy new feature introduced in Applications release 9.2.5 is the G/L Batch Status History.
The G/L batch status history functionality provides the ability to audit when a batch is created, deleted or the batch status is changed. It provides a history table and an inquiry application that tracks who has changed the status of a batch, what the change is, and when the status of a batch has changed. Examples of the actions that are tracked include creation, approval, and posting.
Learn how to activate this feature here: https://docs.oracle.com/en/applications/jd-edwards/financials/9.2/eoaff/working-with-batches.html#understanding-g-l-batch-status-history-release-9.2-update