Any luck implementing CTS_REQUEST_CHECK?

Question

I am trying to implement the BAdI CTS_REQUEST_CHECK in a sandbox system. I have initally implemented all methods just with a BREAK-POINT to see when the methods are called. The implementation is active, but it doesn't seem like the methods are called? Have any of you had any luck trying to implement this BAdI? My goal is to check whenever someone modifies attributes of a shared constant class that this modification ends up in a separate transport request.
Best regards,
Anders

Answer 1

Did you read the documentation of badi in SE18 ?
You can use the business add-in CTS_REQUEST_CHECK to make checks when you are
editing requests.
You can use the following methods:
CHECK_BEFORE_CREATION
This method is called before a request is created and after the creation dialog box. It gives
you the option to:
make your own checkschange the short text and attributes.
CHECK_BEFORE_RELEASE
This method is called before a request is released. It gives you the option to:
make your own checks (for example, on the objects in the request)
change the short text and attributes.
CHECK_BEFORE_CHANGING_OWNER
This method is called before the owner of the request is changed, and after the confirmation
dialog box. It gives you the option to make checks.
Further notes
1. SAP may change request types and task types in future releases. The current request types and
task types are listed in the fixed values of the domain TRFUNCTION.
2. The method CHECK_BEFORE_CREATION is called for all request types, but not for task types.
The two other methods are called for all request and task types.
3. Only Customizing requests and Workbench requests can have attributes. This means that you
do not need to fill the attribute table for other request types, it is simply ignored.
4. If you want to stop one of the methods, you can trigger the exception CANCEL.