Synchronization problem

[Former Member]

Hello, I need some help.

I have instalation SAP NW2004 with backend SAP ERP 4.7 with PI_2004_1.

We try to use MAM 3.0 app, but there is no data after synchronization

(syncbo objects - status "waiting")

I can find on log transaction that is some problems with MEREP_ARECEIVER or MIAUTH objects.

Can someone help me ? MIAUTH imported and enabled...!

Thanks !

michal

LOGS :

Cannot start authority query for user because SyncBoDescriptor for MIAUTH is not available

MEREP_ARECEIVER has started for run number 0000000209 and runtime counter 1

Forced correction of XML document encoding from UTF-8 to sap*

Processing MBL_ID= 0000000001 Seq Number = 33

Receiver does not call handler (return code=4, reason=HANDLER Already Running)

MEREP_ARECEIVER has finished for run number 0000000209 and runtime counter 1

SyncBO ID I-Waiting

5

MAM30_001 4

MAM30_010 4

MAM30_016 4

MAM30_017 4

MAM30_018 4

MAM30_030 4

MAM30_031 4

MAM30_041 4

MAM30_050 4

MAM30_070 4

MAM30_090 4

MAM30_095 4

MIAUTH 8

YPMINV_001 4

[AjithC · Accepted solution]

Hi Michal,

The records are remaining in waiting status because the "MAX number of handlers" setting which is by default 5. So not more than 5 handlers will run at a time. This is a setting to prevent the server from overloading.

You can trigger the handler manually from merep_mon or much better schedule the report "merep_retry_bp" to run every XX minutes which automatically tries to process entries in I-waiting status.

Regards

Ajith

[Former Member]

ok

[AjithC]

If the problem is solved, please reward with points

Ajith

[Former Member]

Thanks to all.

Problem was on parameter = number of handlers. So perodic Job merep_retry_bp was good answer to solve a problem...

Michal

[former_member304703]

Hi Michal,

First, MIAUTH and YPMINV_001 are not standard SAP MAM SyncBos so it seems like your customer development problem.

As for the problem itself, your SyncBos are in "waiting" becuase at least one of them is "inactive".

From your problem description I think that one of your SyncBos description on the middelware does not match BAPI on the backend.

Run "BAPI Wrapper check" (merep_sbuilder) and fix the issues. Then activate SyncBo again.

Regards,

Larissa Limarova