Unknown messages are in scheduled status in asxmb_moni in ECC

[Former Member]

Hi,

we have unknown messages piling up in scheduled status in sxmb_moni of ECC system. the messages say sender is ECC but it is not able to find destination. Not able track down where is this message originates. and we don't want this message to be piled up. and the queue names are XBTS000*.

any inputs are highly appreciated.

Thanks.

Prema

[former_member186851 · Accepted solution]

Hello Prema,

Your message is stuck in Queues, Go to SMQ2 and clear the queues.

[Former Member]

thanks Vadim, raguraman and Nitin.

yes seems like this is standard interface running.  this is was not the case earlier. it started few weeks ago.

how do I know where is this originating from?

and functional team doesn't know how these messages are generated.

[vadimklimov]

Hello Prema,

I would suggest firstly to go through a SAP standard recommendation described in a SAP Note 1317798 (see comments on this above).

If you are interested in identification of caller of this interface, then, assuming it runs quite often, you can figure out a user name in which context the interface is executed (can be retrieved from tx. SXMB_MONI / SXI_MONITOR > individual message display > section "Runtime" > element "SAP:User").

Having this information, you can perform a short ABAP trace collection session (tx. ST12) for that user and capture program that calls the interface. Precisely speaking, you can go through collected traces and search for occurrences of the corresponding proxy class, followed by checking upstream call hierarchy to figure out which program was initiating call of this proxy.

Another option is to analyse recent statistical records (tx. STAD) and focus your analysis on those which were executed by the identified user (you may also want to limit selection by application server host name - this information can also be retrieved from message display, section "Runtime" > element "SAP:Host"). In statistical records that capture outgoing proxy calls, you shall be able to see a section "WebService Records" which will contain a name of a called proxy class and method / operation. Looking into header of such statistical record, you will be able to find for which program / transaction it was created, and figure out what caused an interface call.

It is better to use both described approaches for short period of time for data collection and in periods when system is not heavily loaded since tracing puts additional workload to a system, and analysis of both collected traces and statistical records, even assuming proper filters by at least time period and user name are applied, will take some time.

Regards,

Vadim

[former_member186851]

Hello Prema,

It should be initiated from standard jobs or some codes.

Make sure that nothing is triggering those standard interfaces.

[Former Member]

thanks Vadim,

but still not able to track those messages.

the messages which are piling up are I think standard interfaces. where are these configured not sure.

attached pic has those interfaces.

[Former Member]

thanks raguram. as I replied to vadim, those are the standard interfaces. any idea where are those configured?

[Former Member]

Refer the thread and  comments by Adilson

[former_member186851]

Hello Prema,

Yes,They are.

Someone from ECC team should be able to help you.

[Former Member]

thanks for the replies.

we don't know the triggering point. that is the question. there are messages every minute, so we can not keep canceling them, it s not feasible.

yes I have the system details from sxmb_moni from ECC, and messages are from ECC.

there is no such interface in SAP PI. it is just in SAP ECC system with namespace http://sap.com/xi/APPL/Global2.. and I don't see the servervice interface:  PurchaseOrderChangeInformation_out  in that namespace.

so cancel of message or start/stop channel will not helpme as there are no such interfaces in PI.

[manoj_khavatkopp]

Hi Prema,

Search in ID part for Reciveer determination/ICO with this sender interface name PurchaseOrderChangeInformation_out .

if you still cant find it check whether these objects are deleted and change list is activated.

Br,

Manoj

[vadimklimov]

Hi Prema,

Most likely, the interface is triggered by a standard event of purchase order change of an ERP system. You can use BAdI PUR_SE_PO_INTERFACE_OUT_SELECT in ERP in order to switch on / off triggering standard outbound interfaces which are associated with this event, an interface PurchaseOrderChangedInformation_Out being one of them, and preventing unnecessary calls of unused interfaces for this event and generation of unwanted and unused messages like those you observe. You may have a look at a SAP Note 1317798 which provides details about usage of this BAdI and references a sample ABAP class that implements an example of this BAdI usage.

Regards,

Vadim

[former_member186851]

Hello Prerna,

The interface seems to be a standard one.

Check for the process and cancel those jobs which might running by mistake.

[nitindeshpande]

Hello Prema,

This is a standard interface, which triggers the messages when there is a change in Purchase order.

Please go through the message payload in Moni and take the purchase order number and give it to your functional team (MM/SRM team), they will let you know why these messages are being generated and they can stop it from their end. This would be the permanent fix for this issue.

If you are on Single-stack, then you can stop the Proxy channel used for this scenario. But this would not stop generating the messages in ECC, hence please go for the permanent fix.

If you don't want this Purchase order interface running, then ask your Functional team to deactivate the business function responsible for triggering these messages.

Regards,

Nitin

[Former Member]

Thank you all for the reply. in smq2 there are no failed messages. there are 10 queues with prefix XBTS000*  everything started with scheduled status.

and these messages are not intended..

and the sender system is our ECC system and I have interface name.  but we never wanted those messages to be sent out. the sender is ECC system and I see these messages in ECC system without any receiver and in scheduled status in sxmb_moni.

what do I do if the messages should not go out of ECC?

[former_member182412]

Hi Prema,

You need to identify where this interface is triggering and disable the interface, if you dont want to send it to anywhere you can cancel these messages.

Regards,

Praveen.

[former_member186851]

Hello Prerna,

Get the system details from SXMB_MONI.

get the configuration details using the same in ID and remove them,so that the messages wont flow.

Alternatively you can check for the receiver channel and stop the same.

[former_member182412]

Hi Prema,

If you check the main section of soap header then you will get some clue who is the sender and sender interface.

Regards,

Praveen.

[nitindeshpande]

Hello Prema,

As informed by Raghu, the messages are stuck in SMQ2. Just click on the queue name, it would take to the SMQ2 tcode and there you can see the particular reason for the messages being stuck.

May be the 1st message in the queue is failed due to some reason and hence other messages are in scheduled status.

Regards,

Nitin