My Oracle Support Banner

EEX 9.2: Escheat Payments Program Abends at Step EX_ESCH_PMT.BEGINRUN.INSAPESC With a Unique Constrain Violation on Record PS_EXAP_ESCH_PMT (Doc ID 2991656.1)

Last updated on JANUARY 09, 2024

Applies to:

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

Symptoms

Running the Expense Processing program, (EX_TRAN_PRCS AE Program), with the Escheat Payments option selected, ends up with an abend at Step EX_ESCH_PMT.BEGINRUN.INSAPESC, where a unique constrain violation is found when trying to insert into Record PS_EXAP_ESCH_PMT.

REPLICATION STEPS:

    1.- Log into the FSCM Online Application as a System Administrator
    2.- Navigate to: Accounts Payable > Payments > Cancel/Void Payments > Escheat Payment
    3.- Perform a search for the desired Bank Set ID, Bank Code, Bank Account, and Payment Method of System Check combination
    4.- Identify a couple of FIN Expenses related Payments to Employees (Expense Reports for instance)
    5.- Open the first one, and select the 'Escheat Check' radio-button, ensuring the Date Escheated gets also populated
    6.- Click on SAVE button
    7.- The system pops up the below Warning Message:
           " Warning -- Treasure or Expense transaction payment is being processed (7015,406)
             This is a Treasure or Expense transaction payment, you will need to go back to Treasure or Expense to manually reverse any accounting entries affected by this process.  Proceed? "
    8.- Click on OK button
    9.- Perform the same Steps 5 through 7 on a second Expenses related Payment
    10.- Navigate to: Travel and Expenses > Process Expenses > Expense Processing
    11.- Create a new Run Control, with the Escheat Payments option selected, which should have a displayed count of 2
    12.- Click on RUN button
    13.- Select the EX_TRAN_PRCS AE Program
    14.- Click on OK button
    15.- Navigate to: PeopleTools > Process Scheduler > Process Monitor
    16.- PROBLEM: Find the Process Instance for the EX_TRAN_PRCS just launched, and confirm that it has gone to No Success, with an Error Message

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 problem.

ERROR MESSAGE:

    " -- 2023-09-28 07:14:05.792 ...(EX_ESCH_PMT.BEGINRUN.INSAPESC) (SQL)

      INSERT INTO PS_EXAP_ESCH_PMT (EX_DOC_ID, LINE_NBR, SEQ_NBR, PROCESS_INSTANCE, EX_PYMNT_TYPE, BANK_SETID, BANK_CD, BANK_ACCT_KEY, EMPLID, PYMNT_ID, PAYCHECK_NBR, PYMNT_STATUS, CANCEL_ACTION, POST_STATUS_AP, CANCEL_DT, BUSINESS_UNIT_GL, EX_PYMNT_DEST) SELECT  DISTINCT ' ', 0, 0, A.PROCESS_INSTANCE, ' ', A.BANK_SETID, A.BANK_CD, A.BANK_ACCT_KEY, A.EMPLID, A.PYMNT_ID, 0, A.PYMNT_STATUS, A.CANCEL_ACTION, A.POST_STATUS_AP, A.CANCEL_DT, A.BUSINESS_UNIT_GL, B.EX_PYMNT_DEST   FROM PS_PAYMENT_TBL A, PS_EX_SHEET_PYMNT B   WHERE A.PROCESS_INSTANCE = XXXXXXXX   AND A.PYMNT_ID = B.PYMNT_ID   AND A.BANK_SETID = B.BANK_SETID   AND A.BANK_CD = B.BANK_CD AND A.BANK_ACCT_KEY = B.BANK_ACCT_KEY AND A.EMPLID = B.EMPLID   AND B.EX_PYMNT_DEST = 'A'

      /

      -- Row(s) affected: 0

      -- 2023-09-28 07:14:06.102 Process XXXXXXXX ABENDED at Step EX_ESCH_PMT.BEGINRUN.INSAPESC (Action SQL) -- RC = 805

      ROLLBACK

      /

      -- 2023-09-28 07:14:06.152 SQL Error: ORA-00001: unique constraint (EMDBO.PS_EXAP_ESCH_PMT) violated "


The abend is preventing the needed Escheat Payment Accounting Entries for those Expenses related Payment transactions that got escheated in FIN payables module. This locks not only those Payments, but also the involved Expense Report and Cash Advance transactions, which cannot be further processed as needed.

The Escheat Payments process, (EX_ESCH_PMT AE Program), should be able to handle all possible Payment transactions marked for escheatment, and properly generate the needed Escheatment Accounting Entries.

 

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.