My Oracle Support Banner

EAR 9.2: The Payment Interface AE Program (AR_PAYLOAD) Abends At Step AR_PAYLOAD.PRCS_DTL.UPD_CUST After FSCM 9.2 Image #28 Is Implemented (Defect 27310741) (Doc ID 2428456.1)

Last updated on JUNE 04, 2019

Applies to:

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



After a systems upgrade to PeopleSoft Enterprise FSCM 9.2 Image #28, it has been detected that the Payment Interface AE Program (AR_PAYLOAD) is abending in Error Message when trying to place a NULL value into Record Field PS_PD_IDCUST_TAO4.CUST_ID.

This may seem to be a regression from the codeline changes introduced by <Bug 27310741> (AR 9.2: AR_PAYLOAD IS NOT UPDATING THE CUSTOMER INFORMATION ON PAYMENTS).


      1.- Upgrade the FSCM 9.2 Environment up to Image #28
      2.- Receive a Lockbox file containing Payment information from a Customer, detailing the amounts to be allocated on several specific Items
      3.- Launch the Retrieve Lockbox Files SQR Process (AR25001), to interface the Lockbox electronic payment file into the Deposit EC Staging tables
      4.- Run the Payment Interface AE Program (AR_PAYLOAD)
      5.- Confirm that the process abended in Error Message

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.


    " -- 18:46:28.648 ..(AR_PAYLOAD.PRCS_DTL.UPD_CUST) (SQL)
      UPDATE PS_PD_IDCUST_TAO4 SET cust_id= ( SELECT DISTINCT i.cust_id FROM PS_PD_IDITEM_TAO4 a ,ps_item i WHERE a.deposit_bu=PS_PD_IDCUST_TAO4.deposit_bu AND a.deposit_id=PS_PD_IDCUST_TAO4.deposit_id AND a.deposit_bu=i.business_unit AND a.item=i.item )
      -- Row(s) affected: 0
      -- 18:46:28.968 Process 157290 ABENDED at Step AR_PAYLOAD.PRCS_DTL.UPD_CUST (Action SQL) -- RC = 1407
      -- 18:46:28.996 SQL Error: ORA-01407: cannot update ("EMDBO"."PS_PD_IDCUST_TAO4"."CUST_ID") to NULL "


As the delivered Payment Interface AE Program (AR_PAYLOAD) is abending each and every single time, the electronic Payments and their Regular Deposits cannot be successfully created in the system. This delays further processing outstanding Items through Payment Worksheets.


The Payment Interface AE Program (AR_PAYLOAD) should be able to handle all scenarios of Deposit and Payment information without abending in such manner. 




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

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