Troubleshooting Voucher Batch Processing Error(s) In EnterpriseOne (P0411Z1/R04110ZA)

Purpose

This document provides troubleshooting suggestions regarding Voucher Batch Processing within EnterpriseOne.

Troubleshooting Steps

Errors in Processing

If any errors occur during processing, they are noted on the edit report. You can correct the errors and reprocess the batch. An error on one transaction does not stop the batch from processing. If a transaction in the batch is in error, that transaction is not processed with the rest of the batch. After the batch has been successfully processed, the field VLEDSP is updated from a value of 0 to 1. Successfully processed records remain in the Voucher Transactions - Batch Upload (F0411Z1) and Journal Entry Transactions - Batch File (F0911Z1) tables until they are purged.

Troubleshooting Recommendations

• Initially process a small number of records in a batch. Most errors that occur on one record also occur on all records. Correct the errors on the smaller number of records, and then follow the same sequence of steps when you process a larger number of records in a batch.
• Only errors prevent a batch from processing. Warning messages alert you to nonstandard events, but do not prevent processing. You can disable warning messages by means of a processing option.
• You can run the batch in Proof Mode. However, this may not be necessary as even in Final Mode you can review the transactions before posting during which time they could be deleted. Any errors encountered with the records will prevent those records from being processed.
• Reading error messages in the Work Center helps identify the cause and the resolution of errors. All error messages are also located in the data dictionary, where you can locate the error number and review the glossary.
• If errors occur that you cannot resolve, enter a transaction manually using the Batch Supplier Master Revision program (P0401Z1), and process it successfully. Then compare the table entries of the F0411Z1 transaction that you entered manually with the entries from an F0411Z1 transaction entered using the Batch Voucher Processor Report program (R04110ZA). Comparing the differences helps you locate discrepancies and resolve the errors. See steps below for instructions.

Manual Testing Steps

1. Go to menu G04311
2. Select Batch Voucher Revisions (P0411Z1/ZJDE0001)
3. Enter in a test voucher through this screen and click OK
4. On same menu, select Batch Voucher Processor (R04110ZA/ZJDE0001) and try to process this test voucher batch you created above.

If successful, you can use the F0411Z1 and F0911Z1 tables as a mapping guide for your custom upload program data. Such as Compare F0411Z1 test record to your production F0411Z1 for alignment issues, fields populated versus not populated (i.e. required versus optional), compare F0911Z1 test record to your production F0911Z1 for alignment issues, fields populated versus not populated (i.e. required versus optional), check for NULL values versus Blank value.

Common Errors

Error ID: 0809 "Document Type Invalid"

Scenario: What causes the Batch Voucher Processor Report (R04110ZA) to trigger error "Document type for a manual check entry must be PM" when processing voucher information without payment details?

CAUSE . . . . Document type for a manual check entry must be 'PM'.

RESOLUTION. . Enter a valid document type.

Solution: This error may be caused by incorrect settings in the Batch Voucher Revisions application (P0411Z1) Processing Options. When Processing Option 1: Manual Check on the Manual Checks tab is set to '1', the system attempts to create a voucher in a 'W' type batch (Manual Payment without Voucher Match) and requires a payment number to be stored in the Matching Document field (data dictionary item DOCM) in the Voucher Transactions Batch Upload table (F0411Z1). If this field is blank, the system triggers an error. To correct this issue, follow the steps below:

1. Remove the data from the Voucher Transactions Batch Upload (F0411Z1) and the Journal Entry Transactions Batch File (F0911Z1) table using Batch Voucher Entry (P0411Z1).
2. Update Processing Option 1: Manual Check on the Manual Checks tab to blank.
3. Enter the batch voucher information again into the worktables (F0411Z1 and F0911Z1).
4. Run the Batch Voucher Processor Report (R04110ZA).

Error Message: "Fetch from table F0911Z1T failed"

Scenario: Why does the Batch Voucher Processing Report (R04110ZA) run successfully, but send a "Fetch from table F0911Z1T failed" error message to the Work Center (P012503)?

Solution: This error in the Work Center is caused by Cost Management being enabled in the Cost Management Constants (P1609). For more information, refer to How To Set Up and Map Data For Voucher Batch Processing In EnterpriseOne (P0411Z1/R04110ZA) [Video]"

Error ID 0082 or 1912: "Duplicate Supplier/Invoice Number"

Scenario: Why does the Batch Voucher Processing Report (R04110ZA) return the error message "Duplicate Supplier/Invoice Number"?

Solution: This Issue is caused by the setup in the Accounts Payable Constants (P0000). If the Duplicate Invoice Number Edit (data dictionary item DUIN) option is set to 'H', the system triggers this error when creating a voucher with a duplicate invoice number. To correct this error, either change the invoice number (data dictionary item VINV) to a unique value or alter the Duplicate Invoice Number Edit option.

Error ID "The record being added already exists in cache I09UI003"

Scenario: Why does the Batch Voucher Processing Report (R04110ZA) return the error message " The Record being added already exists in cache 109U1003".

Solution: This issue can be caused if the system detects a duplicate record in one the files being processed. In this case, the logs described that one record inserted into the cache correctly (for an amount, on one of the F0911Z1 lines), and then the error is thrown when it tries to insert the other line into the cache. To correct this error, change one of the JELN lines (not the EDLN) to 2.0.

General Troubleshooting Questions

Question 1: What issue can occur if the F0411Z1 and F0911Z1 records do not correspond?

Answer 1: Because the programs perform data selection and sequencing of the transactions before the first record is read for processing, the following situations could occur that will result in errors:

• A Journal Entry Transactions Batch File table (F0911Z1) record exists with a document number for which there is no corresponding Voucher Transactions Batch Upload table (F0411Z1) record. In this situation, the system stops processing Journal Entry Transactions Batch File table (F0911Z1) records and all records in the tables from this point forward are out of balance.
• A Voucher Transactions Batch Upload table (F0411Z1) record exists with a document number for which there is no corresponding Journal Entry Transactions Batch File table (F0911Z1) record. In this situation, the system writes an error message and continues to process subsequent records.

Question 2: After running the Batch Voucher Processing Report (R04110ZA), why is the Document Company field not the same as the value written in the F0411Z1 table?

Answer 2: It is possible that the original value in the Voucher Transactions Batch Upload table (F0411Z1) and Journal Entry Transactions Batch File table (F0911Z1) does not exist in the Company Constants table (F0010). Another possibility is that the Document Company (data dictionary item KCO) was not populated in the Journal Entry Transactions Batch File table (F0911Z1). When specifying this information in the batch voucher process, ensure both worktables contain the same value for associated records.