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

Similar Messages

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

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

T rfc error in SM58

I m getting " :: 000 " error in SM58 while sending ORDERS
I have tried everything, even recreated all ALE configuration settings.
What could be the reason?
With the same settings, I could transfer MATMAS but its comign only for ORDERS
regards,
Nikhil.

To track the IDOC in SAP XI you need some authorizations to execute IDX5
To start the XI message monitor in the remote system
SXMB_MONI with ACTVT = 03
To start the IDoc monitor in the remote system
SXMB_MONI with ACTVT = 03
Authorization for function groups:
BDMON
BDMT
IDOC_TRACING
SXMB_MONI
Trigger the IDOC in the R/3 system like do the scenario like IDOC to file or File to IDOC.
/people/kamalkumar.ramakrishnan/blog/2008/02/13/monitoring-the-idoc-adapter-in-xipi-using-idx5

Function module not executing in background due to Transactional RFC error in SM58

Hi Team,
I am executing a report which calls a function module in background.This in turn creates a LUW which should eventually get cleared once the processing is completed through commit statement.
However LUW is going for an error whenever it gets executed through commit statement.
The error message in SM58 is
Error msg : Conversation
<init> not found / CPIC-CALL: 'ThSA PCMRCV' : cmRc=19 thRc=
However when I try to excecute the function module in foreground, it works correctly as expected.
Please note that the same report is being used for various clients and the function module is working fine in all others.Hence, I am expecting that thers is no issue with the code.
Is there some settings which we are missing here.
Please provide me your valuable inputs.

Hi Divy,
It appears to network issue. please use below SAP note to perform network analysis using NIPING.
SAP note 500235 - Network diagnosis with NIPING
Hope this helps.
Regards,
Deepak Kori

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

IDoc_AAE Synchronous error in SM58

Dear friends,
I configured IDoc_AAE sender and receiver side. I tested this with success. The next step was to configure an Async-Sync scenario. I configured my scenario according the following Blog:
Request/Response Bean for IDOC_AAE adapter
My scenario is that I want to take an IDOC from ECC and send it to SOAP which is synchronous one and I map the response data to a ALEAUD and send it back to ECC.
My configuration looks like following:
I use the following Beans and parameters in the sender Idoc communication channel:
Now when I want to send an Idoc from ECC I get the following error in SM58:
Commit fault: ASJ.ejb.005043 (Failed in component: sap.com/com.sap.aii.ad
And I get the following error in NWA:
Error in look up for binding. Reason: com.sap.aii.af.service.cpa.CPAObjectNotFoundException: Couldn't retrieve inbound binding for the given P/S/A values: FP=;TP=;FS=BS_******;TS=;AN=IDOC Name;ANS=urn:sap-com:document:sap:idoc:messages;
So If I test this idoc asynchronous it works fine and if I put this Idoc in an Outbound Sync SI it doesn't work and I get an error in SM58.
Do you have any suggestion why it doesn't work and can you please tell me If I can achieve my scenario with this configuration? As I read in the following thread (it was mentioned by Indrajit that we cannot use an Idoc adapter in the ResponseOneWayBean)
ResponseOneWay Bean unable to find the receiver channel
If its true so what do I can do to achieve this scenario? I also can use an asynchronous ABAP Proxy back to ECC instead of an ALEAUD.
You help would greatly appreciated,
Thank you in advanced,
Kind regards,
John

Hi
Unfortunately the way you are trying to get the acknowledgement idoc will not work.The request response bean in the sender idoc adapter only work for
Adapter Namespace: http://sap.com/xi/XI/System.
Adapter Type: File
The same is clearly mentioned in the document you have referred. But there is another alternative approach which you can use to get the acknowledgment back.
You have to use the request response bean in the receiver adapter( say SOAP). In that case the receiver application will trigger an response message with the interface name you have provided in the response bean.
You have to create one more ICO or scenario for that interface triggered by receiver adapter and use the mapping in PI which will convert that in ALEAUD idoc.
Following things needs to keep in mind
You have to use virtual receiver for the second scenario.

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

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 destination error in SM58

Hi,
We are getting an error in SM58 "P85040 does not exist".
What could be the reason for this error in PI system?
When I checked, there is no RFC destination configured with the name P85040. Also there is no communication channel configured with the RFC destination parameter P85040.
Kindlly help.
Thanks,
John

Hi John,
The reason can be the host name you are assigning is not existing.
In RFC destination the host name is for that particular client which is pointing to IP address not to the logical system. You can choose name of RFC destination same as of your logical system.
You can get the host name by login to SAP system and the using MENU ... System->Status and in lower right corner you can find it.
Sachin
Edited by: Sachin Dhingra on Dec 18, 2008 1:18 PM

Rfc to file scenario error in sm58

rfc to file scenario error in sm58
i get the error as com.sap.aii.afccommunication.RfcAfwException
:look up of alternative

hey
>>i have a doubt do we have to use
starting new task or back ground destination
well it depends upon the logic ur gonna implement,both are used for async RFC so u have to see ur requirement and then decide.
have a look at the following
http://help.sap.com/saphelp_nw2004s/helpdata/en/22/042578488911d189490000e829fbbd/frameset.htm
thanx
ahmad

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!

SAP R/3 - XI: Commit fault com.sap.aii.af.mp.module.ModuleException

Hi -
We have an integration setup between SAP R/3 4.7C and SAP XI -
It uses background queues - and in our development environment, on the call to XI, we are receiving the error message:
Commit fault com.sap.aii.af.mp.module.ModuleException: call to messaging
The queue then goes into SYSFAIL status.
This is occurring on all of our integrations between R/3 and XI - which has been previously working -
I have been working w/ our Basis guy & he said that all his checks to both systems look ok.
Do you have any pointers on what to look at or check out?
Your help is very appreciated!
Thanks,
Michelle

Hi Michelle,
Please check if the background Xi database to which your transactions are committed is full. In case it is, you would need Basis help to archive them, before you proceed. Please check your dump for the same.
cheers,
Prashanth
P.S Please mark helpful answers.

Sender RFC error

Hi guys,
I'm doing an RFC to File async scenario just as mentioned in the blog
/people/swaroopa.vishwanath/blog/2006/12/28/send-rfc-to-sap-xi-150-asynchronous
and i have done the configurations also from the blog
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
Now when i execute my report to call the bapi with the rfc destination of my XI server, i'm getting error in sm58 of R/3 as Bean Z_BAPINAME not found. I'm not getting any messages in to XI also..
Please help me on this guys
Thanks
Varun

When i'm creating RFC destination in R/3 which gateway host and gateway service should i enter??
values from R/3 should be entered.
These you can find in transaction smgw, in menu Go To> Parameters> display
here you will get values for gateway host and gateway service of R/3
you should create RFC dest of type TCP/IP, Give a program ID .. it could be anything. This program ID you will have to provide in RFC adapter. Activate the adapter
Then Try to activate RFC dest at R/3.
For more refer
/people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009

RFC Error in SM58 Commit fault

Similar Messages

Maybe you are looking for