Last updated on MARCH 09, 2017
Applies to:PeopleSoft Enterprise CS Campus Community - Version 9 and later
Information in this document applies to any platform.
After applying CS Bundle 44, new code exists within SCC_SL_TRANSACTION.INFC.DIVERSETHNIC.ONExecute to check in staging for an NSPEC row and not insert it if a non-NSPEC row is in production. Also see code that looks like it should be removing an NSPEC row in production if a non NSPEC row is inserted through staging. The code seems to only be removing the NSPEC row from the DIVERS_ETHNIC table only and not ETHNICITY_DTL.
Tested both File Parser and AAWS and loaded applications that had only an NSPEC row. Verified through SQL that they NSPEC row was the only row in the ethnicity_dtl table for the applicant.
The NSPEC row gets removed in DIVERS_ETHIC, but stays in ETHNICITY_DTL.
Expect to see both rows removed from DIVERS_ETHNIC and ETHNICITY_DTL.
The issue can be reproduced at will with the following steps:
1. A test using both File Parser and AAWS and loaded applications that had only an NSPEC row. Verified through SQL that their NSPEC row was the only row in the ethnicity_dtl table for the applicant. Then adding another application for the same person with a WHITE ethnicity value and no NSPEC value in the file. For both the FileParser and AAWS processes, the additional WHITE row was added along with the NSPEC row in the ethnicity_dtl table and the NSPEC row was not removed. The NSPEC row was, however, removed in the DIVERS_ETHNIC table for this applicant.
Run the File Parser job by first running the parse job (SCCFP_PARSE) and then the SMP job (SCC_SL_SMP). To test running AAWS, run the SAD_CREATE_APPL operation followed by the SAD_SUBMIT_APPL operation with the transaction set to real-time.
The issue has the following business impact:
Due to this issue, not all rows are removed where NSPEC.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms