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
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.:) -
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 -
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 -
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
enzoHi 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 -
How to link or call two FIELD EXIT
Hi Friends,
I've to do a Field exit object for MIGO...and my logic is i've to capture the meory id concept by Export and Import function.So, I heard that I've to create one field exit with Export function and again create under one more field exit to import the memory id from Export.
I know the logic of Export and Import.But i dont know how to fix it in the function module,means how to create one field exit and call the same under one more field exit.
Pls do the needful and post me with some good field exit examples for my reference.i.,e How to give codes inbetween Function and End Function. and how to call this field exit with one more field exit for import stmt.
if u find BADI or USER EXIT is good for MIGO,pls reply with good and correct example functions.
Thanks and regards
sankar.
Edited by: sankar babu on Dec 29, 2007 10:00 AMHello Sankar,
Just you want to use the functionaly Import and Export , that why you required two Fields Exit in transitation MIGO.
I suggest MIGO is huge transitation which conver some table like MSEG and BSEG which affect the performance of the program. Better you go with one field Exit . Although there are many Some are attach Below.
Re: MIGO Enhancement
Re: How to add field to MIGO Urgent??
SMOD enhancement MBCF0005 looks promising.
MBCF0002
MBCF0005
MBCF0006
MBCF0007
MBCF0009
MBCF0010
MBCF0011
MBCFC003
MBCFC004
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/QMIMIL/QMIMIL.pdf.
MB_DOCUMENT_BADI or MB_DOCUMENT_UPDATE
and these exits: MBCF0002, MB_CF001
Regards
Swati Namdeo -
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 -
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 -
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. -
Can any one tell me how to work with field exit????
Hi
Can any one tell me how to work with field exit I know how to create them. I want to know how it works. Actually I want to create a field exit for T-CODE MIRO. Where I want to put the value ebeln of the PO Reference tab into the Assignment of details tab and make Assignment field disable.
Thanks in advanceHi,
Follow the Steps,
1. Go to CMOD transaction
2. From the menu "GOTO->TEXT ENHANCEMENTS->DATA ELEMENTS- ->NEW DE CUST DOCU".
3. In the displayed box specify the data element and
press either "CHANGE" or " Ref to screen" button
4. CHANGE button is for defining the documentation
5. "Ref. to screen" if for assigning the screen in which
a field has the this type data element.
Note: You should have used this data element for a
field in that screen.
6. Now it will ask for Function Module name, specify the
FM name and double click it. It will go to the editor.
7. Now using the Import parameters code accordingly
8. Activate and go back
9. Now "Assign the created program ( that is FM) to the
screen by specifying the Program name and Screen
number.
10. Now save and activate.
Note: No need to create a separate project for creating field exit through transaction CMOD.
I hope this is suffice.
Regs,
Venkat Ramanan -
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 -
Hi experts, I'm new on SAP, and I have to deactivate a field exit on the Standard Transaction MIRA, how can i do thath?
Transaction Code - MIRA Fast Invoice Entry
Exit Name Description
LMR1M001 User exits in Logistics Invoice Verification
LMR1M002 Account grouping for GR/IR account maintenance
LMR1M003 Number assignment in Logistics Invoice Verification
LMR1M004 Logistics Invoice Verification: item text for follow-on docs
LMR1M005 Logistics Inv. Verification: Release Parked Doc. for Posting
LMR1M006 Logistics Invoice Verification: Process XML Invoice
MRMH0001 Logistics Invoice Verification: ERS procedure
MRMH0002 Logistics Invoice Verification: EDI inbound
MRMH0003 Logistics Invoice Verification: Revaluation/RAP
MRMN0001 Message output and creation: Logistics Invoice Verification
No of Exits: 10
USER EXIT
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sapgenie.com/abap/code/abap26.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
http://www.easymarketplace.de/userexit.php
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sappoint.com/abap/userexit.pdfUser-Exit
http://www.sap-img.com/ab038.htm
http://help.sap.com/saphelp_46c/helpdata/en/64/72369adc56d11195100060b03c6b76/frameset.htm
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://expertanswercenter.techtarget.com/eac/knowledgebaseAnswer/0,295199,sid63_gci982756,00.html
Exits are basically the hooks whcih SAP has provided to add your own code. There are two types of Exits:
1. Customer exits: Implemented as Function Modules within z includes. Anybody can change it and no access key is required.
2. User Exit: Implemented as subroutines within includes (any include except y or z includes). You need access for the specific include and then you can any subroutine (user exit) within that Include.
BADIs are the enhanced version of user exits where the same logic is implemented via classes and object (OOP)
Enchancement point is the latest once introduces with ECC6.0 . Not very sure about that but you can change it without any access key.
Please go through the following link which will help you understand the exits in a much better way:
http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec07a25db911d295ae0000e82de14a/content.htm
http://www.sap-img.com/abap/what-is-the-difference-between-smod-and-cmod.htm
http://sap.niraj.tripod.com/id21.html
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm
http://www.sap-img.com/ab038.htm
User Exits.
http://www.erpgenie.com/sap/abap/code/abap26.htm
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sapgenie.com/abap/code/abap26.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
http://www.easymarketplace.de/userexit.php
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sappoint.com/abap/userexit.pdfUser-Exit
customer exits
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f1a7e790-0201-0010-0a8d-f08a4662562d
Menu Exit.
http://www.sappoint.com/abap/spmp.pdf
http://www.sappoint.com/abap/userexit.pdf
http://www.sapdevelopment.co.uk/enhance/mod_sapmenu.htm
http://www.sapdevelopment.co.uk/enhance/enhancehome.htm
Rewards if useful.........
Minal -
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 AMHi,
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 -
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. -
Hi Gurus,
I have created a Z program with a MARA-EAN11 data element field which is necessary to read MARA table and return its material code (MATNR) in a text field after ENTER key pressed.
It was created also a Field Exit called FIELD_EXIT_EAN11 and it is working fine in test mode (SE37), but when I try to trigger by ENTER key in my Z program, it is not being executed.
What Am I doing wrong?
Thanks,
Michel KhouriHi Max,
This programs already exits and now it is being implemented Bar Code functionality. The program will read the bar code and then call a routine to fill some fields automatically, as example: Material Code, Materia description, EAN and so on...
The idea is create a new screen (CALL Screen FM) to put those data.
That's the reason to use Field Exit after EAN field/ENTER Key actions.
Thanks again,
Michel Khouri
Maybe you are looking for
-
Adapter Class not formed error in bdk 1.1. with jdk1.4.2
Hi, i have installed j2sdk 1.4.2 on my machine n bdk 1.1 now I have set classpath apropriatly.now when i m going to hook up two beans there appear this error WARNING: Could not Runtime.exec(String) "javac" in the standard way: java.io.IOException: Cr
-
I am trying to create a simple form for people to print out and fill in. I want fields like 'Name' with a line extending from the word for people to write on. What should be the simplest of tasks has confounded me for HOURS. Inserting a line as a 'sh
-
Hi, If you want to upload a Xcelsius file to BI OnDemand, take a look to this blog article. [http://www.clariba.com/blog/xcelsius-in-bi-on-demand-biod/] I hope it can help you. Regards,
-
Generate certificates valid for smart card (Windows logon) with third party PKI (not Microsoft)
Hello everyone today I am working on a mounted on a Red Hat Enterprise PKI Linux Server release 5.5 (Tikanga) is Easycert 5.2.2.15. We need to know what are the necessary data that we have to go to the PKI so it can generate certificates of users in
-
Set delegation and substitution by adminsitrator
Hi, is there a way to activate delegation and substitution for another user, for example using an adminstrator account? Or is there an API do to this and if yes, does anyone have some sample code? I am working with NWCE 7.2. Thanks, Kevin