Trace level="1" type="T" -no interface action for sender or receiver found

Hi Experts,
I try to integrate PI and abap 7.0 using XI adapter (feel doubts about type).
RWB and SXMB_MONI at PI side show that test message was successfully sent. But I cant see it in DQ
http://cnh.com/XI/SDIIOC01/RCVR</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="1" type
What could be the problem which I'm facing and how could I fix this
regards
nagendra

i understood its ur SAP XI to inbound proxy scenario?
Do the message in MONI of XI is showing correctly?
R u getting an error message in R3 moni?
Did u configure ur scenario correctly both at Xi n R3 using sproxy tcode.
chirag

Similar Messages

Error in BPM: "no interface action for sender or receiver found"

hello,
i configured a interface scenario SOAP - PI - Idoc using a BPM sync/async bridge.
i followed the document
when i try to call interface with my soap client i have the follow error in SXMB_MONI:
Timeout condition of pipeline reached
if i check the detail in trace i can found the follow message:
<Trace level="1" type="T">select interface SI_MATREQ_ABS</Trace>
<Trace level="1" type="T">select interface namespace http://pmf/orders</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>
in BPM monitor i cannot see any interesting logs for determine the problem.
I clear cache many time and reimported Integration Process more time.
Have u some suggestion?
thanks in advance

Hi,
Check whether this thread help you or not....
SXMB_MONI: no interface action for sender or receiver found
Regds,
Pinangshuk.

XML Monitor: no interface action for sender or receiver found

Hi,
I am new to XI and currently working on Supplier Network Collaboration ( SNC) to Integrate PO's from ECC to SCM system via XI. I have successfully triggered PORDCR1 message for which I was able to see the XML message in XI. The message is stuck on the Inbound of SCM system ( seen in SMQ2 with error message "Internal error, calling address update without address ID Message no. SR053).
When i double click on Inbound queue (SMQ2) in SCM system it takes me to SXI_Monitor
Below is the log from bottom screen for Trace. Can you please check and see if you could help to resolve the issue?
Thanks,
Tejinder
Below is the Trace bottom screen details
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">http content length 7569</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">Process ID: 27633</Trace>
<Trace level="1" type="T">Work Process ID: 0</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 = AM2</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = ALE_SNC</Trace>
<Trace level="1" type="Timestamp">2014-09-10T15:06:15Z 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 = 005056B61D0E1ED48E9F7E70255B98CE</Trace>
<Trace level="1" type="T">PLNAME = RECEIVER</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 = RECEIVER</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_RECEIVER</Trace>
<Trace level="1" type="T">Queue name : XBTR0005</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTR0005</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="T">--start determination of sender interface action</Trace>
<Trace level="1" type="T">select interface</Trace>
<Trace level="1" type="T">select interface namespace</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 ReplenishmentOrderNotification_In</Trace>
<Trace level="1" type="T">select interface namespace http://sap.com/xi/SNC/Global</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>
</SAP:Trace>

Hi Tejinder
Check this link
NO INTERFACE ACTION FOR SENDER OR RECEIVER FOUND
SXMB_MONI: no interface action for sender or receiver found
Error: no interface action for sender or receiver found
no interface action for sender or receiver found - SMQ2 SYSFAIL
Regards
Osman
Message was edited by: Osman Jabri

Error: no interface action for sender or receiver found

Hello,
I have configured a asynchronous RFC to JDBC scenario.
When i try to execute the end to end scenario , the message in SXMB_MONI is with a green flag(scheduled) and queue status is yellow and when i double the message , the trace shows following message:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<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">Work Process ID: 25711</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 = HXD</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PIAFUSER</Trace>
<Trace level="1" type="Timestamp">2010-05-24T12:23:09Z 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 = 3CA00D0C20460CD10B3CA18E3C804118</Trace>
<Trace level="1" type="T">PLNAME = RECEIVER</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 = RECEIVER</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_RECEIVER</Trace>
<Trace level="1" type="T">Queue name : XBTR0004</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTR0004</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="T">--start determination of sender interface action</Trace>
<Trace level="1" type="T">select interface</Trace>
<Trace level="1" type="T">select interface namespace</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 Z_SD_HP_SALESORG</Trace>
<Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:rfc:functions</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>
</SAP:Trace>
The pipeline steps on the left hand side in sxmb_moni shows only inbound Message i.e remaining steps are not executed.
When i try the execute message by directly sending message from Runtime Workbench , the scenario is executed successfully.
Please help.
Thanks & Regards,
Loveena

Hello,
The problem was with the Client. Our Xi is running on Client 200 wheras at runtime it was picking up the default client 001.
So after changing the default Client 001 to 200.
The scenario was working fine.
But from the third time onwards again it is taking the default Client and I am facing the issue.
I guess it is some Cache problem. Can anybody tell me how to refresh the cache.
Thanks ,
Loveena

NO INTERFACE ACTION FOR SENDER OR RECEIVER FOUND

Hi Masters of SRM
Into SRM/SUS client received an message XML across XI the SXMB_MONI in trace section show the next message

<Trace level="3" type="T">Persisting message Status = 003</Trace>
<Trace level="3" type="T">Message version 002</Trace>
<Trace level="3" type="T">Pipeline SENDER</Trace>
<Trace level="1" type="T">--start determination of sender interface action</Trace>
<Trace level="1" type="T">select interface PurchaseOrderRequest_Out</Trace>
<Trace level="1" type="T">select interface namespace http://sap.com/xi/SRM/Procurement/Global</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</Trace>
<Trace level="1" type="T">select interface namespace</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>
</SAP:Trace
NO INTERFACE ACTION FOR SENDER OR RECEIVER FOUND
what can I do ?
thanks.

Hi Nikhil .
yes the Receiver Determination is Active.
I can see other message into message in SUS client these is the complete message.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">Work Process ID: 884922</Trace>
<Trace level="1" type="T">COMMIT is expected by application !</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 = SND_CENTR</Trace>
<Trace level="3" type="T">Start pipeline found</Trace>
<Trace level="2" type="T">Switch to external start pipeline PID = SENDER</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 = SRD</Trace>
<Trace level="3" type="T">client = 009</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = WF-BATCH</Trace>
<Trace level="1" type="Timestamp">2011-03-08T02:25:46Z 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 = 4D71A759FF9E00D8E1008000B9F06E02</Trace>
<Trace level="1" type="T">PLNAME = SENDER</Trace>
<Trace level="1" type="T">QOS = EOIO</Trace>
<Trace level="1" type="T">Queue-Id = ORD4000000482</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="3" type="T">QOS = EOIO</Trace>
<Trace level="3" type="T">Message-GUID = 4D71A759FF9E00D8E1008000B9F06E02</Trace>
<Trace level="1" type="T">Get definition of external pipeline = SENDER</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = SENDER</Trace>
<Trace level="3" type="T">Internal PLID = SAP_SENDER</Trace>
</Trace>
<Trace level="1" type="T">Get definition of internal pipeline = SAP_SENDER</Trace>
<Trace level="3" type="T">Generate prefixed queue name</Trace>
<Trace level="1" type="T">Queue name : XBQSORD4000000482</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBQSORD4000000482</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 = 4D71A759FF9E00D8E1008000B9F06E02</Trace>
<Trace level="3" type="T">Call qRFC .... Version = 000</Trace>
<Trace level="3" type="T">Call qRFC .... Pipeline = SENDER</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 SENDER</Trace>
<Trace level="1" type="T">--start determination of sender interface action</Trace>
<Trace level="1" type="T">select interface PurchaseOrderRequest_Out</Trace>
<Trace level="1" type="T">select interface namespace http://sap.com/xi/SRM/Procurement/Global</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">Work Process ID: 725194</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">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 SENDER</Trace>
<Trace level="3" type="T">system-ID = SRD</Trace>
<Trace level="3" type="T">client = 009</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = WF-BATCH</Trace>
<Trace level="1" type="Timestamp">2011-03-08T02:25:46Z 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 SENDER</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = SENDER</Trace>
<Trace level="3" type="T">Internal PLID = SAP_SENDER</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_SENDER</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline attributes</Trace>
<Trace level="3" type="T">PID = SAP_SENDER</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">PLSRVID = PLSRV_CALL_INTEGRATION_SERVER</Trace>
<Trace level="3" type="T" />
<Trace level="1" type="Timestamp">2011-03-08T02:25:46Z CST Begin of pipeline processing PLSRVID = SENDER</Trace>
- <Trace level="1" type="B" name="PLSRV_CALL_INTEGRATION_SERVER">
<Trace level="1" type="Timestamp">2011-03-08T02:25:46Z CST Start of pipeline service processing PLSRVID= PLSRV_CALL_INTEGRATION_SERVER</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_CALL_INTEGRATION_SERVER</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_INTEGRATION_SERVER</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_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 level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
<Trace level="1" type="T">URL for integration server read from global configuration</Trace>
<Trace level="1" type="T">URL= dest://SAP NETWEAVER XI</Trace>
- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
<Trace level="2" type="T">Addressing mode: CallIntegrationServer</Trace>
<Trace level="3" type="T">URL = dest://SAP NETWEAVER XI</Trace>
<Trace level="3" type="T">Host =</Trace>
<Trace level="3" type="T">Port =</Trace>
<Trace level="3" type="T">Transport protocol = HTTP</Trace>
<Trace level="3" type="T">Message protocol = 003000</Trace>
<Trace level="3" type="T">Path =</Trace>
<Trace level="3" type="T">Attributes of destination: SAP NETWEAVER XI</Trace>
<Trace level="3" type="T">Type = H</Trace>
<Trace level="3" type="T">Pipeline =</Trace>
<Trace level="3" type="T">Action = EXECUTE</Trace>
<Trace level="3" type="T">Host = mxwpides</Trace>
<Trace level="3" type="T">Port = 50000</Trace>
<Trace level="3" type="T">Client = 001</Trace>
<Trace level="3" type="T">User = PIAPPLUSER</Trace>
<Trace level="3" type="T">Language =</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">SSL not active</Trace>
<Trace level="1" type="T">----
</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">Serializing message object...</Trace>
<Trace level="1" type="T">HTTP Multipart document length: 8089</Trace>
<Trace level="3" type="T">HTTP-client: sending http-request...</Trace>
<Trace level="1" type="T">HTTP-client: request sent</Trace>
<Trace level="3" type="T">HTTP-client: request sent</Trace>
<Trace level="3" type="T">HTTP-client: Receiving http-response...</Trace>
<Trace level="1" type="T">HTTP-client: response received</Trace>
<Trace level="3" type="T">HTTP-client: checking status code...</Trace>
<Trace level="1" type="T">sap-xi-messageid 4D71A759FF9E00D8E1008000B9F06E02</Trace>
<Trace level="1" type="T">HTTP-client: status code = 200</Trace>
<Trace level="3" type="T">Deserializing message object...</Trace>
<Trace level="1" type="T">HTTP-client: parsed & response message object created</Trace>
<Trace level="3" type="T">HTTP-client: closing...</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2011-03-08T02:25:47Z CST End of pipeline service processing PLSRVID= PLSRV_CALL_INTEGRATION_SERVER</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 SENDER</Trace>
</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 = SRD</Trace>
<Trace level="3" type="T">client = 009</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = WF-BATCH</Trace>
<Trace level="1" type="Timestamp">2011-03-08T02:25:47Z 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 002</Trace>
<Trace level="3" type="T">Pipeline SENDER</Trace>
<Trace level="1" type="T">--start determination of sender interface action</Trace>
<Trace level="1" type="T">select interface PurchaseOrderRequest_Out</Trace>
<Trace level="1" type="T">select interface namespace http://sap.com/xi/SRM/Procurement/Global</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</Trace>
<Trace level="1" type="T">select interface namespace</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>
</SAP:Trace>
Thanks.
best regards

BPM Error: no interface action for sender or receiver found

Dear All
I am doing an HTTP to Proxy scenario using BPM Synch Asynch bridge. The error in HTTP is error 500 (Internal Serve Error)
I am getting following error in moni
<Trace level="1" type="T">select interface namespace urn:WorkDelivery</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 LocationSynch_Abs</Trace>
<Trace level="1" type="T">select interface namespace urn:WorkDelivery</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>
</SAP:Trace>
I have seen some posts on sdn regarding the same problem but couldn't get any solution out of it.
Please let me know how can this problem be solved.
Sourabh

I am using Two Synchronous interfaces:
Synh_Out: Used before BPM
Sync_Abs inside Synch/Asynch bridge:
I am using an switch step to check a condition then in both the branches I have a send step and a transformation step:
Send step1 is using one Asynch Abstract Interface
Send step2 is using Another Asynch Abstract Interface. These Interfaces have different message types.
The Transformation step in both the branchs have same operation mapping.
The laststep after switch step is closing A/S bridge.
There are two RDs after after BPM. They are having the same Interfaces as there in the respective send steps.
I can see the xml version of my BPM
Edited by: Sourabh Nirmal on Mar 30, 2010 8:56 AM

SXMB_MONI: no interface action for sender or receiver found

Hi Experts,
I try to integrate PI and BI 7.0 using XI adapter (feel doubts about type).
I used 2 giudes: "How to Push Data into BW from XI" and "How to Send XML Data to BW".
SLD check is ok. Proxy is active at BW side. Quality of Service - Exactly Once.
RWB and SXMB_MONI at PI side show that test message was successfully sent. But I cant see it in DQ (RSA7).
xml from SXMB_MONI at PI and reciever part:
<Trace level="1" type="T">--start determination of sender interface action</Trace>
<Trace level="1" type="T">select interface</Trace>
<Trace level="1" type="T">select interface namespace</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 data_tobw</Trace>
<Trace level="1" type="T">select interface namespace http://integrate/xi/bw</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>
Help me to send xml to BW please.
Thanx in advance,
Alex

>
Alexander Rychkov wrote:
> Hi Experts,
> I try to integrate PI and BI 7.0 using XI adapter (feel doubts about type).
> I used 2 giudes: "How to Push Data into BW from XI" and "How to Send XML Data to BW".
> SLD check is ok. Proxy is active at BW side. Quality of Service - Exactly Once.
>
> RWB and SXMB_MONI at PI side show that test message was successfully sent. But I cant see it in DQ (RSA7).
>
> xml from SXMB_MONI at PI and reciever part:
> <Trace level="1" type="T">--start determination of sender interface action</Trace>
> <Trace level="1" type="T">select interface</Trace>
> <Trace level="1" type="T">select interface namespace</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 data_tobw</Trace>
> <Trace level="1" type="T">select interface namespace http://integrate/xi/bw</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>
>
> Help me to send xml to BW please.
>
> Thanx in advance,
> Alex
confirm if interface data_tobw with namespace http://integrate/xi/bw is present in IR and also if it is activated.
Also do a cache refresh from sxi_cache

IDOC - BPM - IDOC Error --no sender or receiver interface definition found

I have an integration scenario, IDOC - BPM - IDOC. SAP will send ACC_GL_POSTING IDOC to XI, a BPM will start and then the BPM will send an IDOC to another SAP system.
I have read instructions on weblogs:
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
/people/krishna.moorthyp/blog/2005/06/09/walkthrough-with-bpm
The scenario has been successfully tested in the Test Configuration Tool. However, when I try send IDOC from the source, I received the message below in the trace.
<Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_BPE-ENTER_PLSRV">
<Trace level="3" type="T">Processing mode is</Trace>
<Trace level="3" type="T">created BPE proxy for message B45CB0079DFA814BAD22CD1ED64CA6AB</Trace>
<Trace level="1" type="B" name="interface activity determination">
<Trace level="1" type="T">Version 000</Trace>
<Trace level="1" type="T">Message status 000</Trace>
<Trace level="1" type="T">Interface action INIT</Trace>
<Trace level="1" type="T">(must be INIT for a new determination)</Trace>
<Trace level="1" type="T">start CHECK_INTERFACE</Trace>
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface ACC_GL_POSTING.ACC_GL_POSTING01*</Trace>
<Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:idoc:messages</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface ACC_GL_POSTING_abs*</Trace>
<Trace level="1" type="T">select interface namespace http://summaryFinancial.sap.dominofoods.com</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
<Trace level="1" type="T">end CHECK_INTERFACE</Trace>
<Trace level="1" type="T">Set interface action DEL into MAST</Trace>
</Trace>
<Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-GETBLOBDATA" />
<Trace level="3" type="T">inserted message into pipeline PE_ADAPTER</Trace>
<Trace level="1" type="Timestamp">2007-04-30T18:32:30Z EST qRFC raised on XBQO$PE_WS91000003</Trace>
</Trace>
Thanks,
Sergio

Rajeev,
The source system in the receiver determination is connected to R3. Other IDOCs are coming across the XI system.
Below is some trace information in the Receiver Determination.
<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: - IP_GeneralLedger</Trace>
<Trace level="2" type="T">No Receiver found behaviour: 0</Trace>
<Trace level="2" type="T">Number of Receivers:1</Trace>
<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) IP_GeneralLedger ACC_GL_POSTING_abs</Trace>
<Trace level="2" type="T">...valid InbIf without Condition: ACC_GL_POSTING_abs</Trace>
<Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
Thanks,
Sergio

Interface Determination causing issue in Receiver Determination

Hi
I am having an issue with interface and receiver determination as follows:
- Inbound message may be sent to two receivers.
- Message gets sent to first receiver, fails during interface determination. There are multiple inbound interfaces found based on a set of XPATH conditions. This creates an error 'Inbound interface found more than once for outbound interface '. That is itself is not the issue.
- Issue is that the message is stopped from going to the other receiver even if there are no issues in the interface determination for that receiver.
Is there a way to resolve this? Appreciate any help. Thx, Duncan

Again, thanks for the replies.
MONI for RD
- <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="3" type="T">...create rule engine</Trace>
<Trace level="3" type="T">...call rule engine for Condition %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice")% EX and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% CE COSTCENTRE or %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice")% EX and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% CE INTERPLANT or %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice")% EX and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% CE INTERPLANT_ONESTEP or %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice")% EX and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% CE INTRAPLANT or %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice")% EX and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% CE INTRAPLANT_ONESTEP or %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:receivingAdvice")% EX or %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:inventoryActivityOrInventoryStatus")% EX</Trace>
<Trace level="2" type="T">......extracting (new) for Extractor: XP /p2:despatchAdvice</Trace>
<Trace level="2" type="T">......extracting values found: 0</Trace>
<Trace level="2" type="T">......extracting (new) for Extractor: XP /p2:receivingAdvice</Trace>
<Trace level="2" type="T">......extracting values found: 1</Trace>
<Trace level="2" type="T">...valid Receiver with Condition: - GLR430</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 2</Trace>
<Trace level="3" type="T">...call rule engine for Condition %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice")% EX and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% NE COSTCENTRE and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% NE INTERPLANT and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% NE INTERPLANT_ONESTEP and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% NE INTRAPLANT and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% NE INTRAPLANT_ONESTEP</Trace>
<Trace level="2" type="T">...invalid Receiver: P_3PL_XML_ME_ODTH - despatchAdviceToE1EDT20</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 3</Trace>
<Trace level="2" type="T">...valid Receiver w/o Condition: P_3PL_XML_ME_ODTH - S_HTTP</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>
Here, you see that both receivers are found.
MONI for ID
<Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION" />
- 
<Trace level="1" type="Timestamp">2007-02-26T20:06:49Z 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 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) GLR430 WMMBXY.WMMBID01</Trace>
<Trace level="3" type="T">...create rule engine</Trace>
<Trace level="3" type="T">...call rule engine for Condition%CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p1:inventoryActivityOrInventoryStatus/inventoryDocumentType")% CE INVENTORY_STATUS</Trace>
<Trace level="2" type="T">......extracting (new) for Extractor: XP /p1:inventoryActivityOrInventoryStatus/inventoryDocumentType</Trace>
<Trace level="2" type="T">......extracting values found: 0</Trace>
<Trace level="2" type="T">...invalid InbIf: WMMBXY.WMMBID01</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) GLR430 WMMBXY.WMMBID01</Trace>
<Trace level="3" type="T">...call rule engine for Condition%CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p1:inventoryActivityOrInventoryStatus/inventoryDocumentType")% CE INVENTORY_ACTIVITY</Trace>
<Trace level="2" type="T">......extracting (new) for Extractor: XP /p1:inventoryActivityOrInventoryStatus/inventoryDocumentType</Trace>
<Trace level="2" type="T">......extracting values found: 0</Trace>
<Trace level="2" type="T">...invalid InbIf: WMMBXY.WMMBID01</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) GLR430 WMMBXY.WMMBID01</Trace>
<Trace level="3" type="T">...call rule engine for Condition%CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:receivingAdvice/receivingAdviceItemContainmentLineItem/purchaseOrder/documentReference/uniqueCreatorIdentification")% EX</Trace>
<Trace level="2" type="T">......extracting (new) for Extractor: XP /p2:receivingAdvice/receivingAdviceItemContainmentLineItem/purchaseOrder/documentReference/uniqueCreatorIdentification</Trace>
<Trace level="2" type="T">......extracting values found: 2</Trace>
<Trace level="2" type="T">...valid InbIf with Condition: WMMBXY.WMMBID01</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) GLR430 WMMBXY.WMMBID01</Trace>
<Trace level="3" type="T">...call rule engine for Condition%CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:receivingAdvice/carrier/additionalPartyIdentification/additionalPartyIdentificationValue")% CE SHUTTLE</Trace>
<Trace level="2" type="T">......extracting (new) for Extractor: XP /p2:receivingAdvice/carrier/additionalPartyIdentification/additionalPartyIdentificationValue</Trace>
<Trace level="2" type="T">......extracting values found: 1</Trace>
<Trace level="2" type="T">...valid InbIf with Condition: WMMBXY.WMMBID01</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 = 002</Trace>
<Trace level="3" type="T">Message version 002</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="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="3" type="T">Persisting message Status = 014</Trace>
<Trace level="3" type="T">Message version 003</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</SAP:Trace>
Here, you see that the ID runs for the first receiver. It hits an error because two conditions on the ID for the first receiver are satisfied. However, it then stops rather than allow the processing for the other receiver to continue.
Any ideas? Thx, Duncan

Error in Trace Level: could not create BPE proxy for message, no XML objec

Hi
We are doing a scenario of File to RFC using BPM and I am getting this errror in Tcode SXMB_MONI.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<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="BPE_ADAPTER">UNKNOWN_MESSAGE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No object type found for this message; check the activation of the corresponding process</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
And getting this error in Trace level
could not create BPE proxy for message, no XML object definition found for message EB32BB50610A11DC9648001321CB837D
Why this error occurs?
What could be in error?
Thanks in advance
Regards
Sami Qureshi

Hi Sami,
Check if thse threads can help u,
Error in BPE Adapter
BPM - BPE_ADAPTER errors
BPE Adapter Error
Exeception during execution error
***********Reward points if helpfull************

Sbtio.log and trace levels

Hi all,
we're using Tivoli (TSM) with RMAN and I want to log error messages to USER_DUMP_DEST/sbtio.log . The log is there but always empty, even when there is a trace file stating there should be messages in it.
RMAN documentation says that sbtio.log must be configured with TSM. This does not seem to be true: I found that you can set a trace via ALLOCATE CHANNEL .... TRACE <integer>. I did NOT find anything in the RMAN documentation on this topic.
Can anyone enlighten me? What trace levels are there, what do I do to just get the errors dumped to the log? Any hints appreciated.
Thanks, Susanne

The 'details' can' tbe set to be more specific.
MAX_DUMP_FILE_SIZE specifies the maximum size of trace files (excluding the
alert file). Change this limit if you are concerned that trace files may use too much
space.
A numerical value for MAX_DUMP_FILE_SIZE specifies the maximum size in
operating system blocks.
A number followed by a K or M suffix specifies the file size in kilobytes or
megabytes.
The special value string UNLIMITED means that there is no upper limit on trace
file size. Thus, dump files can be as large as the operating system permits.
See Also:
Oracle9i Database Performance Tuning Guide and Reference for
more information on setting this parameter
Your operating system-specific Oracle documentation for the
default value and range of values
Parameter type String
Syntax MAX_DUMP_FILE_SIZE = {integer [K | M] |
UNLIMITED}
Default value UNLIMITED
Parameter class Dynamic: ALTER SESSION, ALTER SYSTEM
Range of values 0 to unlimited, or UNLIMITED
See Also: Oracle9i Database Administrators Guide and Oracle9i
Database Performance Tuning Guide and Reference for more
information on setting this parameter

JAXB anonymous complex types and inner interfaces

When JAXB generates interfaces/classes for a schema with nested anonymous complex types, it nests the resultant interfaces/classes. Is there any way to force JAXB to put these nested interfaces/classes at the top level of the package instead?
Note that if I specify a <class> binding, it changes the name of the inner interface/class, but doesn't change the fact that it's nested. It is my understanding that in JAXB Beta specifying a <class> binding for an anonymous complexType would in fact push it to the top level. Was this a bug, or is it a feature missing from 1.0, or am I misinformed about JAXB Beta?
I realize that scope-wise it makes sense to generate nested anonymous complex types as inner classes, however it leads to highly unreadable code when dealing with deeply nested structures. I'm hoping someone knows of a way to workaround this issue without simply redefining the anonymous complex types as named complex types.
Thanks,
-Greg Merrill

According to sec 4.4 "By default if xml schema component for which java content interface is to be generated is scoped within a complex type then the java content interface should appear nested within the content interface representing the complex type. ".
So I doubt that worked with beta and you may have to represent this anonymous complex type as a named complex type to avoid the nesting.
Regards,
Bhakti

Unable to set trace level

Hello,
I have a problem with the trace level (by trace level I mean this one: http://java.sun.com/j2se/1.5.0/docs/guide/deployment/deployment-guide/tracing_logging.html) in the Java Console when deploying a Java Applet.
With "Next Generation Java Plugin" (JPI >= 1.6.0_10) disabled I am able to set a trace level (0-5) in the java console; if it is enabled I am not able to set a trace level. The Problem is: it seems all outputs written to the Java Console seem to be added to one string, so if there are many trace messages in the java console you'll get a OutOfMemoryException.
And to make things even better: with JPI 1.6U19 and U20 I am not even able to disable the "Next Generation Java Plugin" (well theoretically I am but it seems to ignore my settings).
Also adding Applet Parameters (-Djavaplugin.trace=false -Djavaplugin.trace.option=off) for setting tracelevels has no effect, I get trace messages for loading resources etc. in the java console (Stating "image loaded: jar:http://what.ever.else/some.jar!some.image").
I tested with various Java Plugins (1.6U17, U19 and U20) and various Browsers (IE6 and Firefox 3.5) on WinXP SP2 with no difference.
Does anybody have a clue how to turn off this tracing permanently as it fills up my heap?!?
cheers
Christian

Where exactely did you change the localisation to US and has this to be done on every client running the web interface or just the server it's running on?

To check who change the trace level

Hi All,
Can anyone please help me how can i get that who change the trace level in system, in our client lot of people have Sm50, St01, St05,ST12 and other trace transactions, and it become difficult to track down who is changing the traces level
people often change the trace level and forget, and it become difficult to track down the changes,
can someone help me how can i know that trace level are changed by which user id at what time
Thanks,
Dinesh

I cannot remember the exact names, but if you take look in those transactions (there are more than the ones you have listed..) then you will see a call to FM TH_CHANGE PARAMETER.
You will see the name of the dynamic profile (and the authority check in it against S_ADMI_FCD action ST0M etc...) there, or some checks performed before the function is called.
Then take a look in transaction TU02 for the history of the parameters...
Good luck,
Julius
ps: A popular error exists in transaction SMGW: Wanting to dynamically set the gateway logging via the Expert Functions menu, you might be tempted to increase the "Trace level"... This is the ST11 developer trace!!! Rather choose the Security sub menu and activate the gateway specific log there, otherwise your production system might have some performance problems from the developer trace (which is a different local topic of less interest for gateway security....).
Edited by: Julius Bussche on Nov 4, 2009 12:03 AM

How to launch Web administration service and set trace level for web dispac

Experts,
Can some one help on how to setup trace level for Web dispatcher? and how to launch web administration interface.
Thanks in advance.

Hi Sam,
You can launch the Web Dispatcher Interface through the follwing link:
http://host:port/sap/wdisp/admin
The Username & Password are created when the profile is run for the first time. The userid is ICMADM
This link points to the web disaptcher administration interface & its usage.
You can set the trace level once you login to the interface.
http://help.sap.com/saphelp_nw70/helpdata/en/4f/3bee29d9764e988bdeecdb4d484722/frameset.htm
Hope it is helpful.
Regards,
Abhishek

Trace level="1" type="T" -no interface action for sender or receiver found

Similar Messages

Maybe you are looking for