AP:URL String Is Not Properly Encoded When Attempting To Display The Payment Inq For A Vchr.

(Doc ID 2344705.1)

Last updated on JANUARY 02, 2018

Applies to:

PeopleSoft Enterprise FIN Payables - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

 

ISSUE:
 
The URL string is not properly encoded when attempting to display the Payment Inquiry for a voucher.



The VCHR_EXPRESS component allows the user to access the Payment Inquiry page and display payments for the voucher. New York Property uses M&T bank for payments. The Bank Code is “M&T”

When attempting the inquiry from the Summary tab by selecting Payment Inquiry and pressing GO, the URL is not encoded and the ampersand in “M&T” is considered to be a delimiter, so the Payment Inquiry search page is only populated with “M”.

When transferring from the Payments tab by clicking the Payment Inquiry link, the URL is properly encoded and the Bank Code of “M&T” is properly passed to the Payment Inquiry search page. The Bank Code field is properly populated with “M&T”.

Corrective Action Required: PeopleCode VCHR_PANELS_WK3.GO_PB FieldChange performs the inquiry from the Summary tab. The URL needs to be encoded before the ViewContentURL(&sURL) instruction is invoked (second to last line of code);
 

STEPS:
 
1. Configure a Bank Code that contains an ampersand “&”
2. Pay a voucher from that bank.
3. Access the VCHR_EXPRESS component and search for the voucher
4. Click on the Summary tab
5. In the View Related field, select Payment Inquiry then press the GO Button.

Notice that the bank code only contains the character(s) up until the ampersand and the remaining characters are dropped. The ampersand is being considered as a variable delimiter and not part of the data.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms