Financial Integrity Reports - История изменений

Yarkin.m в 12:31, 12 марта 2026

2026-03-12T12:31:38Z

Yarkin.m: /* Suggestions and Best Practices for Preventing Integrity Issues */

2024-09-16T11:31:48Z

Suggestions and Best Practices for Preventing Integrity Issues

Yarkin.m: /* Suggestions and Best Practices for Preventing Integrity Issues */

2024-09-16T11:28:47Z

Suggestions and Best Practices for Preventing Integrity Issues

Yarkin.m: /* Suggestions and Best Practices for Preventing Integrity Issues */

2024-09-16T11:28:06Z

Suggestions and Best Practices for Preventing Integrity Issues

Yarkin.m: /* Suggestions and Best Practices for Preventing Integrity Issues */

2024-09-16T11:27:23Z

Suggestions and Best Practices for Preventing Integrity Issues

Yarkin.m: /* Suggestions and Best Practices for Preventing Integrity Issues */

2024-09-16T11:27:01Z

Suggestions and Best Practices for Preventing Integrity Issues

Yarkin.m: /* Suggestions and Best Practices for Preventing Integrity Issues */

2024-09-16T11:26:43Z

Suggestions and Best Practices for Preventing Integrity Issues

Yarkin.m: /* Suggestions and Best Practices for Preventing Integrity Issues */

2024-09-16T11:25:48Z

Suggestions and Best Practices for Preventing Integrity Issues

Yarkin.m: /* Overall recommended order */

2024-09-16T11:24:38Z

Overall recommended order

Yarkin.m: /* Preferred Order of A/P Currency Conversion Integrity Reports */

2024-09-16T11:23:32Z

Preferred Order of A/P Currency Conversion Integrity Reports

← Предыдущая		Версия 12:31, 12 марта 2026
Строка 194:		Строка 194:
	\| 9. \|\| Cash Basis Integrity Test (R11C750) \|\| None.		\| 9. \|\| Cash Basis Integrity Test (R11C750) \|\| None.
	\|}		\|}
		+
		+	[[Категория: Экспорт]]

@@ Строка 10: / Строка 10: @@
 # 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.
+# 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.
+## 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.
+## 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 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.
+## 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.
+## 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 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.
+## 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.
+## 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).
+#: 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.
+#: 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

@@ Строка 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.
+#: 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.
+#: 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.
+#: 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.
+#: 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.
+#: 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.
-#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.
+#: 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.

@@ Строка 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 integrity reports often.
-;# Run one integrity report at a time.
+#: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.
 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.

@@ Строка 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 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.
+;# 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.

← Предыдущая		Версия 11:24, 16 сентября 2024
Строка 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:

← Предыдущая		Версия 11:23, 16 сентября 2024
Строка 122:		Строка 122:

	=== Preferred Order of A/P Currency Conversion Integrity Reports ===		=== 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.
		+	\|}