Overview of User Define Codes Within EnterpriseOne Accounts Payable Setup (P0004A)

Many programs in the JD Edwards EnterpriseOne Accounts Payable system use UDCs to process information. Most of the UDCs for the JD Edwards EnterpriseOne Accounts Payable system are shipped with predefined data. You can change or delete the predefined data if it is not hard-coded, and can add UDCs to suit your own needs. You should not change the product code, code type, or description name for the UDCs in the JD Edwards EnterpriseOne Accounts Payable system.

Note: Country-specific UDCs for accounts payable transactions exist for many countries.

UDC	UDC Description
00/DV - Voucher Document Type	Original such as a voucher can exist by itself (i.e. it does not need to be associated with another document type). Valid values are: PV (voucher): The default value for the Voucher Original Document Type is setup in the Voucher Master Business Function P0400047. The system creates a voucher with this code when you enter a supplier's invoice during voucher entry. This document type is soft-coded. PR (recurring voucher): The system creates a voucher with this code when the voucher requires a specific number of payments at specified intervals. The system is hard coded to use the default Document Type PR, but can also be manually populated with another valued when entering the recurring voucher. See FAQ Frequently Asked Questions for Original Document Types for further details. PD (debit memo): The default value for the Debit Memo Original Document Type is setup in the Voucher Master Business Function P0400047. The system creates a debit memo with this code when you enter a credit to the supplier. This document type is soft-coded. PL (logged voucher): The default value for the Logged Voucher Original Document Type is setup in the Voucher Master Business Function P0400047. The system creates a voucher with this code when you enter a logged voucher. This document type is soft-coded.
00/DT - Matching Document Type Codes	Matching documents are always linked to an original document and cannot exist by itself. All Matching Document Types are hard coded. Valid values are: PE (Change in Voucher Amount): The PE document type is linked to a Voucher Document Type and is created when a posted voucher is voided or when the amount of a posted voucher is changed. The original voucher and the PE record will share the same document number. PK (Automatic Payment): The system will create a PK Document when a voucher is paid through the Automatic Payment Process. The document number will default from the GL Bank Account Setup P0030G. PT (Electronic Funds Transfer): The system will create a PT Document when a voucher is paid using the Electronic Funds Transfer process. The document number will default from the Next Number setup P0002 for system 04. PB (BACS Electronic Funds Transfer): The system will create a PB Document when a voucher is paid using the BACS Electronic Funds Transfer process (UK Localization). The document number will default from the Next Number setup P0002 for system 04. PO (void payment): The PO document type is linked to a Payment Document Type and is created when Payment is voided. The original payment and the PO record will share the same document number. PM (Manual Voucher): A PM document type is created when you enter a Manual Payment without Voucher Match. Unlike other Voucher Document Types, the PM document type is hard coded because it is created at the same time as its payment and resides in the same W-type batch. This document cannot exist without its associated Payment (PN). PN (manual payment): The system creates a payment record with this code when you use the manual payment process to pay a voucher.
00/PS - Payment Status Codes	The Payment Status Code is assigned to a voucher in the Accounts Payable Ledger table F0411 to indicate its payment position. Valid values are: A: Approved for payment. H: Hold pending approval (not hard-coded). You can set up additional codes for each type of hold status for vouchers. P: Paid in full. R: Retainage. %: Withholding tax applies. #: Payment in process. The system marks any vouchers that you select during prepayment processing with a # to prevent any changes to the voucher until payment processing is complete. Z: Voucher was selected during the manual payment process. This status appears for a voucher when you have selected the voucher to be paid by a manual payment but have not yet clicked OK on the Manual Payment Entry form.
00/PY - Payment Instrument Codes	Payment instrument codes indicate various methods of payment, such as draft, check, and electronic funds transfer. You assign a payment instrument code to each voucher. Set up a code for each type of payment instrument that you use. Blank is the default value. The system provides these hard-coded payment instrument codes: X: Electronic data interchange (EDI) check. Y: EDI wire. Z: EDI. The system provides these payment instrument codes that are not hard-coded: C: Check (8.75 inches). D: Draft. N: Print Checks - Brazil. T: Electronic funds transfer (EFT). W: Check (8.5 inches).
00/HC - Special Handling Code - AP Pymt	You assign special handling codes for various types of special handling instructions, such as remittance attachment. Special handling codes are not hard-coded. Set up a code for each type of special handling instructions that you use. Examples of special handling codes include: Remittance attachment. Application form attachment. Return payment to tax department.
00/BT - Bank Type Codes	You define bank type codes (00/BT) for setting up multiple bank accounts for suppliers. When you define codes for bank types, you can use any code except those that are hard-coded in the system, such as types V, C, D, P, G, M, and B. When you assign a bank type code to a supplier, a record is created for that supplier in the Multiple Vendor Bank Account Status table (F0401M) with the default Pre-Note Status of P to indicate that the supplier has more than one bank account to make payments.
04/TR and 01/07 - 1099 Processing Codes	The JD Edwards EnterpriseOne Accounts Payable system uses UDCs to select vouchers for IRS Form 1099 processing. These UDCs specify which IRS 1099 form and which box on the form a voucher applies to. The UDC tables in the JD Edwards EnterpriseOne Accounts Payable system for 1099 processing are: Type of Return (04/TR) 1099 Reporting Code (01/07)
04/RC - Replace Character	If the text file that you transfer contains letters or special characters that are not recognized by the bank, you can set up replacement characters in UDC 04/RC. Unlike most UDC codes, the system does not use the code that you specify in this UDC; it uses the first character from the Description 1 field and replaces it with the first character in the Description 2 field. For example, you could replace the letter Z with the number 0. If you leave the Description 2 field blank or accidentally enter the value in the second space of the field, the system replaces the character that you specified in the Description 1 field with blank. The system uses this table only if the appropriate processing option is enabled in program P0457D. The system scans the text file for the characters that are specified in the Description 1 field in UDC 04/RC. It then replaces those characters with the alternate characters that you specify in the Description 2 field. Thus, the system deletes the unacceptable characters from the text file and replaces them with acceptable characters. Note. The system replaces a single character with multiple characters only for the German programs German Bank File Format and Statement Diskette, and Create A/P Bank Diskette - Germany. When you use the Replaced Character UDC for other programs, the system replaces the character that is identified in the Description 1 field with only the first character in the Description 2 field. You can specify that the system replace a single character with one alternate character or with multiple alternate characters. When you specify multiple alternate characters, the length of the string does not change; if the original string is three characters, the modified string is three characters. The system drops certain characters from the string if inserting all of the alternate characters would result in the modified string exceeding the allowed length of the string.
04/SC - Special Character	If the text file that you transfer contains letters or special characters that are not recognized by the bank, you can add them to UDC 04/SC and replace them with the value that is specified in the processing option for the Copy Bank File to Diskette program (P0457D). Unlike most UDC codes, the system does not use the code that you specify in this UDC; it uses the characters that you define in the Description 1 field. You can specify up to 30 characters in the Description 1 field, and if you need more, you can add another code and specify additional characters in the Description 1 field for that code. The system replaces all values in the Description 1 field for all codes with the value in the processing option. For example, if you enter !@#$% in the Description 1 field and enter / in the value of the corresponding processing option, the system replaces every instance of !, @, #, $, and % in the text file with /. Note. To replace characters with blank, leave the processing option for Replacement Character blank. If you do not want to use replacement characters, do not set up any codes in UDC 04/SC.

Common User Define Code Questions

Question 1: Is it necessary to have blank as a valid payment instrument in UDC table 00/PY?

Answer 1: Blank value is hard-coded value in UDC table 00/PY and used as the default payment Instrument for the suppliers those who don't have a valid payment instrument. Several applications will validate the existence of blank in the UDC table; if the blank is not found, a hard error will be triggered.

Question 2: Why is it not recommended to use the Sheffer Stroke or Pipe Symbol (|) as a payment instrument UDC table 00/PY?

Answer 2: While in theory, there is no problem using this character as a payment instrument, the problem is that the (|)symbol is the separator
character for Processing Option values. Therefore, the value is not retained in the processing options and is considered an invalid character to use as a Processing Option value.

Question 3: Does using the exclamation mark symbol ! cause problems when used as a payment instrument value in UDC table 00/PY?

Answer 3: The exclamation mark symbol ! is a defined SQL symbol. For example, the command != is interpreted as not equal to. Hence using the exclamation mark as payment instrument may cause incorrect results when doing a QBE query. The same is true for some other symbols: like % - percentage is used as a wild card.