Lost Transport Import History after the system refresh

[former_member160248]

Hi,

We forgot to take the backup of the TPALOG table before the system refresh. We refreshed our testing system from production system. Right now we donu2019t have the old import history for the testing system. We played with TPALOG table and TPALOGHDR to synchronize TPALOG table with ALOG* files. But we are not able to do that. I remember we had synchronized the TPALOG table with ALOG* files in the past. Please advise for any function/program to achieve this. Thanks.

Thanks.

Raj.

[former_member160248]

Hi Niraj,

Thanks for the reply.

Atlast we endup with writing a small ABAP program to populate the TPALOG table from the different ALOG* files .

Thanks.

Raj.

[former_member126060]

Hello Raj,

The mechanism behind the import history is that STMS will look in table TPALOGHDR to check if the time frame for which the import history is called, is between STARTTIME and ENDTIME.

If it is, it will use the entries in table TPALOG.

If not, it will read the ALOGxxxx files on /usr/sap/trans/log and update table TPALOG.

Modifying the ENDTIME in TPALOGHDR will force reading the ALOG files again and will update the internal table TPALOG. In most cases,using the first date you find in the ALOG file that covers the missing transport.

To reduce the possibility of competing accesses to the action log you can select a system-specific name. For this purpose, set the tp parameter ALLLOG in the STMS transport tool as global and with value:

ALLLOG = ALOG$(syear)$(yweek).$(system)

This will create system dependant ALOG files like, ALOG0318.D01

It should be noted that : The import history in TMS is only available for periods after the last copy of a system. The reason for this is, that TMS needs some information about the ALOG files which are stored

in the database. During a database copy, this information is destroyed and there is no possibility to restore this data.

Best Regards

Niraj