User exit for IW31 which capture screen field Po number

Hi all
I have the requirement that when we save work order created by IW31. It shud trigger any user exit or BADI.
In that we have to validate the screen field Purchase order number BSTKD from the Ztable entries.
My problem is that no user exit passes this value as export parameter. so without that how can I get this value in the include program. Please let me know the user exit which hit after save and passes PO value so I can validate this field. Thanks!!!
Quick answer will highly be appreciated!!
Nikhilesh Vyas

Hello Kiran
Thanks for ur reply
But this Badi does not have purchase order number as parameter in any method which call after user press save button.
Please let me know any other alternative if u have ...thanks!!

Similar Messages

User Exits for MM to hide screen field

Hi All,
I want to make input = 0 for a screen field (valuation price) in PR. Could you tell me the exits available to achieve this,
like field modification exits available for sales document processing.
Thanks
Pradeep

Hi,
I have achieved the result thru a BADI ME_PROCESS_REQ_CUST and method FIELDSELECTION_ITEM_REFKEYS.
    if screen-name = 'MEREQ3320-PREIS'.                " valuation price
     SCREEN-INPUT = 0.
     MODIFY SCREEN.
    endif.
I tried doing it with the Exit you have mentioned, but it did not work, can you tell me in which include we can
get the result.
Thanks
Pradeep

User exit for me 51 to put field descryption for ekbn-sakpto in screen 505

hi .
i have a requirement to put field descryption in screen 505 for me51 tcode(program sapmm06b) for field g/l account in screen 505(Account Assignment for item 00010).
waiting for your resposne.
bye.
sita.

Hi Seetaram,
Hi,
By using the below code you can find the User exits for a particular TCODE.Execute this program and the TCODE in selection screen.
REPORT z_find_userexit NO STANDARD PAGE HEADING.
*& Enter the transaction code that you want to search through in order
*& to find which Standard SAP® User Exits exists.
*& Tables
TABLES : tstc, "SAP® Transaction Codes
tadir, "Directory of Repository Objects
modsapt, "SAP® Enhancements - Short Texts
modact, "Modifications
trdir, "System table TRDIR
tfdir, "Function Module
enlfdir, "Additional Attributes for Function Modules
tstct. "Transaction Code Texts
*& Variables
DATA : jtab LIKE tadir OCCURS 0 WITH HEADER LINE.
DATA : field1(30).
DATA : v_devclass LIKE tadir-devclass.
*& Selection Screen Parameters
SELECTION-SCREEN BEGIN OF BLOCK a01 WITH FRAME TITLE text-001.
SELECTION-SCREEN SKIP.
PARAMETERS : p_tcode LIKE tstc-tcode OBLIGATORY.
SELECTION-SCREEN SKIP.
SELECTION-SCREEN END OF BLOCK a01.
*& Start of main program
START-OF-SELECTION.
Validate Transaction Code
SELECT SINGLE * FROM tstc
WHERE tcode EQ p_tcode.
Find Repository Objects for transaction code
IF sy-subrc EQ 0.
SELECT SINGLE * FROM tadir
WHERE pgmid = 'R3TR'
AND object = 'PROG'
AND obj_name = tstc-pgmna.
MOVE : tadir-devclass TO v_devclass.
IF sy-subrc NE 0.
SELECT SINGLE * FROM trdir
WHERE name = tstc-pgmna.
IF trdir-subc EQ 'F'.
SELECT SINGLE * FROM tfdir
WHERE pname = tstc-pgmna.
SELECT SINGLE * FROM enlfdir
WHERE funcname = tfdir-funcname.
SELECT SINGLE * FROM tadir
WHERE pgmid = 'R3TR'
AND object = 'FUGR'
AND obj_name = enlfdir-area.
MOVE : tadir-devclass TO v_devclass.
ENDIF.
ENDIF.
Find SAP® Modifactions
SELECT * FROM tadir
INTO TABLE jtab
WHERE pgmid = 'R3TR'
AND object = 'SMOD'
AND devclass = v_devclass.
SELECT SINGLE * FROM tstct
WHERE sprsl EQ sy-langu
AND tcode EQ p_tcode.
FORMAT COLOR COL_POSITIVE INTENSIFIED OFF.
WRITE:/(19) 'Transaction Code - ',
20(20) p_tcode,
45(50) tstct-ttext.
SKIP.
IF NOT jtab[] IS INITIAL.
WRITE:/(95) sy-uline.
FORMAT COLOR COL_HEADING INTENSIFIED ON.
WRITE:/1 sy-vline,
2 'Exit Name',
21 sy-vline ,
22 'Description',
95 sy-vline.
WRITE:/(95) sy-uline.
LOOP AT jtab.
SELECT SINGLE * FROM modsapt
WHERE sprsl = sy-langu AND
name = jtab-obj_name.
FORMAT COLOR COL_NORMAL INTENSIFIED OFF.
WRITE:/1 sy-vline,
2 jtab-obj_name HOTSPOT ON,
21 sy-vline ,
22 modsapt-modtext,
95 sy-vline.
ENDLOOP.
WRITE:/(95) sy-uline.
DESCRIBE TABLE jtab.
SKIP.
FORMAT COLOR COL_TOTAL INTENSIFIED ON.
WRITE:/ 'No of Exits:' , sy-tfill.
ELSE.
FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
WRITE:/(95) 'No User Exit exists'.
ENDIF.
ELSE.
FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
WRITE:/(95) 'Transaction Code Does Not Exist'.
ENDIF.
Take the user to SMOD for the Exit that was selected.
AT LINE-SELECTION.
GET CURSOR FIELD field1.
CHECK field1(4) EQ 'JTAB'.
SET PARAMETER ID 'MON' FIELD sy-lisel+1(10).
CALL TRANSACTION 'SMOD' AND SKIP FIRST SCREEN.
Reward if helpful,
phani

How to create user exit for MIGO check "item OK" Field select/unselect?

Hi All,
I want to know User Exit for MIGO Screen. when I click check button it will be show "Item OK " Field select or not.
MIGO Screen post if Item ok field select both parent id and line id . otherwise it will be show error message?.
Can Please every one tell me how to do user exit for MIGO?
mail id: [email protected]
thanks,
S.Muthu,

Hi,
check the BADI MB_MIGO_BADI ( method: POST_DOCUMENT).
COMD enhancment MBCF0005
Regards

User-exit for call new customize screen of another new program

Hello, I'm very appreciate for all who read this topic and give me some advice.
Anyone has an experience about customize standard program to create new screen
and add new screen to pop-up when user click some standard button to do something
for support business requirement and then continue to working the old step (such next old screen).
In QA11 (Manual UD), For posting stock quantity (After click button "Stock for inspection lot")
Business requirement need to avoid user to input stock quantity for unrestriced used (UR) and block
by after click button "Stock for inspection lot". Need to customize to pop-up new created screen for user
to choose sub-set of this inspection lot to post for UR or block by check box (Just overview)
Then after finish to select, Need to go back old screen ("Record UD : Stock" Screen) and default sum
of UR and block into screen (Automatic) for post to mvt.type 321, 350 later.
After checked, Not have any screen-exit after clicked button "Stock for inspection lot".
but i found 1 user-exit which was called after click above button.
So, Can i use user-exit to call new customize screen?
If need to go back from new customize screen to main screen, May have any problem? How to do it?
If finish to do in new customzie screen and need to continue display next old screen. How to do it in PAI of new customize screen.
Thank in advance

Can anyone provide the documentation for this BADI? Also, I'm concerned about the layout of the screen. Can this BADI do the necessary changes on the layout of the screen?
Thanks!

User Exit for IW32 accessrights check on fields

Hello,
i need to implement a check that enables me to block the access on a column within the table (transaction IW32) at the objects-tab for users of a specific role.
That check could be done by showing an error message once the user presses SAVE or by blocking the input in that table. I checked the Userexit EXIT_SAPLCOIH_009 but that one only allows a check on the header data not on the data of the objects-tab.
I hadnt found any other user exit that could do the trick. Is that only possible by SAP-code manipulation ?
Could somebody help me out here ?
Thanks and best regards,
oliver

Hello and thank you very much for the answers.
Pete, i checked the BADI IWO1_SCREEN_MODIFY but im unsure if that would work because it only hides fields and doesnt allow to disable input. Another problem is that the screen-loop only runs over the input-fields above the tab and the table. (like Order, Sys. Status etc)
But i need to modify the table itself. Any idea how i can access the table on the tab here ? I normally use ALVs so the question is too if the screen-loop even run over such old-styled-tables usually. Cant say that 100% but i thought it would. For me it looks it doesnt actually :/
The loop-screen runs only over the elements of dynpro 1108 and not 0300 which contains the table.
Any idea ?
thanks again, your help is highly appreciated.
oliver
Edited by: Oliver Neumann on Jan 29, 2009 10:25 AM

BADI or User exit for FB50 to update custom field in table COEP

Hi all,
i have added one custom field in table COEP through include CI_COBL .
when i do posting through sales order(VA02) or purchase order(ME22n) that custom fields in COEP get updated with controlling document
and through BADI AC_DOCUMENT i m updating that custom field in COEP.
but when i do manual posting through FB50 controlling document is generated in COEP but i m not able to update that custom field
because in this case BADI AC_DOCUMENT is not get triggered.
is there any BADI or User exit or enhancement spot for FB50 through which i can update that custom field in table COEP

Hi Sandy,
Thanks for u r reply,
RFAVIS01 is not getting triggered through FB50
and F180A001 ( EXIT_SAPLF048_001) is getting triggered but it doesnt contain COEP field in its parameter
import - F180A_DOC_HEAD_TAB
F180A_DOC_ITEM_TAB
changing - RELATION_TAB

User Exit for IW31

Hi Friends,
I've to agree a validation on the field RESBD-POSTP but I can't find an user exit to do that.
Thanks in advance.....
Leonardo.

Hi Erwan,
Yes, I tried to used IWO10012, but it didnt work.
Do you know another exit?
Thanks.
Leonardo.

BADI/user exit for me22n - disable/grey out field quantity (MEPO1211-MENGE)

Dear all SAP gurus,
When changing PO (ME22N), I need to disable (grey out) the quantity field on item (MEPO1211-MENGE), when all scheduled quantity is already received (EKET-MENGE = EKET-WEMNG).
Have tried using LMEIGICJI and Handle_event method in CL_SCREEN_VIEW_MM. But still doesn't go to the screen that wants to be disabled.
Tried using BADI ME_PROCESS_PO_CUST, but couldn't find how to disable the quantity field.
(IF_EX_ME_PROCESS_PO_CUST~FIELDSELECTION_ITEM only works for custom field).
Please kindly advise
thanks in advance

Hi Ahmad,
No need of ABAP, follow this IMG Path.
Material Management -> Purchasing - Purchase Order -> Define Screen Layout at Document Level
After Executing it . Choose ME22 from list and then choose display icon.
than double click Quantity and Price here uncheck opt. Entry and check display.
save your work.
Hope this works.
Regards
Ahsan

User Exit for Variable which calls to a Function Module is NOT working ???

Hi all,
    I have a created a variable 'ZNBUSDAY' with Processing Type 'Customer Exit' on 0SCL_DELDAT (Date). The query is on 0PUR_C04 and passing 0SCL_DELDAT to Function Module Z_WORKDAY to get the Next Business Day by using the company Calendar(30). The following code is NOT working and what is WRONG with it, PLEASE? The FM is working FINE.
DATA: wa_calendar(2) TYPE c value '30',
      wa_znbusday    like sy-datum,
      0scl_deldat    like sy-datum,
      p_days         TYPE i value 1.
case i_vnam.
   when 'ZNBUSDAY'.
   CLEAR wa_znbusday.
   CALL FUNCTION 'Z_WORKDAY'
     EXPORTING
     CURR_DATE        = 0scl_deldat
     NUMBER_DAYS      = p_days
     CALENDAR         = wa_calendar
   IMPORTING
     WORK_DAY         = wa_znbusday
     l_s_range-low = wa_znbusday.
     l_s_range-opt = 'EQ'.
     l_s_range-sign = 'I'.
     append l_s_range to e_t_range.
endcase.
Thanks,
Venkat.

Hi Venkat,
Looks like you're only assigning type sy-datum to 0scl_deldat but not the actual value. Try the following:
DATA: wa_calendar(2) TYPE c value '30',
      wa_znbusday    like sy-datum,
      0scl_deldat    like sy-datum,
      p_days         TYPE i value 1.
case i_vnam.
   when 'ZNBUSDAY'.
   CLEAR wa_znbusday.
   0scl_deldat = sy-datum.
   CALL FUNCTION 'Z_WORKDAY'
     EXPORTING
     CURR_DATE        = 0scl_deldat
     NUMBER_DAYS      = p_days
     CALENDAR         = wa_calendar
   IMPORTING
     WORK_DAY         = wa_znbusday
     l_s_range-low = wa_znbusday.
     l_s_range-opt = 'EQ'.
     l_s_range-sign = 'I'.
     append l_s_range to e_t_range.
endcase.
Kind regards,
Alex

PPCO0007 User Exit for Changing Header Fields During Order (CO40)

.. Hi !!!!
I need your help or suggestions,
I need to change the standar order before to save, i found the user exit PPCO0007,
i assign the new value for the order, but when finish the fuction, EXIT_SAPLCOZV_001, the new values are
lost, and finally the system set the standard order.
Someona know how can change the order and the the batch.
Thanks
Noemí Huerta

Hi Noemi
You can use the enchancement PPCO0007 (exit when the production order is saved).
Use the function module EXIT_SAPLCOZV_001 (User Exit for Checking or Changing Header Fields During Order Save) to update the field priority starting the information in the material-customer info record.

User Exit for ME21n - Urgent

HI all,
I want to add a function module when a Purchase order is saved(ME21n), i want to know how to find user exit for ME21n & which user exit to be changed.
I want to call a function module when the user saves the purchase order, please help.
Please also let me know the step to find the user exits.
Thanxs in advance.

Hi,
Please check enhancement MM06E005 (SMOD).
Here list of User exit and BADI for ME21N .
Transaction Code - ME21N Create Purchase Order
Enhancement/ Business Add-in Description
USER EXIT
MELAB001 Gen. forecast delivery schedules: Transfer schedule implem.
MEQUERY1 Enhancement to Document Overview ME21N/ME51N
MEVME001 WE default quantity calc. and over/ underdelivery tolerance
MM06E001 User exits for EDI inbound and outbound purchasing documents
MM06E003 Number range and document number
MM06E004 Control import data screens in purchase order
MM06E005 Customer fields in purchasing document
MM06E007 Change document for requisitions upon conversion into PO
MM06E008 Monitoring of contr. target value in case of release orders
MM06E009 Relevant texts for "Texts exist" indicator
MM06E010 Field selection for vendor address
MM06E011 Activate PReq Block
MMAL0001 ALE source list distribution: Outbound processing
MMAL0002 ALE source list distribution: Inbound processing
MMAL0003 ALE purcasing info record distribution: Outbound processing
MMAL0004 ALE purchasing info record distribution: Inbound processing
MMDA0001 Default delivery addresses
MMFAB001 User exit for generation of release order
MRFLB001 Control Items for Contract Release Order
AMPL0001 User subscreen for additional data on AMPL
LMEDR001 Enhancements to print program
LMEKO001 Extend communications structure KOMK for pricing
LMEKO002 Extend communications structure KOMP for pricing
LMELA002 Adopt batch no. from shipping notification when posting a GR
LMELA010 Inbound shipping notification: Transfer item data from IDOC
LMEQR001 User exit for source determination
LMEXF001 Conditions in Purchasing Documents Without Invoice Receipt
LWSUS001 Customer-Specific Source Determination in Retail
M06B0001 Role determination for purchase requisition release
MEFLD004 Determine earliest delivery date f. check w. GR (only PO)
MEETA001 Define schedule line type (backlog, immed. req., preview)
ME590001 Grouping of requsitions for PO split in ME59
M06E0005 Role determination for release of purchasing documents
M06E0004 Changes to communication structure for release purch. doc.
M06B0005 Changes to comm. structure for overall release of requisn.
M06B0004 Number range and document number
M06B0003 Number range and document number
M06B0002 Changes to comm. structure for purchase requisition release
Business Add-in - BADI
ME_PROCESS_REQ Enhancements for Processing Enjoy PReqs: Internal
ME_PROCESS_PO_CUST Enhancements for Processing Enjoy Purchase Order: Customer
ME_PROCESS_PO Enhancements for Processing Enjoy Purchase Order: Intern.
ME_PROCESS_COMP Processing of Component Default Data at Time of GR: Customer
ME_PO_SC_SRV BAdI: Service Tab Page for Subcontracting
ME_HOLD_PO Hold Enjoy Purchase Orders: Activation/Deactivation
ME_GUI_PO_CUST Customer's Own Screens in Enjoy Purchase Order
ME_DEFINE_CALCTYPE Control of Pricing Type: Additional Fields
ME_COMMTMNT_REQ_RE_C Check of Commitment Relevance of Purchase Requisitions
ME_COMMTMNT_REQ_RELE Check of Commitment Relevance of Purchase Requisitions
ME_PROCESS_REQ_CUST Enhancements for Processing Enjoy PReqs: Customer
ME_PURCHDOC_POSTED Purchasing Document Posted
ME_RELEASE_CREATE BAdI: Release Creation for Sched. Agreemnts with Rel. Docs
ME_REQ_OI_EXT Commitment Update in the Case of External Requisitions
ME_REQ_POSTED Purchase Requisition Posted
ME_TAX_FROM_ADDRESS Tax jurisdiction code taken from address
ME_TRIGGER_ATP Triggers New ATP for Changes in EKKO, EKPO, EKPV
MM_EDI_DELFOR_OUT Enhancements for IDoc Output of SA Releases: Internal
MM_EDI_DESADV_IN Supplementation of Delivery Interface from Purchase Order
MM_EDI_ORDERS_OUT Enhancements for IDoc Output of Purchase Order: Internal
SMOD_MRFLB001 Control Items for Contract Release Order
ME_COMMTMNT_PO_REL_C Check for Commitment-Relevance of Purchase Orders
EXTENSION_US_TAXES Extended Tax Calculation with Additional Data
MEGUI_LAYOUT BAdI for Enjoy Purchasing GUI
ME_ACTV_CANCEL_PO BAdI for Activating the Cancel Function at Header Level
ME_BAPI_PR_CHANGE_01 BAdI: Enjoy BAPIs for Purchase Requisitions (Method Change)
ME_BAPI_PR_CHANGE_02 BAdI: Enjoy BAPIs for Purchase Requisitions (Method Change)
ME_BAPI_PR_CREATE_01 BAdI: Enjoy BAPIs for Purchase Requisitions
ME_BAPI_PR_CREATE_02 BAdI: Enjoy BAPIs for Purchase Requisitions (Method Create)
ME_BSART_DET Change document type for automatically generated POs
ME_CCP_ACTIVE_CHECK BAdI to check whether CCP process is active
ME_CCP_BESWK_AUTH_CH BAdI for authorization checks for procuring plant
ME_CCP_DEL_DURATION Calc. of Delivery Duration in CCP Process (Not in Standard)
ME_CHANGE_CHARACTER Customer-Specific Characteristics for Product Allocation
ME_CHECK_ALL_ITEMS Run Through Items Again in the Event of Changes in EKKO
ME_CHECK_SOURCES Additional Checks in Source Determination/Checking
ME_CIN_LEINRF2R BADI for CIN India - Delivery charges
ME_CIN_LEINRF2V BADI for LEINRF03 excise_invoice_details
ME_CIN_MM06EFKO Copy PO data for use by Country version India
ME_CIP_ALLOW_CHANGE Configuration in Purchasing: Changeability Control
ME_CIP_REF_CHAR Facilitates Reference Characteristics in Purchasing
ME_COMMITMENT_STO_CH BadI for checking if commitments for STOs are active
ME_COMMTMNT_PO_RELEV Check for Commitment-Relevance of Purchase Orders
Reward points
Regards

User Exit for VA01 - Delivery Block

Dear Friends
I wanted to do a User Exit for VA01 which should set the Delivery Block = Credit Memo as default for a particular user.
Can anyone give me the solution.
REg
S.K.Raj

Hi Kamaraj,
First of all u have to find out the perticular exit for make the changes, after that take one field TBTKZ which is flag for decit /credit memo. Based on the condition that flag set as 'X'. If that flag set as 'X' then populate the data.
Here it ishow to find out the user exit.
execute the following report and enter the t-code VA01 it will display all the exits. then search them by seeing coments..
report zuserexit no standard page heading.
tables : tstc, tadir, modsapt, modact, trdir, tfdir, enlfdir.
         tables : tstct.
data : jtab like tadir occurs 0 with header line.
data : field1(30).
data : v_devclass like tadir-devclass.
parameters : p_tcode like tstc-tcode obligatory.
select single * from tstc where tcode eq p_tcode.
if sy-subrc eq 0.
   select single * from tadir where pgmid = 'R3TR'
                    and object = 'PROG'
                    and obj_name = tstc-pgmna.
   move : tadir-devclass to v_devclass.
      if sy-subrc ne 0.
         select single * from trdir where name = tstc-pgmna.
         if trdir-subc eq 'F'.
            select single * from tfdir where pname = tstc-pgmna.
            select single * from enlfdir where funcname =
            tfdir-funcname.
            select single * from tadir where pgmid = 'R3TR'
                               and object = 'FUGR'
                               and obj_name eq enlfdir-area.
            move : tadir-devclass to v_devclass.
          endif.
       endif.
       select * from tadir into table jtab
                     where pgmid = 'R3TR'
                       and object = 'SMOD'
                       and devclass = v_devclass.
        select single * from tstct where sprsl eq sy-langu and
                                         tcode eq p_tcode.
        format color col_positive intensified off.
        write:/(19) 'Transaction Code - ',
             20(20) p_tcode,
             45(50) tstct-ttext.
                    skip.
        if not jtab[] is initial.
           write:/(95) sy-uline.
           format color col_heading intensified on.
           write:/1 sy-vline,
                  2 'Exit Name',
                 21 sy-vline ,
                 22 'Description',
                 95 sy-vline.
           write:/(95) sy-uline.
           loop at jtab.
              select single * from modsapt
                     where sprsl = sy-langu and
                            name = jtab-obj_name.
                   format color col_normal intensified off.
                   write:/1 sy-vline,
                          2 jtab-obj_name hotspot on,
                         21 sy-vline ,
                         22 modsapt-modtext,
                         95 sy-vline.
           endloop.
           write:/(95) sy-uline.
           describe table jtab.
           skip.
           format color col_total intensified on.
           write:/ 'No of Exits:' , sy-tfill.
        else.
           format color col_negative intensified on.
           write:/(95) 'No User Exit exists'.
        endif.
      else.
          format color col_negative intensified on.
          write:/(95) 'Transaction Code Does Not Exist'.
      endif.
at line-selection.
   get cursor field field1.
   check field1(4) eq 'JTAB'.
   set parameter id 'MON' field sy-lisel+1(10).
   call transaction 'SMOD' and skip first   screen.
Hope this helps you..
Regards,
Kumar.

CS - User Exit for initial checking for t-code IH10

Hi all expert,
I am new to CS, I want to know is there any user exit for CS, which can write my own authority check in the t-code IH10
(Display Equipment: Equipment selection)
I want to add a authority group in the Customer master, so that when using IH10, it check the customer's authority group whether the user have right to view the equipment which belongs to the customer.
Thanks.
Terry

Hi,
Its a std report, My suggestion would be not to disturb the current report, instead create your own report could be copy of IH10 & make the changes as required.
Goto: OIAG to create your own authorization group ( make this field as mandatory while executing)
find the free field in Customer Master Data ( if customer reserve fields are available- not reserved for any other purpose, you can use those fields for the same), map this field to "Authorization Group" field in ZIH10 ( Copy of IH10).
Through work around , hope you will achieve this.
Check with the abaper for the feasibility of the above suggetion.
Regards,
Reazuddin MD

How to find user exits for a specific field

hi,
 How can we find a user exit for a specific fields .
as i know Three ways to search user-exits
1. SE80 look includes in a packages with name user-exits
2. by zreport which will fetch user-exit in a T-CODE
3. SMOD
but what if we have to find a user-exit for particular field for e.g bupla(bussiness place) in MIRO.
Please suggest me.
Thanks and Regards ,
Rahul Singh.

Hi Rahul,
Here is the procedure to create field exits.
Step by step procedure for creating Field Exits
There are eight steps to creating a field exit:
Step 1: Determine Data Element
Step 2: Go To Field Exit Transaction
Step 3: Create Field Exit
Step 4: Create Function Module
Step 5: Code Function Module
Step 6: Activate Function Module
Step 7: Assign Program/Screen
Step 8: Activate Field Exit
Step 1: Determine Data Element
u2022 Before you can begin adding the functionality for a field exit, you must know the corresponding data element.
Step 2: Go To Field Exit Transaction
u2022 The transaction to create field exits is CMOD.
u2022 You can use the menu path Tools -> ABAP/4 Workbench -> Utilities -> Enhancements -> Project management.
u2022 From the initial screen of transaction CMOD, choose the Text enhancements -> Field exits menu path.
u2022 After choosing this menu path, you will be taken to the field exits screen. From here, you can create a field exit.
NOTE : Even though you use transaction CMOD to maintain field exits, you do not need to create a project to activate field exits.
Step 3: Create Field Exit
u2022 From the field exit screen of transaction CMOD, choose the Field exit -> Create menu path.
u2022 After choosing this menu path, a dialog box will prompt you for the appropriate data element .
u2022 Enter the data element name and click the u2018Continueu2019 pushbutton.
u2022 Now, you will be able to create the function module associated to the data elementu2019s field exit.
Step 4: Create Function Module
u2022 You will automatically be taken to the Function Library (SE37) after entering a data element name and clicking the u2018Continueu2019 pushbutton.
u2022 In the u2018Function moduleu2019 field, a function module name will be defaulted by the system based on the data element specified. This name will have the following convention:
FIELD_EXIT_<data element>
u2022 You can add an identifier (an underscore followed by a single character ).
u2022 The first function module for a data elementu2019s field exit must be created without an identifier.
u2022 To create the function module, click on the u2018Createu2019 pushbutton, choose menu path Function module -> Create, or press u2018F5u2019.
u2022 After choosing to create the function module, you will get the warning: "Function module name is reserved for SAP". This message is just a warning so a developer does not accidentally create a function module in the field exit name range. By pressing u2018Enteru2019, you will be able to go ahead and create the function module.
u2022 Before coding the function module, you will have to specify the function modules attributes -- function group, application, and short text.
Step 5: Code Function Module
u2022 From the function moduleu2019s attributes screen, click on the u2018Source codeu2019 pushbutton or choose the Goto -> Function module menu path to the code of the function module.
u2022 Here you will add your desired functionality for the field exit.
u2022 Remember that field exitu2019s function module will have two parameters -- one importing parameter called "INPUT" and one exporting parameter called "OUTPUT". These parameters will be set up automatically by the system.
u2022 You must remember to assign a value to the OUTPUT field. Even if the value does not change, it must be moved from the INPUT field to the OUTPUT field.
Step 6: Activate Function Module
u2022 After coding the function module, you must remember to activate it.
u2022 Use the Function module -> Activate menu path to activate the function module.
u2022 At this point, you can return to the field exit transaction.
u2022 You should be able to 'green arrow' back to this transaction.
u2022 When you return to the field exit transaction, you will see an entry for the newly created field exit.
u2022 At this point, the field exit is global. That is, it applies to all screens that use a particular data element. On any screen that uses the data element, the corresponding field exit function module will be triggered, once it is active.
u2022 Also, the field exit will not be triggered yet because it is inactive.
Step 7: Assign Program/Screen
u2022 This step is only needed if you want to make a field exit local.
u2022 To make a field exit local, select the field exit and click on the u2018Assign prog./screenu2019 pushbutton.
u2022 In the dialog box , indicate the appropriate program name and screen number.
This information indicates that the field exit is local to the specified screen in the specified program.
u2022 In the dialog box, you determine which function module gets executed for the field exit by specifying the identifier in the u2018Fld. Exitu2019 field.
u2022 If this field is left blank, the function module triggered will be 'FIELD_EXIT_<data element>'.
u2022 If a single-character identifier is entered into the field, the function module triggered will be 'FIELD_EXIT_<data element>_<identifier>'.
Step 8: Activate Field Exit
u2022 The field exit must be active for it to be triggered by the system.
u2022 Activate the field exit by choosing the Field exit -> Activate menu path.
u2022 After assigning the field exit to a change request, its status will change to u2018Activeu2019 and it will be triggered automatically on the appropriate screen(s).
NOTE : In order to activate the field exit the profile parameter abap/fieldexit = YES must be set on all application servers
Execute the transaction SE38 with PROGRAM NAME - RSMODPRF
Then give the Data Element Name for which field you want to create the exit(Just cross check with your field data element) and execute.
then it takes you to SE37 with the function module name FIELD_EXIT_<DATA ELEMENT NAME> and then create the same function module.
and in the coding part, You can write your logic to display the output of that field. and activate it.
once you complete the above,
Again execute SE38 transaction with program RSMODPRF and again click on Execute button without any Data Element Name. Now you select the data element which you have created and click on Assign prog/ Screen button and assign the program name and screen number of the filed and click on the menu Field Exit and Activate.
Hope it helps.
Regards
Radhika
Edited by: Radhika Pande on Nov 26, 2009 7:58 AM

User exit for IW31 which capture screen field Po number

Similar Messages

Maybe you are looking for