| Purpose |
| Overview |
| Scope |
| Details |
| Set Up |
| 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) |
| Data Selection |
| 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 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? |
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:
This document is intended for users who are setting up and using EDI to process payments.
There are three default Payment Instruments for Electronic Funds Transfers (EFT) payments in the EDI format: X, Y and Z. In the standard JD Edwards EnterpriseOne demo data setup, these Payment Instruments are assigned the Produce EDI Payment Order/Rmt program (P47052T) as the Write program, and the Payment Register Standard program (P04576) as the Register program. The Produce EDI Payment Order/Rmt program (P47052T) corresponds to the Create A/P Bank Tape - EDI Format UBE (R47052T). This program runs when writing the payment and creates records in the EDI Payment Order Header table (F47056W). The Payment Register Standard program (P04576) corresponds to the A/P Auto Payment Register UBE (R04576). In the Work with Payment Instrument Defaults application (P0417), verify that the correct Write and Register programs are associated for the EDI Payment Instruments. Every Payment Instrument must have both a valid Write program (as defined in UDC 04/PP - Produce Bank File) and Register program (as defined in the UDC 04/PR - Register Program Payments) associated to it.
There are two important fields in the Supplier Master application (P04012) for setting up a supplier to receive EDI payments:
The Bank Accounts by Address application (P0030A) is where the supplier bank account information, such as the Routing number and the Account number, is set up. The Bank Type Code field must be V for Vendor Bank Account.
The GL Bank Account Information application (P0030G) defines the originating company bank account information. Here, the bank transit number, the bank account number and the Bank Account X12 information are identified using a GL Bank Account that exists in the Account Master table (F0901). The PreNote Code on the GL Bank Account overrides the PreNote Code value in the Supplier Master record (F0401). This option produces an EDI payment even if the PreNote Code field is checked in the Supplier Master (P04012).
The Copy to Outbound EDI Files (R47057) is located under the Payment Order with Remittance (G47266) menu. The standard print program provided with JD Edwards EnterpriseOne for creating EDI payment records is the Create AP Bank Tape - EDI (R47052T). When writing payments using this program, the system creates records in the following work tables:
After these records are created, the Copy to Outbound EDI Files (R47057) UBE must be run to transfer the records from the work tables into the associated outbound EDI tables:
As the system copies the payment transactions to the EDI payment interface tables, it marks the corresponding transaction in the EDI work tables as processed by updating EDI Successfully Processed (data dictionary item EDSP) to Y. This change prevents the system from copying already processed records.
The following fields are common to the five tables and used by the Copy to Outbound EDI Files program (R47057) and are the only fields you should use for data selection or data sequencing. If any other fields are used for data selection or data sequencing, the report stops and an error message is thrown.
| Key Field | Data Dictionary Item |
|---|---|
| EDI Document Company | EKCO |
| EDI Document Number | EDOC |
| EDI Document Type | EDCT |
| EDI Line Number | EDLN |
| EDI Successfully Processed | EDSP |
| EDI Batch Number | EDBT |
| Batch Number | ICU |
| Batch Type | ICUT |
| Document Company | KCO |
| Company | CO |
| Business Unit | MCU |
| Payment/Item Number | DOCM |
| Match Document Type | DCTM |
| Pmt/Itm Pay Itm | SFXM |
| Address Number | AN8 |
| Transaction Originator | TORG |
| User ID | USER |
| Program ID | PID |
| Work Stn ID | JOBN |
| Date Updated | UPMJ |
| Time of Day | TDAY |
The Bank Tape tab allows users to print additional information on the Create Payment Groups (R04570) report through the following processing options:
Defaults Tab
Print Tab
The version of the Print Program to be used when writing Automatic Payment Control Groups is specified on the Print tab of the Processing Options of the Work with Payment Groups (P04571). This processing option may need to be changed depending on what Print Program is being used for writing payments during a session of the Work with Payment Groups (P04571) application. If this processing option is left blank, version ZJDE0001 is used.
There are five worktables used in the processing of Outbound EDI transactions:
Although these five tables have many common fields, some hold different values for corresponding records depending on what type of information they contain. Only the common fields that share values amongst the tables should be used for data selection on the Copy to Outbound EDI Files program (R47057). Here is a list of the fields that can be used for data selection:
Prior to writing EDI payments in the Work with Payment Groups application (P04571), the following processing options need to be updated:
After your trading partner has verified the receipt of the transactions, run the Update as Sent program (R47058) from the Payment Order with Remittance menu (G47266). This program updates the Processed (data dictionary item EDPSP) field to Y on the payment transactions in your EDI payment interface tables (F47056, F470561, F470562, F470563, and F47057). This change prevents the translator software from reprocessing the same transactions.
After you successfully process EDI payment transactions, they should be removed from the outbound EDI tables by running the Purge EDI Files report (R47059) from the Payment Order with Remittance menu (G47266). When this program runs, the system removes all processed records (Processed (EDSP) equal to Y) from:
Frequently Asked Questions
Answer 1: The only EDI (Electronic Data Interchange) payment print program is the Create A/P Bank Tape EDI Format (R47052T), which does not use the Swift code that may be necessary for payments to European countries. However, there are several EFT (Electronic Funds Transfer) payment programs that are not EDI specific for those countries:
Answer 2: No. Specifications for the flat file formats for EDI 820 payments are not available through Oracle. The file is created following EDI 820 version 3050 specification.
Answer 3: No, this functionality is not available. The records will need to be manually deleted using a database utility (such as SQL).
Answer 4: The Duplicate Not Allowed error is caused by the Document Number (data dictionary item EDOC) when copying records over that are already present in the EDI Payment Order Header Outbound table (F47056). The system uses Next Numbers to generate the EDI Document Number, therefore, this error is rare. To prevent this from happening in the future, you can either purge the EDI records once they are no longer needed or complete the following steps:
Answer 5: If the Pre-Note Code field (data dictionary item AB1), under the Vouchers tab in the Supplier Master (P04012), is checked, the system writes a physical check (R04572) for the first payment cycle to the supplier. Furthermore, during the payment run, a pre-note entry is made to the EDI Payment Order Header table (F47056W). The Pre-Note Code value may be cleared manually, or the system clears the value after the first automatic payment run with a payment instrument of X, Y or Z. After this field has been cleared, EDI payments are created for the supplier and no additional physical checks are printed.
Answer 6: If the EDI payment is written with the Next Payment Number (data dictionary item NXTC) from the GL Bank Account (P0030G), the Special Handling Code for P04572T2 in UDC table 04/PP might not have a value of 2.
Answer 7: When the Payment Control Group is written, depending on the Payment Instrument a check or EFT is generated. For any EFT, the table F04572OW is populated (This is E1 standard).