on 09-19-2009 9:26 PM
Hello,
I have a question on CIF queues.
Whenever there is an outage on APO or R/3 side we put a STOP to the R3 outbound CIF and APO inbound CIF.
This helps us process the queues faster when the system is brought back up again.
My question is what happen if we don't stop the CIF and instead deactivate the integration models before the outage and then activate the integration models after the outage?
Also what is the best approach to handle CIF queues when planning for Outage?
Thanks and Regards,
Sanju
Sanju,
Probably not a good idea to deactivate your transactional IMs. Any transactions that are executed in either system during the period of inactivation will not 'queue up', they will instead be lost. After this, the only way to recover them would be a reconciliation. Messy.
Whenever I prep for a scheduled outage, I stop the queues, as you are doing. Also a good idea to force the users off the systems.
Rgds,
DB49
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sanju,
?? I thought you said you were already performing these steps...
I don't know if there are transactions assigned, if you want you can research this on your own in SE84.
For scheduled outages, I have built jobs with steps that execute the programs. The programs are the same on both sides (R/3 & SCM). I don't bother with outbound, I lock inbound on both sides. You can choose to do whatever you want.
RSTRFCI1 RFC TEST: stop Inbound Queues
RSTRFCI3 RFC TEST: Restart Inbound Queue
RSTRFCQ1 RFC TEST: Stop Outbound Queue
RSTRFCQ3 RFC Test: Restart Outbound Queue
Here is some stuff that may help you better understand the process.
https://service.sap.com/sap/support/notes/717244
https://service.sap.com/~sapidb/011000358700000715082008E
Regards,
DB49
User | Count |
---|---|
11 | |
2 | |
1 | |
1 | |
1 | |
1 | |
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.