Significance of SXMB_MONI in ECC

Hi Folks,
I am using Idoc to file scenario. I have used proxy communication also.
I have a small doubt in monitoring the messages on ECC side.
I can access SXMB_MONI on ECC (sender) side. But I just want to know the siginificance of using MONI in ECC.
Will it show the messages went to PI using Proxys or something else?
Thanks,
Shabbir.

As per my understanding, in MONI we can see the messages processed in Integration Engine.
So by using proxys we can establish the connection between Integration engine of ECC (Local Integration engine) and XI Integration engine.
So I think MONI on ECC will show the messages processed in the Integration engine locally, but I am not sure.
Thanks,
Shabbir.

Similar Messages

Can not see messages in SXMB_MONI of ECC

Hi Friends,
             Here I am facing some problem with SXMB_MONI of ECC. I am doing an XI upgrade from XI3.0 to PI 7.1.
when I am doing my interface upgrade I am unable to see messages in SXMB_MONI of ECC. As ECC is also got upgraded now BASIS is very confused about configuration.
             when I went through some blogs I came across some suggestions like configuration in SXMB_ADM. In ECC the integration engine configuration what I did is
               Role of Business System         : Application System.
               Corresponding Integ. Server    : dest://<HTTP DEST>
              One of my doubts:: Is <HTTP DEST> is the one which we are giving in XI/PI or the new one created for ECC. First BASIS set up <HTTP DEST> as the same one which was configured in PI. Then I went back to BASIS and tell them that ECC is having its own local Integration Engine, so we need to create <HTTP DEST> which connects to integration engine of ECC.
               Then they created one <HTTP DEST> for ECC. but when I am doing connection test, Http response is coming as 400 BAD HTTP Response :: protocol error. I have no idea why it is behaving like that.
               After when I go through some more blogs they are dealing with RFC destinations LCRSAPRFC and SAPSLDAPI. when I check it in ECC I didn't found RFC destination LCRSAPRFC but SAPSLDAPI is existing in ECC.
               more over some blogs deal with the configuration in Transaction SLDAPICUST. when I check it in ECC no configuration was done in SLDAPICUST.
               I already configured ENGINE_TYPE, IS_URL, LOGGING, LOGGING_PROPAGATION, LOGGING_SYNC under specific configuration data of SXMB_ADM of ECC.
               Please let me know what needs to be done and let me out of this confusion. As I am a PI developer I am unaware of all these configurations. expecting replies from gurus....
Regards,
DASARI

Hi Friends,
             Looking at some more blogs I got a doubt.
            Actually my scenario is File - XI - RFC.
            Now my doubt is whether we can see the messages which were going to ECC by RFC adapter ?
            Looking at a thread I got confused whether SXMB_MONI can capture messages only if they are coming from Proxy or IDOC . please clarify me.
Regards,
Dasari.

Outbound Message Missing from SXMB_MONI IN ECC

Dear PI Experts,
I have created IDOC to File scenario, But I am facing error when i am sending data from idoc using tcode we19 .
ERROR is whenever
I have checked tcode SXMB_MONI IN ECC server but XML message is not showing in this tcode ,whereas XML message is showing in tcode SXMB_MONI of PI server .
Please help me .

Hello Diptee ,
I have checked both case of IDOC and screenshots are referenced .
Case 1 .
Tcode BD10 ,
Case 2 .
Tcode WE19,

Sxmb_moni in ECC

Hi experts,
My sxmb_moni transaction in ECC doesn't select the messages sent from the ECC, it never worked yet...
Can you please help me make it work?
Thanks a lot,
Dmitry

As per my understanding, in MONI we can see the messages processed in Integration Engine.
So by using proxys we can establish the connection between Integration engine of ECC (Local Integration engine) and XI Integration engine.
So I think MONI on ECC will show the messages processed in the Integration engine locally, but I am not sure.
Thanks,
Shabbir.

Proxy Activation - ECC 6.0 to SAP PI system

Hi All,
Our envirnonment -
1) SAP ECC 6.0 ( R/3 system)
2) SAP PI ( R/3 system)
To establish communicate between SAP ECC 6.0 to SAP PI ( R/3 system using proxies )-
we have setup following steps on ECC 6.0 system-
1) Created a HTTP connection in the business system of type H.
Please let me know what is the path prefix we need to set.
2) Configuration Business system as local Integration Engine.
3) Connection between Business System and System Landscape Directory
Create RFC destination (TCP/IP) LCRSAPRFC and SAPSLDAPI for the SLD connection.
I have developed a sample interface to send data from SAP ECC --->PI --> File system ( Proxy to file interface)
When i run the report to call the proxy it is pushing the data on the integration engine of the ECC system.
How can i debug what is the problem is ? why the data is not getting pushed on PI system using proxy ?
How can i debug this ? Please let me know if i am missing any thing in proxy activation between ECC to PI system.
Regards,
Kishore

Hi ,
I have cross checked the activation steps.
I am able to create a interface proxy to File
SAP ECC R/3 system --- > SAP PI ---> File system
I have created a proxy on ECC R/3 system using SPROXY. when i trigger the proxy using a abap report the data is not getting pushed on to SAP PI system .
When i do a SXMB_MONI on ECC system it should call the integration server as out bound ... It is throwing a error message as mentioned below.
<?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>XIProtocol</SAP:Category>
<SAP:Code area="PARSER">ITEM_MISSING</SAP:Code>
<SAP:P1>Envelope</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>XML element Envelope missing in SOAP message header (SAP XI Extension)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please let me know how to proceed .
Cheers,
Nanda

Capturing Application Error log from SXMB_Moni

Hi,
I wanted to capture the error information from Application error log from ECC sxmb_moni and forward that as email alert.
We have already alert configuration in place with alert category using standard variables. Was wondering if I have to capture application error log from sxmb_moni what would be steps involved. Please let me know if anybody has worked on this and appreciate your help on this.
Sample Error message from sxmb_moni of ECC system
MT_Fault
Error in Application System
Detailed Information
Process Order invalid
Thanks
Selvam
Edited by: Selvam_muthu on Jun 23, 2011 5:40 PM

Hi Selvam,
As the exception is raised in ECC system, alert cannot be trigger, alert will get trigger when there is a error in PI system. To raise a email, write additional code in ECC to trigger the e-mail with proper error content

Editing Payload in SXMB_MONI

Hi All,
Is this possible to edit payload in SXMB_MONI.
I have already the following url which talks about editing payload from RWB - > Message monitoring.
https://www.sdn.sap.com/irj/scn/wiki?path=%3fpath=/display/xi/whole%252bpayload%252bto%252ba%252bxml%252bfield
Actually I am looking into the options of editing payload in SXMB_MONI of ECC.
Thanks in Advance for the help.
Best Regards
Ashok

Hi ,
am trying to edit only asynchronous message, here is the requirement that we have
Our OTC team has escalated a support issue with a call tag
return that could fail as it comes into SAP.
A "call tag" return is the result of a mis-shipment where the customer
either received damaged product or the wrong product. These returns
come in with not only the account but also the invoice number. The
return is referenced to the originating invoice and the credits are
created based on the prices and discounts that are on the invoice.   If
the invoice number on the return does not match an invoice for the
account, then the return will fail.
For some reason, the return fails in the ABAP Proxy layer of SAP ECC
with Application errors and does not provide the ability for the
business to repair the data.
Unfortunately, this failure occurs frequently in production today (1-2
a week - as many as 15) and we anticipate that we will continue to see
these failures with SAP. The invoice is being manually keyed at the
returns setup. Sometimes the error is caused by a keying mistake and
sometimes the documentation (call tag, invoice, packing list) is not
legible.
We also know that External Vendor cannot correct and resend the
return.   Their process not only creates the return for credit, but
also has to account for all of the inventory that is being sent for
destruction. Their quality steps lock the return down once it has been
sent to client for credit. Their system will not permit the return to
be corrected and resent.
We do, however, need to find a solution for the correction of these
failed returns that allows us to account for the return and create the
proper credit.
Returns (Order To Cash) team require ability to Edit the payload of
Asynchronous ABAP proxy messages in SAP ECC system, which are failed
due to Incorrect data with Message Status as "Application Error -
Manual Restart Possible".
For this the proposed solution is to Edit the Payload via SAP
XI's "Message Editor" in Runtime Work Bench -> Message Monitoring ->
Proxy Runtime of SAP ECC system.
The message editor is configured in SAP XI and ECC system with the
required roles and SAP Correction Notes.
Message Editor is NOT Working for messages with "Application Error -
Manual Restart Possible" status, while it is working as expected for
messages with "System Error - Manual Restart Possible" status.
Below Error Message is seen, while trying to edit the message with
Application Error in SAP ECC,
" Message editor can only be used for executable, asynchronous XI
messages with errors"
This issue in SAP XI's Message Editor needs to be resolved to complete
the testing of proposed solution in Sandbox systems and make a decision
on the solution to be used for this business requirement.

ABAP proxy scenario file - PI7.1- ECC NO_MAPPINGPROGRAM_FOUND

Hello Experts,
I have ABAP proxy scenario file -> PI7.1->ECC . I am getting an error for communication between PI and ECC system. the error is NO_MAPPINGPROGRAM_FOUND and pointing to operation mapping in the software component.
What i found in TCODE SXMB_MONI is 2 adaptor call one from one below the other out of which one is in error.
Also when a file is passed from the file server to the SAP PI I see 2 entries in SXMB_MONI for the same Payload one from source system to target system and one from target system to source system ( ie. from business component as sender and ECC as receiver system and one entry for ECC system as receiver and business system for file as receiver ) is this how it should be
one more thing i would like to specify is that my service interface is Point to point enabled . Is it happening because of that
Request you help on urgent basics
BR Heth

Hi,
1. in PI, by hazard, your Service Interface (SI) does not the mode "synchronous"?
2. or does this SI was declared firstly with "synchronous" mode and the proxy generated with this mode, and then you decided to put "Asynchronous"... without to regenerate the proxy in ECC?
If it's the case, in ECC, select your SI, do a right-click and regenarete the proxy.
3. for the 2nd message (returned by ECC to PI), have you seen the Payload content and SOAP Header?
Could you please also check the Pipeline (e.g CENTRAL, CENTRAL_BACK) ?
4. In SXMB_MONI of ECC, how many messages have you: one ? or two ?
Regards
Mickael

Call / trigger an ECC workflow step from PI ?

Hi,
For a flow "ext (file) -> PI -> ECC (workflow)", from PI, I need to run / execute / trigger () a workflow step in ECC, which already exist. I think that I can acheive this by creating an abap proxy in ECC in which I will call a Bapi or Method to run / execute / trigger () this workflow step. I don't know exactly how for the moment (in parallel I'm doing search about it), but that's not the matter.
before to waste time by searching in this way, what's the best solution to call an ECC workflow step from PI ?
Many thanks.
Mickael
(*) maybe I don't use the good terminology. Sorry.

hi Shabarish,
I'm confortable with web service, IDoc, RFC/bapi and abap proxy (and ...), but here, I prefer to use abap proxy (asynch + sxmb_moni in ecc) except if there is another better approach
else as in PI we have ccBPM, so a workflow , as in ECC we have also workflow , does my approach (abap proxy & call method) is the good one ? or is there a better way between these two workflow tools: PI + ECC ? like a standard "workflow module" or a workflow "connexion" ? (I fear I know the answer but I would prefer to be sure),
Note: I'm in PI 7.11 SP06 and ECC 6.0.
Regards.
Mickael

SRM-PI-ECC Integration issue

Hey All
There is some issue coming in Central Contact management scenario.
SRM 7.0
ECC 6.0 EHP 4
PI
*below is the error details we get in SXMB_MONI of SRM Sytem* <REMOVED BY MODERATOR>
<?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>XIProtocol</SAP:Category>
<SAP:Code area="PARSER">ITEM_UNEXPECTED</SAP:Code>
<SAP:P1><></SAP:P1>
<SAP:P2><Fault></SAP:P2>
<SAP:P3 />
<SAP:P4>ST: ST_XMS_MSGHDR30_SOAP_FAULT</SAP:P4>
<SAP:AdditionalText>System expected the element 'Fault'</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unexpected XML element <>; <Fault> was expected System expected the element 'Fault'</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks
Narender
Edited by: Prateek Raj Srivastava on Mar 5, 2011 4:49 PM

Thanks Buddy.
We have some progress. Now data passed from SRM to PI and now stucked in ECC. The XML file in SXMB_MONI in ECC, shows the staus "Transfer to External Application" and in ECC SMQ2 Queue XBQRCCR4400000066 stucked with status "STOP".
While dubugging the relevant we are getting the error '"COMMNICUTION_FAILURE"
And the Payload .xml file is as below :
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SOAP:Header>
- <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
<SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>
<SAP:MessageId>E04BAF35-8357-83F1-82AD-005056A12FA9</SAP:MessageId>
<SAP:TimeSent>2011-03-11T07:14:32Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Service>SS1CLNT200</SAP:Service>
<SAP:Interface namespace="" />
</SAP:Sender>
- <SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>ES1CLNT200</SAP:Service>
<SAP:Interface namespace="http://sap.com/xi/APPL/Global2">PurchasingContractSRMReplicationRequest_In</SAP:Interface>
</SAP:Receiver>
<SAP:Interface namespace="http://sap.com/xi/APPL/Global2">PurchasingContractSRMReplicationRequest_In</SAP:Interface>
</SAP:Main>
- <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:QualityOfService>ExactlyOnceInOrder</SAP:QualityOfService>
<SAP:QueueId>CCR4400000066</SAP:QueueId>
</SAP:ReliableMessaging>
- <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
- <SAP:Hop timeStamp="2011-03-11T07:14:32Z" wasRead="false">
<SAP:Engine type="BS">SS1CLNT200</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>E04BAF35-8357-83F1-82AD-005056A12FA9</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
- <SAP:Hop timeStamp="2011-03-11T07:14:32Z" wasRead="false">
<SAP:Engine type="IS">is.01.auvimel00s971</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>E04BAF35-8357-83F1-82AD-005056A12FA9</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
- <SAP:Hop timeStamp="2011-03-11T07:14:33Z" wasRead="false">
<SAP:Engine type="BS">ES1CLNT200</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>E04BAF35-8357-83F1-82AD-005056A12FA9</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
</SAP:HopList>
- <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Date>20110311</SAP:Date>
<SAP:Time>181433</SAP:Time>
<SAP:Host>AUVIMEL00S962</SAP:Host>
<SAP:SystemId>ES1</SAP:SystemId>
<SAP:SystemNr>00</SAP:SystemNr>
<SAP:OS>Windows NT</SAP:OS>
<SAP:DB>MSSQL</SAP:DB>
<SAP:Language />
<SAP:ProcStatus>003</SAP:ProcStatus>
<SAP:AdapterStatus>007</SAP:AdapterStatus>
<SAP:User>RFCUSER</SAP:User>
<SAP:TraceLevel>1</SAP:TraceLevel>
<SAP:LogSeqNbr>001</SAP:LogSeqNbr>
<SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
<SAP:PipelineIdInternal>SAP_RECEIVER</SAP:PipelineIdInternal>
<SAP:PipelineIdExternal>RECEIVER</SAP:PipelineIdExternal>
<SAP:PipelineElementId>1DC6B93B44BBA66BE10000000A1148F5</SAP:PipelineElementId>
<SAP:PipelineService>PLSRV_CALL_INBOUND_PROXY</SAP:PipelineService>
<SAP:QIdInternal>XBQRCCR4400000066</SAP:QIdInternal>
<SAP:CommitActor>X</SAP:CommitActor>
<SAP:SplitNumber>0</SAP:SplitNumber>
<SAP:NumberOfRetries>0</SAP:NumberOfRetries>
<SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
<SAP:TypeOfEngine client="200">SND_CENTR</SAP:TypeOfEngine>
<SAP:PlsrvExceptionCode />
<SAP:EOReferenceRuntime type="TID">AC1E020C11E44D79CBD9E0A7</SAP:EOReferenceRuntime>
<SAP:EOReferenceInbound type="TID" />
<SAP:EOReferenceOutbound type="MSGID">E04BAF35835783F182AD005056A12FA9</SAP:EOReferenceOutbound>
<SAP:MessageSizePayload>2929</SAP:MessageSizePayload>
<SAP:MessageSizeTotal>11916</SAP:MessageSizeTotal>
<SAP:PayloadSizeRequest>2929</SAP:PayloadSizeRequest>
<SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap>
<SAP:PayloadSizeResponse>258</SAP:PayloadSizeResponse>
<SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
<SAP:Reorganization>INI</SAP:Reorganization>
<SAP:AdapterInbound>IENGINE</SAP:AdapterInbound>
<SAP:AdapterOutbound>PROXY</SAP:AdapterOutbound>
<SAP:InterfaceAction>DEL</SAP:InterfaceAction>
<SAP:RandomNumber>57</SAP:RandomNumber>
<SAP:AckStatus>000</SAP:AckStatus>
<SAP:SkipReceiverDetermination />
</SAP:RunTime>
- <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:RunTimeItem>
<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
<SAP:Timestamp type="begin" host="AUVIMEL00S962">20110311071433.211</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
<SAP:Timestamp type="end" host="AUVIMEL00S962">20110311071433.256</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="begin" host="AUVIMEL00S962">20110311071433.257</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="end" host="AUVIMEL00S962">20110311071433.274</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
<SAP:Timestamp type="begin" host="AUVIMEL00S962">20110311071433.274</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
<SAP:Timestamp type="end" host="AUVIMEL00S962">20110311071433.387</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_CALL_INBOUND_PROXY</SAP:Name>
<SAP:Timestamp type="begin" host="AUVIMEL00S962">20110311071433.39</SAP:Timestamp>
</SAP:RunTimeItem>
</SAP:PerformanceHeader>
- <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:TraceLevel>Information</SAP:TraceLevel>
<SAP:Logging>Off</SAP:Logging>
</SAP:Diagnostic>
- <SAP:System xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Record namespace="http://www.sap.com/webas/712/soap/features/runtime/metering/" name="CallingType">SA</SAP:Record>
</SAP:System>
- <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: 4580</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 = ES1</Trace>
<Trace level="1" type="T">client = 200</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = RFCUSER</Trace>
<Trace level="1" type="Timestamp">2011-03-11T07:14:33Z AUSVIC</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 = E04BAF35835783F182AD005056A12FA9</Trace>
<Trace level="1" type="T">PLNAME = RECEIVER</Trace>
<Trace level="1" type="T">QOS = EOIO</Trace>
<Trace level="1" type="T">Queue-Id = CCR4400000066</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 : XBQRCCR4400000066</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBQRCCR4400000066</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 PurchasingContractSRMReplicationRequest_In</Trace>
<Trace level="1" type="T">select interface namespace http://sap.com/xi/APPL/Global2</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="T">Work Process ID: 2348</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 RECEIVER</Trace>
<Trace level="1" type="T">system-ID = ES1</Trace>
<Trace level="1" type="T">client = 200</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = RFCUSER</Trace>
<Trace level="1" type="Timestamp">2011-03-11T07:14:33Z AUSVIC</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 RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- 
- <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="Inbound Framework" />
</Trace>
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="T">ROLLBACK WORK requested by application</Trace>
</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Async processing completed OK.</Trace>
<Trace level="1" type="T">system-ID = ES1</Trace>
<Trace level="1" type="T">client = 200</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = RFCUSER</Trace>
<Trace level="1" type="Timestamp">2011-03-11T07:14:33Z AUSVIC</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>
</SOAP:Header>
- <SOAP:Body>
- <SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7">
- <SAP:Payload xlink:href="cid:payload-E04BAF31EF9CE7F189DE005056A10467sap.com">
<SAP:Name>MainDocument</SAP:Name>
<SAP:Description />
<SAP:Type>Application</SAP:Type>
</SAP:Payload>
</SAP:Manifest>
</SOAP:Body>
</SOAP:Envelope>
Can anyone suggest what can be issue ?
Thanks
NAP

PI to ECC via ABAP Proxy - Outbound Queue for HTTP

Dear Experts,
Is there any Outbound Queue for HTTP?
I've a interface scenario where the receiver is SAP ECC and the receiver adapter XI ABAP proxy. As I see in the communication channel the transport protocol used is HTTP. So I think could there be an outbound queue to manage HTTP connection when PI send the data to SAP ECC?
Just like when we are sending IDocs to ECC via tRFC, we could check if the IDoc has really been sent to ECC by checking in tcode SM58 (Outbound tRFC).
In case for ABAP Proxy via HTTP, is there any similar connection to SM58 (IDoc via tRFC)?
Thank you,
Suwandi C.

Hi Kandasami,
Thank you for the reply. I will check for it.
Hi Jens,
Yes, I mean somewhere after the SXMB_MONI in PI and before SXMB_MONI in ECC, is there any queue in between those two?
Thank you,
Suwandi C.

Message stucked at O/B queue in ECC

Dear All,
We have a scenario - Purchase Order Data posted from ECC to SRM system through PI using Proxy.
Problem is when the message is triggered from ECC, it was stucked up at O/B queue in ECC in MCEXO2 queue and the entry was not found in SXMB_MONI in ECC.
Could you please suggest us resolution.
Thanks & Regards,
Soumya.

Dear All,
In SMQ1, select the Q, Unlock & Activate. When we click on activate system issues the message u201CLUWs in status NOSEND must be picked up by the application u2013Message No :: SR082 u201C.
What does that mean ? Can anybody suggest What are we missing ?
Regards,
Soumya.

Duplicate Message ID issue in case of Multi mapping (without BPM)

Hi Experts,
I am doing one sample Example for my requirement of converting the single source message data into the multiple Target messages.
for example, when sender system is sending the 5 sale order details into a single message in PI then my Inbound proxy class of ECC R/3 receiver system must get this sale orders separately, that means inbound proxy class method must be triggered separately for 5 sale orders from sender system. for achieving this, I have used the Multi mapping concept in ESR (without BPM).
This scenario is in Asynchronous mode.
The below screen shots give the details on what I have configures so far.
IN ESR
IN ID
IN SXMB_MONI of PI
IN SXMB_MONI of ECC R/3 Receiver system (Error in Processing)
due to this error, inbound Proxy class method is not being triggered for the single Sale order details as well,
please let me know how to tackle this duplicate message ID issue when we have multiple payloads to process in a single message.
please also let me know if is there any other workaround to fulfil this requirement.
Thank you,
Regards,
Jagesh

Hi Nunu,
Check the below blog for restrictions.
Multi-Mapping without BPM - Yes, it’s possible!
Restrictions
Messages that result from the split in a mapping-based message split are sent using one AE. So only adapters running on the AE are supported. In particular, this means that target IDOC message splits are not supported since the IDOC adapter is not part of the AE.
Regards,
Praveen.

Error in XI Message Processing

Hi
It's an SRM to ECC scenario through XI.
The standard content is already imported from Market place. I get a chequered flag from SXMB_MONI when I run the scenario. Which means all is fine from XI end. However, when we go to the ECC sytem, we see that there is an error. In SXMB_MONI of ECC I get this error
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">Application Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</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" />
I checked SXMB_ADM, and the current value of the paramter IS_URL contains port as 51000, shouldn't it be ABAP port? If the port is wrong how is it showing succes in XI, SXMB_MONI?
Also the Receiver com channel is XI adapter, so it should be a proxy. Is it because of any missing steps in ECC ?
Kindly give inputs
Regards

checked SXMB_ADM, and the current value of the paramter IS_URL contains port as 51000,
it should be the one used for your integration server....can you confirm from any of your basis team?
If the port is wrong how is it showing succes in XI, SXMB_MONI?
In my opinion the port need not be changed....port 8xxx was required to be used till 7.0
Is it because of any missing steps in ECC ?
did you test the proxy in the ECC system? there might be some issue with the data that you are trying to update using the proxy.

Mails/Alerts-triggered for messages stuck in queues and failed in moni

Hi,
I have two doubts.
1) Messages are getting stuck in smq2 of my ECC and PI system. I have to manually push them. Is there any mechanism in which we can get alerts/mails when messages get stuck in queues.
I have already gone through the blog /people/santhosh.kumarv/blog/2009/05/19/sap-xipi-alerts-for-queue-errors and I have implemented it in ECC system. But no mails were generated.
2)Is there any method in which I can get alerts/mails when a message fails in sxmb_moni of ECC system?
Thanks and regards,
Siji

Hi Sanjeev,
I made a report with the following code in it and executed it. So I think that should work even if the job for it is not scheduled. There were messages stuck in queue. But no alert was generated. I had also created alert category in ECC.
Thanks and regards,
Siji

Significance of SXMB_MONI in ECC

Similar Messages

Maybe you are looking for