Need User-Exists in HR Module

Hai,
I need all list of User-Exists available for HR module with transaction wise. I am collecting these for Built a database.
Please forward if you have or if you know any web links, or documents or any type source i wellcome,
Thanks,
Elamaran
mail-id:  [email protected]

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.

Similar Messages

  • Need User Exists

    Hello Friends,
    i need User Exists for PR,PO,MIGO,MIRO Creation transactions , i need to save data in one Custom table for all these transactions. so that i can details for purchase life cycle from refering the single table . i donot require to refer all other tables.
    similar way for SD Transactions ,,
    if any of you came across these type of  reqirement, just guide me
    Thanks and Regards
    Kumar M

    Hi,
    Migo User exits:
    Enhancement/ Business Add-in            Description                                                                               
    Enhancement                                                                               
    MB_CF001                                Customer Function Exit in the Case of Updating a Art. 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                                Article document item for goods receipt/issue slip             
    MBCF0002                                Customer function exit: Segment text in article doc. item                                                                               
    Business Add-in                                                                               
    MB_RESERVATION_BADI                     MB21/MB22: Check and Complete Dialog Data                      
    MB_QUAN_CHECK_BADI                      BAdI: Item Data at Time of Quantity Check                      
    MB_PHYSINV_INTERNAL                     Connection: Core Inventory and Retail AddOn                    
    MB_MIGO_ITEM_BADI                       BAdI in MIGO for Changing Item Data                            
    MB_MIGO_BADI                            BAdI in MIGO for External Detail Subscreens                    
    MB_DOC_BADI_INTERNAL                    BAdIs when Creating an Article Document (SAP Internal)         
    MB_DOCUMENT_UPDATE                      BADI when updating article document: MSEG and MKPF             
    MB_DOCUMENT_BADI                        BAdIs when Creating an Article Document                        
    MB_CIN_MM07MFB7_QTY                     Proposal of quantity from Excise invoice in GR                 
    MB_CIN_MM07MFB7                         BAdI for India Version exit in include MM07MFB7                
    MB_CIN_LMBMBU04                         posting of gr                                                  
    MB_CHECK_LINE_BADI                      BAdI: Check Line Before Copying to the Blocking Tables         
    ARC_MM_MATBEL_WRITE                     Check Add-On-Specific Data for MM_MATBEL                       
    ARC_MM_MATBEL_CHECK                     Check Add-On-Specific Criteria for MM_MATBEL       
    Miro userexits:
    Enhancement/ Business Add-in            Description                                                                               
    Enhancement                                                                               
    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                                                                               
    Business Add-in                                                                               
    INVOICE_UPDATE                          Business Add-In: Logistics Invoice Verification                                                                               
    PO userexits:
    Enhancement/ Business Add-in            Description                                                                               
    Enhancement                                                                               
    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                             
    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                       
    MELAB001                                Gen. forecast delivery schedules: Transfer schedule implem.    
    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    
    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                                                                               
    Business Add-in                                                                               
    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_MMPUR_EINM_CUST                      BAdI Methods for Processing IDoc Data in the SUS Scenario      
    ME_MMPUR_EINM                           BAdI Methods for Processing IDoc Data in the SUS Scenario      
    ME_HOLD_PO                              Hold Enjoy Purchase Orders: Activation/Deactivation            
    ME_GUI_PO_CUST                          Customer's Own Screens in Enjoy Purchase Order                 
    ME_FIELDSTATUS_STOCK                    FM Account Assignment Behavior for Stock PR/PO                 
    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_COMMTMNT_PO_REL_C                    Check for Commitment-Relevance of Purchase Orders              
    ME_PROCESS_PO_CUST                      Enhancements for Processing Enjoy Purchase Order: Customer     
    EXTENSION_US_TAXES                      Extended Tax Calculation with Additional Data                  
    MM_EDI_ORDERS_OUT                       Enhancements for IDoc Output of Purchase Order: Internal       
    MM_EDI_DESADV_IN                        Supplementation of Delivery Interface from Purchase Order      
    MM_EDI_DELFOR_OUT                       Enhancements for IDoc Output of SA Releases: Internal          
    ME_TRIGGER_ATP                          Triggers New ATP for Changes in EKKO, EKPO, EKPV               
    ME_TAX_FROM_ADDRESS                     Tax jurisdiction code taken from address                       
    ME_REQ_POSTED                           Purchase Requisition Posted                                    
    ME_REQ_OI_EXT                           Commitment Update in the Case of External Requisitions                                                                               
    ME_PURCHDOC_POSTED                      Purchasing Document Posted1                                    
    ME_PROCESS_REQ_CUST                     Enhancements for Processing Enjoy PReqs: Customer              
    ME_PROCESS_REQ                          Enhancements for Processing Enjoy PReqs: Internal              
    ME_COMMTMNT_PO_RELEV                    Check for Commitment-Relevance of Purchase Orders              
    ME_BSART_DET                            Change document type for automatically generated POs           
    ME_BAPI_PR_IBS                          BAdI: Enjoy BAPIs for Purchase Requisitions                    
    ME_BAPI_PR_CUST                         Customer BAdI for Enjoy Purchase Requisition BAPIs             
    ME_BAPI_PR_CREATE_02                                                                               
    ME_BAPI_PR_CREATE_01                                                                               
    ME_BAPI_PO_IBS                          BAdI for Inbound/Outbound Mapping BAPI_PO_CREATE1 IBS          
    ME_BAPI_PO_CUST                         Customer BAdI for BAPI_PO_CREATE1 and BAPI_PO_CHANGE           
    ME_BAPI_PO_CREATE_02                                                                               
    ME_BAPI_PO_CREATE_01                                                                               
    ME_ACTV_CANCEL_PO                       BAdI for Activating the Cancel Function at Header Level        
    MEGUI_LAYOUT                            BAdI for Enjoy Purchasing GUI                                  
    SMOD_MRFLB001                           Control Items for Contract Release Order                       
    ME_CCP_ACTIVE_CHECK                     BAdI to check whether CCP process is active                    
    ME_COMMITMENT_STO_CH                    BadI for checking if commitments for STOs are active           
    ME_CIP_REF_CHAR                         Facilitates Reference Characteristics in Purchasing            
    ME_CIP_ALLOW_CHANGE                     Configuration in Purchasing: Changeability Control             
    ME_CIN_MM06EFKO                         Copy PO data for use by Country version India                  
    ME_CIN_LEINRF2V                         BADI for LEINRF03 excise_invoice_details                       
    ME_CIN_LEINRF2R                         BADI for CIN India - Delivery charges                          
    ME_CHECK_SOURCES                        Additional Checks in Source Determination/Checking             
    ME_CHECK_ALL_ITEMS                      Run Through Items Again in the Event of Changes in EKKO        
    ME_CHANGE_OUTTAB                        Enrich ALV Output Table in Purchasing                          
    ME_CHANGE_CHARACTER                     Customer-Specific Characteristics for Product Allocation       
    ME_CCP_DEL_DURATION                     Calc. of Delivery Duration in CCP Process (Not in Standard)    
    ME_CCP_BESWK_AUTH_CH                    BAdI for authorization checks for procuring site                                                                               
    If these helpful rewards points
    Regards
    Pratap.M

  • Need user exist?

    Hello, 
    Need user exist in RFFOEDI1 to create custom segment to populate some  fileds.
    If any one done this type requirement please let me know the user exist.
    Thanks,
    chinna

    Hi,
    This way you can find any user exit:
    1. Go to the program 'RFFOEDI1'. Get the package name from the program attributes.
    2. Go to tcode 'SMOD'
    3. Enter the package name of that program and execute.
    You will get the list of exits available for that package. Based on its description and documentation of each exit you can identify which exit will be useful for you.
    Regards,
    Saba

  • SELECTs in user exists (P/S modules)

    Hi,
    I am implementing user exist triggered when an accounting document is posted ... P/S event no. 00001030. The problem is, that I need to read some records from BSID table ... this event is triggered right before a commit is executed, therefore I suppose that all database changes are already made, but not commited yet. Anyway, I've tried to read these database rows (in the same database transaction), but SELECT does not fetch any row! I know how database servers works, what are database sessions and database transactions ... I thought SAP system works in the same way ...
    Can anybody explain me why ABAP does not see uncommited rows inserted by the same database session/transaction? Is there a way how to read these rows? I already tried to call my function by PERFORM ON COMMIT, ... same results ... also by CALL FUNCTION IN UPDATE TASK ... same results ...
    Is there any sensible way how to read desired uncommited records?

    Hi,
    Check while debugging where BSID table have those values or not.If yes then BSID table should declare in Table fields.If not then you need to dynamically assign the value of table to your workarea.
    Below is the code which might help you:
    Get the Name field enetered on Fb01 screen
      ASSIGN ('(SAPMF05A)BSEC') TO <fs>.
      wa_bsec = <fs>.
    I hope it would help you.
    Regards,
    Swati

  • Cj12 User Exist and Badi's

    Hi Experts,
    As per my bussiness requirement , I need user exist or Badi requied for a Transaction Code CJ12.
    In Transaction Code CJ12 , when i select system/user  status button click , another window will come , in that I have status with status no screen, any radio button select then the below screen Status w/o status no screen , as per my requirement radio button select.
    This is my requirment , I have to satisfy the two condition . So please help me on this which user exist or badi's are avilable for this Tcode CJ12.
    Advance Thank you.
    Thank You
    Srinu

    Srinu,
    this is the program SAPLCJWB fro CJ12.
    open the program and look for call customer-function that displays all the user exits
    Thanks
    Bala Duvvuri

  • How to capture the User input value to user exist function module.

    Hi,
    How can i capture user input value.Here i am using User exist in BPS variable.
    Calculating days using user exist functin module and my input is another variable i.e user defined value.
    How can i capture user defined vaule into my function module.
    This is very urgent can you help me..
    Thanks....

    Hi!
    You can get the instance using the method get_instance of the class cl_sem_variable, and call the method get_value with the return. Check the example:
          CALL METHOD cl_sem_variable=>get_instance
            EXPORTING
              i_area       = (planning area)
              i_variable   = (variable name)
            RECEIVING
              rr_variable  = lr_var
            EXCEPTIONS
              not_existing = 1
              OTHERS       = 2.
          CHECK sy-subrc IS INITIAL.
          CALL METHOD lr_var->get_value
            RECEIVING
              rto_value = et_value
            EXCEPTIONS
              error     = 1.
    After this, read the first line of the table et_value (it should be the value that the user choose on the screen).
    seeya!
    Robson

  • Urgent help needed reg. user exists..

    HI friends,
    I have one issue reg. user exists.
    I need to add 3 additional fields are
    Project Sponsor, Project Manager, WBS Function
    to the transaction  cje2 using the
    enhancement : KAP10001
    Exit :  EXIT_SAPLPS01_002
    i followed writing the code for kap10001 inserted some code and also updated the fields in the ddic tables  RPSCO_X, and  RPSCO_y. 
    the new fields has to populate in the  cje1  characteristic view of the form and report name 12KST1G.
    could you suggest me, how can i populate the new fields in the cje1.
    thanks in advance
    raghavendra rao G

    Hi,
    The code in the attachment is working correctly.
    My client wanted to populate the description also.
    for example.  if astnr(applicant no.), in the report it has to populate as
    applicant number and applicant name.
    for this i have  created entries in TKAF table as follows
    APPLC     KP                                          
    FIENM     ZZASTNR                                                                               
    USGFL     D                                           
    ROLNM     PS_ASTNR                                              
    CHTAB     TCJ05                                       
    CHFIE     ASTNR                                       
    RETAB     TCJ05                                       
    REFIE     ASTNA                                       
    REFIL     ASTNA                                       
    REFLL     25                                          
    DIMPR     0                                           
    RCSIN         1
    RSLIN     1
    CHAIN     1
    CCNUM        0      
    if i run the cje2 transaction, the applicant name is not appearing.
    can anybody give me ideas for this.
    regards
    raghavendra rao G

  • Types of user exists arise in sd module

    what is user exist and what type of user exists arise in sd module?

    Dear Chandu,
    Please go through this IMG path to identify the User exits
    SPRO>sales and Distribution>Syatem modification-->User Exits
    I hope it will help you,
    Regards,
    Murali.
    Please close the completed threads

  • User Exists Info needed

    Hi all,
    We are currently in the process of doing enhancement for Batch management.
    SAP Version - 4.6C
    For MIGO screen, requirement is that after posting details Batch is generated and GR is done. Followed by this expiry date of the batch is to be calculated.
    My ABAP team has confirmed that no user exist is getting activated after posting of documents... Can anyone please suggest me what USER EXIT / BADI to be used??
    regards,
    Parshuram

    hi,
    You want the calculate the expiry date? if it is so, then you can maintain it in shelf life field in MIGO. No need of any customisation.
    This is how it works. SHelf life is the period of safe storage after production or date of manufacture. So if you mention, shelf life as 5 days and date of manufacture as todays date. date of expiry will be 5 days after. by maintaining this you can do the aging analysis.
    Regards

  • User exits for FI module in ECC 5.0 Version

    Hello,
    Can someone help me on this..i need to find a userexit in ECC 5.0 and this is in FI module(please provide me the steps to find as well). I need to do some validations and the exit should trigger at the end of document creation and just before the user clicks save button..Its urgent so i would appreciate a quick reply from anyone who knows about this.
    Thanks,
    Mohsin

    Hi Mohsin,
    Welcome to SDN.
    You can create new custom program in your ECC 5.0 (Developmen Instance) by cut and paste the following sample program. This program will allow you to find user exist based on transaction code i.e FB50.
    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.
    Hope this will help.
    Regards,
    Ferry Lianto

  • User exists in system

    HI
    I need to find out if a particular user name exists in my SAP system. Any User tables or function modules ?
    Thanks

    HI
    You can check using the BAPI,
    BAPI_USER_EXISTENCE_CHECK
    where you can enter the users name and it returns with the message whether the user exists or not.
    Do reward if useful
    Thanks
    Swarna

  • Hi guru's i  am learning ,i am learning user exists plz help me

    hi guru's i  am learning ,i am learning user exists , i don't know anything about that plz help me lie realtime oriented

    Hi
    USER EXIT
    EXIT s are nothing but the R/3 Enhancements which allows you to add your own functionality to SAP’s standard business applications without having to modify the original applications.
    Purpose
    To introduce the techniques of enhancement in standard SAP system. SAP creates customer exits for specific programs, screens, and menus within standard R/3 applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.
    Use
    They do not affect standard SAP source code.
    When you add new functionality to your SAP System using SAP’s exits, you do not alter the source code of standard SAP programs in any way. The code and screens you create are encapsulated as separate objects. These customer objects are linked to standard applications, but exist separately from SAP’s standard software package.
    They do not affect software updates.
    When you add new functionality to your SAP System using SAP’s exits, your objects (called customer objects) must adhere to strict naming conventions. When it comes time to upgrade a to a new software release, customer objects’ names ensure that they will not be affected by any changes or new additions to the standard software package.
    Challenges
    Customer exits are not available for all programs and screens found in the SAP System.
    Modifications
    Any change made to an SAP object in a customer system is called a modification. Customers usually modify their systems for one of two reasons. Either they make changes to the SAP standard in order to adjust the R/3 System to their specific business needs (actual modifications), or they alter individual SAP objects in order to correct an error (as recommended in an SAP error note).
    You should only modify the SAP standard if the modifications you want to make are absolutely necessary for optimizing work flow in your company. Be aware that good background knowledge of application structure and flow are important prerequisites for deciding what kind of modifications to make and how these modifications should be designed.
    need
    ABAP DICTIONARY
    Table Enhancements: There are two ways that you can add additional fields to tables without modifying your system.
    Append Structures:
    Append structures allow you to enhance tables by adding fields to them that are not part of the standard. With append structures, customers can add their own fields to any table or structure they want.
    Append structures are created for use with a specific table. However, a table can have multiple append structures assigned to it.
    Customizing Includes:
    If customers know in advance that one of the tables or structures delivered to them by SAP needs to have customer-specific fields added to it, an SAP application developer can include these fields in the table using a Customizing include statement.
    The same Customizing include can be used in multiple tables or structures. This provides for consistency in these tables and structures whenever the itself include is altered.
    Append structures allow you to attach fields to a table without actually having to modify the table itself.
    Append structures may only be assigned to a single table. A table may, however, have several append structures attached to it. Whenever a table is activated, the system searches for all active append structures for that table and attaches them to the table. If an append structure is created or changed and then activated, the table it is assigned to is also activated, and all of the changes made to the append structure take effect in the table as well.
    You can use append structures in ABAP programs just as you would any other structure.
    Note: When you copy tables that have append structures attached to them, the fields that were found in the append structure of the original table become part of the actual body of the target table.
    Some of the tables and structures delivered with the R/3 standard contain special include statements calling Customizing includes. These are often inserted in those standard tables that need to have customer-specific fields added to them.
    In contrast to append structures, Customizing includes can be inserted into more than one table. This provides for data consistency throughout the tables and structures affected whenever the include is altered.
    Customizing include programs are part of the customer namespace: all of their names begin with 'CI_'. This naming convention guarantees that nonexistent Customizing includes do not lead to errors. No code for Customizing includes is delivered with the R/3 standard.
    You create Customizing includes using special Customizing transactions. Some are already part of SAP enhancements and can be created by using project management (see the unit on 'Enhancements using Customer Exits').
    The Customizing include field names must lie in the customer namespace just like field names in append structures. These names must all begin with either 'YY' or 'ZZ'.
    When adding the fields of a Customizing include to your database, adhere to same rules you would with append structures.
    ABAP DICTIONARY
    Field Exits:
    Field exits take you from a screen field with a data element reference to a function module. Field exits can be either global or local.
    Field exit function modules adhere to the following naming convention:
    prefix: FIELD_EXIT_
    name: <data element name>_
    suffix (optional): 0 to 9, A to Z
    Text Enhancements:
    Possible text enhancements include customer keywords and customer documentation of data elements.
    Text enhancements differ from other application enhancements in that they take effect globally in all related SAP applications after activation (global enhancements).
    Customer Exits
    Function Module Exits
    Menu Exits
    Screen Exits
    Function Module Exits
    Function module exits add functions to R/3 applications. Function module exits play a role in both menu and screen exits. When you add a new menu item to a standard pull down menu, you use a function module exit to define the actions that should take place once your menu is activated. Function module exits also control the data flow between standard programs and screen exit fields.
    Menu Exits
    Menu exits add items to the pull down menus in standard SAP applications. You can use these menu items to call up your own screens or to trigger entire add-on applications.
    SAP creates menu exits by defining special menu items in the Menu Painter. These special entries have function codes that begin with "+" (a plus sign). You specify the menu item’s text when activating the item in an add-on project.
    Screen Exits
    Screen exits add fields to screens in R/3 applications. SAP creates screen exits by placing special sub screen areas on a standard R/3 screen and calling a customer sub screen from the standard screen’s flow logic.
    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
    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

  • Need user exits material

    hi.,
    This is satish we requesting to all. I need user exits materials. It is very important me so please any one send the link or pdf file.
    thanking you all

    Please see the following program. This helps you to find user_exits...
    Start -
    REPORT ZFIND_USEREXITS .
    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.
    *--End--
    Hope this`ll work .
    Thanks

  • User exit for funtion module

    hi ,
        i need user exit for the function module 'J_1I7_USEREXIT_CHEQUENO_CERT'
    i have found the package in which this is stored.Then by giving the 'J1I2' in 'cmod ' i have to get the exit.But i'm not getting.Even by using tcode -'se80'  i have tried but its giving a message ''No objects correspond to the selection criteria''.
    pls tel me if there is any other method where by which i can find out the exit.
    its urgent
    thanks&regards
    prasad

    Hi Vara prasad,
      Finding the user exist or customer exist by using the package is not exact way because in that package called 'J1I2' i has not containing the function module J_1I7_USEREXIT_CHEQUENO_CERT only and also this pakage may be contains other tcodes or function modules etc.. that is the reason you get some user exists by using the package.
    Find the userexists by using the follwoing way:
    Go to SE37 -> open the function module J_1I7_USEREXIT_CHEQUENO_CERT in display mode -> press cnt+F button and search the string PERFORM USER Or CALL CUSTOMER-FUNCTION then you are able to get all the user exists and customer exists for the function module.
    Regards,
    Mahi.

  • New GL User Exist or Enhancement

    Hi SAP Expert
    Currently i have a problem to use New Ledger in my client ECC 5.00
    HQ Company using 544 calender for FI closing
    1 of the coutry need to use Month Calender for FI Closing
    When i do testing on FA depreciation run using tcode AFAB, i cannot specify the Posting date into the
    depreciation posting date and i need to post to correct period.
    Do u know whether in New Ledger / New GL have a user exist or enhancement we can change the data in
    table FAGLFLEXT or FAGLFLEXA in the specify ledger ?
    regards

    Hi Heng,
    Did you manage to get answer to your query "Do u know whether in New Ledger / New GL have a user exist or enhancement we can change the data in
    table FAGLFLEXT or FAGLFLEXA in the specify ledger ?"
    I have a similar requirment to substitute split line items that appear only in New General Ledger view ie in table FAGLFLEXT or FAGLFLEXA?

Maybe you are looking for