Customer Exit implementation

Hi I need to implement one customer exit EXIT_SAPLWRPL_001 for replenishment program with t-code wrp1.Pls can any one tell me the step by step procedure how i need to implement and activate the exit.Is it mandatory to create project in cmod? If yes how can i fing the enhancement to where this exit belongs?I required detailed description.Pls help me
Moderator message: please don't ask for step by step guidance, do your own research for available information before asking.
Edited by: Thomas Zloch on Nov 17, 2010 1:00 PM

Yes, you need to create a project in CMOD.
To find the enhancement, go to transaction SMOD, and do a search (CtrlF). Open up All Selections (ShiftF9), paste EXIT_SAPLWRPL_001 into Component Name, which then returns WRPL0001, which is the exit/enhancement that you must implement.
When you create the project in CMOD, you must assign this enhancement to your project. In the function module, double-click on the include name to create it. Inside, you can include your code with references to the parameters of the function.

Similar Messages

User Exit / Functional Exit / Screen Exit /Customer Exit

Dear all,
Can anybody explain me about the User Exit / Functional Exit / Screen Exit /Customer Exit and give me the step by step procedure.I want to know more plese reply me.

Hi,
Exits are basically the hooks whcih SAP has provided to add your own code. There are two types of Exits:
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
USER EXIT
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/ab038.htm
http://help.sap.com/saphelp_46c/helpdata/en/64/72369adc56d11195100060b03c6b76/frameset.htm
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://expertanswercenter.techtarget.com/eac/knowledgebaseAnswer/0,295199,sid63_gci982756,00.html
Field Exit
If you are in 4.7 and up follow this
1. Run report RSMODPRF
2. Run on the selection screen
3. In list Field Exit > Create
4. Give your data element
5.System will generate the FM FIELD_EXIT_XXXXX
6. Activate it.
7. Select your field exit and assign to your program and screen
8. Select again .. Field exit > Activate
If you are in version below 4.7
1. CMOD
2. Go to >Text enhancment > Field exit
then follow the same step from 3 onwards as given above.
Menu Exit
Procedure for Creating MENU Exits.
1) To get into Area Menu Maintenance Screen Type SE43 T.Code in Command
Line.
2) In Area Menu Paramenter type 'S000' (S triple Zero)
3) Then Press Change Icon in Application Tool Bar. Then It may ask for
Access Key [or] it may display "Specify Processing mode" window. If it ask
for the Access Key Check for the availability of OSS Note and apply to open
Standard SAP Menu to include MENU Exits. Otherwise, if it display "Specify
Processing mode" window with Three Push Button. In which select "Change" and
proceed further.
4) Then it will display "Information" window with the following information
"Caution : The Original Language of the structure is German (editing lang. :
English) ". Then press "Enter Key to proceed further.
5) Then you will get into "Edit Area Menu S000".
6) for eg:- Expand Tools Menu.
7) Then Press ABAP Workbench <Icon>.
8) Then you will get into ABAP Workbench Menu Tree.
9) Then Expand Utilities Menu.
10) In the last line you will find one MENU EXIT Provision to include your
own menu. "Node Text Not Found" This text can be change by double Clicking
that. There you can find the T.Code. Here for Eg:- "+DW4".
11) for eg: - Here change the Text to "Sample Menu Exit" and then note down
the T.Code "+DW4".
12) Then Save with Change Request Number and come out of Transaction SE43.
13) Then Goto Transaction SE93.
14) Then type T.Code "+DW4" and press Create.
15) Then proceed further to create transaction called "+DW4".
I hope this could help you in Creating Menu Exit...
Creating menu exits
http://help.sap.com/saphelp_nw04/helpdata/en/c8/19762743b111d1896f0000e8322d00/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/83/7a18cbde6e11d195460000e82de14a/frameset.htm
Regards,
Satish

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.

How to Verify the Variable Input in Customer EXIT

Hi,
      I have a requirement to find out "Estimated Hours Total Calculation" with User input date range. I know little bit knowledge about Customer Exits please some one give me how to write code in CMOD. I have requirement how to get the Extimated Hours Total Calculation is follows ....
        Actual hours are the Hour Meter Reading used by the truck, it's calculated based on the "from and to" date parameters.
Collect the initial hours and adjusted hours from EM.
Get the PMN and Service Order data close to or within the Date Range.
1) If the Fleet Management Date (Start-up Date on EM) started before the input date Date Range (From-Date), calculate the average usage (in hours) based on the initial hours and the first PMN (or SO) falls within the Date Range to estimate the hour usage at start of Date Range.
2) If the Fleet Management Date started after the From-Date, use the Hour Meter (EM) as the Estimated Hours Begin.
3)If the last PMN (or SO) fell short of the Date Range (To-Date), obtain the Estimated Hours End by applying the average usage to fill the time-gap.
4)If the last PMN (or SO) fell after the Date Range (To-Date), get the Estimated Hours End by getting the next to last PMN performed inside the window parameter,
     calculate the average usage between the two PMN's (or SO's) then apply the weighted average to fill the time-gap.
Adjusted Hours, if not zero or null, needs to be added to the Ending Hours to achieve the real number.
For Example
User Input Date Range: Jan. 1, 2006 - Dec. 31, 2006
Initial Hour (Equipment Master): 10
Adjusted Hours (Equipment Master): 0
Fleet Management Date (Equipment Master): Dec. 1, 2005
1st PM Notification (Feb. 1, 2006): 410
Last PM Notification (Feb. 1, 2007): 2810
Second to last PMN (Dec. 1, 2006): 2410
     Equipment was put into service (12/1/05) before the Date Range, needs to find the Estimated Hours Begin.
     The first PM was performed (2/1/06) exactly two months from in-service date (12/1/05).
     Average monthly usuage from first PMN = (410 - 10) / 2 = 200
     Estimated Hours Begin = 200 + 10 = 210 (estimated Hour Meter Reading on Jan. 1, 2006)
     Average monthly usuage from the last 2 PMN = (2810 - 2410) / 2 months = 200
     Estimated Hours End = 2410 + 200 + 0 (adjusted hours) = 2610 (estimated Hour Meter Reading on Dec. 31, 2006)
     Estimated Hours Total = 2610 - 210 = 2400
           Please give me your valuable answers. Please let me know if you need any further information.
Thanks
Dave Sam.

hi,
well, your requirement seems clear but complex and needs more clarification:
- what kind of infoprovider do you use
- what is posted in your provider, I mean which characteristics and and key figures (name and descriptions)
- what is the user input
depending on that, the implementation may vary
Please clarifiy
Olivier.

Customer exit variable - internal table in BEX

Hi,
i am running a report and using variables in it.
The report runs over a info cube. There are few challenges in it.
One of the variable is posting date, and when user enters posting date i need to negate it with current system date.
If the negated value is greater than 28 then i need to exclude documnet type 'YG' and display the query, else i need to include the dcumnet type 'YG' and document type ' '. The above logic can be well implemented via a customer exit variable(for posting date) using an internal table. We have internal tables like C_T_DATA which is used in data source enhancement, which help us to implement our own desired logic.
Do we have such kind of internal tables, based on which the report output (result set) is derived?
i know that we have l_t_range and e_t_range, but dont know their usage, some one can explain in detail about them?
Thanks in advance.

Hi Selva & Lakshmin,
The code given by Selva is almost correct . If my understanding is clear , you also wanted to include document type ' ' when the negated value is less than 28 .
Modification in Selvas Code :
Variable 'V_DOCTYP' must be of type Multiple Single Values.
DATA : V_DATE LIKE SY-DATUM.
DATA : V_DAYS TYPE I.
if i_step = 2.
when 'V_DOCTYP'.
READ TABLE i_t_var_range INTO loc_var_range WITH KEY vnam = 'ZV_PDATE''.
IF SY-SUBRC = 0.
V_DATE = loc_var_range-low.
ENDIF.
V_DAYS = SY-DATUM - V_DATE.
IF V_DAYS > 28.
l_s_range-low = 'YG'
l_s_range-sign = 'E'.
l_s_range-opt = 'EQ'.
APPEND l_s_range TO e_t_range.
ELSE.
l_s_range-low = 'YG'
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 = ' '.
l_s_range-sign = 'I'.
l_s_range-opt = 'EQ'.
APPEND l_s_range TO e_t_range.
ENDIF.
ENDIF.
Hope the above reply was helpful.
Kind Regards,
Ashutosh Singh

Difference b/w Customer exits and User Exits

Hi,
Can anybody explain diff b/w user exits and customer exits .
How to find out and Impement the coding ..
Thanks Advance
Rohan.A

Hi Rohan,
Check this matter , this may be helpful to you.
CUSTOMER EXITS
The enhancement concept allows you to add your own functionality to SAPs standard business applications without having to modify the original applications. 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.
User exits :
1. Introduction
2. How to find user exits
3. Using Project management of SAP Enhancements
1. Introduction:
User exits (Function module exits) are exits developed by SAP. The exit is implementerd as a call to a functionmodule. The code for the function module is writeen by the developer. You are not writing the code directly in the function module, but in the include that is implemented in the function module.
The naming standard of function modules for functionmodule exits is:
EXIT_<program name><3 digit suffix>
The call to a functionmodule exit is implemented as:
CALL CUSTOMER.-FUNCTION <3 digit suffix>
Example:
The program for transaction VA01 Create salesorder is SAPMV45A
If you search for CALL CUSTOMER-FUNCTION i program
SAPMV45A you will find ( Among other user exits):
CALL CUSTOMER-FUNCTION '003'
exporting
 xvbak = vbak
 xvbuk = vbuk
 xkomk = tkomk
importing
 lvf_subrc = lvf_subrc
tables
 xvbfa = xvbfa
 xvbap = xvbap
 xvbup = xvbup.
The exit calls function module EXIT_SAPMV45A_003
Hope this is helpful.
Reward all the helpful answers.
Regards

Custom Exit to count No: of Employee based on User Input Date

Hi There,
I have a requirement to Count the no: of Employees for each Position Id. This count value changes with time (Time-dependent).
So, when the user Keys-in a date at the Query Execution-Prompt, it should take the date value and then count the no: of employees for each Position Id.
Next, it should display text like If Count = 1    "Single"
                                                  If Count =2     "Double"
                                                  If Count >=3   "Triple"
I was informed that we should create a Calculated Key Figure and then introduce a variable in it with Replacement path as Customer Exit.
My Question is: Could any one provide me the logic to implement the Customer Exit for above requirement. I kow that I need to implement this is BI ABAP editor as Include file.
Further, I referred following Forums links. However, I need more information.
counting the number of rows.
Customer Exit Variable Code
Any Suggestions!
- Anil

Hi,
As I understood, first thing you may not have text for a key figure (will not be able to display "Single", "Doüble" etc..)
Are you doing reporting on master data or cube?.
If it is a master data the it will be better to include count at staging level. You just need to include one key figure count as an attribute and assign 1 over there. You may usee this key figure directly in report.
If it is one cube/DSO then just create one CKF assign value as 1 in report in that. Use Exception aggrigation for this CKF reffering Position id in report. Dipslay this key figure.
I hope it will help.
Thanks,
S

Creation of Customer Exits in release 6.00 is having some problems

I am facing problems while creating Customer Exits in release 6.0. Since due to the introdution of enhancement spots I am not clear as what is significance of enhancement spots for the BADI. How will it affect it?
Also, I am finding differences while creating the BADI in 6.00 release and that of lower releases. In 6.0 release it is not creating the default implementation which the system creates itself for lower releases when the BADI is activated. I want to know if this functionality is removed in the higher release or due to some other reason?
Kindly let me know about these nuances as it is creating much problem in 6.0 release.

I'm just wondering if release 6.00 (I mean SAP ERP) is already available non-rampup customers?
Peter

How to create a customer-exit to calculate a week from a date

Hi my Guru's,
I actually try to implement an Exit variable to calculate a week number from a characteristic date (0FINISHDATE) in my BEX report. Does anyone has an example of customer-exit which calculate a week number after giving a date in the popup.
What I really need is how to initialize the OFINISHDATE value in my Exit.
Any help will be appreciate,
Cheers,
MK2

Hi,
I donot know this following workaround works properly are not. we have to wait for Our BW gurus' suggestions.
1) Create a formula variable with 'Replacement path' as processing type on Characterstic 0FINISHDATE.
2) Create one more Formula variable with 'customer exit' as processing type .
3) In Cmod
DATA: l_s_range type rsr_s_rangesid.
DATA: datein like sy-datum. "la caractéristique date
DATA: date2 like SCAL-WEEK. " déclaration de Résultat
DATA : NUMB1(2) TYPE N.
CASE i_vnam.
when 'FORMULA_VARIABLE2'.
IF I_STEP = 2. "after the popup
LOOP AT I_T_VAR_RANGE INTO LOC_VAR_RANGE
WHERE VNAM = 'FORMULA_VARIABLE1'.
CLEAR L_S_RANGE.
L_S_RANGE-LOW(8) = LOC_VAR_RANGE-LOW(8)
datein(8) = L_S_RANGE-LOW(8).
here we are finding the Week no user entered date.
CALL FUNCTION 'DATE_GET_WEEK'
EXPORTING
DATE = datein
IMPORTING
WEEK = date2.
numb1 = date2+4(2)
CLEAR L_S_RANGE.
L_S_RANGE-LOW = numb1.
L_S_RANGE-SIGN = 'I'.
L_S_RANGE-OPT = 'EQ'.
APPEND L_S_RANGE TO E_T_RANGE.
ENDCASE.
With rgds,
Anil Kumar Sharma .P
Message was edited by: Anil Kumar Sharma

SAP BEx Customer Exit

Hi Gurus,
I've implemented the code below for my report to display Required Start Date (MM/DD/YYYY) by searching and processing either a single Fiscal Year/Period (PPP/YYYY to PPP/YYYY) input or a range/interval Fiscal Year/Period (PPP/YYY) input. The details are,
1) Created 1 User Entry Interval Mandatory Variable under Fiscal Year/Period InfoObject (Display) - ZFYP_IN
2) Created 1 Customer Exit Interval Mandatory Variable under Required Start Date InfoObject (Output) - ZRSD_CX
*& Include           ZXRSRU01
DATA: L_S_RANGE1 TYPE RSR_S_RANGESID,
      L_S_RANGE TYPE RSR_S_RANGESID,
      LOC_VAR_RANGE TYPE RRS0_S_VAR_RANGE,
      ZYEAR TYPE T009B-BDATJ,
      ZMM TYPE T009B-POPER,
      ZMM1 TYPE T009B-POPER,
      ZYEAR1 TYPE T009B-BDATJ,
      ZSTARTDATE TYPE SY-DATUM,
      ZENDDATE TYPE SY-DATUM.
IF I_STEP = 2.
CASE I_VNAM.
**To populate ZCURDAY with current system date**
   WHEN 'ZCURDAY'.
    CLEAR: L_S_RANGE1.
    L_S_RANGE1-LOW    = SY-DATUM.
    L_S_RANGE1-SIGN   = 'I'.
    L_S_RANGE1-OPT    = 'EQ'.
    APPEND L_S_RANGE1 TO E_T_RANGE.
**To Lookup ZREQSTDAT with 0FISCPER*************
**This loop will capture the Fiscal Year/Period range input by the user**
   WHEN 'ZRSD_CX'.
    READ TABLE i_t_var_range WITH KEY VNAM = 'ZFYP_IN'
      INTO LOC_VAR_RANGE.
    IF SY-SUBRC = 0.
       CLEAR L_S_RANGE.
**This 2 call functions are used to convert the Fiscal Year/Period range into**
**Calendar Day range for use on further lookup in Required Start Date**
       ZYEAR = LOC_VAR_RANGE-LOW(4).
       ZMM = LOC_VAR_RANGE-LOW+4(3).
       CALL FUNCTION 'FIRST_DAY_IN_PERIOD_GET'
         EXPORTING
           I_GJAHR              = ZYEAR
         I_MONMIT             = 00
           I_PERIV              = 'SC'
           I_POPER              = ZMM
         IMPORTING
           E_DATE               = ZSTARTDATE.
       IF ZMM EQ 012.
          ZMM1 = '001'.
          ZYEAR1 = ZYEAR + 1.
       ELSE.
          ZMM1 = ZMM + 1.
          ZYEAR1 = ZYEAR.
       ENDIF.
       CALL FUNCTION 'FIRST_DAY_IN_PERIOD_GET'
         EXPORTING
           I_GJAHR              = ZYEAR1
         I_MONMIT             = 00
           I_PERIV              = 'SC'
           I_POPER              = ZMM1
         IMPORTING
           E_DATE               = ZENDDATE.
       ZENDDATE = ZENDDATE - 1.
**A third and final function to use the calendar day range provided to lookup on matching**
**dates in Required Start Date (ZREQSTDAT)*************************************************
       L_S_RANGE-SIGN = 'I'.
       L_S_RANGE-OPT   = 'BT'.
       L_S_RANGE-LOW   = ZSTARTDATE.
       L_S_RANGE-HIGH = ZENDDATE.
       APPEND L_S_RANGE TO E_T_RANGE.
    ENDIF.
ENDCASE.
ENDIF.
However, after doing extensive testing I discovered that the code is only able to process 1 period at a time versus an interval of periods as required.
For example,
Input Fiscal Year/Period Interval - 001/2011 to 004/2011
Expected returned dates - 02/27/2010 to 07/02/2010 (4 periods)
Actual returned dates - 02/27/2010 to 04/02/2010 (only 1 period, the 1st period and not the balance 3 periods)
Only the first period is returned versus the periods entered. I'm not sure what is missing from the code to process the entered interval.
Appreciate any help provided.
Warm regards,
Eric

Hi,
After looking your code, I think the problem is at the below mentioend part.
WHEN 'ZRSD_CX'.
READ TABLE i_t_var_range WITH KEY VNAM = 'ZFYP_IN'
INTO LOC_VAR_RANGE.
IF SY-SUBRC = 0.
CLEAR L_S_RANGE.
**This 2 call functions are used to convert the Fiscal Year/Period range into**
**Calendar Day range for use on further lookup in Required Start Date**
ZYEAR = LOC_VAR_RANGE-LOW(4).
ZMM = LOC_VAR_RANGE-LOW+4(3).
Here, you should put validation like this.
If not LOC_VAR_RANGE-LOW is initial.
      If not LOC_VAR_RANGE-HIGH is initial
          ZYEAR = LOC_VAR_RANGE-HIGH(4).
          ZMM = LOC_VAR_RANGE-HIGH+4(3).
         else.
          ZYEAR = LOC_VAR_RANGE-LOW(4).
          ZMM = LOC_VAR_RANGE-LOW+4(3).
endif.*
else.
put a validation to see that some input is given for fiscal year
endif.
only after these lines go for your function modules. This way, if your variable has range given, it would calculate till the higher range given for fiscal period.
Edited by: Rahul K Rai on Jul 15, 2010 11:17 AM
Edited by: Rahul K Rai on Jul 15, 2010 11:18 AM

Integration of customers and vendors- customer exit for renaming

We are planning to use customers for capacity reservation functionality and vendors for subcontracting in APO.
Due to this, we will need Vendors and Customers in APO.
Currently some plants are using same number range for customers and vendors.
So, we will have to rename either customer number or vendor number.
In such situation, do you recommend renaming customer number or Vendor number?
Do you see impact of renaming customer or vendor in above processes?
Can you please e-mail me which customer exit I should use and steps that should be followed for renaming?
Thanks,
Srini

Your problem:
Different location types with the same name or number in the external system. For example, a customer and a supplier both have the number 1000. This problem occurs especially with vendor and customer numbers.
You can do the following:
described in SAP Note 458914.
Activate BAdI Implementation for Location Prefix
Procedure
1.     Access the activity using one of the following navigation options:
SAP SCM Menu     Tools  Customizing  IMG  Execute Project  SAP Reference IMG  SAP Implementation Guide  SCM Basis  Integration  BAdIs for Specific Applications  Location and Business Partner  BAdI: Inbound Processing for Location
Transaction Code     SPRO
2.     In the Business Add-Ins: All Implementations for Definition SMOD_APOCF001 dialog box, go to the Defined filters table and select the suitable implementation for your problem situation, for example:
Field Name     Entry Value
Bus. add-in implementation name     APOCF001_TYPEDIF
Implementation short text     Locations of different type with similar names
3.     Choose Change.
4.     Confirm the warning message.
5.     On the Business Add-In Builder: Change Implementation APOCF001_TYPEDIF screen, choose Activate business add-in implementation.
6.     In the Prompt for transportable Workbench request dialog box, enter a workbench request and press ENTER.
7.     Choose the Back pushbutton (F3) twice.

USER EXITS Vs CUSTOMER EXITS

Hi all,
can any one clearly explain me the diff between user exits & customer exits.....
points will b rewarded .....
Thank You.
Regards,
Prashanth.

Hi Prashanth Polsani ,
Difference between user exits & customer exits:
User exit - A user exit is a three character code that instructs the system to access a program during system processing.
SXX: S is for standard exits that are delivered by SAP.   XX represents the 2-digit exit number.
UXX: U is for user exits that are defined by the user. XX represents the 2-digit exit number
Customer exit - The R/3 enhancement concept allows you to add your own functionality to SAPs 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.
The following document is about exits in SAP :-
The R/3 enhancement concept allows you to add your own functionality to SAPs standard business applications without having to modify the original applications.
SAP creates user 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.
Types of Exits
There are several different types of user 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 pull down 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.
Field Exits
Field exits allow you to create your own programming logic for any data element in the Dictionary. You can use this logic to carry out checks, conversions, or business-related processing for any screen field. Example: The data element BBBNR identifies a companys international location number. You might want to set up your R/3 System so that all international location numbers are larger than 100.
The field exit concept lets you create a special function module that contains this logic.
You assign the special function module to the data element BBBNR. You then assign the module to any programs and screens in which users can add new international location numbers. When you activate your field exit, the system automatically triggers your special routine whenever a user enters a company location number.
In 4.6c, you can use "RSMODPRF" program to create field exits.
An example of a user exits :-
MODULE user_exit_0001 INPUT
    CASE okcode.
        WHEN 'BACK OR EXIT'.
            CASE sy-dynnr.
                    WHEN '100'.
                         SET SCREEN 0.
                         LEAVE SCREEN.
                    WHEN '200'.
Note that you can write any code that satisfy your needs.                                                     ****
But in this case, this was wrote as a sample code for reference sake.                                    ****
And you can test it.                                                                                ****
                         SET SCREEN 100.
                         LEAVE SCREEN.
             ENDCASE.
      ENDCASE.
As with customer exits two different views are available:
In the definition view, an application programmer predefines exit points in a source that allow specific industry sectors, partners, and customers to attach additional software to standard SAP source code without having to modify the original object.
In the implementation view, the users of Business Add-Ins can customize the logic they need or use a standard logic if one is available.
USER-EXITS can be used only one time.
       Ex:- if your assigning a USER-EXIT to a project in (CMOD), then you can not assign the same to other project.
These r the following web-sites which may find helpful to u :
http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec079f5db911d295ae0000e82de14a/frameset.htm
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sap-img.com/abap/difference-between-badi-and-user-exits.htm
http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec079f5db911d295ae0000e82de14a/frameset.htm
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://www.easymarketplace.de/userexit.php
*****Pls reward points if u find this useful
cheers,
gyanaraj

User or customer exit for ME21N

Hi all,
I have to make a check before saving the Purchase order thru ME21N. Is there any user exit or customer exit available to do this check? Plz clarify.
Regards,
Steve

Hi
Use the BADI ME_PROCESS_PO_CUST
see the sample code and the doc for BADI
BAdI Name: ZCHECK_PO_LINE_ITEM (Implementation name) PO Account assignment
Definition Name: ME_PROCESS_PO_CUST
Interface Name : IF_EX_ME_PROCESS_PO_CUST
Implementing Class: ZCL_IM_BADIN_ACCOUNT_ASSGN
Method : PROCESS_HEADER
METHOD if_ex_me_process_po_cust~process_header .
DATA : re_data TYPE mepoheader.
*get the item data
CALL METHOD im_header->get_data
 RECEIVING
 re_data = re_data.
re_header = re_data.
IF ( re_data-bsart NE 'ZOC' AND re_data-bsart NE 'ZPC' ).
 IF ( re_data-bsart <> 'ZIC' AND re_data-bsart <> 'UB' ).
 IF re_data-bukrs NE '1001'.
 MESSAGE ID 'ZM_MSG' TYPE 'E' NUMBER '000' WITH 'Use only Sipchem Company'
 'Code for External Procurement'.
 ENDIF.
 ENDIF.
ENDIF.
ENDMETHOD.
Method : PROCESS_ITEM
METHOD if_ex_me_process_po_cust~process_item .
DATA: v_menge TYPE bamng, " PR Quantity
 v_statu. " PR Status
DATA : re_data TYPE mepoitem,
 re_data1 TYPE mepoaccounting,
re_accountings TYPE purchase_order_accountings ,
header TYPE purchase_order_accounting.
*get the item data
CALL METHOD im_item->get_data
 RECEIVING
 re_data = re_data.
IF ( re_header-bsart NE 'ZOC' AND re_header-bsart NE 'ZPC' ).
 IF re_header-bsart EQ 'ZRL'.
 IF re_data-konnr EQ space.
 MESSAGE ID 'ZM_MSG' TYPE 'E' NUMBER '000' WITH 'You cant create a Release order'
 'without a reference to Outline Agreeement'.
 ENDIF.
 ENDIF.
 IF ( re_data-banfn EQ space AND re_data-anfnr EQ space ).
 MESSAGE ID 'ZM_MSG' TYPE 'E' NUMBER '000' WITH 'You can create a Purchase order'
 'only with reference to a PR or RFQ'.
 ENDIF.
 IF re_data-knttp NE 'K' AND re_data-pstyp NE '9' .
 IF syst-cprog EQ 'RM_MEPO_GUI'.
 IF re_data-uebto IS NOT INITIAL OR
 re_data-uebtk IS NOT INITIAL OR
 re_data-untto IS NOT INITIAL.
 MESSAGE ID 'ZM_MSG' TYPE 'E' NUMBER '000' WITH 'You cant change delivery settings'.
 ENDIF.
 ENDIF.
 ENDIF.
ENDIF.
ENDMETHOD.
DEFINING THE BADI
1) execute Tcode SE18.
2) Specify a definition Name : ZBADI_SPFLI
3) Press create
4) Choose the attribute tab. Specify short desc for badi.. and specify the type :
multiple use.
5) Choose the interface tab
6) Specify interface name: ZIF_EX_BADI_SPFLI and save.
7) Dbl clk on interface name to start class builder . specify a method name (name,
level, desc).
Method level desc
Linese;ection instance methos some desc
8) place the cursor on the method name desc its parameters to define the interface.
Parameter type refe field desc
I_carrid import spfli-carrid some
I_connid import spefi-connid some
9) save , check and activateadapter class proposed by system is
ZCL_IM_IM_LINESEL is genereated.
IMPLEMENTATION OF BADI DEFINITION
1) EXECUTE tcode se18.choose menuitem create from the implementation menubar.
2) Specify aname for implementation ZIM_LINESEL
3) Specify short desc.
4) Choose interface tab. System proposes a name fo the implementation class.
ZCL_IM_IMLINESEL which is already generarted.
5) Specify short desc for method
6) Dbl clk on method to insert code..(check the code in AAA).
7) Save , check and activate the code.
Some useful URL
http://www.esnips.com/doc/e06e4171-29df-462f-b857-54fac19a9d8e/ppt-on-badis.ppt
http://www.esnips.com/doc/10016c34-55a7-4b13-8f5f-bf720422d265/BADIs.pdf
http://www.esnips.com/doc/43a58f51-5d92-4213-913a-de05e9faac0d/Business-Addin.doc
http://www.esnips.com/doc/1e10392e-64d8-4181-b2a5-5f04d8f87839/badi.doc
www.sapgenie.com/publications/saptips/022006%20-%20Zaidi%20BADI.pdf
http://www.sapdevelopment.co.uk/enhance/enhance_badi.htm
http://help.sap.com/saphelp_nw04/helpdata/en/04/f3683c05ea4464e10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/e6/d54d3c596f0b26e10000000a11402f/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/c2/eab541c5b63031e10000000a155106/frameset.htm
Now write a sample program to use this badi method..
Look for BBB sample program.
AAA
data : wa_flights type sflight,
it_flights type table of sflight.
format color col_heading.
write:/ 'Flight info of:', i_carrid, i_connid.
format color col_normal.
select * from sflight
into corresponding fields of table it_flights
where carrid = i_carrid
and connid = i_connid.
loop at it_flights into wa_flights.
write:/ wa_flights-fldate,
wa_flights-planetype,
wa_flights-price currency wa_flights-currency,
wa_flights-seatsmax,
wa_flights-seatsocc.
endloop.
BBB
*& Report ZBADI_TEST *
REPORT ZBADI_TEST .
tables: spfli.
data: wa_spfli type spfli,
it_spfli type table of spfli with key carrid connid.
*Initialise the object of the interface.
data: exit_ref type ref to ZCL_IM_IM_LINESEL,
exit_ref1 type ref to ZIF_EX_BADISPFLI1.
selection-screen begin of block b1.
select-options: s_carr for spfli-carrid.
selection-screen end of block b1.
start-of-selection.
select * from spfli into corresponding fields of table it_spfli
where carrid in s_carr.
end-of-selection.
loop at it_spfli into wa_spfli.
write:/ wa_spfli-carrid,
wa_spfli-connid,
wa_spfli-cityfrom,
wa_spfli-deptime,
wa_spfli-arrtime.
hide: wa_spfli-carrid, wa_spfli-connid.
endloop.
at line-selection.
check not wa_spfli-carrid is initial.
create object exit_ref.
exit_ref1 = exit_ref.
call method exit_ref1->lineselection
EXPORTING
i_carrid = wa_spfli-carrid
i_connid = wa_spfli-connid.
clear wa_spfli.
Reward points for useful Answers
Regards
Anji

Executing customer exit variable in dropdown box. in WAD

hi Experts,
i have implemented two customer exit variables for current month and next síx months in a query and it is working well, and the code for customer exit variable is correct.
we have a requirement to use the customer exit variables in dropdown box in web application designer. in the dropdown box in web application designer i used command SET_SELECTION_STATE_SIMPLE in that 'command specific Parameters' i had given the exit variables current month and next six months.but after executing the web application designer and if i drill down the report with current month and next six months it's giving error message .
can anyone please tell me how to implement customer exit variables in web application designer through drop down box. i am using this in bi7 reports.
Regards
Sruthi Reddy

Hi,
Customer Exit Variable in SAP BI : is used to calculata MTD,YTD, and some other calculations.
You can define variables with Customer Exits and then write code in CMOD. See the Article/Blogs in the same
https://wiki.sdn.sap.com/wiki/display/profile/Surendra+Reddy
CHeck the Following Articles.
Customer Exit Variables in BW/BI Reports
Using Customer Exit Variables in BW or BI Reports Part - 1
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/business-intelligence/s-u/using%20customer%20exit%20variables%20in%20bw%20or%20bi%20reports%20part%20-%201.pdf
How to use Customer Exit Variables in BW Reports: Part - 2
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/business-intelligence/g-i/how%20to%20use%20customer%20exit%20variables%20in%20bw%20reports%3a%20part%202.pdf
Using Customer Exit Variables in BW/BI Reports Part - 3
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/10fc4382-afa6-2c10-1380-fa224fe4324f&overridelayout=true
Using Customer Exit Variables in BW/BI Reports: Part - 4
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0fefc77-40e3-2c10-8da3-d4bfcb013387?quicklink=index&overridelayout=true
Calculating the Ageing of the Materials
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/business-intelligence/a-c/calculating%20the%20ageing%20of%20the%20materials.pdf
Thanks
Reddy

Customer Exit implementation

Similar Messages

Maybe you are looking for