CRM debugging

I'm trying to debug the CRM middleware for BP replication . I can see the outbound queue of the bp in CRM ( transaction smqs ) . But when I click on 'Debug LUW' button ( function module being CRM_UPLOAD_TRIGGER ) I'm expecting that I can start debugging in the target system which is R/3 4.6C . But I'm not able to debug . The user name
Is the same in both systems and the rfc destination has all the logon information . Is there any other issue which is preventing me from debugging . I have been able to do it earlier when the backend system is ECC 6.0 .
This is bp replication from CRM to R/3

Dear Radha,
Please check whether the Logical destination (R/3 Client) is in dialogue mode or not. If not, it will not allow you to go into ECC/ R/3 while debugging.
Thanks,
Atin

Similar Messages

  • Error in opening zip file after Patch 4 HF6 install

    Hello,
    Just upgraded to EP 6 SP 2 Patch 4 HF 6 on a Windows 2000/MSSQL instance.  In the cluster\server\managers\console_logs the error.log now contains the following;
    error during parse of jar file D:\usr\sap\XXXA\j2ee\j2ee_00\cluster\server\services\servlet_jsp\work\jspTemp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.runtime.admin.LoggingConsole\private\lib\com.sap.portal.runtime.admin.LoggingConsolecore.jar
    java.util.zip.ZipException: error in opening zip file.
    I also receive this error message for several other .jar files we've deployed.
    Any ideas what steps need to be taken to correct this message?
    Regards,
    John

    Here is a list of our .zip errors we see.  Two of these files are not 0-byte in length, they have been identified by a size at the end of the file.
    Also, I am checking on the LoggingConsole.  I'll post something when I have an answer.
    error during parse of jar file D:\usr\sap\DGPA\j2ee\j2ee_00\cluster\server\services\servlet_jsp\work\jspTemp\irj\root\WEB-INF\portal\portalapps\com.kcc.yy.kc.LoggingConsole\lib\com.kcc.yy.kc.LoggingConsoleapi.jar
    java.util.zip.ZipException: error in opening zip file
         at java.util.zip.ZipFile.open(Native Method)
    error during parse of jar file D:\usr\sap\DGPA\j2ee\j2ee_00\cluster\server\services\servlet_jsp\work\jspTemp\irj\root\WEB-INF\portal\portalapps\com.kcc.yy.kc.LoggingConsole\private\lib\com.kcc.yy.kc.LoggingConsolecore.jar
    java.util.zip.ZipException: error in opening zip file
         at java.util.zip.ZipFile.open(Native Method)
    error during parse of jar file D:\usr\sap\DGPA\j2ee\j2ee_00\cluster\server\services\servlet_jsp\work\jspTemp\irj\root\WEB-INF\portal\portalapps\com.sap.pct.crm.kcdam.crmkmconvkc\lib\com.sap.pct.crm.kcdam.crmkmconvkcapi.jar
    java.util.zip.ZipException: error in opening zip file
         at java.util.zip.ZipFile.open(Native Method)
    error during parse of jar file D:\usr\sap\DGPA\j2ee\j2ee_00\cluster\server\services\servlet_jsp\work\jspTemp\irj\root\WEB-INF\portal\portalapps\com.sap.pct.crm.kcdam.crmkmconvkc\private\lib\com.sap.pct.crm.kcdam.crmkmconvkccore.jar
    java.util.zip.ZipException: error in opening zip file
         at java.util.zip.ZipFile.open(Native Method)
    error during parse of jar file D:\usr\sap\DGPA\j2ee\j2ee_00\cluster\server\services\servlet_jsp\work\jspTemp\irj\root\WEB-INF\portal\portalapps\com.sap.pct.crm.kcdam.crmdamkc\lib\com.sap.pct.crm.kcdam.crmdamkcapi.jar
    java.util.zip.ZipException: error in opening zip file
         at java.util.zip.ZipFile.open(Native Method)
    error during parse of jar file D:\usr\sap\DGPA\j2ee\j2ee_00\cluster\server\services\servlet_jsp\work\jspTemp\irj\root\WEB-INF\portal\portalapps\com.sap.pct.crm.kcdam.crmdamkc\private\lib\com.sap.pct.crm.kcdam.crmdamkccore.jar
    java.util.zip.ZipException: error in opening zip file
         at java.util.zip.ZipFile.open(Native Method)
    error during parse of jar file D:\usr\sap\DGPA\j2ee\j2ee_00\cluster\server\services\servlet_jsp\work\jspTemp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.runtime.admin.LoggingConsole\lib\com.sap.portal.runtime.admin.LoggingConsoleapi.jar
    java.util.zip.ZipException: error in opening zip file
         at java.util.zip.ZipFile.open(Native Method)
    error during parse of jar file D:\usr\sap\DGPA\j2ee\j2ee_00\cluster\server\services\servlet_jsp\work\jspTemp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.runtime.admin.LoggingConsole\private\lib\com.sap.portal.runtime.admin.LoggingConsolecore.jar
    java.util.zip.ZipException: error in opening zip file
         at java.util.zip.ZipFile.open(Native Method)
    Portal initialization done.
    error during parse of jar file D:\usr\sap\DGPA\j2ee\j2ee_00\cluster\server\services\servlet_jsp\work\jspTemp\irj\root\WEB-INF\portal\portalapps\com.kcc.yy.kc.PortalMonitor\private\lib\com.kcc.yy.kc.PortalMonitorcore.jar
    java.util.zip.ZipException: error in opening zip file
         at java.util.zip.ZipFile.open(Native Method)
    error during parse of jar file D:\usr\sap\DGPA\j2ee\j2ee_00\cluster\server\services\servlet_jsp\work\jspTemp\irj\root\WEB-INF\portal\portalapps\com.kcc.yy.kc.atKCDesk.MastHead\lib\com.kcc.yy.kc.atKCDesk.MastHeadapi.jar
    java.util.zip.ZipException: error in opening zip file
         at java.util.zip.ZipFile.open(Native Method)
    error during parse of jar file D:\usr\sap\DGPA\j2ee\j2ee_00\cluster\server\services\servlet_jsp\work\jspTemp\irj\root\WEB-INF\portal\portalapps\com.kcc.yy.kc.atKCDesk.MastHead\exlib\com.kcc.yy.kc.atKC.MastHeadapi.jar - 1kb
    java.util.zip.ZipException: error in opening zip file
         at java.util.zip.ZipFile.open(Native Method)
    error during parse of jar file D:\usr\sap\DGPA\j2ee\j2ee_00\cluster\server\services\servlet_jsp\work\jspTemp\irj\root\WEB-INF\portal\portalapps\com.kcc.yy.kc.atKCDesk.MastHead\exlib\com.sap.portal.navigation.mastheadapi.jar
    java.util.zip.ZipException: error in opening zip file
         at java.util.zip.ZipFile.open(Native Method)
    error during parse of jar file D:\usr\sap\DGPA\j2ee\j2ee_00\cluster\server\services\servlet_jsp\work\jspTemp\irj\root\WEB-INF\portal\portalapps\com.kcc.yy.kc.atKCDesk.MastHead\private\lib\com.kcc.yy.kc.atKCDesk.MastHeadcore.jar
    java.util.zip.ZipException: error in opening zip file
         at java.util.zip.ZipFile.open(Native Method)
    error during parse of jar file D:\usr\sap\DGPA\j2ee\j2ee_00\cluster\server\services\servlet_jsp\work\jspTemp\irj\root\WEB-INF\portal\portalapps\com.kcc.yy.kc.atKCDesk.MastHead\private\exlib\com.kcc.yy.kc.atKC.MastHeadcore.jar - 5kb
    java.util.zip.ZipException: error in opening zip file
         at java.util.zip.ZipFile.open(Native Method)
    error during parse of jar file D:\usr\sap\DGPA\j2ee\j2ee_00\cluster\server\services\servlet_jsp\work\jspTemp\irj\root\WEB-INF\portal\portalapps\com.kcc.yy.kc.atKCDesk.ToolArea\lib\com.kcc.yy.kc.atKCDesk.ToolAreaapi.jar
    java.util.zip.ZipException: error in opening zip file
         at java.util.zip.ZipFile.open(Native Method)
    error during parse of jar file D:\usr\sap\DGPA\j2ee\j2ee_00\cluster\server\services\servlet_jsp\work\jspTemp\irj\root\WEB-INF\portal\portalapps\com.kcc.yy.kc.atKCDesk.ToolArea\private\lib\com.kcc.yy.kc.atKCDesk.ToolAreacore.jar
    java.util.zip.ZipException: error in opening zip file
         at java.util.zip.ZipFile.open(Native Method)
    error during parse of jar file D:\usr\sap\DGPA\j2ee\j2ee_00\cluster\server\services\servlet_jsp\work\jspTemp\irj\root\WEB-INF\portal\portalapps\com.kcc.yy.kc.atKC.pagesensitivity\lib\com.kcc.yy.kc.atKC.pagesensitivityapi.jar
    java.util.zip.ZipException: error in opening zip file
         at java.util.zip.ZipFile.open(Native Method)
    error during parse of jar file D:\usr\sap\DGPA\j2ee\j2ee_00\cluster\server\services\servlet_jsp\work\jspTemp\irj\root\WEB-INF\portal\portalapps\com.kcc.yy.kc.atKC.pagesensitivity\private\lib\com.kcc.yy.kc.atKC.pagesensitivitycore.jar
    java.util.zip.ZipException: error in opening zip file
         at java.util.zip.ZipFile.open(Native Method)
    error during parse of jar file D:\usr\sap\DGPA\j2ee\j2ee_00\cluster\server\services\servlet_jsp\work\jspTemp\irj\root\WEB-INF\portal\portalapps\com.kcc.yy.kc.atKC.layouts\lib\com.kcc.yy.kc.atKC.layoutsapi.jar
    java.util.zip.ZipException: error in opening zip file
         at java.util.zip.ZipFile.open(Native Method)
    error during parse of jar file D:\usr\sap\DGPA\j2ee\j2ee_00\cluster\server\services\servlet_jsp\work\jspTemp\irj\root\WEB-INF\portal\portalapps\com.kcc.yy.kc.atKC.layouts\private\lib\com.kcc.yy.kc.atKC.layoutscore.jar
    java.util.zip.ZipException: error in opening zip file
         at java.util.zip.ZipFile.open(Native Method)
    error during parse of jar file D:\usr\sap\DGPA\j2ee\j2ee_00\cluster\server\services\servlet_jsp\work\jspTemp\irj\root\WEB-INF\portal\portalapps\com.kcc.mk.kc.bb\private\lib\com.kcc.mk.kc.bbcore.jar
    java.util.zip.ZipException: error in opening zip file
         at java.util.zip.ZipFile.open(Native Method)
    [email protected]5c #
    error during parse of jar file D:\usr\sap\DGPA\j2ee\j2ee_00\cluster\server\services\servlet_jsp\work\jspTemp\irj\root\WEB-INF\portal\portalapps\com.kcc.yy.kc.atKC.Logon\lib\com.kcc.yy.kc.atKC.Logonapi.jar
    java.util.zip.ZipException: error in opening zip file
         at java.util.zip.ZipFile.open(Native Method)
    error during parse of jar file D:\usr\sap\DGPA\j2ee\j2ee_00\cluster\server\services\servlet_jsp\work\jspTemp\irj\root\WEB-INF\portal\portalapps\com.kcc.yy.kc.atKC.Logon\private\lib\com.kcc.yy.kc.atKC.Logoncore.jar
    java.util.zip.ZipException: error in opening zip file
         at java.util.zip.ZipFile.open(Native Method)
    error during parse of jar file D:\usr\sap\DGPA\j2ee\j2ee_00\cluster\server\services\servlet_jsp\work\jspTemp\irj\root\WEB-INF\portal\portalapps\com.kcc.yy.kc.systemviewer\private\lib\com.kcc.yy.kc.systemviewercore.jar
    java.util.zip.ZipException: error in opening zip file
         at java.util.zip.ZipFile.open(Native Method)
    [email protected]3e #
    error during parse of jar file D:\usr\sap\DGPA\j2ee\j2ee_00\cluster\server\services\servlet_jsp\work\jspTemp\irj\root\WEB-INF\portal\portalapps\com.sap.pct.crm.debug.SOAPTest\lib\Jcatestapi.jar
    java.util.zip.ZipException: error in opening zip file
         at java.util.zip.ZipFile.open(Native Method)

  • OES2 SP3: Master sends poison pill upon creation of new volumes

    I'm experiencing problems when creating a clustered pool and volume on
    OES2 SP3. After assigning a new FC LUN which is available on all nodes
    I'm using iManager to create a new pool and volume on the master node as
    described in the documentation. However, at some point in the procedure
    the master starts killing other nodes. Inspection with nssmu shows that
    the new pool is just available on some nodes. After a reboot everything
    is working nicely.
    Should I send the cluster to maintenance mode prior to adding a new
    volume? How can I force OES2 to scan for new pools other than rebooting
    the system? Is there a known problem or a TID for this behavior?
    Gnther

    Am 05.09.2012 09:38, schrieb Hans van den Heuvel:
    > On Tue, 04 Sep 2012 18:00:53 +0000, Andy Konecny wrote:
    >
    > Hi Andy
    >
    >> From this TID, it does look like the fix isn't generally available yet,
    >> especially given that the TID was last edited today.
    >
    > I have modified the wording in the TID, as the 'naming scheme' part
    > seemed to be confusing here.
    >
    > The should have read as in this particular tree, specific services are
    > installed and named in a specific way for easy identification purposes,
    > and these newly created cluster resources just did not comply to that.
    > They were just not named properly, nothing else.
    Sorry, but right now I'm completely confused. What are you talking about?
    From cluster administration manual:
    "10.1.1 Naming Conventions for Cluster Resources
    Cluster resource names can be up to 63 characters. Novell
    Cluster Services supports only
    alphanumeric characters and the underscore character in
    cluster resource names:
    ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwx yz0123456789_
    Special characters, such as the following, are not supported
    in cluster resource names:
    !@#$%&()
    Because the NSS pool name and Linux volume names are
    automatically used in the cluster resource
    name, do not use special characters !@#$%&() in names of NSS
    pools or Linux POSIX volumes that
    you plan to cluster enable."
    I did not use special characters in names of cluster resources, pools or
    volumes. So will my problem be still related to this TID?
    I will gave to go and check with CRM debugging.
    Günther

  • 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

  • Need help to enable trace/logging for java debugging CRM 5.0 WebShop

    Dear experts,
    I'm new to sap, and i'm working on CRM 5.0 WebShop J2ee application with nwdi.
    I have to add a new functionnality, which has to call a custom FM in CRM. This FM has been tested and is OK.
    I have read the 2 files SAP_ISA50_DevAndExtGuide.pdf and ISA50_DevAndExtTuts_v1_0.pdf which have explain to me the process flow and organization of the framework.
    By helping me with the tutorials, I wrote all the files for my functionnality, from the jsp with the form, to the custom business backend with the call of the FM with parameters and JCo connection. (+ custom BOM, custom BO, BE interface, BE CRM implementation)
    Everything builds without error, and I deploy the application on my test env.
    Then I go to my webapp, I call the custom jsp with form, I put values, then I validate the form, but my FM is not called, and I don't know where is the problem, because I can't see a trace of the process flow, to know where is the error.
    By searching in this forum I found 2 notes that explain how to activate debug trace for all the application, one note for systems before SP11 and another for systems with SP11 and higher. But I don't know how to see the patchlevel of the system (I went to system information of the j2ee server and the on ly thing I can notice is below the server0 properties : Kernel Version:  7.00 PatchLevel.
    In these notes I read about Visual Administrator : I found this directly on the server with remote desktop, but the progress bar at the bottom of the window don't arrives to 100% and I can't see the properties and values of the parameters for the Log.
    I went to XCM too, and set appinfo and logfiledownload to true, then went to Logging into e-commerce administration console : in the Log configuration tab, I can create new configurations but the effective severity automatically sets to error, even if I set All or Debug manually ; in the session log tab, i tried to launch the application, then start log, then validate my form, then stop log, but I can't find anything about the trace of the process flow in the generated file.
    Please help, I have to finish this for end of week and I'm alone ...
    PS I'm french, and don't speak very well English please excuse me.
    Thank you very much.
    J. Lag.

    Hi
    For logs follow this note no[Creation of logs for B2B and B2C Release 5.0|https://service.sap.com/sap/support/notes/1090753]
    Follow this code for calling custom Function Module
    1) ZBOM.java
    public class ZBOM extends DefaultBusinessObjectManager implements BOManager, BackendAware {
    public static final String ZCUSTOM_BOM = "ZCUSTOM-BOM";
    private ZFunction func;
    public ZBOM() { }
    public ZFunction getFUNC() {
      if (func== null) {
       func= new ZFunction();
       assignBackendObjectManager(func);  }
      return func; }
    public void release() { }
    2) ZFUNCTION.java
    public class ZFunction extends BOBase implements BackendAware {
    private ZInterface backendInterface;
    private BackendObjectManager bem;
    private ZInterface getInterface() {
      if (backendInterface == null) {
       try {
        backendInterface = (ZInterface) bem.createBackendBusinessObject("ZCustomBO");
       } catch (BackendException e) {
      return backendInterface;
    public void setBackendObjectManager(BackendObjectManager bem) {
      this.bem = bem;
    public String getCustomFunc(String value) {
      try {
       return getInterface().getIncotermListvalue) ;
      } catch (RuntimeException e) { return ""; }
    3)ZINTERFACE.java
    public interface ZInterface extends BackendBusinessObject {
         public  String getCustomFunc(String value);
    4) ZBACKEND.java
    public class ZBackend extends BackendBusinessObjectBaseSAP implements ZInterface {
         String exportvalue="";
         public String getCustomFunc(String value) {
              try {
                   Function func =getDefaultJCoConnection().getJCoFunction("Z_CUSTOM_FUNCTION_MODULE");
                   func.getImportParameterList().getField("IMPORTPARAMETER").setValue(value);
                   getDefaultJCoConnection().execute(func);
                   exportvalue = func.getExportParameterList().getString("IMPORTPARAMETER");
              } catch (Exception e) {
                   return exportvalue ;
    5) WEB_INF/xcm/customer/modification/bom-config.xml
    <BusinessObjectManager name="ZCUSTOM-BOM" className="com.sap.isa.custom.ZBOM"/>
    6) WEB_INF/xcm/customer/modification/bom-config.xml
    <config isa:extends="../config[@id='crmdefault']">          
       <businessObject type="ZCustomBO"
                    name="ZCustomBO"
                    className="com.sap.isa.custom.ZBackend"
                    connectionFactoryName="JCO"
                    defaultConnectionName="ISAStateless"/>           
    </config>
    Regards,
    [Sateesh Chandra|http://sateeshchandrach.googlepages.com/isa]

  • Debugging RFC function module from ECC to CRM

    Hi All,
    My requirement is to debug an RFC function module present in CRM(7.0) system from ECC(6.0) system. A report program in ECC will call CRM custom FM. I found many posts in SDN with the same issue and tried to implement suggestions provided there. But I couldn't succeed. The approach I followed is:
    I logged in to ECC report program and kept an external breakpoint just before the function module call.
    I logged in to CRM system, opened the function module and kept an external breakpoint there.
    In both the systems I provided the dialogue userid( id through which I log in to SAPGUI) in the system->settings->debugging option.
    In CRM I activated the external break point in  transaction SRDEBUG.
    Now when I execute the report program in ECC, control stops at the breakpoint. If I press F5 at the function call, control is not going to the external break point set in the CRM FM. I am getting output of FM directly.
    I tried with different settings like turning on the check box for IP matching and session breakpoint active immediate, switching to classic debugger etc. I also tried to provide the RFC user id instead of dialogue user but system throws exception saying only dialogue userids are allowed. I found that by inserting an infinite loop statement, control goes inside the RFC CRM FM but I prefer not to change the code.
    Please let me know if I missed anything.
    Thanks and Regards,
    Naren

    Hi,
    Debug RFC calls
    When an RFC function module is called it is usually not possible to debug the call, using the below techniques we can achieve the same. For this example we are calling an RFC enabled FM in ECC system from CRM system.
    Scenario 1: Calling a custom RFC FM
    STEP 1: Add an infinite loop in the remote custom Function Module (adding a u201CDO. ENDDO.u201D statement at the start of the FM would be enough).
    STEP 2: Execute your program in the CRM system. The execution stops at the RFC call, because of the infinite loop.
    STEP 3: Now login to the ECC system and go to transaction SM51 select the process which is executing the RFC and navigate to the menu: u201CProgram/Session->Program->Debuggingu201D this triggers the debugger session in a separate window.
    Scenario 2: Calling a Standard RFC FM
    When we are debugging a standard program we cannot add the infinite loop, hence we cannot go to SM51 and debug the work process. The RFC destination for the ECC system has a User specified, the RFC function module gets executed using this users credentials. Usually the basis team set up the RFC user as non Dialog user, this does not allow debugging. Contact your Basis team and get this changed to a dialog user enabling you to debug RFC function calls via the normal debugger.
    Note: User name configured in the RFC destination (transaction SM59) 
    Note: User type for the RFC User (transaction SU01D)
    Hope this will be helpful..

  • Middleware debug problem  for BP's from CRM to ECC

    I tried few steps to debug BP  changes from CRM to ECC but nothing is working ...
    I deregistered the Queue thru SMQS, made changes to BP.. went SMQ1 select the Queue name Double Click 2 times.. then select the Tool bar (Debug LUW)..    I'm getting "Nothing was selected"
    When is see SMW01, BDOC is processed green and data is transferred to ECC.
    I want to do debug  the BP queue and go to ECC system  as some of my custom EEWB fields are not passing to ECC correctly.
    Any help is highly appreciated.
    Thank you.

    Hi,
    Put a break point in FM  SMW3_MFLOW_UPDATETASKBDOC.
    Create a BP and before save type /h to activate debug, mark update debugging option.
    When stops in FM SMW3_MFLOW_UPDATETASKBDOC you must be sure to set header-dbgmode = 'X' this will make the bdoc stay stopped in SMW01.
    Go to SMW01 and type /h and process the bdoc.
    Put a break in FM CRM_UPLOAD_AFTER_MAP_HANDLER and be sure to change LV_SYNCHRON = 'X' this will allow you to connect in ECC.
    Put a break-point in the "CALL TRANSACTION" command. Change the mode of call transaction and you be able to debug XD*  update.
    Best Regards,
    Caíque Escaler

  • Lot of build errors in project created for debug CRM 5.0

    Hi SDN!
    I want to setup java debugging for CRM 5.0 modified application. According to note 1154496 I created project "crm_b2b".
    I took file src.zip from
    server\usr\sap\<system name>\<instance>\j2ee\cluster\<server number>\apps\sap.com\crmb2b at first try and from
    server\usr\sap\<system name>\<instance>\j2ee\cluster\<server number>\apps\sap.com\crmcrb2b at second try. After import NWDS performed building for my project and shows lot of build errors (more than 12 thousands for 1-st try and near 2 thousands for 2-nd try). I reduced some of error by adding jar files from crm war file to build path. But I don't know how to resolve errors like "The method hasPermissions(Permission[]) in the type UserBase is not applicable for the arguments(EserviceHierarchyPermission[])" (error in com.sap.eservice.common.user.permission.CommonPermission.java, line 186). Also some of errors concerned with requierd libraries in build path.
    My NWDS is 7.0.14
    CRM 5.0 SP 11
    Regards, Lev
    Edited by: Lev Kulaev on Jul 3, 2008 2:03 PM

    Hi!
    Here are my doings:
    1) set breakpoint in standart code
    2) run my debug configuartion
    3) run CRM 5.0
    4) NWDS stopped execution on breakpoint
    5) I right-click on variable, choose "Watch"
    6) NWDS shows me "error during evaluation" in "Expression" tab for selected variable
    I'm confusing since it was possible to use "Watch" for variables in CRM 4.0.
    Yes, you right, I can view all variabe values on "Variables" tab. I wanted to use "Expression" tab because it's more comfortable for me but it seems that I can use only "Variables" tab.
    So, thanks for help! My question is answered, but if you can give me more information about subject, you're welcome.
    Regards, Lev

  • How can we process the CRM Order again for second time in debugging mode

    Hi,
    Can anybody please tell me how can we process the CRM ORDER for second time.  that I want to process in debugging mode.
    Thanks,
    bsv

    Hi bsv,
    Are you trying to reprocess a BDOC for debugging purpose?
    If the BDOC is not with a final status, you will be able to reprocess it using the reprocess button in the smw01 search result list.
    And you may put /h on the popup when you click on the 'reprocess' button.
    If it is allowed to make some changes in the CRM ORDER for testin purpose, it would be easier to perform debugging.
    A more 'careless' way is to deactivate the outbound or inbound queue in transaction smqs or smqr, then in smq1 or smq2 to locate the interested queue, and click on button 'debug LUW'.
    Hongyan

  • How to debug proxies in CRM when called from ECC system

    Hi,
    My requirement is When a Post Goods Issue happens in ECC, the iobject is created in CRM system.
    The proxy is called in the ECC system. The implementation of the proxy is done in the CRM system.
    I am able to debug and see that the values are passed correctly to the proxy.
    In CRM system, the iobject is not created. So, i wanted to debug the implementation which is available in the CRM system.
    How can i debug in CRM system while the Post Goods Issue is done in the ECC system.
    Thanks in advance.
    Regards
    Shanthi

    hi ,  if you want to debug through ERP to CRM , you need to set a external breakpoint in CRM
    And to set the external breakpoint, you need to login CRM system by the middleware user, not a normal user.
    To check the middleware user name, you can search the view CRMRFCPAR in sm30  ERP, find out the RFC destination to CRM,  then check the user used in the RFC destination in SM59

  • Changes are not updated from ECC to CRM How to debug

    Hi,
    QCs 1140049726  and 1140047459 were updated in P20 system to remove the WBS.  This was done per normal P20 process and instructions.  P20 system correctly reflects that QCs have no WBS value and the contracts are BOX - all is correct in P20.
    CSP still shows these QCs as having a WBS assigned to them.  This is incorrect.  It has been over 24 hours since the P20 QCs were changed to reflect no WBS, but CSP still has not been replicated with the correct data.
    How to proceed with it. How to debug from ECC to CRM.
    Prem.

    Hello Prem,
    Could you please have a look at SAP note 656823?
    This note contains debug tips for btx data transfer. Please check point 6 which talks about the delta download.
    Hope this could be helpful.
    Best regards,
    Maggie

  • Debugging Middleware/BDOC when the material data transfered from R3 to CRM

    Hi,
    I am updating the status of Product in CRM using BADI - PRODUCT_CUSTOMER2 (R3_TO_CRM_MATERIAL). This happend when the status is updated in ECC (MM02).
    Now the problem is, I want to debug this BADI, when the material is updated in MM02.
    Could you please help me, how can I debug this BADI.
    Thanks,
    Sandeep

    Hello Sandeep,
    Please check below general steps to debug the delta download of ECC material.
    in R/3
    Set a break point in the function module CRS_MATERIAL_COLLECT_DATA (BTE Implementation)
    Create/Change the material in R/3 by using transaction MM01 or MM02 and press save button.
    Now you can debug the function module CRS_MATERIAL_COLLECT_DATA
    in CRM (inbound queue)
    Deregister the inbound queue R3AD_MATRIA* in transaction SMQR
    Go to the transaction SMQ2 select the inbound queue and debug the queue
    Set a break point on the mapping function module: COM_MAP_BAPIMTCS_TO_PROD_MAT
    for validation debugging Set a break point on the validation function module: COM_PRODUCT_MAT_VALIDATE
    I am sorry that I do not know where BADI  PRODUCT_CUSTOMER2 is called.
    Hope the baove information could be helpful.
    Best regards,
    Maggie

  • How can I debug CRM middleware function call in R/3?

    Hi there,
    I have extended the order line in CRM with a few fields that I need in R/3. I have also extended BAPE_VBAP, BAPE_VBAPX, VBAP_KOM and VBAP_KOMX in R/3 and I have implemented the CRM_DATAEXCHG_BADI BADI to manipulate the BAPIPAREX structure before the BAPI is called in R/3.
    My problem is that I cannot find out which BAPI is called in R/3 to update the sales order and I cannot find out where in CRM_UPLOAD_TO_OLTP it is called? Am I looking the wrong place? Ideally I want to check that the BAPI is called with the correct parameters from CRM, to see if the BADI did what it was supposed to do.
    Best regards,
    Anders

    Below I have stated how Orders flow from CRM to R3 - triggering which all exits in R3 and how we can reach them from CRM in debug.
    A) Block the CSA queue on CRM Side .
    B) Create an order and save it.
    C) Go back to the CSA queue and execute your queue in debug mode . Please put a BreakPoint in 385 line of FM   crm_upload_to_oltp. and line 422 of FM crm_r3_salesdocument_upload.
    D) Put a break point on line 385  of  FM   crm_upload_to_oltp and change the destination in parameter lt_actual_recipients-DEST to <R3SYSTEMRFCDEST>_DIALOG.
    E) Put a break point on line 422 of FM crm_r3_salesdocument_upload and Set the value of variable gv_synchronous_call  = X  in debug.
    F) Then you will be in R3 - debugging how data flows to R3 .
    Hope it helps.
    Regards,
    Kaushal

  • Debugging of ABAP Function Module through ISA Application CRM B2C 4.0

    Hi Experts
    There is way to Debug ABAP FM through ISA CRM b2c Application by Modifying some XML Files as per Extn Guide.
    I tried modifying the <APPLICATION_HOME>\WEB-INF\xcm\customer\modification\modification-config.xml After that I restarted the Application .
    But it is not Breaking for Both Statefull & Stateless FM after running my Application.
    With Some Help i found that if we try it on Remote System ( Means SAP GUI has to in Same System where CRM is Installed ???????????). but that is not Advisable Right !!!.
    So if i am able to Debug ABAP Function Module through ISA Application from any Other remote System.
    I think it will be very Useful.
    Thanks & Regards
    Ravi Sah

    Ravi
    It is other way around !!!
    You should have SAP GUI installed on the machine in which you start(access) your B2C Application. This enables for ABAP Debugging.
    We have tried this and works fine for us !!!
    Thanks
    Jack
    <b>Allot points if my post helps !!!</b>

  • How it is possible to debug the transfer of an order from CRM to ECC

    Hello,
    how is it possible to debug the coding when a CRM sales order is replicated to R/3?
    The outbound of SCM APO and/or the inbound of SAP R/3?
    Thank you in advance.

    Hello,
    Data flow from CRM to R/3 is like below:
    - Write the data to outbound queue of CRM
    - Wrtie data to Inbound queue of R/3
    - Validation and Save in R/3
    So you can debug from CRM outbound queue, by de-registering the queue in txn:SMQR
    R3AI_<OBJECT-NAME> In case of Initial Load
    R3AR_<Request-Name> In case of Request Load
    R3AD_*                           In case of Delta load
    Similarly you can de-register the queue in R/3 as well to debug the R/3 inbound queue.
    As you might be aware that MW generic module CRM_UPLOAD_TO_OLTP, would be called for any data transfer
    between CRM to R/3. You can start debugging from this point.
    Hope this helps!
    Best Regards,
    Shanthala Kudva.

Maybe you are looking for