APAR status
Closed as program error.
Error description
ABAP stage Extraction Object (EO) does not allow job parameters for more than one "IN" operator in the "WHERE" clause of the generated "SELECT" SQL statement. A syntax error is generated: 'Statement "PARAM_n" is not defined.'
Local fix
LOCAL FIX: NONE
Problem summary
The ABAP code generator in the ABAP Stage GUI may create erroneous code when using the 'Build Extraction object' generation method. This may happen when the SQL condition contains more than one column with an IN condition. The symptom is an error message "Following error was encountered ... : Statement "PARAM_3" is not defined. Check your spelling." showing when the SQL Condition builder dialog is to be closed. ur .
Problem conclusion
Code fix: Corrected the internal ABAP syntax check logic. After installing the fix the ABAP code checker works correct also when using an IN condition.
Temporary fix
Comments
APAR Information
APAR number
JR49625
Reported component name
IS PACK FOR SAP
Reported component ID
5724Q5500
Reported release
650
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-03-13
Closed date
2014-04-02
Last modified date
2014-04-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
IS PACK FOR SAP
Fixed component ID
5724Q5500
Applicable component levels
R650 PSY
UP
R700 PSY
UP
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCSRJX","label":"DataStage Pack for SAP R\/3"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.5.0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 April 2014