IDOC not received in XI; error in SM58 of sending system

Hello everybody,
we got a SAP CRM sending a "generated" IDOC.
(IDOC-Type: CRMXIF_PARTNER_SAVE01)
The IDOC seemes to be rejected by XI because
SM58 shows:
- No Service for System Binding_Error Client ...
- function: IDOC_INBOUND_ASYNCHRONOUS
All settings (IDX1, IDX2, ID, IR) are OK!!
All reimports (delete & import IDOC) are made!!
(btw: we got several other IDOCs-Types that work fine!)
Could it be, that the IDOC-type is GENERATED?
Regards Mario

Hi Mario,
Solution for this error is provided in link given below
of Problem Analysis Guide "Sending an IDoc through XI Failed "
http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
Also have you set adapter specific identifiers?
For the same, refer question 3 (integration engine section)
/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
Regards,
Abhy

Similar Messages

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

Can not receive Mac mail -error Outlook cannot find the server. Verify the server information is entered correctly in the Account Settings, and that your DNS settings in the Network pane of System Preferences are correct. Account name: "MacMail"

Can not receive Mac mail -error Outlook cannot find the server. Verify the server information is entered correctly in the Account Settings, and that your DNS settings in the Network pane of System Preferences are correct. Account name: "MacMail"
What are the correct mail account settings and more importantly the correct DNS settings
Thank you for any help you may be able to provide
Cheers
Chris (iMac i7)

Do not delete the old account yet. sign up for an iCloud account if you haven't.
I understand .mac mail will still come through. Do not delete the old account yet.
You cannot use .mac or MobileMe as type of Account, you have to choose IMAP when setting up, otherwise Mail is hard coded to change imap.mail.me.com to mail.me.com & smtp.mail.me.com to smtp.me.com, no matter what you try to enter.
iCloud Mail setup, do not choose .mac or MobileMe as type, but choose IMAP...
On second step where it asks "Description", it has to be a unique name, but you can still use your email address.
IMAP (Incoming Mail Server) information:
          •          Server name: imap.mail.me.com
          •          SSL Required: Yes
          •          Port: 993
          •          Username: [email protected] (use your @me.com address from your iCloud account)
          •          Password: Your iCloud password
SMTP (outgoing mail server) information:
          •          Server name: smtp.mail.me.com
          •          SSL Required: Yes
          •          Port: 587
          •          SMTP Authentication Required: Yes
          •          Username: [email protected] (use your @me.com address from your iCloud account)
          •          Password: Your iCloud password
Also, you must upgrade your password to meet the new criteria: 8 characters, including upper and lower case and numbers. If you have an older password that does not meet these criteria, when you try to setup mail on your mac, using all of the IMAP criteria listed above, it will still give a server error message. Go to   http://appleid.apple.com         then follow directions to change your password, then go back to setting up your mail using the IMAP instructions above.
Thanks to dpepper...
https://discussions.apple.com/thread/3867171?tstart=0

My credit card has been charged for book, however my purchase history shows no record of the transaction and I have not received the book. The online problem reporting system does not have options to report this incident. Who can I cal

My credit card has been charged for book, however my purchase history shows no record of the transaction and I have not received the book. The online problem reporting system does not have options to report this incident. Who can I call?

Would be problems with purchases, billing, and redemption option. It's not 100% exact to your issue, but it will get you to the right department.
Go here https://expresslane.apple.com/GetproductgroupList.do then select ITunes, then Store, then Purchases, Billing, and Redemption. Then.. probably pick "My topic is not listed."

Idoc not received in receiver , sender shows successful in WE02

Hello,
I am sending Vendor from Production to Quality , sender system shows in WE02, idoc status as sucessful. I have checked all ALE settings and they are perfectly fine.
But in receving system I am not able to receive it. In sender , transaction SM58 is showing error:
No authorization to send IDocs with message type CREMAS
Can any one suggest what is the soultion for this scenario?
Thanks,
Madhura

Hello,
Solution for above problem:
After executing transcation SM58, screen will show Function Module as IDOC_INBOUND_ASYNCHRONOUS , put cursor on FM IDOC_INBOUND_ASYNCHRONOUS
, go to EDIT->Execute LUW.
This will solve the problem of authorization.
Thanks,
Madhura

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

IDOC not receiving in XI

Hi -
Using PI 7.0 and checked all the configurations and read all the related blogs but i don't see the IDOC coming into XI.
Checked the SM58 on R3 and does not show any errors.
I checked the WE02 on XI system and shows a status of 60 and 56. Status 60 says "Basic Type MATMAS05 does not exist" which is true because it does not exist on the XI system but exists on the r3 system.
All the ports on xi and r3 system seem to be fine. i pushed the idoc and shows a status '03' on the r3 side.
Any tips/ideas to solve the issue are greatly appreciated.
Thanks,
Tirumal

Hi,
Go to SMQ2 and try to check the Queue Status .
Did you check this SAP note I referred earlier- 940313
Also -http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
GO thru each step ..because it will help you to resolve the problem.
Hints-
1) check WE02 and check the status of Idoc in the R/3 system. Is it sent to XI box/port correctly ?check its control record info , in WE19
2) Did you check Partner Profiles - for outbound parameters -check out this
3) Check the SM59 entry in SAP system - pointing to XI box.
4) Check IDX5 transaction in XI box, if eevrything is success in R/3 system
5) check the Business system in XI - is it pointing to correct R/3 system.
Hope this helps,
Regards,
Moorthy

IDoc not received by the Webmethods

Dear Abapers,
I have a scenario :
Here the idoc is being created perfectly with all the segments prooperly populated. Also from SAP side, we are getting the message that it has been sent.
However, the receiver ( Webemthods) is saying that it is not receiving the idocs . So, what can be the possible reason ??
Appreciate your reply...
Thanks and Best Regards,
Kunal.

error send questionnaire in srm Ros
Registration - Error after Send / No Questionnaire
ROS Questionnaire link sent by email
ROS Questionaire
Re: Status for the transferred Suppliers is not updated in ROS client!

SAP ERP - SAP ME - iDOCS - Not received

Dear Experts,
We are trying to send data ( MATMAS iDOC) from ERP to ME.
We used the below transaction in SAP.
1. using BD10 transaction in SAP ( Send material) Idoc was sent
Checks :
We checked in WE05 in SAP and found that Idocs sent is successful
Opened MII ( Queue Monitor) and Found that Idoc was received successfully with ID but Message ( "" sucessfully Queued) Status : Queued
Problem : We are not able to see the material in ME system
No errors found in NWA logs.
Kindly suggest any solution.
Regards
Shankar

Make sure you have the plant id in the idoc. Here are the few place in the idoc that you need to add the PlantID. We're using TN01 as our plant.
<MATMAS03>/ <IDOC>/ <E1MARCM>/ <WERKS>TN01</WERKS>
<MATMAS03>/ <IDOC>/ <E1MBEWM>/ <BWKEY>TN01</BWKEY>
<MATMAS03>/ <IDOC>/ <E1MVKEM>/ <DWERK>TN01</DWERK>

Outbound IDOC not received at the receiver system.

Hi,
Im sending an IDOC from sap to a non-sap system. During this process, from sap system it is executing successfully without any erros and the status is also '03' .
The problem is that the other system is unable to receive the IDOC sent from SAP system.
The connection is like TCP/IP and the registered server program is given as 'PROGRID' in RFC destination.
I would like to know what would be the possible cases where this IDOC is not received at the receiver system.
The configuration is perfect as per my knowledge. Just want to confirm one thing 'do i need to include any message type such as "SYNCH".
Awaiting for your solutions.
Thanks
rohith

Hi,
If the IDOC is sent successfully from the sender system then the status of the IDOC will be '03' , no matter whether the receiver has received the IDOC or not.
As per your case,
Check the Partner Profile parameters , whether the basic and extended message types are used properly.
The message type Synchron (Sync) is generally needed in Inbound IDOC side. Check whether you have added SYNCH or not.
Hope this Helps.
Regards,
Abhinab Mishra.
Experience is the name everyone gives to their mistakes.

Idocs not being sent from 4.6c to 6.0 system

Hello,
I am sending Idocs from a 4.6c R/3 system to a 6.0 R/3 system. I can see that the Idocs are being created and sent to port OK (status 03) in the 4.6c system but not able to see the Idocs in the 6.0 system.
Actually, there are 2 cases but in both cases I am using the same function module 'ALE_DISPUTE_CREATE' to send the Idocs but only in the first case Idocs are received in the 6.0 system. I checked the parameters of the function module in both the cases and they are same in both the cases with the only difference being the values.
One more difference is the way the data is prepared . In the first case, 'FDM_CASE_DATA_PREPARE' is used to prepare the data and in the second case I am creating the data using normal data extraction and internal tables after which I pass the datas to the function module 'FDM_COM_CASE_CREATE' which is also used in the first case.
'ALE_DISPUTE_CREATE' is within this function module.
I checked the queues in both the systems and did not find anything stuck there. One more interesting case, If I copy the Idocs which are not being sent using WE19, the Idocs are being sent correctly and received correctly in the 6.0 system.
Please advice.
Thanks,
Laxman.

Hi Laxman,
You said that the Status of the IDOC at sender side is '03', have you checked the status of IDOC in reciever system. Check the details of DOC using WE02. Use BD87 to Monitor the messages issued during IDOC processing. These messages will help you to reach to the exact problem.
Regards,
Vaishali.

Acrobat X Pro does not open, gives fatal error - "Acrobat failed to send a DDE command"

Acrobat X Pro does not open and gives fatal error - "Acrobat failed to send a DDE command"
It either does the above or the application starts and is listed in the system processes but never physically opens on the desktop for viewing.

AA 9 will not work for anything but the print function from WORD 2010. The only version of Acrobat that is compatible with OFFICE 2010 for PDF Maker is AA X. Thus, open WORD and print to the Adobe PDF printer. Then open the pdf in Acrobat. Go to FORMS>Add or Edit fields. Since you have no fields at present, Acrobat will ask if you would like to detect form fields. Answer yes and you will get a first cut at the form fields. Yes, you will likely have to add some more and change the ones that Acrobat estimates, but you are on your way.
The other two options you have is to go back to WORD 2007 or earlier or upgrade to AA X (or find someone with AA X and WORD 2010). These methods are pretty much your options with the software combination that you have.

I upgraded to 31.3.0 and now can not receive e-mails, even though I can send them.

Have used Thunderbird for years, but have not been able to receive e-mails for two days since the upgrade. Able to send e-mails, but not receive. Tried deleting e-mails for last few days on server and on Thunderbird, but no change. Tried deleting saved password on Thunderbird, but it only asked for new password when sending e-mail, but does not ask for password for receiving. Tried re-installing Thunderbird, but no e-mails received.

I solved the problem by changing Account Settings / Server Setting changed the port to 995 (default was 110) and the security to SSL. (Not sure how the upgrade changed these settings).

I am not receiving text messages and sometimes when I send texts it does not go through

Hi,
My phone is not receiving text messages and depending on where I am it also does not send, it gives me a message failure. Then if I send it as a text message instead of imessage it will go.
Any ideas how to fix it?

contact your wireless provider. txt messages is their service.

IDOC not received in XI; error in SM58 of sending system

Similar Messages

Maybe you are looking for