on 12-16-2008 3:22 PM
Hi Friends,
Please can somebody explain why I am having to go into SRM transaction SMQ2 (qRFC monitor) to manually process any material or service masters that is required to be replicated between R/3 and SRM 5.0? I am not sure if this is correct but the steps below are carried out by our master data team:
1.Filters set in transaction R3AC1 (middleware adaptor), i.e. only replicate material type HAWA
2.Manually start initial load with transaction R3AS
3.Go to SRM transaction SMQ2 (qRFC monitor)
4.On the item, enter F7 (glasses icon) then followed by manually entering F6 (activate queue)
5.Hit refresh, refresh again and againu2026...sometimes followed by another F6
We have a background job setup for R3AS but these sometimes the jobs remain in the SMQ2 (qRFC monitor) queue and need to be manually processed again with the steps I have just outlined.
Thanks.
David
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
I have looked through these threads and have investigated transaction SMQR further.
Please can somebody clarify what settings need to be applied to this SRM screen for middleware queu R3A*?? Currently, SMQR shows the following settings and I suspect that this is the reason why we are having to manually activate the queu in SMQ2:
Scheduler Information
Scheduler Status : Inactv.
Last Update (Every 2 Minutes) : 15.01.2009 01:25:01
Name of AS Group (DEFAULT = All): DEFAULT
Number of Entries Displayed 2
Host ID : Prod_SRM_00
Number of Active Connections 0
Thanks.
David.
User | Count |
---|---|
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.