on 09-26-2012 10:06 AM
Dear Experts
I am working on scenario file-> PI 7.0 ->SAP R/3(Using IDOC). I am getting outbound status of IDOC as "Message Scheduled on Outbound side" in SXMB_MONI.
I have checked in smq1, smq2 and SM58 in PI system no messages are there. And also checked in SMQ2 in ECC there also I didn't find any messages.
And also I have registered all Queues : SXMB_ADM ->Manage Queues --> Register
Please help me , where can I find these messages? and how to reprocess the same?
Thanks in Advance
Rakesh
Hi Rakesh,
did you checked the IDX5?
cheers,
Edu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi,
weird issue. If they are scheduled at SXMB_MONI and you've clicked at queue ID field of those messages and still cannot find them, seems like the message queue got deleted at some point. If you're the only person responsible of PI, maybe BASIS guys know something...
Like Anupam says, you could ask if those IDOCs could be reprocessed...
cheers,
Edu
HI Eduardo/Anupam,
I am sorry for the wrong reply. I am able to find the messages in IDX5.
Can you please advice me how to reprocess the same.
Thanks & Regards
Rakesh
Hi Rakesh,
it was quite weird IDX5 didn't show anything!
Go tx BD87:
http://wiki.sdn.sap.com/wiki/display/ABAP/Reprocess+or+Delete+an+Idoc
cheers,
Edu
Hi Rakesh,
I just don't know, I'm not an Idoc expert though.I'm sure some expert will shed some light on this.
May you have a look at SAP help?
http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/frameset.htm
cheers,
Edu
Message was edited by: Eduardo Bertoni did you check your connection authorization at sm59 with an authorization test?
Hi Rakesh,
The message may stuck up in the message queues of XI, showing the green flag with status ‘Message scheduled on outbound side’.
To unlock the message from queue, click on Queue ID. It takes you to another screen,
On new screen check the box corresponding to Queue ID and click on Number LUW Entries.
Click on the Unlock icon to pull out of queue. I think this will solve your issue. Otherwise you can reprocess the idoc by using transaction we11.
Best Regards,
Sagarika
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi,
check also smq3 (for recorded entries) just in case.
cheers,
Edu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Rakesh,
Try st22 and check what are the error logs being shown. Consult this with your BASIS team. Perhaps the message queue got deleted. Thus now you can re-trigger the idocs with permission from business and after consultation with BASIS team. BASIS team needs to have a look in the issue.
Is this incident happening for all idocs or specific one? If its for specific ones you can re-trigger the same again. If the problem is for all the idocs in the system
1. check sm59 connection to target system.
2. St22 for error logs
3. Idoc adapter settings if its showing correct details from SLD or not. In ID go to proper business system to which idocs are being sent and check adapter specific identifier.
4. Check if SLD is showing all business systems correctly or not.
Regards
Anupam
Hi Anupam,
I have checked in st22 , it is showing "Non of the selected short dumps exist" .
But I want to explain one more thing . I got this "Message scheduled on outbound ststus" for all the Idocs of one scenario for the 23nd and 24rd dates. But from 25th it is processing successful for the same scenario. now need to process the 23nd and 24th data manually from PI .
Thanks & Regards
Rakesh
Perhaps you use Event driver message proc.
http://help.sap.com/saphelp_nw70/helpdata/en/0d/5ab43b274a960de10000000a114084/frameset.htm
or someone deleted message like Michal mentioned
Br
M.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
>>>>"Message Scheduled on Outbound side".
maybe it was removed from SMQ2 by someone ? as this means that the message is in the queue - so if the queue is empty it might mean that someone took care of that...
Regards,
Michal Krawczyk
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.