Field Exit (Urgent)

Hi Experts,
How can I find table or structure name at field exit include.
I am using a include MV45AFZZ which is for field exit of tcode VA02, Now how can I find table of structure in which data is stored temporarly, so that I can check the same.
With warm regards.
Rajiv singh.

You can get the these tables for another exists while putting a break-point at certain places in the user-exit.
Before that check out the TOP include for that program, and try to find out the structure and internal tables which are being used in that program.
When program stops at the break-point check out your internal tables.
Generally, for SD exists you will find out the transaction data for that perticular transaction in the X structures like XVBAP, XVBRP, XLIPS.
Regards,
Naimesh Patel

Similar Messages

  • Need a document for field exit....urgent

    Can any one please send a document for field exit or have a simple document on how to work on a field exit with screen shots. pls send it ...its urgent
    Thanks and regards
    Nandha kumar R

    Hi,
    A field exit is a type of user exit.
    A user exit is a hook where you can inject your own add-on functionality or behavior to SAP’s standard business applications without having to modify the original applications.
    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.
    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 company’s 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. 
    Field exits (SMOD/CMOD) Questions and Answers
    1. Field exit was created with CMOD, but is not processed when calling the screen.
    -  Since the field exit is not processed until PAI, an action must be triggered on the screen (Return, Save, ...).
    -  Set profile parameter abap/fieldexit to YES and restart the system.
    -  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.
    - Do not work on different application servers since there may be some delay before the field exit is activated.
    - The profile parameter must be set on all or none of the application servers.
    - 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).
    - 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.
    - 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.
    2. How is performance affected by setting abap/fieldexit?
    - If a screen is generated and the profile parameter is set, a check is run on 2 tables (TDDIR, TDDIRS) to see whether a field exit must be generated for the respective field. In practice, the screen load is not generated until the screen is selected after an
    update. The user should not notice any difference because screen generation is very fast.
    3. Can you read the contents of other screen fields in the field exit?
    - In principle, every field exit can store its value in the global variables of the function group (TOP) and hence make them
    available to other field exits. Note here that field exits are always called and not only if an entry is made in the field or if the field is empty. In addition, it is not possible to make any assumptions about the order in which the field exits will be called in the future.
    4. How does the field exit behave on step loop fields ?
    - After the user has entered data, the field exit is called in PAI as often as there are visible fields in the step loop. The system
    variable SY-STEPL is incremented each time. If a new value is assigned to the field, it is displayed in the module between LOOP and ENDLOOP. This module is also called once for each visible step loop line.
    5. Can field exits be debugged ?
    - No. Field exits must be tested separately in the ABAP/4 Development Workbench. For errors which only occur in the screen environment, it is helpful to write interesting variable to the file system using TRANSFER... . These can then be analysed there.
    6. What can you do if the field contents are no longer transported to to ABAP/4.
    - Check whether a value is assigned to the field OUTPUT.
    7. When is the field exit called if a conversion exit is attached to the
       data element ?
    - The field exit is called after the conversion exit. This means that the INPUT field receives the data in the same format as the
    ABAP/4 program also receives it.
    8. Although a global field exit is inactive, a function module is called which does not exist (for example FIELD_EXIT_PROGRAMM_@)
    - This is an error in the kernel which no longer occurs as of 3.0C.  As a temporary measure, it is useful to assign a program and a screen which do not exist to the field exit and then activate the field exit.
    9. Field exit is not visible in CMOD, although created.
    - If you want to create a field exit for a data element, a function module is proposed with the name FIELD_EXIT_. This
    function module must exist for the field exit to work. If you do not create this function module, but do create one with a suffix,
    the data element is not displayed in CMOD.
    10. Field exit is not executed although it is active.
    -  Fields which do not have the 'Input field' attribute usually do not trigger a field exit. The field exit is designed to allow an
    extended input check. It is therefore only called for input fields - even if they are not ready for input at runtime of the         application by LOOP AT SCREEN.
    This rule does not apply, however, if the field is located within a steploop. Here the field will be always activated, even if it is
    invisible.
    - Field exits can only be executed for fields that are directly related tothe dictionary. If the relation is indirect, i.e. via an       ABAP declaration (  LIKE ), no field exit can be executed.
    11. Field exits on check buttons do not work
    -  Field exits are only intended for input fields. As check buttons count as graphical elements, you cannot install field exits on
    them.
    12. Field exits do not work on selection screens
    SAP Field Exits
    From 4.6c onwards, Field exits will no more be supported by SAP.  They removed the function of field exit but they had given lot of flexibility through userexit.
    However, if you still required it, here is how to activate it :-
    First called up transaction  CMOD.
    Then called up transaction PRFB.
    or
    Activation of the field exits and assignment of the dynpros can also be carried out using program RSMODPRF. For this purpose, the program must be started without parameters (input fields remain blank).  If required, new field exits can be created using program RSMODPRF (see the program documentation).
    REFER THIS LINK ALSO.
    defining screen fields using FIELD-SYMBOL
    Thanks,
    Shankar

  • Field Exit Creation -Urgent

    HI Gurus,
                       Has any one created Feild Exit any where in the real time,If so for what Data Element you have created and wht was the senario you hae made use of htat was it for a report .Plz do share that i wud reward points for all useful answers

    Hi,
    Yes we have created a field-exit for data element werks_d. The purpose was to make it obligatory for the user to enter the Plant. Please note that there are some limitations on field-exit e.g. you can not put the debugger on for it. Hence field-exit should be avoided to the extent possible.
    I hope this helps,
    Regards
    Raju Chitale

  • Field Exit or User Exit for Maintenance Order field.

    Dear All,
    we need an field exit or an user exit for order(AUFNR)field in PM module.
    The Client wants that the value of this field should be validated and for certaion condition an error message should be given while saving an invoice for this order.
    Kindly provide the user exit ..
    Its urgent.
    Thansk in advance ..
    regards
    Ajay.

    Implement Field Exit within program   
    For this example I am using dta element 'EBELN' from table EKKO.                   
    Step 1: Execute program 'RSMODPRF', entering the data element of the field
    Step 2:Create function module when prompted, and add you code to the source section using the parameter 'INPUT' as the field value you are checking
    Step 3:      Save and activate Function and execute transaction 'CMOD'.
    Step 4:      Choose option: Goto-> Text Enhancements->Data elements->New DE cust docu.
    Step 3:      Save and activate Function and execute transaction 'CMOD'.
    Step 4:      Choose option: Goto-> Text Enhancements->Data elements->New DE cust docu.
    Step 5:      Enter data element
    Step 6:      Save and activate
    Step 7: Execute program 'RSMODPRF' again but this time leave data element field blank. Step 8: Select the checkbox for the data element you have just created and choose option: Field exit->Activate This will now be active for all instances of this data element, but you can assign specific program and screen combinations by pressing the 'Assign prog./screen' button. You can also change the code you entered in the field exit function module by pressing the 'Edit FM' button.
    regards
    vinod

  • How to link or call two FIELD EXIT

    Hi Friends,
    I've to do a Field exit object for MIGO...and my logic is i've to capture the meory id concept by Export and Import function.So, I heard that I've to create one field exit with Export function and again create under one more field exit to import the memory id from Export.
    I know the logic of Export and Import.But i dont know how to fix it in the function module,means how to create one field exit and call the same under one more field exit.
    Pls do the needful and post me with some good field exit examples for my reference.i.,e How to give codes inbetween Function and End Function. and how to call this field exit with one more field exit for import stmt.
    if u find BADI or USER EXIT is good for MIGO,pls reply with good and correct example functions.
    Thanks and regards
    sankar.
    Edited by: sankar babu on Dec 29, 2007 10:00 AM

    Hello Sankar,
          Just you want to use the functionaly Import and Export , that why you required two Fields Exit in transitation MIGO.
    I suggest MIGO is huge transitation which conver some table like MSEG and BSEG which affect the performance of the program. Better you go with one field Exit . Although there are many Some are attach Below.
    Re: MIGO Enhancement
    Re: How to add field to MIGO Urgent??
    SMOD enhancement MBCF0005 looks promising.
    MBCF0002
    MBCF0005
    MBCF0006
    MBCF0007
    MBCF0009
    MBCF0010
    MBCF0011
    MBCFC003
    MBCFC004
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/QMIMIL/QMIMIL.pdf.
    MB_DOCUMENT_BADI or MB_DOCUMENT_UPDATE
    and these exits: MBCF0002, MB_CF001
    Regards
    Swati Namdeo

  • Warning message in field exit

    Hi All,
    I'd the requirement of giving a warning message for transaction VA01 if user enters some specific order type.
    So I'd created a field exit for AUART for this screen. But i am able to give error message only and found out that warning & info messages can't be given in a field exit.
    Please help me out. Is there any way I can give a warning message in field exit or suggest some other sol. for it.
    Thanks,
    Manu

    Hi,
    Thanks f or your answers, but the issue is that i need to give this message as User enters the details on VA01 screen & presses enters.SO i can't use user exit like move_field_to_Vbak & others.
    Also, using a FM to give pop up message will ultimately make use of statement CALL SCREEN which is not allowed in field exit, i also tried FMs which displays messages normally means not in pop up screen, but again through it also i can only give error messages.
    Please suggets if there is any other option.
    Thanks,
    Manu Parihar

  • Error Message in Field Exit

    Hi All,
    We have a FM which throws an error message. When that is executed in report, it works fine and the error message is displayed.
    We have implemented this FM in FIELD EXIT for PRCTR. But it is not throwing any message. We checked the data, it is fine.
    Can any one know how to solve this??
    Thanks,
    Sreedhar

    Also you need to check whether this is assigned to any program/screen. As you know it will only trigger in the attached program.
    See the documentation of RSMODPRF program.
    Regds
    Manohar

  • Query on Field exits in ECC 6.0

    Hi All,
    We have implemented field exits in SAP R/3 4.6c and now we have upgraded to ECC 6.0.
    I need to know the following information:
    Are field exits obsolete in ECC6.0?
    Can we create new field exits in ECC 6.0 ?
    Going forward, what is the alternative technology/concept to be used - enhancement sports, BADIs etc for field validations(or instead of field exits)?
    Regards
    Shiva

    Hi,
    Though it is obsolete, SAP does not say dont you field exit. You can still use field exit. You can still create field exits.
    Whatever is already existing will definitely work. Creating a field exit is much more simpler and easy than the BADIs or Enhancement points.
    Yes you are right, going forward, you will have to use BADIs or Enhancement points.
    Regards,
    Subramanian

  • How to call an include in a field Exit?

    Hi Guys,
                  i am having a doubt ,How to call an Include in a field Exit function module.
                i wrote as "include zxx_incl." but if i wrote like this in my Field Exit i am getting a Suntax error
    "Recursive INCLUDE nesting in program "ZFLDEXIT_INCL". It contains an
    INCLUDE statement which calls itself or a previously read program
    ("ZFLDEXIT_INCL                           ").
    '                 i am having other doubt while creating an include program does we need to write a 1st statement as include zxx-incl within the same include ZXX_incl? if not i am getting a syntaxt error.
    thanks,
    Gopi.

    Yes, thats the problem.
    Your include is named ZFLDEXIT_INCL and in the first line of that include you probbaly wrote
    include ZFLDEXIT_INCL.
    Delete that, includes don't need a reserved word like programs and reports

  • Field Exit with DYNP_VALUES_UPDATE

    Hello, I am trying to develop a validation in a SAP transaction (XD01) to check some field values and if them are right then fill automatically the rest of the field in the screen, using a Function Modulo and the FM DYNP_VALUES_READ I am able to retrieve the field values correctly, my problem is when a try to fill the rest of the screen's fields with FM  DYNP_VALUES_UPDATE it doesn't work. Does anybody have used this FM? is possible what I am trying to do?
    Thanks in advice for your help.

    Hi Fernando,
    Using Field exit we can't populate multiple fileds, One filed exit is applicable for only one input filed.If you want to implement the
    filed exit for multiple fileds you have to implement the one exit for one filed.
    Regards,
    Mahender Reddy

  • Error while activating field exit

    hi all
    while activating field exit iam getting error
    like system is not configuted for field exit
    solution is Set the abap/fieldexit parameter to YES in the system profile and restart your SAP system
    then in which tcode  i can set the parameter
    thanks in advance

    1)Login to R/3
    2)Tcode RZ10
    3)Select instance profile
    4)click extended maintenance
    5)change
    6)Add parameter
    7)Abap/fieldexit -> save and activate the changes.
    Then restart you r/3 system.

  • While adding custom field in urgent change-Create new field button in AET is not coming

    Dear All,
    we have requirement to add some custom fields in urgent change document. while adding custom fields using AET, create new field button is not coming.
    Thanks in advance. points will be awarded.
    Rahul

    Hi Jignesh,
    Thanks for your valueble inputs, it really helped me to understand the process.
    I checked in Web UI configuration for urgent change document as you mentioned but still that button is not coming.
    In transaction BSP_WD_CMPWB, i have created enh. set: Z_ENHANCEMENT_SET.
    Can you tell what to selelect in application and page popup which comes after selecting Enhance component button. Actually i tried but i am not able to add new record in conf.
    Thanks in advance.

  • Not getting field value in Input field of field exit

    Hi all
       I  am using field exit for data element GWLDT in transaction code IE02. But in this field exit I am not getting the value entered in the field "Begin guarantee date(GWLDT)" in the INPUT field of field exit.How I can get the value in the INPUT field of field exit?
    Regards
    Deepak

    Use this statement in source code.
    output = input.

  • PR creation for 'F" in ME51N, ME52n, the cost center field exit getactivate

    Dear Gurus,
    We have a Cost center Field exit activation, meaning when a PR is generated, the system will validate only for his department cost center. Its working fine
    The issue, when we create PR through ME51n or me52n for Acct Assign "F" here we are going to enter only Work order number and GL number, not cost center. Still this field exit has activation,  here the same error message popup, which suppose not to be.
    So in MM configuration,  i have disabled Cost center field  for acct assignment "F".
    Now when i create a PR for F, for single account assignment, the system will alllow, but if i want to distribute the qty to different work order, the system goes for validation for cost center field exit.
    How to resolve for multiple assignment, how to deactivate the Cost center field exit for this case, its woking fine of Single account assignment (after disable the cost center field for Account Assignment "F")
    Please help me out or any way to do this?
    Regards
    RS
    Edited by: RS on Sep 14, 2009 7:40 AM

    Hi,
    Cross check you have Cost Center field is Hidden for Account Assignment Category A (Asset) in t.code:OME9. Now change Cost Center field as Display for Account Assignment Category A and save.
    Now create a new PO with Account Assignment Category A and find the difference how Cost Center appearing in your PO in “Account Assignment” TAB.
    Regards,
    Biju K

  • Creation of field exit in ECC

    hi friends,
              i am facing a  problem while creating a field exit in ECC. I need to create the field exit on field vkorg and i have created using the program RSMODPERF and the system itself proposing the function module name as 'FIELD_EXIT_VKORG' and i have created the function as well. but when i try to assign program and screen to that field exit then one pop up is coming with three options one is field exit, second one is program, third one is screen. But in first option in f4 help only two options are there one is 0-9, and A-Z. If i select one of that and if i press save then error is coming saying ki FIELD_EXIT_VKORG_1 not exist like that. How to assign program and screen number for the same. Any help will be highly appreciated.
    Thanks a lot.

    check whether u have done the following stepd after coding the Function module..
    After coding, activate the function. And back again to the transaction CMOD.
    The Field Exit will be assigned but still in u2018Inactiveu2019 status and u2018Globalu2019 program
    To make it useful for the specified transaction (program name and the screen number of the destination field), we have to assign the function by giving the u2018Checku2019 , and click u2018Assign prog./.screenu2019 , assign the u2018Program Nameu2019 and the u2018Screen numberu2019 and press u2018ENTERu2019. Then activate.

Maybe you are looking for