Can't find user exit or enhancement at RGJVBR15

Hi everyone,
I need your help guys. Right now,i'm developed sapscript for billing statement (cash call and expenditure). I have finished the form but i have problem at print program RGJVBR15. This print program is called by RGJVBR10 (Tcode : GJ14 --> Hard Copy Billing).GJ 12 and GJ 13 is used to extract data that will be used by forms.
There is statement like this in RGJVBR15 at subroutine CREATE_EXPENDITURE (Line 1421 in include file RGJBF_I1) :
AT NEW C5_CURR. --> Group by funding currency
   PERFORM POPULATE_SPOOL_ID
ENDAT.
  PERFORM F6100_PROC_...  -> This will be used to open form,write form (sapscript)
AT END OF C5_CURR.
ENDAT.
The problem is that i want to change this logic. I want to change the standard logic (display report group by funding currency), i want to ignore this and instead using group currency. So there only one report produced with one currency only (if using standard logic there is more than 1 report based on funding currency). But i can't find user exit or enhancement in this SAP Standard Program. Is anyone know if there is user exit or enhancement in this program? I don't want to use implicit enhancement because it's will produce problem when client want to upgrade their system. Thank you.
Best Regards,
Satria

hi,
for tcode GJ14 user exits avaliables are
Exit Name           Description
JVA-IM-1             Joint Venture: Integration Manager Set Intercompany Lines
JVA_IM_2            User Exit Splitting
JVA_IM_3            User Exit Check Document
regards,
paras

Similar Messages

  • How to know where the user exits or enhancement used in standard sap code?

    Hi
    I m pretty new to abap.
    How can I know where the user exits or enhancement used in standard sap code?
    As i have to add some functionality to the standard sap code. I m looking to search the enhancement or user exits used in this standard code wher i can add my functionality.
    thanks in advance.
    Moderator message : Search for available information, thread locked.
    Edited by: Vinod Kumar on Oct 19, 2011 2:38 PM

    Hi Henry,
    I don't think this is the easiest way to look at the code around a particular field on the screen. Debugging standard programs also can be very tedious, if not impossbile. So, instead of this question, I would like to find out exactly what you want to do if you know the code.
    If you are in a transaction and you want to know where the code of a particular field is, the fastest way to get to it is by pressing the F1 key on the field and then press the Technical info button on the help screen. In here you will typically see the same kind of information but it is very specific to the field you selected.
    PROGRAM(SCREEN) tells you which program is manipulating the main screen, in which your field is embedded. Remember your field may be included in a sub-screen and that subscreen may be the one included in the main screen.
    PROGRAM(SUB SCREEN) tells you which program is directly responsible for the field on the subscreen it is included in. This is where you should find the code most appropriate for the field, but not necessarily.
    PROGRAM(GUI) controls how your push buttons and the menu options in the screen behave and controlled.
    Srinivas

  • User Exit or Enhancement for Material accounting document in VL02N at PGI

    Hi,
    I have 2 requirement at the time of PGI of Delivery.
    1) Currently there are 2 accounting document getting created for 2 countries. i want to restrict acc. document creation for one company code.
    2) I want to change the GL account in the accounting document while creation.
    Could you please help me in finding any user exit or enhancement or BAdi or BTE which can resolve th eissue?
    Thanks,

    Hi,
    GL account can be changed through the badi AC_DOCUMENT.
    Use the the method CHANGE_INITIAL to change the GL account..
    Regards
    Aromal R

  • Help in user exit and enhancement

    hi expects,
            can any body help me by providing me the enhancement and user-exist material.please help me

    Hi Santosh
    User exits (Function module exits) are exits developed by SAP. The exit is implementerd as a call to a functionmodule. The code for the function module is writeen by the developer. You are not writing the code directly in the function module, but in the include that is implemented in the function module.
    The naming standard of function modules for functionmodule exits is:
    EXIT_<3 digit suffix>
    The call to a functionmodule exit is implemented as:
    CALL CUSTOMER.-FUNCTION <3 digit suffix>
    Example:
    The program for transaction VA01 Create salesorder is SAPMV45A
    If you search for CALL CUSTOMER-FUNCTION i program
    SAPMV45A you will find ( Among other user exits):
    User exits (Function module exits) are exits developed by SAP. The exit is implementerd as a call to a functionmodule. The code for the function module is writeen by the developer. You are not writing the code directly in the function module, but in the include that is implemented in the function module.
    The naming standard of function modules for functionmodule exits is:
    EXIT_<3 digit suffix>
    The call to a functionmodule exit is implemented as:
    CALL CUSTOMER.-FUNCTION <3 digit suffix>
    Example:
    The program for transaction VA01 Create salesorder is SAPMV45A
    If you search for CALL CUSTOMER-FUNCTION i program
    SAPMV45A you will find ( Among other user exits):
    CALL CUSTOMER-FUNCTION '003'
    exporting
    xvbak = vbak
    xvbuk = vbuk
    xkomk = tkomk
    importing
    lvf_subrc = lvf_subrc
    tables
    xvbfa = xvbfa
    xvbap = xvbap
    xvbup = xvbup.
    The exit calls function module EXIT_SAPMV45A_003.
    *2. How to find user exits *
    Display the program where you are searching for and exit and search for CALL CUSTOMER-EXIT
    If you know the Exit name, go to transaction CMOD.
    Choose menu Utillities->SAP Enhancements. Enter the exit name and press enter.
    You will now come to a screen that shows the function module exits for the exit.
    *3. Using Project management of SAP Enhancements *
    We want to create a project to enahance trasnaction VA01
    - Go to transaction CMOD
    - Create a project called ZVA01
    - Choose the Enhancement assign radio button and press the Change button
    In the first column enter V45A0002 Predefine sold-to party in sales document . Note that an enhancement can only be used i 1 project. If the enhancement is already in use, and error message will be displayed
    Press Save
    Press Components. You can now see that enhancement uses user exit EXIT_SAPMV45A_002. Double click on the exit.
    Now the function module is displayed. Double click on include ZXVVAU04 in the function module
    Insert the following code into the include: E_KUNNR = '2155'.
    Activate the include program. Go back to CMOD and activate the project.
    Goto transaction VA01 and craete a salesorder.
    Note that Sold-to-party now automatically is "2155"
    for more information.
    try out with this links:
    [http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm]
    Hope answered your question.
    Reward if helpful
    Thanks
    abdul

  • Finding user-exits

    Hi Experts,
    1.How to find the screen Exits and Menu Exits for any Transaction code?
    I know how to find thru SMOD by giving package name and thru MODSAP table.I also know a Z-program is there to find.But i want to find thru SAP program.Like Call Customer function is there any way for finding menu Exits and Screen Exits?
    2. Is access key required to implement Menu and Screen exits in ECC6.0 version?
    3. I will be great full if any body let me know the step by step procedure for implementing screen exit and Menu Exit with an Example in ECC 6.0 version.
    Regards
    Ravi.
    Regards

    1. Finding user exit/BADI
    SMOD, is where you can find the system modifications provided by SAP. CMOD is where you will implement them. If you are looking for all the enhancements provided, then go to CMOD, follow the menu, 'Utilities-->SAP Enhancements'. This will take you to a screen where if you just execute it, you will get all the enhancements provided by SAP.
    It is always difficult to find a user exit if all you have is a program name or a transaction code, unless you do a program like Rich suggested. But even there, you will not be able to find user exits that are implemented as sub-routines(also called forms not sapscript forms). Most of the user exits are documented under the corresponding task under IMG structure. So use transaction code SPRO, go to the IMG structure, choose the application area that your program or transaction might be and then you should find a task that talks about enhancements. If you execute that task most often it will take you to CMOD and sometimes to SE38. But all you want to know is there in the documentation attached to the task. Then you can go to CMOD and see which components are there.
    Finding BADIs
    Business add-ins are enhancements to the standard version of the system.
    Business Add-In is a new SAP enhancement technique based on ABAP Objects.
    They can be inserted into the SAP system based on specific user requirements.
    Each Business Add-In has:
    • at least one Business Add-In definition
    • a Business Add-In interface
    • a Business Add-In class that implements the interface
    In order to enhance a program, a Business Add-In must first be defined
    Subsequently two classes are automatically generated:
    • An interface with ‘IF_EX_’ inserted between the first and second characters of the BADI name.
    • An adapter class with ‘CL_EX_’ inserted between the first and second characters of the BADI name.
    The Application developer creates an interface for this Add-In.
    There are multiple ways of searching for BADI.
    • Finding BADI Using CL_EXITHANDLER=>GET_INSTANCE
    • Finding BADI Using SQL Trace (TCODE-ST05).
    • Finding BADI Using Repository Information System (TCODE- SE84).
    1. Go to the Transaction, for which we want to find the BADI, take the example of Transaction VD02. Click on System->Status. Double click on the program name. Once inside the program search for ‘CL_EXITHANDLER=>GET_INSTANCE’.
    Make sure the radio button “In main program” is checked. A list of all the programs with call to the BADI’s will be listed.
    The export parameter ‘EXIT_NAME’ for the method GET_INSTANCE of class CL_EXITHANDLER will have the user exit assigned to it. The changing parameter ‘INSTANCE’ will have the interface assigned to it. Double click on the method to enter the source code.Definition of Instance would give you the Interface name.
    2. Start transaction ST05 (Performance Analysis).
    Set flag field "Buffer trace"
    Remark: We need to trace also the buffer calls, because BADI database tables are buffered. (Especially view V_EXT_IMP and V_EXT_ACT)
    Push the button "Activate Trace". Start transaction VA02 in a new GUI session. Go back to the Performance trace session.
    Push the button "Deactivate Trace".
    Push the button "Display Trace".
    The popup screen "Set Restrictions for Displaying Trace" appears.
    Now, filter the trace on Objects:
    • V_EXT_IMP
    • V_EXT_ACT
    Push button "Multiple selections" button behind field Objects
    Fill: V_EXT_IMP and V_EXT_ACT
    All the interface class names of view V_EXT_IMP start with IF_EX_. This is the standard SAP prefix for BADI class interfaces. The BADI name is after the IF_EX_.
    So the BADI name of IF_EX_CUSTOMER_ADD_DATA is CUSTOMER_ADD_DATA
    3. Go to “Maintain Transaction” (TCODE- SE93).
    Enter the Transaction VD02 for which you want to find BADI.
    Click on the Display push buttons.
    Get the Package Name. (Package VS in this case)
    Go to TCode: SE84->Enhancements->Business Add-inns->Definition
    Enter the Package Name and Execute.
    Here you get a list of all the Enhancement BADI’s for the given package MB.
    2. No access key will be asked
    3. Step by step procedure
    http://sap.ittoolbox.com/groups/technical-functional/sap-r3-dev/menu-exits-72696#
    http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction

  • To find user exit whever moving average price changed

    Hi Experts,
    I need to write my code whenever moving average price (MBEW-VERPR) get changed, few scenarios are:
    - MBEW-VERPR can be updated from MR21 transaction
    - Create Purchase Order then create delivery then transfer order, on confirmation of transfer order MBEW-VERPR can be changed
    - It can be changed from MIGO transaction on Goods Receipt and Reversal.
    -It can be changed from VL09 transaction on reversal of goods.
    My requirement is to make my code as transaction independent, so I need to find out user exit( or enhancement spots) to write my code to update a z-table.
    Can anyone help me to find out the correct place to write code?
    Regards,
    Piyush Yadav

    Changing average price also creates an accounting document, whatever the origin of the change. So you could try BTE 00001025 of Publish&Subs (P/S). From BKPF header information you should be able to find the original documents (marterial receipt, average price change, etc.)
    Regards,
    Raymond

  • How to find user exit for a perticular screen?

    Dear all,
    Can some one tell me how to find user exit for a perticular screen?
    ex: MC88 screen can we figure out are there any user exit for that screen!!
    Regards,
    Vj

    User exits are built into the Standard SAP code. You just activate them and insert your code into the include programs.
    Here is a program that will list the user exits per transaction code. Not perfect, but it may help.
    report z_find_user_exit no standard page heading.
    tables: tstc, tadir, modsapt, modact,
            trdir, tfdir, enlfdir, tstct.
    data : jtab like tadir occurs 0 with header line.
    data : hotspot(30).
    parameters : p_tcode like tstc-tcode obligatory.
    at line-selection.
      get cursor field hotspot.
      check hotspot(4) eq 'JTAB'.
      set parameter id 'MON' field sy-lisel+1(10).
      call transaction 'SMOD' and skip first screen.
    start-of-selection.
      perform get_data.
      perform write_list.
          FORM get_data                                                 *
    form get_data.
      select single * from tstc
                  where tcode eq p_tcode.
      check sy-subrc eq 0.
      select single * from tadir
                where pgmid = 'R3TR'
                  and object = 'PROG'
                  and obj_name = tstc-pgmna.
      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.
        endif.
      endif.
      select * from tadir into table jtab
                 where pgmid = 'R3TR'
                   and object = 'SMOD'
                   and devclass = tadir-devclass.
      select single * from tstct
              where sprsl eq sy-langu
                and tcode eq p_tcode.
    endform.
          FORM write_list                                               *
    form write_list.
      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.
    endform.
    SMOD, is where you can find the system modifications provided by SAP. CMOD is where you will implement them. If you are looking for all the enhancements provided, then go to CMOD, follow the menu, 'Utilities-->SAP Enhancements'. This will take you to a screen where if you just execute it, you will get all the enhancements provided by SAP.
    It is always difficult to find a user exit if all you have is a program name or a transaction code, unless you do a program like Rich suggested. But even there, you will not be able to find user exits that are implemented as sub-routines(also called forms not sapscript forms). Most of the user exits are documented under the corresponding task under IMG structure. So use transaction code SPRO, go to the IMG structure, choose the application area that your program or transaction might be and then you should find a task that talks about enhancements. If you execute that task most often it will take you to CMOD and sometimes to SE38. But all you want to know is there in the documentation attached to the task. Then you can go to CMOD and see which components are there.
    Regards,
    Amey

  • How to find User exit for PO

    Hi
    My require ment is system should check for the follwoing PO document type
    i have ctreated new document type with respective PR ,  while creating PO system should check following while saving.(ME21N)
    1.PO,
    2.incoterm,
    3.price,
    4.quantity.
    So for that i want find user exit for PO. can u plz heip me....

    Hi
    You can use the BADI  ME_PROCESS_PO_CUST
    use the methods IM_HEADER and IM_ITEM
    if needed check the following  PO related exits
    Enhancement
    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
    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
    MEQUERY1                                Enhancement to Document Overview ME21N/ME51N
    MELAB001                                Gen. forecast delivery schedules: Transfer schedule implem.
    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
    Business Add-in
    ME_PROCESS_REQ_CUST                     Enhancements for Processing Enjoy PReqs: Customer
    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: Custome
    ME_PO_SC_SRV                            BAdI: Service Tab Page for Subcontracting
    ME_PO_PRICING_CUST                      Enhancements to Price Determination: Customer
    ME_PO_PRICING                           Enhancements to Price Determination: Internal
    ME_INFOREC_SEND                         Capture/Send Purchase Info Record Changes - Internal Use
    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_DP_CLEARING                          Clearing (Offsetting) of Down Payments and Payment Requests
    ME_PURCHDOC_POSTED                      Purchasing Document Posted
    SMOD_MRFLB001                           Control Items for Contract Release Order
    EXTENSION_US_TAXES                      Extended Tax Calculation with Additional Data
    ARC_MM_EKKO_WRITE                       BAdI: Enhancement of Scope of Archiving (MM_EKKO)
    ARC_MM_EKKO_CHECK                       BAdI: Enhancement of Archivability Check (MM_EKKO)
    MM_EDI_DESADV_IN                        Supplementation of Delivery Interface from Purchase Order
    MM_DELIVERY_ADDR_SAP                    Determination of Delivery Address
    ME_WRF_STD_DNG                          PO Controlling Reminder: Extension to Standard Reminder
    ME_TRIGGER_ATP                          Triggers New ATP for Changes in EKKO, EKPO, EKPV
    ME_TRF_RULE_CUST_OFF                    BADI for Deactivation of Field T161V-REVFE
    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_RELEASE_CREATE                       BAdI: Release Creation for Sched.Agrmts with Release Docu.
    ME_DEFINE_CALCTYPE                      Control of Pricing Type: Additional Fields
    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 plant
    ME_CCP_ACTIVE_CHECK                     BAdI to check whether CCP process is active
    ME_BSART_DET                            Change document type for automatically generated POs
    ME_BAPI_PR_CREATE_02
    ME_BAPI_PR_CREATE_01
    ME_BAPI_PO_CREATE_02
    ME_BAPI_PO_CREATE_01
    ME_BADI_DISPLAY_DOC                     BAdI for Internal Control of Transaction to be Invoked
    ME_ACTV_CANCEL_PO                       BAdI for Activating the Cancel Function at Header Level
    MEGUI_LAYOUT                            BAdI for Enjoy Purchasing GUI
    ME_CHECK_ALL_ITEMS                      Run Through Items Again in the Event of Changes in EKKO
    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_COMMTMNT_PO_RELEV                    Check for Commitment-Relevance of Purchase Orders
    ME_COMMITMENT_STO_CH                    BadI for checking if commitments for STOs are active
    ME_COMMITMENT_RETURN                    Commitment for return item
    ME_CIP_REF_CHAR                         Enables 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_OA                             Check BAdI for Contracts
    <b>Reward points for useful Answers</b>
    Regards
    Anji

  • Valuation price with user exit/BADI/Enhancement Spot (In valuation variant)

    Hi all,
    i am facing problem finding enhancement when creation of sales order of Valuation price with user exit/BADI/Enhancement Spot  (In valuation variant)
    For refferenece:
    When going to t.code VA03, select one item and go to extras in the menu bar and select costing then you find some amounts calculation i.e valuation price automatically.
    So when creation of sales order i am giving material and that material price automatically takes from material master and creating sales order.
    My customer requirement is to get the valuation price of the input material from Z-table during the sales order cost estimate.
    This Z-table contains the material code, plant , grade  of the material.
    Ex:
    Material         Plant   Grade Price
    A                1000    XYZ     25000
    A                1000    PQR     35000
    A                1000    BCD     45000
    Suppose it depends on sales document type and which grade price i have to take.
    So first of all i am unable to find enhancement where to change this code to get change the valuation price.
    Does anybody have any idea , is there any user exit/BADI/enhancement for this.
    So please help me in this issue.
    Thanks & Regards,
    lokeshgoud

    pls allow me to post the questions

  • User Exit/BADI/Enhancement Point  in VF01 before new document no assignment

    Hi Expert,
       I am looking for a user exit/BADI/Enhancement point which will trigger in VF01 before the new document no (Billing document no assign).
    I need to cross check few things in Billing via VF01 at billing document save and give error message accordingly. The problem is if new number assign and there is error due to my code then when user save the document next he get a new no. its mean a no skip.
    Example: The invoice no is 1000. User start creating a billing document with Vf01 and he get an error message due to my code at exit , at this point of time the next number assign to billing which is 1001 but document not save due to my error message. Now after applying correction user save data and billing document created with no 1002. So there is no skip.
    I tried BADI BADI_SD_ACCOUNTING but this will trigger after no assignment.  Can someone provide me a user exit/BADI/Enhancement point in VF01 which trigger before no range assignment and contain at least Billing header data to use in my code?
    Regards
    Swati
    Edited by: Swati Namdev on Nov 16, 2010 9:55 PM

    HI Brad and team,
       BRED is right. I check few user exit normally all of us have that list or easily available on net.
    BRED: my question is: I need to check the billing date VBRK-FKDAT of document should not be less than the sales order plan billing date VBAP-Oldate.
    If this check fail then won't allow the user to create billing document. The problem is I used one user exit SDVFX001 already define previously that's work fine but issue is that user exit trigger after the billing no assignment. That's why when user get that error message he correct the document and create billing this time he get a new number which is skip of one no.
    That why I need a User Exit/BADI/Enhancement Point  which trigger at save but before document no assignment.
    Please update more about your comment "Why not use a header level copy requirement routine to perform the checks and log the messages? This is the standard process."  .
    Suggest user exit USEREXIT_FILL_VBRK_VBRP  trigger before save. I need at save the reason is VBRK-FKDAT  this can be change.
    Feel free to contact me back if you need more clarification.
    Regards
    Swati
    Edited by: Swati Namdev on Nov 17, 2010 6:22 PM
    Edited by: Swati Namdev on Nov 17, 2010 6:25 PM
    Edited by: Swati Namdev on Nov 17, 2010 6:32 PM
    Edited by: Swati Namdev on Nov 17, 2010 6:47 PM

  • What are all the key words are not recommented in User Exit or Enhancement

    Dear Experts,
    Can any of one tell me, what are all the key words not recommended to use any of the User exit or Enhancement spots?
    Regards,
    Mohana
    Moderator message: please search for available information/documentation.
    Edited by: Thomas Zloch on Feb 22, 2011 4:10 PM

    No Icon:Visitor
    Student
    Honor Student
    Top Student
    Tutor
    Intern
    Teacher
    Grad Student
    Master’s Graduate
    PhD Student
    Associate Professor
    Professor
    Distinguished Professor
    Regents Professor
    Associate Dean
    Dean
    Provost
    FONDA X. COX, PhD

  • Find User Exit or BADI

    Hi all,
    When I worked in the version 4.6 I used to use the object v_ext_act, v_ext_imp and the transaction St05 to find a user exit or a badi when I need it. But since I started to work in the version 6.0 it seems that with these objects I can't find anything.
    Any of you know if SAP has changed the name of these objects?
    Thanks

    Hi Raul,
    Another approach that you can use in order to find out user-exit or badi in a program or transaction is to start execution of it in debug mode and then put a break-point in following statements:
    CALL CUSTOMER-FUNCTION --> to find user-exits.
    CALL BADI --> to find BADI's
    Then just press F8 and SAP will stop whenever a user-exit or badi is invoked.
    Hope this helps.
    Cheers.

  • How to find user exit implemented in the program

    how to find user exit implemented in the program or standerd transaction

    try this program to get the list of all the user exits for a transaction...
    *& Report  Z_USER_EXIT                                                 *
    *REPORT  Z_USER_EXIT                             .
    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.

  • How to find User Exits/ Enhancments/ BADI's for T-code CJ20N

    Hi All,
        In T-code CJ20N, assume there are two fields A & B. User will input value in A, based on A value I need to fill B field. So I need to find first suitable User Exit/ Enhancment/ BADI.
    Kindly help me in this regard. Pls tell me how to find User Exit/ Enhancment/ BADI for a given t-code.
    Regards
    Jaker.

    Hi,
    Check the following , this might help,
    1. CNEX0037
    2.CNEX0038
    3.CNEX0039
    Regards
    Kiran Sure

  • How to find user exit in SPRO

    Hi experts,
                 how to find user exit in spro.
    the path is in spro.
    in spro->financial accounting>travel managment>travel expenses>transfer to accounting-->
    define assigment of wage type to symbolic account.
    when u click on this  it will ask for trip provision variant if we key in the work area number thne we get a screen . in that wage test key start date end date so on... are there so in the field KEY its empty so i want to find a user exit.can u please help me in this.
    regards,
    sunita.

    Hi,
    For more information on user exit,
    use the following link.
    Hope it is useful.
    http://****************/Tutorials/ExitsBADIs/ExitsMain.htm
    Regards,
    Phani.

Maybe you are looking for