Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

RPCEDS39 - Syntax errror after Support pack

Former Member
0 Likes
1,267

hi Friends,

Recently we updated support pack last month , due to which we are facing  a  tricky issue for the report RPCEDS39,.

When we try to execute it, its showing syntax error in all the 3 systems , DEV ,QA and prod.

see the attached screenshot.

Can anyone help me in getting this issue resolved.?

regards

Sona.

1 ACCEPTED SOLUTION
Read only

former_member821147
Participant
0 Likes
1,221

Hi,

Yes check the note above mentioned, as i checked it will solve your issue. if it is cannot be implemented in your system then raise message to SAP.

9 REPLIES 9
Read only

Former Member
0 Likes
1,221


Hi,

Refer SAP note: 1864080 , it may  address your issue

Read only

former_member821147
Participant
0 Likes
1,222

Hi,

Yes check the note above mentioned, as i checked it will solve your issue. if it is cannot be implemented in your system then raise message to SAP.

Read only

0 Likes
1,221

hi pradeep,

the above note u mentioned is for the report HMXCEDT0_CE, but in my case the syntax error comes for me in the ZRPCEDTG0 inside that standard  include RPCEDS39.

My support pack is 71 with release 604.

otherwise can i try for this number 659353

Regards

Sona

Read only

0 Likes
1,221

Hi,

means ZRPCEDTG0 is a copy of RPCEDTG0. Check standard report : RPCEDTG0.

If you are not facing any issue with the standard report, then check for the top includes in your zprogram, if any top include is made custom .. now you have to replace copied include with the newer version .

Regards,

Chandra

Read only

0 Likes
1,221

hi chandra,

Thanks for your prompt reply,

but when i checked the note has already been implemented. Kindly See the below screenshot.

Even this note 659353 that i previously mentioned is there already.

What can i do now?

Regards

Sona

Read only

0 Likes
1,221

Hi,

I understood, that is the reason in the second response I said:


Means ZRPCEDTG0 is a copy of RPCEDTG0. Check standard report : RPCEDTG0.


If you are not facing any issue with the standard report, then check for the top includes in your zprogram, if any top include is made custom .. now you have to replace copied include with the newer version .

This is a problem we face during upgrade, RPCEDTG0 completely upgrades into newer version

where as ZRPCEDTG0 partially upgrades into newer version..Hence this kind of syntax error.

So compare both standard and copied, my doubt is on top includes those you have copied in the older version.

Regards,

Chandra

Read only

0 Likes
1,221

Thanks chandra,

My issue got resolved. I copied the correct include from standard report and made neccesary changes to the Zreport.

Now the issue is resolved.

Many Thanks for all experts who helped me crucially.

Regards

Sona

Read only

ThangaPrakash
Active Contributor
0 Likes
1,221

Hello Sonakshi,

Sometimes there might be some dependent object which is inactive and it leads to error.

Check the inactive objects in the system and active them by following the below step.

Goto SE80 ---> In the dropdown select inactive objects --> * in the user name (which gives you all the objects in the system) --> and the click on display. Activate all and check whether you get the syntax error still.

Regards,

Thanga

Read only

nabheetscn
SAP Champion
SAP Champion
0 Likes
1,221

Hi Sonakshi

Since you have upgraded your system and you had a Z copy of standard you must be using some standard includes. Those standard includes got updated and you custom code was using them and SAP standard new report does not need those variables.

For the time being you will have to do it manually. Going forward please check carefully whether we need a Z copy or not. If it is needed then make sure all includes in standard are also copies to Z does not matter whether you want to edit them or not. Seconldy it is always recommended generate a version with the original copy and then making changes in a new version

Nabheet