on 07-24-2008 9:21 AM
In a particular XI scenario, IDOC is coming from a R/3, but due to some performance reason, we need to stop those IDOCs entering into XI,
i am not supposed to change the Configuration, or Design in Integration builder (due to some reason),
also, we cannot stop those IDOC from R/3 (due to some reason),
How can we stop these IDOCs flowing into XI,
is there any facility in IDOC adapter to filter those particular IDOCs,
pls advice
Dear Sudeep,
I'm not sure what exactly is your performance issue.
If you dont want specific IDocs send to XI from R3 you should remove it
from the Destribution model (BD64)
and\or from the partner profile (WE20).
best of all is to remove the action from the customization that initiats calls for th ALE output type.
consul your SAP R3 uisness pepole or your ALE specialist.
Nimrod.G
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sudeep,
As someone has already pointed out, IDOC Sender ADAPTER will not be there.
So, there is nothing you can do, without touching IR/ID or backend.
What is that stops you from stopping the idocs in backend?
There are multiple ways you can do that if you are ready to change settings in R/3.
Regards,
Ravi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
in runtime workbench --> component monitoring --> adapter engine --> communication channel monitoring --> choose the corresponding channel and stop.
in proper, if you have rights to make in changes in configuration, choose the channel which helps the flow for the same and make the status as inactive.
Regards,
Parvathy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sudeep,
As the IDoc sender is not using any adapter you cant stop it using adapter.
1. As it is using the RFC destination possinly you can lock the RFCUSER in R3 this stops the IDoc in SM58 of R3 itself but ensure that the other iDoc are not using this RFC destination via any port.
2. Try with the option Collect IDoc in the Outbound option for the iDoc in we20 od R3 system
Thanks
SaNv...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.