Processing type as customer exit

is it useful in real time
if it is,
how to work with this.

hi Basha,
see this link
http://help.sap.com/saphelp_sem60/helpdata/en/e3/e60138fede083de10000009b38f8cf/frameset.htm
Best regards
vijju

Similar Messages

BW Authorizations - Query variable with processing mode as "customer exit"

Hi,
Iam new to BW authorizations and have not yet worked on customer exit before. I was going through the documentation at various sites but I could not get the end to end description on how the query process( when using a variable for an InfoObject) works in case of customer exit.
Let's assume that I am using a query variable with processing mode as "customer exit" and at the exit I write some code to extract user's authorizations from a z table. if this is the case, then when an end user runs a query,how will the the system know what value needs to be filled in the variable for the requesting user. Are the user details also sent to the code along with the query variable? If so how. If I mis-understood the process then forgive me and let me know the correct process.

Hi!
welcome to SDN!
customer exit variables need programing by user. so if you create a customer exit variable, you got to right a program which extracts values into this variable. we can do what ever we want in program, SAP will not deal anything ´with customer exits.
with regards
ashwin
PS n: Assigning point to the helpful answers is the way of saying thanks in SDN. you can assign points by clicking on the appropriate radio button displayed next to the answers for your question. yellow for 2, green for 6 points(2)and blue for 10 points and to close the question and marked as problem solved. closing the threads which has a solution will help the members to deal with open issues with out wasting time on problems which has a solution and also to the people who encounter the same porblem in future. This is just to give you information as you are a new user.

Currency conversion type by customer exit variable doesn't work

Hi all.
In my query I need amounts by quarter, applying quarters last date rates as currency conversion.
Query has Year parameter. Based on this parameter, by customer exits I calculate every quarters last date and use them as currency conversion types.
The problem is that query DOESN'T APPLY currency conversions!
I checked TCURR table - currency conversions do exist for applied days
I checked my customer exits - the date calculation works fine
I suppose where is something wrong in query processes (customer exits/currency conversions) sequence before running it.
Someone knows anything 'bout that?

Check these docs.. and check again.
[Creating Currency Translation Types|http://help.sap.com/saphelp_nw04/helpdata/en/80/1a6813e07211d2acb80000e829fbfe/content.htm]
[Use Variables for Currency Conversion|http://www.scribd.com/doc/7061035/How-to-Use-Variables-for-Currency-Conversion]

Processing type as SAP Exit with Variable 0F_ADAY

Hi Experts,
We are using the formula variable in our report as caluculated key figure. I have edited the CKF and drill down the formula node to check the processing type of it and found as SAP Exit and the variable name is 0F_ADAY. How can i navigate to get in to the SAP Exit code. Any help will be appreciated.
Thanks and Regards,
Venkat

Hi Venkat,
Go to the function module "RSVAREXIT" (T.Code - SE37) and check for you variable (0F_DAY)there. From there u can check the code corresponding to that variable;
Regards
Prasad;

Variable creation in bw with customer exit

hi experts,
how to create a variable in bw with customer exit?

Hi
Create a variable with Processing type as customer exit.
Then Go to Se38 and ZXRSRU01 program in change mode and there you write the necessary coding how your customer exit variable should process.
else you can access the include function via CMOD also with selecting the enhancement for reports.
Regards
RaM

Authorisation variable using customer exit

Hi,
how to populate a authorisation object at runtime? is it possible to have a variable etc that can be populated a runtime?
I have a object zsales_off which has different values for different users. i need to create separate roles just to have different values for sales office for different users. i would like to avoid this by having a single role with the zsales_off getting populated at runtime.
please give details steps with code if possible?
i have created the authorisation variable and am using it in the query. if i manually assign values for sales office in the role, it is working fine.
i want to assign values at run time. i am confused with the process as such.
few specific doubts like:
1> the variable should be of "authorisation" processing type or "customer exit" processing type.
2>what to use I_step=0 or I_step =1? how to use? where to use?
3>to write a abap code or use a func module, which one? how to use.
4> what(value) to assign for the zsales_off object in the authorisation profile?
thank u in advance..

Hi torsten,
thank you. but i am afraid it doesn't give me an idea as to how to move ahead?
i have variable with processing type "authorisation" used in many queries.
can i use the customer exit rsr0001 for this variable? what value should be assigned in the authorisatio profile for this object?
please give the detail process and a abap code if possible.
thank u

Customer exit - code for variable

Hi Friends,
I have created a variable "CUST_EXIT_YEST" and defined the processing type as customer exit. Now would like to add code in CMOD.
Requirement: The variable should allow take yesterday's date. Please help me with the code.
Already there are some codes defined for other customer exit variables in CMOD. Can I add my code below that. If so please explain.
Regards,
Surjit

If i'm not wrong you want to show previous day in the variable.
At the bottom of the existing code before EndCase, u can write the below code
Data: loc_var_range      LIKE rrrangeexit, (must be there this kind of declaration in ur existing code)
WHEN 'CUST_EXIT_YEST'.
    IF I_STEP = '1'.
      Read Table I_T_VAR_RANGE into LOC_VAR_RANGE WITH KEY VNAM = 'CUST_EXIT_YEST'.
      myrange-SIGN = 'I'.
      myrange-OPT = 'EQ'.
      myrange-LOW = sy-datum - 1.
      APPEND myrange TO e_t_range.
    ENDIF.

Passing multiple single values in Customer Exit Variables

Hi,
I have one requirement to Pass multiple single values in Customer Exit Variable.
If the user gives 2010 i need to get value previous fisacal year(2009),if its 2009, we need to get 2009.
Just requirement is like how to pass multiple single values?
Thanks.

Hi..
For this create a variable- Types of variable= Characteristics Value> Processing type as Customer Exit-->Reference Char as Fiscal year..
Try this code..
    when 'xxxx'.
      DATA: lv_zp0003_month(2) TYPE n,
              lv_zp0003_year(4) TYPE n.
      CLEAR: lv_zp0003_month, lv_zp0003_year.
      lv_zp0003_month = sy-datum+4(2).
      lv_zp0003_year = sy-datum(4).
If the month is January the year is set to previous year
      IF lv_zp0003_month = '01'.
        lv_zp0003_year = lv_zp0003_year - 1.
       l_s_range-low = lv_zp0003_year.
Else the year is set to actual
      ELSE.
        l_s_range-low = lv_zp0003_year.
      ENDIF.
      IF l_s_range-low = l_s_range-high.
        l_s_range-opt = 'EQ'.
      ELSEIF l_s_range-high IS INITIAL.
        l_s_range-opt = 'EQ'.
      ELSEIF l_s_range-low LT l_s_range-high.
        l_s_range-opt = 'BT'.
      ENDIF.
      l_s_range-sign = 'I'.
      APPEND l_s_range TO e_t_range.
Hope this helps.
Regards.
AKG

Sample of plan version customer exit code

Hi! We have a requirement for Forecast accuracy report to be able to report comparison of current actual v current month forecast and
forecast 1 month ago, forecast 2 months 2 up to 12 months ago. I'm using Calculated/Restricted Key figures with variables "0FISCYEAR & and 0P_FYEAR" with offset and plan version variable 0VERSION & OP_VERS3 but not restricted. The offset for period/year works but not sure how to link it to a plan version specific to period/year. We don't want the variable for plan version to be fixed. We would like to pull the values of the Cal./Rest key figures for period/year and specific version. In our case, we use versions 1, 2, 3 up to 12 for 2010, and version 1 represents 01/2010 forecast/plan version, version 2 is 02/2010 up to 12/2010 version 12. And for 2011, we use versions 101, 102, 103 up to 112. 101 is version specific for 01/2011, 102 for 02/2011 up to 112 for 12/2011. Same thing for FY 2012, our versions are 201 (representing version for 02/2012) , 202, 203 up to 212. We have the same pattern of versions for 2020 as well (starts from 01 to 12; 101 to 112; 201 to 212 up to 901 to 912).
We would like to be able display the values for 12 rolling months for the version specific to period and year as mentioned above.
Example - in the query, I enter period/ year "03/2011" and version 103 (which represents the version for 03/2011). The result of the query should show up the following CKF/RKF columns:
1. Current Actual 03/2011
2. Current Forecast 03/2011 version 103
3. Forecast 1 month ago 02/2011 version 102
4. Forecast 2 months ago 01/2011 version 101
5. Forecast 3 months ago 12/2010 version 12
6. Forecast 4 months ago 11/2010 version 11
7. Forecast 5 months ago 10/2010 version 10
8. Forecast 6 months ago 09/2010 version 09 up to forecast 12 months ago version 03.
I think we will need a short coding/customer exit for variable version but donu2019t know what needs to be done if using enhancement. I created a variable customer exit for plan version "ZVAR_MULTIVERSION_EXIT". Type of variable is characteristic value, processing type is customer exit, reference characteristic is "0VERSION", other basic settings - multiple values and optional. Please advise if anything I need to change on the settings for plan version variable. Then my next question is how to code this scenario or maybe you can provide a sample abap code and how to link the customer exit to the "ZVAR_MULTIVERSION_EXIT" plan version variable.   Please advise and greatly appreciate any help and input you can provide.
Thanks a lot in advance for your help.
Ching

Hi,
Write the code as follows, it will solve your requirement:
"Declare work area WA_RANGE with type same as I_T_VAR_RANGE.
when 'variable_name'.
     IF i_step = 1.
          REFRESH e_t_range.
          data: v_date type sy-datum.
          data: v_mon type I length 2.
          data: v_year type I length 4.
          data: v_month type /bi0/oicalmonth.
          v_date = sy-datum.
          v_mon = v_date+4(2).
          v_year = v_date+0(4).
          v_year = v_year - 1. "Previous Year
          concatenate v_year v_mon into v_month.
          WA_RANGE-SIGN = 'I'.
          WA_RANGE-OPT = 'EQ'.
          WA_RANGE-LOW = v_month.
          append wa_range to e_t_range.
     ENDIF.
Hope this helps.
Regards,
Joe
Edited by: lazarus_joey on Feb 17, 2012 7:04 PM

Change varialbe into Customer Exit type

Hi all,
   Is it possible to change an existing BEx variable from default type into Customer Exit type?
   I know we can't do this in query designer. Any other approach, like modifying a DB table?
Thanks and best regards,
Aaron

Hi DeeCh.
If you want to populate the value before the variabel screen input.then please follow below code
case i_vnam.
when 'ZPKEYDT'.
if i_step = 1.
    l_s_range-low = sy-datum..
      l_s_range-sign = 'I'.
      l_s_range-opt = 'EQ'.
      APPEND l_s_range TO e_t_range.
      clear l_s_range.
          endif.
          endcase.
Regards,
Nanda.S

SAP BPC Custom Process Type - passing parameters

Hi,
I wish to create a custom process type with custom parameters which can be populated from the Data Manager package execution. I went thru the tutorial by Rich mentioned [here|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b0427318-5ffb-2b10-9cac-96ec44c73c11]. But because of access issues, I cannot install the classes on my system using the .BPC files.
Can someone please guide me as to how I can use custom parameters in my process type? So far, I have tried adding the parameter but haven't been successful:
1) Created a class ZCL_UJD_BPC_TEST (with superclass CL_UJD_ACTOR) and populated all the methods for this class.
2) Created a class ZCL_UJD_TEST and created a constructor and PROCESS method. Here I tried to read the parameter XXXXXX.
3) Added the ZBPCTEST process type in RSPC
4) Created a custom process chain with a custom variant /CPMB/ZYYYYYY for the ZBPCTEST process type.
5) Created the DM package and passed value to the parameter XXXXXX using dynamic script.
However, I get the error "Cannot configure the parameter XXXXX in task YYYYYYYY".
Thanks,
Shailesh Kamath.

Hi Shailesh,
Did u solve this, we also implemented same in BPC 7.5 NW but after migration many methods become obselete,please let me know how you approached.
Regards
Ram

Fill BEx Variable with more than one value via Custom Exit

Dear SDN comunity,
I want to fill a BEx Variable via a custom exit. My problem is, I don't know how to fill this variable with more than one value.
I try to give you some background info based on an exaple:
Variable-Details
Type of Variable: Characteristic Value
Variable Name: ZCCD
Description: Company Code Selection
Processing by: Custom Exit
Characteristic: Company Code
Variable Represents: Multiple Single Values
This is the used ABAP code:
WHEN 'ZCCD'.
CLEAR l_s_range.
l_s_range-low = '2002;2004'.
l_s_range-sign = 'I'.
l_s_range-sign = 'EQ'.
APPEND l_s_range TO e_t_range.
The system returns this message:
Value "2002;2004" is too long for variable ZCCD
appreciate your help!
//michael

Eugene, Marcus
it works now, thx a lot!
Please find attached the final code:
CLEAR l_s_range.
l_s_range-low = '2002'.
l_s_range-sign = 'I'.
l_s_range-opt = 'EQ'.
APPEND l_s_range TO e_t_range.
CLEAR l_s_range.
l_s_range-low = '2004'.
l_s_range-sign = 'I'.
l_s_range-opt = 'EQ'.
APPEND l_s_range TO e_t_range.
(Delta to Marcus's code is bold)

Difference between customer exit and user exit?

hi experts
difference between customer exit and user exit?

These r the main differences between user exits and customer exits
1) user exits r subroutines where as customer exits r function modules
2) user exits r not upgraded where as customer exits r will upgrade
3) customer exits r used for creating and additional fields or menu items to stadard tcode where as user exits r used for enabling or disabling the fields on the standrd screen or concatenating the key fields,it is not used adding an additional componenats to stadard tcode
4) customer exits r reusable where as user exits r not reusable.
Also:
1. Customer exits: Implemented as Function Modules within z includes. Anybody can change it and no access key is required.
2. User Exit: Implemented as subroutines within includes (any include except y or z includes). You need access for the specific include and then you can any subroutine (user exit) within that Include.
BADIs are the enhanced version of user exits where the same logic is implemented via classes and object (OOP)
Enchancement point is the latest once introduces with ECC6.0 . Not very sure about that but you can change it without any access key.
Please go through the following link which will help you understand the exits in a much better way:
http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec07a25db911d295ae0000e82de14a/content.htm
http://www.sap-img.com/abap/what-is-the-difference-between-smod-and-cmod.htm
http://sap.niraj.tripod.com/id21.html
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm
http://www.sap-img.com/ab038.htm
User Exits.
http://www.erpgenie.com/sap/abap/code/abap26.htm
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sapgenie.com/abap/code/abap26.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
http://www.easymarketplace.de/userexit.php
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sappoint.com/abap/userexit.pdfUser-Exit
customer exits
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f1a7e790-0201-0010-0a8d-f08a4662562d
Menu Exit.
http://www.sappoint.com/abap/spmp.pdf
http://www.sappoint.com/abap/userexit.pdf
http://www.sapdevelopment.co.uk/enhance/mod_sapmenu.htm
http://www.sapdevelopment.co.uk/enhance/enhancehome.htm
1. Previously there were only user-exits.
2. Then came the concept of customer-exits.
3. user exits were nothing but subroutines
FORM/PERFORM
called from standard programs.
4. The FORM defintion was placed inside
an empty include file.
5. So It was called EVERYTIME.
and we need to MODIFY/REPAIR the
standard include .
6. Then it came with concept of customer-exit
7. It consists of calling a FUNCTION MODULE,
which is called only if
the user-exit is ACTIVATED (other wise not called)
In this case, the code in put inside
a pre-defined Z include.
8. Functionality of both is same, howerver
we can note the following important differences
a) Customer exit is called only if activated.
(hence, it does not waste resources)
b) in customer exit, REPAIR does not happen
to the standard include.
Exits are basically the hooks whcih SAP has provided to add your own code.
User Exits: These are provided only SD module .
They are Empty subroutines with naming like USEREXIT_.
We need to have Access key to implement them.
Customer Exits: These are enhancement techniques.
There are defined in SMOD and implemented in CMOD.
Types of Customer exits: Function exit, Screen Exit, Menu exit.
User Exit and Customer Exit are same ,but SAP Exit and Customer exit are different...
Customer Exit,
Enables you to determine values for variables by means of Functional Module exit.The function module used is EXIT_SAPLRRSO_001.
Create a project in CMOD by selecting the SAP Enhancement RSR00001 and assign this to the enhanced proj and activate it.
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 SAPs 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 SAPs standard software package.
They do not affect software updates
When you add new functionality to your SAP System using SAPs 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
http://help.sap.com/saphelp_nw04/helpdata/en/1d/ca10d858c2e949ba4a152c44f8128a/frameset.htm
SAP EXIT:this processing type contained in variables that are delivered with SAP BW business content.
http://help.sap.com/saphelp_nw04/helpdata/en/1d/ca10d858c2e949ba4a152c44f8128a/frameset.htm
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
reward points if found useful
regards
palak

User exits ,customer exits

anybody tell me difference between userexits and customer exits.

Hi,
These r the main differences between user exits and customer exits
1) user exits r subroutines where as customer exits r function modules
2) user exits r not upgraded where as customer exits r will upgrade
3) customer exits r used for creating and additional fields or menu items to stadard tcode where as user exits r used for enabling or disabling the fields on the standrd screen or concatenating the key fields,it is not used adding an additional componenats to stadard tcode
4) customer exits r reusable where as user exits r not reusable.
Also:
1. Customer exits: Implemented as Function Modules within z includes. Anybody can change it and no access key is required.
2. User Exit: Implemented as subroutines within includes (any include except y or z includes). You need access for the specific include and then you can any subroutine (user exit) within that Include.
BADIs are the enhanced version of user exits where the same logic is implemented via classes and object (OOP)
Enchancement point is the latest once introduces with ECC6.0 . Not very sure about that but you can change it without any access key.
Please go through the following link which will help you understand the exits in a much better way:
http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec07a25db911d295ae0000e82de14a/content.htm
http://www.sap-img.com/abap/what-is-the-difference-between-smod-and-cmod.htm
http://sap.niraj.tripod.com/id21.html
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm
http://www.sap-img.com/ab038.htm
User Exits.
http://www.erpgenie.com/sap/abap/code/abap26.htm
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sapgenie.com/abap/code/abap26.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
http://www.easymarketplace.de/userexit.php
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sappoint.com/abap/userexit.pdfUser-Exit
customer exits
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f1a7e790-0201-0010-0a8d-f08a4662562d
Menu Exit.
http://www.sappoint.com/abap/spmp.pdf
http://www.sappoint.com/abap/userexit.pdf
http://www.sapdevelopment.co.uk/enhance/mod_sapmenu.htm
http://www.sapdevelopment.co.uk/enhance/enhancehome.htm
1. Previously there were only user-exits.
2. Then came the concept of customer-exits.
3. user exits were nothing but subroutines
FORM/PERFORM
called from standard programs.
4. The FORM defintion was placed inside
an empty include file.
5. So It was called EVERYTIME.
and we need to MODIFY/REPAIR the
standard include .
6. Then it came with concept of customer-exit
7. It consists of calling a FUNCTION MODULE,
which is called only if
the user-exit is ACTIVATED (other wise not called)
In this case, the code in put inside
a pre-defined Z include.
8. Functionality of both is same, howerver
we can note the following important differences
a) Customer exit is called only if activated.
(hence, it does not waste resources)
b) in customer exit, REPAIR does not happen
to the standard include.
Exits are basically the hooks whcih SAP has provided to add your own code.
User Exits: These are provided only SD module .
They are Empty subroutines with naming like USEREXIT_.
We need to have Access key to implement them.
Customer Exits: These are enhancement techniques.
There are defined in SMOD and implemented in CMOD.
Types of Customer exits: Function exit, Screen Exit, Menu exit.
User Exit and Customer Exit are same ,but SAP Exit and Customer exit are different...
Customer Exit,
Enables you to determine values for variables by means of Functional Module exit.The function module used is EXIT_SAPLRRSO_001.
Create a project in CMOD by selecting the SAP Enhancement RSR00001 and assign this to the enhanced proj and activate it.
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 SAPs 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 SAPs standard software package.
They do not affect software updates
When you add new functionality to your SAP System using SAPs 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
http://help.sap.com/saphelp_nw04/helpdata/en/1d/ca10d858c2e949ba4a152c44f8128a/frameset.htm
SAP EXIT:this processing type contained in variables that are delivered with SAP BW business content.
http://help.sap.com/saphelp_nw04/helpdata/en/1d/ca10d858c2e949ba4a152c44f8128a/frameset.htm
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
Reward Points if found helpfull..
Cheers,
Chandra Sekhar.

Diff b/w "Customer exits" and "User-exit"

Hi,
What is the difference b/w customer exits and user-exit and also please explain me what are the various types of customer and user-exits.
Thanks in advance.
Ramana

Hi,
Types of Exits
There are several different types of customer exits. Each of these exits acts as hooks where you can attach or "hang" your own add-ons.
Menu Exits
Menu exits add items to the pulldown menus in standard SAP applications. You can use these menu items to call up your own screens or to trigger entire add-on applications.
SAP creates menu exits by defining special menu items in the Menu Painter. These special entries have function codes that begin with "+" (a plus sign). You specify the menu items text when activating the item in an add-on project.
Screen Exits
Screen exits 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 screens flow logic.
Function Module Exits
Function module exits add functions to R/3 applications. Function module exits play a role in both menu and screen exits. When you add a new menu item to a standard pulldown menu, you use a function module exit to define the actions that should take place once your menu is activated. Function module exits also control the data flow between standard programs and screen exit fields.
SAP application developers create function module exits by writing calls to customer functions into the source code of standard R/3 programs. These calls have the following syntax: CALL CUSTOMER-FUNCTION 001.
User exits:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/abap/abap-code-samples/userexits%20in%20a%20transaction.doc
In order to find out the user exits for any tcode,
1. get the developement class of the tcode from SE93.
2. Now goto transaction SMOD and press F4,
3. give in the Deve class in the dev class and Press ENTER
this will show u the exits for any tcode.
or execute this report
http://www.erpgenie.com/sap/abap/code/abap26.htm
which gives the list of exits for a tcode
http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec079f5db911d295ae0000e82de14a/frameset.htm
For information on Exits, check these links
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sapgenie.com/abap/code/abap26.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
http://www.easymarketplace.de/userexit.php
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sappoint.com/abap/userexit.pdfUser-Exit
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.ficoexpertonline.com/downloads/User%20ExitsWPedit.doc
http://www.easymarketplace.de/userexit.php
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/content.htm
Check out these links too...
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sapgenie.com/abap/code/abap26.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
http://www.easymarketplace.de/userexit.php
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sappoint.com/abap/userexit.pdfUser-Exit
http://www.planetsap.com/userexit_main_page.htm
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
USER EXITS
https://forums.sdn.sap.com/click.jspa?searchID=672084&messageID=312792
https://forums.sdn.sap.com/click.jspa?searchID=672084&messageID=1320078
https://forums.sdn.sap.com/click.jspa?searchID=672084&messageID=2669896
****Reward points if helpful.
All the best

Processing type as customer exit

Similar Messages

Maybe you are looking for