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 vs function module exit in sap abap

0 Likes
2,269

I am not understanding the difference between these two.

I have one requirement like if so item is tagged with advance receipt, then only it will not all you to delete that line item.

For this I have gone to MV45FZZ program and find userexit_check_xvbap_delete and my code. Can anyone suggest me if I am going into wrong way.

1 ACCEPTED SOLUTION
Read only

former_member1716
Active Contributor
1,717

Hello Sanjib Ganguly,

Greetings!

Yes implementing USER_EXITS is better in this case. USER-EXITS primarily came into picture for SD Module. Both user exits and Function Exits are features provided by SAP. Considering your current requirement USER_EXITS suits the best. You just need to take care during Upgrade activities.

On a short note on FUNCTION EXITS, they are more encapsulated form of enhancements provided. We cannot implement them as such, we have to wrap them up into a project through predefined enhancements available for them. You can see key words CALL CUSTOMER FUNCTION in any standard programs, these are the external plugins through which your requirement is added.

Hope it helps!

Regards

3 REPLIES 3
Read only

GK817
Active Contributor
1,717

Hi,

You are implementing User Exit, which is a valid way.

FM exits are implemented through SMOD/CMOD and can be identified by CALL CUSTOMER-FUNCTION.

More details:

https://answers.sap.com/questions/4096867/difference-between-customer-exit-and-user-exit.html

Regards

GK

Read only

former_member1716
Active Contributor
1,718

Hello Sanjib Ganguly,

Greetings!

Yes implementing USER_EXITS is better in this case. USER-EXITS primarily came into picture for SD Module. Both user exits and Function Exits are features provided by SAP. Considering your current requirement USER_EXITS suits the best. You just need to take care during Upgrade activities.

On a short note on FUNCTION EXITS, they are more encapsulated form of enhancements provided. We cannot implement them as such, we have to wrap them up into a project through predefined enhancements available for them. You can see key words CALL CUSTOMER FUNCTION in any standard programs, these are the external plugins through which your requirement is added.

Hope it helps!

Regards

Read only

0 Likes
1,717

Thank you.

That means I can write my logic in the userexit "userexit_check_xvbap_for_delete" And make my code as implicit enhancement with in this user exit. I have worked on this way and it's working.

Suggestions please if my approach is right or wrong please.