Unwanted Alerts in Adapter Framework

Hi,
We have a scenario where we process 1000's of messages for the same receiving system. On the receiver adapter we append to one file. This causes file locking issues when multiple messages attempt to write to the same file. On the 2nd or 3rd retry these messages writes successfully to the file.
The issue is that the file locking causes unwanted alerts. Is there a way to configure or change the alerting so that alerts are raised only when it goes to a final status of "System Error".
We cannot make the sender EOIO for performance reasons. I tried using an adapter module to change the QoS to EOIO on the FTP/File receiver adapter, but it seems to be too late at that point. The message is already put into a receiver queue.
Thanks.
Best Regards,
Duke

From my understanding, if the Suppress Multiple Alerts is checked, then no further alerts are generated of a rule until the first alert has been confirmed.
But, what we would like to do is not to even generate an alert until it goes to "System Error" status after all retries have been exhausted.
Thanks.
Best Regards,
Duke

Similar Messages

Alerts in Adapter Framework not sending emails - PI 7.1 SP 7

Hi All,
I am on PI 7.1 SP 7. I have created Alert Category for Adapter Errors, but they are not delivering any emails. I have checked the logs in SXMSALERT_LOGREADER. It says the following
Alert Category <ALRT_NAME> in rule Adapter Exception not yet confirmed. Skip creation of new Alert.
Rule Active - Yes
Suppress Multiple Alerts - Not Checked
Connected to Message - No
So all other parameters are '*'
Adapter Engine is checked.
Can anybody please help?
Thanks,
Geetha

Heyy,
Check the same Discussion here
Alert Category in rule not yet confirmed.
Re: Alert is not triggered
Regards

Alerts from the Adapter Framework

Hello,
I have configured the CCMS to monitor XI message processing. For the Integration Server that works fine. But for the Adapter Framework I don't receive any alerts. I use the CIDX Adapter and I would like to receive an alert, when a RAE has been received or when an RA is overdue. Has anybody an idea if this is possible?
Cheers,
Jürgen

Hi Andreas,
We are on XI 3.0 SP9 and are not receiving email alerts when the J2EE adapters fail in the RWB. We only receive email alerts when messages fail in the ABAP integration server.
Are you implying, from your previous post, that alert configuration in the RWB, although available before SP11, will only trigger alerts from adapter framework errors at SP11 level or higher?
Regards,
Dave

Alerts not getting triggered from Adapter Framework

Hi,
I have done the following steps for the Alerting:-
1. In configuration of RWB, activated monitoring for XI integration server & XIAdapterFramework and set the monitoring level to 'HIGH'.
2. Scheduled the Report 'SXMSALERT_PROCESS_DATA_GET' on ABAP stack.
3. In the 'further settings' link in End-to-End monitoring, activated the monitoring and set the frequency.
4.Created an alert category using t-code 'ALRTCATDEF' and assigned fixed users(myself) to it.
5.Defined an alert rule with '*' in all conditions and 'No restrictions' for the question 'Where did the error occur'.
Finally after all the steps:-
I am able to receive the alerts in the inbox -
a) by running the test report 'RSALERTTEST'
b) from a control step in BPM.
However, alerts are not getting triggered for an error in the Adapter Framework. (an exception in the Adapter Channel)
When i debugged the SXMSALERT_PROCESS_DATA_GET report, there was step where it was looking for process instances in table 'SSPICSPRHD' which was empty and the alert error log said -
 No process instances found for process type ID: 26460B43EB934C4C9ABBE9627380A89E ( XIDomain: domain.00.hqdvsapxi01 )
Any help/hint is welcome !!!
Thanks & Regards,
Renjith.

Hi,
https://www.sdn.sap.com/sdn/weblogs.sdn?blog=/pub/wlg/1382. [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken]
I think this blog will be of help to you..
Cheers,
Divya

Exception caught by adapter framework: unable to create a socket

Hi All,
I am using Idoc to XI To SOAP scinario. I got a alert asying that some messsage id is error. When i am trying to monitor that massage by taking help of the messgae id in the alert the message was successful in the SXMB_MONI,. Then i Went to message monitoring There the message statu was syetem error. Errror log is *Exception caught by adapter framework: unable to create a socket*. The communication channel was inactive wehere as the statsu of the channel was active in the directory... what is the reasonm for this error. and how to resilev this.

As pointed already, a socket exception occurs when then message cannot pass the Firewall settings....there will be a port configured to send message to the SOAP receiver.....ask network guys to make relevant settings so that the port is free from Firewall restrictions.
@Supriya --> Active/ Inactive status of the channel in ID and in CC monitoring are different things.
To change the status of your CC in RWB --> Stop & Start your SOAP CC....the channel will remain inactive till no message is passed through it....once a message is passed the status will change to success/ error.
You can also change the CC status to Automatic.
Regards,
Abhishek.

Message status "Holding" - Message monitoring adapter framework

Hello,
We have some messages with the status "Holding" in a queue in the message monitoring in the adapter framework.
Normally you have to restart the first message of that queue. The message with the status "system error". Unfortunately this message is not available anymore because it is older than 30 days and the retetion period is 30 days.
I already read the blog about "[How to deal with stuck EOIO messages in the XI 3.0 Adapter Framework|http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417100)ID1887311350DB01819286872323159351End?blog=/pub/wlg/3566]"
The blog does not mention what to do when the first message (sequential number) is not available anymore.
Is it possible to restart the messages in the queue in that case?
Thanks
Kind regards
Frank

Unfortunately this message is not available anymore because it is older than 30 days and the retetion period is 30 days.
I assume that the message was deleted.....in this case the next message in the queue will be blocking the queue....so try resending this message....even the blog mentions that you either solve the error or cancel the message....so now start from the second message....if possible solve the error for this message....if not possible to resolve then cancel it so that rest of the queue gets processed
From the blog:
Now the erroneous message is the first message in the display. You can look at the error reason, try to fix the problem and
resend or cancel the message to release the queue.
Regards,
Abhishek.

PI 7.11: Adapter Framework caught exception: null

Hi,
I've a ABAP Proxy - to - SOAP scenario.
Message mapping works.
In the communication channel monitor I get the following error:
MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException
Adapter Framework caught exception: null
In the log viewer in NWA I see the following two messages:
Marked transaction for rollback for meesage 516e304f-b083-8e3e-e100-00000a01095f(INBOUND). Reason: <null>
Caught exception com.sap.engine.interfaces.messaging.api.exception.MessagingException from application code with msgKey: 516e304f-b083-8e3e-e100-00000a01095f(INBOUND)
The payload for calling SOAP receiver looks like that:
<m:setEmployee xmlns:m="http://test.com" xmlns:fo="http://www.w3.org/1999/XSL/Format">
 <ns1:e xmlns:ns1="http://test.com">
 <address_Mail_Incoming_Type>
 <email>test.com</email>
 <phone>7890</phone>
 </address_Mail_Incoming_Type>
 <badge_ID>123</badge_ID>
 <cost_Center>321</cost_Center>
 <date_Hired>1980-01-01T00:00:00.000Z</date_Hired>
 <date_Of_Birth>1950-01-01T00:00:00.000Z</date_Of_Birth>
 <department>123</department>
 <division>ABC</division>
 <employee_Category>A</employee_Category>
 <employee_Code>1000</employee_Code>
 <employee_Id>1000</employee_Id>
 <employee_Status>ACTIVE</employee_Status>
 <first_Name>A</first_Name>
 <last_Name>B</last_Name>
 <letter_code_3>FRI</letter_code_3>
 <location>123</location>
 <position>123</position>
 </ns1:e>
 </m:setEmployee>
When I copy this payload into SOAP UI (surrounded by <soapenv:Envelope>, <soapenv:Header> and <soapenv:Body>), the WS call works.
The URL for the receiving CC should be ok (same as in SOAP UI), the "Do not use SOAP Envelope" checkbox is not flagged.
What can be the reason for that error message?
Thanks in advance!

I've now changed the setting of the external definition to "Using RPC style", but I'm still running into the same error than before:
10.02.2012 14:51:03 Information SOAP: sending a delivery error ack ...
10.02.2012 14:51:03 Error Adapter Framework caught exception: null
10.02.2012 14:51:03 Error MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException
10.02.2012 14:51:03 Information SOAP: sent a delivery error ack
10.02.2012 14:51:03 Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException.
The payload of the CC looks exactly the same than before:
<?xml version="1.0" encoding="UTF-8"?>
<m:setEmployee xmlns:m="http://test.com" xmlns:fo="http://www.w3.org/1999/XSL/Format">
 <ns1:e xmlns:ns1="http://test.com">
 <address_Mail_Incoming_Type>
 <email>test.com</email>
 <phone>123</phone>
 </address_Mail_Incoming_Type>
 <badge_ID>123</badge_ID>
 <cost_Center>123</cost_Center>
 <date_Hired>1990-01-01T00:00:00.000Z</date_Hired>
 <date_Of_Birth>1950-01-01T00:00:00.000Z</date_Of_Birth>
 <department>123</department>
 <division>ABC</division>
 <employee_Category>PERM</employee_Category>
 <employee_Code>1000</employee_Code>
 <employee_Id>1000</employee_Id>
 <employee_Status>ACTIVE</employee_Status>
 <first_Name>A</first_Name>
 <last_Name>B</last_Name>
 <location>ABC</location>
 <position>123</position>
 </ns1:e>
</m:setEmployee>
If I copy that payload (without <?xml version="1.0" encoding="UTF-8"?>) into SOAPUI (surrounded by SOAP envelope), the WS call works without any problem.
Why doesn't it work from PI?
Another question:
Why is it putting <ns1:e> into the payload of the new interface and <ns0:e> for the existing interface (which is working, see Re: PI 7.11: Adapter Framework caught exception: null)?
Could that be the reason why data is not sent properly to the SOAP receiver?

Adapter development on Adapter Framework PI 7.1

Hi experts,
This is relative to PI 7.1 EHP1.
I am learning how to develop an Adapter on Adapter Framework. On help I found this link: Example Adapter and Example Module. On example´s folder (see help link above) I found only a jar called com.sap.aii.adapter.sample.ra.jar, inside that jar there is only classes, no source code, and there is no index.html like it is written on help.
I think something is missing, or not?
Best Regards,
Gabriela

Hi Gabriela,
I am trying to develop a Sample Java Adapter as you did earlier. I have been through SAP Note 1004000 as well. But i couldn't find the "src.zip" as mentioned in the Note. Please help me on it.
Warm Regards,
DNK Siddhardha.

Messages stuck in queue AFWRecv of Adapter Framework

Hello,
Messages stuck in queue AFWRecv of Adapter Framework in our production system(trace in RWB: "to be delivered")
in URL http://xxxxxxx:50000/MessagingSystem/monitor/systemStatus.jsp we can see:
Queue Info
Queue Name isStarted QueueSize ThreadCount (working) MaxThreads
AFWCall true 0 0 (0) 20
AFWRecv true 954 10 (10) 10
AFWRqst true 0 0 (0) 20
AFWSend true 0 0 (0) 10
We have tried to resend the first message but that´the result:
Time Stamp Status Description
2010-10-09 11:24:06 Success The message was successfully received by the messaging system. Profile: XI URL: http://xxxxxxxxx:8100/MessagingSystem/receive/AFW/XI
2010-10-09 11:24:06 Success Using connection AFW. Trying to put the message into the receive queue.
2010-10-09 11:24:06 Success Message successfully put into the queue.
2010-10-11 00:01:46 Success Recovering from loss of connection to database; message loaded into queue by recover job: System Job (Failover Recovery)
2010-10-11 02:48:16 Success System Startup: Message successfully loaded into queue: AFWRecv.
2010-10-13 11:03:19 Success Admin action: Trying to redeliver message.
2010-10-13 11:03:46 Success Admin action: Trying to redeliver message.
Since then it stucks there...
Any help would be apreciated....

Hi,
Go to the runtime workbench --> Message Monitoring --> Click on the 'Configure Table Columns' > Check Sequence ID, Serialization Context & Sequential Number options.> and then click 'Apply'.
Then in the 'Serialization Context' column you will get the queue ID for the stcuk message.
Take that value and click on the 'Show additional Criteria' option on the top and put this value in the 'Serialization context' parameter. Also,select the start/end date as 'This year' --> start.
You will get all the messages stuck in that particular queue for this yoear, try to rectify them, so that your message will be processed.
-Supriya.

Problem with Adapter Framework

Hello All,
Our env. is XI 3.0 and for our development system all the interfaces which are connecting to R3service are getting failed .
And the audit log for one of the interface is shows
Delivery of the message to the application using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Exception thrown in method process. The transaction is marked for rollback.: com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback..
MP: exception caught with cause com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback.
Can any one help me out to resolve this issue..
Best Regards
Raki

Hello Barry,
Thanks for the update.
The issue has been resolved by applying two more patches of SPS19.
Problem Resolution:
When we apply only one patch Adapter Frame Work Core (SAPXIAFC19P_19-20000272.SCA (Adapter Framework Core 19)), there is chance for some sort of inconsistences in the system and the interfaces relating to Adapter Frame work gets failed from reciever end(R3services).
To avoid such problems (inconsistences) we need to apply the patches which are related to that.And those are .
SAPXIAF19P_9-20000273.SCA Adapter Framework for SP19.
SAPXITOOL19P_10-20000274.SCA) Cumulative Patch tool for SP19
Thanks for all helping me out to resolve the problem earliest.
Best Regards
Raki

Error on Adapter Framework with Seeburger component

Hi,
I have the Generic EDI component from Seeburger Adapter, and I have a communication channel using the FTP Adapter from Seeburger with the module localejbs/Seeburger/solution/generic-edi, and when execute the communication channel, I have an error with the solution, the error is:
"Exception caught by adapter framework: Path to object does not exist at solution, the whole lookup name is localejbs/Seeburger/solution/generic-edi.".
I see the Seeburger documentation about installation and configuration from FTP Adapter, but I don´t find information about this error, somebody help me please with information about this error, what configuration I need review or where find documentation about this problem?.
We post a note about this problem on the OSS, the content of the note is:
We have installed the Seeburger's FTP adapter in SAP XI.
A communication Channel is calling this adapter nd executing a module called localejbs/Seeburger/solution/generic-edi. When the adapter is called the next error is shown;
Exception caught by adapter framework: Path to object does not exist at
solution, the whole lookup name is localejbs/Seeburger/solution/generic-edi.
Delivery of the message to the application using connection
FTP_http://seeburger.com/xi failed, due to:
com.sap.aii.af.ra.ms.api.RecoverableException: Path to object does not
exist at solution, the whole lookup name is
localejbs/Seeburger/solution/generic-edi.:
com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at solution, the whole lookup name is
localejbs/Seeburger/solution/generic-edi..
Also, the host-ftp solution was used instead of the generic-edi with the same result.
The system we have is SAP PI 7.0 SPS09 with Seeburger 1.6.
Thanks and greetings,
Hervey.

Hi,
I have the same problem. What was the solution?
Regards
Kristian

Adapter Framework not showing in the SLD or RWB

Hi,
I am on XI3.0, This is referring the the central J2EE adapter.
The adapter framework/engine is not showing up as a component in the runtime workbench or under the technical systems of type XI in the SLD. All other XI components are showing up in both places. What could be causing this? When I go the the adapterframework monitor itself, the adapters show as active.
Regards,
Mrudula

I am not sure, but, can you check whether the exchange profile and the SLD Data Supplier service is configured properly on the central J2EE Engine where the Adapter Framework is running.
Warm regards,
Venki.

Multiple host adapter framework caches in PI 7.1

When I go look at the caches in my PI system, I get multiple host adapter framework caches. That is, when I navigate to http/<host>:50000/dir, then select "Administration" in the upper right hand corner, and then select "Data Cache Overview" I see the following:
af.<sid1>.<hostname1>
af.<sid2>.<hostname2>
Integration server (ABAP) --> this is fine
Mapping Runtime Java --> points to <hostname1>
Mapping Runtime Java --> points to <hostname2>
I just did a system copy (export/import) and I changed all of the parameters. Unfortunately, not soon enough.
Any help is appreciated...

Dumb question:
Do you delete the integration server under the SLD technical systems? That is, "Integration Directory, Adapter Engine, Integration Repository, and RWB (these are all that shows up). If I delete the adapter engine there (it is assigned to the wrong domain), is that the right way?
Or do you do it in the "CIM Instances" --> Class --> XI Adapter Framework (3) entry for the wrong server domain?

Exception caught by adapter framework: No configuration / default adapter specified for EDISeparator

Hello Experts,
I am configuring the scenario ( AS2 to EDISeparator and EDISeparator to IDOC ).
Can you please help me with the error below which is from the either the EDISeparator Receiver channel or the EDISeparator Sender channle.
09.06.2014 17:52:18.709
Information
Message is encrypted with 1.3.14.3.2.7 algorithm
09.06.2014 17:52:18.778
Information
AS2 Message is signed with SHA1 (1.3.14.3.2.26) algorithm
09.06.2014 17:52:18.779
Information
AS2 Message message signature is validated, signer ID is X509CertSelector: [ Serial Number: 1624063516 Issuer: CN=Mendelson AS2 TEST,OU=Integration,O=Mendelson,L=Berlin,ST=Unknown,C=GE matchAllSubjectAltNames flag: true ]
09.06.2014 17:52:18.784
Information
AS2 document size is 350 Bytes
09.06.2014 17:52:18.784
Information
Payload charset converted from ISO-8859-15 to ISO-8859-15
09.06.2014 17:52:18.785
Information
B2B EdifactConverterModule : EDI format detected as EANCOM
09.06.2014 17:52:18.785
Information
B2B EdifactConverterModule: Message will be read as ISO-8859-1.
09.06.2014 17:52:18.785
Information
MP: processing local module localejbs/EdifactConverterModule
09.06.2014 17:52:18.785
Information
0}: The module-paramteter "eancom.subversion.prefix" is not set. Using default value "false"
09.06.2014 17:52:18.786
Information
0}: The module-paramteter "eancom..audit" is not set. Using default value "false"
09.06.2014 17:52:18.791
Information
MP: processing local module localejbs/CallSapAdapter
09.06.2014 17:52:18.791
Information
Application attempting to send an XI message asynchronously using connection AS2_http://sap.com/xi/XI/AS2
09.06.2014 17:52:18.792
Information
Trying to put the message into the send queue
09.06.2014 17:52:18.831
Information
Message successfully put into the queue
09.06.2014 17:52:18.831
Information
The application sent the message asynchronously using connection AS2_http://sap.com/xi/XI/AS2. Returning to application
09.06.2014 17:52:18.836
Information
MIC (DeJYUIusqQj6aaYRASdHhAo+4J0=) is calculated using SHA1 algorithm.
09.06.2014 17:52:18.838
Information
The message was successfully retrieved from the send queue
09.06.2014 17:52:18.843
Information
Message status set to DLNG
09.06.2014 17:52:18.845
Information
MDN is succcessfully signed with SHA1 (1.3.14.3.2.26) algorithm
09.06.2014 17:52:18.859
Information
Trying to put the message into the send queue
09.06.2014 17:52:18.912
Information
Message successfully put into the queue
09.06.2014 17:52:18.913
Information
The message was successfully retrieved from the send queue
09.06.2014 17:52:18.918
Information
Message status set to DLNG
09.06.2014 17:52:18.961
Information
Trying to put the message into the send queue
09.06.2014 17:52:19.001
Information
Message successfully put into the queue
09.06.2014 17:52:19.001
Information
The message was successfully retrieved from the send queue
09.06.2014 17:52:19.006
Error
MP: exception caught with message No configuration / default adapter specified for EDISeparator
09.06.2014 17:52:19.006
Information
Delivering to channel: B2BSE00002_O2C_ORDERS_VANS_PO_WRITE_EDISeparator
09.06.2014 17:52:19.006
Information
Message status set to DLNG
09.06.2014 17:52:19.009
Error
Exception caught by adapter framework: No configuration / default adapter specified for EDISeparator
09.06.2014 17:52:19.010
Error
Transmitting the message to endpoint <local> using connection AS2_http://sap.com/xi/XI/AS2 failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.Exception: No configuration / default adapter specified for EDISeparator
09.06.2014 17:52:19.015
Information
The asynchronous message was successfully scheduled to be delivered at Mon Jun 09 17:57:19 CEST 2014
09.06.2014 17:52:19.015
Information
Message status set to WAIT

Hello Ruchir Sinha and Dimitri Sannen,
I think I have progressed a bit. Just unsure of the usage of the Module configuration .I now get a new error (see below) and the updated config details are :
Sender Interface :
Receiver Interface :
Sender AS2 config :
Receiver EDISeparator config :
Sender EDISeparator config :
Receiver IDOC config :
IDoc details configured but not added in this document
16.06.2014 11:52:35.414
Information
The message was successfully retrieved from the send queue
16.06.2014 11:52:35.420
Information
Delivering to channel: B2BSE00002_O2C_ORDERS_VANS_PO_WRITE_EDISeparator
16.06.2014 11:52:35.420
Information
MP: processing local module localejbs/ModuleProcessorExitBean
16.06.2014 11:52:35.420
Information
Message entered AF MP exit bean and will now be passed to the JCA adapter
16.06.2014 11:52:35.420
Information
Message status set to DLNG
16.06.2014 11:52:35.433
Information
UNA segment UNA found
16.06.2014 11:52:35.444
Information
Parsed UNB segment 333333333/014 to 111111111/014
16.06.2014 11:52:35.445
Information
Parsed UNH segment ORDERS D96A
16.06.2014 11:52:35.514
Information
Searching sender channel for Eancom message part message with Message type ORDERS, Message version number D, Message release number 96A, Interchange sender identification 333333333, Interchange sender identification code qualifier 014, Interchange recipient identification 111111111, Interchange recipient identification code qualifier 014, Message Subversion EAN008, Message Agency UN
16.06.2014 11:52:35.579
Information
Sender channel (Channel) keys: ObjectId=7abf551ddbb638268f91af80ec1c04c8 values: ToPartySchema= Attributes=(Attributes:Channel:EDISeparator:INBOUND) values: edisep.advanced=false snd.interchangeSenderId=.* snd.tradacommessagetype=.* snd.xpath= snd.xpath.value= snd.filterCondition=equal snd.edifactMessageReleaseNumTxt= snd.tradacomMessageTypeUsingFreeText=false snd.eancomMessageReleaseUsingFreeText=false snd.eancomMessageVersionFreeText= snd.odetteMessageType=.* snd.edifactMessageVersion=.* snd.xml.splitPath=null snd.eancomMessageVersion=.* snd.odetteMessageVersion=.* snd.edifactMessageRelNumUsingFreeText=false snd.otherVersionReleaseIndustryIdentifierCodeEnabled=false adapterStatus=active snd.vdaMessageType=.* snd.eancomCONTRLMessageRelease=3 snd.odetteMessageTypeTxt= snd.tradacommessageversion=.* snd.edifactMessageVerNumUsingFreeText=false snd.edifactMessageTypeUsingFreeText=false snd.xpathUsingFreeText=false snd.interchangeSenderIdCode=.* snd.otherVersionReleaseIndustryIdentifierCode=.* snd.odetteMessageTypeUsingFreeText=false snd.tradacomreccode=.* snd.edifactMessageVersionFreeText= snd.edifactInterchangeRecipientIdentification=.* eoio.sequenceId= snd.edifactMessageTypeTxt= snd.odetteMessageVerNumUsingFreeText=false snd.eancomMessageVerNumUsingFreeText=false snd.interchangeReceiverId=.* snd.eancomMessageRelease=.* snd.tradacomsendername=.* snd.tradacomMessageTypeTxt= snd.vdaLieferantenNummer=.* snd.interchangeReceiverIdCode=.* snd.edifactInterchangeSenderIdentificationCode=.* snd.odetteMessageVersionFreeText= snd.versionReleaseIndustryIdentifierCode=.* snd.edifactInterchangeSenderIdentification=.* snd.edifactMessageType=.* snd.eancomMessageType=.* snd.xpathTxt= snd.vdaMessageTypeTxt= deliverySemantics=eo snd.eancomMessageReleaseTxt= snd.plainmessagetype=.* snd.xml.split=false snd.edifactMessageRelease=.* snd.vdaMessageTypeUsingFreeText=false snd.tradacomrecname=.* edisep.addParameterParams=TableData: edisep.addParameterParams {} snd.encoding=iso885915 snd.vdaKundenNummer=.* snd.tradacomsendercode=.* snd.edifactCONTRLMessageRelease=3 snd.edifactInterchangeRecipientIdentificationCodeQualifier=.* snd.transactionSetIdentifierCode=.* Service=ASJAVA_DX5 Channel=B2BSE00002_O2C_ORDERS_PO_ECC_READ_EDISeparator EngineType=CA Party= TransProt=XI TransProtVers=1.0.0 FromPartySchema= FromPartyAgency= Direction=I MsgProt=EANCOM MsgProtVers=1.0.0 EngineName= AdapterType=EDISeparator AdapterSWCV=06c536e6fafe11e0bb1cea8f0a4290b1 ToPartyAgency= AdapterNamespace=http://sap.com/xi/XI/EDISeparator found. New message ID is f18894a8-f53b-11e3-a748-00001e96c7e2
16.06.2014 11:52:35.586
Error
MP: exception caught with cause javax.resource.ResourceException: com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message cannot be dispatched: Message cannot be dispatched: Error during processing local class: localejbs/GenericConverterModule
16.06.2014 11:52:35.586
Error
Message could not be forwarded to the JCA adapter. Reason: com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message cannot be dispatched: Message cannot be dispatched: Error during processing local class: localejbs/GenericConverterModule
16.06.2014 11:52:35.590
Error
Exception caught by adapter framework: com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message cannot be dispatched: Message cannot be dispatched: Error during processing local class: localejbs/GenericConverterModule
16.06.2014 11:52:35.591
Error
Transmitting the message to endpoint <local> using connection AS2_http://sap.com/xi/XI/AS2 failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax.resource.ResourceException: com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message cannot be dispatched: Message cannot be dispatched: Error during processing local class: localejbs/GenericConverterModule

Exception caught by adapter framework

Hi
My scenario is based file -->RFC with BPM (parforEach) and multimapping.
File adapter is picking data according to input file, but RFC couldn't able to process each split data. I am gettign following error.
2006-09-11 10:39:07 Error Exception caught by adapter framework: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was <null>
2006-09-11 10:39:07 Error Delivery of the message to the application using connection AFW failed, due to: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was <null>.
Any idea how to resolve this issue..!
Regards
Sankar!

Hi..
Does this way i mapped file to BAPI, is this correct way ?
does we change the BAPi structure like this in target side?
Source Structure: TargetStructure
Messages (1:1) Message(1:1)
Message1(1:1) Message1(1:1)
MT_Request(1:1)
Recordset(0:U) --> BAPI_INCOMINGINVOICE(0:U)
HDR (0:1) HeaderData(1:1)
LINEITEM(0:U)
 field1(0:1) ---> filed1(0:1)
 field2(0:2)
 HDR--->GLACCOUNTDATA(0:1)
LINEITEM(0:U)---> item(0:U)
field3(0:1) ---> field(0:1)
field4(0:1) ---> field2(0:1)
and my BPM is :
Receive>Transfromation->Block with asyncSEND--->
Receiver : File_MI
Trasformation: IM, sorec: File_AI and tar: BApi_AI
Block -->parForeach, multi: BAPI_AI, curr: BAPI_AI
asyncSend-->BAPi_AI
Note: My input file should have various headers with associated line items...!
Thanks,
Sankar!

Unwanted Alerts in Adapter Framework

Similar Messages

Maybe you are looking for