Random error IN RFC sender channel

Hi all,
Please note that in two different scenarios Same busness system is used but different Sender RFC channels and different Functional modules. In spite of this a random error is occuring. At times scenario works fine and some times it gives error.
"Wrong Sender Agreement:The Sender agreement doe
ot have channel Func_sender_cc"
No error report in SXMP_MONI.
Any clue please.
Regards
venkat

Hi,
Now it is clear very much there is no need of registaring programID specifically any where. Any programID first mentioned in Comunication channel and actived and then defined rfc destination using SM59 with same programID gives successfull test result.
Also for different RFC senders Different ProgramID shall be used to avoid the type errors faced by me.
Hope this helps all
cheers
Venkat

Similar Messages

Error in RFC Sender Adapter

Hello Experts,
Right now i m working on the scenario SRM -> XI -> 3rd party system.
Here i want to send data from SRM to XI, and for that i m using Sender RFC Adapter.
I have configured RFC Sender channel in XI and created RFC Destination into the SRM system, and when i m trying to test the RFC Destination at that time it is giving me error saying that "program POACK_GEE not registered".
Can anyone help me out in this issue... its very urgent...
so waiting for your replies...
Thank you very much,
hetal

Hi Michal,
I already had a look into that... but i didnt find the solution
The error coming is like this....
ERROR program POACK_GEE not registered
LOCATION SAP-Gateway on host <host name> / <service name>
DETAIL TP POACK_GEE not registered
COMPONENT SAP-Gateway
COUNTER 1270
MODULE gwr3cpic.c
LINE 1609
RETURN CODE 679
SUBRC 0
RELEASE 640
TIME Mon May 7 16:45:48 2007
VERSION 2
I have followed all the steps then also i dont know y it is not working...

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

Program Id in RFC sender channel

Hi Experts,
Can the same Program ID be used in 2 different RFC sender channels? I do not want to use the existing RFC sender channel. Please le me know.
Thanks
Suma

Hello.
I can't understand what are you trying to implement here, but here is the correct way to work with RFC CC
1. every sender CC should have the XI as the gateway server. the program ID is then registered on the xi server.
2. If you want to call the same interface from different ECC systems, you will create an RFC destination in each of them, containing the XI as the gateway and the same program ID. in that case you fill the RFC Metadata Repository Parameter with one of the ECC systems (as the RFC have the same metadata in both servers - it doesn't matter which one is written there) look here for more information: [Configuring the Sender RFC Adapter |http://help.sap.com/saphelp_dimp50/helpdata/EN/67/6d0540ba5ee569e10000000a155106/frameset.htm]" and focus on the sentence: "The RFC metadata repository parameters identify the SAP system containing the repository for the RFC metadata. This does not necessarily have to be the sender system" (:
3. If you want to use different interfaces - you will use 2 program IDs, 2 sender channels, 2 sender agreements.
hope it helps.

How many RFC Destinations / RFC Sender Channels

Hello everybody!
I have several RFC --> XI --> JDBC/FILE/SOAP integration scenarios. For each scenario I have one RFC Destination created (pointing to XI) in SM59 in R/3. For each RFC Destination I have created one RFC Sender Channel in XI.
But this doesn't make sense, don't you agree? I should have only one RFC Destination in R/3 to XI, right?
If that is the case:
1) Should I also have only on RFC Sender Channel in XI?
2) What about load balance? What about concurrence? With only one RFC Sender Channel I have to set "Initial Connection" propertie to a big value to be able to handle several RFC calls (to different RFC Functions) in parallel. Is there a limit (a maximum value) I can use in "Initial Connection" propertie?
Thanks
Julio

hi julio,
Yes. We can have only one RFC to point to Same XI System and in the XI, we need only one RFC Sender too.
For LoadBalancing and concurrence, refer the links:
1) https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/c3d9d710-0d01-0010-7486-9a51ab92b927
Limitations regarding RFC Sender
http://help.sap.com/saphelp_nw04/helpdata/en/58/11e6418b7eca17e10000000a155106/content.htm
Bonus Link: 
Re: RFC Adapter as Sender
regards,
nikhilbos

RFC 2 File Error in RFC sender: java.lang.ArrayIndexOutOfBoundsException

Hello,
I'm sending data asynchronously from R3 to a file through XI, I've got the RFC destination (in R3) and sender RFC channel (in XI) configured and tested. Working fine.
Then in my report I've got the following code that sends 1 string and 4 internal tables 2 to XI:
CALL FUNCTION 'Z_RFC_ENVIAR_DATOS_PSP'
    IN BACKGROUND TASK DESTINATION 'SAP_2_XI'
    EXPORTING
      RUTA                       = p_ruta
    TABLES
      IT_DEMANDA           = p_gt_demanda
      IT_STOCKS              = lt_stocks
      IT_CUARENTENAS   = lt_cuarent
      IT_COMPRAS           = lt_repartos.
COMMIT WORK.
I've done that king of connection several times and allways worked but now I've got that error in the communication channel monitoring at RWB:
Error in processing caused by: java.lang.ArrayIndexOutOfBoundsException
And no message is created in XI. What can it be?
Thanks for your help

Hi Chen Lin,
The problem is with the adapter but no message is generated yet in XI, so I don't have XML yet.
The RFC sends the data to XI through the RFC destination and at this point something is wrong because that error is produced. The error is visible in both sides, In transaction SM58 at R3 I can see the error that tRFC hasn't been precessed because the ArrayIndexOutOfBoundsException.
But if I go to communication channel monitoring I can see the same error too, so that confirms that the communication between R3 and XI works fine but something is wrong and the error don't give me more details

Errors in RFC sender Adapter

Hi Guys,
I am configuring a RFC sender Adapter in a newly installed system.
I configured the adapter as per the parematers given in SAP help in the exact way and started getting the error
Error in processing caused by: com.sap.aii.adapter.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 'RD1CLNT020', toParty '', toService '', interface 'Z_TEST', NS 'urn:sap-com:document:sap:rfc:functions' for channel 'RD1CLNT020_IN' (channelId 897afca12ee93b86a5bfcd738c037099)
If I go into SXI_CACHE of the PI system I can see the entry.
My gut feeling is that the adapter is not fetching the metadata properely.
Because I switched the metadata loging from the ECC system to PI system and I got the error
JCO.Server could not find server function 'Z_TEST'
I think in the basis setup we have missed something The version on which we are working is the Latest PI 7.1
If somebody has a document at the the config for JCO or a solution for this problem will be much appreciated.
Thanks & Regards
Gagan Kasana

Hi,
there is no magic with this error - it's a common one
1. my blog - RFC sedenr adapter config -
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
then is still does not work:
2.check out OSS note 730870 - FAQ RFC Adapter
"Question 19:
While sending a RFC call to the RFC Adapter I get a error message like "com.sap.aii.af.rfc.afcommunication.RfcAFWException: lookup of binding via CPA-cache failed..." or "com.sap.aii.af.rfc.afcommunication.RfcAFWException: senderAgreement not found: lookup of binding via CPA-cache failed...". What is missing?"
and you have it working
please let me know if this helped
Regards,
Michal Krawczyk

Error in RFC Sender

Hi,
We are implementing a BAPI to send data to PI. We have created the following
IN R\3
In SM59 create a new RFC connection type T (TCP/IP).
Technical settings:
Activation type: registered server program
PROGRAM_ID: test_program_id
Gateway options:
GAteway host: Host of your R\3 system
Gateway service: Gateway of your R\3 system
In XI
In your RFC Sender Communication Channel:
RFC Server Parameter:
Application Server: Host of your R\3 system
Application Server Service: Gateway of your R\3 system
PROGRAM ID: test_program_id
RFC Metadata Repository parameter
Message Serer: Your R/3 host.
Message Server Service...
SystemmID...
Use a user with authorization to do RFC calls.
Client...
Language...
After we finish setting up your CC, save and Activate.
Now check the RFC in R/3
When we run the program in SAP( which contains the BAPI ) for the first time, it runs & send the data but for next run it gives error in SAP side(SM58) : Commit fault: com.sap.aii.adapter.rfc.afcommunicat ion.RfcChannelMismatchE
Message no. SR053
Can any one help us to solve the RFC connection issue
Thanks

make sure your program id is unique.try changing it.
Ref:
RFC adapter - /people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
trouble shooting rfc/soap -
/people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009

Error in RFC Sender Scenario. CM_PRODUCT_SPECIFIC_ERROR

Hi,
     I try to do a RFC -> XI -> JDBC. When I execute the FM in my R/3 4.6C the following error show up:
"connection to partner broken" / "CPI-C error
CM_PRODUCT_SPECIFIC_ERROR".
An error occurred when executing a Remote Function Call.
"CPI-C error CM_PRODUCT_SPECIFIC_ERROR"
Status of connection.... "CODE=CM_PRODUCT_SPECIFIC_ERROR CM_NO_STATUS_RECEIVED
CM_NO_DATA_RECEIVED SAPCODE=223 CONV=66899296"
Internal error code.... "RFC_IO5"
There is an error in the communication system. To clarify
and resolve the error, contact your system administrator.
Last error logged in SAP kernel
Component............ "NI (network interface)"
Place................ "SAP-Gateway on host zulia / sapgw00"
Version.............. 34
Error code........... "-6"
Error text........... "connection to partner broken"
Description.......... "NiPRead"
System call.......... "recv"
Module............... "ninti.c"
Line................. 1130

Hi Udo,
   The RFC Sender Communication Channel is complete configure as well the SM59 destination.
When I active the RFC Destination trace, this is what appears:
>>>> [1] XI_RFC       : TCP %%RFCSERVER%% >>> OPEN
>>>> [1] XI_RFC       : TCP %%RFCSERVER%% >>> 71385358 (71385358)
   -{9B7BBA2C-FD5D-4C89-A492-9F1982E8E9DD}
Instrument: RfcCallNew send the uuid to the partner {9B7BBA2C-FD5D-4C89-A492-9F
>>>> [1] XI_RFC       : TCP %%RFCSERVER%% >>> WRITE (71385358)
   -{9B7BBA2C-FD5D-4C89-A492-9F1982E8E9DD}
>>>> [1] XI_RFC       : TCP %%RFCSERVER%% >>> FLUSH(WRITE) (71385358)
   -{9B7BBA2C-FD5D-4C89-A492-9F1982E8E9DD}
>>>> [1] XI_RFC       : TCP %%RFCSERVER%% >>> FLUSH(WRITE) (71385358)
   -{9B7BBA2C-FD5D-4C89-A492-9F1982E8E9DD}
>>>> [1] XI_RFC       : TCP %%RFCSERVER%% >>> WAIT (71385358)
   -{9B7BBA2C-FD5D-4C89-A492-9F1982E8E9DD}
======> CPIC-CALL: 'ThSAPCMRCV'
Ha sido cancelada la conexión con un programa CPI-C -> Falló lectura
ABAP Programm: YPRUEBA_XI (Transaction: SE38)
Called function module: ZIG_DATOS_SAP_BDI
User: 11393759 (Client: 210)
Destination: XI_RFC (handle: 1, convid , {9B7BBA2C-FD5D-4C89-A492-9F1982E8E9DD})
Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 2943
CPIC-CALL: 'ThSAPCMRCV'
Ha sido cancelada la conexión con un programa CPI-C -> Falló lectura
>>>> [1] XI_RFC       : TCP %%RFCSERVER%% >>> WAIT IGNORED (71385358)
   -{9B7BBA2C-FD5D-4C89-A492-9F1982E8E9DD}
>>>> [1] XI_RFC       : TCP %%RFCSERVER%% >>> READ (71385358)
   -{9B7BBA2C-FD5D-4C89-A492-9F1982E8E9DD}
>>>> [1] XI_RFC       : TCP %%RFCSERVER%% >>> FREE-Message (71385358)
   -{9B7BBA2C-FD5D-4C89-A492-9F1982E8E9DD}
Regards,
Luis Diego

Error in mail sender channel : invalid sequence number

Hello all,
I'm having the following issue.
I'm using the mail adapter to get messages from a mail server, which are attached to the mail.
This interface is already productive, and is working fine most of the time.
Only frequently I get the following error, which can be found in the java log.
exception caught during processing mail message[630];
java.io.IOException: the specified message not found: -ERR invalid sequence
number
This error seems only to appear when there are a lot of mails to be fetched.
All the mail is read into PI and processed succesfully, only I also get a lot these errors.
Does anyone know what causes this error?
I also don't know where this sequence number is coming from, and what's the meaning of this.
Is it possible it's trying to read the same mail more then once?
The settings in the mail sender channel are:
- transport protocol : POP3
- message protocol : XIPAYLOAD
- Use mail package : enabled
- content encoding : none
- Keep attachments : enabled
- QOS : exactly once
- Set adapter specific message attibutes : enabled
The PI version is 7.01
Thanks a lot in advance for the replies on this question.
Kind regards,
Marco van Iersel

Hi
Well we have used it with POP3 and it is working in the way as it should be.
This feature is recommended by sap when the number of emails to be read is large.
You can set this additional parameter to restrict the number of mails fetched by sender mail adapter in one polling interval.
Sometimes the mailbox configured for the sender mail adapter contains large number of unread mails, which exceeds the average expected number of mails in one polling interval. In such a case, processing of all the unread mails in the same polling interval by sender mail adapter degrades the system performance. To avoid this, set value of this parameter to the maximum number of mails to be fetched and processed in one polling interval. The remaining mails exceeding the limit would be processed in the next polling interval.
That's why I have asked you to give it a try.

RFC Sender Channel

Hi Experts,
I am dealing with RFC channel(sender). How can we incorporate Qos in RFC??
It's taking BE by default. But how to make it EO and EOIO?
Please suggest
T& R
Sushama

For EO, see this
/people/swaroopa.vishwanath/blog/2006/12/28/send-rfc-to-sap-xi-150-asynchronous
EOIO is not supported for standard RFC sender. An adapter module may help. It would be better to achieve EOIO behavior using ABAP Proxy.
Regards,
Prateek

Error with RFC receiver channel

Hi,
Getting this below error for receiver RFC channel. Can anyone please look into this error urgently.
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.NullPointerException: while trying to invoke the method com.sap.aii.adapter.rfc.core.config.RfcConfig.getChannel() of a null object returned from com.sap.aii.adapter.rfc.core.client.RfcClientPool.getConfig()

Hi,
Restarted but no result. Getting another error :
Delivering the message to the application using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: JCO.Exception while calling Z_SD_XI_BAPI_CREATE_VA_SLSORD3 in remote system (RfcClient[CC_RFC_Z_BRONZE_VA_RCVR]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Could not open file /usr/sap/XP3/interfaces/va/br_vaout_20140401_04204.
I do not understand why RFC receiver channel is giving this error.
Can any one please look into it on priority.I need it to get resolved very soon.
Thanks

Error in FCC-Sender Channel.

Hi Experts,
I have configured the following FCC in Sender communication Channel.
DT_HEADER.keyFieldValue =1
DT_HEADER.fieldNames = KEY,FILENAME
DT_RECORDS.keyFieldValue= 2
DT_HEADER.fieldNames= KEY,AMOUNT
DT_TRAILER.keyFieldValue =3
DT_TRAILER.fieldNames= KEY,SUM
DT_HEADER.fieldSeparator = ,
DT_RECORDS.fieldSeparator= ,
DT_TRAILER.fieldSeparator = ,
DT_TRAILER.endSeparator = 'nl'
DT_RECORDS.endSeparator= 'nl'
DT_HEADER.endSeparator = 'nl'
My sender text file is
1,RDFILE
2,100
3,100
In RWB i am getting the following error message,
Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Parameter 'DT_HEADER.fieldFixedLengths' or 'DT_HEADER.fieldSeparator' is missing Consistency check: no. of arguments in 'DT_HEADER.fieldFixedLength' does not match 'DT_HEADER.fieldNames' (0 <> 2)
i need to get Sender XML structure as follows
<DT_HEADER>
 <KEY/>
 <FILENAME/>
 </DT_HEADER>
 <DT_RECORDS>
 <KEY/>
 <AMOUNT/>
 </DT_RECORDS>
 <DT_TALER>
 <KEY/>
 <SUM/>
 </DT_TALER>
i dont know where i did the mistake can any one help me to solve this issue.
Regard's
Preethi.

Hi
You need alter Data type structure first then do file content conversion
DT_Record
 <Header>
 <Key>
 <FileName>
 </Header>
 <Trailer>
</trailer?
then add
HEADER.keyFieldValue =1
HEADER.fieldNames = KEY,FILENAME
RECORDS.keyFieldValue= 2
It works
Regards,
Raj

Getting error in RFC sender adapter

Hi all,
Am doing the rfc to file scenario. I executed rfc, when i checked SXMB_MONI sent messages from R/3 were not found.So when i checked communication channel monitoring "com.sap.aii.af.rfc.afcommunication.RfcAFException: Service: D47_333 not found in CPACache" am getting this error.
I refreshed cache, even i checked in RWB everywhere the status is green.
Can anyone tell how to solve this.
Thanks in advance,
Sakthi

Hi Sakthi,
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
Regards,
Prateek

Error in RFC Receiver Channel

Hi Experts!
In my scenarios i am using Receiver RFC for Look up. The RFC Channel is working fine in Dev server after we transport it to the QA. Now we are getting an error message :GenericRFCChannel" is not found in SXMB_moni.
ID we have made the new configurations. When i have tested in IE the RFC is working fine. so we getting a strange why it is not working while runtime.
Also i am having one doubt, Is it is mandatory to give the SAP BI details in the Software Component in the IE.Here our RFC are in SAP BI system.
Pls give me some ideas to debug this issue. Thanks in Advance.
Regard's
Preethi.

Hai !
I have made a dummy changes nad reactive the channel even now i am getting the error as
Give me some input to debug this issue. Pls.
<Trace level="1" type="B">CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV</Trace>
<Trace level="1" type="T">Mapping-Object-Id:995C3CC70F88314694147FC81DEB10D0 </Trace>
<Trace level="1" type="T">Mapping-SWCV:E179B290F08511DFAAACDF94C0A80049 </Trace>
<Trace level="1" type="T">Mapping-Step:1 </Trace>
<Trace level="1" type="T">Mapping-Type:JAVA_JDK </Trace>
<Trace level="1" type="T">Mapping-Program:com/sap/xi/tf/_dealTicket_OPS_iOam_MM2_ </Trace>
<Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_dealTicket_OPS_iOam_MM2_
Thrown:
com.sap.aii.utilxi.misc.api.BaseRuntimeException: com.sap.aii.mapping.api.UndefinedParameterException: The input-parameter GeneratedReceiverChannel_RFC does not exist.at com.sap.aii.mappingtool.tf7.Transformer.start(Transformer.java:148)
at com.sap.aii.mappingtool.tf7.AMappingProgram.transform(AMappingProgram.java:626)
at com.sap.aii.ib.server.mapping.execution.JavaMapping.executeStep(JavaMapping.java:92)
at com.sap.aii.ib.server.mapping.execution.Mapping.execute(Mapping.java:60)
at com.sap.aii.ib.server.mapping.execution.MappingHandler.map(MappingHandler.java:87)
at com.sap.aii.ib.server.mapping.execution.MappingHandler.map(MappingHandler.java:71)
at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:119)
at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:72)
at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79)
at sun.reflect.GeneratedMethodAccessor555_10000.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
at $Proxy587_10000.processFunction(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:183)
at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:269)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:152)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
Caused by: com.sap.aii.mapping.api.UndefinedParameterException: The input-parameter GeneratedReceiverChannel_RFC does not exist.
at com.sap.aii.ib.server.mapping.execution.MappingParametrization$InputParametersImpl.getValue(MappingParametrization.java:84)
at com.sap.aii.ib.server.mapping.execution.MappingParametrization$InputParametersImpl.getValue(MappingParametrization.java:71)
at com.sap.xi.tf._dealTicket_OPS_iOam_MM2_.__CreateStructures(_dealTicket_OPS_iOam_MM2_.java:276)
at com.sap.aii.mappingtool.tf7.AMappingProgram.preStart(AMappingProgram.java:307)
at com.sap.xi.tf._dealTicket_OPS_iOam_MM2_.preStart(_dealTicket_OPS_iOam_MM2_.java:802)
at com.sap.aii.mappingtool.tf7.AMappingProgram.start(AMappingProgram.java:489)
at com.sap.aii.mappingtool.tf7.Transformer.start(Transformer.java:133)
... 40 more

Random error IN RFC sender channel

Similar Messages

Maybe you are looking for