Debugging user exit

Dear Experts,
                 I found that the User Exit code for Transaction data coming from R/3 to BW is not working properly. I have to debug it. How do I debug it? Can somebody refer me to any documentation or tell me the method used to debug user exits? I know how to debug Update and Transfer rules.. but not user exits?
Thank you.

For update and transfer rules:
1) Load data till PSA.
2) Go to monitor and select details tab.
3) Open Processing node and on a data packet node right click and select simulate update.
4) On the next screen select the data provider and mark the update debugging in update rules and/or debugging in transfer rules
5) On the lower part select all records or selective records.
6) In the update rules, the program will first stop at a point where the different debugging points can be turned on or off. Some are on and some are off. Change them according to your requirements.
Debug User Exit: Assuming you want to debug extraction exit. Put a break point in the code and run in RSA3. If you are trying in production system, then select the enable debugging option in RSA3 and run the extractor.

Similar Messages

  • Unable to debug user exit in CRM BW  (EXIT_SAPLRSAP)

    Hi Gurus,
    Please help me to debug user exit in CRM BW.
    I am using below enhancement
    RSAP0001 (Customer function calls in the service API)
    "EXIT_SAPLRSAP_003"
    Datasource is ZSTAONESYS0_TEXT
    The extract structure
    I have modified is "CRM_BIW_ST_T"
    ===========================
    Data Source "I_CHABASNM"
    CASE i_chabasnm.
    ZSTAONESYS0_TEXT -- Data source name
      WHEN 'ZSTAONESYS0_TEXT'.
        CLEAR l_s_crm_biw_st_t .
        LOOP AT  c_t_texts   INTO  l_s_crm_biw_st_t .
          l_tabix = sy-tabix.
          SELECT SINGLE * FROM crm_jest
                   INTO   wa_status
                   WHERE   inact  =  ' '.
          SHIFT wa_status-stat LEFT DELETING LEADING space.
          CLEAR l_stat.
          l_stat = wa_status-stat(1).
          IF  l_stat  = 'E'.
            l_s_crm_biw_st_t-bwstoppt   = wa_status-stat+3(2).
            MODIFY  c_t_texts  FROM l_s_crm_biw_st_t
                                  INDEX l_tabix.
          ENDIF.
        ENDLOOP.    
    ENDCASE.
    ===========
    Should I use a BADI?
    It would be great if you could give me
    relevant definition name for creating new BADI.
    Can I use "CRM_BWA_MFLOW" ?
    I promise to return and reward the answers.
    Really heart warming
    to see the dedication/ participation of
    Bhanu Gupta / A.H.P / Pizzaman and many others
    Thanks in advance, :-D
    AbyJacob, Bangalore
    ===================

    Dear SB,
    I was able to Debug my user exit successfully.
    ==>include ZXRSAU02. "EXIT_SAPLRSAP_003"
    You guys are really a big help
    Keep up the good work.
    Special Thanks to SDN community
    warm regards,
    Aby Jacob, Bangalore

  • Debug CIF - ECC inbound - User exit CIFORD03 - Planned order to process ord

    Hi
    While Converting planned orders to process orders from APO to ECC, queues are not getting stop in Inbound ECC.. even after setting CIF user as dialog user and maintaining both CIF user and my user ids in /sapapo/c4 to block queues. maintained the same in ECC CIFGPARAMV table.  Outbound queues are stopping in APO, but not able to debug APO outbound queues...
    I want to debug user exit CIFORD03 (EXIT_SAPLCORD_005 ) in ECC . Please reply.
    Thanks
    Sreeni

    Hi Sreeni,
    The setting in /sapapo/c4 against your user ID would be relevant in this case.
    Debugging should be on, and use detailed logging. Also, your RFC user ID should be a dialog user ID or a Service user ID.
    Did you make sure that your user ID and the RFC user ID 'in R/3 for APO' have sufficient debug authorizations (including queue debug authorizations)?
    (You can find out the RFC user in SM59 in APO against the RFC connection that you have for R/3. )
    You should then see a queue stuck in R/3 inbound, where you could enter in debug mode.
    If you go to SMQR in R/3, and see a queue called CF, then it's also possible to deregister this CF queue, and then queues will get stuck in R/3 inbound. You could then use this queue for debug if you have sufficient debug authorizations including queue debug.
    Thanks - Pawan
    Edited by: Pawan Pathak on Feb 16, 2012 1:32 PM

  • Debug for User Exit

    Hi,
    How to Debug User Exits ,Pls Explain step by step?
    Thanks,

    Hi,
    Please find step by step on how to debug:
    Enhancement/Modifications
    1) Execute tcode SMOD to find available enhancement/modifications.
    2) Create a project for the enhancement in tcode CMOD.
    3) You must activate your project first in order to hit a break-point or get into debug mode for your existing enhancements/modifications, if you do not, the best you will be able to do is step through the main program until you hit the call for that particular customer enhancement.
    4) To get into debug, you can enter a hard break-point in the enhancement itself, set a soft break-point with the stop sign, or the long way, before you execute your transaction or while you are in your transaction, you can place a /h in the ok code area (this is the area of your gui where you can type in a tcode). Once you have the /h, hit enter and that will take you into debug, from there, you can do many different things to find exactly what you are looking for.
    User Exits
    1) Identify the main program you want to locate a user exit/debug.
    2) For example, go to SE80 and do a search by program or dev class (SAPMV45A sales order or Dev Class VMOD, most SD user exits are in this dev class). In SE80 if you go by program, most user exit programs end in a 'Z' on a rare occasion 'X' or 'Y'.
    3) If you are looking at including MV45AFZZ, you can see where there are different forms. These forms will get called at times within the program. If you are looking to fill the storage location on the sales order, you will probably want to take a look at the perform that fills in a field in vbap.
    4) If this is what you are trying to accomplish, you will need to do the select against the config Table TVKOL based on the shipping point/plant and possibly storage condition based on your picking strategies.
    5) For the debug part, you can do the same as in the enhancements/modifications but you will not need to activate any projects.
    Regards
    Kiran Sure

  • Java User Exit - File header failed to parse tokens

    I'm getting an OGG-01389 ... File header failed to parse tokens.  File /u01/pump/aa000000, last offset 916, data: 0x   394: <256_char_alpha_num_omitted>
    The doc for OGG-01389 just has:
      Cause: There was an error while parsing the trail header.
      Action: Contact Oracle Support.
    In my log4j, I can see that javawriter.c finds all of the com.goldengate.atg.* classes and methods that it's looking for, with a "Loaded all classes for Java User Exit" log entry.  I also see the following entries from javawriter.c in the log, prior to any indication of error:
    Now loading callback methods
    Calling 'main' with JVM options: [blah, blah, blah]
    setProperty: key=JAVACHKPT, value=true
    Running in JAVA checkpointing mode
    Checking for checkpoint file
    Checkpoint file does not exist
    Java Writer Initialized
    ... then I get the following log output from javauserexit.c ... still looking good:
    (javauserexit.c:389)  [INFO]: Initialized User Exit
    (javauserexit.c:563)  [DEBUG]: User exit: EXIT_CALL_CHECKPOINT
    ... then back to output from javawriter.c :
    (javawriter.c:104)  [DEBUG]: get_current_time
    (javawriter.c:104)  [DEBUG]: get_current_time
    ... and then failure ... coming from javauserexit.c at the line indicated:
    (javauserexit.c:885)  [INFO]: User exit: EXIT_CALL_FATAL_ERROR.
    ... thinking it could have something to do with defaults being set for checkpointing, I tried the following in GGSCI prior to starting the extract in question:
    GGSCI > alter extract uePump, extseqno 0, extrba 0
    EXTRACT altered.
    GGSCI > start uePump
    EXTRACT UEPUMP starting
    ... but I get the same failure as above.
    Earlier in the log, I can see that all of the following goldengate properties are being set to defaults, since I have not specified values for them ... should I? :
    goldengate.userexit.rawchars               ... defaulting to false
    goldengate.userexit.buffertxs               ... defaulting to ops
    Checkpoint file prefix set to: userexit_
    goldengate.userexit.includebefores     ... defaulting to true
    goldengate.userexit.noignorerecs        ... defaulting to false
    goldengate.userexit.noop                    ... defaulting to false
    goldengate.userexit.nosend                 ... defaulting to false
    goldengate.userexit.nosendcols           ... defaulting to false
    Thanks for any info / advice.

    Nevermind.  I was "accidentally" working off "old" srcDb exttrail extract and resulting remote pump rmttrail extract.  Since the src was built by the default GG 11.2 format (because that's the version of GG running there on the DB server), the remote pump extract that my user exit was ingesting was  also the11.2 format.  Just added the "format release 11.1" to the exttrail of the source, and re-flushed everything and my OGG-0138 goes away.
    Sorry about the noise!

  • FM in update task - How do you debug for a user exit (IW32)

    Hi,
    I am working on user exit IWO10009, fm EXIT_SAPLCOIH_009, transaction IW32.
    The user-exit should be called any time an order is saved with parts added to the component tab.
    The import structure of the user exit is CAUFVD, which doesnu2019t contain the items in the component. Instead, I have to go into table RESB and get the components.
    However, when I go into RESB from inside the user-exit, the added components have not yet been added to the table.
    As such, I was thinking of creating a Z function module in update task to process this code after the order is saved & RESB is updated.
    2 questions
    1 u2013 Is this the best way of accomplishing this?
    2 u2013 How do you debug FMu2019s in update task? I have set a breakpoint & have switched system debugging on from inside the debugger, but it doesnu2019t stop inside the fm.
    Please help.
    Thanks,
    John

    Hi,
    to debug update task you need to switch on "update debugging" not the "system debugging" from the menu Settings->update debugging.
    -Ramesh

  • Debug an USER-EXIT which is present inside an INCLUDE

    Hi folks,
    i want to debug a include ' LVEDFF0E.' which is present in the program  'SAPLVEDF.
    my user exit 'ZXEDFU02' is present in the include LVEDFF0E . This exit is to change the IDOC segmants.
    i want to debug my user exit which is present inside a include.i tried so many times but control is not going to that point.
    can anybody tell me how to debug that exit???
    correct answers will be rewarded.
    Thanks & Regards

    Hi,
    Try this way
    /h> choose "breakpoints" from menu> breakpoint at >function module> enter EXIT_SAPLVEDF_002 and press enter press f8

  • Can we debug the USER EXITs

    Hi,
          This is Krishna. Can we Debug the User exits. If possible, how to debug and what r the user exits can we debug.
      If any one knows, pls help me.
      Thanx in advance.
    Regards,
    Krishna.

    Hi,
    Write one of these statements in ur user exit code.
    break-point
    or
    break <URID>
    Thanks
    mahesh

  • Debugging a User Exit

    Hi
    I would like to debug a program, and locate and fix an error in one of the user exits. How can I go about doing this?
    Please help to solve this.
    Regards
    Radha

    Hi,
    Enhancement/Modifications
    1) Execute tcode SMOD to find available enhancement/modifications.
    2) Create a project for the enhancement in tcode CMOD.
    3) You must activate your project first in order to hit a break-point or get into debug mode for your existing enhancements/modifications, if you do not, the best you will be able to do is step through the main program until you hit the call for that particular customer enhancement.
    4) To get into debug, you can enter a hard break-point in the enhancement itself, set a soft break-point with the stop sign, or the long way, before you execute your transaction or while you are in your transaction, you can place a /h in the ok code area (this is the area of your gui where you can type in a tcode). Once you have the /h, hit enter and that will take you into debug, from there, you can do many different things to find exactly what you are looking for.
    User Exits
    1) Identify the main program you want to locate a user exit/debug.
    2) For example, go to SE80 and do a search by program or dev class (SAPMV45A sales order or Dev Class VMOD, most SD user exits are in this dev class). In SE80 if you go by program, most user exit programs end in a 'Z' on a rare occasion 'X' or 'Y'.
    3) If you are looking at including MV45AFZZ, you can see where there are different forms. These forms will get called at times within the program. If you are looking to fill the storage location on the sales order, you will probably want to take a look at the perform that fills in a field in vbap.
    4) If this is what you are trying to accomplish, you will need to do the select against the config Table TVKOL based on the shipping point/plant and possibly storage condition based on your picking strategies.
    5) For the debug part, you can do the same as in the enhancements/modifications but you will not need to activate any projects.
    reward if useful
    regards
    Ravi

  • Debugging a User Exit or Program

    Hi,
    I would like to debug a program, and locate and fix an error in one of the user exits. How can I go about doing this?
    Thanks,
    Shah.

    Hi,
    Enhancement/Modifications
    1) Execute tcode SMOD to find available enhancement/modifications.
    2) Create a project for the enhancement in tcode CMOD.
    3) You must activate your project first in order to hit a break-point or get into debug mode for your existing enhancements/modifications, if you do not, the best you will be able to do is step through the main program until you hit the call for that particular customer enhancement.
    4) To get into debug, you can enter a hard break-point in the enhancement itself, set a soft break-point with the stop sign, or the long way, before you execute your transaction or while you are in your transaction, you can place a /h in the ok code area (this is the area of your gui where you can type in a tcode). Once you have the /h, hit enter and that will take you into debug, from there, you can do many different things to find exactly what you are looking for.
    User Exits
    1) Identify the main program you want to locate a user exit/debug.
    2) For example, go to SE80 and do a search by program or dev class (SAPMV45A sales order or Dev Class VMOD, most SD user exits are in this dev class). In SE80 if you go by program, most user exit programs end in a 'Z' on a rare occasion 'X' or 'Y'.
    3) If you are looking at including MV45AFZZ, you can see where there are different forms. These forms will get called at times within the program. If you are looking to fill the storage location on the sales order, you will probably want to take a look at the perform that fills in a field in vbap.
    4) If this is what you are trying to accomplish, you will need to do the select against the config Table TVKOL based on the shipping point/plant and possibly storage condition based on your picking strategies.
    5) For the debug part, you can do the same as in the enhancements/modifications but you will not need to activate any projects.
    Reward points if found helpfull..
    Cheers,
    Chandra Sekhar.

  • Debugging inbound idoc user exit

    Hi all,
    I have a client who wishes to do some data validation when creating an inbound idoc.  We've identified the appropriate user exit and set a break-point in it, but how do I get the inbound process to stop here so I can see the data coming through, particularly since the process is initiated from a source external to R/3.
    The file data is coming from a warehouse management system into XI, and then being passed from XI through to the function IDOC_INPUT_DELVRY.
    Cheers,
    Stephen

    go thru the below information.
    IDOCs:
    - IDOC is an Intermediate Document'. It is simply a data container used to exchange information
    between any two processes that can understand the syntax and semantics of the data.
    An IDOC is created as a result of executing an Outbound ALE or EDI process.
    In an inbound ALE or EDI process, an IDOC serves as input to create an application document.
    -When an IDOC is created in the system , an unique number(16 Digits) is assigned to it.
    This number is unique with in the client.
    - IDOCs are independent of the sending and receiving systems.
    - IDOCs are independent of the direction of data exchange.
    - In the IDOCs, data is stored in text format.
    - IDOC will wait until the Remote System is Active.
    *IDOC Definition Components
    - Basic Idoc Type: Basic Idoc type defines the structure and format of the business document
    that is to be exchanged between two systems. Basic Idoc type can refer to an SAP provided
    basic IDOC type or a customer developed basic IDOC type.
    - A basic IDOC type has the following characteristics:
    Name : A basic Idoc type can be assigned upto a thirty character name.
    List of permitted segments: The segments make up the IDOC structure.
    Hierarchy of segments : The hierarchy of segments specifies the physical sequence and
    any parent - child relationship in the segments.
    Mandatory Vs Optional Segments : When used in the IDOC type, each segment has
    an attribute that defines whether the segment is option or mandatory.
    Minimum/Maximum range for each segment: It defines the maximum and minimum
    number of timesa data record corresponding to a segment cn exist in an IDOC.
    - Segments : A segment defines the format and structure of a data record.
    Segments are reusable componets. A segment consists of various fields that represent data
    in data record.
    IDOC Run time components:
    - A unique IDOC number 16 digits is allocated.
    - One control record is attached to the IDOC.
    - Segments translate into data records.
    - Status records are attached.
    - Sytax rules are checked.
    IDOC Record Types:
    1. Control Record : The control record contains all of the control information about an IDOC,
    this information basically includes the IDOC number, sender and receiver information,
    and information such as the message type it represents and the IDOC type.
    - there is only one control record per IDOC.
    - The stucture of the control record is the same for all the IDOCs and is defined by SAP.
    - The structure of the control record is defined by the data dictionary structure EDI_DC40.
    - The control record is stored in the EDIDC table.
    2. Data Record : Data records contain the application data. A data record has two sections
    Administrative Section and a Data section.
    - The Administrative section cotain the segment name, client, IDOC number, segment number,
    hierarchy level information.
    - The Data section of a data record is a stram of 1000 bytes where the actual data resides.
    - The data record is defined by the data dictionary structure EDI_DD40.
    - Data records for IDOCs stored in the EDID4 table.
    3. Status Record : Status records are attaced to an IDOC throughout the process as
    the IDOC achieves different milestones or encounters an error. At every milestone a statu code,
    date and time are assigned.
    - Status codes 01 to 49 are reserved for OUtbound process, 50 and above are reserved for
    inbound processes.
    Message Type: Identifies what type of information transformed between logical systems or partners.
    Message type is not a local object type , it is transportable.
    Port : A Port defines the medium in which data is exchanged between the two systems in
    the ALE process, IDocs are transferred via memory.
    1. TRFC ports are used for ALE communicaion.
    2. File Ports used by EDI
    3. CPI-C ports used to communicate with R/2 systems.
    4. Internet ports used to connect with Internet Applications.
    5. ABAP-PI ports used to process data via the ABAP programming interface.
    6. XML ports used to process files in XML format.
    Partner Profiles:
    A partner profile has three views, which maintain different parameters for the partner.
    1. The General Parameters View : Values are stored in table EDPP1.
    2. The Outbound Parameters view : Values are stored in table EDP13, except for the
    Message control parameter , which are stored in table EDP12.
    3. The Inbound Parameters View: Values are stored in table EDP21.
    Transaction Codes :
    WE31- Segment Creation
    WE30 - IDOC structure
    WE81 - Message type creation
    WE82 - Link between Message type and IDOC type.
    WE21 - Creation of POrt
    WE20 - Partner Profile creation
    WE19 - Test tool for IDOC Processing.
    SALE - ALE (Application Linking and Enabling) settings
    Go through the link for basics related to IDOCs:
    http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a6cdd507d11d18ee90000e8366fc2/plain.htm
    Check these links.
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
    Please check this PDF documents for ALE and IDoc.
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
    Check below link. It will give the step by step procedure for IDOC creation.
    http://www.supinfo-projects.com/cn/2005/idocs_en/2/
    Check these out..
    Re: How to create IDOC
    Check below link. It will give the step by step procedure for IDOC creation.
    http://www.supinfo-projects.com/cn/2005/idocs_en/2/
    ALE/ IDOC
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
    go trough these links.
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    You need to excahnge data between systems you need an interface as medium for data transfer.
    IDoc also treat one of the interface options for data transfer.
    Check this link
    http://www.thespot4sap.com/Articles/SAP_ALE_Other_Concepts_Conclusion.asp
    IDOC Debugging:
    1) We generally go for customized IDocs if none of the SAP standard IDoc does not suit our need/business process. Creating is custom IDoc should be a very stringent process. The SAP standard IDocs should be rigorously checked (if any user exits can be of our help or IDoc extension will solve the purpose).
    2) WE19 is the test tool by which we can create IDocs to see whether our functionality is working. It is mostly used to debug inbound function modules.
    For outbound function module debugging you can use the following:
    1) RBDMIDOC - for master IDocs configured via change pointers.
    2) RSNASTED - for transaction IDocs with output/message control.
    3) RSEOUT00 - For IDoc whose status is "to be processed".

  • Debugging a Hierarchy user exit ZXRSAU04

    Guys,
    We have added custom code to the hierarchy user exit ZXRSAU04. I am trying to debug it by right clicking the datapacket and then doing a simulate update. I am getting the message "simulated hierarchies cannot be edited". I added an endless loop in the exit ZXRSAU04 and then loaded a hierarchy. It didn't stop there. If anyone has debugged a hierarchy user exit, please let me know the steps for debugging it. We are on BW version 3.1c.
    Thanks,
    SSB.

    Was this ever solved? I know it was a long time ago, but I am having a similar problem while trying to update my Merchandise Hierarchy.
    I have implemented the code found here : http://www.element61.be/e/resourc-detail.asp?ResourceId=189
    However, I don't believe my ABAP is running, which would put in the new values. I have inserted a never-ending loop in the code, and still that is not hit, neither are any of the debug points inserted at various points in the include files.
    Cheers,
    Andrew

  • Debugging the user exit in ECC

    hi
    we have enabled ATP check in system. when we create a sales order in ECC the call  goes to SCM and it creates the purchase requisition in ECC. we need to capture this purchase requisition number somewhere when we create the sales order. we figured out several user exits that are called during CIF transfer for example  in ECC system
    EXIT_SAPLCPUR_001
    EXIT_SAPLMEPI_001
    EXIT_SAPLMEPI_002
    EXIT_SAPLMEPI_003
    EXIT_SAPLMEPI_004
    EXIT_SAPLMEPI_005
    EXIT_SAPLMEPI_006
    EXIT_SAPLMEPI_007
    but when i put a session/external break point nothing happens. it does not stop. any suggestions
    thanks
    sankar

    If you are trying to set the breakpoint inside the user exit FM ,then the breakpoint will be caught only if an active project exists.
    Try putting a breakpoint outside the user exit FM at some statement.
    Also when you get into the debugger, activate the "update debuggeR"
    Hope this helps!

  • How to find out appropriate user exit

    Hi,
    I want to know how to find out the user exit that matches to the requirement. Suppose for a material master program, there are so many include programs hence im unable to find call custer-function and even unable to debug an appropriate include. Please help me out how to learn user exits in a rightious way.
    Thanks
    Basu

    Look for program SAPICSS_ in your system and run it. This program can also be found under CMOD menu:  Utilities -> SAP enhancements.
    This will only give you the CMOD user exits.
    There is a program someone made that searches for all sorts of user-exits (including BADI's etc.). I remember that it was posted on sapfans.com
    Edited by: Maen Anachronos on Apr 6, 2009 3:22 PM

  • How to get the values from form calls in user exit?

    Hi all,
    I am not getting a specific value readily in an user exit.
    ?Can any one tell me how to find what are the fields,tables available in various form calls(visible while debugging) in an user exit.
    For example sapxkl is one ofthe callls...(sapxkl)<table>[] will hold some data.how to find what r the values available for <table>.
    Thanks.
    Edited by: sanjay_ask on Apr 16, 2010 10:43 PM

    HI ,
    Use this line of code
      field-symbols: <l_fs> type any.
      data: l_value type char20.
    Get Plant
      l_value =  '(SAPLCEI0)GV_WERKS'. " Here give the program name and variable name
      assign (l_value) to <l_fs>.
      v_werks = <l_fs>.         " Instead of V_werks use you internal table
    Thanks
    Subhankar

Maybe you are looking for