This chapter provides overviews of:
Section 2.1, "Overview of Oracle BI Publisher for Automatic Payment Processing"
Section 2.2, "How to Specify Information to Include in the Extract Overview"
Section 2.3, "Overview of Setup to Use BI Publisher for Payment Processing"
The JD Edwards EnterpriseOne software was enhanced to enable you to generate payments in certain payment formats using Oracle's Business Intelligence Publisher (BI Publisher).
The JD Edwards EnterpriseOne Accounts Payable system provide an automatic payment processing process that you use to generate payments. For some payment formats, you can also use BI Publisher to extract the payment data from the JD Edwards EnterpriseOne tables. Some payment formats are supported for both the existing automatic payment process and the BI Publisher extraction of data. Other payment formats are supported for only one method or the other. This document discusses only the payment formats that are supported for BI Publisher.
The process for using BI Publisher to generate payments includes the Payment Information Extractor program(R704001), templates, report definitions, and versions for the payment formats for which you can use the BI Publisher. Each version of the Payment Information Extractor program is set up for a specific payment format. A report definition and template are associated with the version. You set up a payment instrument in the 00/PY UDC table, and associate the payment instrument with a version. The system then uses the associations between the version, report definition, and template to generate the output.
The system launches the Payment Information Extractor program when you set up your automatic payment processing to use the R704001 (P704001) program for automatic payments. When you run the Write function in the Work With Payment Groups program (P04571), the system processes the selected payments and advances the payment status to the Update (UPD) status if no errors occur. If the system encounters errors, the payment status does not advance. After processing payments, the Payment Information Extractor program launches the R704001A program, which writes any error messages to the Work Center and informs you of the location of the output.
This table shows the relationship between the versions, report definitions, and templates for the payment formats for which you can use BI Publisher for payments made from the JD Edwards EnterpriseOne system:
Important!: JD Edwards EnterpriseOne did not create the templates that are used to extract data using the BI Publisher and so cannot modify them. |
The system validates whether the IBAN (International Bank Account Number) and SWIFT (Society for Worldwide Interbank Financial Telecommunication) codes are set up for the company and supplier, if you set the processing options to do so. The program also validates whether the currency code of the payments is equal to the currency code in the processing options. If any validation fails, the system writes an error message to the Work Center and does not advance the payment status to update (UPD).
The SEPA Credit Transfer Initiation payment format (version ZJDE0002 of the Payment Information Extractor program) and the Netherlands Domestic EFT payment format (version ZJDE0005 of the Payment Information Extractor program) have additional validations. Refer to the processing options for these versions for information about the additional validations.
The system uses different versions of the Payment Information Extractor program for each payment format. You set processing options to specify the information to extract, depending on what is required for the format. Excluding unnecessary data from the data extraction improves system performance.
When you set the processing options, you can select to extract this information:
When you select to extract payer information, the system writes data from these tables to the extracted file:
A/P Payment Processing - Summary (F04572)
The system uses the Payment Group Control Number (data item HDC) and Check Control Number (data item CKC) fields to determine the Company (data item CO).
Company Constants (F0010)
The system uses the Address Number (data item AN8) from the F0010 table to access the Address Book Master table (F0101) and Address by Date table (F0116).
Address Book Master (F0101)
Address Number
Tax ID (data item TAX)
Address by Date (F0116)
The system uses the address number and the effective date to determine the address information:
Address (data items ADD1–ADD3)
Postal code (data item ADDZ)
City (data item CTY1)
State (data item ADDS)
Country (data item CTR)
When you select to extract payee information, the system writes data from these tables to the extracted file:
A/P Payment Processing - Summary (F04572)
The system uses the Payment Group Control Number and Check Control Number fields to determine the Payee Address Number (data item PYE).
Address Book Master (F0101)
Address Number
Tax ID (data item TAX)
Address by Date (F0116)
The system uses the address number and the effective date to determine the address information:
Address (data items ADD1–ADD3)
Postal code (data item ADDZ)
City (data item CTY1)
State (data item ADDS)
Country (data item CTR)
When you select to extract bank account information, the system writes data from these tables to the extracted file:
A/P Payment Processing - Summary (F04572)
The system uses the Payment Group Control Number and Check Control Number fields to determine the G/L Bank Account (data item GLBA).
Bank Transit Master (F0030)
Account ID (data item AID)
Transit Number - Bank (data item TNST)
Bank Account Number - Customer (data item CBNK)
Bank Account - Control Digit (data item CHKD)
SWIFT Code (data item SWFT)
International Bank Account Number (data item IBAN)
Address Number - Bank (data item AN8BK)
Address by Date (F0116)
The system uses the bank's address number and the effective date to determine the address information:
Address (data items ADD1–ADD4)
Address
Postal code
City
State
Country
When you select to extract payee bank account information, the system writes data from these tables to the extracted file:
A/P Payment Processing - Summary (F04572)
The system uses the Payment Group Control Number and Check Control Number fields to determine the values to use for these fields:
Bank Account Number - Customer
Bank Account - Control Digit
Transit Number - Bank
Payee Address Number
Bank Transit Master (F0030)
Account ID
Transit Number - Bank
Bank Account Number - Customer
Bank Account - Control Digit
SWIFT Code
International Bank Account Number
Payee Address Number
Address Number
When you select to extract payment information, the system writes data from the A/P Payment Processing - Summary table to the extracted file:
Payment Group Control Number
Check Control Number
Payee Address Number
Payment Amount (data item PAAP)
Date - For G/L - Julian (data item DGJ)
Currency Code - From (data item CRCD)
G/L Bank Account
Address Number
Company
When you select to extract document payment information, the system writes data from these tables to the extracted file:
A/P Payment Processing - Summary
The system uses the Payment Group Control Number and Check Control Number fields to determine the data to extract from the A/P Payment Processing - Detail table (F04573).
A/P Payment Processing - Detail (F04573)
Date -Net Due (DDJ
Payment Amount (PAAP)
Discount Taken (ADSA)
Date - Invoice - Julian (DIVJ)
Supplier Invoice Number (VINV)
The system extracts the ultimate debtor information if:
You specify an address line number in the Ultimate Debtor Addr Line Number processing option for R704001 program, ZJDE0002 version.
You select to extract the ultimate debtor information in the Ultimate Debtor processing option for R704001 program, ZJDE0002 version.
The address of the debtor (company address) is different from the address of the ultimate debtor.
If these conditions are met, the system writes data from these tables to the extracted file:
A/P Payment Processing - Header (F04571), A/P Payment Processing - Summary (F04572), and A/P Payment Processing - Detail (F04573)
Bank Transit Master (F0030)
Address Book Master (F0101)
The system extracts the ultimate creditor information if:
You specify an address line number in the Ultimate Creditor Addr Line Number processing option for R704001 program, ZJDE0002 version.
You select to extract the ultimate creditor information in the Ultimate Creditor processing option for R704001 program, ZJDE0002 version.
The address of the creditor (supplier address) is different from the address of the ultimate creditor.
If these conditions are met, the system writes data from these tables to the extracted file:
A/P Payment Processing - Header (F04571), A/P Payment Processing - Summary (F04572), and A/P Payment Processing - Detail (F04573)
Bank Transit Master (F0030)
Address Book Master (F0101)
Before you use the BI Publisher to produce the payment format output, verify that the necessary UDC tables and values for the Payment Instrument Default program are set up in your system.
You must set up UDC values to process automatic payments. For some formats, you also set up debit information.
You must set up a payment instrument to use for payments that you make using the BI Publisher. Or, you can use an existing payment instrument. After you identify the payment instrument code to use, associate the code to the (R704001) in the Payment Instrument Defaults program (P0417).
You must add the program ID for the Payment Information Extractor program to this UDC table before you can specify the program as the debit statement program for payments in the Payment Instrument Defaults program. As with all payment formats, you enter the program ID with a leading character of P instead of R. For example, to enter the program ID for the Payment Information Extractor program, enter P704001 instead of R704001.
You need to set P704001 as Debit Statement Program if you want to include negative payments in the extraction.
You must add the program ID for the Payment Information Extractor program to this UDC table before you can specify the program as the payment program for in the Payment Instrument Defaults program. As with all payment formats, you enter the program ID with a leading character of P instead of R. For example, to enter the program ID for the Payment Information Extractor program, enter P704001 instead of R704001.
The JD EnterpriseOne system provides hard-coded values for this UDC table. The system uses these values to specify the print templates that use the alignment feature that you set up in the Bank Account Information program (P0030G).
Note: The French Promissory Note format (version ZJDE0003 of the Payment Information Extractor program) uses this UDC table. |
Set up values in this UDC table to create a cross-reference between the currency codes that are required by the payment formats that you use and the currency code values that exist in your system. When you run the Write function in the automatic payment process, the system accesses this UDC table with the transaction currency code to obtain the currency code required by the payment format. For example, if you use the SEPA credit initiation payment format and if the currency code that you use for the euro is EU1, you must set up a cross-reference to the code EUR because the code EUR is required for that format.
If the system does not find a cross-reference in this UDC table, the system uses the payment currency code in the payment format output.
The JD EnterpriseOne system provides hard-coded values for this UDC table. The system uses these values to specify the print templates that produce a draft payment.
Note: The French Promissory Note format (version ZJDE0003 of the Payment Information Extractor program) uses this UDC table. |
The JD EnterpriseOne system provides hard-coded values for this UDC table. The system uses these values to specify the print templates that use the stub feature that you set up in the Bank Account Information program (P0030G).
Note: The French Promissory Note format (version ZJDE0003 of the Payment Information Extractor program) uses this UDC table. If you pay multiple vouchers with one check, you must set the Summarized Pay Item processing option in the Create Payment Control Groups program (R04570) to 1. |
In the Payment Instrument Default program you enter program IDs and versions to specify the payment or debit format to use. As with all payment formats, when you enter a value for the program in the Payment Instrument Defaults program, enter the leading character P instead of R. For example, when you enter the program ID for the Payment Information Extractor program, enter P704001 instead of R704001.
For all payment formats for which you use the BI Publisher, you enter P704001 in the Payments field in the Payment Instrument Defaults program. This table shows the values that you set up for each of the payment formats that you can use with the BI Publisher: