RFC -- XI problem
Hello again guys,
I am currently working on scenario from SAP to Legacy system using XI. The scenario is like this: RFC --> XI --> Legacy. I got no problem at all in the development server for R3 connecting to XI.
However, when i transport the RFC to QA server of R3, then i execute my application in QAS of R3, it runs fine, but when i check in the SXMB_MONI, there are no messages at all. It seems that XI has not receive any call at all.
I have already use a different communication channel which is for connection to my QAS R3 to XI using RFC sender adapter in the Sender Agreement.
I cannot find anything wrong anymore in my configuration. But it seems the QAS is not calling XI at all.
If any of you guys have any idea or advice of what sholud i check more please feel free. I would really appreciate your inputs. Thank you very much.
NB: I have already checked my settings in SM59 as well in the QAS, and all the settings are the same with the ones that i used in development server R3.
Hi Made,
Have you checked Adapter Status in Adapter Monitor to make sure that massege is hittind adapter or not. if it is then it may not be able to call MessageServer or message may not be getting picked from queue of messageserver. Hope it helps to find the cause.
Regards,
Alok.
Similar Messages
-
Rfc sender problem(sap r/3 -se37) 'alternativeServiceIdentifier: party/serv
Rfc sender problem: While executing the rfc in sap r/3 system
It is showing abap run time errors are
'alternativeServiceIdentifier: party/service from channel
configuration are not
(i have taken hint from this weblog /people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step)
These are the configuration at sap xi and sap r/3 system
1) SAP XI (ID)
I have created rfc sender commuication channel in I.D.
Rfc server Parameters->
A.S.(Gateway)-> server {sap r/3 server name}
A.S.S.(Gateway) -> sapgw00
program id -> PDPT
AND RFC Metadata repository parameter
2)SAP R/3 (SM59)
Rfc destination -> PPPP
Connection type -> T
Technical Settings->
(*) Registered Server Program
Program ID -> PDPT
Gate way options
Gateway host -> server
gateway service -> sapgw00
Testconnection-> connected
3) testing rfc at sap r/3(se37)
But when i am executing a rfc in sap system
Rfc target system -> PPPP
and some import parameters
and it is showing the error message as
'alternativeServiceIdentifier: party/service from channel
configuration are not '
4)SAP R/3( SMGW)
CONNECTION TO CLIENT FOR PDPT(TP NAME) REGISTER STATUS IS WAITING
Please help me how to solve this problemHi,
SAP Note 730870 FAQ: XI 3.0 RfcAdapter Q.no 15
<i>Q 15: Whats wrong when the error message "lookup of alternativeServiceIdentifier via CPA-cache failed" shows up while sending a RFC call to the RfcAdapter?
A: A RFC sender channel is located beneath a service within the Integration Directory. Within this service choose "Service" -> "Adapter-Specific Identifiers". The values in the fields "R/3 System ID" and "Client" has to be maintained with the correct values of the system, that sends the RFC call to the RfcAdapter. It normaly only makes sense to have these values filled for services of type "Business System". If maintained in SLD, this fields will be filled automaticaly for services of type "Business System" and can be updated with the button "Compare with System Landscape Directory".</i>
- Give correct appserver and gateway service details in XI.
- Open the service holding the RFC adapter you are trying to use. On the top menu, goto Service -> Adapter Specific Identifiers..
Regards,
Prateek -
Second Time, RFC execution Problem!
Hi all,
Has any one encountered this problem, when calling RFC First time fine and getting data from BAPI, when i call same RFC again, Second Time, RFC execution Problem!. Any idea!, Now i restarted server, that may cause the problem. Other than this, please give me your idea.
Thanks
Ravi GollaHi Bhavik,
<b>In View Controller:</b>
public void onActionCreateProject(com.sap.tc.webdynpro.progmodel.api.IWDCustomEvent wdEvent )
//@@begin onActionCreateProject(ServerEvent)
wdThis.wdGetArchCompController().CreateProject();
wdThis.wdFirePlugOutToProjectCreationResult();
//@@end
<b>In Custom Controller:
</b>
wdDoInit()
__Arch__Arm_Project_Create_Input create = new __Arch__Arm_Project_Create_Input();
wdContext.node__Arch__Arm_Project_Create_Input().bind(create);
public void CreateProject( )
//@@begin CreateProject()
try
wdContext.current__Arch__Arm_Project_Create_InputElement().modelObject().execute();
wdContext.nodeOutput().invalidate();
catch(WDDynamicRFCExecuteException ex)
wdThis.wdGetAPI().getComponent().getMessageManager().reportSuccess(ex.toString());
ex.printStackTrace();
//@@end
I am using other functional modules they all working fine, this is one only has problem
Thanks Bhavic.
Regards
Ravi -
Recurring RFC connection problems
Hi!
I really need some help. We have been experiencing RFC problems for a few months now and our basis team have no clue as to what the problem might be. The problem is that on a daily basis we experience RFC connection problems. It usually happens at about 7am in the morning and lasts for an hour. After that the problem clears itself and for the rest of the day runs smoothly.
We clearly see this problem on our RFC connection to the IBM MQ message server which handles all our incoming and outgoing IDOCS. This is however not the only RFC problem as we have also had RFC connection failures when switching between instances in SM51. This suggests to us that it is probably not a network issue, although the MQ server is housed in a different data center than the SAP servers.
We are running ECC6 and our environment looks like this:
4 hosts running 5 instances: 3 hosts with one instance and 1 host with 2 instances.
While this problem is occurring you can do a connection test in SM59 to MQ which is usually successful. In SMGW we have picked up that it is trying to establish multiple connections to MQ, some connects successfully and some cannot connect. In ST11 in the RFC trace files the error message says that the MQ connection times out.
While monitoring the MQ server we cannot pick up any problems. The MQ server itself seems to run without errors. The only problem is that it cannot connect to SAP to send IDOCS and SAP cannot connect to MQ. The load on the MQ server while this error occurs is minimal compared to the rest of the day.
Does anyone have any ideas as to what the problem might be? Are there any other places other than the ones mentioned in this mail where we can check for errors?
Thank you in advance!
IwanHi Marcelo,
In SM59, just select the RFC and above in same screen you can see the options
RFC----- Display Trace (Shift + F8)
Check the trace file and see if there is any connection problem between the two system.
Regards,
Ravi -
Hi all,
I am trying file->xi->rfc adapter scenario.
My scenario is employee information is written to flat file n will be kept on ftp server.THe file adapter will pickup the file and sends it to rfc adapter through pipeline service.
This is going well. The problem is the data is not being updated into receiving sap system.
in SXMB_MONI transaction the messages are successully processed . But there are no messges in rfc adapter when i gone through idx5 transaction???
Any one have idea??
Thanks in advance.
Rgds,
Ram Srisxmb_moni only shows the status of the integration engine's processing, not the result of what happened in the rfc call. First, you can check if the adapter framework successfully passed the message to the destination system (not on moni, thru RWB)
as far as did the rfc succeed - it's as difficult as always with internal processing. We did a lot of testing by debugging modules on the destination side (manually putting in the data as the adapter would've to step thru & see where the message is "lost") - have not yet found a better way, sorry. It's not so much a problem with XI, just in general the difficulty to debug rfc's -
Hello All,
We are setting up communication between R/3 4.7 and SCM 5.0 system for EWM (Extended warehouse management) with RFC connection and using IDocs to transfer data from one box to another box.
IDoc from R/3 to SCM system is working fine, we are able to complete the transactions in SCM system and after successful completion all transaction in SCM it should trigger Idoc for R/3 which is not happening.
It throws error as <b>"An RFC destination could not be specified for the logical system XXXCLNT123"</b>
We have checked SM59 (RFC connection), WE20 (Partner profile), WE21 ( IDoc port connection) it seems fine.
Interesting thing is we are able to get information about stock from R/3 system in SCM system which are correct information.
Can anyone give some idea if we are missing something to check?
Thanks & regards
Arif MansuriHi Team,
We have the same problem , which was mentioned above. Please let us know, which Message type need to be used for sending the stock information to ERP after Delivery completion
The following Process we followed
PO Creation---ERP
Inbound delivery-ERP
Inbound Delivery Process-EWM
WareHouse Task-EWM
Unloading-EWM
WareHouse Task/WareHouse Order Confirmation-EWM
Once the WT/WO is confirmed , Goods receipt status is updated automatically and "Post Processing Framwork (PPF) status shows with RED and error message says."An RFC destination could not be specified for the logical system E6SCLNT900"
Here I have one doubt, We have maintained client names as A0000039 (for EWM,but original client name is SC7CLNT100 ) and E6SCLNT900 ( for ERP , original client name also E6SCLNT900)
Will there be any issue with A0000039?(because we did not maintained as per the original client name ie SC7CLNT100)
Thank you for your help
Thank you -
Creation of RFC Destination problem
Hi Experts,
I need to establish an RFC communication between TREX7.0 server running on windows 2003 server and the SAPR/3 4.7 EE server running on windows2000.
server. Initially i used TREXAdminTool to create RFC Destination, i was unable to create successfully
Then i used SAPR/3 server from TCODE: SM59, here also am facing the same problem, what are the values i have to give for
1. RFC Destination, 2. Program id 3. Gateway Host and Gateway Service.
PLZ guide me step by step procedure with some example values to create RFC Destination to TREX Server successfully using TREXAdminTool or from SAPR/3 server---SM59
ADV Thanks
Regds
phanikumarHi,
Till now i didn't install explicitly any SAP Gateway on TREX server.
I installed TREX server along with SAP Netweaver WEB AS java.
Shall i need to install any SAP Gateway to configure RFC Destination?
If so can you give me the procedure how to install explicitly SAP gateway?
Regds
Phanikumar -
RFC connection problem during SRM - R/3 integration
Hi,
Our environment is SRM 5.5 server with 2 R/3 backend systems. One of the R/3 systems is in another country. We happen to have RFC problems during the communication between the SRM and R/3 server.
Below you can find the SM21 log related to an operation on SRM server. What might be the reason for this problem? Does anyone know the solution?
Many thanks
Details Page 2 Line 26 System Log: Local Analysis of sapsrmt 1
Time
Type
Nr
Clt
User
TCode
Grp
N
Text
10:24:58
DIA
000
013
EMREK
R4
9
Communication error, CPIC return code 020, SAP return code 223
Communication error, CPIC return code 020, SAP return code 223
Details
Recording at local and central time........................ 07.12.2006 10:24:58
Task......
Process
User......
Terminal
Session
TCode
Program
Cl
Problem cl
Package
91342
Dialog work process No. 000
EMREK
XXXXXXXX
2
K
SAP Web AS Problem
STSK
Further details for this message type
Module nam
Line
Error text
Caller....
Reason/cal
thxxhead
7192
020223
ThRecei
CPIC-Er
Documentation for system log message R4 9 :
A CPIC function has failed. The conversation ID and CPIC function are
specified in the system log entries. Use the conversion ID to find more
detailed information about the error in the system log for the SAP
gateway.
Meaning of the SAP return codes:
1) Gateway errors:
221,,Error in CPIC-SS
222,,Storage bottleneck
223,,Network read error
224,,Network write error
225,,Invalid request
226,,No connection yet
227,,Gateway process terminated
228,,Shared-Memory problem(read)
229,,Shared Memory problem(write)
230,,No free LU
231,,No free gateway process
232,,Error when starting gateway proc.
233,,Incorrect communication type
234,,Connection setup failed
235,,Error in comm. table
236,,No connection to gateway
237,,Connection to gateway closed
238,,Error in GW command (write)
239,,Error in GW comm. (read)
240,,Invalid length
241,,Invalid environment
242,,Timeout
243,,Error setting up SAP connection
244,,Partner has closed connection
245,,Storage overflow
246,,Incorrect APPC header version
247,,APPC server not started
248,,Error accessing TXCOM
249,,Comm. table is full
630,,Invalid mode no. received
631,,Max.no. of gateways reached
632,,No LU specified
633,,Max.no. of clients reached
634,,Invalid TP name
635,,fork failed
636,,Invalid NI handle
637,,rexec failed
638,,TP start failed
639,,NiDgSend failed
640,,Internal error
664,,Gateway host is unknown
665,,Gateway service unknown
666,,NI error
667,,exec failed
668,,R/2 restarted
669,,Symb. destination too long
670,,No more side-info entries
672 ,,Logon to NetWeaver failed
673 ,,IMS Error Purging
674 ,,Timeout for registered programs
676 ,,TP not registered
677 ,,Timeout for registered programs
678 ,,TP is registered
679 ,,TP is not registered
720 ,,Security breach of registered programs
721 ,,SNC deactivated
722 ,,SNC required
723 ,,SNC name not defined
724 ,,Default SNC name not permitted
725 ,,Protocol does not support SNC
726 ,,No local SAP System
727 ,,SNC required
728 ,,Conversation ID not found
729 ,,SNS must do the communication
730 ,,Start of external programs deactivated
731 ,,Gateway shut down
732 ,,No external programs
733 ,,Conversation ID does not match
734 ,,Net conversation error
735 ,,Monitor is not active
736 ,,Conv-ID is not unique
Errors in the CPIC Interface:
450 ,,No storage
451,,No side-info entry
452,,TP-START failed
453,,No initialization
454,,"getlu" failed
455,,"signal" failed
456,,Timeout during conn. setup
457,,CMALLC failed
458,,CMSEND failed
459,,Prepare-To-Receive failed
460,,"mc_flush" failed
461,,CMRCV failed
462,,Argument missing
463,,"get_allocate" failed
464,,CMDEAL failed
465,,TP-END failed
466,,Max.no.of conv. reached
467,,"snaopen" failed
468,,"snactl" failed
469,,No flush in IBM environment
470,,"snaclse" failed
471,,Status error
472,,No side-info entry
473,,No conversation
474,,Connection closed manually
475,,Connection closed automatically
476,,No partner found
477,,Confirm failed
478,,Confirmed failed
479,,GWHOST not in side-info entry
480,,GWSERV not in side-info e.
481,,PROTOCOL not in side-info entry
482,,LU not in side-info e.
483,,TP not in side-info entry
484,,No conn.to gateway
485,,gethostname failed
486,,SAP_CMACCP not executed
487,,Program not in argument list
488,,Host not in argument list
489,,Service not in argument list
490,,Conv-ID not in argument list
491,,Invalid parameter
492,,LU62CVCT failed
493,,LU62ATTCH failed
494,,No CONV table
495,,Incorrect conv.table
496,,Invalid conv modification
497,,NiHostToAddr failed
498,,NiAddrToHost failed
499,,Read operation tab.THOST failed
500 ,,No side info file exists
501 ,,CMRCV failed
Technical details
File
Offset
RecFm
System log type
Grp
N
variable message data
6
245700
m
Error (Function,Module,Row)
R4
9
020223 ThReceiCPIC-Erthxxhead7192Hi,
It will be very difficult to solve without being on the customer site and having all information.
Right now, the error code is network error...
Kind regards,
Yann -
R/3 - XI - R/3 RFC connection problem
hello friends,
I have a scenario which is R/3 -> XI -> R/3.
Since i do not have another R/3 system i am trying to configure sender and reciever on the same system with different clients.
The sender configuration is working fine. Please tell me the setting for the reciever configuration.
Current settings that i have done are --
Message server - <host name>
Message server service - 3600
System Id - <system id>
Logon group - public
When i try to execute the BAPI_USER_GET_DETAIL BAPI it gives me the following error --
<b>"lookup of binding via CPA-cache failed for AdapterType RFC, AdapterNS"</b>
thanks in advance,
Abhi<i>Please can you tell me how to access these Notes. I have never been able to find any such notes :(</i>
For this you need to have SAP service MArket Place id.
Go to https://websmp108.sap-ag.de/notes then give the ,give mentioned SAP Note number-
Anyway the content of the note wrt this problem is here- from SAP Note- 730870
<i>Q 19: While sending a RFC call to the RfcAdapter 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?
A: The RfcAdapter trys to find a Sender Agreement for this RFC call but the lookup failes. The values used for this lookup are:
Sender Party/Sender Service: The values from Party and Service belonging to the sender channel.
Sender Interface: The name of the RFC function module.
Sender Namespace: The fix RFC namespace urn:sap-com:document:sap:rfc:functions
Receiver Party/Receiver Service: These fields are empty. This will match the wildcard '*'.</i>
BTW, did you recheck your RFC adapter configuration. And activate it.
Regards,
Moorthy -
RFC Sender problem between 46D and RFC adapter
Hi,
I have this simple integration scenario where I want to send data to a archiving system;
SAP -> (tRFC) -> XI -> (MQ) -> BizTalk -> (MQ) Arch.syst.
SAP side ***
A Z-program using a Z func. like;
CALL FUNCTION 'ZSD_DCF_SEND_TAG'
IN BACKGROUND TASK
DESTINATION 'XISYSTEM_TRFC_DCF'
EXPORTING
pt_filing_info = gt_filing.
COMMIT WORK AND WAIT.
XI side ***
Both IR and ID is configured correctly, in the development environment everything works just great. I have created a test program where I can define how many calls I will do, looping over the func. call with a commit inside the loop - 500 or more msgs are ok.
The integration scenario is transported to quality enviroment using CMS, and the RFC sender comm.ch. is configured accordingly.
The problem in quality ***
When sending just 1 msg, everything is just fine, message received and delivered to MQ.
When sending >= 2 msgs, the 1 msg is always ok, BUT all others fails due to the following from Adapter monitor;
RFC_HISTORY
- Error: 2006-01-19 10:55:18 CET: com.sap.aii.af.rfc.afcommunication.RfcAFWException: lookup of alternativeServiceIdentifier via CPA-cache failed for channel 'RFCSender_XI0002' (02d4d30de3593874942ed0659add0827, party '', schema 'TechnicalSystem', identifier 'Q93#120')
- OK: 2006-01-19 10:55:17 CET: Message processed for interface ZSD_DCF_SEND_TAG
My sending system is Q93 CLI 505 so I can understand the error, BUT I cannot understand why the RFC adapter is saying the TechnicalSystem is Q93#120 - it should be Q93#505. My Q XI has client 120...
It seems to me that the RFC adapter is kind of confused about the sender..
I have created a OSS message and SAP has looged on and looked into it with both a XI expert and RFC expert without being able to answer - all is configured correctly.
- The SLD config. for bus.system Q93 is ok -
- The bus.system in ID is showing correct vaues for
Adapter Specific Identifiers (SID Q93, client 505)
- Both Dev. and Qual. environment are running on XI 3.0 SP 14 latest patch, RFC component version on the SAP side is identical between dev. and qual. SAP systems
- It doesn't matter which gw I use (Q93 gw or XI gw), the error is persistent
- It doesn't matter if I increase initial conn, max conn.
I have also tried to use qRFC instead, but with the same result.
Anyone using tRFC for asynch. communication from SAP to XI seeing something similar?
Meanwhile, I will do RFC trace on GW and RFC Adapter on AE....
Please, do not say SP15, oss msg for FAQ RFC adapter or links to RFCAdapter config....
best regards
TorsteinHi,
SAP Note 730870 FAQ: XI 3.0 RfcAdapter Q.no 15
<i>Q 15: Whats wrong when the error message "lookup of alternativeServiceIdentifier via CPA-cache failed" shows up while sending a RFC call to the RfcAdapter?
A: A RFC sender channel is located beneath a service within the Integration Directory. Within this service choose "Service" -> "Adapter-Specific Identifiers". The values in the fields "R/3 System ID" and "Client" has to be maintained with the correct values of the system, that sends the RFC call to the RfcAdapter. It normaly only makes sense to have these values filled for services of type "Business System". If maintained in SLD, this fields will be filled automaticaly for services of type "Business System" and can be updated with the button "Compare with System Landscape Directory".</i>
- Give correct appserver and gateway service details in XI.
- Open the service holding the RFC adapter you are trying to use. On the top menu, goto Service -> Adapter Specific Identifiers..
Regards,
Prateek -
Rfc Destination problem in RFC Sender Adapter
Hi experts
I created a Rfc destination type TCP/IP for Rfc Sender adapter.
while creating i passed following parameter:
1) I selected Activation Type option-> Registered Server
2)Given a Program id , same as i given in Rfc sender Adapter config.
3)Gateway option:
i) Gateway Host:Server IP address where i created Rfc.
ii) Gateway Service:sapgw00
After making these entry, i m unable to receive message at XI end (I am executing Rfc at R/3 site due to Rfc sender)Hi
please check for the following things.
1. check the RFC destination using the connection test tab in the R/3 system.
2. check whether the program id that u have given is registered or not.
to check the program id go to the transaction SMGW, in the menu select Goto-->LoggedonClients
check for ur program id name in the table.
3. when you configure the RFC sender adapter in XI then you have to give the same program id name that you will give while creating the RFC destination in the R/3 system.
if u still face the problem please reply me back.
Thanks
Rinku -
Hi,
I am facing a problem in a RFC call. I am calling a RFC, residing in R3, from a ABAP Web Dynpro Component in ABAP Stack.
When I test this RFC in R3, it returns the data perfectly. But when it is called from the ABAP Stack(with 'DESTINATION' ), it
populates only one of the seven fields of the structure to be returned. The same RFC works perfect in Devlopment and Quality,
but not in Production.
I checked the structures in both the system, i.e. DEV and PRD, they are identical.
Can anyone tell me, what are the possibler reasons for the same?
Thanks in advance.
Best Regards,
SagarHi,
Thanks for you prompt reply. The problem was with the authorization that was given to the ID, used for RFC connection.
Thanks once again.
Best Regards,
Sagar -
Imported RFC with problem in converting to XML
Hello,
another nice issue:
I have an aRFC with this import parameter from ABAP:
data: p_data type tab512 occurs 0.
Call function.......
Tables
DATA = p_data
This is the XML source from the mapping test in Int.Rep.
<?xml version="1.0" encoding="UTF-8"?>
<ns:Z_BI_SEND_DATA_512 xmlns:ns="urn:sap-com:document:sap:rfc:functions">
<SYSID_HOME>AAA</SYSID_HOME>
<TARGETSYS>BBB</TARGETSYS>
<DATA>
<item>test1</item>
<item>test2</item>
<item>test3</item>
</DATA>
</ns:Z_BI_SEND_DATA_512>
This is the payload from SXMB_MONI:
<?xml version="1.0" encoding="UTF-8" ?>
- <rfc:Z_BI_SEND_DATA_512 xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
<SYSID_HOME>AAA</SYSID_HOME>
<TARGETSYS>BBB</TARGETSYS>
- <DATA>
- <item>
<WA>test1</WA>
</item>
- <item>
<WA>test2</WA>
</item>
- <item>
<WA>test3</WA>
</item>
</DATA>
</rfc:Z_BI_SEND_DATA_512>
Looks like there is a difference (imported RFC in mapping does not show the work area WA)(so: mapping requires
<DATA>
<item>test1</item>
but RFC generates
- <DATA>
- <item>
<WA>test1</WA>
which hinders the mapping from moving the item lines into the destination file because in mapping the WA area cannot be linked as it is not recognized in mapping.
Any ideas are welcome!
Regards
DirkHi everyone
My problem is related to Dirk's one in that I am using an RFC to send XML data from CRM to XI.
I am trying to send the following string:
<TEST>GREG</TEST>
However on XI the payload looks like this:
<xml version="1.0" encoding="UTF-8"?>
<rfc:_-MARS_-CPE_IMPORT_CRM_CATALOG xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
<IV_CATALOG><TEST>GREG</TEST></IV_CATALOG></rfc:_-MARS_-CPE_IMPORT_CRM_CATALOG>
As you can see < is converted into <
Where and how do I specify that the content of the parameter must not be interpreted?
Thanks
Greg -
RFC & BAPI problem in SUP 2.0
Hi,
I have been using the Standard BAPI's & RFCs for my app. However i am getting the errors for all of them while actually using in workflow app.
1] Invalid Templet for BAPI.
2] java.io.Exception:JASON:character not standard date time type
3] ____BAPI Return is not a standard DateTime type
But i can see the preview of all successfully. Do we need some kind of special requirement fo BAPI & RFC's to work in SUP ?
I am using MBS & simple workflow app concept to design. I have also searched the SDN for any SUP 2.0 & SAP BAPI example. I found My Flights but that was too old in previous 1.5.2 i think so which is of no use.
Your help highly appreciated
BR
YogeshHi,
That's the first thing i checked the version, I have the latest JCO & JAR files being used. So there is no version conflict in Backend EIS & the front UI.
I am on digging out the infinitesimal log entries in the server to fetch the exact reason behind the problem.
I would like to know if you have ever imported the BAPI or RFC would you normally get conflicts with SAP returning the NULL or NaN values from backend.
Because I know Sybase Messaging Client can not handle the NaN & NULL values thats an offcial confirmation from Sybase for RESTful WS i got.
So may be its same but i am not sure I must or someone who has encounter these errors should confirm this.
Best Regards
Yogesh -
Hello All,
Thank you very much for trying to help me.
Here is the problem,
I have a synchronous interface (RFC to XI to SOAP). when I try to push the RFC through SE37 I am getting the following error.
Sender channel 'RFCCommunicationChannelCRD' for party '', service 'CRD' (internal name 'RfcServer[RFCCommunicationChannelCRD]')
Server data: {jco.server.gwhost=snowking.directv.com, jco.server.progid=sdnweblogs, jco.server.gwserv=sapgw00, jco.server.unicode=1}
Repository data: {jco.client.lang=en, jco.client.snc_mode=0, jco.client.client=010, jco.client.passwd=******, jco.webas.ignore_jdsr_error=1, jco.client.user=aleremote, jco.client.sysnr=00, jco.client.ashost=snowking}
Current pool size: 1, maximum pool size : 1
Channel History
- Error: 2006-08-22 15:05:25 PDT: Message processed for interface Z_GET_STORE_FROM_STMS: com.sap.aii.af.mp.module.ModuleException: call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryException: Application:EXCEPTION_DURING_EXECUTE: caused by: com.sap.aii.af.ra.ms.api.DeliveryException: Application:EXCEPTION_DURING_EXECUTE:
and when I go to MONI, I am getting incorrect data, because of that I am getting mapping error. Will any one can help me.
Thanks you very much.Hi Chandra,
Please check this thread..
"call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryExceptio
Hope it helps!
cheers
Prashanth
P.S Please mark helpful answers -
RFC Adapter Problem: Adapter Engine Field Blank
Hi,
I want to invoke a BAPI defined on a R/3 system. I am trying to create a RFC Adapter in the Integration Directory by creating a communication channel.
The problem I am facing is that when I define the Adapter Type as RFC, the Adapter Engine dropdown list is blank and it does not contain any entries.
On passing a document through XI, I can see the following error in the monitor:
<SAP:Code area="INTERNAL">ADAPTER_NAME_INVALID</SAP:Code>
<SAP:P1>RFC</SAP:P1>
<SAP:P2>PLSRV_CALL_ADAPTER</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unknown receiver adapter (name = RFC)</SAP:Stack>
what do i need to configure on the XI and R/3 side ?
thanks,
Manishi followed the steps but i am not getting the populated adapter engine list.
Actually, the Association shows a list of logical systems to be added (Application System, BC Application Server, BC Central Server Instance .....). I experimented with many systems but it is not working.
My basic problem is I need to call a BAPI from XI. The XI monitor shows the error :
Adapter Name Invalid.
Unknown Receiver Adapter (name=RFC).
Now, for the RFC adapter, I have not given it any name. My Communication Channel is called GeneratedChannelRFC. I am not sure where this error is coming from. I would appreciate any help to solve this error.
thanks,
Manish
Maybe you are looking for
-
Does anyone have the same problem with printing using HP color laserjet CP1515n? Printing in black and white is ok. Cannot print in color. There are shadows in color printouts. The colors are not aligned.
-
Configuration of third-party router
Hello, I'm trying to configure a router in place of my BT Home Hub. I am pretty sure it has to be PPPoE because it's ethernet out the back of the Home Hub. I tried what was posted on these forums, I used [email protected] with 'bt' as the password.
-
I can't download linked files on mac osx lion what do i do?
i can't download linked files on mac osx lion what do i do?
-
Imap smtp settings work in thunderbird but not in mail
Hello. One of my imap accounts can't send mail from apple's mail anymore (since updating to 10.8). The exact same settings (Server, Port, Security, Authentification, User Name) on the same computer work in thunderbird. Any idea? Thanks
-
Ipod in car with kensington fm transmitter
I've been using this in my car for ages and I love it. It transmits my music to my car stero and charges my ipod.. My question is this: my iPod charges with a firewire, right? So can I charge my iPhone from the same thing and have it broadcast to my