2011 Mar 23 11:59 PM
Hi all,
I'm using a method call within an IF statement, as follow:
IF Z_CLASS=>METHOD( LT_RETURN ) NE 'X'.
...
Which works perfectly fine in Development environment, but is not working in QA, despite the fact the source is the same.
Error throwing in QA environment:Unable to interpret "Z_CLASS=>METHOD(". Possible causes of error. Incorrect spelling or comma error.
Of course the error is well known for all of us... so, am I missing something here? As far as I know, If the code works in Development, the same code should work in QA.
2011 Mar 24 6:50 AM
Hi,
The only explanation that I can think of is that something went wrong during transport to quality system. Check if this class and this method is active in quality and try to execute this method directly in SE24. You can also check transport logs in SE09.
Best regards
Marcin Cholewczuk
2011 Mar 24 6:50 AM
Hi,
The only explanation that I can think of is that something went wrong during transport to quality system. Check if this class and this method is active in quality and try to execute this method directly in SE24. You can also check transport logs in SE09.
Best regards
Marcin Cholewczuk
2011 Mar 24 8:26 AM
As noticed by Marcin, this for sure is transport related. I bet you included your class within different transport than other released objects. Go to SE03 -> Search for objects in Requests/Tasks -> select checkbox R3TR CLASS -> in input field type Z_CLASS -> run . You will see where your object resides. Judging from class name, this is local (non-transportable) object though.
Regards
Marcin
2011 Mar 24 8:35 AM
Hi,
does your development system and QA systems have the same SAP release and support packages?
Regards,
Klaus
2011 Mar 24 8:36 AM
Check if you Development and Quality both are on Netweaver 7.0 or above...
This syntax will not work in earlier Release
Regards,
Mohaiyuddin
2011 Mar 24 10:53 PM
Thank you all for your replies. It's now working fine, but I can't tell you for sure what was the issue.
The only change done since yesterday was the resolution of this dump, related to the ran out of space due to SGEN.
Runtime Errors DBIF_REPO_SQL_ERROR
Short text: SQL error 1654 occurred when accessing program
Cheers!