Idocs not reaching SAP R3 from XI

Hi All,
I have a File to IDOC scenario, in which i need to process a text file of size 1 Mega Byte. The file from Leagacy reached XI and this has to create 12000 idocs in target R3 system. I can see the idocs(12000) in the IDOC Adapter but these idocs have not reached R3.
In SM58 I see an entry for this with the status "Transaction Executing". This entry is pending since 3 days. This always results in "Time exceeded out", and Iam manually executing it with F6 but still the status shows "Transaction executing".
There are no entries in SMQ1 & SMQ2
I want to push these idocs to R3.
Any suggestions on this will be helpful
Regards,
Santosh

Santosh,
Use IDOC packaging as shown in Michal's blog
/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
Also, try increasing time out values
/people/michal.krawczyk2/blog/2006/06/08/xi-timeouts-timeouts-timeouts
Regards,
Jai Shankar

Similar Messages

IDOC is not reaching SAP from XI

Hi all,
The IDOC that I'm sending from XI is not reaching SAP.
I have tried all most all possibilies. In SXMB_MONI I'm able to see the IDOC gets created successfully (with no error).
I have re-checked the partner profile, SMQ1, Config etc.
Please help me to debug.
Thanks,
AJ.

AJ,
Check if you have a chequered flag on both sides of your message ibn SXMB_MONI?
Check the log of your TRFC in transaction SM58
gards,
Bhavesh
Message was edited by: Bhavesh Kantilal

MATMAS01 IDOC not reaching to SAP XI via report program.

Dear Experts,
WE are facing small challenge.
I searched on SDN on scenarios: IDOC not reaching to SAP XI. But could not find exact solution t oour scenario.
Problem:
MATMAS01 IDOC is not reaching to SAP XI via report program and is in status of 03 on SAP system. And there are not entries under SM58.
Under SAP XI system IDOC entry is not reflecting under IDX5 transaction, I tried to delete meta data of MATMAS01 thru IDX1 and uploaded again but still IDOC is not reaching to SAP XI.
The strange is that MATMS01 IDOC is reaching to XI via WE19 test tool. So PORT and RFC destination settings betweeen R3 and XI is also correct.
What could be the wrong ?
Thanks
Divyesh

When sending Idoc from R/3,
Settings at R/3
create one port at WE21,
Create Partner Profile for Outbound Message type in WE20.
settings at XI
Create one port in IDX1
Import Matadata in IDX2.
Create complete scenario in ESR for Idoc sender, also import IDoc in Imported Objects.
Check these settings & send test idoc using WE19.

Idocs not reaching new PI server

Hi Experts,
We have cloned SAP-PI 7.0 server and SAP-ISU server. Now idocs from from SAP-ISU is not reaching SAPI-PI at all.
Could you pls suggest how to anlayse and solve this problem?
Regards
Anupam

Hi,
Also Could you please try refreshing CACHE and also check the configuration of Integration server in sxmb_adm.please refer this similar threads below for reference.
Link: [https://forums.sme.sap.com/message.jspa?messageID=7947041]
Link: [https://forums.sdn.sap.com/thread.jspa?messageID=374227#374227]
Also check this [https://forums.sdn.sap.com/thread.jspa?threadID=1236817]
Regards,
Venkata S Pagolu

Idoc Not reaching PI even with 03 status

Hi everybody
There are many posts with similar question, but none of them could help me.
I am trying to post an IDOC from one SAP system 3.1 to SAP 6.0 through PI.
I added FIDCC1 to to my partner profile in BD64.
I am creating a invoice and clearing it through f-30 and using the details from the invoice i am trying to trigger an idoc through a program.
Three idocs are getting triggered
1.when i create invoice(f-22)-automatically
2.when I clear invoice (f-30)-automatically
3.When I execute my program
The first two IDOCS are reaching 6.0, but my third IDOC is not reaching. All have same port details and partner profile details.
*All have 03 status in we02 in 3.1*. I am not able to understand why those two are reaching and why the third is not reaching.
None of them are stuck in any queues.
My actual requirement is only the third IDOC to reach 6.0 and I do not even want the first two IDOCs to reach 6.0.
Pls help!
Thank you
Donny
Edited by: Donnesh on Dec 27, 2011 1:14 AM

Hi Friends,
Thanks for the suggestions.
I have checked with all the above provided suggestions.
But as I have clearly mentioned in the problem that other idocs are reaching well in XI from R3 using the same Port, Partner Profile and RFC.
The error is occuring only with only one idoc in which they have made certain changes (added new segments). I have imported the idoc in Design again and then did the mapping again with the changed idoc.
Before the changes I could receive the Idoc successfully in XI system. I don no what happened after the changes.
If it would have been an authorization problem then I guess the other idocs would not have reached the XI system as well.
I guess the problem is somewhere else..
Thanks in advance.

IDOCS not reaching XI (IDEX-GE Content)

If I send IDOCS from I/SU to XI no IDOC is reaching XI.
IDX5 doesn't show any incoming IDOC. There is no error neither in XI nor in the log viewer of Visual Administrator.
The Sender system says in WE02: Datatransfer to port ok.
I checked the port and its RFC: The correct RFC (the one to XI) is set and RFC is working (sm59: test connection is ok, Remote Login from I/SU to XI is working).
IDOCS from a second backend are visible in IDX5. This backend is configured like the first backend (same RFC).
Did anyone have a solution?
Thanks
Ralf

Hi,
These are the complete steps for IDoc communication, check if you have missed any one...
SAP XI
1) RFC Destination (SM59)
     a) Choose create.
     b) Specify the name of the RFC destination
     c) Select connection type as 3 and save
     d) In the technical settings tab enter the details SAP SID/URL and system number#.
     e) Enter the Gateway host as same details above SID/URL.
     f) Gateway service is 3300+system number#.
     g) In the Logon /Security tab, enter the client user & Password details of Destination system.
     h) Test the connection and remote logon.
2) Create Port (IDX1)
     a) Select create new button
     b) Enter the port name as SAP+SID (The starting char should be SAP)
     c) Enter the destination client.
     d) Enter the RFC Destination created in SAP R/3 towards other system.
     e) Save
3) Load Meta Data for IDOC (IDX2) a) Create new
     b) IDOC Message Type
     c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
     a) Choose create.
     b) Specify the name of the RFC destination
     c) Select connection type as 3 and save
     d) In the technical settings tab enter the details SAP SID/URL and system number#.
     e) Enter the Gateway host as same details above SID/URL.
     f) Gateway service is 3300+system number#.
     g) In the Logon /Security tab, enter the client user & Password details of Destination system.
     h) Test the connection and remote logon.
2) Create Port (We21)
     a) First Select Transactional RFC and then click create button
     b) Enter the destination port name as SAP+SID (The starting char should be SAP)
     c) Enter the destination client.
     d) Enter the RFC Destination created in SAP R/3 towards other system.
     e) Save
3) Create Partner Profile (WE20)
     a) Create New
     b) Create the Partner no. name as same the logical system name of the destination system.
     c) Select Partner type LS
     d) Enter details for Type: US/USER, Agent, and Lang.
     e) Click on the + button to select the message type.
     f) Select Partner no. and LS which ever create above.
     g) Select Message type
     h) Select Process code related to the Message type.
     I) save.
In SLD
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system
Name.
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
Check these steps
Regards
Vikas

Erro "Partner not reached" - web service from ABAP

Hi.
I wrote a a sample web service call from abap program from net.
But, when I executed, i am getting error 404 resource not found, partner not reached.."Connection request from (19/1132/0) to host: www.webservicex.net, service: 80 failed (NIEHOST_UNKNOWN)"..
Not sure if any settings need to be done before running this ABAP program..
Pl let me know how to proceed further.
Thanks & Regards
Krish

Hi,
You should check if your server has internet access, may be there is a proxy who block the access.
If you have a proxy you can configure your proxy settings via SMICM.
Regards, Gilles.

Could not stop SAP Server from SAP Management Console

I have a AS-JAVA Server.
I am trying to stop the SAP Server from the SAP Mananement console located in http:
Servername:50013
It asks me for a user id. I specify the Sidadm user id and the same pop up appear again
Please assist

I typed the password of SIDadm and still the popup comes asking me for password
The password i typed is corect

IDOC not reaching XI from SAP

Hi,
I am trying to fire IDOC (DEBMAS) from SAP to XI. The basic Idoc has been exxtended to add some new segments. The required configuration has been done on SAP and XI side(partner profile on SAP and IDX1/IDX2 on XI).
However whenever I fire this idoc from SAP, it shows that Idoc has been triggered but am not able to see the same in SXMB_MONI in XI.
Please let me know if you have any clues

Hi Anand,
The monitoring in SXMB_MONI can only inform u about integration engine.
SM58 errors occur if a RFC destination does not work.
Also what is the Status Text message you see in the SM58 ?
Anyways have a look at this Blog....
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
Regards,
Abhy
Message was edited by: Abhy Thomas

Idocs not reaching XI from R/3

Hi ,
There are two company codes defined in the R/3 system. The idocs are successfully generated and sent to the port from both the company code, status is successful in we02. But the Idocs from only one company code is received in XI and the idocs from the other company code is missing in XI .
Can anyone help me debug this issue.
Regards,
Sneha

did you check the SM58 traces? if anything might have gone wrong the entries there should mostly point out the issue.
Also confirm on your configurations esp. the user id and pwd and other parameters of the RFC destination.
Ref:
Configuration steps required for posting idoc's(XI) -
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
ALE configuration for pushing idocs from SAP to XI -
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi

IDOC not reaching destination system

Hello,
I am trying to send DOCMAS type IDOC from one SAP sys to another SAP sys.The IDOC has the status 03 (The IDoc was sent to an SAP system or an external program via a transactional RFC) but i dont see the IDOC in the target sys.
Please let me know what could have gone wrong.
Thanks,
Rakesh.

Hello Rakesh More ,
First let us know how you corrected the previous error???. What was wrong?
Then talk about the next issue.
If you maintain properly the Inbound IDOC partner profile this error should not come. Make sure you have the below things set-up properly:-
1) In the inbound IDOC in the destination system there should be a partner receiver in the IDOC control data. Make sure you have maintained the partner profile for that partner and for the partner type as well.
2) For the partner make sure you have maintained the proper inbound mesaage type and process code properly.
Thanks,
Greetson
Edited by: Greetson Shunmugasundaram on Aug 1, 2011 9:47 PM

IDOCS not reaching XI

Dear all,
I found a peculiar issue. A set idocs are being posted from SAP to XI.
Always the last IDOC in that set doesn't reach XI. But the status of that IDOC in we02 is 03.
I've even checked for SM58 in SAP, it also clear.
At XI, everything is fine, all the IDOCs reach but only the last IDOC doesn't reach. We have checked in smq2 and idx5, there are no blockages.
This last idoc has some critical data, cases where in it doesn't reach xi, the whole interface may fail.
If any one has faced a similar issue, kindly provide your inputs to solve the same.
Thanks in advance,
Younus

It is weird problem.
What i can suggest is, reload the IDOC Meta Data in XI using IDX2 & refresh the cache because I don't see other problems since you are able to send IDOCs to XI the problem comes only with last IDOC.
Regards,
Sarvesh

IDOC -- File:(R/3-- XI) : Idocs not reaching XI. Where to check for error

Hi,
I have completed the config for IDOC to XI (R/3-->XI) scenario based on various weblogs available on Sdn.
For testing, I am using we19 to trigger the outbound idoc from R/3. But when I look in IDX5 in XI or message monitor, I do not see any message or IDOC there. Even SXMB_MONI in XI does not have any message.
What could be the potential issue for this behaviour. Is there a way where I could debug or any steps that could tell me where to look for the error.
So far only odd behaviour I have observed is:
When in WE19 I trigger the IDOC for outbound processing, XI login screen pops up, where I need to enter password. Once I click enter the screen disappears and the message, IDOC sucessfully sent to external system/Port appears.
Appreciate your help.
Thanks
Shirin

Hi,
I checked SM58 and teher indeed are errors saying
"Name or Password is incorrect (repeat logon) "
So which connection is having incorrect password in SM59?
I checked and I have a working RFC connection (TYpe 3) in SM59 for XI.
Just to add TCP/IP connection(Type T) has 2 connections not working. They are LCRSAPRFC and SAPSLDAPI.
So what should be my next step in correcting this error as I am not sure which RFC connection user-id is responsible for SM58 errors.
Any feedback is welcome.
Thanks
Shirin

IDOC to xi problem IDOC not reaching xi

Dear all,
this is a case of IDOC scenario in development server.
we are sending a IDOC form R/3 system to xi system,and when we are checking it with Tcode sm58 ,it is coming as status 12 .
but when we try ti view this IDOC in xi system with Tcode IDX5 nothing is coming. we check every thing like port configuration in IDX1 and IDX 2.
we checked the code also which is used to trigger Idoc from R/3 System. every thing is fine thete also.
please give some input regarding this problem.
thanks and regards,
Navneet Sumit

HI,
Check whether u have done the proper configuration at the R3 end.
ALE configuration for pushing idocs from SAP to XI
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
Thnx
Chirag

ASN not reached SAP R/3

Hi All,
ASN (Advance Shipment Notification) was sent from SUS system to R/3 ,in R/3 idoc is not getting posted and in WE02
we are getting Idoc error with status 51 " Document already being processed" . Please help me in solve this issue.
Thanks and regards
Uma

Note 1258623 - ME185/ME187: Authorization problem during PO determination
After the second Purchase Order determination during inbound delivery processing you get the error message ME185: Document & already being processed, but no user really blocks this PO
Other terms
ME 185, ME187, ME 187, BORGR, EXITFLAG
Reason and Prerequisites
The reason for this problem is due to a program error.
This error will appear only for the users who do not have the necessary authorization to handle in a PO related plant any purchase order changes (create an inbound delivery is such a change) and PO determination is used for several items.
for us, one user recieved goods from srm via confirmation.and this was not posted that time doc went error state. again he posted new confirmtion. it went fine..
check rfcuser authorisation . for eg, it happened to me there was communication eror between both system. but idoc remain in error in status. i created a new
Solution

Idocs not reaching SAP R3 from XI

Similar Messages

Maybe you are looking for