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 'perform userexit_pricing_prepare_tkomk' 
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.

Similar Messages

A question about field exit

I have created a function module 'FIELD_EXIT_ABREX'.Can I use other field value in this Function Module?How to implement it?

Hi,
Firstly decide the scope : Global or Local to screen.
Global Field Exits are trigerred from all Screens whereas for Screen specific needs the screen to be specified when we go for activating it....
Run program RSMODPRF and specify the field ...
Note : Screen name & data element may be different...so u have to specify Data Element & not Screen field name. Just to remind as this is common pitfall.
Now as u said 'FIELD_EXIT_ABREX' as the Func module created. This gets the screen value of field ABREX in variable INPUT of the Func Mod 'FIELD_EXIT_ABREX' and after processing u can return value throu variable OUTPUT.
You can write u r validations in the FM and do whatever. Just remember the value are lost as soon as this Field Exit is triggerred Again
I hope this should help you for further wwork and any other specific issue do post back ... we'll see dude.
Do reward if this was useful and adds to u r knowledge / solves issue
Regards,

WD Abap - simple question (required field)

hi folks,
quite a simple question i guess.
i have a field marked as required (gets a red asteriks). In the actions i have "Standard" so they should have to do all the validations, but i still can execute the action, i did not find a docu for the behaviour of the "required" features? i thought like in r/3 sapgui appl. a default error messages will be shown?
any ideas?
kind regards,
oliver

Oliver,
I guess there is no difference between WD ABAP and WD Java in this regard, so I will answer from WD Java developer point:
"Required" actually means visual hint to user that input is mandatory. What "mandatory" actually means is application-specific.
For example, in Java string could be either null, or empty, or contains only spaces, or rest. What is mandatory here? Not null? Not empty? Something besides spaces? Ok, even worth, let us assume that we are entering some number (material, order). So string with only zeroes is also "empty".
Hence WD does not handle "required" flag itself, this is left for application developer.
Certainly, some data type constraints like minimal text length, or minimal numeric value may be treated as "required", and here WD works well.
VS

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

Parameter or Field Exit issue

Hi friends,
Im working on Field exit object for MIGO.B4 activating this i've faced some parameter issue and that also has been solved by my Basis consultant.(They set the parameter to "Yes" and restarted the server too.)
Now, i've activated the Field exit data element and inside the FM, i've declared some coding part....the problem is, its not working out fine as what i required exactly.
I want to know either the issue is on still basis consultat side or my program coding part.
FYI
they set the User-defined default status is Yes and still the system default status is "No".(is it the problem???)
*****coding
data: matnr type matnr.
get PARAMETER ID 'MAT' field matnr.
****The logic is read the PO data from the memory ID concept and compare
with the current MIGO quantity.
Pls advise.

Have you activated the field exit.
Go to SE 38 - give the program name as RSMODPRF and Execute.
Then Data Element screen appears. Execute that screen (DO NOT give any Data Element Name here).
Then it will show you the Data element name for which you have created the field exit. Then select that Data Element and then menu FIELD EXIT -> ACTIVATE.
Also click on Assign Prog/Screen button and assign the Program name and screen number for which you are going to use otherwise it will impact on all the screens.
In your coding I could not see and output...You need to give the OUTPUT = < some value> or based on the parameter values you are getting, give your own logic to define that value and assign it to the OUTPUT parameter value. Then you can see the output value.
Hope it helps.
Reward if it is useful.
Thanks,
Srinivas

Simple question: I placed a document in iCoud on my iMac and it appeared on my iOS devices. If I change it on my iPad it changes on my iMac. Now, how do I change it and save it on my iMac so it automatically changes on my iOS devices?

Simple question: I placed a document in iCoud on my iMac and it appeared on my iOS devices.
If I change it on my iPad it changes on my iMac.
Now, how do I change it and save it on my iMac so it automatically changes on my iOS devices?

Welcome to the Apple Community.
I have seen previous versions mentioned in a pop up message before on iCloud.com, but I'm not really sure at all how it would help, as I couldn't get it to do anything.
The best advice I have at this time is to back up your work on your iOS device by regularly saving it to iTunes, if anything goes wrong you can then either load it into the numbers app again on the device or recover it via iTunes on your computer.
My syncs are immediate, I never get chance to see if it works in the background, sorry.

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

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

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 for BSTKD_E

Hello Guru's
             I am facing a unique problem. I have created a field exit for the data element BSTKD_E. I have done the follwoing steps
1) SE38-executed RSMODPRF with data element BSTKD_E.
     i have successfully created the FM for the same. Activated it.
2) Now again i Executed the program RSMODPRF by Keeping   Data element field blank.
   Now the data element BSTKD_E should be visible there, so that i can assign the screen number and program to it.
          but i am not able to see the data element there.
can you put some light into the same, like whats happening?

You should probably post this question in the ABAP forum.

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

Simple Question - Data Import

Hi,
i have a simple question. Is it wise to change our actual import scenarios for input data from systems out of sap to XI?
Today we have the scenario that data from outer systems will send per ftp to a special directory. After that a report will transform the data into a batchinput. The btci will send per rfbibl into the system. Now we have a huge number of such reports. Will it now be better to change to XI, which we use perhaps for MDM?
Xi could take the file from ftp-srever maps the fields an will send per bapi to sap.
Is it a quite simple scenario or is batchinput still the better way.

Hi,
If you have a scenario where you have different file formats , which needs to be converted and then send to different systems based on some conditions , then suggested is XI usage.
However, also if you already have XI installed and running for the MDM system , then you can think of routing all messages through XI. It may make sense to use one system for all routing and data conversion puposes.
Hope this view helps.
Cheerio,
Disha

User Exit, Field Exit

Hi Folks.
I have a question about user exit, or field exit. The question is that if is possible to fill a field with a value, depending on a value entered by the user within the same transaction.
Thanks for your help.
Regards,
Gilberto Li

The field Exit have only INPUT and OUTPUT, but u can validate using another values.
U can:
1- Use the values in that Screen ( Using function GET_DYNP_VALUE)
example:
DATA: l_vkorg TYPE STRING.
CALL FUNCTION 'GET_DYNP_VALUE'
EXPORTING
 I_FIELD = 'RMMG1-VKORG'
 I_REPID = 'SAPLMGD1'
 I_DYNNR = '1004'
CHANGING
 O_VALUE = l_vkorg.
2- Use Parametes ID:
example:
DATAL l_matnr TYPE MARA-Matnr.
GET PARAMETER ID 'MAT' FIELD l_matnr
3- Get Data from tables using SELECT with any of the values that u can get in options 1 or 2.
Example:
DATA:
 l_matnr TYPE MARA-matnr,
 l_mtart TYPE MARA-mtart.
IF INPUT is INITIAL.
GET PARAMETER ID 'MAT' FIELD l_matnr.
SELECT SINGLE MTART
 INTO l_mtart
 FROM MARA
 WHERE MATNR = l_matnr.
Now I have the value l_mtart to validate.
IF l_mtart = 'Z001'
ENDIF.
Greetings

Question on field symbols - DATA MODIFY

hi all, just one simple question...
I already searched forums for help on this q, but got answers which were not of much help..
I am getting data from database table using fetch cursor, into one field symbol fs.this fs is defined type std table.
now in this fs, there is a field counter which I want to change it to a static value 1, al the time.
Can any one give a clear example of how to do ths.. thanks for the help

Hi Neha,
Check this code :
DATA itab LIKE SORTED TABLE OF line WITH UNIQUE KEY col1.
DO 5 TIMES.
line-col1 = sy-index.
line-col2 = sy-index ** 2.
APPEND line TO itab.
ENDDO.
DELETE itab INDEX: 2, 3, 4.
And This...
eg : DELETE itab FROM 3 TO 38 WHERE col2 > 20.
I guess you can add your condition like this...
Regards,
Sai

A simple Question about % in CR Chart!

Hi, I have another simple question.
When i use SQL to storage data and wanna Crystal Report to display the data in chart using %
which data type should i use?
float or string?
and I found when i use 0.12 as 12% in database , It could not display in Crystal Report line chart normally.
What should I do??
Please Help!!!
Thank you VERY MUCH!!!

If you have the datatype as string from your database then try adding the string field as a summary field in chart and select maximum instead of count and if you have them in number format then you can directly select the percentage in chart.
Regards,
Raghavendra

Now a simple question of Field exit.

Similar Messages

Maybe you are looking for