EAP: Financial Sanctions Error - Class Record: Assumed Property SETID Is Not A Valid Field Name (2,274) (Doc ID 2202027.1)

Last updated on AUGUST 11, 2022

Applies to:

Symptoms

Error received running Payment Dispatch with Financial Sanctions turned on

ERROR:
Class Record: assumed property SETID is not a valid field name. (2,274) FS_SDN_SEARCH.SDNSearchEnterprise.OnExecute Name:Validate_Rec PCPC:6996 Statement:120
Called from:FS_SDN_SEARCH.SDNSearchEnterprise.OnExecute Name:Validate Statement:77
Called from:PMT_LOAD.PayeeVal.GBL.default.1900-01-01.Validate.OnExecute Statement:15

Process 42925 ABENDED at Step PMT_LOAD.PayeeVal.Validate (PeopleCode) -- RC = 24 (108,524)
CallAppEngine: Application PMT_LOAD_RT: AppEngine error. (2,653) PMT_LOAD.Payment.PaymentLoadControl.OnExecute Name:CallPaymentLoadAE PCPC:359 Statement:11
Called from:PMT_LOAD.Payment.PaymentHandler.OnExecute Name:ProcessSyncPayment Statement:17
Called from:PMT_LOAD.Interface.PaymentRequestSync.OnExecute Name:Process Statement:7
Called from:AP.Payment.EFTPaymentMsg.OnExecute Name:CallFinGateway Statement:457
Called from:AP_FG_PROC.SENDPMT.GBL.default.1900-01-01.Step01.OnExecute Statement:8

STEPS:
1.  Financial Sanctions turned on through Financial Gateway > Administration > Source Registration > AP > Financial Sanctions Validation box checked
2.  External Bank Account > USBNK > ACH Payment Method > Settle by Financial Gateway > CCD Layout
3.  Add Voucher USA0000002 > ACH Payment Payment Method
4.  Process Payment through Pay Cycle
5.  Click Process button for Financial Gateway Electronic Payments
6.  AP_FG_PROC - No Success

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.