What are reasons for TRDIR-UDAT getting updated apart from importing a transport request?

[BaerbelWinkler]

Hi All!

I already searched the forums but wasn't able to find a good explanation for what I'm seeing in our NW7.50 EHP8 system:

• A SAP Standard include (e.g. MF02DO00) shows a recent date of 2024-09-04 in TRDIR-UDAT
• TRDIR-SDATE and TRDIR-IDATE also show 2024-09-04
• When looking at versioning, the last transport is actually from some SPAU activitity associated with an SPS-Upgrade from 2 years ago which was imported on 2022-12-03

I'm wondering if this apparent discrepancy might be due to e.g. some of the many DDIC-objects used in the code getting imported via a transport request (which would fit the dates timing-wise), necessitating a re-generation of the code and hence updating the dates in TRDIR. Is that a feasible explanation and if not, what else would be causing an update to these dates?

Thanks much for any feedback you might have!

Cheers

Bärbel

[Ryan-Crosby]

Any explicit enhancements active in that include? When I add one in our development environment that triggers updates in the repository data.

[BaerbelWinkler]

Hi Ryan,

Thanks for the suggestion!

I just checked but there don't seem to be any enhancements in the include or overall program SAPMF02D.

Update Nov 8: In another case, an imported change for our enhancement for SAPMV45A seems to have changed TRDIR-UDAT for the SAP-standard program. At least, I can identify transports getting imported fitting the dates for two recent changes.

Cheers

Bärbel