Last updated on MARCH 31, 2017
Applies to:PeopleSoft Enterprise FIN Expenses - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
The PeopleTools User Profile functionality allows both upper case, as well as lower case characters for a User ID (Field OPRID). However, back in the Authorize Expense Users component (Page EX_USR_EE_AUTH), the search allows the configuration by both User ID, or Employee ID. If the User ID radio-button is selected, the Search Value field is going to validate the values entered against the existing PeopleTools User Profile instances defined. An issue though has been detected, as whatever value is being defined at User ID level in the search page, the system will automatically transform that value into all upper case characters.
As the functionality automatically transforms the entered lower case value into an all upper case value, upon performing the search of that value in the User ID records, the system throws an Invalid Value Error Message.
- Log into the FSCM Online Application as User ID VP1
- Navigate to: PeopleTools > Security > User Profiles > User Profiles
- Click on the ADD tab, to create a new entry
- The new User ID value will be lower_case_user (all in lower case)
- Define the remaining fields, such as ID, password, permission lists, etc...
- Navigate to: Travel and Expenses > Manage Expenses Security > Authorize Expense Users
- Select the User ID radio-button
- Click on the look-up icon for Search Value field
- Enter the value of lower_case_user in the User ID field, and click on search
- Confirm that the search displays one result: lower_case_user
- Click on the User ID value found by the search
- Automatically, the system throws an Error Message
To gather more information concerning this scenario and its related problem, refer to the available Replication Steps Word Document here linked containing the complete configuration and the replication steps necessary to reproduce the issue.
" Invalid value -- press the prompt button or hyperlink for a list of valid values (15,11)
The value entered in the field does not match one of the allowable values. You can see the allowable values by pressing the Prompt button or hyperlink. "
The system does not recognize existing User ID values created and stored in lower case characters, and as such, the Authorize Expense Users functionality cannot be used. This prevents Employees from being granted access to their Expense transactions via their current User ID.
The Authorize Expense Users set up page (EX_USR_EE_AUTH) should respect the lower and upper case User ID values.
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