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.

Similar Messages

  • 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 assign program/screen to a  Field exit in ECC 5.0

    Through program RSMODPRF i have given the dataelement and executed and created the function module and activated it.
    1.Now in my Documentation its given to assign the field exit to a program/screen.How should do it(i meant to go to which transaction and procedure how to do it).
    2.I also want to know whether the field exits can be created for sap's data elements only or even data elements starting with z.
    Plz tell me if anyone knows answers to these.
    Regards
    Sajid

    Hi,
    Just execute RSMODPRF program without any entry in selection -screen,
    then select ur dataelement and then press change and there u can define the program screen no in which u want to do this change to be activated.
    <b>Assign Program/Screen.</b>
    After giving the program name and screen name.. activae it..
    Then it will work for only the program u gave in the dataelement assigning.....
    not for all the programs it uses...
    Cheers,
    Simha.

  • Field exit in ECC 6.0

    Hi experts,
    I am trying to write a field exit for Quantity field (data element: co_menge) in the backflush compnent list of MFBF transaction. What exactly I want to do is that whenever the material entered is of the type FERT then the user must enter a negative quantity, if he fails to do so, he should either get a message or it should automatically be converted to a negative quantity.
    I have used RSMODPRF program to create the field exit and the function module contains the following code (just an example):
    FUNCTION FIELD_EXIT_CO_MENGE_A.
    ""Local Interface:
    *"  IMPORTING
    *"     REFERENCE(INPUT)
    *"  EXPORTING
    *"     REFERENCE(OUTPUT)
    if input > 0.
    message 'fieldexit:' type 'S'.
    output = input * -1.
    endif.
    ENDFUNCTION.
    I need this field exit to be activated only for this screen, and not everywhere this data element is used.
    I have already set the SAP System profile abap/fieldexit parameter to YES.
    Kindly assist.

    Hi,
    Just execute RSMODPRF program without any entry in selection -screen,
    then select ur dataelement and then press change and there u can define the program screen no in which u want to do this change to be activated.
    <b>Assign Program/Screen.</b>
    After giving the program name and screen name.. activae it..
    Then it will work for only the program u gave in the dataelement assigning.....
    not for all the programs it uses...
    Cheers,
    Simha.

  • Using Field Exit for a field in table KNA1

    Hi everyone,
    I am working on a ticket, the problem is we have a field called STRAS in table KNA1 which holds the address of the customer but now we want to increase the length of this field from 35 charachters to 55 due to some business requirement. SO my question is if this can be done using Field Exit and if yes.. can you please tell me how as I have never used Field exits.
    Thanks,
    Rajeev

    Hi,
    Using field exit, you can only validate the data entry for the field (either globally or on a particular screen field)
    This is usually done by implementing the field exit for the data element corresponding to the field(in your case STRAS_GP)
    Hence you cannot increase the length of the field using the concept of the field exits...
    Please note that after SAP R/3 4.6c, SAP has stopped the creation of field exits and there will be no support for any new ones created.
    Regards
    Shiva

  • Is there any BADI or any other alternate in ECC for the Field exits

    Hi guys,
    Is there any BADI or any other alternate in ECC for the Field exits:
    FIELD_EXIT_BP_VERS_Z
    FIELD_EXIT_BP_VERSION

    Hi,
    If you are aware that these are the field exit funciton modules that get created when you create a field exit for the corresponding data element.
    Hence there will not be any replacement for this FM, But you need to find where the data element is triggering(the tcode) and check in debugging if there is any BADI/Enhancement Point.
    Hence check for which data element the FM belong to using the program RSMODPRF and check if they are globally activated, then they trigger on all the screen/transactions..(Tedious to replace with BADi/Enhancemnet points everywherre)
    If the field exit is activated for screens, check to which transaction the screens belong to and then check for enhancement point or badi that trigers on the screen..
    Hope this helps
    Regards
    Shiva

  • Field exit creation

    i want to change the logic in wchi Field exits allow you to create your own programming logic for any data element
    but when i create afield exit i did't found field exit  in menu of text enhance ment in ECC6 version what i can do to create afield exit  with module   field_exit_<dataelement name>_<0-9 A-z>

    Hi,
    The only problem is assigning the program and the screen through tr. code CMOD. The option was
    appearing in 4.6 but In ECC 6.0, it is not there.
    This is the main issue.
    i think it will helpful for you.

  • 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

  • Field Exit for Batch Input creation from LSMW

    Hi all,
    I am having problems getting a field exit to work for validation of user id in the "Create Batch Input Session" step of LSMW.
    Program: /SAPDMC/SAP_LSMW_BI_RECORDING
    Screen:  1000
    Data Element: SYUNAME
    Any help would be appreciated.
    Regards,
    Jason
    Message was edited by: Jason Lante

    Field exits are not supported after 4.6 yes, but they still work. I found the reason why my field exit wasn't working; it related to the fact that the field I am applying it to is not directly related to a dictionary object. Meaning I cannot apply a field exit.
    So my question now is what other ways are there to enhance LSMW?
    Regards,
    Jason

  • 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

  • How to know whether a field exit is getting triggered or not??

    HI ,
    We are upgrading a system from 4.6 to ECC, the problem is that, in earlier system field exit was getting triggered but its not getting triggered in ECC, the field exit is active in ECC but still its not getting triggered.
    Field Exit is FIELD_EXIT_SAKNR.
    Please provide some help
    Regards
    Karan Arya

    Hi,
    As part of the extension concept, SAP allows you to install a field exit for each screen field. Similar to the conversion exit, the system branches at the field exit at DCI (DATA COMMUNICATIONS INPUT) to a function module, if the field is an input field and a function code was triggered. The function module must adhere to the following naming convention:
    Prefix: FIELD_EXIT_
    Infix: <Data element name>
    Suffix: _0 to _9 (optional), _A to _Z
    The interface is automatically generated during the creation of the function module, and has 2 parameters:
    Import parameter: INPUT
    Export parameter: OUTPUT
    After a function code has been triggered the contents of the field are made available to the FB via the "INPUT" import parameter. You can edit this and, when changed, make it available to the ABAP/4 processor in "OUTPUT". The input field contents are usually passed on: you can simply write OUTPUT = INPUT.
    If, e.g., you have activated the field exit for the data element 'PROGRAM', then the fields of all the screens, which refer to the data element 'PROGRAM', branch to the function module FIELD_EXIT_PROGRAM. This includes the field 'Program' of the initial screen SAPMS38M0100 in transaction SE38, for example.
    If you do not want the function module to be accessed from all screens, assign particular screens to the data element PROGRAM. By allocating an exit number, it is also possible to branch to other function modules with the corresponding suffix _0 ... _Z.
    Example: You have assigned screen SAPMS38M0100 and exit number 5 to data element 'PROGRAM'. The corresponding field on SAPMS38M0100 branches to FIELD_EXIT_PROGRAMM_5.
    As soon as you activate an exit, the corresponding screens are invalidated.
    Note: Field exits are only taken into account during screen generation if the parameter abap/fieldexit = 'YES' is set in the system profile.
    Requirement
    Set the profile parameter abap/fieldexit = 'YES' before system start.
    Limitations
    The following ABAP statements are not allowed in the function modules of field exits:
    BREAK-POINT,
    CALL SCREEN, CALL DIALOG, CALL TRANSACTION, SUBMIT,
    COMMIT WORK, ROLLBACK WORK,
    COMMUNICATION RECEIVE,
    EXIT FROM STEP-LOOP,
    MESSAGE I, MESSAGE W.
    Note:
    Field exits cannot be edited with the debugger.
    You should not use any external Performs in field exits. The ABAP processor shares the table work areas of externally called programs with those of the first caller. This could lead to errors at field exits that can hardly be analyzed, as field exits are sometimes slipped into the flow of the program at unforeseen events.
    Hope this helps you resolve your issue.
    Regards,
    Jayanth

  • Filed exit in ecc 6.0

    Hi,
    Can we create filed Exit in ECC 6.0
    Please let me know asap as its urgent requiremnt.
    Regards,
    Sunil.k

    Hi
    U should consider the field-exit are not supported from rel 46C by SAP, but u can try to create one by report RSMODPRF.
    Anyway I don't think a trx ENJOY supports the field-exit.
    Max
    Edited by: max bianchi on May 28, 2008 12:01 PM

  • Problem with Field exits

    Hi Gurus
    i have a problem, in MM01/MM02(Basic data1) there is field called Prod.hierarchy(dataelement is prodh_d), for this data element how to create and change Field Exits and how to assign to MM01/MM02 Tcode.
    the code part i have to write is
    1. To validate MARA-PRDHA field length (field exit can handle this). the field length should be 18 char.
    2.Copy the value of MARA-PRDHA to MVKE-PRODH (the code of the field exit above, you can do field-symbol technique to transfer value from mara-prhda to mvke-prodh).
    plz. do the needfull information with all the steps with codeASAP.
    I am using Ecc 6.0 Version.
    Thanks & Regards,
    Sudheer.

    Hello,
    If you want to create a user exit execute report RSMODPRF with out parameters and create the FM to the field you need, and active it.
    But before doing that, check if there is a user exit or badi implementation availavle, it will be a better solution.
    Check for instance, the following:
    USER EXIT
    MGA00001                                Material Master (Industry): Checks and Enhancements
    MGA00002                                Material Master (Industry): Number Assignment
    MGA00003                                Material Master (Industry and Retail): Number Display
    Business Add-in
    BADI_EAN_SYSTEMATIC                     BAdI for Internal Control of EAN Logic
    WRF_DISCONT_PARAMS_I                    BAdI: Parameters in Fashion Discontinuation
    WRF_DISCONT_FACT_E                      BAdI: Follow-Up Actions in Discontinuation
    WRF_DISCONT_CHECKS_I                    BAdI: Scope of Check in Material Reorganization
    MG_MASS_NEWSEG                          User-Specific Fields & Segments in Mass Maintenance
    MATGRP_SKU_UPD                          BAdI for Article Hierarchy Connection
    CDT_CHECK_MATERIAL                      Checks for Existence of a Material in a CDT
    BADI_MM_MATNR                           Modification-Free Archiving Enhancement of MM_MATNR
    BADI_MAT_F_SPEC_SEL                     BAdI for Material Special Field Selection
    BADI_MATNR_CHECK_PVS                    Check Material for Use in iPPE
    BADI_MATERIAL_REF                       Addition of customer-defined default data for material
    BADI_MATERIAL_OD                        Integration of New Objects in Material or Article Master
    BADI_MATERIAL_CHECK                     Enhanced Checks for Material Master Tables
    BADI_GTIN_VARIANT                       User Exit for Customer-Specific GTIN Variant Check
    Hope this helps,
    Dont forget to reward.

  • PO Collaboration : Invoice Creation Type field

    Hello,
    The Invoice Creation Type field in the SNC Web UI is always "Invoice Creation not allowed" irrespective of the settings to the Master Data / Transaction Data.
    Given below are the settings I ve maintained
    ECC System:
    PO -> Item Details -> Invoice Tab:
    Inv. Receipt Indicator - Checked
    GR-Bsd IV - Checked / Unchecked
    SNC System:
    Vaildation Checks - Tried both these settings:
    1. PO_INVOICE_CREATION - Active
        PO_INVOICE_DATA_ASSIGN - Active
        PO_INVOICE_RELATED_TO_PO_OR_ASN - Inactive
    2. PO_INVOICE_CREATION - Inactive
        PO_INVOICE_DATA_ASSIGN - Active
        PO_INVOICE_RELATED_TO_PO_OR_ASN - Active
    Infact, I am not able to see the Invoice tab itself in the PO details screen in SNC Web UI.
    Note : I am using the Orders.Orders05 Idoc for sending the PO from ECC to SNC system.

    Hi Bharath
    Your settings are fine
    Please do the following checks
    If you use IDocs of type ORDERS.ORDER05, SAP SNC can instead read the data for these fields from a reference document, such as a contract, that has previously been transferred via the Core Interface (CIF).
    In your PO you would have referenced a contract/agreement, Please check whether it is CIFed or not
    Also before CIFING do implement these notes
    1053121 & 828912
    Now when you send the ORDERS idoc, The RON xml reads this data and puts in structure
    <FollowUpInvoice>
      <RequirementCode>01</RequirementCode>
      <GoodsReceiptBasedInvoiceIndicator>TRUE</GoodsReceiptBasedInvoiceIndicator>
      <CustomerSelfBillingIndicator>FALSE</CustomerSelfBillingIndicator>
      <ProductTaxationCharacteristicsCode>V1</ProductTaxationCharacteristicsCode>
      </FollowUpInvoice>
    Irrespective, whether you create invoice for ASN or PO, the tab should be visible as Nikhil rightly mentioned
    In SAP SNC , Controlling Invoice Creation for POs is done by FollowUpRequirementCode as mentioned above
    Now since you are using ORDERS, you need to check you SA or Contract in Item Details Tab
    the following fields need to be checked "IR" in both cases and In Header Details Field "Invoicing Party"
    Also during creation of PO, make sure you dont check Unlimited Overdelivery in item delivery tab and even in your reference document.
    Now after implementing above two notes reCIF and try creating PO, It will work
    Please do mention whether you are able to see the above structure in your RON xml in SCM side and what details???
    Best Regards
    Vinod

  • Field Exit For Migo Badi

    Hi to all experts,
    I need to assign F4 help to a headertext field for MIGO tcode . I have searched all the exits but couldnt find field exit for it. What are the different options fulfilling this requirement.Please help me out

    Hi,
        The following are the enhancement/Business Add ins,  Please use the appropriate exit for your requirement
      Enhancement/ Business Add-in            Description
    Enhancement
    MB_CF001                                Customer Function Exit in the Case of Updating a Mat. Doc.
    MBCF0011                                Read from RESB and RKPF for print list in  MB26
    MBCF0010                                Customer exit: Create reservation BAPI_RESERVATION_CREATE1
    MBCF0009                                Filling the storage location field
    MBCF0007                                Customer function exit: Updating a reservation
    MBCF0006                                Customer function for WBS element
    MBCF0005                                Material document item for goods receipt/issue slip
    MBCF0002                                Customer function exit: Segment text in material doc. item
    Business Add-in
    MB_DOCUMENT_UPDATE                      BADI when updating material document: MSEG and MKPF
    MB_DOC_BADI_INTERNAL                    BAdIs During Creation of a Material Document (SAP Internal)
    MB_ME_CSGMT_BADI_SAP                    BAdI: Consignment Processing - Stock Transfer
    MB_MIGO_BADI                            BAdI in MIGO for External Detail Subscreens
    MB_MIGO_ITEM_BADI                       BAdI in MIGO for Changing Item Data
    MB_PHYSINV_INTERNAL                     Connection: Core Inventory and Retail AddOn
    MB_QUAN_CHECK_BADI                      BAdI: Item Data at Time of Quantity Check
    MB_RESERVATION_BADI                     MB21/MB22: Check and Complete Dialog Data
    MB_RESERVATION_SCR                      Screen BAdI for Retrofit DFPS
    MB_RESERVATION_UPCHD                    BAdI for Creation and Changing of Manual Reservations
    MB_RES_BAPI_CHANGE                      BAdI: Execution of Changes to Reservation Fields
    MB_RES_BAPI_CREATE1                     BAdI: Adoption of Customer's Own Fields as Reserv. Fields
    MB_RES_BAPI_DETAIL1                     BAdI: Display of Customer's Own Fields in Reservations
    MB_STOR_LOC_BADI_GTS                    BADI to Check and Change Storage Location (GTS Fct. Only)
    MB_DOCUMENT_BADI_SAP                    BADI for Creation and Changing of a Material Document
    ARC_MM_EBAN_CHECK                       BAdI: Enhancement of Archivability Check (MM_EBAN)
    ARC_MM_EBAN_PRECHECK                    BAdI: Enhancement of Archivability Check (MM_EBAN)
    ARC_MM_EBAN_WRITE                       BAdI: Enhancement of Scope of Archiving (MM_EBAN)
    ARC_MM_EINA_CHECK                       BAdI: Enhancement of Archivability Check (MM_EINA)
    ARC_MM_EINA_WRITE                       BAdI: Enhancement of Scope of Archiving (MM_EINA)
    ARC_MM_INVBEL_CHECK                     BAdI: Enhancement of Archivability Check (MM_INVBEL)
    ARC_MM_INVBEL_WRITE                     BAdI: Enhancement of Scope of Archiving (MM_INVBEL)
    ARC_MM_MATBEL_CHECK                     Prüfung ADD-ON-spezifischer Kriterien für MM_MATBEL
    ARC_MM_MATBEL_WRITE                     Check Add-On-Specific Data for MM_MATBEL
    MB_CHECK_LINE_BADI                      BAdI: Check Line Before Copying to the Blocking Tables
    MB_CIN_LMBMBU04                         posting of gr
    MB_CIN_MM07MFB7                         BAdI for India Version exit in include MM07MFB7
    MB_CIN_MM07MFB7_QTY                     Proposal of quantity from Excise invoice in GR
    MB_DOCUMENT_BADI                        BAdIs During Creation of a Material Document

Maybe you are looking for