Q'S struck  in ECC 6.0

Hello Guru's
We have a Q struck in ECC 6.0 in which  the Q name R3AD_OBJCL destination CRM, status waitupdate  i want to know wht is this Q all abt , and what r the reason why it  is struck in ECC
How to over come this q
Thanks in advance
Regards
Sreeram

Hi ,
The Queue R3AD_* is used to perform a Delta Load from R/3 to CRM.
It is the naming convention followed for the Delta Loads.
For eg, The Intial load Queues will start from R3AI_..*
The possible reasons why the  Queue is not processed is because :
1. The Queue must have not got registered. You can the Inbound Q's using SMQR Tx and Outbound Q's using SMQS Tx.
2. If there is an Initial Load runnig for the same Object.
3.You can also manually delete the entries which are not processed and test the Queue as stated in one of the post above..
Hope it will help you..
Best Regards,
Vignesh Ravikumar.

Similar Messages

  • Client proxy message strucked in ECC queues

    Hi All,
    I am working on Proxy interface. My interface is like below
    ECC 6----
    >PI (7.1) -
    >File
    I had done the entire configuration in ECC and PI for proxy activation. While testing the interface in ECC system messages processed successfully, but the message strucked in queues (SMQ2) in ECC system. If run the queue manually the message processed successfully to the PI.
    Can you please tell any more configurations required?
    Regards,
    Ramesh

    Hi,
    The queue used for Proxy call is not registerd in ECC system. You need to register the queue to process successfully.
    you will get the name of Queue from SMQ2 t-code and register it with t-code SMQR.
    Thanks
    Swarup
    Edited by: Swarup Sawant on Aug 24, 2009 8:03 AM

  • Messages strucking in Receiver ECC

    Hi,
           I have a scenario i.e. non-SAP to PI to SAP ECC. In that, in PI we are getting Successful flags on every monitoring, but data is not inserting in ECC tables, due to Queues strucked in ECC (smq2) and we can see those messages with status scheduled in SXMB_MONI tcode in ECC system. Means messages are strucked in Queue. Some times In production environment it is giving very critical issue. Here I have a doubt. Between PI and ECC only one Queue is available or multiple?  If one message struked in Queue remaining all the messages also be strucking. If only one queue is avail between PI and ECC, Is there any other way to increase number of Queues to overcome this problem.
    Thanks & Regards,
    Srihari.

    Hi Srihari ,
    Every R/3 system will have the concept of queue.
    If the messages are passed successfully from PI and are stuck up in ECC means there might be some data issue with the first failed message in queue. you can save that message using save LUW and then thus releasing rest of messages from queue.
    even if you increase number of queues on ECC , queue stuck still can be a issue. Only way is to remove problamatic message from queue and clear the queue. lateron you can investigate on error message .
    Regards,
    Sheetal

  • IDOC meta deta refresh related query

    Hi ,
    We are dealing with IDOC to file scenario.  The scenario is created and transported to Production .
    Suppose after that we have to add extra field in the IDOC .The ABAP guys  created the new IDOC in SAP system we deleted the old IDOC imported new one  in IR (dev) and done the mapping initally the field was not coming  but after  meta deta refresh (IDX2) the field has succesfully come in PI and sent to destination . We have transported the change ( IDOC and the message mapping ) to other env . Now do we have to refresh the meta deta manually in that environment also? or can we transport the meta deta also in other environment  to avoid manually deletion/updation of meta deta in evry env .
    Kindly update me
    Regards,
    Saurabh

    thanks again
    Even we were also have the same understanding that we don't need to do any thing extra for meta deta refresh in other env.
    but recently we are facing issue in pre prod that  the IDOC(in which extra field has been added ) get struck in ECC and does not come to PI untill we have not manually uploaded the meta deta .  so the client is asking that instead of manual deletion/updation of meta deta can we transport the meta deta or make the process automated .
    Regards,
    Saurabh

  • How to do configuration in Integration Builder for Idoc to PI to EDI system?

    Hi Experts.
    I am working on one interface which is SAP IDOC (DESADV.DELVRY03) >> to>> PI >> to>> EDI system.
    I am done with all ESR objects,
    Can anyone help me about how to and what configuration required to be done in Integration Builder?
    And after configuration how should I test/check my interface?
    Please give your suggestions.
    Any suggestion will be rewarded.
    Thanks in advance.
    Regards,
    Dipen.

    Hi Dipen,
    Configuration:
    SAP ECC
    You have to configure the Output types in NACE and Partner Profile in WE20 properly.
    SAP PI
    In PI, You have to configure the port in IDX1 and load the meta-data in IDX2.
    Testing:
    While on saving the Delivery document, IDoc would be triggered and it would be routed to PI based on the port that you have configured in the partner profile.
    You can check the status of the IDoc in WE02/WE05. Check the tRFC queue in SM58 whether the IDoc is struck in ECC due to any communication issues.
    In PI, you can check whether the IDoc is received or not in the transaction IDX5. If you double-click on the message, it would be routed to the message monitoring.
    The status of the message in the receiver side can be checked in the communication channel monitoring.
    You can let me know if you need any more info.
    Thanks,
    Kanda

  • Struck up with R3AD_* Queues in SMQ1(Outbound Queue in ECC Side)

    Hi ,
    I am using CRM Middleware for replicating business partner(BP) from CRM to ECC
    and material from ECC to CRM.
    BP and Materials are replicating well.
    My Issue is,
    while checking queues in SMQ1 (Outbound Queue in ECC Side), i am getting many queues are pending also
    status as "SYSFAIL".
    QUEUE Names are R3AD_000000123,R3AD_000000139,R3AD_000000141... R3AD_*,etc..
    I tried to unlock the queues and activated, afterthat also queue status is "SYSFAIL". Then i checked in CRM side
    Transaction Code SMW01,
    BDOC Details:
    BDOC State Description: Information no processing.
    BDOC Type :BUS_TRANS_MSG.
    ERROR Message:
       a.Processing of document with GUID 4E57E4A5108162A7E10000000A0BE02A is canceled.
      b.Business transaction type ZEQQ does not exist.
      c.Validation error occurred: Module CRM_DOWNLOAD_BTMBDOC_VAL, BDoc type BUS_TRANS_MSG.
    Thanks and Regards,
    Ravi A

    Maintain a filter in ECC go to Tcode SM30 , then go to table/view and enter CRMRFCPAR click maintain and enter
    User CRM
    Object Name SALESDOCUMENT
    Destination xxxxxxxxxxxx
    Load Type delta download
    Queue Name
    Queue Name
    BAPINAME
    INFO
    InQueue Flag X
    Send XML
    CRM Release 700
    Logical system xxxxxxxxxxx
    this will stop the flow of ecc sales documents to crm
    this will also stop Bdcos in SMW01
    Please let me know if this helped

  • SAP ECC Installation struck at Import ABAP

    Hi All,
    I am currently installing SAP ECC 6.0 EHP 7 on Suse Linux 11 SP3. The database is SAP HANA Rev 82.
    The installation is hung at import ABAP and log files are also not being updated at the OS level. Currently SAPSSEXC is being imported.
    Please find the attached logs for reference. Kindly help.
    PS: Rename the attachment logs.zip.txt to logs.zip.
    Regards,
    Abhishek

    Hi All,
    A bit worried now. I am getting the following error message in the index server log, can someone guide me why this is happening?
    [39386]{-1}[30/-1] 2015-04-30 01:24:05.738807 e SERVER_TRACE     TRexApiAdmin.cpp(01508) : TRexApiAdmin::mergeDeltaIndexLocal, Index Id: SAP<SID>:REPOSRC (169505), main memory merge not supported on tables containing disk lobs!
    [39386]{-1}[30/-1] 2015-04-30 01:24:05.738868 e Mergedog         Mergedog.cpp(01155) : Automerge failed: {IndexName: REPOSRC, Trigger: 7, ReclaimDelta: false, DeltaMerge: true, MemoryMerge: true, OptimizeCompression: false, MainSize: 3056}, error: error during merge of delta index occurred(2450)
    Regards,
    Abhishek

  • ISR NATIVE CONTROLS  ERP -2005 is not working in ECC 6.0, MSS 1.0 Version

    Hi,
    Does anybody knows, why the ISR Controls for ERP 2005 is not working properly.  We utilized the DropDown List Controls, we binded to the correct field in the FORM. We have filled the ADDITIONAL_DATA table, on the SET_ADDITIONAL_VALUES method also, to populate .
    The DropDown values are not populating in runtime.
    We are running ECC 6 Version, Basis is on SP12, and Application Platform is on SP09.  We have MSS 1.0 for SP 10.
    What might be the problem, what do  you feel about procedure in ISR Controls binding? 
    INFO: It doesn't have that SAP-VHLIST , illusion here. 
    Please guide me , as I am strucked from all ways, any note, patch to apply,  any config issue.
    thanks,
    chitti babu

    Hello,
    In case of DDLB, apart from the binding, there's something else needs to be done.
    Goto binding tab : incase adobe life cycle designer 7.1, a link "Specify item values" is highlighted.
    $record.sap-vhlist.FIELDNAME\.DATA\.FIELD.item[*].
    Item Text : text
    Item Key :key.
    This should resolve ths issue.
    Hope this helps.
    Best Regards,
    Saujanya

  • Planned orders are not converted into process orders in ECC.

    Dear All,
    The issue is that Planned orders with conversion tick are not publishing in ECC as manufacturing orders. We did check the relevant master data consistency between APO and ECC and it seems fine.
    We have tried to send the conversion from APO to ECC,all the orders stuck in the R1P inbound queue with error - Order no. XXXX does not exist
    Message no. C/006.
    Based on above message and error we found SAP Note 515740 - Inconsistencies in table CIFORDMAP for this issue.
    Used the transaction SE38 and created RCFORDCH report and 'Checking inconsistencies in table CIFORDMAP'
    Here it shows order series stuck in queues no longer exists.
    But not sure how to reconcile the inconsistency in the CIFORDMAP table.
    Would appreciate your advice.
    Regards,
    Sajit SIngh

    Hi Sajit Singh,
    Could you take some sample items struck for order conversion and check
    whether active PPDS & SNP PPMs available. 
    In some cases, conversion will be affected for want of PPMs.  If it is the
    case with you, try generating the PPM first for that sample item and retry
    converting the orders.
    Could you please check and confirm this.
    Regards
    R. Senthil Mareeswaran.

  • Error while loading data from ECC to BI

    Hi BW Experts,
    while loading data from ECC 6.0 to BI  i got error in details tab of the infopackage as datapackage 1  arrived in bw processing not yet finished.
    Could any one help me out?
    Thanks

    Amar,
       please check the source system job status. If its successfully completed then we can expect data load sucess in BW side.
    to check source system status: RSMO> select related load>in Menu Environment-->Job overview in source system.
    once this over check the TRFC or IDocs struck
    if TRFC, chk in TCode-SM58 or from environment select TRFC from source/data warhouse.
    if you are finding TRFcs are in stuck just select and run manually to complete.
    M

  • Screen output without connection to user, Message struck at inbound queue

    Chaps,
    I executed inbound proxy form PI 7.0, the message was struck in the inbound queue of ECC 6.0,
    with status text "Screen output without connection to user" then when I apply execute LUW then it is converted to
    "ThiSend:bad tm type /connection closed (no data)".
    when i test the same message from 'SPROXY' t.code, inbound proxy class was working fine.
    I came to know that when we call an ABAP program in side a proxy then it will throw same error what I got by checking the below url
    Message struck at inbound que in server proxy
    But in my proxy. I am just putting the data into z table and on some condition I am calling some other BAPI call.
    Here my doubt is calling the SUBMIT for other ABAP program is same as calling the BAPI call?
    because in the above thread clearly saying that don't use the other ABAP program in proxies. is the same case for calling the BAPI call into the proxy?
    In proxy, the logic is I am just simply reading the data from IS(integration server, PI7.0 SP 18) to ECC 6.0(SP14) if the row is not there the data is reading into table. If row is already there then it is stuck up in SMQ2 (inbound queue) of the ECC
    am I missing any basic things? please guide.

    But in my proxy. I am just putting the data into z table and on some condition I am calling some other BAPI call.
    Here my doubt is calling the SUBMIT for other ABAP program is same as calling the BAPI call?
    I too believe ..
    because in the above thread clearly saying that don't use the other ABAP program in proxies. is the same case for calling the BAPI call into the proxy?
    It is saying not suggestable...!!!! BAPI calls work perfectly !1
    In proxy, the logic is I am just simply reading the data from IS(integration server, PI7.0 SP 18) to ECC 6.0(SP14) if the row is not there the data is reading into table. If row is already there then it is stuck up in SMQ2 (inbound queue) of the ECC
    am I missing any basic things? please guide.
    Seems so,
    Lets try below things..
    1. Plz check the user is having auth to run the executable program in ECC.
    2. It seems that you are not using the proxy structures in a correct way..and check the calling program also..!!
    Edited by: Santosh Rawat on Jul 30, 2009 1:12 PM

  • Data struck up in ALE inbox

    Hi,
    While tried to load Masterdata from ECC,  Data struck-up in ALE inbox E1RSSH -> E1RSHIE and it is popping up with a error in process monitoring that 21,35 and 65 node id's are missing. PLease help me out with process of eliminating those records and load the data into Info object.

    Hi,
    Is the job in source system still active. Job name BI_reqnumber
    Also check SM66 in both BW and source system. If you are loading hierarchy it generally takse time to load it.
    Regards,
    Pravin
    Edited by: Pravin Karkhanis on May 28, 2010 3:19 AM

  • Short dump in queue while transfering billing document to the ECC.

    Hi,
    While transferring billing document to ECC we got the error SYSFAIL and The running application consciously caused an abort.
    please find the attached ST22 dump and do the needful. Please give th mail id i will send dump.
    Information on where terminated                                                                   
        Termination occurred in the ABAP program "SAPLCOINT_TP" - in                                  
         "COINT_TPOST_IT_INSERT".                                                                     
        The main program was "SAPMSSY1 ".                                                                               
    In the source code you have the termination point in line 92                                  
        of the (Include) program "LCOINT_TPU03".  
    62     EXPORTING                                                                               
    63       T006_MSEHI = I_MEINH                                                                  
       64     EXCEPTIONS                                                                               
    65       NOT_FOUND  = 1.                                                                       
       66   IF SY-SUBRC = 0.                                                                          
       67     LS_COINT_TPOST_IT-MEHT  = I_MEINH.                                                      
       68   ENDIF.                                                                               
    69   LS_COINT_TPOST_IT-BETRG    = I_BETRAG.                                                    
       70   LS_COINT_TPOST_IT-CURRENCY = I_CURRENCY.                                                  
       71 * Additional data                                                                               
    72   LS_COINT_TPOST_IT-MANDT = SY-MANDT.                                                       
       73   IF NOT I_DATE IS INITIAL.                                                                 
       74     LS_COINT_TPOST_IT-BDATE  = I_DATE.                                                      
       75   ENDIF.                                                                               
    76   LS_COINT_TPOST_IT-REVERSE  = I_REVERSE.                                                   
       77   LS_COINT_TPOST_IT-VORGNG   = COINT_BILLING.                                               
       78 * Derive BUZEI                                                                               
    79   SELECT MAX( BUZEI ) FROM COINT_TPOST_IT INTO LD_BUZEI                                     
       80                                           WHERE GUID = I_GUID.                              
       81 * begin insert note 1003536                                                                 
       82   SELECT SINGLE * FROM COINT_TPOST_IT INTO LS_COINT_TPOST_IT_OLD                            
       83                   WHERE GUID  =  I_GUID                                                     
       84                   AND   BUZEI =  LD_BUZEI.                                                  
       85                                                                               
    86   CLEAR LS_COINT_TPOST_IT_OLD-BUZEI.                                                        
       87   CLEAR LS_COINT_TPOST_IT_OLD-TIMESTMP.                                                     
       88   CLEAR LS_COINT_TPOST_IT_OLD-PROCESSED.                                                    
       89   CLEAR LS_COINT_TPOST_IT_OLD-CHANGED.                                                      
       90                                                                               
    91   IF LS_COINT_TPOST_IT = LS_COINT_TPOST_IT_OLD.                                             
    >>>>>     MESSAGE TEXT-X01 TYPE 'X'.                                                              
       93   ENDIF.                                                                               
    94 * end insert note 1003536                                                                   
       95                                                                               
    96   ADD 1 TO LD_BUZEI.                                                                        
       97   LS_COINT_TPOST_IT-BUZEI = LD_BUZEI.                                                       
       98 * Get TIMESTMP                                                                               
    99   PERFORM GET_TIME_STAMP CHANGING LD_TIMESTAMP.                                             
      100   LS_COINT_TPOST_IT-TIMESTMP = LD_TIMESTAMP.                                                
      101 * Update COINT_TPOST_HD                                                                     
      102   IF NOT LD_INSERT_HD IS INITIAL.                                                           
      103     CALL FUNCTION 'COINT_TPOST_HD_INSERT'                                                   
      104       EXPORTING                                                                               
    105         I_GUID  = I_GUID                                                                    
      106         I_OBJNR = LD_OBJNR                                                                  
      107         I_KOKRS = LD_KOKRS                                                                  
      108         I_DATE  = LS_COINT_TPOST_HD-BDATE                                                   
      109       EXCEPTIONS                                                                               
    110         OTHERS  = 3.                                                                        
      111   ENDIF.                          
    Best Regards,
    Prakesh

    Hi,
    Can you plz help in my issue .
    Dear Gurus,
    Find the below scenario followed by us.
    1.Created the service order with the ZSR3 procurement item category.
    2.PR created for the service order 35035201 in ECC with no 0070088937.
    3.One queue is struck with the below details.
    4.If we re process the queue it will process with out any error and then only our document flow of the CRM service order line item.
    Plz check the queue name R3AD_CRM_SRV_0035025201 in CRM system from
    Tcode SMQ2 which is in SYSFAIL status. The corresponding BDOC in SMW01
    tcode has validation error message " Module CRM_SRV_EXT_VAL, BDoc type
    CRM_SRV_XTN. Message no. SMW3018 " . Plz advise.
    As per my understanding and debugging i think it might be a issue
    As a standard CRM any change/update in ECC document 0070088937 should
    send back the information to the source CRM document with header GUID
    4E6527B4D3070C10E10080000A8C6828 . But system is referring to a
    different GUID where there is no document exist in CRM.
    Pls find the root cause to trigger different GUID when information is
    passed from ECC to CRM system.
    Best Regards,
    Prakesh

  • Job to process messages in Ready Status in SMQ2 ECC

    Hello friends,
    I am sending out messages from SAP ECC to PI  using proxy . The messages are getting stuck in SMQ2 in READY status. I have to each time manually go and activate the queue to send the message out of SAP ECC.
    Is there any job to process them automatically that needs to be set up in SAP ECC ?
    Thank you,
    Teresa

    Hi,
    Investigate why messages were strucked in Queues, there could be some reason, i suggest you too deregister and register queues once again.
    if possible assign sepprate queue for proxy interface.
    Regards,
    Raj

  • Message struck at inbound que in server proxy

    Sub :Message struck in SMQ2 with status text"ThiSend:bad tm type" .
    HI,
    I executed inbound proxy form PI 7.0, the message was struck in the inbound queue of ECC 6.0,
    with status text "ThiSend:bad tm type /connection closed (no data)".
    when i test the same message from 'SPROXY' t.code, inbound proxy class was working fine.
    I came to know the message scheduled due to function
    module sxms_async_exec
    and raising an exception as ThiSend:bad tm type/
    connection closed (no data)
    please provide the details like when this function
    module throw an exception as connection closed(no data).
    inside inbound proxy,
    could you please suggest us, what should be avoided inside the proxy
    method.
    warm regards
    mahesh.

    Hi Chaitanya,
                       previouly, i have the same problem.
                       At that time, we are using 'submit' command inside proxy method i.e i ABAP program.
                         because of that, the message was struck in the inbound que.
                       'submit' is not suggestable inside proxy method.
                       so, pls check your ABAP Program.
    warm regards
    mahesh.

Maybe you are looking for