Community
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
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

Force using Pseud Codes instead of Pragmas

Former Member

‎2017 Jun 29 9:36 AM

0 Likes
866

I'm writing tool which has to be backward compatible. Unfortunately the source system has high EhP which causes that all constants declared in classes are commented with Pragmas (##NO_TEXT). Before 7.02 EhP2 such constants were generated with Pseudo Codes ("EC NOTEXT).

This causes errors when moving development to systems with lower EhP.

Is there any way to force SAP to use old Pseudo codes instead Pragmas?

I'm writing tool which has to be backward compatible. Unfortunately the source system has high EhP which causes that all constants declared in classes are commented with Pragmas (##NO_TEXT). Before 7.02 EhP2 such constants were generated with Pseudo Codes ("EC NOTEXT).

This causes errors when moving development to systems with lower EhP.

Is there any way to force SAP to use old Pseudo codes instead Pragmas?

Reply
1 REPLY 1
Read only

matt
Active Contributor

‎2017 Jun 29 1:11 PM

0 Likes
676

What happens if you change the pragmas manually to EC comments? Do they get automatically recreated?