SMQ1 problem

Dear Friends,
We are facing problem while clearing the queue on production server. After entering in to the SMQ1 xction, If we click on Bell icon (change view option), it gives Runtime Error : TIME_OUT. Previously it used to open. There is no problem with SMQ2 xction.
Could you please help in this.
Regards,
Vikas G

Hi Anil,
We are able to see lot of queues from different server. SAP Standard job is also getting completed successfully. But still there are large number of queue present.
For eg.
Number of Displayed Entries:         2,039,904
Number of Displayed Queues:                875
   Cl. Queue name               Destination                      Entries
   300 BW3000FI_AA_12           BWPCLNT300                                1
   300 BW3000FI_AP_4            BWPCLNT300                                1
   300 BW3000FI_AP_6            BWPCLNT300                                1
   300 BW3000FI_AR_4            BWPCLNT300                                1
   300 BW3000FI_GL_4            BWPCLNT300                               26
   300 BW3000FI_GL_6            BWPCLNT300                                1
   300 BW3002LIS_02_HDR         BWPCLNT300                           23,061
   300 BW3002LIS_02_ITM         BWPCLNT300                           37,731
   300 BW3002LIS_02_SCL         BWPCLNT300                           27,438
   300 BW3002LIS_03_BF          BWPCLNT300                            2,054
   300 BW3002LIS_04_PECOMP      BWPCLNT300                            2,042
   300 BW3002LIS_04_PEMATNR     BWPCLNT300                            2,042
   300 BW3002LIS_04_P_ARBPL     BWPCLNT300                            3,731
   300 BW3002LIS_04_P_COMP      BWPCLNT300                               21
   300 BW3002LIS_04_P_MATNR     BWPCLNT300                              566
   300 BW3002LIS_05_Q0ITEM      BWPCLNT300                               49
   300 BW3002LIS_05_Q0NOTIF     BWPCLNT300                              266
   300 BW3002LIS_05_QE1         BWPCLNT300                            5,432
   300 BW3002LIS_05_QVUDN       BWPCLNT300                            2,475
   300 BW3002LIS_11_VAITM       BWPCLNT300                           61,304
   300 BW3002LIS_11_VAITM       BWTCLNT300                        1,748,503
   300 BW3002LIS_11_V_ITM       BWPCLNT300                           44,460
   300 BW3002LIS_11_V_SSL       BWPCLNT300                           71,220
   300 BW3002LIS_13_VDITM       BWPCLNT300                            4,408
   300 CFFCCF002210.00251.0401 APOCLNT002                               24
   300 CFFCCF002210.00279.0700 APOCLNT002                               20
   300 CFFCCF0026005973B91      APOCLNT002                                1
   300 CFFCCF002A5552117R4      APOCLNT002                                3
   300 CFFCCF002A5557367R4      APOCLNT002                                1
   300 CFFCCF002M06000185F1     APOCLNT002                                3
Hope you would have understood the problem.
Regards,
Vikas G.

Similar Messages

Problem with SMQ1 to Delta Q

hello ,
We are facing the problem of transferring the data from SMQ1 to RSA7 for application 03 .
Rootcause - Because at the moment there are 2 million entries and the job is getting aborted due to memory call . The job is failing at the time of selection parameter when accessing the data . I have checked and found out the table TMCEXUPD , where number of document has been set as 000000 for application 03 . It means , the program is trying to access all the data from table , and due to bigger data set it is failing .
Is there any custmizing way way where I can eidt this table ?
Please advice .
Regards

THis Blog is related to Back up of SMQ1 ,
Here i am facing the problem with data transfer from smq1 to delta Q . I have given all the job details in my last messge .
short dump error - ABAP/4 processor: DBIF_RSQL_SQL_ERROR
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
neither
caught nor passed along using a RAISING clause, in the procedure
"SHOW_JOBSTATE" "(FUNCTION)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
Please advice .
Regards

SMQ1 deletion problem too much time larger queue

Hi Experts
We have to delete Queues from SMQ1, the problem is the data volume is huge in queues and system is taking too much time to delete these queues.
To delete 122000 records it took 4 hours to delete the queue from SMQ1.
Problem is we have to delete total of 51,48,000 records in total and one queue has huge data that is 26,10,000.
Is there any solution to fasten the process of deletion or any work around SMQ1 to delete the queues faster.
We are deleting queues in live system I mean the production system is up and running.
Thanks
Navneet

Hi Navnet,
Use the report RSTRFCQDS to delete the particular queue of SMQ1.
The report should check the inconsistencies between the tables:
TRFCQOUT, ARFCSSTATE, QREFTID and ARFCSDATA, therefore it will take time.
The fastest way to delete them is: you use a sql tool to delete all the entries in TRFCQOUT, ARFCSSATE, QREFTID and ARFCSDATA. In this case, you also delete the entries in SM58 (tRFC).
See also SAP Note 760113.
Rgds,
Colum

Meet a problem of data exchange for sale order from CRM to R3.

Dear Friends:
 I do the data exchange for sale oder from to R3 today , the problem's detail is as follows:
 When i save a sale order in CRM (Version is 5.0) . it can automatically generate a bdoc which bdoc type is BUS_TRANS_MSG. but the bdoc status alway is "Sent to receivers (not all have confirmed)". and the original order in CRM can not be change .it quote that "Document is being distributed - changes are not possible", so i check the order status analysis in detail .it presents two error messages ," Event 'BEFORE_CHANGE', attribute ' FINI': Error code for function module 'CRM_STATUS_BEFORE_COMPLETED_EC' , "Item is not yet completed in OLTP system". so i check the order in R/3 ,it has already been create and without any error messages.
 Would like to tell me how to solve it . thanks your any idear..

Hi Benjamin,
When performing uploads to R/3 from CRM there is a response from the OTLP system that is sent back to the CRM Middleware to confirm that the data records were received and processed correctly.
Here is a checklist you can run through to verfiy that the connections, systems and objects that are needed are all in place:
On R/3 system:
- Check R/3 outbound queue (transaction SMQ1) for any entries that are not reaching CRM.
- Check that all RFC destinations on R/3 are defined correctly and are pointing to CRM
- Check the CRMCONSUM table in R/3 to ensure CRM is registered as a consumer
- Check the CRMRFCPAR table in R/3 to ensure that order objects are valid for exchange between R/3 and CRM
- Check for any short dumps in R/3 (ST22/ST21)
On CRM:
- Are there entries stuck in the inbound queue (SMQ2) with R3AU* names?
- What does the CRM Middleware Trace show (SMWT)? Sometimes this has more detail than the specific BDoc overview (SMW01)
- Check for short dums in CRM (ST22)
Let us know what else you uncover and we can work from there.
Brad

Delta reocrds are not getting extracted . Problem with delta Quaue

Hello friends .
Could you please help me in this scenario ?
Its related to delta load from application 12 , - 2LIS_12_VCITM.
Some how data is not getting transferred from LBWQ to RSA7 . There are more than 200000 entries in LBWQ , but the job is not able to transfer any entries to RSA7.
For rest other application , data is going correctly .
The job status showing is correct , like XXXXX LUW are transferred there is no error in Job log , it technically correct .
I have found one notes , in SAP service market place , but still it doesnt match with my job status . My job status is NOTESID ..where as per the notes it should WKEDPI*** ( something like this ) .
I have taken below steps to solve this problem but still it doesnt work .
1.     Removed job from schedule ( the job for LBWQ to RSA7 ) and Executed the job manually .
2.     Executed Program RMSBW12.
3.     Deleted the Delta Q from RSA for application 12 and regenerated the same once again by running the infopackage , early delta initialization with out data transfer , . Once Delta Q is generated , run the job once again .
I hope , I tried with all correct way ..but still I could not able to transfer the data .
But with all above steps , still data is not transferred . Daily infopackage is running as per the schedule , and bringing only 0 record . If it still doesnt work then I have to do Re-initilization . and this is big cost for us . as we have to lock the sys for users and so on .
Could you please give me some tips , that how can I transferr the data from LBWQ to delta Q ( RSA7) . If it works then definitely , I will save my lot of time .
Please suggest me , how can I proceed . Please save me from this situation.
Many many thanks in advance.
Regards,

Hi Akshay,
Go to SMQ1 and check MCEX12 Queue. If your delta records are piling up in SMQ1 and not being transfered to RSA7, you need to check your back gound job control option once again.
The back ground collector job will collect the recrords from SMQ1 and push to RSA7.
Try to execute RMBWV312 program in SE38 and manully push all the recrods to RSA7. Once all the records are available in RSA7 you will find the MCEX12 queue will be cleared in SMQ1.
Cheers
Praveen

Problem with initial download from R/3 to CRM

Hello All,
Initial we were able to download & replicate all object from CRM to R/3 & vice versa such as product ,BP, sales documents & conditions etc. After that <<removed>> R/3 system was refreshed by Client itself. After refresh, connectivity between R/3 & CRM is disturbed.We have observed that while initial download we are facing problem in SMQ1 & SMQ2. After debugging we found that table entry i.e. table :- CRMMLSGUID from CRM & CRMPRLS from R/3 have Logical system guid values different( which should be identical). Because of this no replication is happening between CRM & R/3. How to rectify this?
Regards
Priyanka
Edited by: Rob Burbank on Dec 9, 2011 4:37 PM

Hello,
see note 588701:
"The queues are deliberately halted since the change of the logical
system name in the R/3 backend or the linking of new R/3 backend clients
to a client of the EBP/CRM Server with the same logical system name as a
client already linked to the R/3 backend would lead to severe data
inconsistencies in various CRM applications.
For this reason, such changes are not allowed on principle. The halting
of the queues prevents such data inconsistencies. The following
situations may lead to the queues being halted:
o The logical system of a client of an R/3 Backend system linked to
 the EBP/CRM server was changed in current operation.
o A new client of an R/3 Backend system or a client of a new R/3
 Backend system was linked to an existing client of the EBP/CRM
 server where the logical system name was already assigned to a
 client of an R/3 Backend system linked to the CRM server before.
There are different cases in which different forms of processing are
required or where several options exist:
- The logical system name of an R/3 Backend client was changed
 in current operation. In this case, the data hangs in the
 outbound queues of the R/3 Backend system as specified under
 point 1 of the symptom. In this case, the logical system name
 Seite 2
must be changed back to the original value. Then the outbound
 queues can be reactivated. If no data was transferred to the
 EBP/CRM server before the change, also a correctioin of the
 check table is possible.
- The same logical system name was used again in a new client of
 an R/3 Backend system that was linked to the EBP/CRM server.
 In this case, the data is in the inbound queue of the EBP/CRM
 server with the exception GUID_FOR_LOGSYS_CHANGED. In this
 case, the queue entries which have status SYSFAIL must be
 rejected, however, not the entire queues. If the new client of
 the R/3 Backend system you have linked has exactly the same
 data as the old client and if it is meant to replace the old
 client (that is, this was deactivated), also a correction of
 the check tables is possible. In this case, the inbound queues
 can be reactivated after the correction.
The correction of the corresponding check tables or the correct
procecure in individual cases is to be agreed upon with the support of
SAP or SAP consultants at the customer site. In justified cases, SAP can
carry out the correction of the check tables. "

Problem in CRM Credit Memo replication into ECC.

Dear all,
I am Creating a Credit Memo from CRM Complaint transaction. Complaint is getting created and saved without any errors. But the same is not replicating in ECC.
There are no errors in 'Transaction Error log', 'SMW01' and Inbound and Outbound Queues of both system. (SMQ1 and SMQ2)
No trace at all where the problem is coming.
The other functions like Return Request, Replacement and Substitute delivery are working fine within Same Complaint Transaction.
I have maintained all settings as per C26 & C28 Best Practices Documentation.
Still the problem exist. Request you to help me in resolving the issue. Your help will be highly appreciated
Best regards
Raghu ram
Edited by: Raghu Ram on Jun 14, 2010 2:43 PM

Hi,
Whats the solution to this issue ? We are facing exactly the same issue
Any relevant help is appreciated.
Thanks,
Ashish

Problems in transferring Scheduling Agreements from ECC to APO

Hi All
We are facing a strange problem in transferring scheduling agreements to APO.
When we create the integration model, it shows the selected scheduling agreements and vendors. On activating the integration model in CFM2 or CFM3, we do not get any error.
But when we check in APO, we do not see any scheduling agreements.
Can any one tell us what could be problem or where should we check to identify the issue ?
Best Regards
Mitesh

Hi Mitesh,
Did you try deleting all the integration models in CFM7 and trying again ? You could also try deleting the blocked queues in SMQ1.
Regards
Mukundan

Receiver File Adapter Problem

Hello,
I m message is in "To be Delivered" status
In the detials i could see following error :
Admin action: Redelivering the message failed, due to: com.sap.aii.af.ra.ms.api.DuplicateMessageException: Message ID 995b0348-a504-7441-e100-00000a1974ee(INBOUND) already exists in queue: File_http://sap.com/xi/XI/SystemRecv.
In SMQ1 & SMQ2 nothing is stucked.
How can i clear AE queue??
Thanks,
Maheshwari

Hi,
Go though the below link
I also faced the same problem. In my case some other sceanario CC are in error status and all messages in those CC are structed in message system i.e. in AE . So i rectified all error CCand i resend messages.
Difference between Business System and Business Service
If that is not the case then restart ur J2EE engine
Thanks,
Venkatesh

BPM problem in PI (XI 7.0)

Hi guys!
I have a scenario, where I use BPM. The underlying system is PI 7.0 (NW 2004s). I send Idoc from r/3, send it into bpm, this should make a sync call to web service and the ws response is mapped to ather idoc and sent again into r/3.
I created all the necessary objects in repository and directory and have a problem - when I send the Idoc, it is received by XI, but not processed... the status of the message is Scheduled. In the receiver interface and receiver there are no values in spite i have configured receiver and interface determination...
This is already the 2nd PI, where I have this problem. In the first one I was able to ommit the BPM, but here I am not. Does someone have the same experience? Problems with BPM in PI7.0?
I was looking also on the workbench component monitor - BPM - tha status is yellow triangle.. Sub-parts with NONgreen light are:
Maintain prefix numbers
Configure RFC destination
Schedule background job for missed deadlines
Schedule background job for work items with errors
Schedule background job for event queue
Schedule background job for clearing report
Schedule background job for deadline monitoring
How to fix these problems? is there any guide? Is it a task for basis person or consultant?
Thanx a lot for answer! Points are guaranteed
Olian

hi Olian,
as you are saying like your message came upto XI , but not proccessed so may be its a problem of queue so to TCode::SMQ1 and SMQ2 and clear this QUEUE.
hope this will solve this issue.
your one prob is Configure RFC destination
so check in R/3 sys Tcode : SM59 for RFC Destination
can you make remote login and connection test , if not so make technical Setting Properly.
hope this will help
regards
HONEY

IDoc to Fie Scenario Problem In PI

Hi Experts,
i am doing scenario like IDoc to file , i have created evrthing configurations all and all.
i trigger IDoc on r3 system using T-code we19, it showing sucess on r3 sytem. i am checking IDOc monitoring using t-code we05 to showing status 03. but the message not coming to PI system, what is problem it may be, please guide me
regards,
alekhya reddy.

Hi,
The Following are the Possible checks
1) Check in R/3 side SMQ1 & SMQ2
2) Check in R/3 side SM58
In R/3 system, Goto SM58 tcode and see if the IDOC have stuck up in Queue.
If the entry is available then select it and press F6, to push it manually.
This happens normally if IDOC stuck up in queues.
regards,
ganesh.

Problem XI -- R/3 System

Hi,
when I'm sending an idoc-message from XI to R/3, in the transaction "sxmb_moni" all seemed to work fine, but no idoc-message is receiving in the R/3-System.
The RFC-Destination works fine and also the port and the local system is created.
Can anybody help me please?
Thanks.
Regards
Stefan

Hi Stefan,
I think the RFC destination is missing some authorizations.
Anyway cross check the following:-
Check Transactions SMQ1 and SMQ2.
Check your RFC destination to R/3 from SM59.
Take a look at Message Monitoring at Runtime Workbench.
If nothing works out, delete the user and create it again with the same rights and password. This should solve your problem.
Regards.
Praveen

Message failed in SMQ1: XIAFUSER Password no longer valid

hello
i am having scenario where a sender file adapter picks the file and pushes to the BPM.
but when i checked in SXMB_MONI-> PE, i could see message status "Scheduled on the outbound side"
When checked in SMQ1 it gave me SYSFAIL error in the queue.
The error is "Password logon no longer possible - too many failed attempts" for XIAFUSER for function module "SWF_XI_MSG_RAISE_EVENT" at destination "WORKFLOW_LOCAL_500".
i checked the destination is fine. also the XIAFUSER is the service users and hence its password never expires or changes.
Thanks in advance.
Regards
Rajeev

hi,
XIAFUSER password is not expired it is locked because of too many failed attempts, ask your basis to release the lock or reset the password. this shd solve your problem.
Regards,
Sukarna

BPM scenario: error in SMQ1

Hi friends,
i have created a basic and simple scenario using BPM. i'm sending a xml file and receiving the same file without any transformation. but i'm getting SYS FAIL error in SMQ1. error is "password logon no longer possible. too many failed attempts".
more details of error table:
user:PIAFUSER
Function module: SWF_XI_MSG_RAISE_EVENT
Destination: WORKFLOW_LOCAL_001
program: SAPMSSY1
i checked for the user PIAFUSER and its not locked.
Note: other scenario which is not using BPM (text file to xml file) doesn't have any problem or error and working properly.
thanks,
Girish

i have created a basic and simple scenario using BPM
i checked for the user PIAFUSER and its not locked
other scenario which is not using BPM (text file to xml file) doesn't have any problem or error and working properly.
What about WF-BATCH ?
Regards,
Abhishek.

Problem on FTP receiver adapter

Hi, All,
I have two scenarios, both from XI SAP proxy to FTP receiver. And two scenarios are running almost at the same time. I need to send thousands of messages through these scenarios. Now I got problems when I sent out around 300 messages. The messages just stuck there and don't get through to FTP receiver communication channels. I configured these two FTP receiver communication channels in one Business System. I don't if that causes the problem. Please advise. Thanks a lot.
Jack

Hi! Jack,
According to my Understanding Check once again the below steps..
1. Check both Queues regarding SMQ1 and SMQ2.
2. Another thing is got to Communication Channel monitoring and select your Channel and check AUDIT
   LOG and ADD TIME STAMP such that u can get 2 things.
         a) first of all one information that up to at what time XI got picekd the file and
         b) Also u can observe another point that whether the File got picked from Source and holding in XI or else stil the XI doesn't got picked.
3. The most important thing is You asked how to clear all the queues right ? U can delete queues in two ways.
       a) U can go to SMQ1 and SMQ2 and delete the queues there it self
       b) THere is another way to monitor the XI MESSAGES in detail view by search category in
            ASYNCH and SYNCH mode and also based on ERRORS..
Note:: In order to monitor you need to check the monitoring on SYSTEM.JSP level. Go through the below linik.
http://HOSTNAME:PORT/MessagingSystem/monitor/systemStatus.jsp
THere u can get each and every messages and u can clear the BULK of messages in queue.
Regards:
Amar Srinivas Eli

SMQ1 problem

Similar Messages

Maybe you are looking for