DEBUGGING A FIELD EXIT
hi all,
i know there is a way to debbug a background process
from the se50 transaction, isn't?
I need to debbug a filed exit, I've put in it a infinite loop (do. enddo.) but I can't enter in the source code in debbug mode.
Can anyone help me?
thanks
enzo
Hi Enzo,
No, you can't debug a field exit with SM50.
For background jobs, you just select the process with the background job running (will have process type BTC from memory), and then choose menu Process->Debugging.
This will stop the job and throw up a session on your PC in debug mode at the next line of code in the program. You can debug as you like and then hit continue to return the job to its running state.
Cheers,
Brad
Similar Messages
-
Debugging field-exit with the new debugger
Hi everyone,
I could debug a field-exit with the new debugger, but I cannot do it anymore. I chose the options "system debug" and "update debug" in the configuration menu that time but it's not working now.
Before you answer "<b>FIELD-EXIT CANNOT BE DEBUG!</b>", take a look first at the The New ABAP Debugger 7.00 Presentation where it mentions that's possible.
And also I saw a post: Re: activation of field exit for particular sereen
where Ramesh Kashigari said that it's possible too.
Anyone knows How can I configurate the new debbuger for this?Hi Florian,
I agree that it should now be possible. I saw this on a SAP Java Development Day at the start of '04 when NetWeaver 04 was launched.
I saw it being used in the NetWeaver Development Studio.
It seemed very clever indeed. You could debug the Java code then jump to the ABAP debugger when the BAPI is called then jump back into the Java code when the BAPI call is completed. It seemed to work very well and did not have any issues.
Hope this helps.
Kind regards
Colin.:) -
Hi,
I am trying to create a field exit on Outline Agreement Field(KONNR) in ME21N. Can anybody plz guide me how I can debug the Function Module at the time of excuting the Transaction.
Thanks in advance,
Rinku.No.Field exit can not debug. 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.
Check whether you have assigned a value to the OUTPUT field.
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.
regards
vinod -
Debugging Field-Exits - ECC6.0
Hello guys.
A friend said me that in release ECC 6.0, the Debug for Field-exits is possible, however, i don't get debugging same following the steps that he sends me.
Somebody knows how i do this?
Thanks for all.
Hugs.
Danilo CardosoI don't think there is a direct way to debug Field Exit.
Generally, we use the messages, either status or Error to know if everything is fine with one processing block. if that is fine than we remove those messages and put after the next block and so on.
Regards,
Naimesh Patel -
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 -
Hi Gurus,
i have a problem, in MM01(Basic data1) there is field called Prod.hierarchy(dataelement is prodh_d), for this data element how to create Field Exits and how to assign to MM01 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 ASAP.
Thanks & Regards,
Sudheer.You can create a field exit to the data element by running the report RSMODPRF.
You will then have to assign the the program name & screen No. (In this case the program name & screen No. in MM01 transaction.)
You will have to write a field exit for MARA-PRDHA and within that ensure that the field length is 18char.( The input value you read should be of 18 char).
You can read the screen field value by using the fn. module to read the screen values & put that value inside MVKE-PRODH. This can be written in another exit.
Important Things to Note.
1.You cannot debug a field exit.
2. Assign the correct program name & screen no. to activate the field exit.
3. This is written at data element level.
Hope this helps...
Let me know if you need any further details.
Regards
Deepu.
Reward Points if it helps. -
Hi Gurus,
How can we keep a break point in filed exit . can any one help me .
I Kept break point in the functional module(field exit) but when i execute cursor is not stopping at break point.
can any one help me
thanking in advance.
Thanking you,
RajuHi,
The following ABAP statements are not allowed in the function modules of field exits:
BREAK-POINT, " We can not ues this statment
CALL SCREEN, CALL DIALOG, CALL TRANSACTION, SUBMIT,
COMMIT WORK, ROLLBACK WORK,
COMMUNICATION RECEIVE,
EXIT FROM STEP-LOOP,
MESSAGE I, MESSAGE W.
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.
<b>Conclusion is We can not debug the Field Exits</b>
Regards
Sudheer -
Use of field exit for validation of KNTTP in ME51N
Hi All,
I've a client who is still running on SAP 4.6C. There is a requirement to validate the Account Assignment Field KNTTP based on the document type, and if the validation fails, to raise an error message. As there is no standard user exit that I've been able to find for this field, and we don't want to modify standard screens, I've created a field exit against the KNTTP field and generated the FM FIELD_EXIT_KNTTP, and activated it, but it doesn't work.
As this is the first Field Exit I've coded could someone please assist me with understanding the following: in the parameters list is the value of INPUT the value of, in this instance, the KNTTP field and also is it possible to read other screen data within this FM, for example, if the KNTTP value eq 9, can I read the BSART field of the current transaction, and if so, how do I reference it (BSART, EKKO-BSART, MEREQ_TOPLINE-BSART, parameter id BSA, etc)?
Any suggestions on how to debug the process would be greatly appreciated as well.
Any help would be greatly appreciated.
Regards,
SteveDue to lack of assistance, we were unable to pursue this requirement - the users were not happy, but what can you do, huh!
-
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 -
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 RHi,
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 -
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. -
Is it possible to work with Field Exits in R/3 Enterp. Basis 6.20???
How could I work with them?
Yes you can.
SE 38 --> Prog RSMODPRF
http://www.sapdevelopment.co.uk/enhance/fexits.htm
But Have a look at OSS note 29377 as well:
Symptom
Problems and questions concerning field exits
Other terms
FAQ, Q+A, SMOD/CMOD, field exits
Reason and Prerequisites
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).
Solution
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).
Generate the screen on which the exit should be active using SE51. It is possible that it was not correctly generated. If you want to be sure that all screens that use the data element are regenerated, you can transfer Report rsmodfdg from the correction instructions and start it with SE38. The Report uses the affected data element as the input parameter and regenerates all screens that use the data element.
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 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, 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 variables 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 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 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 can lead to an ABAP dump error when function module FIELD_EXIT_<data element name> is called.
This is an error in the kernel which no longer occurs as of Release 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.
Due to performance reasons, the active/inactive indicator is stored in the screenload. This can cause inconsistencies between Source and Load. Generate the affected screen with se51. If you want to be sure that all screens that use the data element are regenerated, you can transfer Report rsmodfdg from the correction instructions and start it with se38. The Report uses the affected data element as the input parameter and regenerates all screens that use the data element.
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_<data_element>. 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 to the dictionary. If the relation is indirect, i.e. via an ABAP declaration (<fieldname> LIKE <dictionary element>), no field exit can be executed.
11. Field exits do not work on selection screens.
Results from the previous item since ABAP-internal fields and never the original Dictionary fields are used on selection screens.
12. Field exists do not work on check buttons.
Field exits are only intended for input fields. As check buttons count as graphical elements, you cannot install field exits on them.
13. How can all screens that use a data element be generated?
If you want to be sure that all screens that use a specific data element are regenerated, you can transfer Report rsmodfdg from the correction instructions into a customer report (e.g. zsmodfdg). The Report regenerates all screens. In this way, you can ensure that active field exits refer to screens and that inactive exits cannot be called on any screen. The Report uses the affected data element as the input parameter. The affected data element is in the name of the exit: FIELD_EXIT_<data element name>.
14. Restriction of usage
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.
Erwan -
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,
RahulField 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 -
Hello
i'm working in ECC 6 and my req is to create a field exit for a data element so as to validate the field before saving ..
i have executed the program 'RSMODRPF' and created the function module and also in CMOD in 'Field exits for data elements' when i'm trying to assign the screen name and no, it is not getting saved. i understand i need to set the system parameter 'ABAP/FIELDEXIT' to 'YES'..
my question is how to set the above system parameter? also am i in the right direction in creating a field exit to validate the field?
Thanks in advanceHi Shekar
<b>Please do not post multiple threads for same topic. We all could see the threads irrespective of where you have posted in ABAP Development section.
</b>
<b>The profile parameter abap/fieldexit should be set to 'YES'. Use transaction RZ11 to check the parameter value.</b>
Please read these threads which discusses the same problem and might be helpful,
problem field exit
Field exits don't work
Debugging Field Exits
Other Links
http://www.sap-img.com/abap/field-exits-smod-cmod-questions-and-answers.htm
Regards
Kathirvel -
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,
SudheerHi,
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
Maybe you are looking for
-
Make PDF portfolio compatible for editing with earlier versions of Acrobat
I've built a PDF portfolio in Acrobat Pro X and then sent it to someone running Reader v9 and they can't edit it (and need to). Is there a way to save the PDF portfolio down so they can edit it? Why does Adobe make this so difficult?
-
How to update my phone is my 3g plan
dear sir i don't have wifi network but i am use 3g data so how can update ios 8.2 on my phone
-
I bought a new computer and copied Itunes Music from a backup hard drive and now I have duplicates of over 2000 songs.( I placed all folders in ITunes Media) How can I mass delete all duplicates or how can I reload all music without getting duplicate
-
I have worked with mozila firefox last 10 years. Now i need work inside Intelbrás, at my space, to see my security cams system, and i can´t because has no compatibility. so, i am using both Mozilla, and, IExplorer to see my remote control cameras usi
-
Error 7 when opening file running LabVIEW 2010 executable
I am using Open/Create/Replace File in LabVIEW 2010 to open a text file. This works fine until I compile the code. I then get Error 7. I have tried paths that look like the following but none work. c:\<directory name>\file.txt c:\<application name.