Purpose |
Troubleshooting Steps |
Payment Instrument and Print Program Set Up (P0417) |
Work with Payment Instrument Defaults (P0417) |
Print Programs |
Print Payment Hierarchy |
Reprint Check Register |
Supplier Master Information (P04012) |
Troubleshooting Error(s) |
Error:"Duplicate Not Allowed" |
Frequently Asked Questions |
Question 1: Can there be multiple records in the Work with Payment Instrument Defaults program for the same payment instrument? |
Question 2: Is it possible to pay vouchers using a credit card? |
Question 3: What are the different valid Special Handling code values for UDC 00/PY - Payment Instruments? |
Question 5: Why is payee information printing on the check? |
>
This document helps troubleshoot Payment Instrument and Print Program Set Up and Errors (P0417).
Payment instruments are used to determine what type of payment is produced for a voucher or group of vouchers. Payment instruments are defined in UDC table 00/PY (Payment Instrument). The Code (data dictionary item KY) in this table is a single character field and can be any letter, number or symbol. For more information, see Overview of EnterpriseOne Accounts Payable Setup. It is recommended that UDC table 00/PY (Payment Instrument) include a blank value as a default for any suppliers without a payment instrument configured in the Supplier Master (P04012).
After a payment instrument is defined in UDC table 00/PP (Payment Instrument), the Work with Payment Instrument Defaults (P0417) is used to link it to a:
As of release 8.9, versions of the print programs can also be specified for all UBEs associated with a payment instrument.
Payment instruments can also be associated to specific GL Bank Accounts in the Work with Payment Instrument Defaults (P0417). The system determines what payment instrument to use for groups of vouchers from the A/P Payments - Default Print and Update (F0417) based on the Payment Instrument (PYIN) and GL Bank Account (ANI) in the following hierarchy:
Some of the programs associated with a payment instrument have processing options that further define the format of a payment. It is important to review and, if necessary, revise these processing options before using each program. Although the programs are defined as Pxxxxx (where x is the program number) in the Work with Payment Instrument Defaults (P0417), the actual programs that run during the Write process of a payment are UBEs with a naming convention of Rxxxxx (where x is the program number). For example, the P04572, the standard print payment format, is equivalent to R04572 in the Work with Batch Versions (P98305W).
To review the processing options for any of the print programs, follow these steps:
1. From the System Administration Tools menu (GH9011), choose Batch Versions.
2. On Work With Batch Versions - Available Versions (P98305W), enter the program number in Batch Application (data dictionary item PID).
3. Click Find.
4. Choose the desired version.
5. Select Processing Options from the Row exit.
6. Revise the processing options, as necessary.
The system uses the following hierarchy to fetch the correct record:
If the PDF file generated by the Update program was saved, it can be reprinted from Work with Submitted Jobs. If the Payment Register PDF file was not saved, the report which most closely matches the information provided on the check register is the Payment Register (R09313). R09313 is based on data in the Account Ledger table (F0911). Only posted payments appears on the R09313 report. This report does not show the voucher detail that prints on the check register (R04576). The UBE cannot be run separately from Batch Version (BV) and ignores any data selection.
After a payment instrument has been defined in UDC table 00/PY (Payment Instrument) and assigned payment printing programs in Work with Payment Instrument Defaults (P0417), it can be used as the default payment instrument for a supplier. This default is set in the Supplier Master Information (P04012) application.
If a supplier has a default payment instrument, any voucher created for them has the payment instrument automatically assigned. However, this field can be overwritten during voucher entry or changed at a later time using the Speed Status Change (P0411S) application.
Scenario: What causes the error "duplicate not allowed" when adding a new record in Work with Payment Instrument Defaults (P0417)?
Solution: New records added using the Work with Payment Instrument Defaults (P0417) must be uniquely identified by its combination of Payment Instrument (data dictionary item PYIN) and GL Bank Account (data dictionary item ANI). If there is another record with the same Payment Instrument and GL Bank Account, the system triggers a duplicate error and will not create the record.
Answer 1: Each payment instrument can have multiple records in the Work with Payment Instrument Defaults (P0417). However, each record needs to have a different GL bank account associated to it.
Answer 2: This functionality is currently unavailable within the JD Edwards EnterpriseOne software.
Answer 3: EnterpriseOne has several predefined payment types with these special handling codes:
Answer 4: Standard Voucher Entry (P0411) is designed to update all pay items with the same Payment Instrument (data dictionary item PYIN) as the first pay item. Speed Status Change (P0411S) is the only application that allows the Payment Instrument to be updated at the pay item level.
Answer 5: Processing Option 2: Payee Information on the Select tab of the A/P Auto Payments Print Drive (R04572) determines if payee information is printed on the checks. The valid values for this processing option are: