SCC_SL_SMSET Application Engine Program is Creating New ID's for All Duplicate Applicants Loaded from File.
(Doc ID 2490667.1)
Last updated on FEBRUARY 04, 2019
Applies to:PeopleSoft Enterprise CS Recruiting and Admissions - Version 9 to 9.2 [Release 9]
Information in this document applies to any platform.
On : 9 version, Prospect/Admissions Data Load
When running the Application transaction management process delivered in Campus Solutions 9.0 Bundle# 51 / Campus Solutions 9.2 Image 11 i.e. SCC_SL_SMSET , a staged record with exactly the same application information is not identified as a match and a new id is created for all the applicant.
Customer had two application rows for the same person and both rows are automatically marked as “Add New ID” (by the delivered CTM's Run Search/Match feature), it will Post/Create 2 IDs for both the rows, ignoring the fact that it would’ve already created an ID for that person, when it processed the previous row (which means, the second row should’ve been treated, more like an “Update ID” instead but that’s not happening
When multiple identical applicants get loaded from a file, the lower temp ID should have constituent status as "New ID Created" and rest of the identical should be ID updated.
The issue can be reproduced at will with the following steps:
1. Main Menu > Setup SACR > System Administration > File Parser > Run File Parser
2. Select File Mapping ID
3. Run File Parser Process
4. Verify Constituent Staging Data
5. Run Transaction Management Process (SCC_SL_SMSET)
6. Verify Constituent Staging Data
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