Skip to content

Change to the new editor without use development transactions like SE38, SE37, SE80, etc.

License

Notifications You must be signed in to change notification settings

Devmmanuel/set-new-abap-editor

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

3 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

set-new-abap-editor


Change to the new editor without use development transactions like SE38, SE37, SE80, etc.


Sometimes in SAP Systems the Debugger for some users, can be will see like this

image

There are different transactions where you can change this configuration like the next:

  • SE24
  • SE37
  • SE38
  • SE80
  • Etcetera

But what Happen if you need to do a DEBUG in Productive Ambient, you can have access to the transactions mentioned below

The problem can be resolved with this Program, the Program set the new ABAP Editor for the current user that is executed the program/transaction, the only thing you need to do is create the program in your server and create a transaction for the report then transport to the Productive System, and now when you need to do a DEGUG in PROD ambiente you can configure the new ABAP Editor if you don't have configured for you user


After the execution of this program, the Debugger will be see like this

image




IMPORTANT NOTE

If you want to know more about this project visit mi article about this project in Hashnode

How to Configure the New ABAP Editor Using SAP ABAP Code

About

Change to the new editor without use development transactions like SE38, SE37, SE80, etc.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages