My Oracle Support Banner

EAP 9.2: Payment Archive Functionality Is Not Considering As Eligible Payment Transactions Coming From Expense Reports Nor Cash Advance In Expenses Module (Doc ID 2696832.1)

Last updated on AUGUST 03, 2020

Applies to:

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

Symptoms

When using the Archiving functionality for Payment transactions, on Record PS_PAYMENT_TBL, none of the Query Names delivered consider as eligible, and hence do not process, any Payment transaction that is related to Expense Reports, or Cash Advances coming from Travel and Expenses module.

    - Query Name AP_ARCHIVE_PYMNT_ALL (Payment Archive - All Banks)
    - Query Name AP_ARCHIVE_PYMNT_BANK_ACCT (Payment Archive by Bank Acct)

The delivered Query Names, which select the eligible Payment transactions, seem to be expecting a Voucher ID linked to all Payments. As such, whenever Expenses related transactions are archived, their related Payments transactions residing in Record PS_PAYMENT_TBL (Owned and supported by Accounts Payable module), are being left orphan, because the archiving functionality of Payments does not consider them for processing.

REPLICATION STEPS:

    1.- Log into the FSCM Online Application as an Expenses User
    2.- Create a new Expense Report transaction, and submit it for approval
    3.- Log into the FSCM Online Application as an Expenses Approver
    4.- Approve the submitted Expense Report
    5.- Log into the FSCM Online Application as an Expenses Administrator
    6.- Launch the Expense Processing program with the options of Post Liabilities, and Stage Payments
    7.- Create a new Pay Cycle, and launch Payment Selection, and Creation
    8.- Launch the Expense Processing program with the options of Post Payments, and Update Staged Payments
    9.- At this stage, query Record PS_PAYMENT_TBL and confirm that the Payment ID and Reference is stored for the Expense Report at hand
    10.- Go to the Archive Data To History Run Control ID, and define the criteria needed:
              a) Archive Template = AP_PYMNT
              b) Process Type = Selection
              c) Selective Query = AP_ARCHIVE_PYMNT_ALL
              d) Define Binds = Select a From Date, To Date, and Process Instance values
    11.- Confirm that the PSARCHIVE AE Program completed successfully
    12.- Query again Record PS_PAYMENT_TBL and confirm that the Payment ID and Reference is still stored for the Expense Report at hand

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

While all Expense Report and Cash Advance transaction data in Expenses module can be archived properly, their respective Payments will be left over in Record PS_PAYMENT_TBL til the end of times, not only affecting performance, but leaving orphan rows in the system.

The delivered Archive Payments functionality, and their delivered Queries, should be considering the Expenses related Payment transactions, not only Voucher related Payments.

 

NOTE: In the images/screenshots/examples mentioned and/or 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.