EAP 9.1+: Trial Register (APX2030) Not Displaying Remit Bank, Branch, And Account For Single Payment Vendor, As Well As Vendor Bank Related Links Are Disabled At Voucher Level Once Paid (Doc ID 1961256.1)

Last updated on MARCH 18, 2016

Applies to:

PeopleSoft Enterprise FIN Payables - Version 9.1 to 9.2 [Release 9]
Information in this document applies to any platform.

Symptoms

ISSUE:

A couple of problems have been detected around the Single Payment Vendor delivered functionality. First and foremost, when creating a Single Payment Vendor, users cannot define any Banking details given the nature of such new Vendor. Instead, all this relevant information (Vendor Bank Details, Vendor Bank Address, and even EFT Options), have to be manually defined at the Voucher level. This is the only place within the entire FSCM Online Application the data of such specific Vendor is to be stored and viewed.

Once the Single Payment Voucher has been through all the Pay Cycle processing, and a payment has been generated, the same links listed below, to be found at the Single Payment Vendor tab from the affected Voucher, are no longer active:

   - Vendor Bank
   - Vendor Bank Address
   - Transfer to EFT options

This disables the Users from reviewing the Vendor's Bank details if needed, or if an audit requires it.

Additionally, once the Pay Cycle is being processed, at the stage of launching the Trial Register report (APX2030), this one does not contain the Remit Bank, Remit Branch, and Remit Account of the Vendor's Banking details either. This is essential to the report, and is always properly populated when the Voucher payments are related to a Regular Vendor. Again, relevant Banking detail data from the Single Payment Vendor is not available to the users, or auditors in this format either.

REPLICATION STEPS:

   - Log into the FSCM Online Application as User ID VP1
   - Navigate to: Vendors > Vendor Information > Add/Update > Vendor
   - Create a brand new Vendor ID with the following information:
        - Set ID = SHARE
        - Vendor ID = GCS0000001
        - Persistence = Single Payment Vendor
        - Short Name = GCS Single
        - Name = GCS Single Payment Vendor
        - Effective Date = 01/01/1900
        - Effective Status = Active
        - Terms Options = Specify
        - Terms = 00
        - Currency Options = Specify
        - Currency Code = USD
        - Rate Type = CRRNT
        - Payment Method = EFT
        - Handling Options = Specify at This Level
        - Handling = RE
        - Bank Options = Specify
        - Bank = USBNK
        - Account = CHCK
        - Currency Code = USD
        - Rate Type = CRRNT
   - Save all the changes, and ensure the new Vendor is approved if needed
   - Navigate to: Set Up Financials/Supply Chain > Business Unit Related > Payables > Payables Options
   - Open Set ID SHARE, and go to the Voucher Options 1 tab
   - Make sure to define 'Single Payment Vendor ID' = GCS0000001
   - Navigate to: Set Up Financials/Supply Chain > Common Definitions > User Preferences > Define User Preferences
   - Open existing User ID VP1
   - Click on the Procurement link
   - Click on the Payables Online Vouchering link
   - Click on Security for Voucher Styles link
   - Make sure to select the option of 'Allow Single Payment Voucher', and save the changes
   - Navigate to: Set Up Financials/Supply Chain > Business Unit Related > Payables > Payables Options
   - Open the Set ID SHARE, and make sure to place the following values:
        - Method = Electronic Funds Transfer
        - Bank Code = USBNK
        - Bank Account = CHCK
        - Handling = RE
   - Navigate to: Banking > Bank Accounts > External Accounts
   - Open the combination of Bank Set ID SHARE, Bank Code USBNK, and Bank Account CHCK, making sure of the following values:
        - GL Unit = US001
        - Branch = NEWYORK
        - Currency Code = USD
        - Payment Method = Electronic Funds Transfer
        - Form ID = EFT1
        - Settle By = Pay Cycle
        - Layout = UFF
   - Navigate to: Accounts Payable > Payments > Pay Cycle Processing > Payment Selection Criteria
   - Add a new Pay Cycle ID AP_GCS, and set up the following:
        - At the Source tab define a Source = VCHR, and Business Unit = US001
        - At the Bank/Method, set Bank Set ID SHARE, Bank Code USBNK, Bank Account CHCK, and Payment Method 'Electronic Funds Transfer'
   - Navigate to: Accounts Payable > Vouchers > Add/Update > Regular Entry
   - Create a new Voucher with the following information:
        - Business Unit = US001
        - Voucher ID = NEXT
        - Voucher Style = Single Payment Voucher
        - Vendor ID = GCS0000001
        - Invoice Date = 01/10/2014
        - Gross Invoice Amount = 1000
        - Tax Exempt Flag = Y
        - Pay Terms = 00
        - Account = 610000
   - At the Payments tab, click on 'Schedule Payments' button
   - At the Single Payment Vendor tab:
        - Fill in all the necessary Vendor Address Information fields
        - Click on the Vendor Bank link
        - Fill in all the relevant Vendor Bank information (including Bank Name, Branch Name, and Bank Account data)
        - Click OK
        - Click on the Vendor Bank Address link
        - Fill in all the needed information on the required fields
   - Save the created Voucher, and proceed to approve it if approvals are required
   - Navigate to: Accounts Payable > Batch Processes > Vouchers > Voucher Posting
   - Create a new Run Control ID GCS with the below values:
        - Request ID = VCHR_POST
        - Process Frequency = Always Process
        - Post Voucher Option = Post Voucher
        - Business Unit = US001
        - Voucher ID = (Transaction Number of the Voucher created)
   - Launch the process to completion
   - Navigate to: Accounts Payable > Payments > Pay Cycle Processing > Pay Cycle Manager
   - Open existing Pay Cycle ID AP_GCS
   - Run Payment Selection, making sure the Voucher ID has been properly selected
   - Run Payment Creation
   - Click on the Trial Register link
   - On the new page for Trial Register, add a new Run Control ID
   - Define the Pay Cycle ID AP_GCS, and run the process by selecting APX2030 process
   - ISSUE #1: On the resulting Trial Register PDF file (APX2030), confirm that the Vendor's Remit Bank, Remit Branch, and Remit Account are nowhere displayed in the report
   - Navigate to: Accounts Payable > Payments > Pay Cycle Processing > Pay Cycle Manager
   - Open again Pay Cycle ID AP_GCS
   - Perform all needed tasks to ensure that the Pay Cycle is set into Completed status
   - Navigate to: Accounts Payable > Vouchers > Add/Update > Regular Entry
   - Open the Voucher ID created for the Single Payment Vendor
   - Go to the 'Single Payment Vendor' tab
   - ISSUE #2: The links for 'Vendor Bank', 'Vendor Bank Address', and 'Transfer to EFT Options' are disabled

To gather more information concerning this scenario and its related problem, refer to the available Replication Steps Word Document here linked containing the complete configuration and the replication steps necessary to reproduce the issue.

BUSINESS IMPACT:

Once the Single Payment Vendor related Voucher has been paid via Pay Cycle, the Vendor's Bank Account information can no longer be reviewed neither online via the 'Single Payment Vendor' tab at the Voucher level, nor in the Trial Register report (APX2030). There is no way to double check such information if there are any doubts on the data entered. As such, users are powerless in confirming the transaction.

EXPECTED BEHAVIOR:

First and foremost, for audit purposes, the Vendor related links at the 'Single Payment Vendor' tab at the Voucher level should always be available regardless of the Voucher being paid or not. This data should always be viewable for tracking purposes, in case such Vendor needs to be inspected, or double-checked. Secondly, the Trial Register Report (APX2030) should always contain the Vendor's Remit Bank, Branch, and Account information, regardless if the Vendor has been defined as a Regular Vendor, or a Single Payment Vendor. The Vendor's Account information is relevant, and a big reason why this report is being used.
 

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