Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

user exit

Former Member
0 Likes
796

hi guys,

i want to write a custom code in the subroutine USEREXIT_FIELD_MODIFICATION

in the program MV45AFZZ. which is a standard userexit prog.

can any body tell me how to do it.

2. what is the exact difference and procedure for USEREXIT AND CUSTOMER EXIT.

thankx

will be rewarded.

ahmed

9 REPLIES 9
Read only

Former Member
0 Likes
746

Hi,

Goto SOMD, and activate the Use exit first, then there in the Function moduel you need to write the code.

Read only

Former Member
0 Likes
746

Hi,

1) Check this example..

    • I am disabling the field payment terms..VBKD-ZTERM.

IF SCREEN-NAME = 'VBKD-ZTERM'.

SCREEN-INPUT = '0'.

ENDIF.

2) Userexits doesn't require project for activating it..Generally userexits are subroutines where you can directly code in sap standard program like MV45AFZZ..

Customer exits require a project for including the enhancement..Then it requires activatation for the user exit to work..

Thanks,

Naren

Read only

anversha_s
Active Contributor
0 Likes
746

hi,

Customer Exit
SAP creates customer exits for specific programs, screens, and menus within standard 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.

If you want to enhance the functionality of your SAP System, you should take advantage of the exits available in standard applications. There are two main reasons why you should use exits rather than modifying SAP software yourself. Add-ons attached to exits have the advantage that:

· They do not affect standard SAP source code

When you add new functionality to your SAP System using SAP’s exits, you do not alter the source code of standard SAP programs in any way. The code and screens you create are encapsulated as separate objects. These customer objects are linked to standard applications, but exist separately from SAP’s standard software package.

· They do not affect software updates

When you add new functionality to your SAP System using SAP’s exits, your objects (called customer objects) must adhere to strict naming conventions. When it comes time to upgrade a to a new software release, customer objects’ names ensure that they will not be affected by any changes or new additions to the standard software package.

Customer exits are not available for all programs and screens found in the SAP System. You can only use customer exits if they already exist in the SAP System. You find find more information about locating applications with pre-defined exits in Locating Applications that have Exits

User Exits:

User exits allow you to add additional functions to the SAP standard.

Programs with user exits contain subroutine calls at certain points in their syntax that are identified by the prefix USEREXIT. The actual user exits are located in an include that has been assigned to a module pool. This is where customers can include any changes (enhancements) that they want to make to the system. These includes are always processed during program flow.

Advantage: In principle, customers can modify anything they want that is found in the include (tables, structures, and so forth).

Disadvantage: SAP cannot check the individual enhancements themselves which often leads to errors in the enhancement process.

Thanks and Regards,

Anver

Read only

Former Member
0 Likes
746

For field modification take the screen name of the field into the case and process the logic.

CASE SCREEN-NAME.
    WHEN 'KUWEV-TXTPA'.
      CHECK NOT KUWEV-TXTPA IS INITIAL AND KUWEV-LAND1 = 'US'. "sample code to validate the field 
          SELECT * FROM XXXX INTO TABLE I_TAB
          WHERE XXX = XXX.
          if sy-subrc eq 0.

          endif.   
Process the logic.
       ENDCASE.

regards,

vijay

Read only

Former Member
0 Likes
746

Ahmed,

To do the changes in MV45AFZZ for the first time you will have to get 'Access Key' as it is SAP standard Exit. Once you get the Access Key you will have to press button 'insert' from the application toolbar iin routine USEREXIT_FIELD_MODIFICATION. This will allow you to write your code there. rest all updates are already posted here.

Thanks

Read only

Former Member
0 Likes
746

Hi,

no need of access key for this. you can change the same by creating a request

Regards

Shiva

Read only

Former Member
0 Likes
746

1. Please have a look at below link to get the details abt the user exit that you have mentioned.

<a href="http://help.sap.com/saphelp_46c/helpdata/en/1c/f62c7dd435d1118b3f0060b03ca329/content.htm">User Exits for Sales order processing</a>

2. A 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.

I hope it helps.

Best Regards,

Vibha

*Please mark all the helpful answers

Read only

Former Member
0 Likes
746

Hi Ahmed,

User Exits are used to add additional functionality to the SAP standard applications.These exits can be identified with the keyword 'USEREXIT' which is found in the include statements.On clicking this exit, you will goto ABAP editor where u can place your own code.For Userexits u need not go for implementing a project.

On the other hand, Customer exits acts as hooks to which you can hang on your own functionality(source code).The main advantages of this customer exits are

1.this don't effect the SAP standard source code and

2.this doesn't have any effect when there is any upgrading of software.

coz these are stored as seperate objects.

Read only

Former Member
0 Likes
746

Hi Ahmed,

User Exits are used to add additional functionality to the SAP standard applications.These exits can be identified with the keyword 'USEREXIT' which is found in the include statements.On clicking this exit, you will goto ABAP editor where u can place your own code.For Userexits u need not go for implementing a project.

On the other hand, Customer exits acts as hooks to which you can hang on your own functionality(source code).The main advantages of this customer exits are

1.this don't effect the SAP standard source code and

2.this doesn't have any effect when there is any upgrading of software.

coz these are stored as seperate objects.

If found useful ,please do reward points.

Thanks ,

Naresh