File Parser Sub Parse Field in File Mapping Not Trimming Blank Spaces from the File Value
(Doc ID 2530784.1)
Last updated on JANUARY 01, 2020
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, External Data Loads
When using the 'Sub Parse Field' for parsing the Ethnicity values (comma separated values) from Common App, Sub Parse does not trim the spaces which are between the comma separated values.
Example: Black, White. In this situation, there is a space in between the comma and White. After running the File Parser, the process - SCCFP_PARSE ignores the 'White' from the file.
It should create two rows: 1) for Black and 2) for White
The issue can be reproduced at will with the following steps:
1. Create a File Mapping for a record and use the 'Sub Parse Field'. Navigation: Main Menu > Set Up SACR > System Administration > Utilities > File Parser > File Mapping Definition
2. The Sub Parse field should be comma separated with a space in between the fields. Eg: Black, White
3. Run the File Parser using a file which has this comma separated values. Navigation: Main Menu > Set Up SACR > System Administration > Utilities > File Parser > Run File Parser (In the run control definition, choose the file mapping definition in which you used the 'Sub Parse Field' and in the File Path give the folder from where the process should pick up the input file)
4. Once the SCC_PARSE process goes to success, notice that the sub parse field has introduced an unnecessary row with a blank space for the sub parsed field.
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