Troubleshoot: How to process messages in "Recorded for Outbound processing"
Dear Experts,
I have File >XI(3.0)>IDoc scenario with 10-25 interfaces. Per interface an average of 200 msges.
Now we have an issue. from past 6 days all the messages for one of the interfaces are in status: "Recorded for Outbound processing"(with that single small black right arrow) in SXMB_MONI(around 1760 till now). Other than this few 100 messages for couple other interfaces are also in same status. There are other message interfaces using the same Idoc type; but they dont have this problem.
I have checked the queues: SMQ1/Q2. There are no errors. The other threads mention about some reports; but all are for error messages. So that also did not help!
On the first day someone had deleted the error queue entry. They had first checked the message in the queues but that was not showing any status. (This is very strange... but for some messages , the left most status column is not showing any status at all.. but while clicking on the end time column; I am getting the pop up which says succesfully processed). But this is not our problem right now.
Please help me process the messages in the "Recorded for Outbound processing" status.. some how!!!
Thanks in advance for your inputs....
P.N: Runtime workbench here is not configured properly. No CC monitoring tab; message monitoring shows only adapter messages etc.... So cannot check anything here
Thank you for your inputs.
@Udo.... SMQR- no issues.
The RFC destination is fine.
@Abhishek The Idoc has not reached SAP. The xml messages in XI are in "Recorded for outbound processing" which is kinda like Scheduled, i think. Anyway I checked the R/3 cant find the messages or errors.
Any help would be highly appreciated....
Similar Messages
-
Problem Recorded for Outbound Processing...
Hello,
My Scenario is idoc - xi - soap . But when i test my scenario. It didnt work properly. When i checked xi monitoring, I saw my process stayed in "Recorded for Outbound Processing". I think it didnt call adapter.
Is anyone have idea whats wrong?
Thanks.
Rasimhi,
run the report
RSXMB_REGISTER_QUEUES
RSXMB_RESTART_MESSAGES
Refer this blog
XI : How to Re-Process failed XI Messages Automatically
And if problem is still there:
Try to de register and register your queue try to delete the entry in the queue by double clicking on the Queue ID in SXMB_MONI and restarting your message.
regards,
ujjwal kumar -
Recorded for outbound processing in SXMB_MONI???
Hi XI friends,
in my file to abap proxy,
in sxmb_moni i am getting message like "recorded for outbound processing" and Q status is stopped.
please help me.
thanks and regards
ramHi friends..
Trace is like this
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?><!-- Call Adapter --> <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30"><Trace level="1" type="T">Party normalization: sender </Trace>
<Trace level="1" type="T">Sender scheme external = XIParty</Trace>
<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
<Trace level="1" type="T">Sender party external = </Trace>
<Trace level="1" type="T">Sender party normalized = </Trace>
<Trace level="1" type="T">Party normalization: receiver </Trace>
<Trace level="1" type="T">Receiver scheme external = </Trace>
<Trace level="1" type="T">Receiver agency external = </Trace>
<Trace level="1" type="T">Receiver party external = </Trace>
<Trace level="1" type="T">Receiver party normalized = </Trace>
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST"></Trace><!-- ************************************ -->
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
<Trace level="2" type="T">Request Line = POST /sap/xi/engine?type=entry HTTP/1.1</Trace>
<Trace level="2" type="T">Host = dcexi0605.aaaa.com:8030</Trace>
<Trace level="2" type="T">Server protocol = HTTP/1.1</Trace>
<Trace level="2" type="T">Remote address = 10.161.20.123</Trace>
<Trace level="1" type="T">COMMIT is done by XMB ! </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS"></Trace><!-- ************************************ -->
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE"></Trace><!-- ************************************ -->
<Trace level="3" type="T">XMB was called with external pipeline PID = ENTRY</Trace>
<Trace level="3" type="T">Getting type of XMB... </Trace>
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE">
</Trace>
<Trace level="2" type="T">XMB kind = CENTRAL</Trace>
<Trace level="3" type="T">Start pipeline found </Trace>
<Trace level="2" type="T">Switch to external start pipeline PID = CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
<Trace level="3" type="T">No triggers found. OK. </Trace>
</Trace>
<Trace level="1" type="T">**************************************************** </Trace>
<Trace level="1" type="T">* * </Trace>
<Trace level="1" type="T">* * </Trace>
<Trace level="1" type="T">XMB entry processing </Trace>
<Trace level="3" type="T">system-ID = BGX</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAFUSERBGX</Trace>
<Trace level="1" type="Timestamp">2007-02-28T10:29:00Z CET </Trace>
<Trace level="1" type="T">* * </Trace>
<Trace level="1" type="T">* * </Trace>
<Trace level="1" type="T">**************************************************** </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE"></Trace><!-- ************************************ -->
<Trace level="1" type="T">Message-GUID = D5951F70C64311DBB7213A3BFF6537A2</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC"></Trace><!-- ************************************ -->
<Trace level="3" type="T">QOS = EO</Trace>
<Trace level="3" type="T">Message-GUID = D5951F70C64311DBB7213A3BFF6537A2</Trace>
<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="3" type="T">Generate prefixed queue name </Trace>
<Trace level="1" type="T">Queue name : XBTI0006</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0006</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment </Trace>
<Trace level="3" type="T">Setup qRFC Scheduler </Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK! </Trace>
<Trace level="3" type="T">Call qRFC .... MsgGuid = D5951F70C64311DBB7213A3BFF6537A2</Trace>
<Trace level="3" type="T">Call qRFC .... Version = 000</Trace>
<Trace level="3" type="T">Call qRFC .... Pipeline = CENTRAL</Trace>
<Trace level="3" type="T">OK. </Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message </Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking </Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST </Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC </Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye ! </Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="3" type="T">Version number = 000</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"></Trace><!-- ************************************ -->
<Trace level="3" type="T">Persisting message Status = 001</Trace>
<Trace level="3" type="T">Message version 000</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
<Trace level="3" type="T">Trace object available again now. OK. </Trace>
<Trace level="3" type="T">Message was read from persist layer. OK. </Trace>
<Trace level="3" type="T">Message properties in XMB object were setup. OK. </Trace>
<Trace level="3" type="ToDo">Make sure we catch exceptions in persist read </Trace>
<Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
</Trace>
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC"></Trace><!-- ************************************ -->
<Trace level="3" type="T">message version successfully read from persist version= 000</Trace>
<Trace level="2" type="T">Increment log sequence to 001</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="3" type="T">system-ID = BGX</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAFUSERBGX</Trace>
<Trace level="1" type="Timestamp">2007-02-28T10:29:00Z CET </Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC"></Trace><!-- ************************************ -->
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">Pipeline attributes </Trace>
<Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
<Trace level="3" type="T">ENABLE = 1</Trace>
<Trace level="3" type="T">TRACELEVEL = 0</Trace>
<Trace level="3" type="T">EXEMODE = A</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">Pipeline elements </Trace>
<Trace level="3" type="T">ELEMPOS = 0001</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS = 0002</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS = 0003</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS = 0004</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS = 0007</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS = 0008</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">FL_DUMMY = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS = 0009</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="1" type="Timestamp">2007-02-28T10:29:00Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
<Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
<Trace level="1" type="Timestamp">2007-02-28T10:29:00Z CET Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification... </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV) </Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_RD_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG = </Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
<Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N </Trace>
<Trace level="1" type="T"> Cache Content is up to date </Trace>
<Trace level="2" type="T">Start without given receiver </Trace>
<Trace level="2" type="T">Classic Receiver Determination via Rules. </Trace>
<Trace level="2" type="T">Check conditions for rule line no. 1 </Trace>
<Trace level="2" type="T">...valid Receiver w/o Condition: - SAP_ERP_aaaa_PPR </Trace>
<Trace level="2" type="T">No Receiver found behaviour: 0 </Trace>
<Trace level="2" type="T">Number of Receivers:1 </Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2007-02-28T10:29:00Z CET End of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call </Trace>
<Trace level="3" type="T">Message-Version = 001</Trace>
<Trace level="3" type="T">Message version 001</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
<Trace level="1" type="Timestamp">2007-02-28T10:29:00Z CET Start of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification... </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV) </Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_ID_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG = </Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
<Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N </Trace>
<Trace level="1" type="T"> Cache Content is up to date </Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) SAP_ERP_aaaa_PPR MI_IN_S_StockAdj </Trace>
<Trace level="2" type="T">...valid InbIf without Condition: MI_IN_S_StockAdj </Trace>
<Trace level="2" type="T">Number of receiving Interfaces:1 </Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2007-02-28T10:29:00Z CET End of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call </Trace>
<Trace level="3" type="T">Message-Version = 002</Trace>
<Trace level="3" type="T">Message version 002</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT"></Trace><!-- ************************************ -->
<Trace level="1" type="Timestamp">2007-02-28T10:29:00Z CET Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification... </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV) </Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_RECEIVER_SPLIT</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG = </Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
<Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV"></Trace><!-- ************************************ -->
<Trace level="3" type="T">Case handling for different plsrv_ids PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="2" type="T">got property produced by receiver determination </Trace>
<Trace level="1" type="T">number of receivers: 1 </Trace>
<Trace level="1" type="T">Single-receiver split case </Trace>
<Trace level="1" type="T">Post-split internal queue name = XBTOG___0002</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Persisting single message for post-split handling </Trace>
<Trace level="1" type="T"> </Trace>
<Trace level="1" type="T">Going to persist message + call qRFC now... </Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking </Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST </Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye ! </Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"></Trace><!-- ************************************ -->
<Trace level="3" type="T">Persisting message Status = 012</Trace>
<Trace level="3" type="T">Message version 003</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE"></Trace><!-- ************************************ -->
<Trace level="3" type="T">Trace object available again now. OK. </Trace>
<Trace level="3" type="T">manual Restart Flag X</Trace>
<Trace level="3" type="T">Message Guid D5951F70C64311DBB7213A3BFF6537A2</Trace>
<Trace level="3" type="T">Version 000</Trace>
<Trace level="3" type="T">Pipeline ID CENTRAL</Trace>
<Trace level="3" type="T">EOIO Force I</Trace>
<Trace level="3" type="T">Restart Trace </Trace>
<Trace level="3" type="T">Message was read from persist layer. OK. </Trace>
<Trace level="3" type="T">Message properties in XMB object were setup. OK. </Trace>
<Trace level="3" type="T">Error of the prevous version: </Trace>
<Trace level="3" type="T">Area </Trace>
<Trace level="3" type="T">Error ID </Trace>
<Trace level="3" type="T">Restart of Queue? </Trace>
<Trace level="1" type="T">Persisting message with status ManualRestart, version: 003</Trace>
<Trace level="1" type="T">*************************************** </Trace>
<Trace level="1" type="T">* Setup of qRFC Scheduler OK!!! </Trace>
<Trace level="1" type="T">*************************************** </Trace>
<Trace level="3" type="T">Call qRFC .... MsgGuid = D5951F70C64311DBB7213A3BFF6537A2</Trace>
<Trace level="3" type="T">Call qRFC .... Pipeline = CENTRAL</Trace>
<Trace level="3" type="T">OK. </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"></Trace><!-- ************************************ -->
<Trace level="3" type="T">Persisting message Status = 016</Trace>
<Trace level="3" type="T">Message version 005</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE"></Trace><!-- ************************************ -->
<Trace level="3" type="T">Trace object available again now. OK. </Trace>
<Trace level="3" type="T">manual Restart Flag X</Trace>
<Trace level="3" type="T">Message Guid D5951F70C64311DBB7213A3BFF6537A2</Trace>
<Trace level="3" type="T">Version 005</Trace>
<Trace level="3" type="T">Pipeline ID CENTRAL</Trace>
<Trace level="3" type="T">EOIO Force I</Trace>
<Trace level="3" type="T">Restart Trace </Trace>
<Trace level="3" type="T">Message was read from persist layer. OK. </Trace>
<Trace level="3" type="T">Message properties in XMB object were setup. OK. </Trace>
<Trace level="3" type="T">Error of the prevous version: </Trace>
<Trace level="3" type="T">Area </Trace>
<Trace level="3" type="T">Error ID </Trace>
<Trace level="3" type="T">Restart of Queue? </Trace>
<Trace level="1" type="T">Persisting message with status ManualRestart, version: 005</Trace>
<Trace level="1" type="T">*************************************** </Trace>
<Trace level="1" type="T">* Setup of qRFC Scheduler OK!!! </Trace>
<Trace level="1" type="T">*************************************** </Trace>
<Trace level="3" type="T">Call qRFC .... MsgGuid = D5951F70C64311DBB7213A3BFF6537A2</Trace>
<Trace level="3" type="T">Call qRFC .... Pipeline = CENTRAL</Trace>
<Trace level="3" type="T">OK. </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"></Trace><!-- ************************************ -->
<Trace level="3" type="T">Persisting message Status = 016</Trace>
<Trace level="3" type="T">Message version 006</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
<Trace level="3" type="T">Trace object available again now. OK. </Trace>
<Trace level="3" type="T">Message was read from persist layer. OK. </Trace>
<Trace level="3" type="T">Message properties in XMB object were setup. OK. </Trace>
<Trace level="3" type="ToDo">Make sure we catch exceptions in persist read </Trace>
<Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
</Trace>
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC"></Trace><!-- ************************************ -->
<Trace level="3" type="T">message version successfully read from persist version= 006</Trace>
<Trace level="2" type="T">Increment log sequence to 007</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="3" type="T">system-ID = BGX</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = saa_aaa</Trace>
<Trace level="1" type="Timestamp">2007-02-28T11:28:10Z CET </Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC"></Trace><!-- ************************************ -->
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">Pipeline attributes </Trace>
<Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
<Trace level="3" type="T">ENABLE = 1</Trace>
<Trace level="3" type="T">TRACELEVEL = 0</Trace>
<Trace level="3" type="T">EXEMODE = A</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">Pipeline elements </Trace>
<Trace level="3" type="T">ELEMPOS = 0001</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS = 0002</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS = 0003</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS = 0004</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS = 0007</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS = 0008</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">FL_DUMMY = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS = 0009</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="1" type="Timestamp">2007-02-28T11:28:10Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
<Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
<Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">
<Trace level="1" type="Timestamp">2007-02-28T11:28:10Z CET Start of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification... </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV) </Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_MAPPING_XMS_PLSRV3</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG = </Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
<Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
<Trace level="2" type="T">......attachment XI_Context not found </Trace>
<Trace level="3" type="T">Mapping is already determined in the interface determination </Trace>
<Trace level="3" type="T">Object ID of Interface Mapping 7344EE703ACE3FE5AB19EDA1D3F48BBC </Trace>
<Trace level="3" type="T">Version ID of Interface Mapping B2CF8EF067FF11DBA742D7830A967135 </Trace>
<Trace level="1" type="T">Interface Mapping http://aaaa.com/xi/PROCESS/PPE/ERP_MES IM_MES_StockAdj_TO_SAP </Trace>
<Trace level="3" type="T">Mapping Steps 1 JAVA com/sap/xi/tf/_MM_MES_StockAdj_To_SAP_ </Trace>
<Trace level="3" type="T">Dynamic configuration is empty </Trace>
<Trace level="2" type="T">Mode 0 </Trace>
<Trace level="3" type="T">Creating Java mapping com/sap/xi/tf/_MM_MES_StockAdj_To_SAP_. </Trace>
<Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._MM_MES_StockAdj_To_SAP_ </Trace>
<Trace level="2" type="T">Java mapping com/sap/xi/tf/_MM_MES_StockAdj_To_SAP_ completed. (executeStep() of com.sap.xi.tf._MM_MES_StockAdj_To_SAP_ </Trace>
<Trace level="3" type="T">Dynamic configuration is empty </Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2007-02-28T11:28:10Z CET End of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call </Trace>
<Trace level="3" type="T">Message-Version = 007</Trace>
<Trace level="3" type="T">Message version 007</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
<Trace level="1" type="Timestamp">2007-02-28T11:28:10Z CET Start of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification... </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV) </Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_OUTBINDING</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG = </Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL"></Trace><!-- ************************************ -->
<Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV">
<Trace level="2" type="T">O U T B O U N D - B I N D I N G </Trace>
<Trace level="2" type="T"> Cache Content is up to date </Trace>
<Trace level="2" type="T">determine OUTBOUND BINDING for: </Trace>
<Trace level="2" type="T">-BS_FTP_MES_GeneralServices </Trace>
<Trace level="2" type="T">-SAP_ERP_aaaa_PPR </Trace>
<Trace level="2" type="T">http://aaaa.com/xi/PROCESS/PPE/ERP_MES.MI_IN_S_StockAdj </Trace>
<Trace level="2" type="T">Channel found: - SAP_ERP_aaaa_PPR - CC_IN_SAP_XI_StockAdj </Trace>
<Trace level="2" type="T">no header mapping defined </Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2007-02-28T11:28:10Z CET End of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call </Trace>
<Trace level="3" type="T">Message-Version = 008</Trace>
<Trace level="3" type="T">Message version 008</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_ADAPTER"></Trace><!-- ************************************ -->
<Trace level="1" type="Timestamp">2007-02-28T11:28:10Z CET Start of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV"></Trace><!-- ************************************ -->
<Trace level="3" type="T">Calling pipeline service: PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification... </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV) </Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">ADRESSMOD = SD</Trace>
<Trace level="3" type="T">P_CLASS = </Trace>
<Trace level="3" type="T">P_IFNAME = </Trace>
<Trace level="3" type="T">P_METHOD = </Trace>
<Trace level="3" type="T">FL_LOG = </Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">Channel for Integration Engine: XI</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV) </Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = IENGINE</Trace>
<Trace level="3" type="T">ADRESSMOD = SD</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_IE_ADAPTER</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG = </Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL"></Trace><!-- ************************************ -->
<Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
<Trace level="3" type="T">Channel for Integration Engine: XI</Trace>
<Trace level="1" type="T">Sender: Header mapped to</Trace>
<Trace level="1" type="T">Party = </Trace>
<Trace level="1" type="T">Agency = </Trace>
<Trace level="1" type="T">Scheme = </Trace>
<Trace level="1" type="T">Service = BS_FTP_MES_GeneralServices</Trace>
<Trace level="1" type="T">Receiver: Header mapped to</Trace>
<Trace level="1" type="T">Party = </Trace>
<Trace level="1" type="T">Agency = </Trace>
<Trace level="1" type="T">Scheme = </Trace>
<Trace level="1" type="T">Service = SAP_ERP_aaaa_PPR</Trace>
<Trace level="1" type="T">Party denormalization: sender </Trace>
<Trace level="1" type="T">Sender target scheme = </Trace>
<Trace level="1" type="T">Sender target agency = </Trace>
<Trace level="1" type="T">Sender party normalized = </Trace>
<Trace level="1" type="T">Sender party external = </Trace>
<Trace level="1" type="T">Party denormalization: receiver </Trace>
<Trace level="1" type="T">Receiver target scheme = </Trace>
<Trace level="1" type="T">Receiver target agency = </Trace>
<Trace level="1" type="T">Receiver party normalized = </Trace>
<Trace level="1" type="T">Receiver party external = </Trace>
<Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
<Trace level="2" type="T">Addressing mode: url</Trace>
<Trace level="3" type="T">Host = dceaaaa08.aaaa.biz</Trace>
<Trace level="3" type="T">Port = 8010</Trace>
<Trace level="3" type="T">Transport protocol = HTTP 1.0</Trace>
<Trace level="3" type="T">Message protocol = </Trace>
<Trace level="3" type="T">Path = /sap/xi/engine?type=receiver</Trace>
<Trace level="2" type="T">Auth mode: basicSAP</Trace>
<Trace level="3" type="T">Conversion of language from char2 to char1 EN</Trace>
<Trace level="3" type="T">User = SAPJSF</Trace>
<Trace level="3" type="T">Client = 400</Trace>
<Trace level="3" type="T">Language = E</Trace>
<Trace level="3" type="T">Creating HTTP-client </Trace>
<Trace level="3" type="T">HTTP-client: creation finished</Trace>
<Trace level="3" type="T">Security: Basic authentication SAP </Trace>
<Trace level="3" type="T">Serializing message object... </Trace>
<Trace level="3" type="T">HTTP-client: sending http-request...</Trace>
<Trace level="3" type="T">HTTP-client: request sent</Trace>
<Trace level="3" type="T">HTTP-client: Receiving http-response...</Trace>
<Trace level="3" type="System_Error">HTTP-Client: exception during receive: HTTP_COMMUNICATION_FAILURE</Trace>
</Trace>
<Trace level="2" type="T">Switch back to normalized party (HTTP response)</Trace>
<Trace level="1" type="T">Sender scheme external = </Trace>
<Trace level="1" type="T">Sender agency external = </Trace>
<Trace level="1" type="T">Sender party external = </Trace>
<Trace level="1" type="T">Sender party normalized = </Trace>
<Trace level="1" type="T">Party normalization: receiver </Trace>
<Trace level="1" type="T">Receiver scheme external = </Trace>
<Trace level="1" type="T">Receiver agency external = </Trace>
<Trace level="1" type="T">Receiver party external = </Trace>
<Trace level="1" type="T">Receiver party normalized = </Trace>
<Trace level="2" type="T">Undo header mapping (HTTP response) </Trace>
<Trace level="1" type="T">Sender: Header before undo of mapping</Trace>
<Trace level="1" type="T">Party = </Trace>
<Trace level="1" type="T">Agency = </Trace>
<Trace level="1" type="T">Scheme = </Trace>
<Trace level="1" type="T">Service = BS_FTP_MES_GeneralServices</Trace>
<Trace level="1" type="T">Receiver: Header before undo of mapping</Trace>
<Trace level="1" type="T">Party = </Trace>
<Trace level="1" type="T">Agency = </Trace>
<Trace level="1" type="T">Scheme = </Trace>
<Trace level="1" type="T">Service = SAP_ERP_aaaa_PPR</Trace>
<Trace level="2" type="T">Sender: Header after undo of mapping</Trace>
<Trace level="2" type="T">Party = </Trace>
<Trace level="2" type="T">Agency = </Trace>
<Trace level="2" type="T">Scheme = </Trace>
<Trace level="2" type="T">Service = BS_FTP_MES_GeneralServices</Trace>
<Trace level="2" type="T">Receiver: Header before undo of mapping</Trace>
<Trace level="2" type="T">Party = </Trace>
<Trace level="2" type="T">Agency = </Trace>
<Trace level="2" type="T">Scheme = </Trace>
<Trace level="2" type="T">Service = SAP_ERP_aaaa_PPR</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call </Trace>
<Trace level="3" type="T">Message-Version = 009</Trace>
<Trace level="3" type="T">Message version 009</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="3" type="System_Error">Error exception return from pipeline processing! </Trace>
<Trace level="1" type="T">Persist Message in Retry State </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"></Trace><!-- ************************************ -->
<Trace level="3" type="T">Persisting message Status = 009</Trace>
<Trace level="3" type="T">Message version 010</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</SAP:Trace>
please guide me..
ram -
Delete messages stuck in status 12, Recorded for Outbound Processing
I am on a PI 7.10 SP8 system. I have 59,000 XML messages showing in status 12 ( Recorded for Outbound Processing) that I would like to just delete or cancel. These have accumulated over several days of testing interfaces. If I have to allow them to be processed, that would also work but is not needed. I have read about 6 different forum threads and tried several things but nothing has worked yet. <br>
The messages can not be cancelled from SXMB_MONI. <br>
The queues are no longer showing in SMQ2. <br>
I have tried restarting and re-registering the queues. <br>
I've tried RSXMB_RESTART_MESSAGES and RSXMB_CANCEL_MESSAGES. <br>
SWPR & SWPC show nothing to restart. <br>
Any ideas on something else to try? <br>Hi,
You can try to delete or archive mesages. use following links.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/402fae48-0601-0010-3088-85c46a236f50
Delete Messages SXMB_MONI
http://help.sap.com/saphelp_nw04/helpdata/en/0e/80553b4d53273de10000000a114084/frameset.htm
Too many questions on Archive/Delete messages.
Inder -
Recorded for Outbound Processing
Hi All,
Very Good Morning.
My message having large kind of payload. When i test my scenario with small kind of that data, Message successfully stored to target system database using the stored procedure,
But in my real time scenario. it having large kind of the data(for ex:170Mb) of data,Messages are not processed target end. It staying queues and status in SXMB_Moni shows " Arrow mark having Recorded for Outbound Processing".
queue name is "XBTM0000" shows in SMQ2,
Can provide me your valuble suggestion how i able to solve my issue.
Thank you
SateeshHi Suraj,
In this scenario i am using BPM ,
My BPM Steps are Receive1-Transformation1-Send1Synchornously-Transformation2-Send2.BPM Graphflow shows completed upto send2 step,There is no error in BPM.
I tested same scenario using small kind of data(for my test system) more than 2000 records. it,s succesfly stored in the target end. But in real time data having more than 1 and half laks records.when i am using the real time scenario data i am getting this problem.
My BPM is successful proceed completly upto final step when i am using the real time data but my message is stucked queue.
For example my message flow is
1)Sender service to BPM(Receive step)(Request Message)
after transformation step
2)BPM to Receiver service(Send Synchronously)
3) Receive service to BPM
after transformation step
4) BPM to Sender service(send step)
Upto 4 th step my message are display in SXMB_Moni, My 4 th shows the arrow mark having recorded with outbound processing.
Thanks,
Sateesh -
Status in SXMB_MONI ( Recorded for outbound Processing )
Hi All,
I getting a status "Recorded for Outbound Processing" for all interfaces in SXMB_MONI. Earlier all the Interfaces were working fine.
Kindly let me know your valuable inputs...
Thanks & Regards,
AnkurHi Ankur,
Pls do check the following.
1. Pls check whether on the outbound side the user id and password you are using are correct and is not changed.
2. The messages are getting assigned into the queues and the queue processing is happening properly.
3. If the volume of data is more, say for eg more no of idocs, etc. then it will take some time for the processing.
4. First of all go to the message monitoring tool and cancel all the messages of the same interface which is 'on hold' status and cancel them all from the beginning.
Cheers
JK -
Restarting "Recorded for outbound processing"
Hi,
Is there anyway to restart automatically, "recorded for outbound processing" messages, on PI system?
Thank you,
Best regards,Register your queues again and see if it gets processed.
Last option could be to try to delete the message from queue and then restart it in moni.
Regards,
Prateek -
Restart message scheduled for outbound processing
Hi,
I'm having a BPM process that collects IDocs. A lot of messages got stuck now in the status message scheduled for outbound processing. Can I manually restart these messages? What will it happen if I restart them? Will they be sent twice or just once?
Thanks in advance,
George> I'm having a BPM process that collects IDocs. A lot of messages got stuck now in the status message scheduled for outbound processing. Can I manually restart these messages?
I think you are looking in MONI for status "Recorded for Outbound Processing" .. correct?
Just scroll towards right and then you will find the Queue ID against your message, just click on this id and see if it has got stuck in queue if yes then just process it from there.
>What will it happen if I restart them? Will they be sent twice or just once?
If you process the message it will be posted only once.
Regards,
Sarvesh -
Scheduled for Outbound processing - SMQ2 has 0 entries!
Hi !
After a XI server reboot because of a JCO communication failure, there were a lot of messages stuck in queues. We executed manually the LUWs and everything went ok, but we still have some messages with "Scheduled for Outbound processing" status in SXMB_MONI (right black arrow icon) and its queues are all empty via SMQ2.
Those messages were sent EOIO.
What should we do? restart manually each message in order?
Thanks!
Regards,
Matias.Hi Sreenivas!
There is no audit log, because the message with Waiting status is in Integration Engine, not in Adapter Engine. The audit log for the process of getting the message to enter XI went OK, all steps are in Success in audit log...but there is no audit log for "leaving" XI.
If I restart each message manually, they go ok...is there any way to ensure the EOIO order and make XI to resend them in order?
Regards,
Matias. -
How to stop message "planned for outbound processing"?
We have two messages with status "planned for outbound processing". Because we want to quit them i want to know how to do this?!
Can somebody help?! these messages seems to be stuck because of java-mapping!?
brHi,
Check the Queue name in Sxmb_moni and as expert Aamir mentioned go to Tcode - SMQ2 look for the Queue name and delete the message.
Cheers
Agasthuri Doss -
"Scheduled for Outbound processing" message
Hi,
My scenario is: R/3 (IDoc Customer) -> XI -> PC (file) and I use a BPM with option "multi to single".
In the Message Monitoring, I have two steps:
1. Idoc DEBMAS06 --> BPM:
status = "Processed successfully". Thus it's ok.
2. BPM --> my PC:
status = "Scheduled for Outbound processing" and in column "outbound" I have not "IENGINE". There is no other error message and obviously no data are sent to my PC.
Have you already seen this message?
And have you a solution?
Note: Last friday, the same scenario was ok. I have just changed some data inside the mapping (occurence was not change).
Mickael.Hi,
Try resetting the status to "Ready".
If you get SYSFAIL again, try deleting that particular LUW. If there are other messages waiting in the queue, just click on the unlock queue button and the remaining messages will flow thru.
Regards,
Sridhar -
Message stuck in SXMB_MONI status " Sceduled for Outbound Process." Urgent
Hello All,
All messages in our XI environment are getting stuck with status Scheduled for Outbound Processing ...I have already done the following..
1) Registered the Queues
2) Deleted entries in SMQ1 and SMQ2 and restarted messages
Last time we had this issue, we were finally able to reslove it by doing a J2EE restart. But this has resurfaced again within a week, and this time even the restart is not working.
Do you think some parameter has been set incorrectly during the install ..
Any help would be appreciated ..
thanks
MayankHey Mayank,
Did you got JCO failure error for any of XI message before start of getting this error message?
If so it's failing because of RFC connection problem...
You need to go to Tcode : SM59 in your xi server
check the TCP/IP Connections which is created while post-installation phase..
1. AI_RUNTIME_JCOSERVER.
2. AI_DIRECTORY_JCOSERVER
Solution : Increase the default value for CPIC_MAX_CONV (se note 314530).
Hope this wull solve your problem.
Nilesh -
Messages with Status "Scheduled" or "Sceduled for Outbound Processing"
Hi All,
When i run my interface, sxmb_moni shows the status of messages as "Scheduled" or "Sceduled for Outbound Processing".
I know the reason and the problem gets resolved when I unlock the queues.
But, is there a solution that I can resolve this completely? Reason being, everytime the interface is triggered, I have to unlock the queues. And if it is ccBPM scenario, I have to unlock multiple times, to acheive the flow completion
Thanks,
SwapnaHi,
Check if u have set the value for monitor parameter QRFC_RESTART_ALLOWED to 1. default is 0.Also if your queues are registered in SMQR.Also checvk these reports
· RSARFCSE: Restart an LUW (background job)
· RSARFCEX: Restart tRFC LUWs (background job)
· RSQOWKEX: Restart QOUT qRFC LUWs
· RSQIWKEX: Restart QIN qRFC LUWs
Thanks!
Edited by: sudhir tiwari on Oct 10, 2008 12:19 PM -
Message scheduled for outbound processing
Hi All,
We have an issue where a message is stuck in MONI in scheduled status. We checked to see if there is any stuck queues, we did not find any errors nor entries. The message has the staus "Scheduled for Outbound processing", also we can see the JOB ID (JOBnumber) with status "job not yet executed". The remaining interfaces in this landscape are working fine.
Appreciate your help!!!
Thanks,
GunasreeHi
We can prevent this problem through standard SAP program RSQIWKEX. This program need to execute background. Whenever any message stuck in queue automatically this problem will restart error message automatically. If you want to delete error message from queue (due to this error message remaining messages are in hold stage. for remaining message execution we need to delete error message from queue) we need to change one function in this probem.
Existing function TRFC_QIN_RESET_LUW , this function only can restart error message.
Need to add function TRFC_QIN_DELETE_LUW , this function delete error message from queue.
For this program execution we need to mentioned queue name(mandatory), find message stucking queue name and give same name to program in variant.
/people/gourav.khare2/blog/2007/12/21/mass-cancellation-of-error-messages--xi
Re: Unable to delete the messages scheduled for outbound processing
Regards
Pothana -
How to maintain a condition record for a output type ?
Hi All
How to maintain a condition record for a output type ?Hi,
Goto NACE and there is a button for maintiaining the Condition Reocrds.
Maybe you are looking for
-
Just got the apple TV for fathers day! I hook it up today and tried to watch a movie from my iTunes and got a error HDCP! What is this and how can I fix it? What do I need? Please help!!
-
FYI: New version of Disk Warrior seems to hang when run with Snow Leopard
FYI: It seems that the new version of Disk Warrior hangs when run in Snow Leopard
-
Set PR field in PO entry screen as requird field
Hi, I trying to set the PR field in PO entry screen as requird feild, but it's not working. I try to set to display only, it's working. Anyone can help me on this? Thanks! Regards, Anson
-
HOW TO FIX IT, GARAGE BAND FOUND AUDIO FILES IN 8 BIT FORMAT. THIS FORMAT IS UNSUPPORTED AND CANNOT BE PLAYED
-
Question(s)... Will the MA589LL 20" intel imac (late 06-white- 2.16 cpu & X1600 radeon) support and drive an Apple M9177LL/A-A1081 20" Cinema Display? What about the earlier 'white' 20" Display, M88932M-A? My primary interest is as a second monitor f