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

Similar Messages

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

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

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

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

Error while activating field exit

hi all
while activating field exit iam getting error
like system is not configuted for field exit
solution is Set the abap/fieldexit parameter to YES in the system profile and restart your SAP system
then in which tcode i can set the parameter
thanks in advance

1)Login to R/3
2)Tcode RZ10
3)Select instance profile
4)click extended maintenance
5)change
6)Add parameter
7)Abap/fieldexit -> save and activate the changes.
Then restart you r/3 system.

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

Error in activating Field exits

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

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

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,
Steve

Due to lack of assistance, we were unable to pursue this requirement - the users were not happy, but what can you do, huh!

How to write the code for IMPORT and export in Field exit

Hi,
Using the FB01 tcode with condition as document type (ZF) and company code
i want to substitute values should come in the next screen.
i am passin the document type and the company code in the FB01 initial screen (100) and added field exit for Cost centre.
if the Doc type ZF and company code is 0245 then the field exit shoul trigger and give the defaul cost centre value if it contain any cost centre valu it over write the existing if it is empty i will write the defauls cost centre value.
Thanks & Regards,
Nelsons......

Hi,
As i have understood, if ur doc type is ZF and company code is 0245, then you want to pass the value to cost centre field in next screen.
You can use program RSMODPRF. here enter the data element of cost centre field and assign the screen no and program name (for FI docs prg name would be SAPMF05A).
After assigning program and screen no , Create the function module where u have to write an 'if' statement for assigning value to cost centre (i.e export field in FM)
the values for company code and document type can be fetched from their respective parameter ids i.e. BUK and BAR.
Regards,
Seema Jaisinghani

FIELD exit For WADAT

Hello ,
I have Implemented a field exit for Data element WADAT, but my requrement is, The value In the field LIKP-WADAT in VLO2n/VLO1N TRansaction should not be allowed to change even a single time.
Is there any user exit do statisfy my requirement
cheers.

Field exit can be used to validate a user entry and not restrict a user entry. Even if you implement field exit user can always go and change the contents of field and in field exit ( only triggered in PAI ) there is no way to determine if field value was changed .
You should make the field output only in case you dont want users to change it.
Check if you have BADI LE_SHP_DELIVERY_PROC in your system. In this BADI you can use method CHANGE_FIELD_ATTRIBUTES to set the attributes of LIKP-WADAT in parameter CT_FIELD_ATTRIBUTES to disable input .
Cheers.
Sanjay

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.:)

IMPORT to memory id with field exit

hi everyone, i need your help, i'm import to memory/export with field exit, I must capture a data of ik11, from table IMRG... this is the code:
FUNCTION FIELD_EXIT_IMRC_MDOCM.
   DATA: V_MDOC LIKE IMRG-MDOCM.
EXPORT V_MDOC TO MEMORY ID 'DOC'.
ENDFUNCTION.
And the field exit where capture the data and import to memory:
FUNCTION FIELD_EXIT_IMRC_CNTRC.
    GET PARAMETER ID 'IPT' FIELD V_POINT.
      IMPORT V_MDOC FROM MEMORY ID 'DOC'.
    MESSAGE E001(ZEXITS_PRUEBAS) WITH V_MDOC.
ENDFUNCTION.
I proof with message, 'cause i can't use a break, really?!!!!
Please help me!
Thanks.!

Hi Jimena,
I remember a field exit being connected to a data element and program screen (dynpro). The field exit is processed when the screen field is processed by dynpro processor. But I do not see the screen field's value being exported to memory.
The reason you can't put brekpoints is that actually the code is triggered by dynpro processor not abap runtime environment.
If you want to proove thecode beeing executed, you can write info to file.
SAP does not actively support field exits since a couple of releases. Are you sure this still works?
You could try to find a BADI: Use the method I found at SDN some time ago:
Follow the below steps to find out what all BADI's are called when you press any button in any transaction.
1) Goto se24 (Display class cl_exithandler)
2) Double click on the method GET_INSTANCE.
3) Put a break point at Line no.25 (CASE sy-subrc).
Now
4) Execute SAP standard transaction
5) Press the required button for which you need to write an exit logic, the execution will stop at the break point.
6) Check the values of variable 'exit_name', it will give you the BADI name called at that time.
7) This way you will find all the BADIs called on click of any button in any transaction.
Regards,
Clemens

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

Parameter or Field Exit issue

Similar Messages

Maybe you are looking for