Troubleshooting JD Edwards EnterpriseOne Accounts Payable Payment (K or M) Batch Types Post Failure (R09801, P09801)

Purpose

This document has been created to help troubleshoot a specific automatic payment batch (K) post failure due to an out of balance condition.

Troubleshooting Steps

Overview

This troubleshooting document provides assistance with resolving this specific post failure condition below:

• A post failure within JD Edwards EnterpriseOne Accounts Payable automatic payment batch (K) that errors:
• Amount out of balance condition between A/P Payment Ledger Header (F0413) and A/P Payment Ledger Detail (F0414) and/or
• Failure causes interruption during post process
• Key factors included:
• Issue is in non-currency environment
• No taxes/vertex involved
• No discounts involved

Basic Post Overview Video Presentation

Below you will find a link to our AP Payment basic post presentation. This includes an overview for automatic payment processing, manual payment with voucher match payment processing and manual payment without voucher match payment processing.

Data Collection Instructions - (Summarized Details)

Oracle support will ask for these items below to troubleshoot this specific post failure scenario:

1. Query F0413 and F0911 by batch number (ICU) only, export to excel.
1. The General Ledger (F0911) only exists if batch has partially or successfully posted. You may find zero records.
2. The General Ledger (F0911) is the key table that determines how the payment batch can be resolved.
2. From the F0413 query in step 1 above, gather all unique payment ID numbers (PYID) and query the F0414, export to excel.
3. From F0414 in step 2 above, gather all unique voucher document numbers, query F0411, export to excel.
   1. A/P Payment Detail table (F0414) does not have batch number (ICU) as a field. The A/P Payment Header table (F0413) connects to the detail table (F0414) only by payment ID number.
4. Attach R09801 for same batch number
5. Attach R09801E for same batch number
6. Attach image of work center error(s) for same batch number

Data Collection Instructions - (Full Details)

For full details on how to use data browser, please refer to Databrowser Troubleshooting Tips. Scroll to to the "Additional Information" section for links to our online guide library based on your tools release.

Successful Post Summary

• When you create an automatic payment you first go through a series of processes.
• First you run the "Create Payment Control Group" program (R04570) process where you create data within the temporary payment worktables:
• F04571 (Temporary Payment Header)
• F04572 (Temporary Payment Headers)
• F04573 (Temporary Payment Details - Voucher details)
• After the payment control group is created you then use the "Work With Payment Control Groups" program (P04571) process to write the payments.
• After you review the payments that were created, then you use the same "Work With Payment Control Groups" program (P04571) to update the payment control group which converts the data from the temporary payment tables to the main payment tables, which are:
  
  • F0011 (Batch Header)
  • F0413 (Payment Header - Payment summary information)
  • F0414 (Payment Details - Voucher details)
• When the group is updated, if the batch is not auto posted, there are no General Ledger entries (F0911) created yet.
• When you post the payment batch the A/P Payment tables (F0413 and F0414) are updated with a post code of D and the payment records are added to the General Ledger along with an AE entry to trade both with post codes of P.
• Reminder - Your AE entries are either created in detail, per voucher the payments pay, or by batch depending on your offset method set in the constants. See Understanding Accounts Payable Payment Post Process Within JD Edwards EnterpriseOne Financial Management (R09801, P00241) for full details.

Good Record Example before Automatic Payment Posts to General Ledger

F0413 Key Fields

F0414 Key Fields

Good Record Example After Automatic Payment Posts to the General Ledger

F0413 Key Fields

F0414 Key Fields

F0911 Key Fields

Out Of Balance Post Failure Scenarios

See examples listed below and refer to the video presentation for a live demo exampl as well.

AP Payment Out Of Balance Live Demo Example and Overview Presentation (Video)

Below you will find a link to our AP Voucher and AR Invoice Basic Post Presentation.

Scenario 1: Automatic Payment Batch (K) Has A/P Ledger Header (F0413) Out Of Balance To A/P Ledger Detail (F0414)

First complete the data browser query instructions listed at the beginning of this troubleshooting document. Next, review your excel sheet to compare your F0413 to your F0414 tabes for the batch in question.

A/P Ledger Header table (F0413) and A/P Ledger Detail table (F0414) Key fields To Review:

F0413 Key Fields

F0414 Key Fields

In this Post Failure example above, this is the issue:

• Comparing A/P Ledger Header table (F0413) by payment ID equal to 4321 the total shows as 2,000.00 where as the A/P Ledger Detail table (F0414) shows for payment ID equal to 4321 a grand total of 3,000.00 causing an out of balance condition of 1,000.00 therefore the post fails.
• Post failure results:
• The F0911 did not get posted and no AE(s) was created in the F0911 for this voucher and it set the F0413 post code to failure status of P.
• Repeat this same comparison above for every payment, using payment ID (PYID), to find all payments with an out of balance condition.
• Once you gather all the payment(s) that need corrections:
• Use a database utility to make the correction(s):
• Update the table with the incorrect amount
• Update the failed post code(s) in the F0413 from P to blank (space value not NULL)
• Approve the batch header
• Attempt to post.

Scenario 2: Failure Interrupts Post Process - (GL Posted Successfully A/P Payment Ledgers Post Failed)

F0413 Key Fields

F0414 Key Fields

F0911 Key Fields

In post failure example above, this is the issue:

• The General Ledger (F0911) shows the payment 1234 posted successfully and the system properly created the AEs entry to trade account, however, due to system failure the A/P Payment Ledger tables (F0413 and F0414) stopped the post process and were set to a post failure status of P.
• Post failure results:
• The F0413 did not finish the post process and has set the post code (POST) to a failure code of P.
• Repeat this same comparison above for every payment, using payment ID (PYID), to find all payments with an out of balance condition.
  
  • Once you gather all the payment(s) that need corrections:
  • Use a database utility to make the correction(s):
  • Update the failed post code(s) in the F0413 and F0414 from P to D (Posted) status.
  • Update the batch header (F0011) for this batch only and set the status to Posted.