Field Exit Issue

Hi Experts.
Does another code rather than the INPUT parameter, triggers on a field exit ???. i'm trying to validate several values trought GET PARAMETER, EXPORT, IMPORT, but the field exit does'nt validate that code, Just the input parameter.
Hope you can help me.
Regards.

Hi
Ensure that profile paramater is set
abap/fieldexit = YES (or TRUE ?? -> not sure)
(Ask your BASIS Person to help you out).
Regards
- Atul

Similar Messages

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

Warning message in field exit

Hi All,
I'd the requirement of giving a warning message for transaction VA01 if user enters some specific order type.
So I'd created a field exit for AUART for this screen. But i am able to give error message only and found out that warning & info messages can't be given in a field exit.
Please help me out. Is there any way I can give a warning message in field exit or suggest some other sol. for it.
Thanks,
Manu

Hi,
Thanks f or your answers, but the issue is that i need to give this message as User enters the details on VA01 screen & presses enters.SO i can't use user exit like move_field_to_Vbak & others.
Also, using a FM to give pop up message will ultimately make use of statement CALL SCREEN which is not allowed in field exit, i also tried FMs which displays messages normally means not in pop up screen, but again through it also i can only give error messages.
Please suggets if there is any other option.
Thanks,
Manu Parihar

PR creation for 'F" in ME51N, ME52n, the cost center field exit getactivate

Dear Gurus,
We have a Cost center Field exit activation, meaning when a PR is generated, the system will validate only for his department cost center. Its working fine
The issue, when we create PR through ME51n or me52n for Acct Assign "F" here we are going to enter only Work order number and GL number, not cost center. Still this field exit has activation, here the same error message popup, which suppose not to be.
So in MM configuration, i have disabled Cost center field for acct assignment "F".
Now when i create a PR for F, for single account assignment, the system will alllow, but if i want to distribute the qty to different work order, the system goes for validation for cost center field exit.
How to resolve for multiple assignment, how to deactivate the Cost center field exit for this case, its woking fine of Single account assignment (after disable the cost center field for Account Assignment "F")
Please help me out or any way to do this?
Regards
RS
Edited by: RS on Sep 14, 2009 7:40 AM

Hi,
Cross check you have Cost Center field is Hidden for Account Assignment Category A (Asset) in t.code:OME9. Now change Cost Center field as Display for Account Assignment Category A and save.
Now create a new PO with Account Assignment Category A and find the difference how Cost Center appearing in your PO in “Account Assignment” TAB.
Regards,
Biju K

Messages in field exits

Hi all,
I need to perform some validations over a field and I am doing it on a field exit. The requirement is that I have to inform the user if, after the validation, the exit changes the value of the field.
Does anyone has a hint for that?
Thanks in advance!
Best Regards,
Ezequiel Martin

Well, I have changed the strategy because it was too difficult and complicated because I had to perform several other validations using other fields, and in case those other fields were changed, validate everything again.
After all, I have put al the required validations in a user exit and issued an error message proposing a new value for the field so the user will have to change it manually.
This is, by far, the simplest solution I found.
Thank you all for your time and help!!
Cheers,
Ezequiel Martin

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 "FIELD-EXIT CANNOT BE DEBUG!", 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.:)

Field exit is not working for a user

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

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

Field Exit for customer master data

hi
i want to execute a check every time that we create a new customer
this check should check that the field "VAT REG.." is field and not blank
please your advice what is the best practice for this issue, field exit? badi? or is there any other way recommended
i think that there is option to use field exit but i don't know which field exit and how to do it
many thanks

Hi Meir,
You go to SE84, and enter the enhancement I provided. Then, you activate the user-exit and write your own code. You can consult your ABAP team, if you are not sure about implementing user-exit.
Regards,
Eli

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,

Field Exit For Migo Badi

Hi to all experts,
I need to assign F4 help to a headertext field for MIGO tcode . I have searched all the exits but couldnt find field exit for it. What are the different options fulfilling this requirement.Please help me out

Hi,
    The following are the enhancement/Business Add ins, Please use the appropriate exit for your requirement
Enhancement/ Business Add-in            Description
Enhancement
MB_CF001                                Customer Function Exit in the Case of Updating a Mat. Doc.
MBCF0011                                Read from RESB and RKPF for print list in MB26
MBCF0010                                Customer exit: Create reservation BAPI_RESERVATION_CREATE1
MBCF0009                                Filling the storage location field
MBCF0007                                Customer function exit: Updating a reservation
MBCF0006                                Customer function for WBS element
MBCF0005                                Material document item for goods receipt/issue slip
MBCF0002                                Customer function exit: Segment text in material doc. item
Business Add-in
MB_DOCUMENT_UPDATE                      BADI when updating material document: MSEG and MKPF
MB_DOC_BADI_INTERNAL                    BAdIs During Creation of a Material Document (SAP Internal)
MB_ME_CSGMT_BADI_SAP                    BAdI: Consignment Processing - Stock Transfer
MB_MIGO_BADI                            BAdI in MIGO for External Detail Subscreens
MB_MIGO_ITEM_BADI                       BAdI in MIGO for Changing Item Data
MB_PHYSINV_INTERNAL                     Connection: Core Inventory and Retail AddOn
MB_QUAN_CHECK_BADI                      BAdI: Item Data at Time of Quantity Check
MB_RESERVATION_BADI                     MB21/MB22: Check and Complete Dialog Data
MB_RESERVATION_SCR                      Screen BAdI for Retrofit DFPS
MB_RESERVATION_UPCHD                    BAdI for Creation and Changing of Manual Reservations
MB_RES_BAPI_CHANGE                      BAdI: Execution of Changes to Reservation Fields
MB_RES_BAPI_CREATE1                     BAdI: Adoption of Customer's Own Fields as Reserv. Fields
MB_RES_BAPI_DETAIL1                     BAdI: Display of Customer's Own Fields in Reservations
MB_STOR_LOC_BADI_GTS                    BADI to Check and Change Storage Location (GTS Fct. Only)
MB_DOCUMENT_BADI_SAP                    BADI for Creation and Changing of a Material Document
ARC_MM_EBAN_CHECK                       BAdI: Enhancement of Archivability Check (MM_EBAN)
ARC_MM_EBAN_PRECHECK                    BAdI: Enhancement of Archivability Check (MM_EBAN)
ARC_MM_EBAN_WRITE                       BAdI: Enhancement of Scope of Archiving (MM_EBAN)
ARC_MM_EINA_CHECK                       BAdI: Enhancement of Archivability Check (MM_EINA)
ARC_MM_EINA_WRITE                       BAdI: Enhancement of Scope of Archiving (MM_EINA)
ARC_MM_INVBEL_CHECK                     BAdI: Enhancement of Archivability Check (MM_INVBEL)
ARC_MM_INVBEL_WRITE                     BAdI: Enhancement of Scope of Archiving (MM_INVBEL)
ARC_MM_MATBEL_CHECK                     Prüfung ADD-ON-spezifischer Kriterien für MM_MATBEL
ARC_MM_MATBEL_WRITE                     Check Add-On-Specific Data for MM_MATBEL
MB_CHECK_LINE_BADI                      BAdI: Check Line Before Copying to the Blocking Tables
MB_CIN_LMBMBU04                         posting of gr
MB_CIN_MM07MFB7                         BAdI for India Version exit in include MM07MFB7
MB_CIN_MM07MFB7_QTY                     Proposal of quantity from Excise invoice in GR
MB_DOCUMENT_BADI                        BAdIs During Creation of a Material Document

How to know whether a field exit is getting triggered or not??

HI ,
We are upgrading a system from 4.6 to ECC, the problem is that, in earlier system field exit was getting triggered but its not getting triggered in ECC, the field exit is active in ECC but still its not getting triggered.
Field Exit is FIELD_EXIT_SAKNR.
Please provide some help
Regards
Karan Arya

Hi,
As part of the extension concept, SAP allows you to install a field exit for each screen field. Similar to the conversion exit, the system branches at the field exit at DCI (DATA COMMUNICATIONS INPUT) to a function module, if the field is an input field and a function code was triggered. The function module must adhere to the following naming convention:
Prefix: FIELD_EXIT_
Infix: <Data element name>
Suffix: _0 to _9 (optional), _A to _Z
The interface is automatically generated during the creation of the function module, and has 2 parameters:
Import parameter: INPUT
Export parameter: OUTPUT
After a function code has been triggered the contents of the field are made available to the FB via the "INPUT" import parameter. You can edit this and, when changed, make it available to the ABAP/4 processor in "OUTPUT". The input field contents are usually passed on: you can simply write OUTPUT = INPUT.
If, e.g., you have activated the field exit for the data element 'PROGRAM', then the fields of all the screens, which refer to the data element 'PROGRAM', branch to the function module FIELD_EXIT_PROGRAM. This includes the field 'Program' of the initial screen SAPMS38M0100 in transaction SE38, for example.
If you do not want the function module to be accessed from all screens, assign particular screens to the data element PROGRAM. By allocating an exit number, it is also possible to branch to other function modules with the corresponding suffix _0 ... _Z.
Example: You have assigned screen SAPMS38M0100 and exit number 5 to data element 'PROGRAM'. The corresponding field on SAPMS38M0100 branches to FIELD_EXIT_PROGRAMM_5.
As soon as you activate an exit, the corresponding screens are invalidated.
Note: Field exits are only taken into account during screen generation if the parameter abap/fieldexit = 'YES' is set in the system profile.
Requirement
Set the profile parameter abap/fieldexit = 'YES' before system start.
Limitations
The following ABAP statements are not allowed in the function modules of field exits:
BREAK-POINT,
CALL SCREEN, CALL DIALOG, CALL TRANSACTION, SUBMIT,
COMMIT WORK, ROLLBACK WORK,
COMMUNICATION RECEIVE,
EXIT FROM STEP-LOOP,
MESSAGE I, MESSAGE W.
Note:
Field exits cannot be edited with the debugger.
You should not use any external Performs in field exits. The ABAP processor shares the table work areas of externally called programs with those of the first caller. This could lead to errors at field exits that can hardly be analyzed, as field exits are sometimes slipped into the flow of the program at unforeseen events.
Hope this helps you resolve your issue.
Regards,
Jayanth

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

Field exits is not working in the COPA

Dear All,
I had create the field exits for profit center and it is working well in all the screen except the COPA. My profit center field exits will automatically change the profit center value if user key in the valid profit center department in the profit center field.
However, it is not working in the COPA screen. Please kindly advise.
thank you very much

Thank u for your answer.
Yes, of course .. i�ve already apply the unique key validator for the entity.. so that custom error message is the error im trying to get in the application.
Other issue is when im trying to edit that error message: when im going to edit the message the previous error im entered is not there. Is it normal?

Can I call popup on Field-Exit ?

Hi,
    I create field-exit vorgang at MIRO and when the conditional begins, display a popup ( i used popup_to_confirm) but instead, An error occurred RPERF_ILLEGAL_STATEMENT.
So, if i really got it on field-exit a can't call screen, dialog, submit and use message W or I.
Someone can help with this, please i really need.
regards
Marcos Rodrigo

I won't go into the reasons for not using field exits any more as this is well documented. However, if this is your only choice then you can get popups to work by encapsulating your requirement into a function module.
To get it to work you have to flag your function module as RFC enabled and use the syntax:
CALL FUNCTION func STARTING NEW TASK task
   DESTINATION dest
   PERFORMING subr ON END OF TASK.
Now if you combine this with a wait command
WAIT UNTIL log_exp
then get your subroutine defined in subr to set a flag to which the WAIT command is looking for.
This works by your field exit waiting until the RFC has finished. However, as it is STARTING NEW TASK then this has the ability to do anything i.e. SUBMIT, CALL SCREEN, issue message etc as it is a separate dialog process.
Edited by: Pete Devereux on Jan 28, 2009 3:25 PM

Field Exits Function

Hai, can we use the field exits function to copy from other field value?
for example, when we entering the date inside the screen 01/01/2012, then we exit the fields, this value will direct copy to other field? that mean both for the field is the same value. can it be done inside the SAP?
My consultant said this cannot be done. hope some of the expert at here can give me a solution.

Hi,
What is the transaction code you are trying for? Generally, field exits are not recommended due to performance issues. However, it is possible to copy a value from one field to another field using BADIs. Kindly check if there are any BADIs available or not for your transaction code.
Thanks and regards,
Sreniya

Field Exit Issue

Similar Messages

Maybe you are looking for