Synchronous Interace - Message trigger is not identified

[lnirmala]

Hi all,

We are having a synchronous interface in Production PI system where data flows between source application (SAP ECC) and target application(non-SAP system). The SAP users execeute certain transaction code to trigger data to SAP PI via proxy on real-time basis.

But we could see that on a particular day around 13 messages were triggered from SAP ECC without execution of assigned transaction code and data got processed to target application from SAP PI.

We are unable to find any log at SAP ECC end which will help us to find how these messages were triggered to SAP PI. Also these messages were processed to SAP PI within 30 seconds and we need to trace the trasaction/report/method which has triggered these proxy from SAP ECC end.

Could you please let me know if there is any possible way in which we can trace the origin of these messages. Also pls let me know if someone has faced similar issue for synchronous interface.

Thanks

Lekshmi

[iaki_vila]

Hi Lekshmi,

It is a really weird for sync scenario, for async is possible because is parameterizable to resend them.

The only way to follow the tracks is to have the monitoring in the sender system, you can enable the monitor sxmb_monitor as in PI ABAP stack. Depending your PI version you can have different trace logs, what is your PI version?.

Have the ABAPERs trace how many programs/module functions use that proxy?, in ABAP exists the where-used list button to know this.

Regards.

[lnirmala]

Hi Vila,

We could see all these 13 messages in tc sxmb_moni of SAP ECC system but we are unable to get more information on same.

Our PI version is SAP PI 7.31 dual stack . But since this issue occurred sometime back we dont have the messages in tc sxmb_moni of SAP PI as messages got deleted.

The proxy can be called from FI Business Transaction event(FM created for the call) or custom report.

We could not see which transaction or report triggered these messages to SAP PI.

Thanks

Lekshmi

[iaki_vila]

Hi Lekshmi,

At least in your ECC you can go to the table SXMSPMAST and to know the user, not the program.

Regards.

[lnirmala]

Hi Vila,

We will get the user from tc sxmb_moni of SAP ECC but that user didnt execute any report/tcode to tigger these messages to SAP PI.

Thanks

Lekshmi

[pvishnuvardan_reddy]

Hi Lekshmi,

Normally for proxy triggering, either we can go for tcode mechanism or batch job pointing to the report mechanism. The former one is a manual process while the later one is a automatic process.

So, can you please check with any ABAPer on this, how the report is being handled for the interface triggering.

Coming to the user part, if you see with which user id the message is getting triggered from sxmb_moni in ECC, then some one who might be using this id or the user himself is triggering the report. Please check with corresponding functional POC on this.

Regards

Vishnu

[lnirmala]

Hi Vishnu,

We have checked with the user but seems like he didnt execute the tcode or report which is used to trigger the proxy.

So I would like to know whether there is any log or table which will record the list of activities performed at SAP end during a particular time frame. May be this will lead us to the trigger that executed this proxy.

Thanks

Lekshmi

[iaki_vila]

Hi Lekshmi,

I don't know how to do exactly with a standard table, but you can enable the trace log of the tables here:

The you will have the program, user and time the table has been changed. You will can see it in the SCU3 transaction.

Regards.

[markangelo_dihiansan]

Hi Lekshmi,

In ECC, if you have enabled LOGGING_SYNC to 1, you should be able to see which user that triggered the proxy by going to sxi_monitor -> double-click the message -> SOAP Header -> Runtime -> look for <sap:user> (I think, can't confirm right now).

Aside from that, the abap proxy can be triggered manually in sproxy -> look for SWCV -> look for namespace -> service interface -> double click and then press f8 thrice.

Regards,

Mark