Timestamp in SRT_MONI Reflecting When Message Was First Sent Outbound

[ybuc]

Good afternoon,

I'm working with data in SRT_MONI and struggling to understand what is the exact field that identifies the moment in which the message is sent out bound.

What is the field that is giving me this information?
Or is there a way I can have that time by adding performance data to 

CREATED_TS

?

[OwenLiu]

Are you using Public Cloud? If not, please change tag accordingly.

[ybuc]

I'm not using Public Cloud - we use S4Hana ERP and we are on Azure.(Pacemaker Cluster).
I'm so new to SAP Community that I don't even know which tag you are referencing.
Maybe you can introduce me.
The scope of my question on a wider scale is to understand if a message can be tracked end to end from SRT_MONI to CPI to the next hop.
I see capability in the data but the timestamps I have do not match. Hence my question.

[OwenLiu]

I changed the tags accordingly.

[DominikTylczyn]

Hello @ybuc 

I think that's Execution Date and Execution Time fields. There is also the UTC timestamp at last change field that combines date and time together.

Best regards

Dominik Tylczynski

[ybuc]

Hello Dominik,

I hope you're doing well.

Could you please clarify what you mean by "Execution Date & Time"? Are you referring to the technical fields CHANGED_DATE and CHANGED_TIME in SRT_MONI?

As part of my analysis of the data exchange between the S/4 system (SRT_MONI) and CPI, I’ve observed that the CHANGE_TS field in SRT_MONI generally appears after the log_start time of the corresponding CPI message. This leads to a paradox where the message seems to be registered in CPI before it was actually sent from SRT_MONI.

Therefore, I would like to ask: Which field accurately indicates the outbound timestamp of a message leaving SRT_MONI?

In the attached screenshot, I’ve highlighted in red the same tracked object IDs (Sales Order ID + Transaction ID), first as seen in S/4 (top) and then in CPI (bottom). In blue, I’ve highlighted the timestamps showing this paradox:

• 2025-04-22T12:48:47.810Z → First step: S/4 – Message delivered

• 2025-04-22T10:48:47.781Z → Second step: CPI – Message processing started

Basically CPI as seen the message from S4 0,03 seconds (30ms) before change_ts value written in SRT_MONI.

Looking forward to your insights on this.

Best regards,

[DominikTylczyn]

Hello @ybuc 

You have asked about outbound messages in SRT_MONI. Here is what I see for them in SRT_MONI and I meant the highlighted fields:

What you are seeing might not be a paradox after all. I guess it is due to message processing time in CPI - it is fast, nevertheless it is not instantaneous, it does take time:

1. A message is actually received by CPI
2. A CPI integration flow is executed - the message is parsed, mapped, etc.
3. The message is persisted or pushed to the receiving system.
4. The message processing acknowledgment is pushed back to S/4. This updates the message status in S/4 and effectively changes the message.

All that happens fast and synchronously. I guess your timestamp 2025-04-22T10:48:47.781Z comes from step 1 or 2 and your timestamp 2025-04-22T12:48:47.810Z from step 4. Even though the SRT_MONI fields are labeled execution date/time, I think they are really last change date/time.

Best regards

Dominik Tylczynski

[ybuc]

As you are describing it it make a lot of sense! And Actually I truly thank you for this insight that you are sharing.
But then this leads me back to my original question: Which field accurately indicates the outbound timestamp of a message leaving SRT_MONI?

What I'm thinking is that I'll need to use create_ts as technical field giving the timestamp of the message even thought it doesn't really mean that the message was first sent outbound for delivery at that time.

Regards

[DominikTylczyn]

Hello @ybuc 

Given the synchronous nature of message processing, it can be argued that a message truly leaves SRT_MONI once it is fully processed by CPI, i.e. once step 4 is done. Before that the message is still owned by SRT_MONI or rather S/4 side - if message processing fails, the error handling is S/4 responsibility not CPI's. Therefore the execution date/time fields or last change date/time fields give you the correct timestamp of when the message truly left SRT_MONI.

I don't think you can get in SRT_MONI a timestamp when a message processing started in CPI.

Best regards

Dominik Tylczynski

[ybuc]

You latest comment is very clear and brings also more clarity on what should be my expectation from this technology. Although keep in mind I'm not asking "SRT_MONI a timestamp when a message processing started in CPI" I'm asking for "SRT_MONI a timestamp when a message leave outbound from S4 for the first time (regardless of CPI answering or not)". And probably this is not available.

Thank you again for sharing the details you gave me an understanding that I had not reached previously on how SRT_MONI and S4 is handling the communication.
May I ask you if there is an official document from SAP which breaks down the communication stream in relation to SRT_MONI?

I have made searches but I found difficult to orientate my self in SAP documentation.
I will not insist anymore on this topic, as I understand the limits, and accept your latest answer.
Regards

[DominikTylczyn]

Hello @ybuc 

Unfortunately, I've never seen any more detailed technical documentation of that communication. What I shared here is my understanding, it is not coming from any documentation.

Best regards

Dominik Tylczynski