cancel
Showing results for 
Search instead for 
Did you mean: 

T51 - Replication Problem - Merep_deltaBO table

Former Member
0 Kudos

Hi All,

We are doing iniial replication for T51 SyncBOs for MAU 3.0 applicaion.

We have many entries in the Merep_DeltaBO table with R3Keys coming from the backend which are now in the Status 'P'.

We have looked into the replicator report - merep_replicator_start and that report is making the status as 'P' for all the entries in the Merep_DeltaBO table.

How are these entries supposed to get clear from Merep_DeltaBO table and go to Merep_207.

Thanks,

Ankur

Accepted Solutions (0)

Answers (2)

Answers (2)

former_member304703
Contributor
0 Kudos

Hi Ankur,

Records in merep_deltabo table can be in status "P" for two reasons:

1. records are locked when keys are processed be replicator job (temporary state)

2. if key processing resulted in error (permament state) for wahtever reason, for example, BAPI abend, BAPI returned records with duplicate primary keys

Records are moved from merep_deltabo to merep_207 in this manner:

when you configure system to supportT51 you execute a report Z_maintain_server_driven_cust on the middleware for each SD SyncBo. That create a record in table memsd_dep which will triger replicator job to process ZZZ amount of keys in merep_deltabo every XXX minutes (as you specified).

Cheers,

Larissa Limarova

Former Member
0 Kudos

Hi,

go to SM37 - have a look into the process. What is the report telling you - I guess the processes are stopped that start with "MEBDTMAM_XXX". The question is: if you open the spool for the item that had some runtime - hopefully there had been one with some runtime - and then click on the icon in column TYPE - what does it tel you there?

Usually the MEBDTMAM job starts, takes items from the table, gets the details from the backend - and then it stores the items in MEREP_207. Problems can be in the area of: Wrong name of RFC, wrog setup process,..... Look into your previous taks and check the document I mentioned - this should give you a fairly good idea about the errors.

Another issue: are you on the latest patch level and have you imported all necessary notes?

Regards,

Oliver