topic Re: BADI Namespace in Application Development and Automation Discussions

BADI Namespace

Former Member — Mon, 11 Jun 2007 22:32:16 GMT

Hi,

I'm having problems using a particular BADI that is included as part of the SAP demo for mobile applications. Apparently this BADI is part of a development project that got added as part of the standard implementation. Others have come across the same problem and have suggested to enhance the namespace in order to deactivate the BADI (). So please any links or how to steps will be greatly appreciated.

Thanks,

Miguel

Re: BADI Namespace

Former Member — Tue, 12 Jun 2007 04:58:13 GMT

Hi,

You can define an your own name space by trx SE03

Development in Namespaces

Note the following points when you develop in reserved namespaces:

System change option

To be able to change objects in namespaces you must set the system change option of your system to modifiable.

Packages

Objects in your namespace must be assigned to a package that begins with the namespace ID. Before you begin development work, create packages with namespace prefixes for your projects.

You can also assign local objects and test objects in your namespace to local ($) and test (T) packages. Later on you can reassign them to one of the transportable packages in your namespace, if necessary.

Objects

You assign objects to a namespace by placing the reserved namespace ID in front of each object name as a prefix.

For more information, see SAP Note 104010 in SAPNet - R/3 Frontend.

name space is there to differentiate between SAP standard ones and the ones developed by us.

'Z' and 'Y' are the name spaces allocates for objects created by us.

where as A TO X for SAP STANDARD.

for lock objects alone name space gain differs,

'EZ' / 'EY' for us

SAP has reserved name ranges for customer objects and SAP objects. Use these customer name

ranges to make sure that your objects are not overwritten by SAP objects during the import of

corrections or an upgrade.

Only use the customer name ranges. If you do not keep to the name ranges for customer objects you

may lose your development objects.

SAP delivers a few system objects with names that fall within the customer name range. These objects

already existed when the customer name range was extended from YY/ZZ to Y/Z.

These objects are listed in table TDKZ.

You can reserve and use exclusive namespaces based on the SAP standard for central group

development or for the development of your own products (see Development in Reserved Namespaces

In KW (= SAP Knowledge Warehouse) I found good information in the following three topics (use Search in the top menu bar to get to the right webpages):

"Setting Up a Namespace for Development"

"Development in Reserved Namespaces"

"Namespace Information System"

Regards

Re: BADI Namespace

Former Member — Tue, 12 Jun 2007 20:47:50 GMT

Hi,

Thanks for your tips. Im not really sure if Im asking the correct question. This is what I have done until now. Under transaction se19 I was able to copy and fix the SAP Standard BAdi implementation. My own implementation is under my local namespace. The problem is that the BAdi still uses the standard implementation that contains code error (missing an included class). The real answer Im looking for is how to deactive the BAdi implementation when I dont have permission to access the namespace (choosing change on se19 returns a no licence error).

Thanks again,

Miguel

Re: BADI Namespace

Former Member — Wed, 13 Jun 2007 00:01:19 GMT

Hi Miguel,

Instead of selecting change button have you tried Enhancement Implementation -> Deactivate.

Reward points if useful.

Regards,

Atish

Re: BADI Namespace

Former Member — Wed, 13 Jun 2007 14:38:13 GMT

Yes, we also recieve the error regarding the license.

Thanks,

Miguel

Re: BADI Namespace

Former Member — Tue, 19 Jun 2007 19:01:10 GMT

There was a mistake in the installation package that prevented the namespace objects from been deactivated.

Thanks,

Miguel