topic Re: Custom Workbench object not modifiable in Application Development and Automation Discussions

Custom Workbench object not modifiable

Former Member — Mon, 21 Jul 2008 19:30:40 GMT

Hi,

I need your help for a new challange. I have to declare some workbench objects as not modifiable or at least not trasportable.

I listed them in a custom table and now I'm looking for BAdIs, user exit or similar to reach the target.

I'm working on an ECC 6.0 and in SPRO I found something interesting under

SAP NetWeaver => Application Server => SystemAdministration => Change & Transport System => Business Add-Ins...

The "Business Add-In when editing request" sounds really good to make some check while releasing a CR (and the documentation confirms it).

There are four method in BAdI definition :

CHECK_BEFORE_CREATION

CHECK_BEFORE_RELEASE

CHECK_BEFORE_CHANGING_OWNER

CHECK_BEFORE_ADD_OBJECTS

The last one is listed but not explained. No documentation, no implementation.

Does anyone have an idea about how it works or if it works ?

Otherwise is there any suggestions about declaring some workbench objects as not modifiable or at least not trasportable ?

(I'm not talking only of reports or dictionary...)

Thanks in advance,

Gianluca

former_member195698 — Mon, 21 Jul 2008 22:04:24 GMT

What you can do is create a temp implemenation for this method and put a break point?

From the name it seems to be triggered

when you modify some object , popup comes up to specify the Transport and you add that object to the TR.

CHECK_BEFORE_ADD_OBJECTS

Former Member — Tue, 22 Jul 2008 07:22:17 GMT

hi,

I already tried but it seems not to work...

Thanks,

Gianluca

ThomasZloch — Tue, 22 Jul 2008 07:35:31 GMT

I can confirm that CHECK_BEFORE_RELEASE works just fine if you want to prevent transports with certain objects to be released/transported.

You could also move the objects in question to a new package without a transport layer.

Thomas