-
Products and Technology
By Category
-
Groups
Activity Groups
Industry Groups
Influence and Feedback Groups
Interest Groups
Location Groups
Customer Only Groups
- Developers
- Partners
- Events
- Help Center
- Topic Pages
-
Explore SAP
Products
Learning and Support
-
- Products and Technology
- Groups
- Developers
- Partners
- Events
- Help Center
- Topic Pages
-
Explore SAP
- Explore SAP
-
Products
- Products
- SAP Business Suite
- Artificial Intelligence
- Business applications
- Data and analytics
- Technology Platform
- Financial Management
- Spend Management
- Supply Chain Management
- Human Capital Management
- Customer Experience
- SAP Business Network
- View products A-Z
- View industries
- Try SAP
- Partners
- Services
- Learning and Support
- About
- SAP Community
- Groups
- Interest Groups
- Application Development and Automation
- Discussions
- BAdI / User-Exit when saving or activating reposit...
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.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results forÂ
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
This group has been set to read-only. Please go to our new Developer forums to publish your content instead.
Read only
BAdI / User-Exit when saving or activating repository object?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2021 Dec 22 10:03 AM
584
- SAP Managed Tags
- ABAP Development
- ABAP Extensibility
Hi everyone,
I am looking for a User-Exit or BAdI that is called when a Data Dictionary Object is saved or activated, preferably filterable by customer name space and / or object type.
I tried with a breakpoint in cl_exithandler get_instance method but the two hits I got are not applicable in my opinion (one had to do with FCODE handling and the other tried to find a CTS project).
I want to create SE61 documentation on the fly in the background when objects are saved / activated hence the requirement. I know that there's ABAPDoc, but on my release only for select objects and a lot of contractors have only access to SE80.
Cheers Christian
0 REPLIES 0
Bluesky