Financial Integrity Reports: различия между версиями

Материал из JD Edwards E1
Перейти к навигации Перейти к поиску
 
(не показано 14 промежуточных версий этого же участника)
Строка 1: Строка 1:
 +
== Suggestions and Best Practices for Preventing Integrity Issues ==
 +
# Run integrity reports often.
 +
#: Depending on the size of the company and the volume of transactions entered, users may run integrity reports nightly, weekly, or monthly.  Frequent review of integrity reports aids in rapid identification and resolution of discrepancies.  No single integrity report will verify all data.
 +
# Run one integrity report at a time.
 +
#: Please make note of the Recommended Order.
 +
#: Allow each integrity program to complete prior to running the next.  Running integrity reports in a single-threaded job queue ensures that the programs are run sequentially.
 +
# Run integrities after normal business hours.
 +
#: Some integrity reports read large tables such as the Account Ledger table (F0911), which requires a great deal of processing time.
 +
#: Also, no changes should be made to the data when integrity tests are running.  The integrity reports may show false results if users are entering or posting transactions when the reports are running.
 +
# Save the integrity reports for some amount of time; comparing integrity reports is helpful when researching integrity issues.
 +
# Create a central contact to report, research and correct integrity issues. This contact is responsible for out of balance batches and integrity resolution.
 +
# Assign responsibility to a central contact for making changes or deletions to companies, business units, and accounts.
 +
#: By having a single user or group of users who make changes to important accounting information, records are kept consistent, risk of fraud is lowered and confusion around changes is avoided.
 +
# General Ledger Post (R09801):
 +
## The General Ledger Post program (R09801) can be run in multi-threaded queue since record locking is used on the Account Balance table (F0902).  Coexistent clients should not run the post UBE (R09801) in a multi-threaded queue unless the UBE is exclusively run in EnterpriseOne.
 +
## Post all batches before running integrities (R09801).  This is because some integrity issues are caused by unposted batches.
 +
## When posting transactions, verify the output of the Post Edit report (R09801) to ensure that the correct accounts were debited or credited.  Also verify the work center for any error messages.
 +
# When database corrections are necessary:
 +
## Copy the production data into a test environment, and make the required correction in the test environment first.
 +
## If the results are satisfactory, promote the corrected data to the production environment.
 +
# Security:
 +
## Place security on the Batch Header Revisions program (P0011).  Action Code security can prevent erroneous deletion of batch headers and invalid out of balance postings.
 +
## Place security on System Constants (P0000).  Changes to System Constants impact all users.  Changing some options, such as those related to multicurrency, also change how records are created, which could cause data issues such as duplicate Account Balance table (F0902) records.
 +
## User running integrity reports should not have any security set up.
 +
# Set up batch approval.
 +
#: For more details, please consult KM article "E1: 09: Overview of Batch Approval and Post Security Setup" (P00241/P0000) (Document 664703.1).
 +
# Set the Trade Accounts up with Post Edit Code of "M" (machine generated entries).
 +
#: This limits entries to the accounts to only system-generated records.
 +
# Do not change the Automatic Account Instruction (AAI) for the Trade Accounts unless all transactions are paid (A/P vouchers and A/R invoices) and posted (A/P vouchers and payments; A/R invoices and receipts).
 +
# Do not change the tax percentage for a Tax/Rate Area (P4008); enter a new tax rate instead.
 +
# Consider limiting the number of transactions per batch. Smaller batches are easier to research
 +
 
==Overall recommended order==
 
==Overall recommended order==
 
# Create Baselines:
 
# Create Baselines:
Строка 34: Строка 66:
  
 
  Note - The following reports are not dependent on each other, this is only Oracle Support's recommended order.  It is important to run each and clean up any discrepancies before running the next report.
 
  Note - The following reports are not dependent on each other, this is only Oracle Support's recommended order.  It is important to run each and clean up any discrepancies before running the next report.
 +
 +
===  A/R Integrity Reports===
 +
These can be found on Menu G03B21.
 +
 +
KM articles to help you run and research these integrity reports:
 +
* E1: 03B: How To Run and Research Accounts Receivable Integrity Issues  (Document 2242260.2)
 +
* E1: 03B: FAQ - Frequently Asked Questions on Accounts Receivable Integrity Reports … (Document 872884.1)
 +
 +
Recommended order just for A/R integrities:
 +
# AR to Account Balance by Account ID (R03B707) as a baseline
 +
# Batch to Detail (R007031)
 +
# Transactions to Batch Header (R007021)
 +
# Unposted Batches (R007011)
 +
# AR to GL by Batch Integrity Report (R03B701)
 +
# AR to GL Receipts by Batch (R890911BI)
 +
# F03B11 to F03B14 Integrity (R8903B14I)
 +
# General Journal by Account Report (R09311) for the A/R Trade account(s) with data selection set to Document Type not equal to AE
 +
# AR to Account Balance by Account ID (R03B707): compare to its baseline
 +
 +
=== A/P Integrity Reports ===
 +
These can be found on Menu G0421.
 +
 +
KM articles to help you run and research these integrity reports:
 +
 +
* E1: 04: How To Run EnterpriseOne Accounts Payable Integrity Reports ... (Document 1407766.1)
 +
* E1: 04: FAQ - Frequently Asked Questions Regarding AP Integrity Reports ...  (Document 663128.1)
 +
 +
Recommended order just for A/P integrities:
 +
# AP to GL Integrity by Offset Account report (R047001A) as a baseline
 +
# Batch to Detail (R007031)
 +
# Transactions to Batch Header (R007021)
 +
# Unposted Batches (R007011)
 +
# AP to GL by Batch (R04701)
 +
# AP Payments to Voucher (R04713)
 +
# AP Payments to GL by batch (R04702A)
 +
# General Journal by Account Report (R09311) for the A/P Trade account(s) with data selection set to Document Type not equal to AE
 +
# AP to GL Integrity by Offset Account report (R047001A): compare to its baseline
 +
 +
===G/L Integrity Reports===
 +
These can be found on Menu G0922.
 +
 +
KM articles to help you run and research these integrity reports:
 +
* E1: 09: How To Troubleshoot EnterpriseOne General Ledger Integrity Issues (Document 1541001.1)
 +
* E1: 09: Overview of General Accounting Integrity Reports ... (Document 664780.1)
 +
 +
Recommended order just for G/L integrities:
 +
# Account Balance to Transactions (R09705) as a baseline
 +
# Repost Account Ledger Report (R099102) as a baseline
 +
# Unposted Batches (R007011)
 +
# Transactions to Batch Header (R007021)
 +
# Batch to Detail (R007031)
 +
# Batches Out of Balance (R007032)
 +
# Transactions without Account Master (R097021)
 +
# Account Balance without Account Master (R097031)
 +
# Accounts without Business Units (R097041)
 +
# Companies in Balance (R097001)
 +
# Company by Batch Out of Balance (R09706)
 +
# Intercompany Accounts in Balance (R097011)
 +
# Account Balance to Transactions (R09705): compare to its baseline
 +
# Repost Account Ledger Report (R099102): compare to its baseline
 +
 +
==Base Currency Conversion Integrity Reports==
 +
 +
===Preferred Order of A/R Currency Conversion Integrity Reports ===
 +
 +
{| class="wikitable"
 +
! # !! Report Name (Program Number) !! Prerequisite For Running In Final Mode
 +
|-
 +
| 1. || F03B11 to F03B22 Integrity (R8903B22I) || None
 +
|-
 +
| 2. || F03B11 to F03B40 Integrity (R8903B40I) || Run the F03B11 to F03B22 Integrity report.
 +
|-
 +
| 3. || F03B11 to F03B14 Integrity (R8903B14I) || Run the F03B11 to F03B40 Integrity report.
 +
|-
 +
| 4. || F03B14 to F03B41 Integrity (R8903B41I) || Run the F03B11 to F03B14 Integrity report.
 +
|-
 +
| 5. || F03B14 to F03B13 Integrity (R8903B13I) || Run the F03B14 to F03B41 Integrity report.
 +
|-
 +
| 6. || F03B22 to F03B23 Integrity (R8903B23I) || Run the F03B14 to F03B13 Integrity report.
 +
|-
 +
| 7. || F03B11 to F0911 Integrity (R890911AI) || Run the F03B22 to F03B23 Integrity report.
 +
|}
 +
 +
All these reports have proof and final modes. For more information on what the reports do in each mode, and any setup needed for these reports, please review Section 7.2.1 Completing the Accounts Receivable Preconversion Integrity Checklist of the following online guides:
 +
* JD Edwards EnterpriseOne Applications Base Currency Conversion Implementation Guide for Release 9.2
 +
* JD Edwards EnterpriseOne Applications Base Currency Conversion Implementation Guide for Release 9.1
 +
 +
=== Preferred Order of A/P Currency Conversion Integrity Reports ===
 +
 +
{| class="wikitable"
 +
! # !! Report Name (Program Number)  !! Prerequisite For Running In Final Mode
 +
|-
 +
| 1. || F0411 to F0911 Integrity (R04711) || None.
 +
|-
 +
| 2. || F0414 to F0411 Integrity (R04713) || None.
 +
|-
 +
| 3. || F0414 to F0911 Integrity (R04712) || Run the F0414 to F0411 Integrity and F0411 to F0911 Integrity reports.
 +
|-
 +
| 4.  || A/P to G/L Integrity by Offset Account (R047001A) || None.
 +
|}
 +
 +
All these reports have proof and final modes. For more information on what the reports do in each mode, and any setup needed for these reports, please review Section 7.2.2 Completing the Accounts Payable Preconversion Integrity Checklist of the following online guides:
 +
* JD Edwards EnterpriseOne Applications Base Currency Conversion Implementation Guide for Release 9.2
 +
* JD Edwards EnterpriseOne Applications Base Currency Conversion Implementation Guide for Release 9.1
 +
 +
=== Preferred Order of G/A Currency Conversion Integrity Reports ===
 +
 +
{| class="wikitable"
 +
! # !! Report Name (Program Number) !! Prerequisite For Running In Final Mode
 +
|-
 +
| 1. || Unposted General Journal (R09301) || None.
 +
|-
 +
| 2. || Accounts without Business Units (R097041) || None.
 +
|-
 +
| 3. || Account Balance without Account Master (R097031) || None.
 +
|-
 +
| 4. || Transactions without Account Master (R097021) || None.
 +
|-
 +
| 5. || Companies in Balance (R097001) || None.
 +
|-
 +
| 6. || Intercompany Accounts in Balance (R097011) || None.
 +
|-
 +
| 7. || Account Balance to Transactions (R09705) || None.
 +
|-
 +
| 8. || Foreign Account Balances (R09707) || None.
 +
|-
 +
| 9. || Cash Basis Integrity Test (R11C750) || None.
 +
|}

Текущая версия на 14:31, 16 сентября 2024

Suggestions and Best Practices for Preventing Integrity Issues

  1. Run integrity reports often.
    Depending on the size of the company and the volume of transactions entered, users may run integrity reports nightly, weekly, or monthly. Frequent review of integrity reports aids in rapid identification and resolution of discrepancies. No single integrity report will verify all data.
  2. Run one integrity report at a time.
    Please make note of the Recommended Order.
    Allow each integrity program to complete prior to running the next. Running integrity reports in a single-threaded job queue ensures that the programs are run sequentially.
  3. Run integrities after normal business hours.
    Some integrity reports read large tables such as the Account Ledger table (F0911), which requires a great deal of processing time.
    Also, no changes should be made to the data when integrity tests are running. The integrity reports may show false results if users are entering or posting transactions when the reports are running.
  4. Save the integrity reports for some amount of time; comparing integrity reports is helpful when researching integrity issues.
  5. Create a central contact to report, research and correct integrity issues. This contact is responsible for out of balance batches and integrity resolution.
  6. Assign responsibility to a central contact for making changes or deletions to companies, business units, and accounts.
    By having a single user or group of users who make changes to important accounting information, records are kept consistent, risk of fraud is lowered and confusion around changes is avoided.
  7. General Ledger Post (R09801):
    1. The General Ledger Post program (R09801) can be run in multi-threaded queue since record locking is used on the Account Balance table (F0902). Coexistent clients should not run the post UBE (R09801) in a multi-threaded queue unless the UBE is exclusively run in EnterpriseOne.
    2. Post all batches before running integrities (R09801). This is because some integrity issues are caused by unposted batches.
    3. When posting transactions, verify the output of the Post Edit report (R09801) to ensure that the correct accounts were debited or credited. Also verify the work center for any error messages.
  8. When database corrections are necessary:
    1. Copy the production data into a test environment, and make the required correction in the test environment first.
    2. If the results are satisfactory, promote the corrected data to the production environment.
  9. Security:
    1. Place security on the Batch Header Revisions program (P0011). Action Code security can prevent erroneous deletion of batch headers and invalid out of balance postings.
    2. Place security on System Constants (P0000). Changes to System Constants impact all users. Changing some options, such as those related to multicurrency, also change how records are created, which could cause data issues such as duplicate Account Balance table (F0902) records.
    3. User running integrity reports should not have any security set up.
  10. Set up batch approval.
    For more details, please consult KM article "E1: 09: Overview of Batch Approval and Post Security Setup" (P00241/P0000) (Document 664703.1).
  11. Set the Trade Accounts up with Post Edit Code of "M" (machine generated entries).
    This limits entries to the accounts to only system-generated records.
  12. Do not change the Automatic Account Instruction (AAI) for the Trade Accounts unless all transactions are paid (A/P vouchers and A/R invoices) and posted (A/P vouchers and payments; A/R invoices and receipts).
  13. Do not change the tax percentage for a Tax/Rate Area (P4008); enter a new tax rate instead.
  14. Consider limiting the number of transactions per batch. Smaller batches are easier to research

Overall recommended order

  1. Create Baselines:
    • AP to GL Integrity by Offset Account report (R047001A) as a baseline
    • AR to Account Balance by Account ID (R03B707) as a baseline
    • Account Balance to Transactions (R09705) as a baseline
    • Repost Account Ledger Report (R099102) as a baseline
  2. Batch Header integrities:
    • Unposted Batches (R007011)
    • Transactions to Batch Header (R007021)
    • Batch to Detail (R007031)
    • Batches Out of Balance (R007032)
  3. G/L integrities for accounts and companies:
    • Transactions without Account Master (R097021)
    • Account Balance without Account Master (R097031)
    • Accounts without Business Units (R097041)
    • Companies in Balance (R097001)
    • Company by Batch Out of Balance (R09706)
    • Intercompany Accounts in Balance (R097011)
  4. A/P integrities:
    • AP to GL by Batch (R04701)
    • AP Payments to Voucher (R04713)
    • AP Payments to GL by batch (R04702A)
    • General Journal by Account Report (R09311) for the A/P Trade account(s) with data selection set to Document Type not equal to AE
    • AP to GL Integrity by Offset Account report (R047001A): compare to its baseline
  5. A/R integrities:
    • AR to GL by Batch Integrity Report (R03B701)
    • AR to GL Receipts by Batch (R890911BI)
    • F03B11 to F03B14 Integrity (R8903B14I)
    • General Journal by Account Report (R09311) for the A/R Trade account(s) with data selection set to Document Type not equal to AE
    • AR to Account Balance by Account ID (R03B707): compare to its baseline
  6. Final G/L integrities:
    • Account Balance to Transactions (R09705): compare to its baseline
    • Repost Account Ledger Report (R099102): compare to its baseline
Note - The following reports are not dependent on each other, this is only Oracle Support's recommended order.  It is important to run each and clean up any discrepancies before running the next report.

A/R Integrity Reports

These can be found on Menu G03B21.

KM articles to help you run and research these integrity reports:

  • E1: 03B: How To Run and Research Accounts Receivable Integrity Issues (Document 2242260.2)
  • E1: 03B: FAQ - Frequently Asked Questions on Accounts Receivable Integrity Reports … (Document 872884.1)

Recommended order just for A/R integrities:

  1. AR to Account Balance by Account ID (R03B707) as a baseline
  2. Batch to Detail (R007031)
  3. Transactions to Batch Header (R007021)
  4. Unposted Batches (R007011)
  5. AR to GL by Batch Integrity Report (R03B701)
  6. AR to GL Receipts by Batch (R890911BI)
  7. F03B11 to F03B14 Integrity (R8903B14I)
  8. General Journal by Account Report (R09311) for the A/R Trade account(s) with data selection set to Document Type not equal to AE
  9. AR to Account Balance by Account ID (R03B707): compare to its baseline

A/P Integrity Reports

These can be found on Menu G0421.

KM articles to help you run and research these integrity reports:

  • E1: 04: How To Run EnterpriseOne Accounts Payable Integrity Reports ... (Document 1407766.1)
  • E1: 04: FAQ - Frequently Asked Questions Regarding AP Integrity Reports ... (Document 663128.1)

Recommended order just for A/P integrities:

  1. AP to GL Integrity by Offset Account report (R047001A) as a baseline
  2. Batch to Detail (R007031)
  3. Transactions to Batch Header (R007021)
  4. Unposted Batches (R007011)
  5. AP to GL by Batch (R04701)
  6. AP Payments to Voucher (R04713)
  7. AP Payments to GL by batch (R04702A)
  8. General Journal by Account Report (R09311) for the A/P Trade account(s) with data selection set to Document Type not equal to AE
  9. AP to GL Integrity by Offset Account report (R047001A): compare to its baseline

G/L Integrity Reports

These can be found on Menu G0922.

KM articles to help you run and research these integrity reports:

  • E1: 09: How To Troubleshoot EnterpriseOne General Ledger Integrity Issues (Document 1541001.1)
  • E1: 09: Overview of General Accounting Integrity Reports ... (Document 664780.1)

Recommended order just for G/L integrities:

  1. Account Balance to Transactions (R09705) as a baseline
  2. Repost Account Ledger Report (R099102) as a baseline
  3. Unposted Batches (R007011)
  4. Transactions to Batch Header (R007021)
  5. Batch to Detail (R007031)
  6. Batches Out of Balance (R007032)
  7. Transactions without Account Master (R097021)
  8. Account Balance without Account Master (R097031)
  9. Accounts without Business Units (R097041)
  10. Companies in Balance (R097001)
  11. Company by Batch Out of Balance (R09706)
  12. Intercompany Accounts in Balance (R097011)
  13. Account Balance to Transactions (R09705): compare to its baseline
  14. Repost Account Ledger Report (R099102): compare to its baseline

Base Currency Conversion Integrity Reports

Preferred Order of A/R Currency Conversion Integrity Reports

# Report Name (Program Number) Prerequisite For Running In Final Mode
1. F03B11 to F03B22 Integrity (R8903B22I) None
2. F03B11 to F03B40 Integrity (R8903B40I) Run the F03B11 to F03B22 Integrity report.
3. F03B11 to F03B14 Integrity (R8903B14I) Run the F03B11 to F03B40 Integrity report.
4. F03B14 to F03B41 Integrity (R8903B41I) Run the F03B11 to F03B14 Integrity report.
5. F03B14 to F03B13 Integrity (R8903B13I) Run the F03B14 to F03B41 Integrity report.
6. F03B22 to F03B23 Integrity (R8903B23I) Run the F03B14 to F03B13 Integrity report.
7. F03B11 to F0911 Integrity (R890911AI) Run the F03B22 to F03B23 Integrity report.

All these reports have proof and final modes. For more information on what the reports do in each mode, and any setup needed for these reports, please review Section 7.2.1 Completing the Accounts Receivable Preconversion Integrity Checklist of the following online guides:

  • JD Edwards EnterpriseOne Applications Base Currency Conversion Implementation Guide for Release 9.2
  • JD Edwards EnterpriseOne Applications Base Currency Conversion Implementation Guide for Release 9.1

Preferred Order of A/P Currency Conversion Integrity Reports

# Report Name (Program Number) Prerequisite For Running In Final Mode
1. F0411 to F0911 Integrity (R04711) None.
2. F0414 to F0411 Integrity (R04713) None.
3. F0414 to F0911 Integrity (R04712) Run the F0414 to F0411 Integrity and F0411 to F0911 Integrity reports.
4. A/P to G/L Integrity by Offset Account (R047001A) None.

All these reports have proof and final modes. For more information on what the reports do in each mode, and any setup needed for these reports, please review Section 7.2.2 Completing the Accounts Payable Preconversion Integrity Checklist of the following online guides:

  • JD Edwards EnterpriseOne Applications Base Currency Conversion Implementation Guide for Release 9.2
  • JD Edwards EnterpriseOne Applications Base Currency Conversion Implementation Guide for Release 9.1

Preferred Order of G/A Currency Conversion Integrity Reports

# Report Name (Program Number) Prerequisite For Running In Final Mode
1. Unposted General Journal (R09301) None.
2. Accounts without Business Units (R097041) None.
3. Account Balance without Account Master (R097031) None.
4. Transactions without Account Master (R097021) None.
5. Companies in Balance (R097001) None.
6. Intercompany Accounts in Balance (R097011) None.
7. Account Balance to Transactions (R09705) None.
8. Foreign Account Balances (R09707) None.
9. Cash Basis Integrity Test (R11C750) None.
Источник — http://wiki.sgsproject.nichost.ru/index.php?title=Financial_Integrity_Reports&oldid=108518