Field exit creation

i want to change the logic in wchi Field exits allow you to create your own programming logic for any data element
but when i create afield exit i did't found field exit in menu of text enhance ment in ECC6 version what i can do to create afield exit with module field_exit_<dataelement name>_<0-9 A-z>

Hi,
The only problem is assigning the program and the screen through tr. code CMOD. The option was
appearing in 4.6 but In ECC 6.0, it is not there.
This is the main issue.
i think it will helpful for you.

Similar Messages

Field Exit Creation -Urgent

HI Gurus,
Has any one created Feild Exit any where in the real time,If so for what Data Element you have created and wht was the senario you hae made use of htat was it for a report .Plz do share that i wud reward points for all useful answers

Hi,
Yes we have created a field-exit for data element werks_d. The purpose was to make it obligatory for the user to enter the Plant. Please note that there are some limitations on field-exit e.g. you can not put the debugger on for it. Hence field-exit should be avoided to the extent possible.
I hope this helps,
Regards
Raju Chitale

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

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

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

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

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

TabStrip and Field Exit......

Hi Friends,
I need the complete step by step working process of "Tabstrip and FieldStrip".Also any sample code will be highly appreciated.
Points will be rewarded for Requirement.
Thanx ,
Mandeep.

Hi,
TABSTRIP
Tabstrip is used to display multiple subscreens on the same area of the screen in designing transactions
see the links related to Module pool, in which you find the Tabstrip
Check the below link:
http://wiki.ittoolbox.com/index.php/FAQ:What_is_module_pool_program_in_abap%3F
http://help.sap.com/saphelp_46c/helpdata/en/35/26b1aaafab52b9e10000009b38f974/content.htm
http://sap.mis.cmich.edu/sap-abap/abap09/sld011.htm
http://sap.mis.cmich.edu/sap-abap/abap09/index.htm
http://www.geocities.com/ZSAPcHAT
http://www.allsaplinks.com/files/using_table_in_screen.pdf
http://help.sap.com/saphelp_webas630/helpdata/en/9f/db9cdc35c111d1829f0000e829fbfe/content.htm
http://www.sapdevelopment.co.uk/dialog/dialoghome.htm
http://www.sap-img.com/
http://help.sap.com/saphelp_46c/helpdata/en/08/bef2dadb5311d1ad10080009b0fb56/content.htm
http://www.sapgenie.com/links/abap.htm
http://help.sap.com/saphelp_nw04/helpdata/en/c9/5472fc787f11d194c90000e8353423/frameset.htm
You can also check the transaction ABAPDOCU which gives you lot of sample programs.
Also you can see the below examples...
Go to se38 and give demodynpro and press F4.
YOu will get a list of demo module pool programs.
One more T-Code is ABAPDOCU.
YOu can find more examples there.
See the prgrams:
DEMO_DYNPRO_TABLE_CONTROL_1 Table Control with LOOP Statement
DEMO_DYNPRO_TABLE_CONTROL_2 Table Control with LOOP AT ITAB
http://www.geocities.com/ZSAPcHAT
http://www.allsaplinks.com/files/using_table_in_screen.pdf
FIELD-EXIT
http://www.erpgenie.com/abap/fieldexits.htm
http://www.sap-basis-abap.com/sapab014.htm
V4.6c onwards no longer supports field exits!!! In any case here's how to activate them:
Activation of the field exits and assignment of the dynpros is 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 below for documentation).
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.
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.
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,
Priyanka.

Help with a field exit

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

Can any body tell me, can we attach field exits to Njoy trnsactions in 4.7

Hi,
can any body tell me how to attach field exits to the enjoy transactions in 4.7.
I was not been able to attch the field exits to "Account assignement catagory" in trnasaction ME51N(Purchase requisition creation) using the program "RSMODPRF".
Please suggest.
Best Regards
Ramanjaneya Reddy

But hey! Your in 4.7, use BADIs!
Goto transaction SE18, search and you will find some stuff like ME_PROCESS_REQ. There are several dozens for purchasing, so go for the new technics.
By the way, I'm not sure if workaround is still possible in 4.7.
Implementation will be done with SE19.
Regards,
Christian

Field exit and Authorization grp

Hi All,
I have the following requirement...
I Created a field exit for the data element (MATKL-for example)..Is there any chance that we could use that AG as indicator to evaluate in the field exit???
That is...
If the material group(MATKL) has the AG(Authorization group) populated with a value (ZRES for example) ,then that particular Material group is restricted and should not be used in the creation/modification of documents.
Is there any possiblilty of achieving the above requirement..??
Please suggest a solution.
Regards
Shiva

My requirement in this scenario is : I need to decide between a authorization group and field exit to restrict the users using some group of material groups which are obsolete.
Since the field exits are created over a data element in many transactions such as ME21N/22N/23N/..etc the data element for material group is not MATKL so in such cases I need to create field exits for all data elements which the material group uses across various transactions.
On the other hand, if I could restrict the use of certain material group based on authorization group then use of field exit would not be required
But the possible problem with this may be to restrict only certain transactions but not all the transactions.
Authorization Object: M_MATE_WGR
Definition :
Material group authorization for material master records.
This object determines whether a user is authorized to maintain the material master record for a specific material group.
Defined Fields
Fields
Possible values :
ACTVT
01 User may create data.
02 User may change data.
03 User may display data.
06 User may mark data for deletion.
BEGRU (Authorization grp-table T023)
Here you must specify the
authorization groups from Table T023
for which the materials concerned may
be processed.(may be any number of grps)
Regards
Shiva

Fields in Creation of free goods VBN1

hi everybody,
Can somebody expalin in detail the fields in creation of free goods(T-vbn1) like free goods quantity,additional quantity,documnet quantity and calculation rule....
Please dont copy paste anything form SAP help....I read that one......
I would appreciate if u explain with your sentence..
Will reward point if it helps.
Ghassan

Hi Gafoor,
Material
Material, for which free goods is to be
granted
Minimum quantity
Minimum quantity for which free
goods can be granted
From
Quantity of sales material
FGQ--- Quantity unit of free goods material
Free goods -- Quantity of free goods with reference to the quantity and quantity unit of the sales material.
AQU - Quantity unit of the free goods additional quantity
Rule - Calculation rule
Prorata
whole units
unit related
D -- Delivery controlling - it tells how you can manage the delivery of free goods with respect to the main item ordered.
Additional material - Additional material (only available for entry in exclusive free goods)
Hope it helps. Please reward if helpful.
Thanks & Regards
Sadhu Kishore

What are the mandatory fields while creation of material master in differen

what are the mandatory fields while creation of material master in different views?

Hi Gopi,
This is purely depends on the function configuration, which would be done MM consultants. Kindly check with them.
thanks & regards
Kishore Kumar Maram

Field exit creation

Similar Messages

Maybe you are looking for