Conversation ID not specified - T51 Server Driven Replic MAM30_050

[Former Member]

Hi,

I switched the partner replication to server driven replication (T51). After successful configuration I started the RALM_ME_PART_FULL_DOWNLOAD_SD report for initial replication. This report generates in the middleware five jobs which run the MEREP_REPLICATOR_START with variant MAM30_050BE.

Inside the backend I have round about 500.000 partners and after replication 270.000 partners inside table MEREP_207, but 391.000 remain inside table MEREP_DELTABO.

I run the initial replication with log level 7 an got sometimes the log message:

 Z_MEREP_GEN_T51_____MAM30_050 has started for run number 0000055601 and runtime counter 1 
 Metadata reading was successful (SyncBO=MAM30_050, #=198)                                 
 Default values loaded successfully (SyncBO=MAM30_050, #=1)                          
Conversation ID not specified.                                               
Z_MEREP_GEN_T51_____MAM30_050 has finished for run number 0000055601 and runtime counter 1

Strange is that some keys of MEREP_DELTABO already exist in MEREP_207, after replication.

In SAPNote 711983 is described the Conversation ID identifies the Device/User/Application. But in moment of initial replication I don't have a device. The job is only running with my user and knows the application, but no device.

Why the MEREP_DELTABO isn't empty, after initial replication?

Thanks a lot,

Greetings

Andreas Dommes

[Former Member]

Hi Andreas,

Once we replicate from R/3 system, all records will come to MEREP_DELTABO and from there records should be pulled to MEREP_207(MiddlewareDB table).

So for this some Job is to be scheduled so..run the report in Middleware system

Z_MAINTAIN_SERVER_DRIVEN_CUST

This report creates entries in MEMSD_DEP for Server-Driven SyncBOs. This report will be replaced by a MI program to maintain the values.Entries in the keytable MEMSD_DEPTYPE will also be created if neccessary.

So once this done all the records are pulled to MEREP_207 middleware DB.

If still the problem persists:

Q) Records are not present in MEREP_207 even though they are present in MEREP_DELTABO?

A) Check MEREP_503 table whether any entry exists for the failed job.Replication process does not run until the job is removed from MEREP_503 table. This is applicable for only SP lower than SP 16.

Hope this is helpful.

Cheers,

Karthick