Are Field Exits Not Recommended ?

Hi everybody
I saw recently a post wich comments that Field-Exits are not more recommended and supported by SAP.
It's that true ?    Why are these not recommended ?
where can i see informatión about that ? so i could justify their use or not.
Thanks for help.
Regards
Frank

Hi Frank,
Its not that you cannot use field exits now. Whatever was delivered by SAP will be supported but no further development will take place on enhancing field exits by SAP. See OSS note 29377. It will clear all your doubts.
It says -
Note                                                                     
Field exits are frozen on the 4.6C maintenance level and are not further 
developed. This means that the existing functionality is kept with all   
restrictions (see also the last item below). Existing exits can be       
further used and are called at runtime as usual.                         
Existing exits can be maintained using program RSMODPRF (run the         
program using transaction SE38). 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).                                                                               
14. Restriction of usage                                                                               
o  Field exit technology was developed for input fields on dynpros  
       and cannot be used for other/new dynpro elements. This means that
       this technology does not offer support for the new ScreenPainter 
       elements such as graphical elements (e.g. checkbuttons,          
       radiobuttons, dropdown listboxes), controls (except for table    
       controls which are supported like a step loop), or selection     
       screens.                                                
Cheers.

Similar Messages

  • Field Exit Not Getting Triggerd

    Hi friends , i ve created filed exit for t-code MB31 for original batch check ,
    the fiedl exit has been activated but it is not getting triggerd.
    Please reply ,
    Thanks and regards ,
    Mahesh
    Message was edited by:
            Mahesh Mogare

    Hi Thomas ,
    Thanks for reply , i ve set the parameter abap/fieldexit is to YES in quality server ,
    and activate my field exit , and it is getting triggerd in quality server , i trnsport the same request in production server , i ve also check the filed exit is in active mode in prodution server , but it is not getting triggered , is it necessary to set the parameter abap/fieldexit is to YES  in production server .
    Please Reply .
    Regards,
    Mahesh .

  • Work area field value not getting populated in table control grid.

    Hi all,
    I am currently facing an issue where I have declared a variable and have fetched the workarea field name in it. To be exact, the variable contains the workarea name whose value I am finally populating to the table control. Now although the workarea name when manually copied and pasted in field name in debugging mode exhibits the value of the it, Im unable to fetch the same value in the variable as I have only the work area name in it. I need the value of the workarea-field to be in the variable.Please provide your valuable suggestions for this issue...
    Regards,
    Edited by: Vishwanath Sreedharen on Jan 2, 2012 3:25 PM

    Hi Nabheet,
    Please consider the below example...
    DATA: l_var(30) TYPE C.
    CONCATENATE 'wa' '-' I_FIELD2-NAME INTO l_var.
    The i_field2-name contains the name of a custom table field CP_CUSTOM_GRP. So now the l_var contains wa_cp_custom_grp.
    Now consider the wa_cp_custom_grp has a value 'BA'.
    Now my issue is the l_var contains wa_cp_custom_grp but not its value(too obvious)... Would like to know whether is there a way through which the value of this wa_cp_custom_grp  'BA' could be populated to the variable l_var...

  • Business Area field should not get translate while doing allocations in co

    Dear All,
    In ecc 6.0 when we will be allocating expenses through assessment and Distribution the system credits sender cost center and debits receiver cost center,the same will be applicable for Business Area also.
    But my client is having plant =business area for which they are making financial statements business area wise.
    The client wants its business area not to get affected by above allocations ,Is there any method of restricting costs to remain in same business area and not getting translated to another business area.
    Example :                    cost center           profit center           business area
    expenses                      1011                   1001                     101
    allocation from cctr to cctr 1012 which is having pctr 1002 and business area 102
    expenses                      1012                   1002                       102
    So my requirement is the system should not update business area 102
    Thanks and regards
    vijay

    Hi Vijay,
    Profit Center is derived basing on Assignments. If you have assigned a Profit Center in the Cost Center Master
    Data, obviously for whatever the postings that take place in that Cost Center, will be posted to Profit Center also
    (Statistical).
    In your case, Cost Center 1011 and 1012 have been assigned to different Profit Centers 1001 and 1002. So,
    conceptually what the system is doing is correct.
    You want to restrict the postings to happen to Business Areas. I suggest you, this is not problem of
    stopping/restricting the transaction postings but You have to restructre your Cost Centers and Profit Centers.
    It's rather a Business Process / Structure change required than technical requirement in the system by restricting
    the postings.
    Pls revert back for further discussion...
    Srikanth Munnaluri

  • 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

  • Change Business area field

    The business area field has not picked up the BA for some documents. Can the business area be input in the field of the already posted document.
    The field status of the BA at GL, Account group, posting key level has been made as optional.

    And most important activate Business Area FS in company code settings (T001)
    Company Code > Enter global parameters
    Cheers
    Hein

  • Field Exits are not working in ECC6

    Hi Friends,
    We upgraded our 4.6C system to ECC6 but after upgradation field exits are not working. What could be the reason.
    We are using GUI version-7.1 and SP-10,Release-6.
    Rewarded,
    Steve

    Hi there,
    Try this link ... it could help you.
    [http://www.sap-img.com/abap/field-exits-smod-cmod-questions-and-answers.htm|http://www.sap-img.com/abap/field-exits-smod-cmod-questions-and-answers.htm]
    If not, give an example.
    I did the same upgrade without problems.
    Best regards.
    Valter Oliveira.

  • Field exit is not working for a user

    Hi,
    We have implemented a field exit in ME12 to change the purchase info record short description. It is working fine for most of the users except for some users. I just wanted to know is there any way we can restrict the field exits based on Authorization
    Did any one faced this kind of issues
    Bhanu

    Hi,
    Reason could be that users are logged on different servers : check that profile parameter abap/fieldexit is set equally in all application servers.
    If it's okay, then you'll find the reason only by tracing 2 users, one which is okay, the other not, doing exactly the same thing. To do that, use SE30 with a variant with "no aggregation", as Olga explains in her blog ([SDN blog: ABAP Runtime Analysis (SE30) - How to analyze ABAP program flow|http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/4847/17050 [original link is broken] [original link is broken] [original link is broken] ]). Then you compare the 2 traces to see from which point execution differs. You can use SAT transaction, available from 7.0, to compare 2 traces far more quickly.
    BR
    Sandra

  • 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

  • Field Exit is not working in ecc6.0

    hi all,
    i have upgraded my system from 4.7 to ecc6.0, there was a field exit 'FIELD_EXIT_QLGO_VM04_A'  in 4.7 for QA32, but problem is that it was working in 4.7 but not working in ECC6.0 while codes are the same. can anyone help me that what shud i do?
    Regards saurabh.
    Edited by: saurabh srivastava on Dec 6, 2008 11:45 AM
    Edited by: saurabh srivastava on Dec 6, 2008 11:57 AM

    Hi
    U can ran the report to manage the field-exit (now I don't remember the name) by SE38 and check if your field-exit is still active and if it's active u can check the system parameter abap/fieldexit by trx RZ10: it has to be set to YES.
    Anyway u should consider the field-exit are not supported by SAP from release 4.70.
    Max

  • Functional Area field not getting populated in the AUFK table

    Hi Friends,
    The table AUFK is the table for Internal Order master data.
    The issue which we are facing is:
    In a particular Order type, the field 'Functional Area' is suppressed in the field status group for the order master data.
    But the cost centers which are maintained in the order master has the functional area field populated with value.
    In the table AUFK, the functional area field is populated for some internal orders and not populated for others. In all cases it should pick the functional area from the cost center which is maintained in the internal order.
    Please guide us about what can be the possible reason(s) for populating the field in some cases while not populating in other cases.
    Thanks a lot in advance for your help.
    Regards,
    Shilpi

    Hi,
    maintain the functional area in order master data to ensure 100% functional area is available in AUFK.
    I can't tell you the reason why its sometimes appearing and sometimes not bur FUNC_AREA is not picked from responsible/requesting cost center (from master data).
    If in customizing of internal order order types a "model-order" is assigned with maintained functional area, this func_area is taken if you create a new order for this ordertype.
    Best regards, Christian

  • I need to add check whether 21 fields of a internal table are empty or not.

    Hello,
    I need to add check whether 21 fields of a internal table are empty or not.How can we write a code for the same wand what would be the correct syntax for it.
    I tried entering all the fields in the IF loop with AND condition but its giving syntax error.Perhaps this is because the lenght of the IF condition would be more than the allowed one.

    Hi,
    After the select quiery.
    If not itab is initial.
    Message 'Table is not empty'    type 'I'.
    Endif.
    Regards,
    Jagadish.

  • 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.

  • Depreciation Key field is not in change mode in dep area

    Hello Sap Guru,
    I am facing a problem in my depreciation area. In my depreciation area, field of depreciaiton key is coming in grey mode automaticallly i.e I am not able to enter my dep. key there.
    Please suggest what to do.
    Thanks & Regards
    Deepak Garg

    Hi,
    Where do you want to change the dep key?
    in AS02?
    in OAYZ?
    Go to AO21 and select your screen layout rule 1000 and choose field group rules and for field group dep key, select all check boxes like mnno, Sbno, and copy as maintainance level.
    This will fix your issue.
    Thanks,
    Srinu

  • Field exit showing---not allowed to change cross client customizing

    hi all ,
    when im trying to activate field exit . Its showing---not allowed to change cross client customizing.
    how to correct that.
    thanks in advance.
    sg

    hi SG,
       first and foremost thing while using field exit is, ask your basis person to include the parameter abap/fieldexit = Y in your instance profile.
    Otherwise u can't use the field exits.
    Regards....
    Arun.
    Reward points if useful.

Maybe you are looking for