BADI / user exit for Tcode IW32?

Hi
Are there any BADIs / user exits for changing component data in Transaction IW32 for a maintainance order?
regards
cs

Enhancement
IWO10012                                Maintenance order: Priority handling on central header
Business Add-in
IWO_UI_USEFLEX                          BAdI for Calling Up an Alternative UI
I hope it helps.
Best Regards,
Vibha
Please mark all the helpful answers

Similar Messages

BADI / USER-EXIT FOR DEFAULTING THE FIELD VTTK-TNDR_ACTC IN TCODE VT01N

Hi,
I require a BADI / USER-EXIT for defaulting the field VTTK-TNDR_ACTC(Currency of Actual Shipment costs) to 'EUR' in transaction VT01N(Shipment Transaction) .
Please could anyone help me with this .
Regards,
Sushanth H.S.

Hi!
User Exits in Transportation
In Transportation, there are enhancements that you can use with transaction CMOD.
For a detailed description of the individual enhancements, see the documentation on the individual enhancements or function modules in transaction SMOD.
You can display all enhancements that are available for the area of transportation by choosing F4 in the Enhancement field. Enter V56* in the Enhancement field and choose Execute. Enter V54* to get a list of all enhancements for the area of shipment cost processing.
Business Add-Ins in the transports
Business add-ins (BADIs) are predefined user exits. They enable businesses, partners, and customers to add additional softward to the SAP source code. The linkup of SAP's New Dimension Products, such as APO and BW, to the standard system is thus possible.
Customer-specific functions can be executed before the save time and after the database update.
The following methods are available for the BADI with the definition name 'BADI_LE_SHIPMENT':
AT_SAVE: BADI is called up at the time of the save. Checks and return to dialog are possible.
BEFORE:_UPDATE: BADI is called up right before the data is saved to the database, that is, when all the data is available (for example, internal ly assigned shipment number).
IN_UPDATE: BADI is called up after the database update.
Standard Settings
Creating a BADI method:
Call up transaction SE19. Enter a name of your choice. Choose "create" and in the dialog box enter the definition name 'BADI_LE_SHIPMENT'. Afterwards, enter a short text for implementation. Save the BADI.
On the tab page 'Interface', choose the method for implementation by double-clicking on it. Now you can enter your customer-specific program code. Save and activate the code. You can acess the transmission parameters entered in the BADI definition. With the method ***_AT_SAVE you can initiate the exception ERROR_WITH_MESSAGE (description 'An error message has occurred' ) if you wish to return to the dialog.
Afterwards, go to the heading and activate the interface.
Regards
Tamá

BADI/User Exit for KO02

Dear Experts,
When I'm setting the BUDGETED status manually to Internal Order (With out distributing the Budget to Order in IM52) and after if I m setting RELEASE status the system is accepting. So, I want to stop this without giving the budget in IO, it should not accept to release IO.
This is not possible with User Status, coz' User may go and set manually "REL" Status.
can anyone suggest me the BAdi/User Exit for KO02(Internal Order Change) tcode.
Thanks,
Sanju.

When you set a User status , you can assign an Authorization Object on who can change the status .
Follow the path in SPRO--> Controlling --> Internal orders --> Order Master Data > Status Management> Define authorization Keys for Status Management
Define Authorization Keys for Status Management
In this step you define authorization keys which you can use to set up authorization checks when you manually set or delete a user status. When the system sets a user status as a reaction to business transaction, it does not perform an authorization check.
When you set or delete a user status, the system checks whether the user is authorized for this action. In addition to the status profile and the object type, the system also checks the authorization key assigned to the user status in question.
Example
You want to define that certain user statuses can be changed only by a specified employee group.
To do this, create an authorization key and assign it to the relevant user statuses.
In the general authorization maintenance you can then assign authorizations for this key via the authorization object B_USERSTAT.
Activities
1. Check whether you want to define authorizations for your user statuses.
2. If necessary, create authorization keys as follows:
a) Choose "New entries".
b) Enter a key and an explanatory text in the appropriate fields and choose "Save".
You have now created the authorization key.
3. Assign the authorization key to one or more user statuses in your status profile.
4. Define corresponding authorizations and include them in the relevant authorization profiles.

User Exit for TCode CJ20N to populate Project system user fields

Hi team,
need one support from your side..
I am looking for User Exit for TCode CJ20N to populate Project system user fields on SAVE.
I have found
Enhancement CNEX0001
Short text PS: User field
which is exactly suiting my req...as it has USER Fields (USR08/USR09 )in export paramters..
BUT it is not triggering on SAVE,,
Any hint or is any other user exit/badi which have USER Fields in export paramters.
Warm Regards
Krishan

Hi Krishnan,
If you want a custom tab that contains User defined fields at Project level then you have to use CNEX0006 user exit. Before this you must declare your fields using the CI include CI_PROJ in the PROJ table.
If you want a custom tab that contains User defined fields at WBS level then you have to use CNEX0007 user exit. Before this you must declare your fields using the CI include CI_PRPS in the PROJ table.
In the PBO function module exit of these exits you must use the following statements as the first statement.
MOVE-CORRESPONDING sap_proj_imp TO proj.
MOVE-CORRESPONDING sap_prps_imp TO prps.
In the PAI function module exit of these exits you must use the following statement as the last statement.
MOVE-CORRESPONDING proj TO cnci_proj_exp.
MOVE-CORRESPONDING prps TO cnci_prps_exp.
The remaining programming as in the case any Screen Exit.
Regards,
Abijith

BADI/USER EXIT for IW21 & IW22

Hi all,
Pls post me the correct BADI and USER EXIT for Tcode IW21 & IW22.
FYI
My req'ment is to do an enhancement to check the user level for releasing/issue permitting orders.User level should be assigned to the respective person to release the FLAG and not by all.
Pls comment.
thanks & regards
sankar

Hi,
IWO10026            User check on setting status 'Do not perform'
IWO10027            User exit: Generate user-defined settlement rule
IWOC0001            Create PM/SM notification: Determine reference object
IWOC0002            PM/SM notification: Check whether status change is allowed
IWOC0003            PM/SM authorization check of ref. object and planner group
IWOC0004            Change single-level list editing PM/QM/SM ALV settings
Regards,
Pankaj

BADI/ User Exit for transaction FTR_EDIT/FTR_CREATE initial screen

Hi All,
I want a BADI/User Exit for FTR_EDIT/FTR_CREATE transactions to validate company code and partner fields.
please provide your suggestions.

Hi,
here is a coding example that I implemented in the BAdI FTR_TR_GENERIC. This coding is executed when the user press the check button. The method is EVT_TRANSACTION_CHECK. This example is checking the payment date dfaell if it is equal to the system date. If not then a message is sent to the message handler. Here is the code:
DATA: faelligkeit TYPE d,
        faelligkeit_text type c length 10,
        meldungstext TYPE c LENGTH 100.
FIELD-SYMBOLS: <it_source> LIKE LINE OF pi_proxy_transaction->a_tab_conditions.
IF sy-uname = 'XYZ'.
*    BREAK-POINT.
    READ TABLE pi_proxy_transaction->a_tab_conditions INDEX 1
      ASSIGNING <it_source>.
    faelligkeit = <it_source>-dfaell.
    CALL FUNCTION 'CONVERT_DATE_TO_EXTERNAL'
       EXPORTING
         DATE_INTERNAL                  = faelligkeit
       IMPORTING
         DATE_EXTERNAL                  = faelligkeit_text
       EXCEPTIONS
         DATE_INTERNAL_IS_INVALID       = 1
         OTHERS                         = 2
    IF sy-subrc <> 0.
       MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    IF faelligkeit <> sy-datum.
      CONCATENATE 'Fälligkeit' faelligkeit_text 'incorrect' INTO meldungstext separated by space.
      CALL METHOD pi_proxy_messages->set_message
        EXPORTING
          pi_message_id       = 'T0'
          pi_message_number   = '101'
          pi_message_severity = 'E'
          pi_message_var1     = meldungstext
        EXCEPTIONS
          OTHERS              = 4.
    ENDIF.
ENDIF.
It is not a really nice coding but it shows in a simple way how to use the BAdI.
Regards
Robert

BADI/ User Exit for transaction FTR_EDIT/FTR_CREATE

Hi All,
I want a BADI/User Exit for FTR_EDIT/FTR_CREATE transactions to validate company code and partner fields.

Hi,
here is a coding example that I implemented in the BAdI FTR_TR_GENERIC. This coding is executed when the user press the check button. The method is EVT_TRANSACTION_CHECK. This example is checking the payment date dfaell if it is equal to the system date. If not then a message is sent to the message handler. Here is the code:
DATA: faelligkeit TYPE d,
        faelligkeit_text type c length 10,
        meldungstext TYPE c LENGTH 100.
FIELD-SYMBOLS: <it_source> LIKE LINE OF pi_proxy_transaction->a_tab_conditions.
IF sy-uname = 'XYZ'.
*    BREAK-POINT.
    READ TABLE pi_proxy_transaction->a_tab_conditions INDEX 1
      ASSIGNING <it_source>.
    faelligkeit = <it_source>-dfaell.
    CALL FUNCTION 'CONVERT_DATE_TO_EXTERNAL'
       EXPORTING
         DATE_INTERNAL                  = faelligkeit
       IMPORTING
         DATE_EXTERNAL                  = faelligkeit_text
       EXCEPTIONS
         DATE_INTERNAL_IS_INVALID       = 1
         OTHERS                         = 2
    IF sy-subrc <> 0.
       MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    IF faelligkeit <> sy-datum.
      CONCATENATE 'Fälligkeit' faelligkeit_text 'incorrect' INTO meldungstext separated by space.
      CALL METHOD pi_proxy_messages->set_message
        EXPORTING
          pi_message_id       = 'T0'
          pi_message_number   = '101'
          pi_message_severity = 'E'
          pi_message_var1     = meldungstext
        EXCEPTIONS
          OTHERS              = 4.
    ENDIF.
ENDIF.
It is not a really nice coding but it shows in a simple way how to use the BAdI.
Regards
Robert

BADI/User Exit for custom table update from Delivery

Hi
Our requirement is to update a custom table with the delivery number and other related details when the picking status is changed to "C". Kindly suggest BADI/User exit for this requirement .
Thanks in Advance for your immediate help .

Hi Joseph,
See SAP Note 415716 - User exits in delivery processing. It says when you have the document number available, what is permitted, what not, ....
I hope this helps you
Regards
Eduardo

BADI / User exit for Purchase order(ME21N) after saving the document

Hi expert,
I need the BADI / User exit for Purchase order(ME21N) after saving the document
This is for email sending after create the purchase order so PO document number will be the import parameter
pls help me
point will be reward
Regards,
Ganesh

Hi Ganesh,
Could you please share your solution?
Thanks.
Hoops
Edited by: Hoops on Jun 13, 2011 10:51 PM

User exits for Tcode FCH5

May any one of you plz suggest me any userexits for tcode fch5.
i want to restrict the field of account id for validation.
how can i do this.
waiting for your reply.

Hi Pawan,
U can use this program to find user exit for Tcode FCH5
Find User exit for Tcode
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.
Rgds,
Prakash

Badi or User-Exit for TCode-oawd

Hi All,
Please help me out with a BADI or EXIT for the Tcode - OAWD (Store Documents) .As per our requirement, while executing OAWD, after the step - work item created, we want to add a pop-up which will take us to tcode- SBWP.
Any help will be highly appreciated .
Thanks/Regards
Priya

Hi
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.
This will solve your BADI finding problem in future as well !!
Mark if helpful
Regs,
Tushar Mundlik

Badi/User Exit for VF01

Hi Experts,
Please understand my issue/requirement that, I have to make the item conditions tab in display or deactivate mode to prevent users to change or create the price or conditions while posting VF01.
As std, system allows users to create or change the prices/qts and also add new conditions. My client needs to make it as display mode for all type of postings in VF01.
Please guide me, how to arrive it through Exit or Enhancements.
thanks & regards
Sankar.

Hi,
Try these steps to find the BADI.
1. Go to the TCode SE24 and enter CL_EXITHANDLER as object type.
2. In 'Display' mode, go to 'Methods' tab.
3. Double click the method 'Get Instance' to display it source code.
4. Set a breakpoint on 'CALL METHOD cl_exithandler => get_class_name_by_interface'.
5. Then run your transaction.
6. The screen will stop at this method.
7. Check the value of parameter 'EXIT_NAME'. It will show you the BADI for that transaction.
These are exits in VF01.
SDVFX001            User exit header line in delivery to accounting
SDVFX002            User exit for A/R line in transfer to accounting
SDVFX003            User exit cash clearing in transfer to accounting
SDVFX004            User exit G/L line in transfer to accounting
SDVFX005            User exit reserves in transfer to accounting
SDVFX006            User exit tax line in transfer to accounting
SDVFX007            User exit: Billing plan during transfer to Accounting
SDVFX008            User exit: Processing of transfer structures SD-FI
SDVFX009            Billing doc. processing KIDONO (payment reference number)
SDVFX010            User exit item table for the customer lines
SDVFX011            Userexit for the komkcv- and kompcv-structures
V05I0001            User exits for billing index
V05N0001            User Exits for Printing Billing Docs. using POR Procedure
J_3RSINV            User Exits for Printing Billing Docs. using POR Procedure
V60A0001            Customer functions in the billing document
V60P0001            Data provision for additional fields for display in lists
V61A0001            Customer enhancement: Pricing
Hope this helps u.
Thanks.

BADI/User exit for ME18 to specifically check for Approval Level...

Hi all,
I hope this is not a repost. I have found none so far in SDN forum. However if do, please point it to me. I will gladly close this thread.
Ok, i need a userexit/badi, whichever will do, to check for user approval levels in ME18.
So far I couldn't find a user exit/Badi that is suitable in my SAP system using SMOD and the program that find user exit by TCODE.
I hope SAP do provide a user exit that can actually check for user Approval Level in ME18.
Can anyone share this info on this issue?
Thanks,
William Wilstroth

There are few enhancement points available for ME18. Please check them once.
Thanks,
Srinivas

BADI/User-Exit for MD14

Hi,
Our client wants to update certain data in PR while the PRs are created from Planned orders or after a PR is created from a Planned order.
I've implemented BADI MD_PURREQ_CHANGE but while testing, the debugger is not taking to the break point.
Thus it appears that this BADI is not applicable for MD14.
I need a BADI/User exit where I can change the material description in PR.
Please help.Helpful answers shall be rewarded.

Hi abhijit,
Check this program.You will get all exits for a transaction.
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.

User exit for tcode ME9A

Hi Guys,
Im trying to add custom error message for tcode ME9A. Is there any user exits or badi available to do this? Thanks.

hi,
copy the below code and in the selection screen enter the T-code..
it will help for you not only for htis t-code to find user exists it will help for all T-codes..
*& 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
&----Validate Transaction Code
Find Repository Objects for transaction code
Find SAP Modifactions
Take the user to SMOD for the Exit that was selected.
*& 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.
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 = 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.
and the user eixists are
Transaction Code - ME9A                     Message Output: RFQs
Exit Name           Description
AMPL0001            User subscreen for additional data on AMPL
LMEDR001            Enhancements to print program
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
M06B0002            Changes to comm. structure for purchase requisition release
M06B0003            Number range and document number
M06B0004            Number range and document number
M06B0005            Changes to comm. structure for overall release of requisn.
M06E0004            Changes to communication structure for release purch. doc.
M06E0005            Role determination for release of purchasing documents
ME590001            Grouping of requsitions for PO split in ME59
MEETA001            Define schedule line type (backlog, immed. req., preview)
MEFLD004            Determine earliest delivery date f. check w. GR (only PO)
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
No of Exits:         36
Regards,
Prabhudas

BADI / user exit for Tcode IW32?

Similar Messages

Maybe you are looking for