EAP: Financial Sanctions Validation -- Parse Errors were found while performing a search on the Financial Sanctions. (7175,14) (Doc ID 663385.1)

Last updated on APRIL 04, 2025

Applies to:

This document was previously published as Customer Connection Solution 201073295

Symptoms

Running the Financial Sanctions Validation for all SetIDs.  Has around 123,000 Vendors but only has around 23,000 Vendors that need to go through the Validation process.  The Validation process runs to completion but the log has an error.

ERROR
Parse Errors were found while performing a search on the Financial Sanctions. (7175,14).  

This error is occurring 336 times within the log. Unfortunately, the log does not show which Vendors are having a problem.

The only way the Customer can figure out which Vendor is having a problem is to rerun the process with the trace turned on.  If the Customer reruns the Financial Sanctions Validation process with the trace option, -TOOLSTRACEPC 1996, the process will abend at AP_SDN_VAL.MAIN.Step04 (PeopleCode) with the following error:

Cannot convert type Boolean to object type ApiObject. (180,604) FS_SDN_SEARCH.SDNSearchEnterprise.OnExecute  Name:FindSDN  PCPC:10031  Statement:214
Called from:FS_SDN_SEARCH.SDNSearchEnterprise.OnExecute  Name:Validate_Rec  Statement:90
Called from:FS_SDN_SEARCH.SDNSearchEnterprise.OnExecute  Name:Validate  Statement:40
Called from:AP_SDN_VAL.MAIN.GBL.default.1900-01-01.Step04.OnExecute  Statement:15

The AE SQL/PeopleCode Trace showed that the Vendor Name, ABCDE, was having a problem.  Customer reviewed the  Address and found that the issue was with the # sign or having extra spaces around the # sign.  Once the # sign was removed, the process was reran, and the process no longer had a problem with ABCDE.  However, the next Vendor Name that had an issue was XYZ.

Customer is requesting the following:  
1.  The Financial Sanctions Validation lists which Vendors are having parsing issues when the following error is received -- Parse Errors were found while performing a search on the Financial Sanctions. (7175,14).  A PeopleCode trace should not have to be run in order to find out which Vendor/s are having a problem.
2.  The Financial Sanctions Validation process lists what is wrong with the Vendor when the parsing error occurs because when the Customer reviews the Name and Address, to the Customer, everything appears to be fine.  However, the issue might be with extra spaces or a special character that should be valid but is corrupted somehow.

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.