Assignment of Enhancement[SMOD] to a Project [CMOD].

[Former Member]

Hi,

I have changed a FM in a enhancement, in the development system, and activated the FM it worked perfectly fine in the Development Environment. But when it moved to the Integration system eventhough the code in the FM is seen it was not executed.

Later, i came to know that the enhancement is to be assigned to a Z ot Y project in CMOD. First deactivate the project, assign the enhancement and again activate the project. Then transport this project also to the Integration system.

My doubt is what for all this is done. Is it not enough activating the FM of a particular Enhancement.

One more doubt: Is there any difference between user-exit and customer-exit.

Thanks in advance for your valuable replies.

Regards,

Raghavendra Goutham P.

[Former Member]

Hi Raghav

Both user exit and customer exit are same.

the thing z->y is because the BASIS people would have configured Y program in the integration system.

regards

kishore

[Former Member]

Hi,

<b>Customer Exit:</b>If you need to use a processing type other than manual entry / default value, replacement path, SAP exit, or authorization, then a customer exit gives you the option of setting up a processing type for variables, tailor-made to your specific needs.

The customer exit is designed as an enhancement that you can configure with customer-specific logic.

<b>User Exits:</b>

Making modification without changing SAP standard code or logic.

[vinod_gunaware2]

Hi

Goto CMOD create new project then assign component

and activate project.

If it already attached then just activate.

Tranport to particular system

regards

vinod

[Former Member]

Hi,

Activating the FM is not enough.

If you have a look at Enhancement Project in CMOD,

you will see that there are number of other components involved in it, like Function modules, customer screens, etc. Also, one cnhancement can be assigned to exactly one project.

SAP accesses your FM thru this enhancement project only. i.e. this project in turn call your FM and hence you need to activate and transport the project also.

User exit is a part of customer exits. The other components of customer exits can be screen exits, menu exits, field exits, etc.

Hope this helps...

Regards

Shashank

[Former Member]

Hi raghavendra,

1. My doubt is what for all this is done. Is it not enough activating the FM of a particular Enhancement.

a) There is a good reason why SAP has does like this.

Suppose a customer has written code in the FM(user-exit).

After some time it does not want that functionality,

then instead of REMOVING all lines of code in the FM,

the customer can just DEACTIVATE the project/exit.

b) more than one enhancement can be combined

in one project.

The reason is that to develop some requirement,

more than one enhancement/exit may be requried,

all at the same time.

TO BUNCH all these in same group, project concept

came into picture.

c) another reason is,

the system firsts check wheteher the enhancement

is active or not.

If its not, then there is no necessity

to call the FM AGAIN & AGAIN whenver

user-exits get fired.

Hence, it is more efficient.

Not all customers use all user-exits.

2. Is there any difference between user-exit and customer-exit

Practically no difference.

User-exits were previously used as

a FORM/PERFORM which were empty initially.

The customer had to write his own code

in this forms and these forms were called from

sap transactions.

these forms were called everytime.

Then came the concept of customer-exits

which is implemented using FUNCTION MODULES

(and not form/perform)

and activation concpet also came into picture.

regards,

amit m.