IFS App 10 IEE - End to end monitoring of transactions/Http calls

Hi Rohit,
perhaps you can use PURCHASE_REQ_LINE_TAB .DATE_ENTERED?

I tried a SELECT on table PURCHASE_REQ_LINE_TAB (copied into DWH on MS SQL Server)

select 
min(date_entered) , max(date_entered),
datediff(ss,min(date_entered) , max(date_entered)) as Diff
, count(*)
from
extr_IFS_PURCHASE_REQ_LINE_TAB
where order_no = 'P400001125'
Result:
2025-02-03 02:55:06.0000000    2025-02-03 02:55:14.0000000   8    96 

So creating this 96 ReqLines took 8 seconds.
Hmmm, must be an automatism.

Get this example by looking the follow:
select 
ORDER_NO, count(*)
from
extr_IFS_PURCHASE_REQ_LINE_TAB
group by order_no
order by count(*) desc

If - and it is a great IF - your peoble create PurchReqLines manually, 
you can measure the “Timestamp” (DATE_ENTERED) for the first Line and the last Line.

At least you can give it a try and see what are the DATEDIFFs (in seconds) 

In our DD = datadictionary we found the following Datefields.

Perhaps you will find more details there. (ROWVERSION?)
HTH 
CU
Michael

Hi Michael, thanks.

What we are looking for is to measure the end-to-end response time from the end-user perspective — specifically, the total time it takes for all HTTP calls to complete for a given action on a particular LU object.

I used Purchase Requisition as an example to explain the scenario. So, what we want 

When the user clicks the New/Save/Delete button
Start the stopwatch.
    HTTP requests are initiated to the IFS backend:
    HTTP Request 1
    HTTP Request 2
    HTTP Request 3
    ...
    ...
    Wait until all HTTP requests are completed and their responses are received.
Stop the stopwatch.

Measure the response time.