E1: 04: How To Set Up and Process EDI Payments (820) (R47052T/R47057/R47058) (Doc ID 661977.1)

Last updated on JUNE 17, 2024

Applies to:

JD Edwards EnterpriseOne Accounts Payable - Version XE and later
JD Edwards EnterpriseOne EDI - Version 9.1 to 9.1 [Release 9.1]
Information in this document applies to any platform.

Purpose

Overview

When using EDI Payments, Accounts Payable payment transactions are created and stored in the EDI interface tables so they may be sent as outbound EDI 820 transmissions. EDI payments are created using the same process as other automatic payments. The only difference is the Payment Instrument (data dictionary item PYIN) used should point to a program that creates electronic payment files rather than physical checks. The standard EDI Payment Program is Create AP Bank Tape - EDI (R47052T). After EDI payments are created, you must also:

Transfer outbound payment transactions.
Run the Update as Sent program (R47058).
Purge processed outbound EDI payments.

Note: Please refer to JD Edwards EnterpriseOne Data Interface for Electronic Data Interchange 9.0 Implementation Guide, Understanding Data Interface for the Electronic Data Interchange System section and Processing EDI Documents for more details on the EDI process within JD Edwards EnterpriseOne. To access online guides refer to knowledge <Document 1437787.1>.

Scope

This document is intended for users who are setting up and using EDI to process payments.

Details

	To view full details, sign in with your My Oracle Support account.
	Don't have a My Oracle Support account? Click to get started!

In this Document

Payment Instrument (P0417)

Supplier Master Information (P04012)

Bank Accounts by Address (P0030A)

GL Bank Account Information (P0030G)

Copy to Outbound EDI Files (R47057)

Important Processing Options for Creating EDI Payments

Create Payment Control Groups (R04570)

Create A/P Bank Tape - EDI Format (R47052T)

Work with Payment Groups (P04571)

Updating Processed Transactions (R47058)

Purging Processed Outbound EDI Payments (R47059)

Question 1: Does JD Edwards EnterpriseOne provide a Payment Print Program for EDI Payments to European countries (i.e. UK, Germany, Switzerland, or France)?

Question 2: Does Oracle provide detail specifications of the flat file layout for the EDI 820 payment process?

Question 3: Is there a program to purge the records in the EDI worktables: (EDI Payment Order Header F47056W, EDI Payment Order Bank F470561W, EDI Payment Order Vendor F470562W, EDI Payment Order Payee F470563W, EDI Payment Order Remittance Advice F47057W)?

Question 4: When running the Copy To Outbound EDI File UBE (R47057), why are the records not copied to the EDI Payment Order Header Outbound table (F47056), even though they were added to the remaining EDI outbound tables and the "Duplicate Not Allowed' error message is being thrown?

Question 5: Why does the system create a check (R04572) when running EDI payment R47052T?

Question 6: Why is the system using the Next Payment Number from the GL Bank Account when writing an EDI payment?

Question 7: Why are records written to the ACH table F04572OW while processing EDI 820 transactions when running the R47052T UBE?

Question 8: When undoing or resetting an EDI payment group, is the payment bank tape file removed?

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.