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

Similar Messages

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

Inbound idoc failing to reach SAP system.

Hi All,
We are upgrading our SAP system from release 700 to 730. Post upgrade we have identified that idocs which are supposed to reach SAP as inbound are failing in Biz Talk with below message.
Error details: Microsoft.ServiceModel.Channels.Common.XmlReaderParsingException: The segment name is not valid for the IDOCTYP, Release, or CIMTYP. Segment name: E2EDT37003GRP IDOCTYP: SHPMNT03 Release: 700 CIMTYP: . Ensure that your message xml validates against the operation schema.
This happening for only one inbound idoc which is using SHPMNT03 idoc.Whereas other inbound idoc which is using /AFS/ORDERS05 idoc is reaching SAP without any issues. I am bit confused why this is happening for idoc SHPMNT03.
Please let me know your thoughts.
Thanks,
Gowrinath.

Hi Ramya,
Thanks for your response.
In Biz Talk schema is designed for 700 release idoc.Whereas our system is upgraded to 731 release.
Hotfix is for Biz Talk. Can't we implement any solution in SAP side.
Thanks,
Gowrinath.

Reg: IDoc is u0091pushedu0092 into SAP from the external EDI system

Iam facing one issue in our system for message type DESADV (inbound). please read through .
"When an IDoc is pushed in from the external EDI system & even though the inbound Partner Profile is set to immediate processing mode:
The IDoc stays in status 64 - 'IDoc ready to be transferred to application'. This assumes that the IDoc has not been processed yet and still needs to be processed with program RBDAPP01 (or via the process button in BD87).
We don't want to again run this program "RBDAPP01". What was the problem.
I appreciate ur help.

Hi Krishna,
In some other scenarios if an IDocs remains in status 64, it means that the processing within the IDoc engines did not reach its end, where the new status could be set. There are two principal reasons:
1. In the matching partner profile the processing is not set to "Trigger immediately"
2. The application that processes the IDoc abnormally ends with a fatal error (crashes). If this happened you will see a trace in the system log (ST22). In this case have the satellite system write the file to disk but you trigger the EDI_DATA_INCOMING. Then start EDI_DATA_INCOMING from SE37 manually and debug yourself through the individual steps. A good start would be to set a break-point in the application handling function (in your case: IDOC_INPUT_DESADV ).
If useful do reward.
Regards,
Adarsh Srivastava

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

Posting idocs in sequence in SAP from file (without BPM)

Hi,
I have a requirement of posting the TWO idocs from the single file. But I need to send the idocs in sequence. Can you anyone explain the process how we can ecomplish from XI without using BPM.

Hi,
you can ONLY do that if your ERP,R3 (IDOC receiver system) system
is based on WAS 6.40
the whole scenario is described step by step in my book:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Idocs are not reaching to midleware or external Vendor

Hi Everyone,
We are sending delivery forecast idocs through a customising transaction, the idoc status is 12 but it does not reached to midleware or external vendor. When we create a new idoc through test tool(WE19) by copying the above idoc(which was created by customising transaction), its reaching midleware and vendor. Could you please tell, whats going wrong with the idocs which were created through customising program/transaction.
Thanks in advance.
Thanks and Regards
Raghu

sorry, no ideas at the moment.
You are using the same IDoc (which is in Status 12) and process it with WE19 and it´s working ?
Go to your IDoc Monitor.
OPen both IDocs and go to the STATUS Information.
Open all Status Data and read through longtext and Details, maybe you can locate it there.

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 segment not reaching XI

Hi,
I have a peculiar problem where the values populated in an IDoc segment are not coming to XI, though the values are visible in the sender SAP system, they are not present in the IDoc XML generated in XI.
Please help if someone faced a similar problem.
Thanks
Pushpinder

Hi,
Check if problems are raised on Cache of Design side of your IB.
Environment - Cache Status Overview
Then "Clear Data Cache".
And try again.
Regards,
Giuseppe

Data not reaching SOA from B2B

Hi All,
i have configured a generic file listening channel. B2B is picking up the file succesfully and it is also getting processed succesfully without any error
But data is not getting read by the B2b adapter(configured in default mode) which i have configured in SOA layer neither i can see in the queue(IP_IN_Queue). if i undeploy the soa process then i am able to see the data in IP_IN_Queue.
Strangely, if instead of generic file channel, if i configure my trading partner to listen the data using MLLP over TCP. then data is getting read by SOA layer.
Now i have a couple of questions:
1. In B2b 11g, we have 4 queues, IP_IN_Queue, IP_OUT_Queue , B2B_IN_Queue, B2B_OUT_Queue. Now which of these are used by B2b to pass data to soa in default configuration.
2. Why in case of generic file listeing channel my SOA composite is not receiving the data from B2B.
Regards,
Saurav Singla

Hi Anuj,
I have checked the application message. Application message does not have any detail about the composite instance or any location where its dumping the data.
In diagnostic logs i can find the following error.
[oracle.soa.b2b.engine] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@466f92] [userId: <anonymous>] [ecid: 74f716a25b8ba015:-4fb641d9:130ae246230:-8000-00000000000043a5,0] [APP: soa-infra] Error -: B2B-50029: B2B runtime error: oracle.xml.parser.v2.XMLParseException: '=' missing in attribute.[[
 at oracle.tip.b2b.msgproc.MessageHandler.deliverMessageToFabric(MessageHandler.java:1588)
 at oracle.tip.b2b.msgproc.MessageHandler.doDeliverMessageToDestination(MessageHandler.java:629)
 at oracle.tip.b2b.msgproc.MessageHandler.deliverMessageToDestination(MessageHandler.java:246)
 at oracle.tip.b2b.msgproc.Request.putMsg(Request.java:690)
 at oracle.tip.b2b.msgproc.Request.continueRequest(Request.java:500)
 at oracle.tip.b2b.msgproc.Request.incomingRequest(Request.java:421)
 at oracle.tip.b2b.engine.Engine.processIncomingMessageImpl(Engine.java:2819)
 at oracle.tip.b2b.engine.Engine.processIncomingMessage(Engine.java:1660)
 at oracle.tip.b2b.engine.Engine.incomingContinueProcess(Engine.java:4047)
 at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:3687)
 at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:3160)
 at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:619)
 at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:220)
 at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
 at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
 at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
Caused by: oracle.xml.parser.v2.XMLParseException: '=' missing in attribute.
 at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:323)
 at oracle.xml.parser.v2.NonValidatingParser.parseAttrValue(NonValidatingParser.java:1664)
 at oracle.xml.parser.v2.NonValidatingParser.parseAttr(NonValidatingParser.java:1555)
 at oracle.xml.parser.v2.NonValidatingParser.parseAttributes(NonValidatingParser.java:1487)
 at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1328)
 at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:376)
 at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:322)
 at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:226)
 at oracle.xml.jaxp.JXDocumentBuilder.parse(JXDocumentBuilder.java:155)
 at oracle.tip.b2b.utility.XMLUtil.parseDocument(XMLUtil.java:130)
 at oracle.tip.b2b.utility.XMLUtil.parseDocument(XMLUtil.java:146)
 at oracle.tip.b2b.msgproc.MessageHandler.deliverMessageToFabric(MessageHandler.java:1190)
 ... 15 more
oracle.xml.parser.v2.XMLParseException: '=' missing in attribute.
 at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:323)
 at oracle.xml.parser.v2.NonValidatingParser.parseAttrValue(NonValidatingParser.java:1664)
 at oracle.xml.parser.v2.NonValidatingParser.parseAttr(NonValidatingParser.java:1555)
 at oracle.xml.parser.v2.NonValidatingParser.parseAttributes(NonValidatingParser.java:1487)
 at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1328)
 at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:376)
 at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:322)
 at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:226)
 at oracle.xml.jaxp.JXDocumentBuilder.parse(JXDocumentBuilder.java:155)
 at oracle.tip.b2b.utility.XMLUtil.parseDocument(XMLUtil.java:130)
 at oracle.tip.b2b.utility.XMLUtil.parseDocument(XMLUtil.java:146)
 at oracle.tip.b2b.msgproc.MessageHandler.deliverMessageToFabric(MessageHandler.java:1190)
 at oracle.tip.b2b.msgproc.MessageHandler.doDeliverMessageToDestination(MessageHandler.java:629)
 at oracle.tip.b2b.msgproc.MessageHandler.deliverMessageToDestination(MessageHandler.java:246)
 at oracle.tip.b2b.msgproc.Request.putMsg(Request.java:690)
 at oracle.tip.b2b.msgproc.Request.continueRequest(Request.java:500)
 at oracle.tip.b2b.msgproc.Request.incomingRequest(Request.java:421)
 at oracle.tip.b2b.engine.Engine.processIncomingMessageImpl(Engine.java:2819)
 at oracle.tip.b2b.engine.Engine.processIncomingMessage(Engine.java:1660)
 at oracle.tip.b2b.engine.Engine.incomingContinueProcess(Engine.java:4047)
 at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:3687)
 at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:3160)
 at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:619)
 at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:220)
 at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
 at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
 at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
Error -: B2B-50029: B2B runtime error: oracle.xml.parser.v2.XMLParseException: '=' missing in attribute.
 at oracle.tip.b2b.msgproc.MessageHandler.deliverMessageToFabric(MessageHandler.java:1588)
 at oracle.tip.b2b.msgproc.MessageHandler.doDeliverMessageToDestination(MessageHandler.java:629)
 at oracle.tip.b2b.msgproc.MessageHandler.deliverMessageToDestination(MessageHandler.java:246)
 at oracle.tip.b2b.msgproc.Request.putMsg(Request.java:690)
 at oracle.tip.b2b.msgproc.Request.continueRequest(Request.java:500)
 at oracle.tip.b2b.msgproc.Request.incomingRequest(Request.java:421)
 at oracle.tip.b2b.engine.Engine.processIncomingMessageImpl(Engine.java:2819)
 at oracle.tip.b2b.engine.Engine.processIncomingMessage(Engine.java:1660)
 at oracle.tip.b2b.engine.Engine.incomingContinueProcess(Engine.java:4047)
 at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:3687)
 at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:3160)
 at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:619)
 at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:220)
 at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
 at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
 at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
Caused by: oracle.xml.parser.v2.XMLParseException: '=' missing in attribute.
 at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:323)
 at oracle.xml.parser.v2.NonValidatingParser.parseAttrValue(NonValidatingParser.java:1664)
 at oracle.xml.parser.v2.NonValidatingParser.parseAttr(NonValidatingParser.java:1555)
 at oracle.xml.parser.v2.NonValidatingParser.parseAttributes(NonValidatingParser.java:1487)
 at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1328)
 at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:376)
 at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:322)
 at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:226)
 at oracle.xml.jaxp.JXDocumentBuilder.parse(JXDocumentBuilder.java:155)
 at oracle.tip.b2b.utility.XMLUtil.parseDocument(XMLUtil.java:130)
 at oracle.tip.b2b.utility.XMLUtil.parseDocument(XMLUtil.java:146)
 at oracle.tip.b2b.msgproc.MessageHandler.deliverMessageToFabric(MessageHandler.java:1190)
 ... 15 more
It looks like dat errro is coming while delivering message to fabric.
But i have no idea why this error is coming because with the same configuration and ecs files, when i am sending the data through MLLP, its working perfectly fine.

Notification not reaching SAP inbox

Hello All,
I have created a new workflow. Everything is working fine in Developement System.
I transported this to Quality system.
Its showing workflow log is correct.But user is not receiving any notification in mail box.
Task is dialog step. Agent is General.
What can be the reason?

Quick test, in SWU3, use the WF System Verification. You can do as yourself and should be able to ad-hoc create / test as the user in question. This will do several things right out of the box. Test you agents, batch jobs, background / foreground steps, WF sub system is running correctly...
Also, run the ... darn. <forgot t-code>. The WF development testing t-code. Where you can do the tracing, testing agent assignment, etc en-mass. If you don't figure it out by moring, I will pop open an SAP cleint and forward along. It's cocktail hour! Tomorrow..
Rick Sample
p.s.
I think you need to check the Agent assignment on those tasks in each client. Client specific when making them General Task.

Can not reach internet from vlan on 3560 switch but can from switch

ISP provided me IP (207.70.170.42) and gateway address(207.70.170.41) connecting to their router( meto E).
I can ping outside the network when logged into the switch through telnet but not when connected through a pc on the vlan.
I can ping the IP address on port GI0/1 207.70.170.42 from the PC on vlan 99 (192.168.20.3).
What do I need to configure to get the VLAN to send traffic to the internet.
Tried ip route 0.0.0.0 0.0.0.0 207.70.170.41
Tried ip route 192.168.20.0 255.255.255.0 207.70.170.41
Tried ip route 192.168.10.0 255.255.255.0 207.70.170.41

Hi @rbrewer02,
Are you doing NAT or PAT for private IP addresses? Remember that the ISP just see the public IP address that it gives to you (207.70.170.42 in your case).
You should configure NAT so that your private IP ranges get translated into your public IP address.
If you need help in configuring NAT just tell me.
Rgrds,
Martin, IT Specialist

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.

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.

IDOC is not reaching SAP from XI

Similar Messages

Maybe you are looking for