SCC_SL_SMSET Does Not Respect the 'No Match Found' Parameter. (Doc ID 2553096.1)

Last updated on DECEMBER 14, 2021

Applies to:

Symptoms

VERSIONS:
---------------
Campus Solutions 9.2 PUM 13 and PUM 14.

Campus Solutions 9.0 Bundle #53 and Bundle #54.


ACTUAL BEHAVIOR
---------------
The SCC_SL_SMSET process in PUM 13 does not respect the No Match Found -> Ignore parameter in Transaction Setup, resulting in erroneous creation of new IDs.

EXPECTED BEHAVIOR
-----------------------
The SCC_SL_SMSET process should respect all setup parameters, including the No Match Found parameter.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1. Navigate to Set Up SACR > System Administration > Utilities > Constitutent Transaction Management
2. On the Search/Match Setup tab, set the No Match Found parameter to 'Ignore'
3. Run the Transaction Management process for against staged constituent data that will not match

This results in the erroneous creation of a new EMPLID.

In CS 9.0 this issue only occurs in Bundle #53 and Bundle #54. This issue is not present in earlier version levels of Campus Solutions 9.0.

In CS 9.2 this issue only occurs in PUM 13 and PUM 14. This issue is not present in earlier version levels of Campus Solutions 9.2.

Cause

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