Upgrade for Field-Exits

Hi there!.
My customer is asking me to upgrade from 4.6c to ECC 6.0 their field-exits. But I've reading about Enhancement Framework, and for validations made for Field Exits, I would need a SAP Source Key Code to modify the SAP Object and implement the online validations in the screen SAPLCOMD Dynpro 3170.
Has someone tried to work with this new technology ? what could I do for Upgrade this Field Exits?..
Thank you very much for any help!.
Antonio

Hello,
There was a recent discussion onthis topic. Here's the link.
How to reduce input field length
Apart from the name of the Standard Report, I hope you'll find something else of use , too.
Regards,
Anand Mandalika.

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 SAPs 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 companys 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

Alternate solution for Field Exit

Hi All,
Is there any other way to get the functionality of Field Exit?
According to my requirement, I have to populate some values in a table control based on the value entered in a field.
Please tell me a solution for this.
Thanks,
Nandhu.

Hi,
As per your requirement you want to populate some values based on the value of some other field.
You can try for EXITS or if the field from which you want to use the value and the other fields which you want to populate are input fields then you can as well use field exits.
Variables declared globally for storing values in the top include of the function group for field exits can be accessed in other field exits. So you can make use of this functionality.
Thanks.

Steps for field Exit

Hi friends,
For my requirement, I have to use Field Exit.
Can u please provide me steps/ notes for field exit.
Regards.

Hi,
Follow this:
- check data element of your field
- go to SE37 and create a function group of your choice
- run the program RSMODPRF
- type your data element and run it
- the system has to create FM for the field exit. It already suggests the name. Do not change it, just create that one.
- assign your previously created Function Group
- don't change the interface of the FM: input and output must be handled here in order to transport data to/from screen. Here you can check it the field fullfills your requirement
IF input = ...
MESSAGE 'Wrong input' TYPE 'E'. "message type E will restart PAI and field will be input ready again
ENDIF.
"at the end you must use this
output = input. "to transport data
- now using menu BACK function go back to program RSMODPRF and activate your field exit (Fieldexit -> Activate).
- Don't forget to activate your FG and FM too.
This procedure will activate Global field exit, if you want to create a local one, use the same program but Assing a screen and program to that data element.
Regards
Marcin

Alternative for field exit on select-option

Good afternoon,
I know that field exit doesn't work for select-option (SAP Note 29377, point 11) but i want to know if it exists an alternative (I use SAP 4.6, and an update to ECC6 is expected next month).
The field exit would be the best option because we must add exit in many transaction (approximately 100) in little time.
Thanks for your answers,
Best regards,
Anne.

Hi
A) Are there any way for debbuging field exit?
The trick to debug the field-exit is to download the data to a file on application server;
B) How run the field exits on field no editable?
It can't do it, because a field-exit is triggered as soon as a value of the field is changed.
D) Is used the field exit on version >= 4.6C
SAP doesn't support the field-exit from realese 4.7: the field-exit still works on the realese 4.7 and, I suppose, 5 and 6.00: but it doesn't work for enjoy transactions.
Anyway I believe it's better to replace the field-exit with a new solution from realese 4.7
Max

Report name for FIELD EXITS

Dear Friends,
I want to write <b>FIELD EXITS</b>. I know there is a standard report given by SAP for this but i dont know the name so can anybody help me?

Hello,
There was a recent discussion onthis topic. Here's the link.
How to reduce input field length
Apart from the name of the Standard Report, I hope you'll find something else of use , too.
Regards,
Anand Mandalika.

Help for field exit

hi friends,
i am new to field exit .i want to know how field exit works,
can any one send me sample code or step-by-step procedure.
plz do the needful.
tnnx.
sonu

Exits are basically the hooks whcih SAP has provided to add your own code. There are two types of Exits:
1. Customer exits: Implemented as Function Modules within z includes. Anybody can change it and no access key is required.
2. User Exit: Implemented as subroutines within includes (any include except y or z includes). You need access for the specific include and then you can any subroutine (user exit) within that Include.
BADIs are the enhanced version of user exits where the same logic is implemented via classes and object (OOP)
Enchancement point is the latest once introduces with ECC6.0 . Not very sure about that but you can change it without any access key.
Please go through the following link which will help you understand the exits in a much better way:
http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec07a25db911d295ae0000e82de14a/content.htm
http://www.sap-img.com/abap/what-is-the-difference-between-smod-and-cmod.htm
http://sap.niraj.tripod.com/id21.html
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm
http://www.sap-img.com/ab038.htm
User Exits.
http://www.erpgenie.com/sap/abap/code/abap26.htm
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sapgenie.com/abap/code/abap26.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
http://www.easymarketplace.de/userexit.php
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sappoint.com/abap/userexit.pdfUser-Exit
customer exits
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f1a7e790-0201-0010-0a8d-f08a4662562d
Menu Exit.
http://www.sappoint.com/abap/spmp.pdf
http://www.sappoint.com/abap/userexit.pdf
http://www.sapdevelopment.co.uk/enhance/mod_sapmenu.htm
http://www.sapdevelopment.co.uk/enhance/enhancehome.htm
USER EXIT
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sapgenie.com/abap/code/abap26.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
http://www.easymarketplace.de/userexit.php
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sappoint.com/abap/userexit.pdfUser-Exit
http://www.sap-img.com/ab038.htm
http://help.sap.com/saphelp_46c/helpdata/en/64/72369adc56d11195100060b03c6b76/frameset.htm
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://expertanswercenter.techtarget.com/eac/knowledgebaseAnswer/0,295199,sid63_gci982756,00.html
Rewards if useful.........
Minal

How to use the method for field-exit to trigger the workflow?

Dear all,
     I want the workflow to trigger , when ever the check box for DELIVERY COMPLETED is checked in ME22N .
     I have developed a method in SE18 for the corresponding field and defined function module SWE_EVENT_CREATE with BOR bus2012 and event CHANGED.
    Now how to use this method to make my workflow to trigger?Shall I create an event in delegated bus2012 and can I call this method?
Thanks and regards,
S.Suresh

Hi
You want to place your method which is defined for particular filed.right?
For that you can go for BADI. First you check whether any badi is getting called form that tcode ME22N. Then to place your method, implement that BADI. So whenever that BADI is getting called, it will call your event. Through Event workflow will be getting triggered.
Regards,
Hemalatha.

Alternatives to Field Exit for executing a transaction?

Hello,
i'm looking for a way to add code to an existing dynpro, so that a double-click on a field executes a different transaction. As far as i know this is not allowed in a field exist. If there's also no BADI-method defined, what else can be used? Is there any other way than changing the current code of the application itself?
TIA!

Hi,
The alternative for field exits after R/3 4.6C has been the enhancement Points...
Check in debugging if there exists an implicit enhancement point in the PAI of the screen,
If so you can add your code to call a new transaction...
Regards
Shiva

Field Exit for VA11 screen ?

Hello Abapers,
I need ur help to find out the field exit available for VA11 screen.
How to find the field exit wht is the procedure?
Thks

Hi Venkateswar,
First you check this link once.,
http://www.****************/Tutorials/ExitsBADIs/MK01/FieldExit.htm
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).
Please find below the step by step procedure for field exit :-
There are eight steps to creating a field exit:
Step 1: Determine Data Element
Step 2: Go To Field Exit Transaction
Step 3: Create Field Exit
Step 4: Create Function Module
Step 5: Code Function Module
Step 6: Activate Function Module
Step 7: Assign Program/Screen
Step 8: Activate Field Exit
Step 1: Determine Data Element
Before you can begin adding the functionality for a field exit, you must know the corresponding data element.
An easy way to determine the data element associated to a particular screen field is to:
Go the appropriate screen.
Position the cursor in the appropriate field.
Press F1 for field-level help.
Click on the Technical info pushbutton (or press F9) on the help dialog box.
On this Technical Information dialog box, the data element will be specified if the field is 'painted' from the ABAP/4 Dictionary.
Step 2: Go To Field Exit Transaction
The transaction to create field exits is CMOD.
You can use the menu path Tools -> ABAP/4 Workbench -> Utilities -> Enhancements -> Project management.
From the initial screen of transaction CMOD, choose the Text enhancements -> Field exits menu path.
After choosing this menu path, you will be taken to the field exits screen. From here, you can create a field exit.
NOTE : Even though you use transaction CMOD to maintain field exits, you do not need to create a project to activate field exits.
Step 3: Create Field Exit
From the field exit screen of transaction CMOD, choose the Field exit -> Create menu path.
After choosing this menu path, a dialog box will prompt you for the appropriate data element .
Enter the data element name and click the Continue pushbutton.
Now, you will be able to create the function module associated to the data elements field exit.
Step 4: Create Function Module
You will automatically be taken to the Function Library (SE37) after entering a data element name and clicking the Continue pushbutton.
In the Function module field, a function module name will be defaulted by the system based on the data element specified. This name will have the following convention:
FIELD_EXIT_<data element>
You can add an identifier (an underscore followed by a single character ).
The first function module for a data elements field exit must be created without an identifier.
To create the function module, click on the Create pushbutton, choose menu path Function module -> Create, or press F5.
After choosing to create the function module, you will get the warning: "Function module name is reserved for SAP". This message is just a warning so a developer does not accidentally create a function module in the field exit name range. By pressing Enter, you will be able to go ahead and create the function module.
Before coding the function module, you will have to specify the function modules attributes -- function group, application, and short text.
Step 5: Code Function Module
From the function modules attributes screen, click on the Source code pushbutton or choose the Goto -> Function module menu path to the code of the function module.
Here you will add your desired functionality for the field exit.
Remember that field exits function module will have two parameters -- one importing parameter called "INPUT" and one exporting parameter called "OUTPUT". These parameters will be set up automatically by the system.
You must remember to assign a value to the OUTPUT field. Even if the value does not change, it must be moved from the INPUT field to the OUTPUT field.
Step 6: Activate Function Module
After coding the function module, you must remember to activate it.
Use the Function module -> Activate menu path to activate the function module.
At this point, you can return to the field exit transaction.
You should be able to 'green arrow' back to this transaction.
When you return to the field exit transaction, you will see an entry for the newly created field exit.
At this point, the field exit is global. That is, it applies to all screens that use a particular data element. On any screen that uses the data element, the corresponding field exit function module will be triggered, once it is active.
Also, the field exit will not be triggered yet because it is inactive.
Step 7: Assign Program/Screen
This step is only needed if you want to make a field exit local.
To make a field exit local, select the field exit and click on the Assign prog./screen pushbutton.
In the dialog box , indicate the appropriate program name and screen number.
This information indicates that the field exit is local to the specified screen in the specified program.
In the dialog box, you determine which function module gets executed for the field exit by specifying the identifier in the Fld. Exit field.
If this field is left blank, the function module triggered will be 'FIELD_EXIT_<data element>'.
If a single-character identifier is entered into the field, the function module triggered will be 'FIELD_EXIT_<data element>_<identifier>'.
Step 8: Activate Field Exit
The field exit must be active for it to be triggered by the system.
Activate the field exit by choosing the Field exit -> Activate menu path.
After assigning the field exit to a change request, its status will change to Active and it will be triggered automatically on the appropriate screen(s).
NOTE : In order to activate the field exit the profile parameter abap/fieldexit = YES must be set on all application servers
Please reward points if helpful.
Cheers,
Swamy Kunche

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.

Error in activating Field exits

Hi...
At the time of activating field exits data element , I am getting the message as " System is not configured for
field exits " . In a default profile I also set the parameter abap/fieldexit = YES & restarts sap logon too.
Plz.. give me the solution ASAP
Thanks in advance
Deepa

Hi Deepa,
refer to this link
Field Exits
re: field exits
hope it helps..
Regareds!

Now a simple question of Field exit.

well, im really very glad because my last post was a success and i can solve de problem!!!!thank you all...
this time i need in the VF01 on one field ('Reference'/Xblnr), when the user press save, to show some popup allowing entry data, so the user may choose some keys from a Ztable that i have to create, and then continue saving.
May i use a field exit for this?what steps shall i follow to activate a field exit and put my code?
Note: there isn't an User exit that appear in the moment i need, the one i asked in my last post doesn't work for this and any of the others finded in ZFindexit. when i'm debugging <b>'perform userexit_pricing_prepare_tkomk' </b>
appeared, is this an User exit? inside this perform i have changed manually while debugging the field i need and the proccess ended OK. how can i activate this exit?
well, i'm sure that someone know the asnwer....
i'll be very glad with the ones who can help me!!!!
and i'll give points in rewards for those who help me as a gratefulness of my part...
i'm waiting your help, thank in advance....

Hi andrew,
you will have a standard program RSMODPRF for field exits.
Execute that program and create a a field exit(function module) for 'XBLNR' giving the data element of XBLNR and number of the field exit as inputs.
There you can write the related code...
Hope this helps you.
Regards,
Vinod.

The way how field exit gets called??????

Hi ALL,
Can any guru tell me how exactally the field exit works.
Senario- I have created field exit on Data element WERKS_EXT for user validation on plant level for T-code VA01.
Issue- I don't have proper user details in Dev. system to test this thing, for ulternative what i m doing is; I am running VA01 by putting brake point inside my Include for field exit to check it is getting called or not?
But the control is not coming to this field exit code and it is creating sales order .
I have checked, it is ACTIVE and GLOBLE for all screens.
So, please tell how exactally the field exit works and how i can test this?
Regards,
Rahul

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. Field exits cant be debugged.
For details on field exits, have a look at below link.
http://www.sap-img.com/abap/field-exits-smod-cmod-questions-and-answers.htm
http://www.sap-basis-abap.com/sapab014.htm
Best Regards,
Vibha
*Please mark all the helpful answers

Problem activating field exit

Dear Friends,
When i try to activate my field exit using program RSMODPRF, the following message appears.....
System is not configured for field exits (see long text)
Message no. ENHANCEMENT032
Diagnosis
The system is configured wrong. Field exit maintenance will have no effect.
System Response
The profile parameter abap/fieldexit is set to YES during screen generation. A screen load is generated that allows you to branch to field exits.
This parameter may only be set in the customer system.
Note: If the parameter has been set, you must check that, for each field, the system branches to the correct corresponding function module during screen generation. For performance reasons, you should not set this parameter during generation unless field exits have actually been created for your system.
Procedure
Set the abap/fieldexit parameter to YES in the system profile and restart your SAP system.
How to solve this problem....
Thanks & Regards,
Sudheer

Hi,
         go thourgh the documentation of the program RSMODPRF..
Short text
Field Exits for Data Elements
Description
Maintenance transaction for creating and activating field exits
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.
Requirements
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.
Questions and answers on field exits
1. A field exit was created with the CMOD and activated, but it does not get executed when the screen is called.
Since the field exit is not executed until DCI, some action must occur in the screen (e.g. press Return, saving....).
Set the abap/fieldexit profile parameter to YES and start the system again.
After the FIELD_EXIT... function module has been activated and the field exit has been activated, the transaction in whose screen the field exit is to be executed must be terminated. The screen is not generated until it is called.
Do not work on different application servers, otherwise there may be a delay before the field exit becomes active.
The profile parameter must be set either on all application servers or on none.
If the field exit is to be active in certain screens only, then you should check whether you have selected the correct program and the correct screen number (Careful with SUBSCREENS Do not rely on the F1 information for the field!
2. How does setting abap/fieldexit affect the performance?
If a screen is generated and the profile parameter is set, then the system checks in 2 tables (TDDIR, TDDIRS) to see whether a field exit has to be generated for the field. In practice the screen load after a Put is not generated until the screen is called. The user will not experience a noticeable delay, since screen generation is extremely fast.
3. Can the contents of other screen fields be read in a field exit?
In principle all fields can be copied to global variables in the TOP or the function group. However, since the order in which the field exits are called is not guaranteed, this possibility should not be used.
4. How does the field exit work in step-loop fields?
After data input to DCI the field exit will be called as many times as fields are visible on the step-loop. The SY-STEPL system variable is incremented each time. If a new value is assigned to be field, then it will be visible in the module between LOOP. ENDLOOP. This module will also be called as many times as there are visible step-loop lines.
5. Can field exits be debugged?
No. Field exits have to be tested in isolation in the development environment. To analyze problems that occur only in the screen environment, the relevant variables can be written to the file system using TRANSFER... and can be analyzed there.
6. What should one do if the field contents are not getting transported to ABAP/4?
Check whether you have assigned a value to the OUTPUT field.
7. When does the field exit get called in the case that there is a conversion exit attached to the data element?
The field exit will be called after the conversion exit. This means that the INPUT field contains the data in the same form as that in which the ABAP/4 program also gets them.
rEGARDS

Upgrade for Field-Exits

Similar Messages

Maybe you are looking for