EAR 9.2: Payment Interface Process Abends at Step AR_PAYLOAD.SETDEPID.UPDTPYM2 With Error Code 1407 (Cannot Update NULL to PS_PD_PAYMNT_TAO5.DEPOSIT_ID) After Patch 33980129 (Doc ID 3018664.1)

Last updated on JUNE 28, 2024

Applies to:

Symptoms

It has been detected that when multiple instances of the Receivables Payment Interface process, (AR_PAYLOAD AE Program), are running at the same time, the system starts abending at Step AR_PAYLOAD.SETDEPID.UPDTPYM2, stating that it is unable to place a NULL value into Record Group PS_PD_PAYMNT_TAO5.DEPOSIT_ID.

This is taking place right after having implemented the solution from <Bug 33980129>, delivered within PeopleSoft Enterprise FIN 9.2 PUM Image #44. Prior to that, this was not taking place. The below new Steps were introduced, which is causing the problems in the logic:

    - Application Engine Program, Section: AR_PAYLOAD.LBHDR
    - Application Engine Program, Section: AR_PAYLOAD.LOCKDATA
    - Application Engine Program, Section, Step, and SQL: AR_PAYLOAD.LBHDR.UNLK_LB     (D)
    - Application Engine Program, Section, Step, and SQL: AR_PAYLOAD.LBHDR.UNLK_LB     (S)
    - Application Engine Program, Section, Step, and SQL: AR_PAYLOAD.LOCKDATA.LOCKCUS2     (D)
    - Application Engine Program, Section, Step, and SQL: AR_PAYLOAD.LOCKDATA.LOCKCUS2     (S)
    - Application Engine Program, Section, Step, and SQL: AR_PAYLOAD.LOCKDATA.LOCKDEP2     (D)
    - Application Engine Program, Section, Step, and SQL: AR_PAYLOAD.LOCKDATA.LOCKDEP2     (S)
    - Application Engine Program, Section, Step, and SQL: AR_PAYLOAD.LOCKDATA.LOCKITE2     (D)
    - Application Engine Program, Section, Step, and SQL: AR_PAYLOAD.LOCKDATA.LOCKITE2     (S)
    - Application Engine Program, Section, Step, and SQL: AR_PAYLOAD.LOCKDATA.LOCKPAY2     (D)
    - Application Engine Program, Section, Step, and SQL: AR_PAYLOAD.LOCKDATA.LOCKPAY2     (S)

REPLICATION STEPS:

    1.- Have multiple FIN Receivables Users log into the FSCM Online Application in their respective sessions, and perform all the below steps
    2.- Navigate to: Accounts Receivable > Payments > Electronic Payments > Process Payment Interface
    3.- Create a new Run Control ID, with only the Lockbox check-box selected
    4.- Click on the RUN button
    5.- At the Process Scheduler Request pop up window, ensure the AR_PAYLOAD AE Program is selected
    6.- At the exact same time, have all logged Users click on the OK button, in their respective sessions
    7.- Navigate to: PeopleTools > Process Scheduler > Process Monitor
    8.- PROBLEM: Confirm that multiple Process Instances from AR_PAYLOAD AE Program have been running, and at least one of them will end up in No Success with an Error Message, while the others will be marked in Success, but nothing has been processed

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:

Due to this abend, Lockbox Payment transactions are not getting their respective Deposits created in the system, which prevents further processing of outstanding Invoices in FIN Receivables module, to match with Payment Predictor, or manual Payment Worksheet. This delays the closing, or partial pay of Items, along with their missing Accounting Entries to be interfaced to the FIN General Ledger module.

The Receivables Payment Interface process, (AR_PAYLOAD AE Program), should be able to handle all the Lockbox transactions uploaded into the Staging Records, and generate the needed Deposits, and Payments.

Changes

Cause

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