Problem field exit

I abap expert...
I have a problem with field exit for KOB1.
I created field exit for the 'Order' field, in the first screen of kob1.
data element AUFNR, screen 0110 and program RKAEP000.
AUFNR ACTIVE RKAEP000 0110 <- this my.
 SAPLKACB 1007 <- already exist.
 SAPLKACB 2007 <
 In the FM for aufnr:
function field_exit_aufnr.
""Interfaccia locale:
*" IMPORTING
*" VALUE(INPUT)
*" EXPORTING
*" VALUE(OUTPUT)
output = input.
message e000(zo) with 'bella'.<-this message no work
Someone help me? i forget or wrong something?
Thank you

you can check if it is active running RSPARAM program in SE38 transaction . YOu have to find abap/fieldexits in parameters name. There must by 'YES' value in user defined vales column (second one). I dont know if you can do it by yourself it depends of your authorisations. Bu there is one warning. After setting value to yes you have to restart your whole system !!! , to have it working.
BR, Jacek
P>S plese reward helpful answers
have you activated your field exit ?? (chec using RSMODPRF
- program)
ANd opne more question - are you testing it on your develpment system ?? ora after transporting to otehr system ??
Message was edited by: Jacek S³owikowski
Message was edited by: Jacek S³owikowski

Similar Messages

Help in field exits

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 advance

Hi Shekar
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.

The profile parameter abap/fieldexit should be set to 'YES'. Use transaction RZ11 to check the parameter value.
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

Problem with Field Exit

I have created an field exit through a program RSMODPRF. The requirement is that I have to change the type of screen field from CHAR to NUMC. That I have already done, but how to validate the felid if the user enters the character values or how to prevent user not to use character values.

I don't understand your problem. I'm in 4.7 and made small test:
REPORT ztest.
TABLES wlk1.
PARAMETERS p_lfdnr like wlk1-lfdnr.
I even can't type in any characters - that's already handled by GUI!
Field-exits (even with RSMODPRF) will not be available in future release - if possible (and necessary) make your checks in a user-exit.
Regards,
Christian

Problem with Field exits

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

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

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

Field Exits problem in Quality system after trasports

Dear Freinds,
We did Field Exit changes in Developement system and the changes are working perfect when we tested.
Where as we transport the changes to QA(Quality system) the filed exit is not working. We checked the code, and the code was moved to QA. We set the flag for field by sitting Basis guys (field status as YES). Even though field exit changes are not working in QA.
Could you please suggest is there any other settings we have to make sure to work this feild exit in QA...? And in case any manuval settings in QA the same we need to do in prodcution manuvally..
thanks in advance...
Cheers !

the profile parameter should be set on ALL application servers & system should be restarted. If your exits do not work after that, just try to deactivate/activate your exits directly on QA system. It will certainly help.

Field exit problem

hi guys ...
Can anyone help me ,I am unable to activate field exit for data element
dzfbd/t for tcode mir0 .
we want baseln dt to be = mat doc pstng dt ,is there any user exit
which fires on first screen of MIR0 .field exit is not triggering.Any other way to accomplish this will be awarded with good points .
thx.

Hi,
You can use
For imprting
IMPORT Var_1 from memory id 'MEMORY_1' .
For Exporting
EXPORT var_1 to memory id 'MEMORY_1' .
U have to use same memory var to which ur exporting and importing.
Thanks
Chaitanya

How to call an include in a field Exit?

Hi Guys,
              i am having a doubt ,How to call an Include in a field Exit function module.
            i wrote as "include zxx_incl." but if i wrote like this in my Field Exit i am getting a Suntax error
"Recursive INCLUDE nesting in program "ZFLDEXIT_INCL". It contains an
INCLUDE statement which calls itself or a previously read program
("ZFLDEXIT_INCL                           ").
'                 i am having other doubt while creating an include program does we need to write a 1st statement as include zxx-incl within the same include ZXX_incl? if not i am getting a syntaxt error.
thanks,
Gopi.

Yes, thats the problem.
Your include is named ZFLDEXIT_INCL and in the first line of that include you probbaly wrote
include ZFLDEXIT_INCL.
Delete that, includes don't need a reserved word like programs and reports

Field Exit with DYNP_VALUES_UPDATE

Hello, I am trying to develop a validation in a SAP transaction (XD01) to check some field values and if them are right then fill automatically the rest of the field in the screen, using a Function Modulo and the FM DYNP_VALUES_READ I am able to retrieve the field values correctly, my problem is when a try to fill the rest of the screen's fields with FM DYNP_VALUES_UPDATE it doesn't work. Does anybody have used this FM? is possible what I am trying to do?
Thanks in advice for your help.

Hi Fernando,
Using Field exit we can't populate multiple fileds, One filed exit is applicable for only one input filed.If you want to implement the
filed exit for multiple fileds you have to implement the one exit for one filed.
Regards,
Mahender Reddy

Creation of field exit in ECC

hi friends,
i am facing a problem while creating a field exit in ECC. I need to create the field exit on field vkorg and i have created using the program RSMODPERF and the system itself proposing the function module name as 'FIELD_EXIT_VKORG' and i have created the function as well. but when i try to assign program and screen to that field exit then one pop up is coming with three options one is field exit, second one is program, third one is screen. But in first option in f4 help only two options are there one is 0-9, and A-Z. If i select one of that and if i press save then error is coming saying ki FIELD_EXIT_VKORG_1 not exist like that. How to assign program and screen number for the same. Any help will be highly appreciated.
Thanks a lot.

check whether u have done the following stepd after coding the Function module..
After coding, activate the function. And back again to the transaction CMOD.
The Field Exit will be assigned but still in u2018Inactiveu2019 status and u2018Globalu2019 program
To make it useful for the specified transaction (program name and the screen number of the destination field), we have to assign the function by giving the u2018Checku2019 , and click u2018Assign prog./.screenu2019 , assign the u2018Program Nameu2019 and the u2018Screen numberu2019 and press u2018ENTERu2019. Then activate.

Field exit for cmod

Hi,
Field exit was created with CMOD, but is not processed when calling the screen.
Thanks,
Biju

Hi Biju,
Please find below an extract on how to approach the problem
1. The field exit was created with CMOD, but is not processed when the screen is called.
Field exits can be defined only for data elements whose name is shorter than 19 characters. The name of the data element plus the prefix "FIELD_EXIT_" must not exceed the maximum length of a function module name (30).
Since the field exit is not processed until PAI, an action must be triggered on the screen (choose enter, save, and so on).
Set the profile parameter abap/fieldexit = YES and restart the system.
After activating the function module FIELD_EXIT... and the field exit, leave the transaction on whose screen you want to execute the field exit. The relevant screen is only generated when the transaction is called.
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 no 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).
Use transaction SE51 to generate the screen on which the exit should be active. 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 copy the report rsmodfdg from the correction instructions and start it with transaction SE38. The report uses the affected data element as the input parameter and regenerates all screens that use the data element.
Use transaction SE51 and choose 'Field list' to check that the screen field actually has 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 the transport, field exits are marked as active but are not processed. Tip: First try to deactivate the field exit once more and then activate it again.
http://www.saptechies.com/faqs-field-exits-cmod/
Regards
Byju

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

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.

Problem field exit

Similar Messages

Maybe you are looking for