cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Error in SLT data replication DMC_RT_MSG229 - Cannot update logging table in sender system

Erick_Grilo23
Explorer
0 Kudos
227

Hello Experts,

I am facing an odd issue in a SLT replication landscape which works as following:

Origin System                                                        Central System                            Target System
SAP ECC (version 617, SP 0013) ->  SLT  ( DMIS 2018_1_752, SP 0012) -> HANA DB

Up to last week, the replication of a couple of Z tables was working just fine.

However, it has come to my attention that yesterday the replication started to fail with the following error:

Cannot update logging table in sender system (conversion object Z<z_table_name>)

Message no. DMC_RT_MSG229

 

I have checked the logs, and this happens forall the entries that the replication job runs through (DMC_MT_STARTER_BATCH).

Erick_Grilo23_1-1759981323504.png

 

I noticed that the logging table exists in SE14 in the source system, and looks fine but not in the ABAP DDIC (i.e., not in SE11 transaction / TADIR table).

I can see that in SLT, the logging tables are setup (LTRC -> Expert Function -> Display Table Information)

Erick_Grilo23_0-1759980687871.png

I found out that note 3438605 seems to solve it, but it is not applicable in the system version). I wanted to check if there could be another cause for this issue, and it looks like the absence of the the TADIR entry for the logging table is the issue, although dropping and recreating the objects seemed to have no effect.

Any guidance is greatly appreciated.

Thanks,

Erick Grilo.

 

 

Accepted Solutions (0)

Answers (1)

Answers (1)

Erick_Grilo23
Explorer
0 Kudos

Well it turns out that the problem indeed started after a refresh. We had to open an SSO with SAP to repair some process, and follow the guide in SAP Note 3438605, mainly steps 2.1.1 -> 2.1.2 -> 2.1.3 -> 2.4.5.2 -> 2.4.5.5. The key is that this error only did go away after the transparent table for the logging table appears in TADIR, so if it's not there, this note might solve your problem

Thanks,

Erick Grilo