Query regarding screen exits

Hi ppl,
I am looking for a screen exit for tcode MSC3n.
Using SMOD, I found the following enhancements:
BATCHCHK
MBCFC010
SAPLCHVW
SAPLMHD1
SAPLV01D
SAPLV01P
SAPLV01Z
SAPLV1ZE
SAPLV1ZN
But, all these have function exits. There was no screen exit specifically mentioned in any of these enhancements.
Does it mean that there is no screen exit or will these function exits be useful?
Please help.
Regards,
David.

Hi,
My requirement is to remove 2 fields from a subscreen of the tcode MSC3n and replace with 2 custom fields which I have appended in the standard database table. All the fields are from the same database table.
Thanks,
David.
Edited by: David D on Aug 28, 2009 6:59 AM

Similar Messages

  • Query on Screen Exits

    Hi,
    We have a requirement to add the field 'Cost Centre' to the transaction VA01.I believe that the same can be done using a screen exit.
    I would like to know the screen exit that can be used for this purpose and also how to go about doing this.
    Thanks and Regards,
    Nejuma Iqbal

    Hi check the exits available for VA01
    SDTRM001           Reschedule schedule lines without a new ATP check                     
    V45A0001            Determine alternative materials for product selection                 
    V45A0002            Predefine sold-to party in sales document                             
    V45A0003            Collector for customer function modulpool MV45A                       
    V45A0004            Copy packing proposal                                                 
    V45E0001            Update the purchase order from the sales order                        
    V45E0002            Data transfer in procurement elements (PRreq., assembly)              
    V45L0001            SD component supplier processing (customer enhancements)              
    V45P0001            SD customer function for cross-company code sales                     
    V45S0001            Update sales document from configuration                              
    V45S0003            MRP-relevance for incomplete configuration                            
    V45S0004            Effectivity type in sales order                                       
    V45W0001            SD Service Management: Forward Contract Data to Item                  
    V46H0001            SD Customer functions for resource-related billing                    
    V60F0001            SD Billing plan (customer enhancement) diff. to billing plan          
    SDAPO001            Activating Sourcing Subitem Quantity Propagation

  • Regarding screen exit

    Hi Friends,
    I created the sales order using VA01 and enter the payment terms and saved. But mu requirement is when i go through VA02, payment terms field must be in display mode. So, user not able to chage the payment terms value.
    Please give exact solution with Screen exit name and modifications.
    Thanks in advance
    Regards
    Govind.

    Hi,
        The SAPMV45A , 8309 screen is the Additional Data B tab providded by SAP to add your custom fields . In order to capture the data from this custon field you can use
    the user exit MV45AFZZ, USEREXIT_SAVE_DOCUMENT_PREPARE OR
    USEREXIT_SAVE_DOCUMENT depening on your functionality.
    If you include the field MGANR as a part of the VBRK /VBRP structure then these will be available.
    step by step method to implement screen exit:
    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 screen’s flow logic.
    the tcode is cmod...
    1.From the main screen of the Project management transaction, proceed as follows:
    Select Enhancement components and choose Change.
    2.Choose Edit component.
    3.Choose the screen exit and double click on it
    4.Create your subscreen using the Screen Painter.
    5.Design your screen to be added to the standard screen and activate the particular screen and return back to the flow logic .
    6.Choose the PAI and PBO to write down the logic.
    7.Generate your screen and choose Back (the green arrow) to return to the Project management transaction.
    8.Go to the transaction ME22 to view the customer defined screen exit.
    9.Enter the purchase order number and press Enter.
    10.Go to the menu header --> Details.
    11.Purchase number is visible on the standard screen
    Regards

  • Regarding Screen Exits

    Hi all,
    In tcode XD02 i want to add 3 fields (account no. , Branch and Bank Details)..In Standard Screen.
    What is Screen Exit For the XDO2?
    Can Any One Tell the Step by step process to create Screen Exits.
    How To work with  Tcodes CMOD And SMOD?

    Hi,
    Check the link below on screen exits:
    http://****************/Tutorials/ExitsBADIs/ExitsMain.htm
    regards
    Shiva

  • Help regarding screen exit

    Hi,
    Can any body please give me the step by step procedure how to implement the screen exits?I am very thankful if some one gives the screen shots also.I know what's meant by screen exit and how to find that also,but I need some on how to implement that.
    Thanks&Regards
    Mahesh

    use to add screen to standard programqtransction
    for example  : we want to add subscreen
    for item in me22n .
    goto transction -> cmod -> create project
    now add Enhancement ( for example 'MM06E005')
    in the componennt you will see screen exit
    you can choose the one that you need ,
    in our case 111  , and now you have to implement .
    also you have to add structure ci_ekpodb to ekpo
    and open
    EXIT_SAPMM06E_016 - pbo
    EXIT_SAPMM06E_018 - pai
    this is for now ,
    if you have particular question ask for  ,
    for example its enough.

  • Question regarding Screen exits

    Hello Developers,
    Is it necessary for a subscreen area to pre-exist on a standard SAP transaction screen in order to add customer fields to the screen or is it possible to define this within a BAPI? 
    I would like to add customer fields to the screen for txn IE36 (program RIFLET20) but I don't believe it provides for a screen exit. The program does call an exit handler IHSA_LIST_EDITING of class CL_EX_IHSA_LIST_EDITING but the existing methods don't appear to provide the functionality that I need.
    Would this be possible for transaction IE36?
    Thank you for your help,
    Terry

    It is neccessary to have a subscreen area and screen number and program name which are provided by SAP for customer enhancement in Exits.

  • Query regarding screen capture in webdynpro

    Hi
    i needed to use the java.awt.Robot class to perform a screen capture. This is basically used to capture signature which is done on a applet. But hwile i am using it gives me java.awt.headless exception which basically means that i cannot use display devices or certain other features. is there any way get past this.
    Is there any way i can do a screen capture using webdynpro.
    I have few more doubts regarding a application that i need to make. If i am not able to get a solution for this problem i would explain the scenario and probably someone could help me with solution for the same
    thanks
    regards
    Srikumar V

    The problem is that the iframe control is not really supported and should not be used anymore i think.
    But anyways: Since there is actually no out of the box solution, the steps you would hav to go are as follows:
    1. Get Access to the image data (client side)
    I suppose the paint method of one of the AWT/Swing components is overwritten to draw the signature with a pointig device (eg mouse/touch screen)
    in the method public void paint(Graphics g) you have access to the component's Graphics object.
    When the user presses a button in that applet you need to get the latest graphics object of the component and get the bitmap data out of it.
    This is basically the same as using the java robot screenshot, just more elegant.
    But it is important of course, that the navigation to the new view is somehow triggered by the applet so that it can send the request to the servlet before the applet is destroyed.
    2. Send the data to the Server
    I think the best would be to write a servlet to accept the bitmap data from the applet and store it to a database. When the File is uploaded you have to navigate to the next view (using portal navigation or javascript to reload the parent frame)
    Then you need to query that database from Webdynpro to get the file.
    3. Now you would have to use a library like iText to create a PDF file with your image in it.
    This is all not really easy and I can only describe some rough ideas. I cannot think of an easier way to do it right now since client side coding is not supported by webdynpro.

  • Query regarding User Exit

    Hi exps
    Could you please tell me , which user exits get triggered when I save
    Invoice List (T code  : VF22) producing Idoc.
    Also tell me whether the exit EXIT_SAPLVEDF_002 get triggered during this
    process or not ?           
    Let  me know soon
    Regards
    Tulip

    J_3RSINV
    SDVFX001            User exit header line in delivery to accounting
    SDVFX002            User exit for A/R line in transfer to accounting
    SDVFX003            User exit cash clearing in transfer to accounting
    SDVFX004            User exit G/L line in transfer to accounting
    SDVFX005            User exit reserves in transfer to accounting
    SDVFX006            User exit tax line in transfer to accounting
    SDVFX007            User exit: Billing plan during transfer to Accounting
    SDVFX008            User exit: Processing of transfer structures SD-FI
    SDVFX009            Billing doc. processing KIDONO (payment reference number)
    SDVFX010            User exit item table for the customer lines
    SDVFX011            Userexit for the komkcv- and kompcv-structures
    V05I0001            User exits for billing index
    V05N0001            User Exits for Printing Billing Docs. using POR Procedure
    V60A0001            Customer functions in the billing document
    V60P0001            Data provision for additional fields for display in lists
    V61A0001            Customer enhancement: Pricing
    Check with these .

  • Query regarding screen designing

    Hi Experts,
       I am designing a page using  sap  webdynpro  java in which page header should contain 5 buttons as follows.
    Home  Porders  Corders   Inventory    GReciepts
    By clicking GReciepts i should get  4 buttons As follows.
    OFSummery   GReciept   GRDetailList    CBSummery.
    in OFSummery I have to design a FORM.
    which property is required from rootuielement container to reech my requirement.Please help me in this regard.
    thank's@Regard's,
    Prashanth

    For this,
    1. First, in the context create an attribute of type Visibility.
    Steps for this:
    Create a context attribue
    In properties of the attribute you see the property 'type'.
    To the far right of this is a button with three dots, click it, a window pops up.
    Select 'Dictionary Simple Type'.
    Expand 'com.sap.ide.webdynpro.uielementdefinitions'.
    Select 'Visibility'
    Click 'OK'
    2. Bind this attribute to the Visible property of the container.
    3. On the 'Onclick' action of the header row button, set the visibility value of the container to Visible.
    wdContext.current<node>Element().set<Visibilityattribut>(WDVisibility.VISIBLE);
    4.in the onInit(), write:
    wdContext.current<node>Element().set<Visibilityattribut>(WDVisibility.NONE);
    Thanks and Regards,
    Shyam.

  • Regarding Screen exit in vl01n

    Hi All,
    I would like to add one more tab in the t.code Vl01n,Can i use this "DELIVERY_ADDR_SAP " BADI,Some body suggest me how to proceed as i am doing this for the first time.Kindly share your thoughts

    Hi
    If you are enhancing the screen in HEADER level
    Use BADI LE_SHP_TAB_CUST_HEAD
    If you are enhancing the screen in ITEM level
    Use BADI LE_SHP_TAB_CUST_ITEM
    Methods:
    ACTIVATE_TAB_PAGE " Assign the Program name & screen number
    TRANSFER_DATA_TO_SUBSCREEN  " transfer data from table to new tab
    TRANSFER_DATA_FROM_SUBSCREEN " transfer data from new tab to table

  • Screen Exit for LT12

    Hi Folks,
      I need a help regarding Screen Exit for LT12 Tcod.My requirement is to add a screen for Serial Number Keyin for a material and confirm the TO.I try to find an Exit and a Badi where i can put my Custom logic which updats the Serial Number in a Custom 'Z' Table but iam unable to stop at none of the exits .Please help me if any one had worked on this sort of an requirement. I want an Exit/Badi which stops at the time of Save or Confirm TO Ok_code

    hi vamsi,
    check the below link may be helpful for you
    User-Exit in transaction LT12
    if u find it useful plz reward the points
    Regards,
    Naveen

  • Regarding  FB60 screen exit

    hi i want to add a subscreen for fb60 . for this in enhancement what are the screen exits are available?? i have used badi_f040_screen_600,badi_fdcb_subbas01, badi_fdcb_subbas02 and badi_fdcb_subbas03. but these are not get triggered.. any thing is there to find??

    Hi,
    Try one of the following exit:
    RFEPOS00                                Line item display: Checking of selection conditions            
    RFAVIS01                                Customer Exit for Changing Payment Advice Segment Text         
    FARC0002                                Additional Checks for Archiving MM Vendor Master Data          
    F180A001                                Balance Sheet Adjustment                                       
    Ashvender

  • Regarding field and screen exits

    Hi,
         plz. send me the step-by-step procedure to create Field and Screen exit.

    Screen Exits:
    Screen exits are provided by SAP to allow the programmer to add his own sub screen in the already available standard SAP screen. The standard screen will have a sub screen area defined especially for this purpose. The call to this sub screen will also be present already in the standard code.
    For example, there is an enhancement RVEXAKK1 available for foreign trade transactions.
    As you see in the above screen in screen areas block the calling screen, its number, sub screen area and the called screen with its number are defined. Here the main screen 101 in program SAPMV86E is having a sub screen area ZUSATZ and the screen 100 from program SAPLXAKK will be the sub screen for that area.
    It is mandatory for the called screen to be in a function group that starts with X. Here the function group is XAKK.
    Also, if you see the above enhancement, it also has two FM exits. These two FM exits will be used to pass data to & from the sub screen. These FM calls will be in PBO & PAI modules of the main screen. These FMs are also part of the above said function group.
    And the function group will not have that sub screen 100 defined. The programmer can create his own screen with the number 100(or whatever is called).
    Calling of the sub screen.
    sub screen call     in PBO of main screen 101          this module has the FM exit call
    Sub screen call in PAI block of main screen          this module has FM exit call
    Create the screen 101 in program SAPLXAKK from transaction CMOD.
    Double click here to create the screen
    Once screen creation is done, use the two FM exits present in the enhancement to pass data to the sub screen and get data from the sub screen.
    Field Exits
    1. Field exit was created with CMOD, but is not processed when calling the screen.
       o  Since the field exit is not processed until PAI, an action must be
          triggered on the screen (Return, Save, ...).
       o  Set profile parameter abap/fieldexit to YES and restart the
          system. Setting the profile can be done by a BASIS person.
    o     To check if the parameter is set or not use transaction RZ10.
       o  After activating the function module FIELD_EXIT... and the field
          exit, leave the transaction on whose screen the field exit is to
          be executed. The screen is not generated until the transaction is
          started.
       o  Do not work on different application servers since there may be
          some delay before the field exit is activated.
       o  The profile parameter must be set on all or none of the
          application servers.
       o  If the field exit is to only be active on specific screens, check
          whether you chose the correct program and the correct screen
          number (take care with subscreens).
       o  Using SE51 -> Field list, check that the screen field does have a
          reference to a data element. In the name of the field exit use the
          name of the data element and not the field name.
       o  After transport, field exits are marked as active but will not be
          processed. Tip: First try deactivating the field exit once more
          and then afterwards, activate it again.

  • Screen exits - Urgent.

    Hi,
    I am working on screen exits for VA01.
    Can someone tell me how to add table control in a sub screeen at item level in additional data B ?

    Hi
    How to implement screen exit for a SAP standard transaction HOT
    Introduction
    SAP provides standard transactions to enter data into database. But a client may want to maintain some additional information in SAP other than what is provided.
    To make provisions for this, additional screens have to be provided and additional fields must be added into appropriate database table.
    To pave way for this, SAP has provided the option for screen exits. Usually, SAP provides the following:
    An append structure in the database table with the new fields.
    A subscreen area into the standard screen – where the programmer can attach his subscreen of his own program with the new fields.
    A function group under which the new subscreen has to be created with the new fields.
    Function exits to synchronize the PBO and PAI of the standard SAP program with the PBO and PAI of the subscreen – so that data can flow back and forth between the standard SAP program and the program written by the developer for the subscreen. These function modules also exist in the same function group under which the subscreen will have to be developed.
    Finally, a linkage has to be done between the subscreen area of standard SAP screen with the custom subscreen constructed by the developer.
    Typically, SAP provides an enhancement in which the developer can create an append structure, use the function exits to synchronize the PBO and PAI of the standard SAP program and the custom subscreen program, and make the necessary linking( as mentioned above in step 4. But, again, this is not a hard and fast rule. Linking in some case, is also done by configurations.) SAP also usually provides the name of the function group under which the subscreen has to be developed.
    Necessary guidance about implementing a screen exit development is usually available in the Documentation section of the enhancement ( can be availed by transaction SMOD).
    Pre-Requisites
    The developer to work on screen exit should have essential knowledge on the following:
    DDIC concepts, including the knowledge of append structure.
    Concept of SAP Enhancements and implementing them using Projects.
    Concept of function exits.
    Knowledge on Module Pool – including subscreens, Tabstrip controls etc.
    Steps
    Guidelines
    So, a developer can follow the guidelines mentioned below to implement a screen exit to a standard SAP transaction, as and when required:
    Find out the Required Enhancements
    Go to SMOD. Press F4 in the Enhancement field. In the next popup window, click pushbutton ‘SAP Applications’. A list will appear that contains information on all the enhancements, categorized under functional areas. Developer must search for the enhancements relevant to his functional area of interest – for e.g., Purchasing, Asset Accounting, etc.
    Note down the enhancements. Then, come to the initial screen of SMOD and view the documentation of each enhancement to find out which one is required for your development.
    Utilize the Enhancement in a Project
    After you have found one, do as directed in the documentation. Generally, the steps are as follows:
    Create a project using CMOD including your enhancement.
    Create the append structure with new fields.
    Go to the desired function group and create a subscreen with the new fields. Write PBO and PAI for the subscreen, if required.
    Use the function exits in the enhancement to link the PBO and PAI of the subscreen with that of the main SAP program supporting the SAP transaction.
    Maintain necessary linkage between the subscreen area of standard SAP program with the custom subscreen developed along with the custom program name. This can be done in the project (developed by CMOD including the enhancement) or outside as a part of configuration.
    Activate the project.
    Test to ensure that required functionality are met.
    Case Study 1
    Add three new custom fields for Asset master and maintain information for them
    Requirement
    Three fields in the legacy system have to be maintained in Asset master. These fields are:
    Original Asset number – 20 characters
    Location 2 – 15 Characters.
    Model no – 20 characters
    Location 2 should start with ‘L’.
    Pre-Analysis
    Finding out the Enhancement
    As described above, the enhancement is determined. It was found, that enhancement AIST0002 will serve the purpose. It contains the following components (can be viewed by transaction SMOD):
    Exit Type Description EXIT_SAPL1022_001 Function Exit Check of User-Defined Fields when Using Create and Change BAPI EXIT_SAPLAIST_002 Function Exit Transfer Data for User Subscreens in PBO. EXIT_SAPLAIST_003 Function Exit Transfer of User-Defined Fields to SAP Master Data Transactions CI_ANLU Customizing Include Include structure to add new fields
    Studying the Function Exits
    The function module level documentation for the function exits are then viewed from transaction SE37. The documentation clearly laid out for the purpose for their use:
    EXIT_SAPLAIST_002
    Function module Level Documentation
    This function module is called by asset master data maintenance at the start of the dialog. (When changing, it is called after reading of the data from the database; when creating it is called after the transfer of the default values from the asset class and reference asset.) The purpose of the function module is to enable this function group to recognize the master data. For interpreting or controlling master data fields that are important for user fields, it is possible to transfer to global variables at this point, so that they can be recognized when the user subscreens are processed.
    Import Parameters
    Understanding
    This function module is called at the PBO to pass the information retrieved from the database to pass them to the custom subscreen and its underlying program. Import parameter : I_ANLU will be populated with the values for user-defined fields which will be passed to the subscreen program. So, there must be some sort of variable assignment from I_ANLU.
    EXIT_SAPLAIST_003
    Function module Documentation: This function module is called by SAP asset master data maintenance after the screens are processed, but before saving. The purpose of the function module is to transfer fields entered on user sub-screens of SAP asset data maintenance to the database for updating. The export parameter for this function module is:
    Understanding
    This function module will be used to transfer the user entered data in the subscreen fields to the main SAP program, which will then be saved into the database.
    Studying the Documentation of the Enhancement
    The enhancement documentation (as is viewed from the initial screen of SMOD] also supports the idea. Moreover, it informs that we need to develop a subscreen under function group XAIS. This is the function group under which the two function exit modules also exist. So, if the custom subscreen refers to the global data of the function group XAIS, then those values will also be available to these function exits as well.
    Going to SE80 and viewing the function group XAIS helps us to inform that there are three DDIC tables declared for it:
    Deciding the Final course of Action
    After making all the investigations, the final course of action was determined.
    SrlNo Step Justification
    A project has to be created using transaction CMOD where the enhancement AIST0002 will be included.
    Customizing include CI_ANLU has to be created with the custom fields demanded When CI_ANLU will be developed, the custom fields will get appended to the database table ANLU. Also, these fields will be used to create screen fields in the new subscreen.
    A custom subscreen, say, 9000 will be developed under function group XAIS. The screen group for the screen will be ‘CUST’ (or any name). The three custom fields added to table ANLU (by creating CI_ANLU) will be used to create new fields in the screen.
    In the PAI of the subscreen, validation for Location to start with ‘L’ will be added. The subscreen with three new fields has to be developed so that it can be attached to a subscreen area of the asset master screens.
    In the custom include of the function exit module ‘EXIT_SAPLAIST_002’, the following code will be written:-
    ANLU = I_ANLU. I_ANLU is the import parameter of this FM. The value is assigned to the global variable ANLU, referring which the three new subscreen fields are developed. So, data retrieved from database table ANLU will be passed to this FM as I_ANLU by the standard SAP main program. The value will be taken and passed to the global variable of the function group XAIS, so that the three custom fields (referring to ANLU of XAIS) get populated.
    In the custom include of the function exit module ‘EXIT_SAPLAIST_003’, the following code will be written:-
    E_ANLU = ANLU. The changed values in the subscreen fields exist in global variable ANLU for the function group XAIS. This function exit module will pass the data back to the SAP main program as E_ANLU.
    Proper linkage/configuration has to be done so that the new subscreens get linked to the appropriate subscreen area of the Asset master screen. This has to be done – otherwise, the new custom subscreen will not be displayed in the Asset master screens.
    Development
    Creating a Project to include the enhancement
    Go to transaction CMOD and create a project.
    Enter a description for the project. Then, click on the pushbutton ‘Enhancement Assignments’ in the Application Toolbar.
    Enter the name of the enhancement and Save.
    Go to ‘Components’.
    Creating Custom Include for ANLU
    The screen shown below will appear, showing all the enhancement components under the assignment AIST0002. Double-click on the name of the Include Structure to create it.
    Create the include structure with three new fields, as required. Then, save and activate it.
    Develop the subscreen and the program
    Go to transaction SE80. For the function group XAIS, create a new subscreen 9000.
    Create it as subscreen.
    Then, go to the Layout of the screen and create three new fields from Database table ANLU.
    Drag the fields in the screen body and place them.
    Then, save and activate the screen and come back to screen flow editor.
    Create the PAI module to add validation for field “Location 2”, as required .
    Activate the whole function group and come out.
    Write code in the Function Exits to synchronize the programs
    Now, code has to be written in the function modules EXIT_SAPLAIST_002 and EXIT_SAPLAIST_003 so that data flows to and fro between the main SAP program and custom subscreen program. For that, go back to transaction CMOD and change the function exits.
    Write code in the function module EXIT_SAPLAIST_002 called once at the beginning of the transaction:
    Write code in EXIT_SAPLAIST_003 to pass the data from the subscreen to SAP main program.
    Then, activate everything – the whole project and come out.
    Complete the configuration to link the subscreen
    The development portion is complete. Now, linking of the subscreen has to be done with the subscreen area of the main program. In most of the cases, this linking can be done in the enhancement itself. But, here, requirement is a bit different. It is done by configuration using SPRO.
    Assets are created under Asset class. And for each asset class, there is a layout assigned to it. For a layout, there are multiple tab pages assigned to it. And, for each tab page, there are multiple screen groups/field groups assigned.
    Here, the requirement is to create these three custom fields in the tab page ‘General’ of asset master screen ( AS01/AS02/AS03/AS91).
    Determine the Layout
    To achieve this, first of all, we need to find out which layout is assigned to asset class 1000.For that, go to transaction AOLK( information has to be obtained from functional consultant).Select the Asset Class ‘1000’ and click on folder ‘General Assignment of Layout’.
    Here, for Asset class 1000, for all the user groups, tab layout SAP is assigned. Since layout ‘SAP’ cannot be changed, it has to be copied and manipulated to include our screen group. Later, the new layout has to be assigned over here.
    Create new tab layout
    Go to transaction AOLA. Copy the tab layout ‘SAP’ to create another layout, say, YSUB.
    System will copy all the settings and will inform you about that.
    Select your newly created layout and double-click on the folder ‘Tab page titles’.
    You want to put your custom fields in the tab page “General”. So, select this tab page entry and double-click on the folder "Position of Groups".
    Here, all the field groups currently residing in the tab-page “General” are shown. Add an entry for your newly created fields.
    Select the group box from the list. An entry will come with “U” padded with the custom subscreen prepared by you.
    Then, save and come out.
    Assign the new Layout to Asset Class
    Now, go to tcode AOLK and assign tab layout YSUB for asset class 1000.
    Save and come out.
    Test the Exit
    Everything is over. Now, go to transaction code AS01/02/03 or AS91 to deal with an asset of asset class 1000. You will see your new fields added to the screen. Add values to them…save. Then, enter into the tcodes again to see whether the values entered by you are being displayed or not.
    Original Source: ittoolbox.com
    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.
    and you just go through these links also
    Screen exit
    http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
    screen-exits
    Check the following link.
    https://www.sdn.sap.com/irj/sdn/advancedsearch?query=how%20to%20find%20screen%20exits&cat=sdn_all
    Reward points if useful
    Regards
    Anji

  • Query Selection screen field validatoin

    I am testing a query using the RSRT2 transaction and have a query selection screen whose fields i want to create custom validations for. ( which should trigger when check or execute is pressed )
    How can this be achieved ?
    I tried looking for exits but did not find a relevant one.
    Thanks in advance.

    Hello,
    You need to write a routine in SMOD for selection screen validations.
    It will come in i_step = 3. please refer foll code as example:
    The code example is to check whether date is less than or equal to current date. If user enters future date it pop ups saying enter date less than or equal to current date.
    DATA:  LI_VAR like rrrangeexit,
           wa_t_var_range like LI_VAR,
           count type i value 0.
    IF i_s_rkb1d-infocube EQ 'CUBE1' or
       i_s_rkb1d-infocube EQ 'CUBE2'.
    Check whether only one of date variable is entered in variable screen.
    IF I_STEP = 3.
        Read table i_t_var_range into wa_t_var_range with key vnam = 'VARDATE'.
          if wa_t_var_range-low > sy-datum.
            CALL FUNCTION 'RRMS_MESSAGE_HANDLING'
              EXPORTING
                I_CLASS  = 'RSBBS'
                I_TYPE   = 'E'
                I_NUMBER = '000'
                I_MSGV1  = 'Enter date less than or equal to current date'.
            raise again.
          endif.
    ENDIF.
    ENDIF.
    Regards,
    Shashank

Maybe you are looking for