Error SXMB_MONI
Hello,
i've a RFC - JDBC interface .
The database is Microsoft access, when i trigger the interface the follow error occurs in SXMB_MONI, response msg:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Inbound Message
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
can somebody help me please?,
thanks very much
Hi,
Try looking for the exact error in Adapter monitoring at http://<servername>:<port>/mdt/amtServlet. For that you can use the following procedure:
Double clicking the JDBC adapter in the adapter list --> Look for your communication channel.
There in history you will get exact error.
Also check your communication channel configuration and see if your JDBC adapter is properly configured.
Please find below the configuration which you can use
JDBC Driver: jdbc.odbc.JdbcOdbcDriver
Connection: jdbc:odbc:Driver={Microsoft Access Driver (*.mdb)};DBQ=H:/xitemp/DB/myDB.mdb
If you are using the Access DB file on your local server then make sure it it is shared properly and accessible from your XI system. I hope that should solve your problem.
Regards,
Jitender Chauhan
Similar Messages
-
BPM Error Permanent Error in BPE inbound processing
Hi
I require some urgent help on this BPM issue.
We are trying to integrate SRM PO being directly sent to Vendors using HTTP. We are getting an error saying Permanent Error in BPE inbound processing. The scenario works like this.
SRM system would sent PO using the SRM Standard interface PurchaseOrderRequest_Out. We need to transform the message into cXML format and send it to the vendors using HTTP adapter. Using the HTTP response we need to trigger an email to the business process team.
The SRM interface is under the software component SAP SRM Server 5.5 and our mapping is being done in a common software component and for the vendor interface we have another software component. We have created a relationship in the SLD by making the common SWC as dependent software component to SAP SRM Server and Vendor Software Component. So in the integration repository we are able to get the interfaces for the SAP SRM Server and Vendor Software Component under the common software component. The receive step for this BPM is a copy of the standard SRM interface PurchaseOrderRequest_Out(as the standard interface is an asynchronous interface) and we would require an abstract interface for the BPM. We have checked the semantics for the BPM and its fine. The related ID development is in place. When the message is being triggered, it gives us this above mentioned error. When we go to the QRFC monitor we are able to check the details.
Regards,
IndranilHi Indranil,
You don't see you BPM....
First go to SXI_CACHE and check that your BPM is listed there and that the compilation has been completed succesfully.
Is this the first time the BPM is being used? If so check if has been configured. For example, go to RWB->Component Monitoring->BPE in <SYSID>
and check if any error is listed there.
In order to check what is going on in your BPM you can trace it:
SXMB_MONI_BPE->Diagnosis Processes with Errors
SXMB_MONI->Process, get your msg and click on 'PE'. You should see the workitems and see if there is any error.
Hope this helps you....
Regards,
Encinas. -
BPM: skip a permanent error in a sequential ForEach ? Possible ?
In a BPM, i split a message with 100 records in 100 individual records (1..n mapping).
Then i use a ForEach Block (sequential) to send those 100 records using a synchronous Send step.
The Send step is a call on a partner Web Service.
Sometimes i receive a SOAP Fault.
This SOAP fault can be:
a) a temporary problem on the remote system... for example a database is down
b) a permanent problem... for example something's wrong in a XML structure
But i don't know in advance what kind of unexpected problem this is.
So i have to stop the process and someone must determine if it's a case a) or b), using the BP Monitor.
In case of a), i just have to wait the problem is solved and restart the BP exactly where it was stopped
In case of b), there's no chance to solve the problem. The BP must skip this Send step N and continue with the Send step N+1 in the ForEach loop.
I'm not allowed to resend the whole 100 records in case of a problem with the record 50 for example....
If a set "Start new transaction" everywhere, the BP will be able to restart exactly where it was stopped.
Now my questions:
Is is possible to manually force the BP to:
- restart exactly where it was stopped ?
- skip the error and continue to the next step ?
- restart from the beginning ?
How ?
Thank you
Edited by: Thierry Genoud on Feb 5, 2009 2:14 PMHi Indranil,
You don't see you BPM....
First go to SXI_CACHE and check that your BPM is listed there and that the compilation has been completed succesfully.
Is this the first time the BPM is being used? If so check if has been configured. For example, go to RWB->Component Monitoring->BPE in <SYSID>
and check if any error is listed there.
In order to check what is going on in your BPM you can trace it:
SXMB_MONI_BPE->Diagnosis Processes with Errors
SXMB_MONI->Process, get your msg and click on 'PE'. You should see the workitems and see if there is any error.
Hope this helps you....
Regards,
Encinas. -
Tons of email alerts but no errors
Hello PI gurus
I am having a strange problem.
We have several Synchronous interfaces and they have been working very well for many many weeks.
However, today I am getting thousands of alerts by email (it has crossed 10K so far).
In the email, all it says is 'Message.General' and it gives the message ID, interface and namespace info etc.,
However, using SXMB_MONI, when I check for the message ID (each and everyone) says the message was processed successfully.
When I try to list for messages with ERRORS, SXMB_MONI says no errors.
Does any one know why I am getting this kind of alerts?
I know synchronous messages are getting tried multiple times before getting processed successfully but what I don't understand is the 10K PLUS alerts
Thanks
Ram10K emails!!
RWB --> Alert config --> check the option Suppress Multiple Alerts of this Rule for the alert rule which is used by this SYNC interface.
your SYNC interfaces are re-tried multiple times by the CC??
additionally check tcode SLG1 to find what is creating those many alerts.
Edited by: abhishek salvi on Nov 16, 2011 10:50 AM -
ALERT not getting triggered for messages in error in adapter engine
Hi All,
I am doing the same scenario where I have created two Alert category Alert_cat1 and Alert_cat2, both are similar but one i have created for error in integration engine(Alert_cat1 ) and other for adapter engine(Alert_cat2).
Now for Alert_cat1 i have created a rule and in the setting "where did the error occur" I have given no restriction.
Now for Alert_cat2,as discussed in the above blog I have created many rule each for various adapter.
I have tested it, above mentioned configuration is working for message mapping error (sxmb_moni)
but not for any error in adapter engine for messages in waiting or system erroe status.
Kindly suggest where I am going wrong.
Regards
Shefali SHI,
please refer this below blog:
Does Alerts work for Integrated configurations scenario??
thanks, -
SAP GRC ERROR - NO_RECEIVER_CASE_BE
Hi All, I'm try implemented GRC and get this error (SXMB_MONI):
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_BE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
My receiver determination with the following values:
Service - GRC_NFE_CORE_70 (name of my BSystem)
Interface - SRVSC_nfeStatusServicoNF_SYNC_OB
Namespace - http://sap.com/xi/NFE/005a
Configured receivers
Service - SEFAZ_GO_HOMOLOG (name of my BService created)
Condition - (/ p1: nfeStatusServicoNF/p1: CUF = GO)
This error changes when configured to remove the condition receivers, this condition: Condition = (/ p1: nfeStatusServicoNF/p1: CUF = GO)
New Error:
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: unable to create a socket</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
Anybody help-me??
Thanks.
HMattos.Venkat,
I make cache refresh full using the user PIDIRUSER, see result bellow:
CPA cache refresh (mode=full) successfully executed in 7077 milliseconds.
But the error persist..
Other sugestion?
Regards,
HMattos. -
Hi all, I have configured a File-to-Idoc Integration Scenario and y get the next error (SXMB_MONI)
tag?
ThanksThank Rajevv.
I have recoded my java mapping to write a correct xml. Now I have a xml this this structure
<ZRI_CONTRATOS>
<IDOC BEGIN="">
<EDI_DC40 SEGMENT="">
<TABNAM/>
<MANDT/>
<DOCNUM/>
<DOCREL/>
<STATUS/>
<DIRECT/>
<OUTMOD/>
<EXPRSS/>
<TEST/>
<IDCOTYP/>
<CIMTYP/>
<MESTYP/>
<MESCOD/>
<MESFCT/>
<STD/>
<STDVRS/>
<STDMES/>
<SNDPOR/>
<SNDPRT/>
<SNDPFC/>
<SNDPRN/>
<SNDSAD/>
<SNDLAD/>
<RCVPOR/>
<RCVPRT/>
<RCVPFC/>
<RCVPRN/>
<RCVSAD/>
<RCVLAD/>
<CREDAT/>
<CRETIM/>
<REFINT/>
<REFGRP/>
<REFMES/>
<ARCKEY/>
<SERIAL/>
</EDI_DC40>
<ZRS_CABECERA_CNT SEGMENT="">
<OBJECT_EX/>
<TYPE_CNT/>
<OBJECT_ID/>
<PARTNER_NUMBER/>
<PARTNER_FCT/>
<PARTNER_NUMBER2/>
<PARTNER_FCT2/>
<PARTNER_NUMBER3/>
<PARTNER_FCT3/>
<PARTNER_NUMBER4/>
<PARTNER_FCT4/>
<DATE_BEGIN/>
<DATE_END/>
<DATE_SIGN/>
<ESTAT/>
<CURRENCY/>
And I get the next error:
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>I::000</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Fehler: I::000</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
But the fiedl Fehler: I::000 gaves me little information ( Error: I::000). Does any one any idea of where the problem cuold be.
Thanks -
Dynamic file Name Generation-problem
Hi Friends..
in My Idoc to File..
i want to generate Dynamic File Name ..
i put the logic in Message mapping -java intialization section
Container container = null;
SimpleDateFormat simpledatFormat = new SimpleDateFormat("yyyyMMdd");
Date date = new Date();
String datewithYear = simpledatFormat.format(date);
SimpleDateFormat simpledatFormat1 = new SimpleDateFormat("HHmmss");
Date date1 = new Date();
String datewithMs = simpledatFormat1.format(date1);
DynamicConfiguration conf = ((DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION));
DynamicConfigurationKey key = DynamicConfigurationKey.create("http:/"+"/"+"sap.com"+"/"+"xi"+"/"+"XI"+"/"+"System"+"/"+"File" , "FileName");
String oldFileName=conf.get(key);
String valueNew;
if( oldFileName == null){
valueNew = "HRXML"+datewithYear+datewithMs+".xml";
else{
valueNew =oldFileName+datewithYear+datewithMs+".xml";
//set the new filename
conf.put(key, valueNew);
and i did in reciever File adaper adaper specific settings..
i am getting error sxmb_moni..
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Request Message Mapping
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_ZHRMD5_to_HRMasterData_MM_</SAP:P1>
<SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
<SAP:P3>java.lang.NullPointerException</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_ZHRMD5_to_HRMasterData_MM_: java.lang.NullPointerException</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
if we remove the dynamic File configuration logic in message mapping ..i am getting the result..
please guide me..Container container = null;
DynamicConfiguration conf = ((DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION));
bound to get a NPE as your variable container is not getting intialized to a valid object ref here... -
Hi All,
Business scenario: File-To-File, file needs content conversion
My Graphical mapping is working fine. I tested with sample file in interface mappin also. but when I'm executing the scenario it is giving following error.
Error: (SXMB_MONI)->error inf
RuntimeException in Message-Mapping transformatio
Content:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Request Message Mapping
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_FILE_TO_FILE_CSV_</SAP:P1>
<SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
<SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>During the application mapping com/sap/xi/tf/_FILE_TO_FILE_CSV_ a com.sap.aii.utilxi.misc.api.BaseRuntimeException was thrown: RuntimeException in Message-Mapping transformatio~</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error
Can anyone pls analyze and suggest any solution, otherwise shall I post to SAP bcz i posted the same earlier and past some days I'm struggling to solve but faild: I executed Idoc-to-File and File-to-Idoc but in that no content conversion takes place.
regards,
venu.Hi Suraj,
Following is the payload of Inbound message.
<?xml version="1.0" encoding="utf-8" ?>
- <ns:FILEINPUTCSV xmlns:ns="urn://f1send">
- <Root>
- <H1>
<F1>"V00"</F1>
<F2>10</F2>
<F3>"venu"</F3>
<F4>144857</F4>
<F5>77</F5>
<F6>29</F6>
</H1>
- <sub1>
<KF>"A11"</KF>
<S12>"ARC"</S12>
<S13>240904</S13>
<S14>20050</S14>
<S15>9</S15>
</sub1>
- <sub2>
<KF>"A12"</KF>
<S22>"ARC"</S22>
<S23>12345</S23>
<S24>990</S24>
<S25>9</S25>
</sub2>
- <sub3>
<KF>"A27"</KF>
<S32>"Va2440094"</S32>
</sub3>
</Root>
</ns:FILEINPUTCSV>
Following is the source document view on message mapping test
<?xml version="1.0" encoding="UTF-8"?>
<ns:FILEINPUTCSV xmlns:ns="urn://f1send">
<H1>
<F1>V00</F1>
<F2>10</F2>
<F3>venu</F3>
<F4>144857</F4>
<F5>77</F5>
<F6>29</F6>
</H1>
<sub1>
<S11>A11</S11>
<S12>ARC</S12>
<S13>240904</S13>
<S14>20050</S14>
<S15>9</S15>
</sub1>
<sub2>
<S21>A12</S21>
<S22>ARC</S22>
<S23>12345</S23>
<S24>99</S24>
<S25>9</S25>
</sub2>
<sub3>
<S31>A27</S31>
<S32>Va2440094</S32>
</sub3>
</ns:FILEINPUTCSV>
Following is the content conversion at sender adapter side.
Document name:FILEINPUTCSV
Name space:urn://f1send
Record set name: Root
Record set structure: H1,1,sub1,,sub2,,sub3,*
Record set sequence:Ascending
Record sets per message: *.
Key Field name: KF
Key field type: String
Name value
H1.fieldname : F1,F2,F3,F4,F5,F6
H1.filedSeparator : ,
H1.endSeparator : 'nl'
H1.processFieldNames : fromConfiguration
sub1.fieldNames :KF,S12,S13,S14,S15
sub1.fieldSeparator : ,
sub1.endSeperator : 'nl'
sub1.processFieldNames :fromConfiguration
sub2.fieldNames :KF,S22,S23,S24,S25
sub2.fieldSeparator : ,
sub2.endSeparator : 'nl'
sub2.processFieldNames : fromConfiguration
sub3.fieldNames :KF,S32
sub3.fieldSeparator :,
sub3.endSeparator :'nl'
sub3.processFieldNames : fromConfiguration
H1.keyFieldValue :"V00"
sub1.keyFieldValue :"A11"
sub2.keyFieldValue :"A12"
sub3.keyFieldValue :"A27"
Follwoing is the runtime exception in SXMB_MONI
During the application mapping com/sap/xi/tf/_FILE_TO_FILE_CSV_ a com.sap.aii.utilxi.misc.api.BaseRuntimeException was thrown: Runti
meException in Message-Mapping transformatio~
Exception of class CX_XMS_SYSERR_MAPPING
Regards,
venu.
Regards,
venu. -
PI 7.11 - How to create a System Error in SXMB_MONI using a Java Mapping
Hi
We ve go a Java Mapping in a File-to-HTTP Scenario. It works perfect except of one error case: if an empty source file or a source file with the wrong structure is delivered. In this case our Java Mapping forwards an empty payload to the HTTP channel. So, for PI is the mapping successful.
I'd like to recognize this case and invoke a system error in the SXMB_MONI, so that this mapping will be stopped and our alerting concept informs the users. I know, how to recognize the case in Java but need to know how to create the System Error Status in the PI System.
Thanks in advance
MichaelHi Michael,
Please refer here for the mapping API description:
http://help.sap.com/javadocs/NW04S/SPS09/pi/com/sap/aii/mapping/api/package-summary.html
You can use the StreamTransformationException exception describet there to raise an error from your Java mapping. Direct link:
http://help.sap.com/javadocs/NW04S/SPS09/pi/com/sap/aii/mapping/api/StreamTransformationException.html
You might also consider using the "Empty-File Handling" option in sender file CC to avoid processing empty files by PI.
Hope this helps,
Greg -
System Error in Message Monitoring while it shows checked flag in SXMB_MONI
Hia,
We are working on ABAP Proxy --> SAP PI 7.1 --> SOAP (Asynchronous Scenario).
(ECC -> PI -> Legacy CRM)
I have following queries:
1. While sending messge across to Legacy system, we can see CHECKED flag in SXMB_MONI but there is System Error in Message Monitoring. When checked legacy system is unable to receive any message. Cannot understand the issue.
2. Is there any way to check in PI system whether the message has reached Legacy System other than making scneario synchronous?
RegardsSystem is getting connected and able to send asynchronous messages to legacy system. But getting following error while sending synchronous error:
2010-05-10 13:15:05 Information Delivering to channel: CC_SOAP_SOReject_Out
2010-05-10 13:15:05 Information SOAP: request message entering the adapter with user J2EE_GUEST
2010-05-10 13:15:05 Information SOAP: completed the processing
2010-05-10 13:15:05 Information SOAP: continuing to response message f33caa90-5c07-11df-c659-96d147c2ff0f
2010-05-10 13:15:05 Error SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Object reference not set to an instance of an object.
2010-05-10 13:15:05 Error Adapter Framework caught exception: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Object reference not set to an instance of an object.
2010-05-10 13:15:05 Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Object reference not set to an instance of an object.. Setting message to status failed.
2010-05-10 13:15:06 Error The message status was set to FAIL.
I have already checked Data Structure and it is fine.
Regards
In this scenarios we are using XSLT mapping using CDATA.
Please suggest solution. -
Hi,
I created a scenario in my XI development scenario.i tested it and it worked there correctly.but once i put all these scenarios into my XI production i get the following error in the transaction sxmb_moni
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Receiver Grouping
-->
- <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 =</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="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- <!-- ************************************
-->
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
<Trace level="1" type="T">COMMIT is done by XMB !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<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="1" type="T">system-ID = XIP</Trace>
<Trace level="1" type="T">client = 200</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = XIAPPLUSER</Trace>
<Trace level="1" type="Timestamp">2005-10-12T10:39:28Z 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 level="1" type="T">Message-GUID = 4349D7D080A900FE00000000AC15012C</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 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="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="1" type="T">Queue name : XBTI0011</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0011</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler 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="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<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 level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="1" type="T">system-ID = XIP</Trace>
<Trace level="1" type="T">client = 200</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = XIAPPLUSER</Trace>
<Trace level="1" type="Timestamp">2005-10-12T10:39:28Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- <!-- ************************************
-->
<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="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION" />
- <!-- ************************************
-->
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<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="1" type="T">No Relation found - accept given receivers.</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
</SAP:Trace>
Thanks and Regards,
JishiHi Jishi
Not enough information in the trace.
Boost up ur trace level as Manish said, also check the entry for your pipeline url as well in your SLD for the business system you are using.
It should be something like this,
http://XIServer:8000/sap/xi/engine?type=entry
cheers
Sameer -
Error in Out bound status in sxmb_moni in WS to IDOC scenario
HI all,
This question remains unresolved I have Provided the trace contents as asked by XIans.
I am Again sending the contents of the trace.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Response
-->
- <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 =</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="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- <!-- ************************************
-->
<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.0</Trace>
<Trace level="2" type="T">Host = pitest.monet.local:8001</Trace>
<Trace level="2" type="T">Server protocol = HTTP/1.0</Trace>
<Trace level="2" type="T">Remote address = 10.10.10.26</Trace>
<Trace level="1" type="T">COMMIT is done by XMB !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- <!-- ************************************
-->
<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 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 = PIT</Trace>
<Trace level="3" type="T">client = 001</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = ZPIAPPLUSER</Trace>
<Trace level="1" type="Timestamp">2007-02-01T05:40:57Z CST</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 level="1" type="T">Message-GUID = 4B7D33199091C54592B7B94A466ED9C2</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 level="3" type="T">QOS = EO</Trace>
<Trace level="3" type="T">Message-GUID = 4B7D33199091C54592B7B94A466ED9C2</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 : XBTI0004</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0004</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 = 4B7D33199091C54592B7B94A466ED9C2</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 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 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 = PIT</Trace>
<Trace level="3" type="T">client = 001</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = ZPIAPPLUSER</Trace>
<Trace level="1" type="Timestamp">2007-02-01T05:40:57Z CST</Trace>
<Trace level="1" type="T">----
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC">
<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 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 level="3" type="T" />
<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 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 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 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 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 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 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 level="3" type="T" />
<Trace level="1" type="Timestamp">2007-02-01T05:40:57Z CST Begin of pipeline processing PLSRVID = CENTRAL</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
<Trace level="1" type="Timestamp">2007-02-01T05:40:57Z CST 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 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 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: - ERP_D_ADR200</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-01T05:40:57Z CST 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-01T05:40:57Z CST 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 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 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) ERP_D_ADR200 ATT_ABS.ATT_ABS01</Trace>
<Trace level="2" type="T">...valid InbIf without Condition: ATT_ABS.ATT_ABS01</Trace>
<Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2007-02-01T05:40:57Z CST 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 level="1" type="Timestamp">2007-02-01T05:40:57Z CST 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 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 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 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 = XBTO4___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 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 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-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 level="3" type="T">message version successfully read from persist version= 004</Trace>
<Trace level="2" type="T">Increment log sequence to 005</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 = PIT</Trace>
<Trace level="3" type="T">client = 001</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = ZPIAPPLUSER</Trace>
<Trace level="1" type="Timestamp">2007-02-01T05:40:57Z CST</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- <!-- ************************************
-->
<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 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 level="3" type="T" />
<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 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 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 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 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 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 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 level="3" type="T" />
<Trace level="1" type="Timestamp">2007-02-01T05:40:57Z CST 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-01T05:40:57Z CST 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 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 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 already defined in interface determination</Trace>
<Trace level="3" type="T">Object ID of Interface Mapping 4AE42F31B3BC3733A792B4DDEDD54756</Trace>
<Trace level="3" type="T">Version ID of Interface Mapping 1D47292048CD11DB8AD9FDDE0A0A0A5E</Trace>
<Trace level="1" type="T">Interface Mapping http://www.gemsconsult.com/LAB_ABA/wstoidoc PublishLeaveStatusSoapIN_to_ATT_ABS01</Trace>
<Trace level="3" type="T">Mapping Steps 1 JAVA com/sap/xi/tf/_PublishLeaveStatusSoapIN_to_ATT_ABS01_</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/_PublishLeaveStatusSoapIN_to_ATT_ABS01_.</Trace>
<Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._PublishLeaveStatusSoapIN_to_ATT_ABS01_</Trace>
<Trace level="2" type="T">Java mapping com/sap/xi/tf/_PublishLeaveStatusSoapIN_to_ATT_ABS01_ completed. (executeStep() of com.sap.xi.tf._PublishLeaveStatusSoapIN_to_ATT_ABS01_</Trace>
<Trace level="3" type="T">Dynamic Configuration Is Empty</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2007-02-01T05:40:57Z CST 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 = 005</Trace>
<Trace level="3" type="T">Message version 005</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-01T05:40:57Z CST 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 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 level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <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">-KCRS_3RDP_D</Trace>
<Trace level="2" type="T">-ERP_D_ADR200</Trace>
<Trace level="2" type="T">urn:sap-com:document:sap:idoc:messages.ATT_ABS.ATT_ABS01</Trace>
<Trace level="2" type="T">Channel found: - ERP_D_ADR200 - IDOC</Trace>
<Trace level="2" type="T">no header mapping defined</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2007-02-01T05:40:57Z CST 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 = 006</Trace>
<Trace level="3" type="T">Message version 006</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_CALL_ADAPTER">
<Trace level="1" type="Timestamp">2007-02-01T05:40:57Z CST Start of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
- <!-- ************************************
-->
<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 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 level="3" type="T">Channel for IDOC adapter: IDoc</Trace>
<Trace level="3" type="T" />
<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 = IDOC</Trace>
<Trace level="3" type="T">ADRESSMOD = SD</Trace>
<Trace level="3" type="T">P_CLASS = CL_IDX_IDOC_SERVICE</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 level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- <!-- ************************************
-->
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">---- Outbound IDoc-Adapter -
</Trace>
<Trace level="1" type="T">----
</Trace>
- <Trace level="1" type="B" name="CL_IDX_IDOC_SERVICE-ENTER_PLSRV">
<Trace level="1" type="T">Pipeline Service ID: PLSRV_CALL_ADAPTER</Trace>
<Trace level="1" type="T">Get Information from IS-Header Objekt</Trace>
<Trace level="1" type="T">Get Information from SD-IDoc-Endpoint</Trace>
<Trace level="2" type="T">----
</Trace>
<Trace level="2" type="T">IDoc-Endpoint Channel :</Trace>
<Trace level="2" type="T">RFCDEST : ADR_200</Trace>
<Trace level="2" type="T">Port : SAPADR</Trace>
<Trace level="2" type="T">Docrel :</Trace>
<Trace level="2" type="T">Version : 3</Trace>
<Trace level="2" type="T">Saprel : 700</Trace>
<Trace level="2" type="T">Queue-ID:</Trace>
<Trace level="2" type="T">----
</Trace>
<Trace level="1" type="T">Sender and Receiver after Header-Mapping</Trace>
<Trace level="1" type="T">Sender service KCRS_3RDP_D</Trace>
<Trace level="1" type="T">Receiver service ERP_D_ADR200</Trace>
<Trace level="1" type="T">Get IDoc-XML from the Resource Objekt</Trace>
- <Trace level="1" type="B" name="IDX_XML_TO_IDOC">
<Trace level="1" type="T">Parse XML-BODY</Trace>
<Trace level="1" type="T">Get the Metadata for port SAPADR</Trace>
<Trace level="2" type="T">----
</Trace>
<Trace level="2" type="T">IDX_STRUCTURE_GET Details</Trace>
<Trace level="2" type="T">Port : SAPADR</Trace>
<Trace level="2" type="T">IDoctyp : ATT_ABS01</Trace>
<Trace level="2" type="T">Cimtyp :</Trace>
<Trace level="2" type="T">Release :</Trace>
<Trace level="2" type="T">Version : 3</Trace>
<Trace level="2" type="T">Direction : 2</Trace>
<Trace level="2" type="T">SAPREL : 700</Trace>
<Trace level="2" type="T">----
</Trace>
<Trace level="1" type="T">Convert one IDoc</Trace>
<Trace level="2" type="T">Convert Control Record</Trace>
<Trace level="2" type="T">Convert Data Records</Trace>
<Trace level="3" type="T">Segment= E1BP7011_1</Trace>
<Trace level="2" type="T">Number of found Data records: 1</Trace>
<Trace level="1" type="T">Make Syntax check of actual Idoc</Trace>
<Trace level="2" type="T">----
</Trace>
<Trace level="2" type="T">IDX_SYNTAX_CHECK</Trace>
<Trace level="2" type="T">Port : SAPADR</Trace>
<Trace level="2" type="T">IDoctyp : ATT_ABS01</Trace>
<Trace level="2" type="T">Cimtyp :</Trace>
<Trace level="2" type="T">RFC-Dest :</Trace>
<Trace level="2" type="T">----
</Trace>
<Trace level="1" type="T">Convert Segment-Types to Segment-Definitions</Trace>
</Trace>
<Trace level="1" type="T">Call Outbound IDoc-Adapter</Trace>
<Trace level="1" type="T">Call Outbound IDoc-Adapter</Trace>
- <Trace level="1" type="B" name="IDX_OUTBOUND_XMB">
<Trace level="1" type="T">FM IDOC_INBOUND_ASYNCHRONOUS with RFCDEST= ADR_200</Trace>
<Trace level="2" type="T">Used TID = 0A0A0A57187045C17D691641</Trace>
</Trace>
<Trace level="2" type="T">TID : 0A0A0A57187045C17D691641</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2007-02-01T05:40:57Z CST End of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</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="3" type="T">Async processing: skip mapping of response</Trace>
</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Async processing completed OK.</Trace>
<Trace level="3" type="T">system-ID = PIT</Trace>
<Trace level="3" type="T">client = 001</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = ZPIAPPLUSER</Trace>
<Trace level="1" type="Timestamp">2007-02-01T05:40:57Z CST</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="3" type="T">Persisting message Status = 003</Trace>
<Trace level="3" type="T">Message version 008</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</SAP:Trace>
Please let me know where the problem is?
Thanks,
SrinivasaPSrinivas,
This is your error msg. Right? This is what the others are asking you...
Have you checked Wojcitech's reply? Do that. Let us know the result...
P.S: I copied this from one of your previous threads.
Regards,
Jai Shankar
<i>HI I am Gettin the following error in SXMB_MONI
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
<SAP:P1>XML IDoc conversion: No known segments identified</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: XML IDoc conversion: No known segments identified</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
att_abs01is the Idoc used.
Thanks
<b>Hi,
Please check your configuration in IDX1 and verify if port is the same in IDOC receiver communication channel. Check also if in IDX2 you have current IDOC metadata, you can try to download it manually.
Regards,
Wojciech</b>
</i> -
Hi,
I am facing a small problem in XI. Could you please help me out for the same.
The problem is like
for a XI type communication channel for sender FTP I see following error in SXMB_MONI -
Unable to read user password from communication channel of type Error when accessing the secure store (access ID = 3650CAFA1FBAA04E8F260C6C4C1923FA) Error while reading from the secure store: ERROR_UNKNOWN: Cannot find entry in secure store (SECSTORE,023).
Could anyone of you please let me know what could be the problem here. I have specified the correct user name and pwd in communication channel.
Thanks,First of all, u have to access the J2EE server. So go to the system where XI is installed.
Now ConfigTool can be used in 2 ways. The easier one is GUI Config Tool. After installing the SAP Web AS Java, a configtool directory is created, containing a configtool script file. U have to double click it to open.
Then see this
http://help.sap.com/saphelp_nw04/helpdata/en/4e/d1cf8d09a94ae79319893c2537d3a0/frameset.htm
Now specific to ur requirement, c this
http://help.sap.com/saphelp_nw04/helpdata/en/c4/c13230eea54e7996b89fecef904a1c/frameset.htm
Regards,
Prateek -
Hi Experts ,
I found this error in SXMB_MONI.please help me what would be the error.I have checked in SMQ1,SMQ2 also but the queues are not strucked.
<!-- ************************************
-->
<Trace level="1" type="T">User: PIECC</Trace>
<Trace level="1" type="T">Language: E</Trace>
<Trace level="1" type="T">ALE-AUDIT-IDoc-Inbound Handling</Trace>
<Trace level="1" type="T">IDoc-Inbound-Handling</Trace>
<Trace level="2" type="T">Tunneling needed?</Trace>
<Trace level="2" type="T">Partytype = LS fallback to logical system</Trace>
<Trace level="1" type="T">Syntax-Check-Flag X</Trace>
<Trace level="1" type="T">IDoc-Tunnel-Flag</Trace>
<Trace level="1" type="T">Queueid</Trace>
- <Trace level="1" type="B" name="IDX_IDOC_TO_XML">
<Trace level="1" type="T">Docnum 0000000000881605</Trace>
<Trace level="1" type="T">Get the Metadata for port SAPR3D</Trace>
<Trace level="2" type="T">----
</Trace>
<Trace level="2" type="T">IDX_STRUCTURE_GET Details</Trace>
<Trace level="2" type="T">Port : SAPR3D</Trace>
<Trace level="2" type="T">IDoctyp : /AFS/ORDERS06</Trace>
<Trace level="2" type="T">Cimtyp : ZIMPOINFO</Trace>
<Trace level="2" type="T">RFCDest :</Trace>
<Trace level="2" type="T">Release : 700</Trace>
<Trace level="2" type="T">Version : 3</Trace>
<Trace level="2" type="T">Direct : 1</Trace>
<Trace level="2" type="T">SAPREL : 700</Trace>
<Trace level="2" type="T">----
</Trace>
<Trace level="1" type="T">Convert Segment-Definitions to Types</Trace>
<Trace level="1" type="T">Make Syntax check of current IDoc</Trace>
<Trace level="2" type="T">----
</Trace>
<Trace level="2" type="T">IDX_SYNTAX_CHECK</Trace>
<Trace level="2" type="T">Port : SAPR3D</Trace>
<Trace level="2" type="T">IDoctyp : /AFS/ORDERS06</Trace>
<Trace level="2" type="T">Cimtyp : ZIMPOINFO</Trace>
<Trace level="2" type="T">----
</Trace>
<Trace level="2" type="T">Create XML-Control Record</Trace>
<Trace level="2" type="T">Create XML-Data Records</Trace>
</Trace>
<Trace level="2" type="T">Partytype = LS fallback to logical system</Trace>
<Trace level="2" type="T">Set Sender Routing-object</Trace>
<Trace level="1" type="T">Set Receiver Routing-object</Trace>
<Trace level="1" type="T">Exit Function IDX_INBOUND_XMB</Trace>
<Trace level="1" type="T">Message ID = 005056A961341EE189D58C5E5FB798DC</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS">
<Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_EXT_PID: CENTRAL</Trace>
<Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_INT_PID: SAP_CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="2" type="T">system-ID = PID</Trace>
<Trace level="2" type="T">client = 300</Trace>
<Trace level="2" type="T">language = E</Trace>
<Trace level="2" type="T">user = PIECC</Trace>
<Trace level="1" type="Timestamp">2011-12-14T23:36:04Z PST</Trace>
<Trace level="1" type="T">ACL Check is performed</Trace>
<Trace level="1" type="T">XML validation is executed</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- <!-- ************************************
-->
<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 level="1" type="T">Queue name : XBTL0000</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
</Trace>
<Trace level="1" type="T">Generated prefixed queue name =</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="1" type="T">--start determination of sender interface action</Trace>
<Trace level="1" type="T">select interface ZPOMSG./AFS/ORDERS06.ZIMPOINFO</Trace>
<Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:idoc:messages</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="2" type="T">Increment log sequence to 001</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="2" type="T">system-ID = PID</Trace>
<Trace level="2" type="T">client = 300</Trace>
<Trace level="2" type="T">language = E</Trace>
<Trace level="2" type="T">user = PIECC</Trace>
<Trace level="1" type="Timestamp">2011-12-14T23:36:04Z PST</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- <!-- ************************************
-->
<Trace level="1" type="T">>>>PID delete old pid determination coding</Trace>
- <Trace level="1" type="B" name="PLSRV_XML_VALIDATION_RQ_INB">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_XMS_PLSRV_VALIDATION-ENTER_PLSRV">
<Trace level="1" type="T">Reading sender agreement</Trace>
<Trace level="1" type="T">Message does not contain a sender agreement</Trace>
<Trace level="1" type="T">Inbound validation by Integration Engine does not take place</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <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">Using Receiver Determination AC49C10FD6A33945A771DAA45DC95E91</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: - BC_HighJump</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 2</Trace>
<Trace level="2" type="T">...valid Receiver w/o Condition: - BC_CheckPoint</Trace>
<Trace level="2" type="T">No Receiver found behaviour: 0</Trace>
<Trace level="2" type="T">Number of Receivers:2</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <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) BC_CheckPoint SIIA_PO_Creation_CheckPoint</Trace>
<Trace level="2" type="T">...valid InbIf without Condition: SIIA_PO_Creation_CheckPoint</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) BC_HighJump SI_PO_Creation_WS_I_Async</Trace>
<Trace level="2" type="T">...valid InbIf without Condition: SI_PO_Creation_WS_I_Async</Trace>
<Trace level="2" type="T">Number of receiving Interfaces:2</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
- <!-- ************************************
-->
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT2->ENTER_PLSRV" />
- <!-- ************************************
-->
<Trace level="1" type="T">number of receivers: 2</Trace>
<Trace level="1" type="T">Multi-receiver split case</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Splitting loop start</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="2" type="T">child 1</Trace>
<Trace level="1" type="T">Post-split internal queue name = XBTM0000</Trace>
<Trace level="1" type="T">Persisting split kid = 005056A961341EE189D58C508D91B8DC</Trace>
<Trace level="1" type="T">Generated prefixed queue name =</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="1" type="T">--start determination of sender interface action</Trace>
<Trace level="1" type="T">select interface ZPOMSG./AFS/ORDERS06.ZIMPOINFO</Trace>
<Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:idoc:messages</Trace>
<Trace level="1" type="T">--start determination of receiver interface action</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface SIIA_PO_Creation_CheckPoint</Trace>
<Trace level="1" type="T">select interface namespace urn:foxhead.com/highjump/INF008/PO_Creation</Trace>
<Trace level="1" type="T">--no interface action for sender or receiver found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="2" type="T">Increment log sequence to 001</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="2" type="T">system-ID = PID</Trace>
<Trace level="2" type="T">client = 300</Trace>
<Trace level="2" type="T">language = E</Trace>
<Trace level="2" type="T">user = PIECC</Trace>
<Trace level="1" type="Timestamp">2011-12-14T23:36:04Z PST</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- <!-- ************************************
-->
<Trace level="1" type="T">>>>PID delete old pid determination coding</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="B" name="CL_XMS_MAIN-CALL_PLSRV" />
- <!-- ************************************
-->
<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="1" type="T">Interface mapping missing in cache</Trace>
</Trace>
<Trace level="2" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
Regards,
ShajuHi,
pease see this thread,
Posting XML via HTTP post returns "Envelope missing in SOAP message header"
regrads,
ganesh.
Maybe you are looking for
-
Itunes get "Send Error Report" message
Alright so when I try and open itunes I get a send error report message. I've tried updating it and that doesnt work and I've already tried reinstalling it. I thought quicktime was the error so I went to try and remove it from my computer. As it was
-
Web layout in Illustrator CS4 and import to DreamWeaver
I'm much more comfortable working in Illustrator CS4 than in DreamWeaver CS4. I'd like to lay out my web pages in Illustrator and then transfer those layouts to DreamWeaver. Does anyone know of tutorial on how to do this, or have any suggestions o
-
Drag and drop issues. I'm not alone.
So clearly I'm not the only one dealing with this, I've seen other topics with people running into this problem. All of a sudden last night I was unable to drag and drop stuff around, copy and past, run a new program and I have no Spotlight. I've res
-
I have a 2008 24" iMac (model 8,1) I bought it new in 2010 from MacConnection. This machine has been wonderful, however in the last week or so the screen seems to "flicker" upon waking from sleep (I rarely shut the iMac down.) The flickering lasts fo
-
2 devices 1 acount in game center
please help i have iPhone and iPad and i have one apple ID on the both when i try to sign in game center in my iPad it made new acount i need to delet this new acount and use same acount in all my devices please how can i?