Scheduled for Outbound Processing
Hi,
I have a simple problem: I want to send a XML file from a place to another place. When I put the file in the sender folder, XI import this file correctly, therefore, the file doesn't go to the receiver folder.
In the XML monitor, the current status (message lifecycle) is "Scheduled for Outbound Processing".
What can be happening?
Tks,
Douglas
Hello Douglas,
I think that message is sitting in the queue. May be you should check whether queue registrations are done already. Otherwise the message might sit in the outbound queue. You can goto the queue entry (from monitoring) and unlock it if this is the case.
Regards
Rampi.
Similar Messages
-
"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 -
Scheduled for Outbound Processing in SXMB_MONI
I have a scenario RFC -> ccBpm1 -> ccBpm2 -> ccBpm3 -> RFC.
The scenario was working perfectly. I made some simple changes in ccBpm3 and some errors started to happen.
The Xml message from ccBpm1 to ccBpm2 started to stuck (message Scheduled for Outbound Processing in SXMB_MONI). I didn´t make ANY change in ccBpm1 or ccBpm2, before the error started.
When I made a "dummy" change in ccBpm2 and I reactivate it, the message from ccBpm1 to ccBpm2 process, but then the message from ccBpm2 to ccBpm3 stucks. If I do a dummy change in ccBpm3, the message from ccBpm1 to ccBpm2 stucks again.
I have no Queues locks in smq1 and smq2. The Cache status are all 0 in SXI_CACHE. I have tried to reimport all Integration Process in Integration Directory, but no sucess.
Seems to be any kind of bug.
Any idea?
ThanksFirst, I would like to know.. if there was a justification to divide the scenario into 3 BPMs. Because BPMs add to system performance. They get converted to workflows on abap engine and context switches from java to abap engine. You might want to check you configuration in ID test configuration and then close analysis of the message processing in each of the ccBPMs.
VJ -
Scheduled for Outbound processing - Sysfail
I´m trying to build a (Mail-> XI -> File) Scenario and I´m having some problems.
The attachment of the mail must be passed to xi bpm and for that I used the module PayloadswapBean
(according to /people/michal.krawczyk2/blog/2005/12/18/xi-sender-mail-adapterpayloadswapbeanstep-by-step)
On SXMB_MONI I checked that the Mail -> XI message have worked fine. But inside the BPM, the senders steps doesn´t work, all keep "Scheduled for Outbound processing" status
I´ve tried a sent step to Sap r/3, to File, and all have the same error. In runtime workbench, I checked that the messages aren´t arriving to adapter.
In SMQ2 I checked that when this error happens, a queue is created with status Sysfail. On details of message it says "Access with 'ZERO' object reference not possible."
Can anyone help me please ?
Thanks
Vitor ZaninottoIs the sender getting invoked in the BPM? If yes then check in the adapter engine for any errors for that particular message. My guess is there would be some messages of the same instance which are stuck in the adapter engine. Once you clear the error/messages, try restarting the queue. This might solve the problem.
Cheers,
Sarath
Award points if helpful. -
Green flag: scheduled for outbound processing
We had some network connection problem.Outcome was that in SXI_MONI ,there were some
red color flags,single rectangles,green flags.
Firstly i restarted red color flag,secondly i restarted single rectangles.In this way,first two issues got resolved.
Third problem was "scheduled for outbound processing" ie green flags.
Fo this , i decided to fiest relate how many actual idocs are posted to destination.While i was going with htis activity.
automatically after two hours green flags got processed.
So what does this means ,that green color flag is scheduled to run later and an XI consultant needn;t work on this part ?Dear sirs,
I feel registrations should be one time activity, ideally speaking.The queue cannot come into picture if it was not registered.
Now i a queue is stuck due to network disconnect( i am referring to only and only network disconnect) here.I do not mean any message mapping failure and i do not mean any udf error or something.
So if a queue is stuck due to a netwrk disconnect,plz guide me witha solution.What i came acroos i just mentioned.
As what u r saying that we need to register/deregister queus.Kindly justify this article then as given in subject.
You may correct spelling of technical.I did so to avoid this site filter.
http://www.saptecnical.com/Tutorials/XI/XMLMessageQueues/Monitor.htm
Edited by: aditya sharma on Jul 26, 2010 3:01 PM -
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. -
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 -
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 -
SXI_MONITOR: Scheduled for Outbound Processing
Hi folks,
After a connection problem with AE, now already fixed. Iu2019m experiencing a strange issue!! It occurs at only one interface where the message gets stuck at SXI_MONITOR with the status u201Cscheduled for outbound processingu201D without any entry at SMQ1/2 or SM58 u2013 this interface is an ABAP proxy to IDoc. Only at RWB I can see those entries with status u201Cwaitingu201D at Integration Engine. However, every time I try to resend or cancel I get the following error: u201CUnable to cancel/resend 1 of 1 messages; update the statusu201D.
After I read several threads with similar issue I expend all the tips suggested, unfortunately without success.
What I did:
SLD, Adapter Meta data, CPAcache, sxi_cache cleared,
AE entry at sxi_cache deleted,
RWB - Cache test ok,
Deregister/Register and activate all queues,
IDoc adapter deleted,
All ID objects related to this interface were deleted and created again,
Several j2ee restarts,
stop/start sap,
IDX2 u2013 IDoc meta data deleted,
Changed manually the message status directly at table SXMSPMAST to a restartable status.
All PI components are in green status.
Curiously at sxi_monitor I changed the layout in order to check which queue id my message is getting stuck and I found u201CPACKAGEu201D as queue name. I donu2019t know which kind of queue is this u201CPACKAGEu201D!
Anyone knows what is going on here?
Thanks in advance,
Ricardo.
Edited by: Ricardo Quintino on Jul 15, 2008 9:57 PMHi,
Scheduled status may come for different reasons,
1) Receivers are not ready
2) Queues are stuck up
3) Connection Problem
4) Waiting for the confirmation etc..
But it is prefer to check the status in the transaction SMQ2 in the XI box. I know you already did it. There are some better ways like to try re registering the queue.
Also this blog may help u-
XI : How to Re-Process failed XI Messages Automatically
if nothing is helping, then restart the server may help. lets c.
Regards
Aashish Sinha
PS : reward points if helpful -
Message in status "scheduled for outbound processing"
Hi,
I was tring to perfom volume test. The scenario is XMLFILE --> XI --> IDOC(R/3). I reduced the polloing interval to 2secs and it went well for 15 min. Later I left it like that for an hour and found that all the messages are queued up scheduled for processing. I checked SMQ2 there were lot of messages. I deleted them all and then activated the queuse through SXMB_ADM ->Manage Queues transaction. In the QRFC Monitor I see the scheduler status as Inactive. I tried to make it active, it starts and becomes inactive again. Still I can see all the messages in SXMB_MONI. Are there any specific steps that we need to perform to clear the queues.
Thanks.
Srinivas VaidyamHi,
it's normal for transaction SMQR to show the scheduler in status "Inactive" (it just happens not to be running at the
time you enter SMQR, a moment later you might have found it to be running).
Rather than just deleting all the queues you should have clicked on the queue name for a waiting message from SXMB_MONI (in the default SXMB_MONI display mode you need to scroll a bit to the right to the see which queue a message is in). Drill down on the next screen (double click the queue name etc.) to see a list of all queued messages including a brief description of why the first message got stuck. You can now either "retry" or "delete" the message. Then go back one screen and unlock the queue (open lock icon) if you find it not to be in the status running. Refresh the display to make sure that messages get processed.
Of course these steps do not need to be performed manually. There's an automatic retry mechanism and if that repeatedly fails the report RSXMB_RESTART_MESSAGES (which you will need to schedule) will try to resend the messages.
You should now cancel all messages belonging to this testrun in SXMB_MONI. Make sure that none of the queues are blocked and restart your test.
Regards,
Hans Christian -
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 -
Schedule lines for outbound process
hi
can anyone tell me what is schedule lines for outbound process
thanksthanks charlie for your answer can you pl tell me what does it means configured delivery types, item categories and schedule line for outbound processes.
thanks -
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 -
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 hereThank 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.... -
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
Maybe you are looking for
-
I have exclamation marks on my iTunes songs on my computer. How do I get rid of them?
I have iTunes match and it works fine on the iPad however on my computer where they originated from there is an exclamation mark with a circle around it on my songs and it will only play one song and then stops. I can manually double click on each so
-
Handling password while initial load process
Dear Experts, This is about password handling in IDM. While doing initial load, I do not want to bring passwords from my target systems (AD/SAP) into IDM. So which password(s) the users will use to login into target systems (AD/SAP) after initial loa
-
Hi, I am trying to upload Regional structure using LSMW. I have recorded transaction SR10 (Create City) but I am not sure how to proceed further. What changes I need to do in the recording and what should be the target structure for that. If anybody
-
Console login trouble with Crystal Reports Server XI
I installed Crystal Reports Server XI on a new box (replacing old), then applied SP1, and then SP2 bringing it up to the same level as the old box - Version Name: BOXIWIN_SP2 Build Number: 11.0.101.8004. However, when I restarted the server and logge
-
So they removed Pattern maker, and the Extract filters from Photoshop CS4
Personally I hardly ever used these, but did occasionally. I was wondering how this is going to affect others? I don't see how removing two items from the filters menu makes much difference to anything. Maybe its more of a launch time issue, although