Problem in IDOC Receiving on MII

Hi
I am using MII Version 12.1.4 Build(46). We have configured IDOC in SAP ECC, SAP Netviewer and in MII.
We are able to generate iDoc from ECC but we are not able to receive it on MII Message Monitor.

Manoj,
The underlying NW CE installation must also be at SP3 (minimum). Please check and let me know if you already have the update. The IDoc Listener configuration changed a bit from 12.0 to 12.1 so there may be some other modifications needed.
Regards,
Mike

Similar Messages

Performance problem in IDoc receive (DELFOR01)

Hi,
I have serious problems in receive of Idoc Delfor01 (IDOC_INPUT_DELINS). We receive more than 3000 Idoc daily of this type and the process of then during all day....
One of more common error is foreing_lock of VBAK table. This error occurs in the Form beleg_sperren (line 459 from IDOC_INPUT_DELINS) when the process try enqueue one vbeln entrie from VBAK (o think by the high number of Idoc received) and, the process waits a large time trying enqueue the table entry until the error...
When I analyze the IDOC_INPUT_DELINS i see a batch-input for the VA32 transaction (at line 528). I think if call a Bapi instead a Call Transaction have more performance... it´s right?
I would appreciate help with possible solutions to this problem.. Have a better mode to process large amount of these IDoc type? Or have other FM than IDOC_INPUT_DELINS with better performance???
Regards,

Not need immediatly, but a quickly possible... In WE20 if I choose the background program the process will executed* fastly than I choose Imediattly start?
*executed via schedule job of program RBDAPP01.
I stil reading the notes above..

Problems in IDOC receiver communication channel

Hi,
I am trying to build an interface to get data from 3rd party legacy system using JDBC and post the data into ECC using IDOCS. I have IDOC built in ECC, I am able to import the metadata in IDX2 after creating port in IDX1. But after building the whole interface, I dont see the IDOC receiver communication channel which has to post IDOCS in the ECC 6.0 system.
Please assist.
Rgds
Kishore

OK in that case, we are getting the following error in the Message monitoring:
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="OUTBINDING">CO_TXT_OUTBINDING_ERROR</SAP:Code>
<SAP:P1>-BS_AVN_TO_FILE_JDBCSERVER</SAP:P1>
<SAP:P2>-BS_WOAV_IDOC_SENDER,urn:sap-com:document:sap:idoc:messages.ZAVENTITY01.ZENTITY</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>No standard agreement found for , BS_AVN_TO_FILE_JDBCSERVER, , BS_WOAV_IDOC_SENDER, urn:sap-com:document:sap:idoc:messages, ZAVENTITY01.ZENTITY</SAP:AdditionalText>
<SAP:Stack>Problem occurred in receiver agreement for sender -BS_AVN_TO_FILE_JDBCSERVER to receiver -BS_WOAV_IDOC_SENDER,urn:sap-com:document:sap:idoc:messages.ZAVENTITY01.ZENTITY: No standard agreement found for , BS_AVN_TO_FILE_JDBCSERVER, , BS_WOAV_IDOC_SENDER, urn:sap-com:document:sap:idoc:messages, ZAVENTITY01.ZENTITY</SAP:Stack
Please check and assist.
Rgds
Kishore

A problem about IDOC Receiver

Hi, everybody.
This time, I'm developing a IDOC Receiver though the SAPIDocReceiver class. With the dotnet Connector manual from SAP, the receiver side on dotnet is easy to develop. But how to configure the SAP R/3 to send IDOC to the dotnet side, I can't find the clear steps in the manual.
So I searched some material about how to configure IDOC, and hope it will be useful to my work. But most of them mainly focus on how to configure a IDOC transformation between SAP system but not NON-SAP system.
So what I want to ask is IS there some difference with the two configuration, I mean the SAP to SAP one and the SAP to NON-SAP one. I guess the difference should be have. Are the necessary configure step like create a logic system, allocate logical systems to clients and so on also necessary under the NON-SAP case? I think some of the configure actions is different in this two case. Can anyone give me some clear steps or tell me where I can get them?
thanks to all.

Hi,
for testing purposes you can do the following:
(1) via SM59 create the RFC destination for your dotnet application
(2) via WE21 create a trfc-port pointing to the RFC destination created in (1)
(3) via SM30 maintain view V_TBDLS to create a new logical system for your dotnet application for example DOTNET (and maybe for the SAP client you are testing with - here the name could be for example <SID>CLNT<CLIENT>)
(4) via SCC4 assign the logical system to the SAP client (for example <SID>CLNT<CLIENT>) only if not already maintained.
(5) In WE20 create a partner profile for logical system created for the dotnet application in step (3)
(6) In WE20 add outbound parameters for the message type (for example MATMAS) and idoc type (MATMAS03) you want to send. As partner port use the trfc-port of step (2)
(7) In WE19 create an IDoc via basic type (the idoc type used in step (6), for example MATMAS03) and maintain the following fields in the control record EDIDC:
recipient port the port created in step (2)
recipient partner number the logical system name of the dotnet application created in (2)
recipient partner type'LS'
sender port SAP<SID>, where SID is the SAP system id
sender partner number the logical system name the SAP client maintained in step step (4)
sender partner type'LS'
message type the message type used in step (6), for example MATMAS
In the other segments E1* you can fill in whatever you like
Hit the push button "Standard outbound processing"
(8) you can check if the IDoc has been sucessfully created by BD87. If an error has occurred in the receiving application or there is any other error you can also see it here. Maybe the IDoc is not passed to the receiver, then you can process the IDoc also from here.
This is how you can create your test environment. If you want to get the IDoc created form the SAP application it depends on the application how to do that!
Best regards,
Willy

Problem in Idoc Receiver

Hi guys.
I have a FILE to IDOC scenario.
The original idoc have only 1 ocurrence but I've changed the ocurrence with an external definition based on idoc xsd with ocurrence 0..N.
When any idoc is generated in mapping Im getting the next erro in moni:
Error: MSGGUID 901EF81123CC4D131091DF1F61EB83B4: Tag found instead of tag IDOC BEGIN=
Why Im getting this error in sxi_monitor if I've especified my cardinality to 0..N??
Thanks a lot.
Regards.

>> Error: MSGGUID 901EF81123CC4D131091DF1F61EB83B4: Tag found instead of tag IDOC BEGIN=
First export the idoc locally and change the occurence of idoc tag from 1 to 0 to unbounded. Check in the mapping you specify the modified idoc. Also acivate the objects and update cache.
Tips
a) Use your modified idoc in the message mapping target side
b) Operation mapping - Specify original idoc as target message in the inbound side. (you might get some warning during activation.. please ignore it)
c) In the interface determination check you specify operation mapping and inbound interface as original idoc....
If you do all the above steps, You should not get this error. Hope this helps.
Edited by: Baskar Gopal on Feb 24, 2011 9:30 AM

IDoc not received in MII

Hi All,
I am using SAP MII 12.1.5 Build 87.
I am facing problem with iDoc Listner we have configured iDoc Listner properly in SAP ERP, SAP NW and in SAP MII.
We are able to send iDoc from SAP but we are not able to receive same in MII.
Port and iDoc Server is giving status connected previously it was working fine in SAP MII 12.1.5 Build 83.
Following are the log details for SAP MII Logger as well as SAP NW Log.
SAP NW Log:
Error processing JRA IDOC message
SAP MII Log:
Error processing JRA IDOC message
Error processing JRA IDOC message [server=xxx, client=xxx]
[EXCEPTION]
java.lang.NullPointerException
at com.sap.xmii.ejb.JRAListenerBean.onMessage(JRAListenerBean.java:130)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MessageListenerType.invoke(Interceptors_MessageListenerType.java:110)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Lock.invoke(Interceptors_Lock.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
at com.sap.engine.services.ejb3.runtime.impl.MDBProxyInvocationHandler.invoke(MDBProxyInvocationHandler.java:77)
at $Proxy943.onMessage(Unknown Source)
at com.sap.mw.jco.jra.idoc.JRAIDocExtension$IDocMessageHandler.onMessage(JRAIDocExtension.java:72)
at com.sap.mw.jco.jra.JRA$ReaderThread.sendDirectToMdb(JRA.java:6641)
at com.sap.mw.jco.jra.JRA$ReaderThread.sendAsynchRequest(JRA.java:6601)
at com.sap.mw.jco.jra.JRA$ReaderThread.handleRequest(JRA.java:6771)
at com.sap.conn.jco.rt.DefaultServerWorker$RequestDispatcher.handleRequest(DefaultServerWorker.java:989)
at com.sap.conn.jco.rt.DefaultServerWorker$RequestDispatcher.handleRequest(DefaultServerWorker.java:967)
at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:142)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:2927)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2659)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2478)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2362)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2207)
at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:259)
at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:322)
at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:220)
at com.sap.mw.jco.jra.JRA$ReaderThread.run(JRA.java:7260)
at com.sap.engine.services.connector.jca15.work.TaskImpl.run(TaskImpl.java:255)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
Please help me out on this issue.
Regards,
Manoj Bilthare
Edited by: Manoj Bilthare on May 19, 2010 12:57 PM

Hi Manoj,
Once you have configured your Listener have you checked pressing the update button and i dont want to ask you which version of NW SP you have installed as you said it was working for you with Build 83, but nevertheless NW SP Level should not be not less than SP3.
If this doesn't help you,please try restarting your server again.
How about the credential editor have you configured this as well?
Regards,
Sudhir Kumar
Edited by: Sudhir Kumar Shambana on May 19, 2010 10:46 AM

IP Job in BW finished, but how can I check the IDoc receive status in BW ?

Hi,experts
After I execute a Infopackage with loading more than 200000 records data, the infopackage monitor show me yellow light, 186020 from 200000 records. this infomation still show me till now, seaval hours,it looks pause here.
And I check the request in the R/3, the Job has finished. as you know it means the R/3 push the IDoc already finished.
and how can I do now ? or how can I check the IDoc receive status in BW side?

Hi,
I too had the same problem, i executed the following to solve the proble, may be this will help you:
1) Go to T-code SM58 and select TRFC and press F6,
2) For manual push of I-Docs, GO to T-COde BD87 select perticular idoc and see the status if it is not executed properly then do the manual push by pressing Execute option,
Thanks,

Problem sending IDOC DESADV /AFS/DELVRY03 to XI

Hi Gurus,
I have problems sending IDOCs DESADV (basic type /AFS/DELVRY03) created by function LSEND_IDOC to XI system. IDOC is correctly created by R3 system (AFS ECC 5.0) and correctly sent on the XI port (Status: Data passed to port OK - 03), but XI system doesn't receive IDOC.
If I resend the same IDOC by WE19 tcode goes ok!!
In R3 sending system nothing warnings/errors in syslog or sm58.
Any suggests? Thanks in advance.

Issue solved! It is necessary close the master idoc with a commit

IDOC Receiver - Unable to convert sender service to ALE

Hi!!!
I am trying to configure the following scenario: FILE - XI - IDoc to R/3.
A business service called IDOC_Demo recovers from the server the file, and after mapping it, it tries to send it to IBP, the R/3 system using a IDOC Receiver comunication channel.
IBP is configured in SLD.
I have in XI System the RFC conexion, and I have define the port via TCODE IDX1.
But it does not work, I am geting the following error:
"Unable to convert sender service IDOC_Demo to an ALE logical system"
I have checked the adapter specific identifiers, but I can not see anything wrong...
I do not know what can I check! Could someone help me?! What can I do?
Thank a lot!!
Araitz.

Thank you very much, but I still get the error message! Of course, I read your blogs Michal before posting the question, and they have been very useful, but still...
In SLD I only have the R/3 system, the name is IBP and the business landscape and the logical system name (I do not know if this could cause a problem).
The connexion is IBP, and it works, and in idx1 I have configured a port, and its name is SAPIBP, using the IBP connexion.
Design I have imported the CREMAS.CREMAS03 IDOC, and I have done a mapping interface, I have disabled the EDI_DC40, and set begin and segment to 1.
Configuration I have created a business service, IDOC_Demo, that has a communication channel, sender, file type.
And I have the IBP service. In adapter specific I can see: logical system IBP, and R/3 System IBP, client 100. If I push the Compare with SLD button, nothing happens what should happen?
IDOC_Demo receives the file, and via an Outbound, async interface, calls IBP, that receives the IDoc using a receiver IDoc type adapter
Now the receiver agreement has information in the header mapping, sender service, IDOC_Demo, receiver service, IBP.
And I do not know why, but it does not work any idea?
Than you!
Araitz.

Problem with idoc DEBMAS

Hi everybody.
We have a problem with idoc DEBMAS.
This idoc is sent from R3 to PI throw change pointers then the idoc is field only with the data modified in the master custumer.
We need the information fill it in the segment /IDOC/E1KNA1M/E1KNVVM to determine the receiver determination but this segment is not always sent.
What can be done in R3 to send always this segment.
We dont want to sent the whole data but always this segment.
Any idea???
Thanks a lot!!!!!

Hi,
As E1KNVVM segement is not mandatory, when you are triggering IDoc based on change poitner data might not populted in the E1KNVVM segment until some sales data is changed.
if you need that segement always just copy the Idoc type and make it mandaotry field.
otherwise yoy can populate some fields like STDVRS with the reruried constant and can use in your receiver determination.
Regards,
Suresh

EDI Idoc -- Receiver JMS Adapter.

Hi,
I'm facing this issue from few days.
Sender is EDI Idoc and contains header and Footer.
This is placed in the application server of SAP system.
From there xi picks the EDI Idoc and sends to JMS server.
Facing problem on the receiver JMS Adapter.
Find the error message.
"Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: No transition found from state: ERROR, on event: process_commence for DFA: CC_JMS_RCV_DEVWR0000000:165b1638fd823a8f822f0db8a9b1d488"
I have provoded the "dict" and "doc" value also.
Pls suggest.
Thanks in advance,
Jeevan.

Hi Guys,
There could be some problem while deploying the libraries. Check out the thread No transition found from state: STARTING
Thanks,
PP

IDoc received with status 8

Hi Experts,
Please find the below Error now i am getting.
No data available
Diagnosis
The data request was a full update.
In this case, the corresponding table in the source system does not
contain any data.
System Response
Info IDoc received with status 8.
Procedure
Check the data basis in the source system.
Please provide me solutions ASAP, this issue.
Thanks & Regards,
Bharathi.

Hi Ananda,
I have followed ur post, but same problem i am facing.
The Error below following:
No data available
Diagnosis
The data request was a full update.
In this case, the corresponding table in the source system does not
contain any data.
System Response
Info IDoc received with status 8.
Procedure
Check the data basis in the source system.
Please give me any other solutions, how to resolved this issue.
Thanks in Advance.
Regards,
Bharathi.

Configuring IDOC Listener on MII 12.1

Hi,
I had a basic question around the configuration.
This is from 12.1 help:
"The SAP Java Resource Adapter (SAP JRA) server is used to connect to SAP ERP Central Component (SAP ECC) to receive remote function calls (RFC) and IDocs. You can use the asynchronous HTTP interface to post data to SAP MII for asynchronous transaction processing."
In this regard is it mandatory to first configure SAP JRA on NW and then proceed with the IDOC specific config both on the R/3 as well as NW side?
The reason I ask this is that we are currently struggling with this config on 12.1.8 (build 30) where the BASIS folks are observing that the system hangs when they try to add enteries to the XMIIIDOC component . Before going through with the IDOC config they made sure that the JRA is configured and followed the steps as mentioned in the 12.1 installation guide under "Configuring JRA for JRA Actions" & "Cloning the default JRA Config" sections.They are simultaneously also following up in the NW forums to find a solution.
Additionally I had another question (this one's specifically for MIke Appleby ). Would one have to follow similar config steps as IDOC when configuring the RFC listener , atleast from the NW CE perspective? We are trying to download Control Recipes from R/3.
Thanks
Udayan

Hi Udayan,
Yes, the configuration for the RFC Listener is essentially the same as the IDoc Listener, except the binding is different (do not change either type from the default values and you should be fine).
The differences between the two Listener types are really on the ECC side. The installation instructions for Batch Manufacturing included the RFC Listener setup. Keep meaning to write a separate document for RFC Listeners, but haven't yet.
One general note of caution for all readers:
Do not reuse ProgIDs from an IDoc Listener in an RFC Listener and vice versa. Only use a unique ProgID once (and deleting them from one Listener or MII server to use them elsewhere is generally not advisable).
Roughly 90% of the tickets entered for IDoc Listeners with MII are because of ProgIDs used in more than one place.
Regards,
Mike

PROBLEM POSTING IDOCS IN MASS

Hi people.
Ive got a Z FM to process inbound INOTIF idoc. To improve the perfomance Im trying to make the process in mas (BD51).
The process is triggered by the program RBDAPP01 but it doesn´t work.
The whole Idocs are set with satus we51 without ale status.
By debbuging I can see de program only make the process for the first idoc...
This loop is only executed once despite of there are more the one entry in table idoc_control with all the number idocs to be processed:
loop at idoc_control.
loop at idoc_data where docnum=idoc_control-docmun.
BAPI TO CREATE NOTIFICATION.
endloop.
endloop.
When I process only one Idoc the process works fine.
¿Anybody knows whats the problem with this mass posting?
Regards and thank u so much

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>

Incomplete Idoc received in SAP R/3

Hi XI Gurus
I am working on a File to Idoc scenario and stuck because of a strange issue.
The output Idoc structure sent from XI and as viewed in IDX5 / SXMB_MONI is as below
<?xml version="1.0" encoding="UTF-8"?>
<ACC_DOCUMENT01>
 <IDOC BEGIN="1">
 <EDI_DC40 SEGMENT="1">
 <SNDPRT>LI_SND</SNDPRT>
 <SNDPFC>LF_SND</SNDPFC>
 <SNDPRN>0000000100</SNDPRN>
 </EDI_DC40>
 <E1BPACHE09 SEGMENT="1">
 <OBJ_TYPE>BKPFF</OBJ_TYPE>
 <OBJ_KEY>PR2000627830002007</OBJ_KEY>
 <OBJ_SYS>T47CLNT800</OBJ_SYS>
 <BUS_ACT>RFBU</BUS_ACT>
 <USERNAME>lovein</USERNAME>
 <COMP_CODE>3000</COMP_CODE>
 <DOC_DATE>2007-09-11T05:18:52-07:00</DOC_DATE>
 <PSTNG_DATE>2007-09-11T05:18:52-07:00</PSTNG_DATE>
 <DOC_TYPE>SA</DOC_TYPE>
 </E1BPACHE09>
 <E1BPACCAHD/>
 <E1BPACGL09>
 <ITEMNO_ACC>1</ITEMNO_ACC>
 <GL_ACCOUNT/>
 <ACCT_TYPE>S</ACCT_TYPE>
 <DOC_TYPE>SA</DOC_TYPE>
 <COMP_CODE>3000</COMP_CODE>
 <PSTNG_DATE>2007-09-11T05:18:52-07:00</PSTNG_DATE>
 <VENDOR_NO/>
 </E1BPACGL09>
 <E1BPACAP09>
 <ITEMNO_ACC>00001</ITEMNO_ACC>
 <VENDOR_NO/>
 <COMP_CODE>3000</COMP_CODE>
 <PYMT_METH>ach</PYMT_METH>
 </E1BPACAP09>
 <E1BPACCR09>
 <ITEMNO_ACC>1</ITEMNO_ACC>
 <CURR_TYPE>00</CURR_TYPE>
 <CURRENCY>USD</CURRENCY>
 <CURRENCY_ISO>USD</CURRENCY_ISO>
 <AMT_DOCCUR>-30000</AMT_DOCCUR>
 </E1BPACCR09>
 <E1BPACCR09>
 <ITEMNO_ACC>Constant</ITEMNO_ACC>
 <CURR_TYPE>00</CURR_TYPE>
 <CURRENCY>USD</CURRENCY>
 <CURRENCY_ISO>USD</CURRENCY_ISO>
 <AMT_DOCCUR>0</AMT_DOCCUR>
 </E1BPACCR09>
 <E1BPACCR09>
 <ITEMNO_ACC>Constant</ITEMNO_ACC>
 <CURR_TYPE>00</CURR_TYPE>
 <CURRENCY>USD</CURRENCY>
 <CURRENCY_ISO>USD</CURRENCY_ISO>
 <AMT_DOCCUR>30000.00</AMT_DOCCUR>
 </E1BPACCR09>
 </IDOC>
</ACC_DOCUMENT01>
But the Idoc received in SAP R/3 as viewed in Transaction WE02 or table EDID4 has only one node E1BPACHE09
and because rest of the nodes are missing SAP R/3 fails to process the Idoc .
Any help to analyse the issue will be highly appreciated.
Thanx
Lovein

Hi Lovein,
What you can do is:
1. Go to SXMB_MONI and take the output xml.
2. Now go to your mapping under TEST tab and test the above mentioned output xml and see what is the output, i mean are you able to see all the desired output as per you mapping or not.
3. If not then probabily you will get an error message, then try to find out the solution in your mapping only.
4. If you are not able to do that, kindly send the error message, which you got in mapping.
I hope this will solve your issue.
Regards,
Sarvesh
****Reward points, if found helpful.

Problem in IDOC Receiving on MII

Similar Messages

Maybe you are looking for