Customer exits

[Former Member]

Hi Experts

What is meant by customer exit, can we say the exits which are available in SMOD is customer exits.

Can we do screen changes in customer exit only, can't we do screen changes in user exit.

Pls explain me clearly.

Thanks in advance

Regards

rajaram

[Former Member]

customer exit is a type of user exit. A user exit is a handle that SAP put into their code, allowing a customer to add their own routines. There are many types of user exit, and often they differ between modules, so I can't give a step by step guide to finding them.

rgds

rajesh

[former_member404244]

Hi,

yes u r ryt...Customer exit is SMOD ....we can also do screen exits for userexits..The example for this is

goto->VA02->goto menubar ->ITEM ->ADDITIONAL DATA A and ADDITIONAL DATA B...in these two screens u can add the custom fields....but it requires an access key..

Regards,

Nagaraj

[Former Member]

thats what nagaraj

how can we know all the user exits like that.

i also know that one, can u tell me other one, or how to fine the exits like that.

Regards

Rajaram

[former_member404244]

Hi,

Userexits start with userexit_*..... for a program say SAPMV45A,goto SE80 and then in the subroutines tab u will find....These user exits are available maximum in SD module only....as per the requirement u have to see whther any userexit or customer exit is available for screens...

Regards,

Nagaraj

[Former Member]

But for Additional data A and B, there is no exit start with userexit_,

so whats that actually.

pls explain me.

Regards

Rajaram

[former_member404244]

Hi,

Additonal data A and additional data B are for screen exits....they won't start with userexit_*....u can only put your custom fields there and u will use append sturucture method and add fields to VBAP....then u will populate them either by BDC or Custom IDOC/BAPI..

But the userexits where u can directly write ur code will only start with userexit_*...Here u can write ur code by getting the access key.....

Regards,

Nagaraj

[Former Member]

k thank u yar am clear now abt it.

finally i want to confirm onething that

the exits which are available in smod all are called customer exit, is it so?

REgards

rajaram

[former_member404244]

HI,

yes you are right.... customer exits is for SMOD...

Regards,

Nagaraj

[Former Member]

i dont understand that, populate them by bdc,idoc/bapi.

why and what we populate here, pls explain me yar.

[former_member404244]

Hi,

as u are adding ur custome fields in the standard screen...For populating the values into those fields u have to use either BDC or custom bapi/idoc....why i used custom is the standard bapi or idoc won't have your custom fields...hence inorder to populate either u have to extend stanard bapi or create a new custom idoc to update the values..

I hope u got the point..

Regards,

Nagaraj

[Former Member]

I got ur point nagaraj, thank u very much

but in our company they used the following codes only to populate data. i think they have not used any bdc/bapi.

can u tell me how they could do this pls.

MODULE FILL_TABLE_8459 INPUT.

DESCRIBE TABLE I_Zsactivity LINES V_LINES.

ZSACTIVITY-POSNR = V_POSNR.

IF TC1-CURRENT_LINE GT V_LINES.

APPEND Zsactivity TO I_Zsactivity.

ELSE.

MODIFY I_Zsactivity FROM Zsactivity INDEX TC1-CURRENT_LINE.

ENDIF.

ENDMODULE.

Regards

Rajaram

[Former Member]

Hi!

Application enhancements allow customers to enhance their

application functions. Cutomer exits are preplanned by SAP and generally consist of several components.

The SAP application programmer creates SAP enhancements from function module exits, menu exits and screen exits. For this Tcode SMOD is provided.

Regards

Abhijeet

[Former Member]

Hi Raja,

Customer exit -

It is R/3 enhancement concept allows you to add your own functionality to SAPu2019s standard business applications without having to modify the original applications. SAP creates customer exits for specific programs, screens, and menus within standard R/3 applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.

Screen exit which is type of customer exit is used to add fields to screens in R/3 applications. SAP creates screen exits by placing special subscreen areas on a standard R/3 screen and calling a customer subscreen from the standard screenu2019s flow logic.

Regards,

Chandra Sekhar

[Former Member]

Hi Raja Ram,

User exit -> implemented in form of subroutine under includes (starting with any letter other than y or z) so you need the access key to change them.

Customer Exit -> implemented in the form of includes starting with y or z, so you don't need an access key to change them. The developer key is more than enough to change any customer exit.

SMOD -> used to find/create/change existing exits.

CMOD -> create/find/change existing project.

for more information refer to the following link.

regards...

gautam.