cancel
Showing results for 
Search instead for 
Did you mean: 

T51 - Trigger scheduling - How to do?

Former Member
0 Kudos

Hi,

I would like to change the trigger shedule for our SyncBO ZSRVPROC from default of 300 sec to 60 sec. Therefore I found the SAP Note 711983 - Using Server Driven Download SyncBO

========================

Feldname Feldwert

NAMESPACE (initial)

NAME DOR_MSRCM

VERSION 1.0

TYPE TRIGGER

TYPE_INDEX 0000000001

DEPENDENCY_NAME INTERVAL

DEPENDENCY_VALUE 60

-


NAMESPACE (initial)

NAME DOR_MSCRM

VERSION 1.0

TYPE TRIGGER

TYPE_INDEX 0000000001

DEPENDENCY_NAME SYNCBO

DEPENDENCY_VALUE ZSRVPROC

==========================

But if I calle the merep_deltatbo fm manually, the created job is still sheduled round about 5 minutes in the future. Has anyone an idea what's going wrong?

As I took a deeper look into the merep_deltabo fm I found something with T51SYNCBOCONFIG which I have to use for the package size configuration. So I tried the following with the same result:

========================

Feldname Feldwert

NAMESPACE (initial)

NAME T51SYNCBOCONFIG

VERSION 1.0

TYPE TRIGGER

TYPE_INDEX 0000000001

DEPENDENCY_NAME INTERVAL

DEPENDENCY_VALUE 60

-


NAMESPACE (initial)

NAME T51SYNCBOCONFIG

VERSION 1.0

TYPE TRIGGER

TYPE_INDEX 0000000001

DEPENDENCY_NAME SYNCBO

DEPENDENCY_VALUE ZSRVPROC

==========================

I am running MI 2.5 with SP 17 and all relevant SAP notes.

Thanx,

Kai

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos
Former Member
0 Kudos

Hi,

yes I checkt the MI Help...there is the link to the sap note. In the MI Help itself are only technical details about the package size configuration, but not about the trigger scheduling.

Greetings,

Kai

Former Member
0 Kudos

Hi,

I red the MI Help again and found out that you have to configure the intervall with the transaktion MI_MCD and not like the description in the sap note via the table MEMSD_DEP. So I added a value for the intervall and it is working fine.

Thanx,

Kai

Answers (2)

Answers (2)

raghavendra_sn
Explorer
0 Kudos

Hi ,

Using MI_MCD transaction would create an entry in MEMSD_DEP table .

It can done either ways -

1. using MI_MCD transaction

2. directly entering needed data in MEMSD_DEP table.

I need to ask few questions ?

How many background processes do u have ?

have u enabled parallel replication ?

Regards,

Raghu

raghavendra_sn
Explorer
0 Kudos

Hi ,

Using MI_MCD transaction would create an entry in MEMSD_DEP table .

It can done either ways -

1. using MI_MCD transaction

2. directly entering needed data in MEMSD_DEP table.

I need to ask few questions ?

How many background processes do u have ?

have u enabled parallel replication ?

Regards,

Raghu