New Enhancement Framework

[Former Member]

Hi All.

I have seen and even worked on the new Enh Framework offered from Netweaver 7.0.

I have even gone through the weblogs in SDN.

What I fail to understand, and eventually, convince my boss, is why this shift?

I mean, by giving Enhancement Spots, and Enh. Implementation, what is the adv we get?

They say it is like hooks where we can attach our code.

But earlier also, it was like that.

Only change now is in Implicit enhancement where we don't need any 'Hooks'. can someone please highlight to me how Enhancement spots are so different from earlier exits?

thanks in adv.

[Former Member]

hi

/people/thomas.weiss/blog/2006/01/24/what-the-new-enhancement-framework-is-for-150-its-basic-structure-and-elements-for-beginners

/people/thomas.weiss/blog

reward points if it helps

Regards

Gunjan

[Former Member]

If you read my post again, I said clearly that I have gone through the web logs. I have even worked in this new Framework.

But I am not able to understand why this change. Even in older versions, there was a point where SAP thought customers might need to enhance, and so they called a BADI or customer exit. Now they call an Enhancement. But what advantage to we get by this, except for Implicit enhancements?

[former_member650010]

Hello Kumar,

you are completely right. Even in older version we provide several enhancement possibilities like classic BAdIs, Customer Exits and Appends and, if these exits fits your requirements, its perfect! Unfortunately many customers (and our industry solutions, too) needed changes or adaptations at places where no such exits exists, so they had to modify coding or objects.

The goal was to provide much more enhancement places without a huge effort.

In ERP 2005, we provide some thousands User Exits and BAdIs but maybe millions of source code plugin enhancements possibilities.

So adaptation should be done in the following priority:

1. Customizing

2. Explicit Exits with a well defined Interface: BAdIs, User Exits, CI-Includes

3. Explicit Exits without a well defined Interface: Explicit Source Code PlugIns

4. Implicit Exits: Implicit Source Code Plugins, Functiongroup Enhancements, Class/Interface-Enhancements, Appends

5. Last Resort: Modifications

Note that you are always responsible for your adaptations. e.g. even with BAdIs which has a well defined interface you can do things that harms your system.

Regards

Michael