My Oracle Support Banner

EEX: Step EX_STAGE_PMT.PAYMENTS.VNDPMT2 Sets BANK_SETID Field Value With Wrong SetID If Re-Stage Payments Is Run For Vendor Expenses (Doc ID 2617988.1)

Last updated on DECEMBER 05, 2019

Applies to:

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

Symptoms

The functional team has detected that the Stage Payments process (EX_STAGE_PMT AE Program) is incorrectly populating BANK_SETID Field on Records PS_EX_SHEET_PYMNT and PS_EX_SUMM_PYMNT for Expense Reports that contain Vendor Payment expense lines, and that have been previously unstaged.

When the Stage Payments program is run the first time, it properly populates the Bank Set ID field on both Records, then after a subsequent Unstage Payments, the second run to Stage Payments uses the Step EX_STAGE_PMT.PAYMENTS.VNDPMT2, which contains the wrong coding, to set the Bank Set ID value:

    BANK_SETID = B.VENDOR_SETID     (Being PS_EXVNDPMT_TAO4 B)

It equals the Bank Set ID for the Supplier Set ID, which is incorrect. If the Supplier ID is defined under a Set ID that differs from the Set ID defined under the Bank Account being used, then this problem happens.

Additionally, this problem happens when at the Supplier configuration level, the Additional Payables Options section has the Bank Options set to 'Specify', and Bank Code, and Bank Account are populated. If left to 'Default from Higher Level', this problem does not take place, as Step EX_STAGE_PMT.PAYMENTS.VNDPMT2 is not being used.

REPLICATION STEPS:

    1.- Define a new Supplier ID under Set ID SHR03, and at the Additional Payables Options section define a Bank Code, and Bank Account value
    2.- Define a Bank Account under Set ID SHARE
    3.- Define at the Expenses Options level, for Set ID US001, the Bank Code and Bank Account details using Set ID SHARE
    4.- Define a new Payment Type linked to the Supplier ID under Set ID SHR03
    5.- Define a Corporate Card Supplier, and link it to the same Supplier ID under Set ID SHR03
    6.- Create a new Expense Report with at least one Expense Line using the Payment Type of  that Supplier
    7.- Submit the Expense Report for approval
    8.- Approve the Expense Report for payment
    9.- Launch the Stage Payments, and Post Liabilities processes against the Expense Report
    10.- Query Records PS_EX_SHEET_PYMNT, and PS_EX_SUMM_PYMNT for the Expense Report transaction, and confirm that Field BANK_SETID is storing the correct value coming from Expenses Options set up (Set ID is SHARE)
    11.- Launch the Unstage Payments process
    12.- Confirm that the Expense Report has reverted to a status of APY, and both Records PS_EX_SHEET_PYMNT, and PS_EX_SUMM_PYMNT are empty
    13.- Launch the Stage Payments process against the Expense Report
    14.- Query Records PS_EX_SHEET_PYMNT, and PS_EX_SUMM_PYMNT for the Expense Report transaction, and confirm that Field BANK_SETID is now storing the value of SHARE, which is incorrect (Set ID is SHR03)

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.

No Bank Account is defined under that incorrect Bank Set ID, and as such, Pay Cycle cannot pick up the Expense Report for payment. At this stage, the Expense Report cannot be corrected at the Update Staged Payments under Vendor Payments page, because Bank Set ID is not an editable field. No matter how many times the Expense Report is later un-staged, to be staged once again, because from now on, Step EX_STAGE_PMT.PAYMENTS.VNDPMT2 is being used, applying the wrong codeline over and over again. The only way to fix this is to close the Expense Report, and create a brand new one from scratch. This generates a lot of unnecessary manual steps for Employees, and could greatly delay the payment to Credit Card Suppliers, which could cause late payment fees to be incurred.

The Stage Payments process (EX_STAGE_PMT AE Program) should always be consistent, and populate the BANK_SETID Field from Records PS_EX_SHEET_PYMNT, and PS_EX_SUMM_PYMNT, taking the value correct value whether that is Expenses Options, or Supplier set up.

NOTE: In the attached document, user details / company name / address / email / telephone number represent a fictitious sample (based upon made up data used in the Oracle Demo Vision instance). Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.