Skip navigation



So you run your Trial Balance report in FASTR for the company Controller, and some of the amounts are not exactly what you are expecting…this can’t be right! Where in the world are these numbers coming from?

Before you pack up your coffee mug to move to a remote island, know that there is help available.


When you need to research questionable account balances for a FASTR version, you can create an audit trail using the Balance Auditor feature.  With the balance auditor activated, the system determines which records in the Account Balances table were used to create the account balances on your report. Even more than that, it allows you to drill down into the Account Ledger Inquiry, and ultimately the original journal entry!



It’s really easy to setup and use.  Link to Doc ID 1994077.1 How to use Balance Auditor on FASTR Reports.


Make it even easier to use by setting up Balance Auditor as a menu option! See how with Doc ID 627072.1.



A few things to remember when using this feature:

  • The balance auditor provides an audit trail for non-calculated amounts only. It does not provide an audit trail for amounts that are the result of column, row, or cell calculations.  Balance Auditor also does not work with reports using Organization Structures.
  • Because the balance auditor requires significant system resources, you should run a version with it activated only when necessary.
  • The information on the audit trail might differ from the information in your account ledger. This is because the account ledger is dynamic, that is, when someone posts a transaction, it is reflected immediately. The audit trail, in contrast, is static. If someone posts a transaction after you create the audit trail, it is not reflected in the audit trail.



For additional information on FASTR problem resolution, Doc ID 1548783.1 Troubleshooting FASTR Reports.



Your payroll department is like a railway station.  There are numerous of schedules/deadlines to meet and you can’t miss any of them.    We live and breathe by these deadlines.

As you know, there are many important deadlines in payroll:


  • Deadlines to enter deductions such as child support, levies, and garnishments into the payroll system prior to processing payroll.
  • Deadlines to upload timecards, process payroll and deposit money into the bank to cover your employee payroll.


Just as you wrap up the remainder of the state electronic filing for W-2s, it’s time prepare for your quarterly reports, such as 941 and SUI.  We understand your needs and are here to help.  Here are some important documents that will assist you as you prepare your 941 and SUI (State Unemployment Insurance) quarterly reports:

For the 941 report:

  • First, you need to download the current Software Update (SU) for 941 to receive the up-to-date legislative changes.  See Doc ID 657268.1-World HCM Current Software Downloads for the appropriate SU for your system release level.
  • If this is the first time you are preparing your 941, or if you need a refresher on what each line on the 941 represents, take a look at Doc ID 763134.1- 941 Quarterly Worksheet Line Explanations.  Additional questions? See Doc ID 627222.1-941 Worksheet FAQ's.


For the SUI report:

  • First, you need to download the current Software Update (SU) for SUI to receive the up-to-date legislative changes.  Find the appropriate SU for your system release level using Doc ID 657268.1-World HCM Current Software Downloads.
  • Use Doc ID 627186.1- State Unemployment Insurance – SUI for an overview of SUI and its setup process.


Still need some help?  We’re here for you.  Post a quick question for a quick response on the World HRM/Payroll Community!



Because software and hardware are constantly evolving, your software life cycle will include an upgrade phase. You may need to upgrade your software because of necessary hardware upgrades. You may want to reap the rewards of the updated release’s new functional and technical enhancements - to increase efficiency and effectiveness for your business or enhance the user experience and productivity. Or, your decision to upgrade may be to align with support timelines – to assure you are on a Premiere support release (Lifetime Support Policy PDF). Often, the upgrade project is driven by mix of many factors.  Whatever your reasons for upgrading, you will want to reduce the costs and the risks associated with the upgrade. Being proactive can help you be prepared and minimize your business downtime and the risks of upgrading your system.


KM document “Moving on UP! Proactive Upgrades for Current ERP Systems: Oracle Applications Unlimited - document 1983566.1 provides information about the Upgrade and Migration Lifecycle Advisors as well as other product-specific upgrade resources available to assist you in maintaining a current and up-to-date ERP system.


Checkout the new document here:


You can share feedback or find out more by contacting the JD Edwards Proactive Support team at:



So, you’re upgrading and wondering if your discrete work orders are in place and ready for the upgrade?



There are some best practices that you should consider.  First, you need  to process open, partially completed work orders that have pending accounting activity not yet reported. By generating and posting these transactions, you’ll clear the unaccounted fields that the Work in Process program uses to generate manufacturing journal entries.  This will result in a ‘clean’ cutover in Manufacturing Accounting.  What’s important is that you’ll avoid inconsistencies in the Work Order Production File which values are used by the Work Order Variances program to generate the IV transactions.


This same importance pertains to all work order related files. Always, run programs in PROOF mode first and then in FINAL mode prior to upgrading to troubleshoot and correct any possible errors.


For fully completed work orders, generate manufacturing variances with P31804 as this is the last step to fully ‘close’ a Work Order and should be run once in final mode.


Finally, post all manufacturing transactions to the General Ledger. Run all active batches through to completion and verify the posting edit reports are free of errors. Then, use the Item Ledger & G/L Integrity report to confirm that no discrepancies exist between the Item Ledger (Cardex) and G/L manufacturing entries.


Remember, you can access key upgrade information via the UPGRADE section of the Information Center page for the Release that you are upgrading to.  For example, if you are upgrading to A9.3.1, check out:  Information Center: Upgrading to JD Edwards World Release A9.3/A9.3.1 (Doc ID 1447731.2) for documents that are specific to a A9.3.1 release upgrade.


Keep your eye out on My Oracle Support for new knowledge documents regarding additional best practices for discrete work orders and upgrading.  In the meantime, post questions on My Oracle Support Community or open a Service Request!

             20th Century - Green Screen                                     Meets                         21st Century - Google Map

Snap2.bmp                           Snap3lrg.bmp  

            JD Edwards World is movin' on up!  Did you know that you now have the ability to define Generic Exits which can navigate to a URL rather than an RPG program?  Users can also exit to browser-based functionality on the client workstation; such as displaying documents on a network drive directly from a field in JD Edwards World.

The Web Enablement Navigation Bar has been expanded to include Generic (User-Defined) Exits, with the capability to show more than 24 exits from a program.  Generic Exits allow you to define an exit from a World application program without having to make coding changes to the application program.  There are two types of Generic Exits. The first type, allows you to define an exit to another interactive application program.  The second type allows you to define an exit to a URL or PC Process. 

Use this link to A9.3 Documentation; Working with Generic Exits, Chapter 47.5 Working with Generic Exits.  For use case examples, take a look at A9.3 Generic Exit Functions (Doc ID 1478037.1).




So here you are in your second week of your great new job in the accounting department of a company that uses JD Edwards World software and after spending time getting familiar with it week one, you’re feeling pretty confident...UNTIL … your boss comes by and tasks you with finding out why the trial balance she just ran is out of balance!  She needs it cleared up by the end of the week because the auditors arrive early Monday morning. 

Wow! It’s your first actual assignment! Yea!  Uh oh!  You suddenly realize that although you paid a great deal of attention during your training, you really only know the basics of getting around in JD Edwards World. Panic sets in!  Your mind is a blank!  You suddenly can’t even remember what a trial balance is!  How are you going to find out what’s wrong?

Ok... take a deep breath, you can do this. Let’s take it a step at a timeSince the trial balance only reports posted amounts, the first thing you should do is run some integrity reports that check to see if you have any problems with batches:

1.  Start with the Transactions to Batch Header report. This integrity will report discrepancies between the batch header’s status and the transactions within the batch. It will also show any transactions that are missing a batch header.  It’s easy to fix these types of issues. If your transactions are unposted and the batch header is posted, just update the batch status on the batch header to “approved” and resubmit the post program. If a batch header is missing, you can add it very easily.  Look at Doc ID 626947.1 - How to Add, Update, or Delete a Batch Header Record for complete steps.


2.  Next, run the Batch to Detail and Out of Balance report.  This report lists batches posted out of balance.  If any batches are listed, you should investigate these batches and make correcting entries. What?  How do I investigate, you are probably thinking.  Don’t worry, we’ve got you covered.  Have a look at Doc ID 662609.1 - Finding Batches Posted Out of Balance.

3.  Now run the Unposted Batches integrity report.  This integrity looks for any batch headers that are not posted. Sometimes it’s as simple as this - some batches just didn’t get posted!

4.  After correcting any batch issues, run the Companies in Balance integrity report.  This report will list all your companies.  Companies that don’t balance will have amounts listed in any of three columns on this report.  This can be a difficult integrity to clear because there are so many different reasons a company can be out of balance.  But, you guessed it...we’ve got something to help:  Take a look at Doc ID 657081.1Troubleshooting the Companies in Balance Integrity Report. This document lists the most common reasons a company may be out of balance which are:


  • Journal entries are posted to the prior year after the Close Year program has been run.
  • There are batches posted out of balance. (The three batch integrities you’ve already run may not have caught all of them.)
  • Intercompany settlement records are missing.
  • There has been a fiscal date pattern change to the company.
  • Data is missing in records.

It then details steps to solve various scenarios found on the report.

Along with the documents just mentioned, you might want to bookmark this document that will guide you in keeping your data in sync on an on-going basis:  Doc ID 950649.1 -Financial Integrity Reports - Preferred Order to Run and Functionality Overview. 

Still need some guidance?  We’re here to help! Post quick questions to our customer community, which is monitored by Support experts.  If you think you need more in-depth help, open a service request with us!

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.