How to find CUSTOMER EXIT for a Standard SAP program

Hi
To introduce the techniques of enhancement in standard SAP system. 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.
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.
Any change made to an SAP object in a customer system is called a modification. Customers usually modify their systems for one of two reasons. Either they make changes to the SAP standard in order to adjust the R/3 System to their specific business needs (actual modifications), or they alter individual SAP objects in order to correct an error (as recommended in an SAP error note).
You should only modify the SAP standard if the modifications you want to make are absolutely necessary for optimizing work flow in your company. Be aware that good background knowledge of application structure and flow are important prerequisites for deciding what kind of modifications to make and how these modifications should be designed.
SAP application programmers create SAP enhancements in transaction SMOD using function module exits, menu exits, and screen exits.
Customers are given a catalog containing an overview of existing SAP enhancements. They can then combine the SAP enhancements they want into an enhancement project using transaction CMOD.
SAP enhancements are made up of component parts. These components include function module exits, menu exits, and screen exits. A specific component may be used only once in a single SAP enhancement (this guarantees the uniqueness of SAP enhancements).
Customer enhancement projects consist of SAP enhancements. Each individual SAP enhancement may be used only once in a single customer enhancement program (this guarantees the uniqueness of a customer project).
SAP application programmers preplan function module exits, menu exits, and screen exits for their applications and combine them to create useful enhancements for the R/3 System.
Customers create their own enhancement projects for their systems using SAP enhancements. You can customize the individual components of an enhancement project by creating your own include programs (for function module exits), texts (for menu exits), and subscreens (for screen exits).

Similar Messages

How to find user exit for a perticular screen?

Dear all,
Can some one tell me how to find user exit for a perticular screen?
ex: MC88 screen can we figure out are there any user exit for that screen!!
Regards,
Vj

User exits are built into the Standard SAP code. You just activate them and insert your code into the include programs.
Here is a program that will list the user exits per transaction code. Not perfect, but it may help.
report z_find_user_exit no standard page heading.
tables: tstc, tadir, modsapt, modact,
        trdir, tfdir, enlfdir, tstct.
data : jtab like tadir occurs 0 with header line.
data : hotspot(30).
parameters : p_tcode like tstc-tcode obligatory.
at line-selection.
get cursor field hotspot.
check hotspot(4) eq 'JTAB'.
set parameter id 'MON' field sy-lisel+1(10).
call transaction 'SMOD' and skip first screen.
start-of-selection.
perform get_data.
perform write_list.
      FORM get_data                                                 *
form get_data.
select single * from tstc
              where tcode eq p_tcode.
check sy-subrc eq 0.
select single * from tadir
            where pgmid = 'R3TR'
              and object = 'PROG'
              and obj_name = tstc-pgmna.
if sy-subrc ne 0.
    select single * from trdir
             where name = tstc-pgmna.
    if trdir-subc eq 'F'.
      select single * from tfdir
                     where pname = tstc-pgmna.
      select single * from enlfdir
                     where funcname = tfdir-funcname.
      select single * from tadir
                     where pgmid = 'R3TR'
                       and object = 'FUGR'
                       and obj_name eq enlfdir-area.
    endif.
endif.
select * from tadir into table jtab
             where pgmid = 'R3TR'
               and object = 'SMOD'
               and devclass = tadir-devclass.
select single * from tstct
          where sprsl eq sy-langu
            and tcode eq p_tcode.
endform.
      FORM write_list                                               *
form write_list.
format color col_positive intensified off.
write:/(19) 'Transaction Code - ',
20(20) p_tcode,
45(50) tstct-ttext.
skip.
if not jtab[] is initial.
    write:/(95) sy-uline.
    format color col_heading intensified on.
    write:/1 sy-vline,
    2 'Exit Name',
    21 sy-vline ,
    22 'Description',
    95 sy-vline.
    write:/(95) sy-uline.
    loop at jtab.
      select single * from modsapt
      where sprsl = sy-langu and
      name = jtab-obj_name.
      format color col_normal intensified off.
      write:/1 sy-vline,
      2 jtab-obj_name hotspot on,
      21 sy-vline ,
      22 modsapt-modtext,
      95 sy-vline.
    endloop.
    write:/(95) sy-uline.
    describe table jtab.
    skip.
    format color col_total intensified on.
    write:/ 'No of Exits:' , sy-tfill.
else.
    format color col_negative intensified on.
    write:/(95) 'No User Exit exists'.
endif.
endform.
SMOD, is where you can find the system modifications provided by SAP. CMOD is where you will implement them. If you are looking for all the enhancements provided, then go to CMOD, follow the menu, 'Utilities-->SAP Enhancements'. This will take you to a screen where if you just execute it, you will get all the enhancements provided by SAP.
It is always difficult to find a user exit if all you have is a program name or a transaction code, unless you do a program like Rich suggested. But even there, you will not be able to find user exits that are implemented as sub-routines(also called forms not sapscript forms). Most of the user exits are documented under the corresponding task under IMG structure. So use transaction code SPRO, go to the IMG structure, choose the application area that your program or transaction might be and then you should find a task that talks about enhancements. If you execute that task most often it will take you to CMOD and sometimes to SE38. But all you want to know is there in the documentation attached to the task. Then you can go to CMOD and see which components are there.
Regards,
Amey

How to create customer exit for characteristic variables and for text vars.

hi friends,
can anybody tell me how to create customer exit for characteristic variables and for text variables in bw ides system.
thanks,
sree

Hi,
Please have a look at:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f1a7e790-0201-0010-0a8d-f08a4662562d
Krzys

How to find USER-EXIT for tcode - F110

I am new in USER-EXIT Please help   how to find USER-EXIT for F110
ASAP

Hi,
Enhancement/ Business Add-in            Description
Enhancement
RFFOX074                                Frame for user exit RFFOX074 (in program RFFOCH_U)
RFFOX075                                Frame for user exit RFFOX075 (in program RFFOCH_U)
RFFOX081                                Frame for user exit RFFOX081 (in program RFFOF__T)
RFFOX082                                Frame for user exit RFFOX082 (in program RFFOF__T)
RFFOX100                                Frame for user exit RFFOX100 (in program RFFOUS_T)
RFFOX101                                Frame for user exit RFFOX101 (in program RFFOUS_T)
RFFOX102                                Frame for user exit RFFOX102 (in program RFFOUS_T)
RFFOX103                                Frame for user exit RFFOX103 (in program RFFOUS_T)
RFFOX104                                user exit
RFFOX105                                Frame for user exit RFFOX105 (in program RFFOUS_T)
RFFOX200                                Frame for user exit RFFOX200 (in program RFFONZ_T)
RFFOX210                                Frame for user exit RFFOX210 (in program RFFOAU_T)
RFFOX211                                Frame for user exit RFFOX211 (in program RFFONZ_T)
RFFOX230                                General program for user exit RFFOX230 (in program RFFOJP_L)
RFFOX240                                Enhancement for User Exit 240 (RFFOAT_P)
RFFOX250                                Enhancement for User Exit 250 (RFFODK_E)
RFFOX901                                Framework for user exit RFFOX901 (in program RFFOM100)
RFFOX902                                Framework for user exit RFFOX902 (in program RFFOM100)
FDTAX001                                Enhancement to Transaction FDTA (event after the download)
FEDI0002                                Function exits for EDI DOCS in FI - Incoming pyt adv.notes
FEDI0003                                Function exits for EDI docs in FI - Save PEXR segments
FEDI0004                                Function exits for EDI docs in FI - particular events
FEDI0006                                Function Exits for EDI-docs in FI: Save IDCR Segments
RFFOX003                                Frame for user exit RFFOX003 (in program RFFOM100)
RFFOX041                                Framework for user exit RFFOX041 (in program RFFOBE_I)
RFFOX042                                Framework for user exit RFFOX042 (in program RFFOBE_E)
RFFOX043                                Framework for user exit RFFOX043 (in program RFFOBE_D)
RFFOX061                                Frame for user exit RFFOX061 (in program RFFOCH_P)
RFFOX062                                Frame for user exit RFFOX062 (in program RFFOCH_P)
RFFOX063                                Frame for user exit RFFOX063 (in program RFFOCH_P)
RFFOX064                                Frame for user exit RFFOX064 (in program RFFOCH_P)
RFFOX065                                Frame for user exit RFFOX065 (in program RFFOCH_P)
RFFOX066                                Frame for user exit RFFOX066 (in program RFFOCH_P)
RFFOX071                                Frame for user exit RFFOX071 (in program RFFOCH_U)
RFFOX072                                Frame for user exit RFFOX072 (in program RFFOCH_U)
RFFOX073                                Frame for user exit RFFOX073 (in program RFFOCH_U)
Business Add-in
FI_BSTM_MC_EXIT                         FI Account Statement: Exit from MultiCash Conversion
FI_F110_SCHEDULE_JOB                    F110: Check before scheduling a proposal/update run
No.of Exits:         36
No.of BADis:          2
Arunima

How to change the field length in standard sap program.

Hi All,
How to change the field length in standard sap program.
Urgent
Example:
Text1 type c length 75,
To change :
Text1 type c length 150,
Point will be rewarded..
Thank you,
Vikram.C

If the only solution is to change the sap standard program, simply change the program, it will prompt for an access key. This key can be retrieved in the SAP support portal (service.sap.com) at keys and requests, sccr keys, register object.
Sometimes these actions are outsourced to a competence center, so maybe youre not entitled to do this, in any case ask a resident senior developer for support.
regards, Rob

How to find User exit for PO

Hi
My require ment is system should check for the follwoing PO document type
i have ctreated new document type with respective PR , while creating PO system should check following while saving.(ME21N)
1.PO,
2.incoterm,
3.price,
4.quantity.
So for that i want find user exit for PO. can u plz heip me....

Hi
You can use the BADI ME_PROCESS_PO_CUST
use the methods IM_HEADER and IM_ITEM
if needed check the following PO related exits
Enhancement
MEVME001 WE default quantity calc. and over/ underdelivery tolerance
MM06E001 User exits for EDI inbound and outbound purchasing documents
MM06E003 Number range and document number
MM06E004 Control import data screens in purchase order
MM06E005 Customer fields in purchasing document
MM06E007 Change document for requisitions upon conversion into PO
MM06E008 Monitoring of contr. target value in case of release orders
MM06E009 Relevant texts for "Texts exist" indicator
MM06E010 Field selection for vendor address
MM06E011 Activate PReq Block
MMAL0001 ALE source list distribution: Outbound processing
MMAL0002 ALE source list distribution: Inbound processing
MMAL0003 ALE purcasing info record distribution: Outbound processing
MMAL0004 ALE purchasing info record distribution: Inbound processing
MMDA0001 Default delivery addresses
MMFAB001 User exit for generation of release order
MRFLB001 Control Items for Contract Release Order
AMPL0001 User subscreen for additional data on AMPL
LMEDR001 Enhancements to print program
LMELA002 Adopt batch no. from shipping notification when posting a GR
LMELA010 Inbound shipping notification: Transfer item data from IDOC
LMEQR001 User exit for source determination
LMEXF001 Conditions in Purchasing Documents Without Invoice Receipt
LWSUS001 Customer-Specific Source Determination in Retail
M06B0001 Role determination for purchase requisition release
M06B0002 Changes to comm. structure for purchase requisition release
M06B0003 Number range and document number
MEQUERY1 Enhancement to Document Overview ME21N/ME51N
MELAB001 Gen. forecast delivery schedules: Transfer schedule implem.
MEFLD004 Determine earliest delivery date f. check w. GR (only PO)
MEETA001 Define schedule line type (backlog, immed. req., preview)
ME590001 Grouping of requsitions for PO split in ME59
M06E0005 Role determination for release of purchasing documents
M06E0004 Changes to communication structure for release purch. doc.
M06B0005 Changes to comm. structure for overall release of requisn.
M06B0004 Number range and document number
Business Add-in
ME_PROCESS_REQ_CUST Enhancements for Processing Enjoy PReqs: Customer
ME_PROCESS_REQ Enhancements for Processing Enjoy PReqs: Internal
ME_PROCESS_PO_CUST Enhancements for Processing Enjoy Purchase Order: Customer
ME_PROCESS_PO Enhancements for Processing Enjoy Purchase Order: Intern.
ME_PROCESS_COMP Processing of Component Default Data at Time of GR: Custome
ME_PO_SC_SRV BAdI: Service Tab Page for Subcontracting
ME_PO_PRICING_CUST Enhancements to Price Determination: Customer
ME_PO_PRICING Enhancements to Price Determination: Internal
ME_INFOREC_SEND Capture/Send Purchase Info Record Changes - Internal Use
ME_HOLD_PO Hold Enjoy Purchase Orders: Activation/Deactivation
ME_GUI_PO_CUST Customer's Own Screens in Enjoy Purchase Order
ME_FIELDSTATUS_STOCK FM Account Assignment Behavior for Stock PR/PO
ME_DP_CLEARING Clearing (Offsetting) of Down Payments and Payment Requests
ME_PURCHDOC_POSTED Purchasing Document Posted
SMOD_MRFLB001 Control Items for Contract Release Order
EXTENSION_US_TAXES Extended Tax Calculation with Additional Data
ARC_MM_EKKO_WRITE BAdI: Enhancement of Scope of Archiving (MM_EKKO)
ARC_MM_EKKO_CHECK BAdI: Enhancement of Archivability Check (MM_EKKO)
MM_EDI_DESADV_IN Supplementation of Delivery Interface from Purchase Order
MM_DELIVERY_ADDR_SAP Determination of Delivery Address
ME_WRF_STD_DNG PO Controlling Reminder: Extension to Standard Reminder
ME_TRIGGER_ATP Triggers New ATP for Changes in EKKO, EKPO, EKPV
ME_TRF_RULE_CUST_OFF BADI for Deactivation of Field T161V-REVFE
ME_TAX_FROM_ADDRESS Tax jurisdiction code taken from address
ME_REQ_POSTED Purchase Requisition Posted
ME_REQ_OI_EXT Commitment Update in the Case of External Requisitions
ME_RELEASE_CREATE BAdI: Release Creation for Sched.Agrmts with Release Docu.
ME_DEFINE_CALCTYPE Control of Pricing Type: Additional Fields
ME_CHANGE_OUTTAB Enrich ALV Output Table in Purchasing
ME_CHANGE_CHARACTER Customer-Specific Characteristics for Product Allocation
ME_CCP_DEL_DURATION Calc. of Delivery Duration in CCP Process (Not in Standard)
ME_CCP_BESWK_AUTH_CH BAdI for authorization checks for procuring plant
ME_CCP_ACTIVE_CHECK BAdI to check whether CCP process is active
ME_BSART_DET Change document type for automatically generated POs
ME_BAPI_PR_CREATE_02
ME_BAPI_PR_CREATE_01
ME_BAPI_PO_CREATE_02
ME_BAPI_PO_CREATE_01
ME_BADI_DISPLAY_DOC BAdI for Internal Control of Transaction to be Invoked
ME_ACTV_CANCEL_PO BAdI for Activating the Cancel Function at Header Level
MEGUI_LAYOUT BAdI for Enjoy Purchasing GUI
ME_CHECK_ALL_ITEMS Run Through Items Again in the Event of Changes in EKKO
ME_COMMTMNT_REQ_RE_C Check of Commitment Relevance of Purchase Requisitions
ME_COMMTMNT_REQ_RELE Check of Commitment Relevance of Purchase Requisitions
ME_COMMTMNT_PO_REL_C Check for Commitment-Relevance of Purchase Orders
ME_COMMTMNT_PO_RELEV Check for Commitment-Relevance of Purchase Orders
ME_COMMITMENT_STO_CH BadI for checking if commitments for STOs are active
ME_COMMITMENT_RETURN Commitment for return item
ME_CIP_REF_CHAR Enables Reference Characteristics in Purchasing
ME_CIP_ALLOW_CHANGE Configuration in Purchasing: Changeability Control
ME_CIN_MM06EFKO Copy PO data for use by Country version India
ME_CIN_LEINRF2V BADI for LEINRF03 excise_invoice_details
ME_CIN_LEINRF2R BADI for CIN India - Delivery charges
ME_CHECK_SOURCES Additional Checks in Source Determination/Checking
ME_CHECK_OA Check BAdI for Contracts
Reward points for useful Answers
Regards
Anji

Customer exit for Custominzing standard BSP applications?

Hello everyone,
I'm getting start in BSP applications and the only thing that I need to do at the moment is to write a LOG in a table when user goes to a Purchase Order detail view, print or download.
Is there any way to insert a code in the standard BSP application, like an exit?
Thanks!

Hi Regis,
Where do you want to put your customer exit on ?
Do you have a specific BSP application in mind ?
Usually, people code their own BSP applications, that is why you don't find customer exit. It is only relevant for standard code.
About the aspect of writing a log it is more pure ABAP-oriented so you might find a better audience in the ABAP programming forum.
Best regards,
Guillaume

How to find user exit for the transaction PBAW

Dear Freinds
In Recruitment ....PBAW(Job Advertisements--when we execute the
transaction PBAW ...we can find create Advertisement... > here will create posting
in this screen i have to add a field Status . could you please let me know how
i can add.. Is there any user exit through which i can add a field or there is any way...
as it is standard..
regards
Vamsi.

Hello Vamsi,
This might be of help. It is a program to find user exits based on transaction codes. Just install it on your sandbox and see if it works for you.
http://www.erpgenie.com/abap/code/abap26.htm
KR,
Peter Linn

How to find user exit for XK01/XK02/MK01/MK02/FK01/FK02

I am working on an outbound interface and sending data from SAP to external syatem. I need to send the new supplier is created or modified data (transaction XK01/XK02/MK01/MK02/FK01/FK02) an user-exit is called to check which fields had been maintained / modified.
Can you please help me in identifying how do i find the user exit for the above transactions.
Thanks and regards
Amol S

Hi,
If you need to find out the user-exits for the transaction which you have listed.
you can goto T code SE85 under Enhancements -> Customer Exit -> type in the package name for the tcode you are looking you would get the availlabel exits for the following tcode.
and smod test those exits.
Regards,
Ranjith Nambiar

How to find user exits for a specific field

hi,
 How can we find a user exit for a specific fields .
as i know Three ways to search user-exits
1. SE80 look includes in a packages with name user-exits
2. by zreport which will fetch user-exit in a T-CODE
3. SMOD
but what if we have to find a user-exit for particular field for e.g bupla(bussiness place) in MIRO.
Please suggest me.
Thanks and Regards ,
Rahul Singh.

Hi Rahul,
Here is the procedure to create field exits.
Step by step procedure for creating Field Exits
There are eight steps to creating a field exit:
Step 1: Determine Data Element
Step 2: Go To Field Exit Transaction
Step 3: Create Field Exit
Step 4: Create Function Module
Step 5: Code Function Module
Step 6: Activate Function Module
Step 7: Assign Program/Screen
Step 8: Activate Field Exit
Step 1: Determine Data Element
u2022 Before you can begin adding the functionality for a field exit, you must know the corresponding data element.
Step 2: Go To Field Exit Transaction
u2022 The transaction to create field exits is CMOD.
u2022 You can use the menu path Tools -> ABAP/4 Workbench -> Utilities -> Enhancements -> Project management.
u2022 From the initial screen of transaction CMOD, choose the Text enhancements -> Field exits menu path.
u2022 After choosing this menu path, you will be taken to the field exits screen. From here, you can create a field exit.
NOTE : Even though you use transaction CMOD to maintain field exits, you do not need to create a project to activate field exits.
Step 3: Create Field Exit
u2022 From the field exit screen of transaction CMOD, choose the Field exit -> Create menu path.
u2022 After choosing this menu path, a dialog box will prompt you for the appropriate data element .
u2022 Enter the data element name and click the u2018Continueu2019 pushbutton.
u2022 Now, you will be able to create the function module associated to the data elementu2019s field exit.
Step 4: Create Function Module
u2022 You will automatically be taken to the Function Library (SE37) after entering a data element name and clicking the u2018Continueu2019 pushbutton.
u2022 In the u2018Function moduleu2019 field, a function module name will be defaulted by the system based on the data element specified. This name will have the following convention:
FIELD_EXIT_<data element>
u2022 You can add an identifier (an underscore followed by a single character ).
u2022 The first function module for a data elementu2019s field exit must be created without an identifier.
u2022 To create the function module, click on the u2018Createu2019 pushbutton, choose menu path Function module -> Create, or press u2018F5u2019.
u2022 After choosing to create the function module, you will get the warning: "Function module name is reserved for SAP". This message is just a warning so a developer does not accidentally create a function module in the field exit name range. By pressing u2018Enteru2019, you will be able to go ahead and create the function module.
u2022 Before coding the function module, you will have to specify the function modules attributes -- function group, application, and short text.
Step 5: Code Function Module
u2022 From the function moduleu2019s attributes screen, click on the u2018Source codeu2019 pushbutton or choose the Goto -> Function module menu path to the code of the function module.
u2022 Here you will add your desired functionality for the field exit.
u2022 Remember that field exitu2019s function module will have two parameters -- one importing parameter called "INPUT" and one exporting parameter called "OUTPUT". These parameters will be set up automatically by the system.
u2022 You must remember to assign a value to the OUTPUT field. Even if the value does not change, it must be moved from the INPUT field to the OUTPUT field.
Step 6: Activate Function Module
u2022 After coding the function module, you must remember to activate it.
u2022 Use the Function module -> Activate menu path to activate the function module.
u2022 At this point, you can return to the field exit transaction.
u2022 You should be able to 'green arrow' back to this transaction.
u2022 When you return to the field exit transaction, you will see an entry for the newly created field exit.
u2022 At this point, the field exit is global. That is, it applies to all screens that use a particular data element. On any screen that uses the data element, the corresponding field exit function module will be triggered, once it is active.
u2022 Also, the field exit will not be triggered yet because it is inactive.
Step 7: Assign Program/Screen
u2022 This step is only needed if you want to make a field exit local.
u2022 To make a field exit local, select the field exit and click on the u2018Assign prog./screenu2019 pushbutton.
u2022 In the dialog box , indicate the appropriate program name and screen number.
This information indicates that the field exit is local to the specified screen in the specified program.
u2022 In the dialog box, you determine which function module gets executed for the field exit by specifying the identifier in the u2018Fld. Exitu2019 field.
u2022 If this field is left blank, the function module triggered will be 'FIELD_EXIT_<data element>'.
u2022 If a single-character identifier is entered into the field, the function module triggered will be 'FIELD_EXIT_<data element>_<identifier>'.
Step 8: Activate Field Exit
u2022 The field exit must be active for it to be triggered by the system.
u2022 Activate the field exit by choosing the Field exit -> Activate menu path.
u2022 After assigning the field exit to a change request, its status will change to u2018Activeu2019 and it will be triggered automatically on the appropriate screen(s).
NOTE : In order to activate the field exit the profile parameter abap/fieldexit = YES must be set on all application servers
Execute the transaction SE38 with PROGRAM NAME - RSMODPRF
Then give the Data Element Name for which field you want to create the exit(Just cross check with your field data element) and execute.
then it takes you to SE37 with the function module name FIELD_EXIT_<DATA ELEMENT NAME> and then create the same function module.
and in the coding part, You can write your logic to display the output of that field. and activate it.
once you complete the above,
Again execute SE38 transaction with program RSMODPRF and again click on Execute button without any Data Element Name. Now you select the data element which you have created and click on Assign prog/ Screen button and assign the program name and screen number of the filed and click on the menu Field Exit and Activate.
Hope it helps.
Regards
Radhika
Edited by: Radhika Pande on Nov 26, 2009 7:58 AM

How to write customer exit for the variable

Hi Experts,
I have a requirement to create the variable, the scenaria is like this..
I need to create the variable which gives the period/year values,if yours enters the values 05.2007 then the variable should return the first monthe the year i.e.01.2007.
I hope it can be done by writing the customer exit..but iam unware how to achieve this.
Please explain me step by step and cope for customer exit to done this.
Points will be awarded
Suraj.

hi Suraj,
there should variable sap exit for first month,
for customer exit, check this how to doc for steps
https://websmp210.sap-ag.de/~sapdownload/011000358700002762582003E/HowToDeriveVariableValue.pdf
your code may look like
INCLUDE ZXRSRU01                                                   *
DATA: L_S_RANGE TYPE RSR_S_RANGESID.
DATA: LOC_VAR_RANGE LIKE RRRANGEEXIT.
CASE I_VNAM.
WHEN 'your 1st month variable'.
    IF I_STEP = 2.                                  "after the popup
      LOOP AT I_T_VAR_RANGE INTO LOC_VAR_RANGE
              WHERE VNAM = 'your user input variable'.
        CLEAR L_S_RANGE.
        L_S_RANGE-LOW      = LOC_VAR_RANGE-LOW(4)."low value, e.g.200001
        L_S_RANGE-LOW+4(2) = '01'.
        L_S_RANGE-SIGN     = 'I'.
        L_S_RANGE-OPT      = 'EQ'.
        APPEND L_S_RANGE TO E_T_RANGE.
        EXIT.
      ENDLOOP.
    ENDIF.
ENDCASE.
hope this helps.

How to find proper exit for a particular job !

I have the list of exits for a particular tcode e.g va01....
Now how to find which is the correct one for a particular purpose...i.e while saving the order some thing will happen
thanks

Hi MORONEY ,
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
Regards,
Ramesh.

How to find screen exit for a screen?

Hi,
If you know the transaction, how to find if there is a screen exit exists or not?
Here even I know the screen number also. I have opened it in screen painter. How can I see if there is a screen exit for the screen?
Thank you.

Hii
Screen Exit is nothing but enhancing the screen like creating some more fields, subscreen and so on.
1. Go to the screen>System>Status-->Program (Double
click this program. It will take you to the program.
2. Now, Goto-->Object Directory Entry.
3. Make a note the package name.
4. Now run the transactions SMOD, press F4 and enter the
above noted package, press enter.
5. It will display list of Exits.
6. Now go back to the initial screen SMOD.
7. Specify the exit name here and select the radio button
Components.
8. It will display four group boxes one for FM, second
for Fcodes, thrid for Screen areas and last for
includes.
9. Goto transaction CMOD, create a new project, and
click the button "Enhancement assignments" and
specify your enhancements that you got in SMOD.
10. Now bouble clikc the enhancement, it will take you to editor with some includes starting with Z, double clikc the include you want to edit and proceed.
Screen exit
Regards
Naresh

How to create Object Links For non standard SAP Objects?

Hi all,
I need to create an object link in cvo1n for a non standard SAP object (inspection characteristics) . we have two ways to do this
1. Create a screen for the rquirement by taking the standard screens as reference.
2. Implement badi document_obj.
I need a step by step process to perform both the steps. Sample codes will be helpful.
One more thing is that i need a link in the standard screens of inspection characteristics also. How to get a two way link both in cv01n and in the standard inspection char screen.

hi
Customizing for the Do cument Management , you must maintain the key fields for the SAP objects that you want to link to document info records, by choosing Control Data ® Maintain key fields.
Process
Program two screens for the following module pools for the SAP object that is to be linked additionally:
u2013 SAPLCV00
u2013 SAPLCVIN
The process logic must be according to that of screen 0204 in program SAPLCV00 and must not be changed.
Create the function module OBJECT_CHECK_XXXX (XXXX = name of the SAP object).
If this object can be classified, this function module already exists in the standard system. Otherwise, copy the existing function module OBJECT_CHECK_EQUI (linking of equipment) and change it to suit the new object.
also you can attach the document to PRT also. but it will not show you in dms. This type of attachment is only from otherside.
thanks
nitin
award point if useful

How to find Primary Key for a particular SAP Databse Table?

Hi Guys,
How to find Primary Key and foreign key for Particular SAP Databse table ?for Ex : EKKO , EKPO , EKKN , EKBE , EKBEH , EKET and EKETH.
Thanks,
Srinivas.

Use transaction SE11 to display the table. Put the cursor on the field you want to display the check table and click 'Foreign key' push button (a key with an bottom point arrow), then it will show the check table of the foreign of a field.
Or by just simple double click on the field, a pop-up window of all the attribute (including the foreign key and the check table if exists) will show too.
Please reward point for helpful answer.
Minami

How to find CUSTOMER EXIT for a Standard SAP program

Similar Messages

Maybe you are looking for