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

Similar Messages

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

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

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

RFC Sender Channel Issue : STFC_CONNECTION

Hi All,
There has been an issue with the RFC sender channels. When SAP triggers the data, we see an error in the RFC sender channel as below
Error in processing caused by: com.sap.aii.af.rfc.afcommunication.RfcAFWException: senderAgreement not found: lookup of binding via CPA-cache failed for AdapterType RFC, AdapterNS http://sap.com/xi/XI/System, direction INBOUND, fromParty '', fromService '<ServiceName>', toParty '', toService '', interface 'STFC_CONNECTION', NS 'urn:sap-com:document:sap:rfc:functions' for channel '<ChannelName>' (channelId 7f84f67e7efe39949dc12a2f569236fb)
But the data gets processed at the very next moment.
Program ID used in the channel is same as the ID registered in SAP. Is there some configuration missing either at SAP PI or SAP R/3 system?
Regards,
Prajeet

Hi Prajeet,
please refer this wiki [link |https://wiki.sdn.sap.com/wiki/display/XI/RFC+Faqs?showChildren=false]Q19,hope this helps.
Check if you are using the same program ID in multiple scenarios. May be if you keep different the program ID names in different RFC adapters, it should resolve the error.
also check here :/people/danny.deroovere/blog/2008/02/26/change-client-in-scenarios-with-sap-business-system
Regards,
Srinivas

What is SAP recommended approach to create multiple Sender Idoc_AAE adapters channels?

Hi All,
We have more than 100 interfaces which receives Idocs from multiple SAP ECC Systems. What is the best approach to use Idoc_AAE sender adapter with multiple communication channels for One system and for multiple SAP systems as well.
Q) How many communication channels we can assign or bind to one Resource Adapter(Assume InboundRA)?
Q) What is performance impact if we create more Resource Adapter to Connect multiple SAP System?
Please share your views to create multiple Idoc_AAE sender communication channels to connect one SAP ECC Systems?
Regards,
Sreeramulu Konjeti.

Hi Vertika - It should work without changing the occurrence as it's on the sender side...
In your mapping, you would receive all the IDOC's though the occurrence is 0..1...
Just simply paste the payload in the test tab and see.. it should not throw any error..

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

JMS Sender Channel not Polling

Hi Guys,
Scenario: BEA Weblogic -
> JMS Queue -
> Sender Channel JMS -
> SAP XI -
> SAP R3
We had initially setup this scenario using MessageSelector because the provider JMS Queue had mutiple message types on it. As Murphy's law would have it, the MessageSelector stopped polling the day before go-live. Basically, if we pointed one JMS SC to the provider JMS Queue using MessageSelector it worked fine, if we pointed multiple JMS SC's no messages were being picked up from the queue. We still haven't identified why the MessageSelector functionality stopped working but as a quick work around to MessageSelector before go-live we used blog:
[/people/robert.warde3/blog/2009/03/18/pi-basics-generic-message-interface|/people/robert.warde3/blog/2009/03/18/pi-basics-generic-message-interface]
Now we have a situation where, BEA Weblogic manages the provider JMS Queue & they perform a health check 4 times a day & if they encounter a problem they bounce the server & JMS Queue service. XI and the SC seem to re-connect fine most of the time when Weblogic & JMS Queue is back up but there are times when I see a green light in RWB for the SC but it's not polling for messages on the JMS Queue. We use Hermes JMS to monitor messages on the Queue to check if there are in fact messages to be picked up & the messages are queued.
What I'm looking for is a best practice guide for how to manage this. I don't want to keep toggling between Hermes JMS & RWB to verify if the SC is in fact polling messages altho' it shows as green in RWB. Please advise. Thanks.
Regards, Trevor

Thanks Kai & Joel.
Joel, I'm not really looking to add another layer with the JMS Connector Service. For me it's just adds another possible point of failure. At the moment the message passes thru 5 systems including SAP R3 & end system & then the response comes back the same route.
Going out from SAP, the Receiver channel to the JMS queue seems to work fine. With the responses coming back, the Sender Channel seems to re-connect ok (I'm assuming) otherwise it wouldn't be green in RWB but doesn't pick up any messages. It's also an intermittant phenomenon. Manually stopping & re-starting the Sender Comm Channel fixes the problem but we won't know if there's a problem until we check if messages are being picked up from the queue.
Kai's notes led me to some things I could possibly look at like additional parameter in JMS channel config, CONNECTION_TEST_POLL (note 948016). I'm still not sure how we can make this work for us because we essentially need to bounce the JMS channel so it starts polling again in the event of a JMS Queue Provider bounce but I need to first establish that the JMS Queue was bounced.
Note 1088675 will also be irrelevant cos the channel looks like it re-connects, just doesn't poll.
Trevor

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 in sender channel:

When activating changes in IR I used to get system message as NoClassDefFoundError.Even then the componenets used to get activated.
Initially every thing was working fine with the sender channel.
It was successfully picking up the file and sending the same to receiver channel.
Suddenly after a day I sarted getting this error (below).And the file was not getting picked up.
Error in channelError: javax.ejb.TransactionRolledbackLocalException: nested exception is: java.lang.RuntimeException: java.lang.NoClassDefFoundError: com/sap/aii/af/app/mp/impl/ModuleProcessorCategories; nested exception is: javax.ejb.EJBTransactionRolledbackException: nested exception is: java.lang.RuntimeException: java.lang.NoClassDefFoundError: com/sap/aii/af/app/mp/impl/ModuleProcessorCategories
sxmb_moni message:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
There was no such error: And I had not made any changes since it was working fine.
Is this error because of the message I used to get in IR.?Was might be the cause

Hi,
Please check you message first properly all conditions supporting or not.Is message is having any exceptional chars , and Check whether your are using Async or Synch communication , respectivly the sender and receiver communication mode supporting both sides. and check your J2EE is working fine or not, Check your interface is having the module processors in sender side/receiver side is yes , those are working fine or not , those are properly imported properly or not.
these diffects may not effect the activation of components.
Also check your receiver Business system is working fine or not
And also check your receiver agreement is configured,receiver determination and interface determination all are refered same business systems or not.
,please see the following threads
Error RCVR_DETERMINATION
No Receiver Determination
Re: NO_RECEIVER_CASE_ASYNC
XPATH and RECEIVER DETERMINATION
XI 3.0 No receiver could be determined
Regards
Chilla..

IDOC_AAE sender adapter XML : missing encoding="UTF-8"?

Hi All,
We have a IDOC to JMS scenario using IDOC_AAE as sender channel.
Symptom
The IDOC whihc we have received from ECC should add XML version and encoding information to the created IDOC XML file.
Other Terms
IT SHOULD BE AS
<?xml version="1.0" encoding="UTF-8"?>
But we are getting as <?xml version="1.0" >
Can you please share your views on this ?
Regards.,
Siva

Shiva,
Add XML AnonymizerBean in target channel module to replace/Add UTF encoding.
AF_Modules/XMLAnonymizerBean
Regards
Aashish Sinha

File not able to pick while using FCC at sender channel

Hi Experts ,
we design one scenario that we need to process flat file to ECC. So we have used FCC at sender channel.
while we testing , only its showing as successfull logs in channel , but we not able to pick the file.
could you please check the below details and let me know it i missed any thing.
PFB file which need to pick.
PFA scrren shot of FCC
26.Jun 2014 #123
Country|Currency|Amount|Code|Rate
Australia|dollar|1|AUD|18.989
Brazil|real|1|BRL|9.119
Bulgaria|lev|1|BGN|14.037
Canada|dollar|1|CAD|18.836
China|renminbi|1|CNY|3.242
Croatia|kuna|1|HRK|3.623
Denmark|krone|1|DKK|3.682
EMU|euro|1|EUR|27.455
Hongkong|dollar|1|HKD|2.603
Hungary|forint|100|HUF|8.916
IMF|SDR|1|XDR|31.154
India|rupee|100|INR|33.540
Indonesia|rupiah|1000|IDR|1.668
Israel|shekel|1|ILS|5.883
Japan|yen|100|JPY|19.824
Lithuania|litas|1|LTL|7.952
Malaysia|ringgit|1|MYR|6.272
Mexico|peso|1|MXN|1.550
New Zealand|dollar|1|NZD|17.678
Norway|krone|1|NOK|3.286
Philippines|peso|100|PHP|46.019
Poland|zloty|1|PLN|6.627
Romania|new leu|1|RON|6.258
Russia|rouble|100|RUB|59.842
Singapore|dollar|1|SGD|16.137
South Africa|rand|1|ZAR|1.894
South Korea|won|100|KRW|1.986
Sweden|krona|1|SEK|2.989
Switzerland|franc|1|CHF|22.569
Thailand|baht|100|THB|62.119
Turkey|lira|1|TRY|9.469
United Kingdom|pound|1|GBP|34.361
USA|dollar|1|USD|20.179
FCC details
channel logs.
regards
raju

Hi Peddaraju,
Cross check correct source directory and file name is maintained in the sender file communication channel. If everything is fine try to restart the XPI File Adapter service in NWA.
Troubleshoot as suggested in the below thread:
File Adapter in PI not reading file from file system.
Regards,
Krupa

Jms message id in jms sender channel

Hi
Is it working for you remove id from jmsmessageid in a jms sender channel?
I can see still in the logs that my message id is starting with ID:
Florin

Hi Florin !
You mean this:
"If you have selected JMSMessageID, JMSCorrelationID, or JMSProperty and entered a JMS message ID in these fields, you should see the Remove 'ID:' Marker from JMSMessageIDindicator. Set the indicator.
This is necessary because the JMS specification stipulates that each JMS message ID starts with 'ID'. However, this conflicts with ISO-11578."
Maybe you need to reactivate your sender comm channel to force the update of cache and try again. To reactivate, just edit your adapter, make any dummy changes (e.g. change description) and reactivate again.
Then try scenario once more and check if it is working.
Regards,
Matias.

Sender Channel not working(RFCSenderR3)

Hello All,
In my XI 3.0 QA env...there is one service "RFCSenderR3" which is not showing any messages in message monitoring ,but if i check in Communication channel monitoring for that service it shows as :
Sender channel 'RFCSenderR3' for party ",service'RQ1'
ERROR can not instantiate RfcPoolException:error initializing
RfcServerPool:com.sap.aii.af.rfc.core.repository.RfcRepositoryException:can not connect to destination system due to :com.sap.mw.jco.JCO$Exception:(103) RFC_ERROR_LOGON_FAILURE:Mandante 101
Here RQ1 is the R3 reciever system.
And i have checked rfc connection from R3 end which shows it is fine..
Can any one suggest me ,exactly wat need to be checked to solve this problem .And I am not sure what to check from R3end also....
can any one guide to me ..
Best Regards
raki

Hello All,
Thanks for helping yaar,the problem got resolved .
After verifying the user Id & password , I restarted that particular channel from Communication channel monitoring.Then it got worked with successful execution.
Thanks one and all for helping me out.
Best Regards
Rakesh

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

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

Similar Messages

Maybe you are looking for