IDOC not reachig Legacy

Hi Experts,
My senario is Idoc coming from SAP to PI,from PI must reach Legacy(Jms adapter),SAP has posted Idoc but it is not reaching legacy,Even I dont see any message related to that interface in MONI,I have taken the idoc number and checked in IDX5 it is i red status and error Receiver not found.In payload there is filed missing "<SNDLAD>IND<SNDLAD> ,BUT IN rECIVER DTERMINATION THERE IS NO condition may be this is the issue or any thing else kindly help me.
Regards,
Prasad.

hi,
No Reciver aggrement found for Sender.
first you need to check configuration objects..reciver determination and interface determination.is it working fine you have to some changes in re activate it.
i hope this will help you.
regards,
ganesh.

Similar Messages

IDOC not there in WE02

Hi Gurus,
I am doing a FILE TO IDOC scenario for taking Material Master data from the MDM system and posting the IDOC into the R/3 system..
The entry is there in MONI with the chequred flag but there is no IDOC in we02 of the R/3 system.
Also , i pasted the payload from teh MONI and checked in the mapping and the test was shown to be successful.
Can Anyone please tell me what can be the cause and its probable solution?
Thanks in advance,
Shweta.

(1) Error Category - CO_TXT_OUTBINDING_NOT_FOUND
The problem is in Technical routing.
Check whether the receiver determination and interface determination objects are active in change lists tab. If they are not active, activate the objects.
Also check the if the receiver determination and interface determination objects are referenced to the same namespace or not. Sender and receiver interface objects should always refer to the same Namespace.
(2) Error Scenario - ATTRIBUTE_IDOC_METADATA
Check the receiver communication channel (Created using IDOC adapter). In this communication channel check if the two mandatory parameters are passed correctly.
Following is further info on those two mandatory parameters.
(i)Check if the RFC destination which is created in XI to connect the target SAP R/3 system is working fine.
(ii)Check if the port that has been created in XI is in the form SAP<SID of R/3 system>. If not, create in the form of SAP<SID of R/3 system>. To this port, specify the above RFC Destination.
(3) Error Scenario - IDOC not yet created in target SAP R/3 system.
Go to R/3 system and check at Tcode WE05 if the IDOC has been created successfully. If error is u2018"Partner profile not configured" check point 9.
Suppose IDOC did not get created at R/3 end and all the pipeline steps were successful in SXMB_MONI, then go to Tcode : IDX5 in XI and click on Transaction ID field and check the status description which explains the problem.
(4) Error Scenario - Partner profile not configured.
Go to Tcode WE20 in R/3 system and check if the partner profile has been configured correctly and is filled with the inbound parameters.
regards
chandra

IDOC not displayed in WE05

Hi Experts,
I have successfully run my scenario CSV-pi-Idoc yesterday. IN MOni XML file is Ok. In R/3side (WE05) Idoc generated successfully. But Yesterday night Basis people change R/3 password. Now my problem is in R/3 IDOC not displayed in WE02.
Iam also change password in SM59. But no result. Where can I do changes. can any one help me.
Thanks
Hari

Hi Hari,
Make sure in SXMB_MONI in your PI system the message is showing successful flag in outbound side (ie.. drag the scroll bar to ur right had side and see if you can see checkered flag). If you see any error then go to tcode sm58 (trfc queue) and filter based on dates and u will find error logs in detail and take appropriate action.
Mostly it might be authetication problem so better to check in ur R/3 destination in Sm59 in PI system if your rfc test and authentication test is successfully showing green or not.
Thanks,
Prasanthi.

Idoc Not received?

Hi
During data loading , I got one Error that Idoc Not received.
What will be the cause of problem and How to resolve it?
Regards & Thanks
Durai

Hi Robert Negro !
I checked , Dump has been there.
How can I resolve?
what will be other causes apart from the Dump?
Thanks A Lot .
Regards
Durai

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 getting post

Hi Friends,
i am using transaction WPUK , there if i enter eann number starting from 1, for ex. 1WMDP000023 Then idoc posted but
if i enter eann number starting from 0, for ex. 0OA103403929908 , idoc not gettign post , error is eann number not exist or not maintained against the material number, but i have already maintained via MM42 in basic view.
pls suggest what i should do, i am already debugging but can't resolve it.

Hi Medha,
Give the leading zeros and check.
Regards,
madhu.

IDOC not getting genrated

Hi Experts,
Need your help.
In idoc creation, I have changed material description, its generating master idoc but communication idoc not getting generated.
Please suggest me the solution,
Regards,
Rachna

Hi,
Idoc's are generated based on the payment method and any how in the payment method we will give the required curriencies which are applicable for that payment method.
And u had mentioned as WE05 for IDOC list, but actually the T.Code for IDOC list is WE02.
Check the settings, it has to come. Reply back for more clarifications.
regards
srikanth.

When executing t.code VL03N then IDOC not getting generated

I have a issue in upgarde project as below;
Go to transaction VL03N
     -Enter Outbound Delivery number
     -Click on document flow
     -Select Goods issue material document and click on Display Document
     -Material document is displayed.
     -Then go to: System -> Services for Object
     -Click on display Relationship
     -IDOC number must be displayed.
But Idoc not generated, here only material documets are displaying, pleass let me know what is the error.
Thanks in advance,
Vishwanath

Hi,
IDOCs will not be triggered in VL03N. IDOCs will be triggered in either VL02N or VL01N based on the output type maintained (if you are triggering idoc based on Message control).
Regards
Vinod

Idoc not recive while sending using program & SEND IDOC IMMEDIATELY in we20

i am sending idoc using program - with function master dat distribute function,
now if i set SEND IDOC IMMEDIATELY in outbound message in we20 'partner profile' than idoc get status 03 but at reciver end idoc not found with any status.
if select collect idoc immideatly than work properly.
what precaution needed while sendig idoc throug send idoc immideatly with Program,
regards,
r p.

Hi rp,
when using SEND IDOC IMMEDIATELY in outbound messge, the packet size should be 1 and use start subsystem option.
Thanks,
Rajeev Gupta
Message was edited by:
RAJEEV GUPTA

Idoc WPUWBW: Status 51 - IDoc not fully processed

Hi All!
Hi All!
This is regarding Goods Moment.
In Quality, Idoc is successfully generated at POSDM system and also in ECC system.
In Production, Idoc is successfully generated at POSDM, but in ECC it is failed (Idoc WPUWBW: Status 51-IDoc not fully processed).
So, at WPER it is showing as In deficit of stock. But stock is available.
Kindly suggest me how to close this issue.
Note: PFA Below. Its the screenshot of the error at WPER.
With Regards,
Yarnagula Sudhir.

Dear Venu
Difficult to answer with this limited information. If you share some more info will be easier to help
regards
Manish

LSMW:Post IDocs Not Yet Posted

Dear All,
I am facing an error in the last step of generating IDocs with BAPIs.
Post Idocs not yet posted, status is red and status text is application document not yet posted.
Please help me.
regards,
Prosenjit.

hi prosenjit,
some where u have missed activating or saving documents.pls chk once.
thanks
sagar

Idoc not received in xi

Hi,
i using idoc to file scenario . idoc are getting posted from sap sucefully i.e status 03 & no entries are found in sm58 .
I am unable to trace the idoc in xi i.e idx5 , sxmb_moni .
I have create port in idx1 for r3 also.
I am unable trace message in RWB .
Plz help me to solve this thread
Thanks,
Sridhar

Hi,
This are the ALE settings,
These will be the Configurations needed in your R3,
1. SM 59 - Create an RFC destination for your XI .
2. We21 -- Create a port for XI
3. We 20 -- Create a partner profile entry for the Outbound IDOCs for XI.
Configuration on XI
1. IDX2 - Import IDOC metadata.
For eg : Lets assume the R/3 system and Xi system are QZA and X7A.
In XI :
Step 1 : In SALE Tcode :
a)Create Logical systems for R/3 and XI.
EG : (QZACLNT100) and (X7ACLNT100).
b) Assign the logical system of XI to Client.(X7ACLNT100)
Both the above options u can find in SALE transaction under SENDING and RECEIVING SYSTEMS tab
Step 2 : In SM59 create RFC destination in XI pointing to R/3(i.e IP address of R/3) (This RFC Destination name shd be same as the Sender LS name)=> QZACLNT100 is my RFC destination.
Step 3: Create the PORT in XI for the Sender system and assign the RFC destination.
In R/3 :
Step 1:
In SALE Tcode :
a) Create Logical systems for R/3 and XI for
b) Assign the logical system of R/3 to Client.(QZACLNT100)
Step 2 : In SM59 create RFC destination in R/3 pointing to XI(i.e IP address of XI) (This RFC Destination name shd be same as the Receiver LS name)=> X7ACLNT100 is my RFC destination.
Step 3: In SALE Tcode under Modelling and Implementing Bussiness Processes-> maintain Disribution Model and Distribute Views.
a)Click on that ,it shall take to Tcode BD64 ,where u can create a Distribution Model.
b)Once you create that ADD MESSAGE type(You have the button at the top), there it shall ask for Receiver and Sender LS and Message type.
c)In Menu Bar EDIT->Generate Partner Profile.
Click on that and press Execute .
This shall create 2 partner profile X7ACLNT100 and QZACLNT100 ,X7ACLNT100(this is the partner number for QZA system) shall have the outbound parameter as CREMAS, and QZACLNT100 is created with no parameters ,you need not worry .
d) Click EDIT->MODEL VIEW->Distribute.
This shall distribute the model and you can see the distribution mode aslo getting created in XI system.
This configuration shall surely help u out as it worked out for me.
Configurations required for IDocs in R/3
In your XI system, you need to do the following.
1. Create a RFC destination to your R/3 system
2. Create a port in IDX1 of your XI system and use the RFC destination in step1.
3. Try importing a idoc metadata thru idx2 transaction to check whether the configuration is correct.
4. In your SLD configure the technical system and business system. The technical system should hold the logical system name you have in your R/3 system client.
5. Import the business system and you can use it in your configuration scenario.
Please also refer below links for details.
Go thru this-
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
SAP R3 ->Legacy system including master data using XI
Regards,
Phani

IDocs not created in file to IDoc scenario

Hi all
I am trying this file to IDoc scenario.
File picked up successfully and sent to R/3 BackendBut Idoc is not postedthe status records
In /n we05 in R/3 Backend shows that EDI: Partner profile inbound not available
I created/tested all basics like RFC dest, port etc.
File service that I am using is a business service hence I am specifying a Logical system name in
Adapter specific Identifiers of the file service.
I disabled EDI_DC40 control tag record as IDoc adapter
takes care of it.
So at first I tried the configuration of IDoc comm. Channel by checking the Apply control record values from payload
But SXMB monitor gave an error regarding this control record tagI guess as we have disabled it so there wont be any values
for control record in payload (correct me if I am wrong).
So I unchecked the checkbox Apply control record values from payload and monitor showed up as successfully processed.
But in the backend I am getting this error regarding partner profile.
I also tried to use an existing profile (LS type) by modifying its inbound parameters to accept CREMAS Idoc.
But the error is as persistent as me
Pls help
Sudhir

Hi
Sender --> LEGACY, maintained in SLD (Logical system).
Receiver--> ENI maintained in SLD with logical sys name M700.
Partner Profile LEGACY maintained in R3.
Following is the IDocOutbound in SXMB monitor in XI.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
<SAP:TABNAM>EDI_DC40</SAP:TABNAM>
<SAP:MANDT>100</SAP:MANDT>
<SAP:DOCREL>640</SAP:DOCREL>
<SAP:DOCNUM>0000000000001013</SAP:DOCNUM>
<SAP:DIRECT>2</SAP:DIRECT>
<SAP:IDOCTYP>CREMAS03</SAP:IDOCTYP>
<SAP:CIMTYP />
<SAP:MESTYP>CREMAS</SAP:MESTYP>
<SAP:MESCOD />
<SAP:MESFCT />
<SAP:SNDPOR>SAPAXI</SAP:SNDPOR>
<SAP:SNDPRN>LEGACY</SAP:SNDPRN>
<SAP:SNDPRT>LS</SAP:SNDPRT>
<SAP:SNDPFC />
<SAP:RCVPOR>SAPENI</SAP:RCVPOR>
<SAP:RCVPRN>M700</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
<SAP:RCVPFC />
<SAP:TEST />
<SAP:SERIAL />
<SAP:EXPRSS />
<SAP:STD />
<SAP:STDVRS />
<SAP:STATUS />
<SAP:OUTMOD />
<SAP:SNDSAD />
<SAP:SNDLAD />
<SAP:RCVSAD />
<SAP:RCVLAD />
<SAP:STDMES />
<SAP:REFINT />
<SAP:REFGRP />
<SAP:REFMES />
<SAP:CREDAT>0000-00-00</SAP:CREDAT>
<SAP:CRETIM>00:00:00</SAP:CRETIM>
<SAP:ARCKEY>DF57A2C0532811D9AD84000F206A031B</SAP:ARCKEY>
</SAP:IDocOutbound>
Control record of IDoc in R3
Tab: Typeinfo
 Basic type-->CREMAS03
 Message Type-->CREMAS
Tab: Partner
 Recipient
 Port -->SAPENI
 Partner Number--> M700
 Partner Type-->LS
 Sender
 Port -->SAPAXI
 Partner Number--> LEGACY
 Partner Type-->LS
Pls help
Regards
Sudhir

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

Idoc Not received on MII Message Listener

Hi All,
I am trying to post Idoc from R/3 to MII Server , but some how I am not getting it
I have configured Destination, Parter, Partner Profile on the R/3 and Message Listener on MII.
When I am trying to send Idoc from R/3 using BD10 transaction (Idoc type MATMAS), Idoc Status as 03 in WE02 transaction , but I the MII server does not show up for this.
Even the Failed Messages is showing no results.
Am I missing some thing here.
Any help is appreciated.
Kind Regards

I got the issue,
The problem was Partner was wrongly selected.
Thanks

IDOC not reachig Legacy

Similar Messages

Maybe you are looking for