on 02-15-2008 6:57 AM
Hi all !
I have a scenario in which the IDoc has arrived at XI from an R/3.Now this Idoc is to go to another R/3.
On Idx 5 it shows me successful inbound and outbound transfer of IDocs.
But at the outbound it is not showing me the client of the R/3 system to which this idoc has gone.
I have a doubt that this idoc has not gone to the system which it should actually go to.
So how can I check to which system this idoc has gone
And how can i rectify and make this idoc go to the desired output R/3 system?
Also plz tell if Idocs can be transferred to and from non sap R/3 systems
Kindly reply
Thanx
Quick Checks for the errors:
1. Check out the Message Processing Status in XI- Transaction SXI_MONITOR
2. Check out the SM58 of XI System in case of any queue stuck
3. Check out the Receiving SAP System - in WE02 so that you can find the IDOC has got reached or not
4. Hope your configurations like Receiver determination and Agreement is right
5. Also check out the Receiver Business System is correctly configured i.e Client Name, Logical System Name etc in the SLD
Regd. Non SAP Systems , if you want to transfer the IDOC information to the non-SAP System, you can send the IDOC data in the File format. I.e this format may be xml, csv whatever..
so kind of IDOC>XI>File Scenario
otherway is also very much possible.
Hope this helps,
Rgds moorthy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI,
It is bit possible to transfer IDOC from even NonSAP systems (provided those should be certified prtner to use IDOC)
see below link
Please follow below steps to trace the IDOC,
Troubleshooting IDOC scenario
1. Start with checking the status in sm58 of sender R/3
Follow the steps
2. Try deleating the IDoc from IDX2 and refiring the same.
3. Check your RFC destination definition (the one pointing to your XI server) to confirm that it is of type '3' (R/3 system) and not 'T' (TCP/IP).
In your ID, in the Sender Business System --> Adapter Specific Identifiers, give the logical name for the business System pointing to the R3 system
4. Monitor the SM58 in R/3 for IDOC status.
5. Trouble shooting file to IDOC and IDOC to file
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/error%2bhandling%2bin%2bfile-idoc%2bscenario
Refer below links for indepth troubleshooting
Refer below steps
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
IDOC to File steps to be followed please verify your scenario with it
R3 system.
1. Create SM 59 RFC destination to XI,.
2. We21 - Create port to XI.
3. We 20 -- Maintain Partner Profile for the outbound Idoc.
XI SLD
1. Create technical system for R3 system
2. Create Business System for the Client of the R3 system.
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
These are the required steps for IDoc to File scenario...
In R3 (i.e., your IDES system)...
RFC dest to XI (sm59) - any name
Logical system (bd54) - any name
Port to XI (we21) - any name
Partner profile for the logical system (we20) - use Logical system name created in bd54
In XI...
RFC dest to R3 (sm59) -
Port to R3 (idx1) -
create metadata for the idoc (idx2)
In sld...
create business system for R3 with Logical system name as r3 sys.
In we19
and give in control record as
Sender : Port ; Partner
Receiver : Port = <Port created in WE21> ; Partner = <Partner created in we20>
see the below links
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
Also
/people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133
IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
thanks
Swarup
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Yes we can do idcos can transfer r/3 and non sap systems.
check u r receiver R/3 by using transaction code we05 is u r idoc is successfully posted or not.....
while creating u r port wht login details u given in RFC connection that r/3 will receive the message,.
if any concern reply
plz reward points
thanq
Edited by: krishnachitanya siddavattam on Feb 15, 2008 8:04 AM
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 |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.