Idocs stuck in ECC SM58

Dear Experts,
I have an ICO configured scenario where sender is ECC and receiver is a 3rd party application (Sender IDOC_AAE-PI-SOAP asynchronous scenario). Idocs are stuck in SM58 of ECC, connection test of relevant RFC destination is successful.
Error text: Name or password is incorrect (repeat logon)
Please help in resolving the issue.
Thanks and Regards,
Mani

Hi Mani,
Please check the RFC user name and password which you have mentioned in RFC destination with the help of basis team, it will resolve your issue.
Just mail the screenshots to basis team they will help you.
Regards
Bhargava Krishna

Similar Messages

Java IDOC_AAE configuration issue in PI IDOC sender channel and in ECC SM58.

Dear Experts,
My configuration scenario is outbound: SAP (IDOC)-------->PI------->AS2 ThirdParty.
SAP PI version: 7.31 dual stack.
First time i have done IDOC_AAE settings done in ECC and PI NWA with the help of below links.
http://scn.sap.com/docs/DOC-34155
http://scn.sap.com/docs/DOC-31398
While sending the DESADV.DELVRY05 standard idoc from ECC to PI i am getting below error in Sender IDoc channel.
Could you please help me on this issue ,I will appriciate you .This is very urgent.
Error in PI IDOC Sender channel : Processing error = Value with name ApplyCntlRecFromPayload not available
and I are getting below error in SM58 ECC system.
Error in ECC SM58: Commit fault: ASJ.ejb.005043 (Failed in component:
Thanks,
Aadi

Hi Aadi,
Please check the below SAP notes
1952406 - "Commit fault" error in SM58 transaction when sending IDOC from backend system to PI sender Java IDOC adapter
1928302 - Possible NullPointerException with IDOC_AAE sender channels processing
reference - Commit fault: ASJ.ejb.005043 (Failed in component: sap.com/com.sap.aii.ad) while sending to PI system
also check the link - http://saphelp.me/commit-fault-asj-ejb-005043/
regards,
Harish

Sm58 IDOC stuck

Hello,
IDOC stuck in sm58 with error No authorization to send IDocs with message type
scenerio is FTP to IDOC. We are using Pi7.1 its simple secenerio can u pls let me know what is case how can we solve this.

Hi Michal
do you not use the "Permitted Agent" then? or does that not have any affect at all???
Specifies the job (person or group of people) to be notified if processing errors occur on the IDoc interface. You can define up to three different jobs:
in the inbound or outbound partner profiles for special partners, messages and direction.
in the general partner profiles for special partners.
in the general IDoc Administration settings.

TIME OUT error in ECC SM58

hi All,
We have sent some 2000 Idocs from ECC,
my scenario is FILE to FILE.
I am collecting all the idocs into a file using IDOC XML port..
File havnt reached XI.. even not created in application server ... all idoc are stuck in ECC side.. when i go to SM58.. getting error like TIME OUT error ...
Please help guys.. how i can sent those.... 2000 stuck Idocs?

Hi Sam,
check the 'Timeouts in PI' section in the PI Troubleshooting Guide -
[#1060264 PI Troubleshooting Guide 7.1|http://service.sap.com/sap/support/notes/1060264]
Regards
Kenny

"An IdocException occurred" while posting Idocs from SAP ECC to SAP PI AEX

Hi all,
While sending Idocs from SAP ECC to SAP PI 7.4 AEX, we are experiencing this issue at SAP ECC-SM58
Only a particular Idoc type is having this issue.
Below are the checks done before posting this query:
1. Pushed other Idocs from the SAP ECC to PI and all were getting exchanged successfully.
2. Reloaded the meta data in PI for the particular Idoc type in issue.
3. Checked the RFC destinations in SAP ECC, RFC connection test is also working fine.
4. Unicode option enabled in the SAP ECC RFC destination pointing to PI-AEX
5. Restarted the inboundRA service in PI AEX.
Is there anything still missing. What could be root cause of this issue.
If anyone has encountered it before, pleases share the resolution.
Thank you
Younus

Hi Amit,
Thanks for the reply. Log viewer doesn't provide much help on the error.
The error desc says
"JRA]serverExceptionOccurred. Server XI_IDOC_DEFAULT_SID, Managed_Application_Thread_58, connectionId=5-ip address|sapgw20|XI_IDOC_DEFAULT_SID, Exception: com.sap.conn.jco.JCoException: (104) JCO_ERROR_SYSTEM_FAILURE: An IDocException occurred"
regards,
Younus

In 4.6C, How to delete IDoc stuck?

Hi, experts
after I load more than 20000000 records data from R/3 side, I found out there are too many IDoc stuck in R/3 side use SM58.
How can I delete these IDoc in one time? the T-CODE 'WE11' and the program 'RSETESTD' can not use in my 4.6C system.RSETESTD.

try BD87

Idoc stuck on smq2

I have a scenario where sending idoc from SAP ECC to SAP PI without error, but to reach the SAP PI is not processed, in reviewing the TX SMQ2 the idoc gets stuck and I have to activate them manually to generate the XML, as I can investigate because automanticamnete not processed and remain in waiting to be done manually

Hi Leon,
You need to register and activate the queue by using T-Code SXMB_ADM.
Also check if ithe queue is unlocked.
By using the transaction SMQ2 you can reset the queue's status.
Set IS configuration parameter MONITOR QRFC_RESTART_ALLOWED to value 1.This will initiate processing of messages stuck in the queue
You can run RSQIWKEX to run periodically. It resets the queues automatically.
You have to go to SXMB_ADM. Then click manage Queues and you have to dergister all the queues. After doing this you need to go to SMQ2 and you have to actiavte the queues.
After all this try to re-register the queues in SXMB_ADM ..
Regards,
Rohit

Sending IDOC from SAP ECC to SAP MII

Hello,
Issue while configuring.
I have configured the RFC Destination in the Netweaver message listener and when i check the connection in SM59 I got error as timeout during allocate of registered program and I have attached the screenshot of the error page.
I would request a reply asap.
Thanks,
Praveen

Hi Praveen,
First, I would suggest that you identify what version, and SP, of MII and ECC. Also the NW version and SP if applicable.
Second, use this custom Google search and terms MII, IDoc Listener, and perhaps SM59. There are many discussions on IDoc Listeners going back a number of years. Many of the issues with IDoc Listeners have not changed in most of that time, so look at the older ones as well. I presume that you found and are using my How to Send an IDoc from SAP ECC to the SAP MII IDoc Listener (MII 12.1 to ECC 6.0) to set up your Listener? If not, you should review your configuration and setup procedure against it.
I have not looked at MII 14.0 or 15.0, but understand that the configuration of Listeners really has not changed since MII 12.1. So the document is still applicable.
Third, roughly 90% of the problems experienced with IDoc Listeners involve multiple uses of the self registering ProgID. Deleting it in one place, generally does not work. Use it in one place only. Create a new ProgID for each separate Listener (either type) on each separate MII instance for each ECC instance. Save yourself a lot of headaches. Never, ever reuse ProgIDs!!!
Fourth, most of the other issues involve a PI/XI system in the middle. Those are a bit more complicated since they rely on getting the connection configuration set up properly in PI. Since I am not that familiar with PI systems (most times it is not involved with the Listeners), I generally have to get other experts involved. Sometimes a CSS ticket is required.
Regards, Mike
SAP P&I Technology RIG

** Not able to import IDoc from SAP ECC system

Hi Friends,
I am not able to import the IDoc from SAP ECC system in IR. I have checked that, hostname, client, server no. everthing is correct. I checked in SLD also. Host Name is correct.
While import (after giving the user name and password), I am getting the following error.
Problems to reach R3 System
What could be the probelm ?
Kindly help me friends.
Thanking you.
Kind regards,
Jegathees P.

Hi,
Just counter check following step
1. Go to SWCV definition tab select radio button for Import of RFC....
2. In Connection Data for Import from SAP System maintain correct System and correct Client.
3. Make sure you maitain ECC system in Central SLD.
4. In Import Screen check at the top of the screen have SAP System, is that system from where you want to import the IDOC.
With Regards
Sunil

Idocs stuck in workflow at status 51

Hi all,
There are lot of Idocs stuck in status 51 in workflow. Work flow error message reads as "Document OvershipCl does not exist". Can someone explain what does this mean and how do we clear these items.
Regards,
Santosh

Hi Santosh
You could also use transaction BD87 for further analysis and processing. This is more interactive. Please select the IDOC and on the left screen the the status record with entry 51 will have the details as to why the IDOC failed. Please correct as required in order that the IDOC will get processed.
Hope it helps. Please do assign points if found useful.
Regards,
Karthik

How to Post Idoc's from ECC to SCM

Dear Friends,
This is Shalini Shah.
how to post the Idoc(MATMAS05)
from ECC to SCM-APO.
please give me the details on this topic.
Regards,
ShaliniShah

Please see the Wiki page details mentioned in this [sticky|Wiki page for SCM-APO; thread at the beginning of the forum.
Refer to the [CIF|https://wiki.sdn.sap.com/wiki/display/SCM/CIF] Wiki page for details on setting up and using CIF. I am not aware of the IDOC details but if it material master (as SB has mentioned) then your best option of transferring the master data from ECC to SCM / APO will be to use the CIF.
After intial CIF settings are maintained (see details inthe CIF Wiki page) you will need to create Integration Models and activate them for transferring the data.
Somnath

Idocs stuck in sm58

Hi All,
When I triggered Idocs in R3 ,they were stuck in sm58 with status : :000. I'm not able to release it.
I checked with port information, everything is correct.
When I checked with threads in SDN it says to check with authorization of userId in sm59 of R3. if this is
the case then I ll not be able to send any Idocs from R3. But in my case other Idocs are getting triggered,
only the newly created ones are stuck. Kindly suggest sollution to resolve this issue.

Hi,
for checking the metadata you could also have a look here:
http://help.sap.com/saphelp_nw04/helpdata/en/8a/b8b13bb3ace769e10000000a11402f/frameset.htm
Regards
Patrick

Select one of the installed languages- Idoc stuck in sm58

Hi,
We have observed a strange issue during testing.
Some interface Idocs going from R/3 system to XI got stuck in sm58 with error
Select one of the installed languages
Later it was found that language EN was not specified in RFC destination and in the user profile which was being used in this RFC.
It was fixed and interface was working fine.
What I was not able to understand was why other interfaces were processing Idocs successfully using the same RFC destination?
regards,
Anirudh

Hello,
Are your other interfaces still using the same RFC destination and port to PI , or do you have differnt? if different that could explain your issue.....

Idoc getting stuck up in SM58

Hi All,
Previously we have created one outbound Idoc. we were passing data to external system via XI. it was successfully reaching to external system.
now we have added one more segment to existing Idoc. after processing doc, in WE05 transaction, Idoc status is showing as 03 i.e. data successfully passed to port. the issue is that the Idoc is not getting passed to external system i.e. XI . In SM 58, the Idoc is getting stuck up. it gives error message as below,
EDISDEF: Port SAPCAG segment defn Z2WY_SV_DLR000 i n IDoc type ZWY_SV_SPG_
Message no. SR053
Please let me know if anybody has idea on this.
Thanks,
Chandra

Hi Chandrashekhar,
If you are using XI/PI, go to IDX2 transaction and see whether the idoc is re-loaded successfully with new segment. If not, just delete the idoc and load it again for the port you are using. I think this should fix your problem.
Thanks,
Adithya K

Idoc stuck in Sm58 Commit fault: ASJ.ejb.005043 (Failed in component:

Hi All,
We have an IDoc to File scenario and IDoc is stuck in tRFC with the error :Commit fault: ASJ.ejb.005043 (Failed in component:sap.com/com.sap.aii.ad
This is the new PI box and IDoc is triggered for the first time.
RFC destination is created for PI Java Stack as we are using ICO.
PI Version: 7.31
Regards,
Mani

Hello,
If you still receive the error after the above recommendations please go to the NWA logs and traces in PI and provide the corresponding error message from the developer trace.
Also check the configuration as per the following link has been done:
Configuring PI 7.30 Java IDoc Adapter
Kind regards,
Sarah

Idocs stuck in ECC SM58

Similar Messages

Maybe you are looking for