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

Similar Messages

IDOC_AAE sender channel shows Commit fault: ASJ:ejb 005043 [Failed in component error]

Hello All.
We have a scenario IDOC to JDBC [ async-sync] scenario. And we have used Async/sync bridge using request response bean module.
Now the issue is that when IDOC is triggered from ECC it shows Commit fault:ASJ:ejb 005043[failed in component] error in SM58.
And if we click on "execute LUW" option the IDOC message reaches PI and gets processed successfully.
Could you please let me know how to fix this.
Thanks,
Jane

Hi Avinash,
NWA logs shows the following error :
[JRA]Couldn't start ResourceAdapter Servers with properties {jco.server.gwhost=essdev03, jco.server.progid=SAPRDB670POALEFEDEX, jco.server.gwserv=sapxxxx}, cause: JCo server is currently running. Current server state is ALIVE
Global [startApp] operation of application [sap.com/ClonedRA_xi~idoc~RA_~MCK_RDA_D~IDOC_Out_CLMLeadData] failed with errors on server process [2664350].
Thanks,
Jane

RFC Error in SM58 Commit fault

My scenario is RFC to XI to FILE.
I made RFC destination in SM59
and configure xi according to
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
The connection test in SM59 is succeeded.
I would like to execute BAPI, so wrote following..
CALL FUNCTION 'BAPI_CUSTOMER_GETLIST'
 IN BACKGROUND TASK
 DESTINATION 'BAPI_XI_001'
 <<< parameters >>>
 COMMIT WORK.
BUT in SM58, I got error
'Commit fault: com.sap.aii.af.rfc.afcommunication.
RfcAFWException: alterna '.
Any ideas?
Best regards.

Thank you very much for your information.
I checked Q&A19 of SAP NOTE 730870
and configured XI again.
Then I got a different error...
' program BAPI_CUSTOMER_GETLIST not registered / CPI
C-CALL: 'ThSAPECMINIT'# '
I have already checked the spelling of BAPI's name.
Have you saw this error??

RFC Error in SM58 Commit fault com.sap.aii.af.rfc.afcommunication

Have a RFC interface between Sap R/3 and XI. Submit RFC request: call function 'Z_PGM'
 in background task
 destination 'XID'
 tables
 it_zmsfi_labels = t_table.
Getting error in SM58 in R/3 : Commit fault com.sap.aii.af.rfc.afcommunication.Rf cAFWException: alternat
Message no. SR053
Any ideas? If I do test connection on in SM59 on TCP connection it's Ok.

call function 'Z_PGM'
in background task
destination 'XID'
tables
it_zmsfi_labels = t_table.
COMMIT WORK.
This should solve your problem.
regards
SKM

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

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.

MATMAS outboud Idoc: problem in SM58

Hi experts,
i have done Idoc to File scenario through SAP PI 7.0 server,
here SAP ECC 6.0 is the sender (MATMAS05- idoc) and Fileserver is the Receiver system and the SAP PI 7.0 is the Middleware system.
created Prtner profiles, customer distribution model view and distributed.
i triggered the IDOC from SAP ECC 6.0 system, (BD10), in WE05it is showing as IDoc processing success, data has sent to port and the status code is 03.
then i checked in tcode SM58, there it is showing under the
user - username
Function Module - IDOC_INBOUND_ASYNCHRONOUS
Target System - PI7CLNT001
Status Text - : : 000
can anybody tell me what would be the problem?
Thanks,
Kumar

Hi,
what kind of connection do you use between ECC and PI - RFC / Proxy? You can check this via SM59.
Is the file reaching PI or does the IDoc stuck in SM58? If it stucks in SM58 - try to reprocess it (hit F6 button).
Also what settings do you use in WE20 for partner PI7CLNT001?
Thanks,
Kai

RFC Error : Commit fault: com.sap.aii.af.rfc.afcommunication

Hi ,
I am having a problem in a RFC to File scenario. My Sender RFC is working fine and is showing the status green in the CC Monitoring in AdapterEngine under Component Monitoring. But we are trying to trigger the data to the RFC we are getting the following error "Commit fault: com.sap.aii.af.rfc.afcommunication.R
fcAFWException: alterna "
The RFC connection when tested it is ok .. the connection is established.
Please suggest.
Regards,
Hemanthika

Hi,
1. Refer to the following notes
SAP Note 730870
SAP Note 775765
Also check
RFC Error in SM58 Commit fault
RFC Error in SM58 Commit fault com.sap.aii.af.rfc.afcommunication
2. have a look to R/3 transaction SM58 to find your message
Thanks
swarup

Error sending IDoc from ERP to PI 7.4 Java Only (stuck in SM58)

Hi specialists
I'm trying to send an IDoc to our new PI 7.4 Java Only.
Because of some authorization issues I changed the RFC Destination <blabla> on PI (nwa) pointing to the ERP system.
Now the IDoc is stuck in SM58 (tRFC queue) and I get this error message:
The IDoc Destination <blabla> was changed. Refresh the destination instance with
Meldungsnr. SR053
Anyone able to tell me where to do this refresh? I'm new to PI 7.4 Java Only and could not find useful answers on SCN and other internet sources.
Thanks a lot in advance for any hints.
Renaud

Hi Iñaki
Great document btw... didn't stumble uppon this before. Thanks.
I carefully went through it but nothing I tried helped.
The RFC destination (PI -> ERP) is working fine.
The resource adapter (inboundRA) is configured correctly. I can confirm, that the connection test of the RFC-Destination inside ERP (ERP -> PI) is successful.
BUT still: sending an IDoc from ERP to PI fails with this message in SM58:
The IDoc Destination <destinationName> was changed. Refresh the destination instance with
Meldungsnr. SR053
This seems to happen every time after one changes some settings in the destination specified in the inboundRA property "destinationName".
So my question still is: how / where do I refresh this destination instance on a PI 7.4 Java Stack Only??? I mean without having to restart the whole PI instance...
Best regards
Renaud

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

Sap R/3 and XI -- Commit fault ModuleException. Please help

Hi All,
I have a RFC interface between Sap R/3 and XI.
I am getting error in SM58 in R/3 :
Commit fault com.sap.aii.af.mp.module.ModuleException: call to messaging.
If I do test connection on in SM59 on TCP connection it's ok.
For the above error I also receive for some time the below SLD error message in RWB of XI
"Error during communication with System Landscape Directory: HTTP response code: 503 (Not Ready)"
Please advice as it is production problem.
Regards

Hi Rick,
Sometimes this error comes when there are huge amount of transactions taking place simultaneously. To resolve this ask your Basis guy/DBA to increase the screen numbers in database.
Thanks!

RFC - XI Commit Fault error

Hi All
I have created an RFC (from R/3) that I am using to trigger a BPM in XI (3.0).
RFC Destination - SM59
I have set up the RFC Destination in R/3 as follows:
Connection Type = T
Activation Type = Registration
Program ID = zabfcxi
GatewayHost = Trx SMGW -> HostName = R/3 system (i.e. NOT the XI server)
GatewayService = sapgw00
XI Sender Communication Channel - CC_RFC_SENDER
In XI I have configured a RFC Sender communication channel as follows:
RFC Server Parameter
Application Server = Trx SMGW -> HostName = R/3 system (i.e. NOT the XI server)
Application Server Service = sapgw00
Program ID = zabfcxi
RFC Metadata Repository Parameter
Application Server = Trx SMGW -> HostName = R/3 system (i.e. NOT the XI server)
System Number = 00
Logon User/Password = myUser and myPassword
Logon Language = EN
Logon Client = 041
Sender Agreement
I have also set up a sender agreement:
Service = R3_DEV_030
Interface = Z_RFC_GET_SO_REQUESTS2 (name of RFC imported to XI)
Sender Comm channel = RFC Sender adapter defned above
When I run the test connection in SM59 it works without any problems.
I have written a small ABAP that calls the RFC:
CALL FUNCTION 'Z_RFC_GET_SO_REQUESTS'
IN BACKGROUND TASK
DESTINATION 'Z_ABFC_XI'
EXPORTING
REQUEST_SALES_ORDERS = export.
COMMIT WORK.
When I run this it completes with no errors. However, nothing appears to be getting through to XI. I have checked the log in SM58 and find that it is failing with this error:
Commit fault: com.sap.aii.af.rfc.afcommunication.RfcAFWException: lookup
I have followed the SAP note "FAQ XI 3.0 RFC Adapter" qu.19 which states this is caused by incorrect Sender agreement but it all looks OK to me - hence why I have posted the details of it. I have also performed a full refresh of the cache but this has not fixed it either.
Is anybody able to help...?
Thanks
Andy

Hi Andrew,
Hope these threads will help you.
Error: Commit fault com.sap.aii.af.rfc.afcommunication.RfcAFWException: alt
RFC error Commit fault com.sap.aii.af.rfc.afcommunication
"maximum size of requests for one LUW has been reached"
getting error in RFC sender adapter
Error in RFC communication
Reward points if helpfull.....

Commit fault: com.sap.aii.adapter.rfc.afcommunication.RFCAFWExpection: lo

Hi,
we are doing a RFC to file scenario. it works fine in DEV and QA. but in production sporadically it shows commit fault: com.sap.aii.adapter.rfc.afcommunication.RFCAFWExpection: lo error in SM58.
I have refreshed the cache and all the necessary componets like Sender C.C, receiver C.C, Receiver determination, interface determination, sender agreement and receiver agreement is present.
how to solve this issue. its production issue. pls help ASAP

Hi,
The ECC's business system has Technical System,Client number and Logical System Name.
Also the same is reflected in BS of Integration Builder. it has the logical system, R/3 system and client number in Adapter specific identifiers.
Can you also let me know how to check the complete error message in Tcode SM58. when i double-click on the error it just shows "Commit fault: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException:lo". how can i view the full message

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 in Sm58 Commit fault: ASJ.ejb.005043 (Failed in component:

Similar Messages

Maybe you are looking for