Verifying Data Integrity for General Accounting

This chapter provides an overview of General Accounting integrity reports and discusses how to:

• Run the Transactions to Batch Headers report.

• Run the Batch to Detail report.

• Run the Unposted Batches report.

• Run the Batches Out of Balance report.

• Run the Company by Batch Out of Balance report.

• Run the Companies in Balance report.

• Run the Intercompany Accounts in Balance report.

• Run the Account Balance to Transactions report.

• Run the Accounts without Business Units report.

• Run the Account Balance without Account Master report.

• Run the Transactions without Account Master report.

Understanding General Accounting Integrity Reports

Use integrity reports to supplement your internal balancing procedures and to locate potential balancing problems and data inconsistencies.

Integrity reports are an integral part of the JD Edwards EnterpriseOne General Accounting system. Running integrity reports helps you ensure that your system functions correctly and that tables remain in balance. It also 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 conversion.

• Daily, if necessary.

• At the end of the month.

• At the end of the fiscal year.

The more often that you run GL integrity reports, the easier it is to determine when a problem occurred. Some integrity reports are exception reports that list only discrepancies among tables.

The JD Edwards EnterpriseOne General Accounting system has three types of GL integrity reports.

Batch Header Reports

Use the batch header reports to identify discrepancies between the Batch Control Records table (F0011) and the F0911 table. Run the batch header reports in this sequence:

1. Transactions to Batch Headers

2. Batch to Detail

3. Unposted Batches

Out-of-Balance Reports

Use the out-of-balance reports to verify that:

• Transactions within a company are in balance.

• Accounts balance on a period-by-period basis.

• Intercompany settlement accounts are in balance.

If a batch has the Exclude Batch from Integrity Report option selected in the Batch Header Revisions program (P0011) and the batch contains an out-of-balance entry, the batch will not appear on the Batches Out of Balance and Company by Batch Out of Balance integrity reports. When you run these two integrity reports, ensure that the data selection for Include Batch on Integrity (IBOI) flag is not equal to N.

Chart of Accounts Reports

Use the chart of accounts reports to verify that the company number in the F0901 matches the company number in the Business Unit Master (F0006), F0902, and F0911 tables. You should also run these reports if you move one or more business units to another company.

In update mode, run the chart of accounts reports in this sequence:

1. Accounts without Business Units.

   This report uses the company number in the F0006 table to update the company number in the F0901 table.

2. Account Balance without Account Master.

   This report uses the company number in the F0901 table to update the company number in the F0902 table.

3. Transactions without Account Master.

   This report uses the company number in the F0901 table to update the company number in the F0911 table.

This sequence ensures that the company number always originates from the F0006 table. By running the Accounts without Business Units report first, it also ensures that the other two integrity reports use the company information in the F0901 table to update the F0902 and F0911 tables.

List of General Accounting Integrity Reports

To decide which integrity report to run, review this list of reports and descriptions:

Running the Transactions to Batch Headers Report

This section provides an overview of the Transactions To Batch Headers report and discusses how to:

• Print the Transactions To Batch Headers report.

• Set processing options for Transactions To Batch Headers.

• Correct discrepancies on the Transactions To Batch Headers report.

Understanding the Transactions To Batch Headers Report

The Transactions To Batch Headers report (R007021) identifies discrepancies between a batch record and its associated transactions. This report compares batches in the F0011 table with transactions in these tables:

• F0911

• F03B11, F03B13, and F03B14

• F0411, F0413, and F0414

Specifically, the report lists unposted transactions with a batch header record that is marked as posted (D) as well as unposted and posted transactions without matching batch header records. For transactions without matching batch header records, you can set a processing option to rebuild missing batch header records in the F0011 table.

This report can be lengthy. For example, if a 500-line journal entry has a integrity issue, the system prints all 500 lines. For this reason, you might want to create different versions of this report and use processing options to specify whether to compare GL, AP, or AR transactions with the batch records.

You must set at least one of the GL, AR, or AP processing options for the system to process records. Otherwise, the system prints the message No Data Selected on the report.

Printing the Transactions to Batch Headers Report

Select Integrity Reports and Updates (G0922), Transactions to Batch Headers.

Do not enter data selection criteria for this report.

Setting Processing Options for Transactions to Batch Headers (R007021)

Processing options enable you to specify the default processing for reports.

Post/Unposted

Select

Because this is a batch header report, the system uses the batch date, not the general ledger date, to select records.

G/L

If you specify a range of batch types or batch numbers in the Batch processing options and specify 1 for this GL processing option, the system identifies the batches and then compares the corresponding records in the F0911 table to the F0011 table.

If you specify a range of batch types or batch numbers in the Batch processing options and leave this GL processing option blank, the system does not perform an integrity check between the F0911 and F0011 tables.

A/R

Values for these processing options are:

• Blank: Do not include records from the specified table for comparison with batch control records in the F0011.

• 1: Include records from the specified table for comparison with batch control records in the F0011.

If you specify a range of batch types or batch numbers in the Batch processing options and specify 1 for any these processing options, the system identifies the batches and then compares the corresponding records in the AR table to the F0011 table.

If you specify a range of batch types or batch numbers in the processing options and leave any of these AR processing options blank, the system does not perform an integrity check between the specified table and the F0011 table.

For example, assume that you specify the batch type range IB through RB in the processing options. Then you specify 1 for the GL and AP processing options and leave the AR processing options blank. The system will perform an integrity check on the batches within the IB through RB range that exist in the F0911 table and compares them to the F0011 table.

A/P

Values for these processing options are:

Blank: Do not include records from the specified table for comparison with the batch control records in the F0011 table.

1: Include records from the specified table for comparison with the batch control records in the F0011 table.

If you specify a range of batch types or batch numbers in the Batch processing options and specify 1 for any these processing options, the system identifies the batches and then compares the corresponding records in the AP table to the F0011 table.

If you specify a range of batch types or batch numbers in the Batch processing options and leave any of these AP processing options blank, the system does not perform an integrity check between the specified table and the F0011 table.

Options

Correcting Discrepancies on the Transactions To Batch Headers Report

After running the Transactions to Batch Headers report, you should correct any discrepancies by setting the processing option to rebuild missing batch header records in the F0011 table. Correct any discrepancies identified on this report before you run the Batch to Detail report.

To prevent future discrepancies, consider assigning responsibility for batch revisions to one user.

Missing Batch Header Records

The reasons for this error to appear on the Transactions to Batch Headers report include:

• A computer failure.

• A conversion or interface program created a batch header incorrectly.

• A user created a batch header incorrectly.

• A user did not enter the actual number of documents on the Batch Header Revisions form.

Posted Batch Header Record, No Posted Detail

This error appears on the Transactions to Batch Headers report if a user incorrectly changes a batch header record to a posted status.

To correct this discrepancy, change the status of the batch header record to A (approved) on the Batch Header Revisions form and post the batch.

See Also

Adding and Revising Batch Headers

Running the Batch to Detail Report

This section provides an overview of the Batch to Detail report, lists a prerequisite, and discusses how to:

• Print the Batch to Detail report.

• Set processing options for Batch to Detail.

Understanding the Batch to Detail Report

The Batch to Detail report (R007031) compares the status of the batch header records for each batch in the F0011 table to the status of the corresponding transactions in these tables:

• F0911

• F0411, F0413, and F0414

• F03B11, F03B13, and F03B14

The system does one of the these:

• Updates the status of the batch header to D in the F0011 table if all corresponding transaction records in the batch are marked as posted.

  For example, if all F0911 records for batch type G are posted, but the batch header record for the batch in the F0011 table is not posted, the report updates the status of the F0011 record to D (posted).

• Deletes the batch header and prints a message on the report indicating that the batch was deleted if one of these situations apply:

  • No records exist for batch type G in the F0911 table.

  • No records exist in either the F03B11 table or the F03B13 and F03B14 tables and the A/R Integrity Check Flag processing option is set to 1.

  • No records exist in either the F0411 table or the F0413 and F0414 tables and the A/P Integrity Check Flag processing option is set to 1.

    Note. If the A/R or A/P Integrity Check Flag processing option is blank, the report ignores the batch regardless of whether unposted records exist in the AR or AP tables. A blank processing option indicates that the batch is not eligible for the integrity check.

Prerequisite

Correct any discrepancies that are identified on the Transactions to Batch Headers report before you run the Batch to Detail report.

Printing the Batch to Detail Report

Select Integrity Reports and Updates (G0922), Batch to Detail.

Setting Processing Options for Batch to Detail (R007031)

Processing options enable you to specify the default processing for reports.

Date Range

Because this is a batch level report, the system uses the batch date, not the general ledger transaction date, when selecting records.

A/R

A/P

Batch

Running the Unposted Batches Report

This section provides an overview of the Unposted Batches report, lists a prerequisite, and discusses how to print the report.

Understanding the Unposted Batches Report

The Unposted Batches report (R007011) prints a list of all unposted batch transactions in your system. Use this report as a reminder to:

• Post batches that have an approved status.

• Review and approve batches that are still pending.

• Research batches that are in error.

The Unposted Batches report prints batch control information from the F0011 table only. If the batch header does not exist for a batch of unposted transactions, the batch does not appear on this report.

This report sorts information by batch type and then by batch number.

Prerequisite

Correct any discrepancies that are identified on the Batch to Detail report before you run the Unposted Batches report.

Printing the Unposted Batches Report

Select Integrity Reports and Updates (G0922), Unposted Batches.

This report has no processing options.

Running the Batches Out of Balance Report

This section provides an overview of the Batches Out of Balance report and discusses how to:

• Print the Batches Out of Balance report.

• Set data selection for Batches Out of Balance.

• Set processing options for Batches Out of Balance.

• Correct discrepancies on the Batches Out of Balance report.

Understanding the Batches Out of Balance Report

You should research any batches that are out of balance. You might have intentionally posted some batches out of balance or you might have batches that posted out of balance due to system problems.

The Batches Out of Balance report (R007032) reviews the net amount in each batch. If the net amount is not zero, the net difference - not the batch amount - prints on the report. If the amounts net to zero, the batch is in balance and does not print.

See Also

R09301 - Unposted General Journal, General Journal by Batch, Unposted Cash Basis

Printing the Batches Out of Balance Report

Select Integrity Reports and Updates (G0922), Batches Out of Balance.

Setting Data Selection for Batches Out of Balance

Enter a batch number, batch type, and company number in data selection, if possible, to improve processing time for the report.

Setting Processing Options for Batches Out of Balance (R007032)

Processing options enable you to specify the default processing for reports.

Date Range

Because this is a batch level report, the system uses the batch date, not the general ledger transaction date, when selecting records.

Ledger Type

Correcting Discrepancies on the Batches Out of Balance Report

After running the Batches Out of Balance report, you should correct any discrepancies that the system detects. To analyze the detail records for a batch, run the General Journal by Batch report (R09301).

To prevent future out-of-balance postings, consider:

• Assigning security to the Work With Batch Versions - Available Versions form to prevent improper changes.

• Assigning responsibility for out-of-balance posting to one user.

Batches Posted Out of Balance

The reasons for this error to appear on the report include:

• The batch was purposely posted out of balance.

  To remove the batch from the report, select the Exclude Batch from Integrity Report check box on the Batch Overrides form. Maintain documentation for this batch.

• The intercompany settlement constant is set to *.

  To correct this error:

  • Enter journal entries manually, if intercompany settlements are necessary, and post the batch.

  • Change the intercompany settlement constant to 1 or 2 so that the system automatically creates intercompany settlements.

Batch is Partially Posted

A reason for this error to appear on the report is a computer failure or job cancellation. To correct this error:

• Select the Allow Batch to Post Out of Balance check box on the Batch Overrides form and post the partially posted batch again.

• Enter journal entries manually, if intercompany settlements are necessary.

Note. To prevent the system from deleting an empty batch header for specific batch types, enter x in the Description 02 field of the batch type in UDC table 98/IT.

Running the Company by Batch Out of Balance Report

This section provides an overview of the Company by Batch Out of Balance report, lists a prerequisite, and discusses how to:

• Print the Company by Batch Out of Balance report.

• Set processing options for Company by Batch Out of Balance.

• Correct discrepancies on the Company by Batch Out of Balance report.

Understanding the Company by Batch Out of Balance Report

The Company by Batch Out of Balance report (R09706) reviews only posted transactions in the F0911 table. This report totals all posted transactions in the F0911 table by batch and compares each batch total to the batch header record in the F0011 table. It prints all batches that are out of balance and includes:

• The amount by which the batch is out of balance.

• The company numbers that have out-of-balance batches and the portion of the total discrepancy for each company.

This report is an exception report. If no discrepancies exist, the report is blank.

Prerequisite

To ensure accuracy, run the Company by Batch Out of Balance report when users are not accessing the system.

Printing the Company by Batch Out of Balance Report

Select Integrity Reports and Updates (G0922), Company by Batch Out of Bal.

Setting Processing Options for Company by Batch Out of Balance (R09706)

Processing options enable you to specify the default processing for reports.

Additional Ledger

Correcting Discrepancies on the Company by Batch Out of Balance Report

After running the integrity report, you should correct any discrepancies that the system detects.

A Batch is Out of Balance by Batch and Company

The reasons for this error to appear on the report include:

• The batch was intentionally posted out of balance because the general accounting constants are set accordingly or the batch was set to allow out-of-balance postings on the Batch Overrides form.

• A computer failure or job cancellation occurred.

To correct the error:

• Select the Allow batch to post out of balance check box on the Batch Overrides form, change the Intercompany Settlements field to * in the general accounting constants, and post the batch.

• Change the value in the Intercompany Settlements field back to 1 or 2 so that the system automatically creates intercompany settlements.

Running the Companies in Balance Report

This section provides an overview of the Companies in Balance report and discusses how to:

• Print the Companies in Balance report.

• Locate out-of-balance conditions.

• Correct discrepancies on the Companies in Balance report.

Understanding the Companies in Balance Report

All transactions within each company balance should net to zero. The Companies in Balance report (R097001) uses information from the F0902 table to determine whether a company is in balance.

This report identifies adjustments that posted to a prior year that are not included in the balance forward amounts for an account, amounts that were posted after the period cutoff, and missing intercompany settlements. For intercompany settlements, run this report and then run the Intercompany Accounts in Balance report (R097011) immediately to ensure that intercompany accounts are in balance.

Note. The Intercompany Settlements field in the general accounting constants controls the automatic generation of intercompany entries. To automatically create intercompany entries for journal entries, you must set this constant to 1 or 2.

The Companies in Balance report includes three columns. These columns appear blank if a company is in balance. If a company is out of balance, the summarized (net) amount appears in the columns as described in this table:

Printing the Companies in Balance Report

Select Integrity Reports and Updates (G0922), Companies in Balance.

This report has no processing options.

Locating Out-of-Balance Companies

After running and reviewing the Companies in Balance report, you can locate the source of out-of-balance companies by:

• Running any of these reports:

  • Batch to Detail (R007031)

  • Account Balance to Transactions (R09705)

  • Intercompany Accounts in Balance (R097011)

• Reviewing specific batches or batch types using the General Journal Review program (P0011).

• Running the Trial Balance Report (R09410) to determine which periods are out of balance for each company.

  Select level of detail 5 for a summarized report.

• Verifying that data in the F0911 table is correct.

  Run the Repost Account Ledger program (R099102) with the appropriate processing option set to print a report only. If the system identifies discrepancies on the report, run the Repost Account Ledger program in final mode to correct the discrepancies.

  See Reposting the Account Ledger.

Correcting Discrepancies on the Companies in Balance Report

After locating the source of the out-of-balance companies, you should correct any discrepancies that the system detects.

To prevent future out-of-balance conditions, consider:

• Placing security on the Work With Batches form and in the general accounting constants to prevent improper changes.

• Assigning responsibility for correcting out-of-balance conditions to one user.

Company is Out of Balance in YTD Column

The reasons for this error to appear on the report include:

• The batch was posted out of balance.

  To locate and correct out-of-balance batches, run the Batch to Detail report and the Company by Batch Out of Balance report. Additionally, run the Account Balance to Transactions report to determine whether an account does not balance and the period for which it does not balance. Create an out-of-balance entry to correct the original entry.

• The F0902 table contains erroneous data that does not equal the transactions in the F0911 table.

  Create an out-of-balance entry. If necessary, run the Repost Account Ledger program with the processing option set to update the F0902 table so that the F0902 table will match the total of posted records in the F0911 table.

Two Companies are Out of Balance by the Same Amount in the YTD Column

This error appears on the report if the intercompany settlements were not set up properly, and therefore, were not created for some batches during posting. Ensure that you:

• Research the automatic accounting instructions (AAIs) that control intercompany settlements and, if necessary, correct them.

• Restrict the intercompany accounts to automatic journal entries (posting edit code M).

• Verify that the Intercompany Settlements field in the general accounting constants is set to 1 or 2.

To locate the error:

• Run the Intercompany Accounts in Balance report to locate any imbalances.

• Run the Trial Balance by Object report or use the Trial Balance by Object inquiry form to determine the period in which the out-of-balance condition occurs.

To correct the error, create a balancing intercompany journal entry and post with the Intercompany Settlements field set to * in the general accounting constants. If this field is not set to *, the batch creates intercompany settlements, which causes the transaction for each company to net to zero and does not eliminate the out-of-balance condition. When you are finished, you must change this field back to its original setting.

Amount in PACO (Post After Cut Off) Column

This error appears on the report if a journal entry was posted to the next fiscal period or year and it does not net to zero. To correct this error:

• Run the Trial Balance Report for future fiscal periods and years to locate the entry.

  Research the data on the report to determine whether you need to enter two one-sided journal entries to move the amounts to the proper periods. Post these entries out of balance.

• Run the Company by Batch Out of Balance report to identify batches that posted out of balance for the company with the PACO amount.

  Create an out-of-balance entry to correct the original entry. Post the entry out of balance.

Prior Year Total for a Company That is Out of Balance

The reasons for this error to appear on the report include:

• An entry was created in the prior year to reclassify an amount between a balance sheet and an income statement account but the year was not reclosed.

• A batch was posted out of balance in the prior year.

• The F0902 table from the prior year contains erroneous data that does not equal the transactions in the F0911 table.

To correct the error:

• If the prior year entry is a reclassification between a balance sheet and an income statement account, run the Annual Close program (R098201) again to recalculate retained earnings.

• Verify that the AAI item GLG4 for retained earnings is correct.

• If an out-of-balance condition exists in the prior year, run the Batch to Detail report and the Company by Batch Out of Balance report to locate out-of-balance batches.

  Additionally, run the Account Balance to Transactions report to determine whether an account does not balance and the period for which it does not balance. Create an out-of-balance entry in the prior year to correct the original entry, and then run the Annual Close program to recalculate retained earnings.

• If the F0902 table contains erroneous data in the prior year that does not equal the transactions in the F0911 table, enter an out-of-balance journal entry to correct the original entry.

  If necessary, run the Repost Account Ledger program with the processing option set to update the F0902 table. The F0902 table will match the total of posted records in the F0911 table.

Missing Company

This error appears on the report if a company was deleted after journal entries for the company were posted. To correct the error:

• Re-enter the missing company using the Company Names & Numbers program (P0010).

• Transfer the amounts from the missing company to another company.

Running the Intercompany Accounts in Balance Report

This section provides an overview of the Intercompany Accounts in Balance report and discusses how to:

• Print the Intercompany Accounts in Balance report.

• Set processing options for Intercompany Accounts in Balance.

• Locate out-of-balance intercompany accounts.

• Correct discrepancies on the Intercompany Accounts in Balance Report.

Understanding the Intercompany Accounts in Balance Report

If you have multiple companies that are set up for hub or detail intercompany settlements, you should verify that all intercompany accounts are in balance. The Intercompany Accounts in Balance report (R097011):

• Uses information from the F0902 table to compare the balances among the company's various intercompany settlement accounts.

• Determines whether AAI items and the associated intercompany accounts are set up correctly.

• Includes all of the periods in the current year, previous year, and next year.

  The report is not based on any specific financial period.

The intercompany accounts for your companies should be in balance. If they are not, the Intercompany Accounts in Balance report lists the intercompany accounts, their balances, and the amount that is required to balance each account.

Transactions that posted with the intercompany settlement code * do not appear on this report. The system automatically uses this code when batches are posted out of balance. To locate imbalances that are caused by missing intercompany settlements, print the Companies in Balance report.

A message appears on the Intercompany Accounts in Balance report only if these conditions occur:

• All intercompany accounts are in balance.

• The intercompany accounts are not set up in the AAIs.

  Note. If you have multiple companies with different base currencies, do not run this integrity report. Instead, run the Companies in Balance report.

  See Intercompany Accounts in Balance (R097011).

Printing the Intercompany Accounts in Balance Report

Select Integrity Reports and Updates (G0922), Intercompany Accts in Balance.

Setting Processing Options for Intercompany Accounts in Balance (R097011)

Processing options enable you to specify the default processing for reports.

Ledger Type

Locating Out-of-Balance Intercompany Accounts

After reviewing the Intercompany Accounts in Balance report, select any of these methods to locate the out-of-balance intercompany accounts:

• Run the Batch to Detail report.

• Run the Companies in Balance report.

• Review batches or batch types using the General Journal Review program.

• Run the Monthly Spreadsheet report (R10412A) or the Trial Balance By Object Report (R094121) to determine which period is out of balance.

Correcting Discrepancies on the Intercompany Accounts in Balance Report

After running the Intercompany Accounts in Balance report, you should correct any discrepancies that the system detects.

To prevent future out-of-balance conditions, assign the posting edit code M to intercompany accounts to allow only machine-generated transactions.

Intercompany Accounts Do Not Balance

The reasons for this error to appear on the report include:

• The intercompany AAI items were set up improperly.

• Manual journal entries were improperly posted to accounts that should allow only automatic entries.

• Intercompany accounts allow for manual posting and an intercompany entry was made without the offsetting entries.

To correct the error:

• Correct AAI items ICH and ICCC, if they were set up improperly.

• Void or correct incorrect journal entries to intercompany clearing accounts.

Running the Account Balance to Transactions Report

This section provides an overview of the Account Balance to Transactions report and discusses how to:

• Print the Account Balance to Transactions report.

• Set processing options for Account Balance to Transactions.

• Correct discrepancies on the Account Balance to Transactions report.

Understanding the Account Balance to Transactions Report

The Account Balance to Transactions report reviews balances in the F0902 table, verifies the amounts against the posted transactions in the F0911 table, and prints any out-of-balance conditions by period. If this integrity report does not locate F0911 records with the same account number, period number, fiscal year, and ledger type as the F0902 records, it deletes the invalid period balance from the F0902 table as long as these conditions apply:

• A processing option is set to clear invalid period balances.

• The affected ledger type has the Prevent Direct Balance Update check box selected in the Ledger Type Master Setup program (P0025).

If the Account Balance to Transactions report locates F0911 records with corresponding F0902 records, the system does not delete invalid period balances from the F0902 table, regardless of the processing option and ledger type master setup.

See Also

Setting Up Ledger Type Rules for General Accounting

Printing the Account Balance to Transactions Report

Select Integrity Reports and Updates (G0922), Acct Balance to Transactions.

Setting Processing Options for Account Balance to Transactions (R09705)

Processing options enable you to specify the default processing for reports.

Select

Options

Units

Correcting Discrepancies on the Account Balance to Transactions Report

After running the Account Balance to Transactions report, you should correct any discrepancies that the system detects.

To prevent future out-of-balance conditions, consider:

• Placing security on the Work With Batches form to prevent improper changes.

• Assigning responsibility for out-of-balance posting to one individual.

• Allowing only one user to void, change, or delete entries.

Important! To prevent inaccurately deleting records from the F0902 table, ensure that you select the Prevent Direct Balance Update check box in the Ledger Type Master Setup program only for those ledger types that should not allow data entries directly to the F0902 table. Certain ledger types might allow direct updates to the F0902 table, such as the BA ledger or other budgeting ledger types.

Account Balance and Detail Columns are Out of Balance

The reasons for this error to appear on the report include:

• Data entries were damaged by improper void or revision processes.

  If data entries are damaged in the F0911 table, run a data utility program. If data entries are damaged in the F0902 table, run the Repost Account Ledger program.

• An entry was not properly created by the conversion/interface programs.

  Research the error and add the missing entries. Verify the validity of F0911 records and correct the conversion/interface programs.

Balance Column Has an Amount and Detail Column Does Not Have an Amount

This error appears if entries were made directly to the F0902 table. To correct this error, select the Prevent Direct Balance Update option in the Ledger Type Master Setup program for any ledger type that should not allow data entries directly to the F0902 table. Then run the Account Balance to Transactions report with the Clear Invalid Period Balances processing option set to 1 to delete invalid balances from the F0902 table.

Date Pattern is Incorrect

This error appears if changes were made to the fiscal date pattern after journal entries were entered in the system. If the date pattern of the prior company is different from the new company, run the Repost Account Ledger program with the processing option set to print only the report. After reviewing the report, run the Repost Account Ledger program with the processing option set to recalculate the amounts to correct the fiscal period and year balances.

Running the Accounts without Business Units Report

This section provides an overview of the Accounts without Business Units report and discusses how to:

• Print the Accounts without Business Units report.

• Set processing options for Accounts without Business Units.

Understanding the Accounts without Business Units Report

The Accounts without Business Units report (R097041) verifies that a business unit and valid company number exist for each record in the F0901 table. The report compares the F0901 table to the Business Unit Master table (F0006) and lists any discrepancies in which the account master records in the F0901 table do not have corresponding business units in the F0006 table. A missing business unit is identified by * in the Invalid MCU column on the report. The report also lists discrepancies in which the company number is different between the F0901 and F0902 tables.

If you run the report in update mode, the system updates the company number in the F0901 table with the company number in the F0006 table.

The Accounts without Business Units report also identifies accounts that are missing level of detail assignments. Accounts should be assigned a level of detail 3–9. An account with a blank level of detail is identified by * in the Invalid LOD column on the report. If the level of detail for an account is missing and you display levels of detail on a form or print them on a report, the amounts that appear might be overstated or understated.

Note. If your company recently converted its chart of accounts to the JD Edwards EnterpriseOne General Accounting system, ensure that you run this report to identify and correct accounts with missing level of detail information.

You should correct any discrepancies identified on the Accounts without Business Units report before you run the Account Balance without Account Master report.

Printing the Accounts without Business Units Report

Select Integrity Reports and Updates (G0922), Accounts w/o Business Units.

Setting Processing Options for Accounts w/o Business Units (R097041)

Processing options enable you to specify the default processing for reports.

Update

Running the Account Balance without Account Master Report

This section provides an overview of the Account Balance without Account Master report and discusses how to:

• Print the Account Balance without Account Master report.

• Set processing options for Account Balance without Account Master.

• Correct discrepancies on the Account Balance without Account Master report.

Understanding the Account Balance without Account Master Report

The Account Balance without Account Master report (R097031) verifies that an account master number or a valid company number exists for each transaction in the F0902 table. If the account master or company number does not exist, the report prints the account balance information.

If you run the report in update mode, the system updates the company number in the F0902 table with the company number in the F0901 table.

Note. Alternatively, you can run the Update BU.Obj.Sub to Jrnl Ent program (P09806) instead of running this report and the Transactions without Account Master report in update mode. The Update BU.Obj.Sub to Jrnl Ent program automatically updates records in the F0902 table as well as the F0911 table.

Prerequisite

Correct any discrepancies identified on the Accounts without Business Units report before you run the Account Balance without Account Master report.

Printing the Account Balance without Account Master Report

Select Integrity Reports and Updates (G0922), Account Balance w/o Account Master.

Setting Processing Options for Account Balance without Account Master (R097031)

Processing options enable you to specify the default processing for reports.

Update

Correcting Discrepancies on the Account Balance without Account Master Report

After you run the Account Balance without Account Master report, you should correct any discrepancies that the system detects.

Account Master Company Column is Blank

This error appears on the report if the account is not set up. To correct the error, add the account by entering the short account ID from the report using the Review and Revise Accounts program (P0901).

Company Number is Not in the Account Balances Table

This error appears on the report if the company number is not in the F0902 table. To correct the error, set the processing option for this report to update the company number in the F0902 table with the company number in the F0901 table. This processing option is helpful if you change the company number in the account master record and want to globally update the F0902 table.

Running the Transactions without Account Master Report

This section provides an overview of the Transactions without Account Master report and discusses how to:

• Print the Transactions without Account Master report.

• Set processing options for Transactions without Account Master.

• Correct discrepancies on the Transactions without Account Master report.

Understanding the Transactions without Account Master Report

The Transactions without Account Master report (R097021) verifies that for each record in the F0911 table, an account master number or valid company number exists in the F0901 table. If the account master information or company number does not exist in the F0901 table, the report prints every account transaction from the F0911 table.

If you run the report in update mode, the system updates the company number in the F0911 table with the company number in the F0901 table.

Prerequisite

Correct any discrepancies that are identified on the Account Balance without Account Master report before you run the Transactions without Account Master report.

Printing the Transactions without Account Master Report

Select Integrity Reports and Updates (G0922), Transactions w/o Acct Master.

Setting Processing Options for Transactions w/o Acct Master (R097021)

Processing options enable you to specify the default processing for reports.

Update

Correcting Discrepancies on the Transactions without Account Master Report

After you run the Transactions without Account Master report, you should correct any discrepancies that the system detects.

Company Number is Not in the Account Ledger Table

This error appears on the report if the company is not in the F0911 table. To correct the error, set the processing option to update the company number in the F0911 table with the company number from the F0901 table. This processing option is helpful if you change the company number in the F0901 record and want to globally update the F0911 table.