E-DMW: "INSERT DATA SET CONTENT" PAGE ISSUES

(Doc ID 2245162.1)

Last updated on JULY 17, 2017

Applies to:

PeopleSoft Enterprise PT PeopleTools - Version 8.55 and later
Information in this document applies to any platform.

Symptoms

PROBLEM STATEMENT:
-----------------------------------
When using the search functionality within the “Insert Data Set Content” page there were found multiple issues from
- Fatal PeopleCode SQL error
- Incorrect retrieved error message.

ERRORS:
-----------------------
1) Message
   " A fatal PeopleCode error occurred. Please consult your system log for details. "

  Message
  " The Bind expression(s) entered have produced an invalid SQL expression. Please correct and retry. (257,229)
    The combination of search operations and values entered produces an invalid SQL expression. Please review the invalid SQL text to determine the issue and correct it before retrying. "

  Analysis (from log file):
  " PSAPPSRV.17076 (8877) 1-208006 07.57.00 748124.570655 SQL error. Function: SQLExec^M
    Error Position: 69^M
    Return: 907 - ORA-00907: missing right parenthesis ^M
    Statement: select count(*) from ps_setid_tbl a where upper(a.setid) in upper((:1, :2))^M
    Original Statement: Select count(*) FROM %Table(SETID_TBL) A WHERE %upper(A.SETID) IN %upper((:1, :2)) "

2) Message
    " Invalid value CZE01% (25,297)
      The value specified does not meet the requirements of the data type or length for this field. Please enter a valid value to continue "


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Log in to PIA
2. Create a DataSet for example for SetID
3. Use ADS in Data Migration Workbench
4. Insert Data Set Content
  Use Advanced search (IN) and ensure Case Sensitive Flag is “Deselected”
5. Hit Search
6. The first reported issue occurs
  ( If the Case Sensitive Flag is selected it works fine )

7. Use the same ADS as used above and go to the Insert Data Set Content page
8. Enter as SetID the total value of SETID E.g. CZE01
9. Hit Search
10. The second reported issue occurs
  ( If instead of CZE01, CZE0 is used then it works fine.
  The system should also be able to handle the value CZE01 when using begins with )
  

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms