Restrict messages in RFC adapter or in source/sending (SAP R/3) system

Hi All,
I have SAP R/3 to web service scenario via XI (RFC to SOAP). In that scenario RFC caries the attachments, some time the attachments size is more than 5mb. Due to that java stack of XI becomes unresponsive. Due to that SMQ2 gets filled up with the entries and other scenarios are also severely effecting.
Is there any way to restrict the message, if itu2019s size is more than 5mb in RFC adapter of XI or can we stop the processing/sending of such a messages in source system itself (SAP R/3).
I welcome all your suggestions.
Thanks & Regards,
Venu V

Hi Praveen,
The attachments to the tickets in source system. The RFC caries that data, once that data size is more than 5mb then it affecting the server.
I am getting following errors
u201Ccom.sap.aii.af.ra.ms.api.DeliveryException: Could not create Message from TransportMessage. Reason: com.sap.aii.af.ra.ms.api.MessagingException: com.sap.aii.af.ra.ms.api.MessagingException: Could not parse XMBMessage due to Read timeout. The client has disconnected or a synchronization error has occurred. Read [45434] bytes. Expected [101981].u201D
u201CJCO_COMMUNICATION_FAILURE
Error opening an RFC connection
"COMMUNICATION FAILURE" during JCo call. Error opening an RFC connectionu201D
Thanks & Regards,
Venu V

Similar Messages

HTTP and RFC Adapter are not Required Sender

Hi All,
I have one dought....
Why Plain HTTP and RFC Adapter are not Required Sender Communication Channel and Sender Agreements...
I Know this two Adapter are in ABAP Stack....
Please clarify my dought...
Regards

Idoc Adapters do NOT require Sender Communication Channel.
The Sender System identifies itself at the Integration Server, with the fields SNDPOR and Client of the Control Record.
Sender Communication channels are used for communication betweeen the Application System and the Integration Server.
In the case of Idocs, all idocs are tranferred to the Integration Server pipeline and NOT to the regular EDI/IDOC interface.
The RECEVIER DETERMINATION is based on the values in the Control Record.
If you are doing ALE, then you have to maintain the idoc types which are NOT to be transferred to the Integration server by executing report IDX_SELECT_IDOCTYP_WITHOUT_IS.
By maintaining the Idoc Types using this report, only these idoc types are sent to the regular EDI/IDOC interface.

RFC message monitoring (RFC Adapter)

Hello everyone!
I am planning to use the RFC receiver adapter in XI to send messages to an SAP system. My question is, how would I monitor the RFC messages coming into the SAP system? Will they be viewable in sxmb_moni?

hey
yes u can monitor RFC's in sxmb_moni.
in addition to that you can see SM58 (in case of any errors in RFC)
thanx
Aamir

Sender RFC adapter - Tight coupling to an SAP client

Hi ,
We are using a sender RFC adapter to receive a RFC request from SAP , process the request in XI and then send back a response to SAP.
Our requirement is that , this request may come from different SAP clients(client 100, 130 , 200 etc). Looks like RFC adapter configured under a Business System in XI cannot listen to calls from multiple clients and works for only one client. We get dumps in SAP when invoking this RFC from other clients.
Also i hear that the same program id cannot be used in two different RFC sender adapters, meaning i have to create a different RFC destination , create a different program id for each client in SAP.
Is there a way around for this issue ?
Thanks
Saravana

Hi Saravana,
you may try a little workaround:
configure your rfc adapter only with client 100
and try invoking RFC from clients: 130 , 200
on the client 100 first (with a dummy RFC on client 100)
and then from this dummy RFC on client 100 you can start your standard RFC with your rfc adapter
don't know any other way:)
Regards,
michal

RFC Adapter to connect to Non SAP System

Hi,
I have a scenario to connect to a non SAP system using RFC adapter. I am not used to the same. I need to know whether this is possible and what are the steps to be done.
Thanks and regards
Siji

Hi,
These links should help.
Non-SAP application connecting to PI via Sender RFC Adapter
Error by setup RFC Interface with non SAP system
SAP PI to Third Party system through RFC Connectivity ??
Regards,
Jannus Botha

Configuring SAP R/3 system as data source for SAP BW3.5 system

HI All,
Please help me in getting some document for integrating SAP R/3 4.7 with SAP BW3.5 as data source system.
Thanks in advance.
Regards,
Nalla.

Hi,
I have got the link which has solution for my question from old questions in this Forum.
http://help.sap.com/saphelp_nw04/helpdata/en/00/dc54384ac9a81be10000009b38f8cf/frameset.htm
So stopping this thread.
Regards,
Nalla.

Problems in RFC Adapter

Hi All,
I'm using RFC adapter to send messages to XI. The import parameter of the RFC is a very complex structure. One of the embedded strcuture contains a table. During runtime, if I use "APPEND line TO tale" statement to fill that table in the client of RFC Adapter, the program dumps. The short text is "After a value an end tag must follow. That did not happen in". This short text is obviously incomplete. My questions are:
1. How can I view the complete short text of this dump?
2. Is there any restriction on the RFC adapter parameter? I only use "import" and "export" parameters. I'll not use "table" parameters. Could I use a very complex structure which contains embedded structures and tables as import parameters?

HI Jerome,
>>>1. How can I view the complete short text of this dump?
have you tried TCODE - ST22 ?
>>>2. Is there any restriction on the RFC adapter parameter? I only use "import" and "export" parameters. I'll not use "table" parameters.
please use the table - this is the parameter for storing many values (lines) of a structure
Regards,
michal

Error in pushing a request to R3 System using RFC Adapter

I am trying to send a request to R3 system using an RFC Adapter as my end point and pointing to
the Application server of the R3 box.
In the Transaction SM58 I see and error saying "Exception in handleRequest of server Xmb2RfcService: java.lang.Exception:"
Here are the corresponding details:
Caller: CENTRALADMIN
Function Module: SRFC_ADAPTER_SERVICE
Target System: AI_RFCADAPTER_JCOSERVER
Host: .... (The XI Server)
Program: SAPMSSY1
Clnt: 100
As per the SRFC_ADAPTER_SERVICE function module, the purpose stated so...
"This function is the glue between the JCo RFC Inbound Adapter and the XMS Pipeline."
By the by the RFC adapter is started and I can see no activity in the log after startup.
I would really appreciate for any idea/leads in solving this. Thanks.

Here are the details
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%Config File for RFC Adapter%%%%%%%%%%%%%%%%%%%%
RFC ADAPTER CLASSNAME FOR ADAPTER ENGINE
classname=com.sap.aii.rfcadapter.core.RfcAdapterModule
RFC ADAPTER CONFIGURATION PROPERTIES
Tue Jan 21 13:27:43 CET 2003
1. GENERAL SECTION
1.1 trace settings
RfcAdapter.trace=2
-> adapter trace level 0 = none
 1 = error
 2 = standard
 3 = request
 4 = payload
 5 = binary payload outbound
#RfcAdapter.traceStack=0
#RfcAdapter.listenException=0
#RfcAdapter.listenState=0
-> additional trace switches (in general not needed)
RfcAdapter.traceFile=./LogFiles/Adapter_rfc.log
-> name of trace file (traces to stdout if not specified)
 NOTE: in a productive environment, the trace file should be written to the
 log-file directory of the Adapter Engine
1.2 connectivity settings
RfcAdapter.registerInbound=sourceBackendXD1
-> space-delimited list of logical names for inbound R/3 systems subsections.
 The adapter will register with all R/3 systems defined in this list and
 those systems can send RFC requests into the XI via an RFC destination
 that has to be setup in SM59 to point to the RFC Adapter
RfcAdapter.accessInbound=toXmb
-> logical name for inbound access to XMB subsection
RfcAdapter.registerOutbound=fromXmb
-> logical name for outbound access from XMB subsection
RfcAdapter.accessOutbound=targetBackend
-> space-delimited list of logical names for pre-allocated outbound R/3 systems subsections.
 This is an option to speed up connection setup during request processing. The RFC Adapter
 preallocates sessions to all listed R/3 systems.
RfcAdapter.clientCloseConn=1
-> close calling connections after call (1) or just reset session (0)
 NOTE: the reset mechanism is slightly faster for request processing. However, it does
 not re-connect after a target system shutdown and hence requires a restart of the
 RFC Adapter in such a situation.
#RfcAdapter.maxDynPools=128
-> maximum number of dynamically allocated client pools to access outbound R/3 systems
#RfcAdapter.minDynPoolSize=4
-> initial number of clients in dynamically allocated client pools
#RfcAdapter.incDynPoolSize=4
-> increment number of clients in dynamically allocated client pools
#RfcAdapter.maxDynPoolSize=64
-> maximum number of clients in dynamically allocated client pools
2. SUBSECTION FOR REGISTRATION TO CLIENT APPLICATION SYSTEMS
(one subsection per incoming R/3 system; requires callback service user for repository access)
RfcAdapter.sourceBackendXD1.host=db03
RfcAdapter.sourceBackendXD1.sysnr=00
RfcAdapter.sourceBackendXD1.progid=Rfc2XmbService
-> recommended is: RfcAdapter.sourceBackend.progid=Rfc2XmbService
RfcAdapter.sourceBackendXD1.poolsize=5
RfcAdapter.sourceBackendXD1.unicode=1
-> source system is Unicode installation (1) or not (0)
RfcAdapter.sourceBackendXD1.client=500
RfcAdapter.sourceBackendXD1.user=XIAPPLUSER
RfcAdapter.sourceBackendXD1.passwd=********
RfcAdapter.sourceBackendXD1.lang=EN
RfcAdapter.sourceBackendXD1.trace=2
-> enable RFC trace for this connection (1) or not (0)
#RfcAdapter.sourceBackendXD1.sncName=<SNC_name_of_adapter>
-> e.g. RfcAdapter.sourceBackendXD1.sncName=p:CN=USERNAME, O=ORGNAME, C=DE
#RfcAdapter.sourceBackendXD1.sncLib=<SNC_library_path>
-> e.g. on Win2K: RfcAdapter.sourceBackendXD1.sncLib=C:
Program Files
SECUDE
SECUDE for R3
secude.dll
#RfcAdapter.sourceBackendXD1.sncQop=<SNC_quality_of_protection>
-> 1,2,3,8,9 e.g. RfcAdapter.sourceBackendXD1.sncQop=1
#RfcAdapter.sourceBackendXD1.sncAcl=<SNC_access_control_list>
-> logical names for allowed callers e.g. RfcAdapter.sourceBackend.sncAcl=peerB6A peerB6Q
#RfcAdapter.sourceBackendXD1.sncAcl.peerB6A=p:CN=B6A, O=SAP-AG, C=DE
#RfcAdapter.sourceBackendXD1.sncAcl.peerB6Q=p:CN=B6Q, O=SAP-AG, C=DE
-> details for peer ACL lists
3. SUBSECTION FOR ACCESS TO XMB INBOUND RFC SERVICE
(only one entry possible)
RfcAdapter.toXmb.host=web03
RfcAdapter.toXmb.sysnr=00
RfcAdapter.toXmb.poolsize=5
RfcAdapter.toXmb.client=100
RfcAdapter.toXmb.user=XIAPPLUSER
RfcAdapter.toXmb.passwd=******
RfcAdapter.toXmb.lang=EN
RfcAdapter.toXmb.trace=2
4. SUBSECTION FOR REGISTRATION OF XMB OUTBOUND RFC SERVICE
(only one entry possible)
RfcAdapter.fromXmb.host=web03
RfcAdapter.fromXmb.sysnr=00
RfcAdapter.fromXmb.progid=Xmb2RfcService
this value must be in sync with Program Id setting for AI_RFCADAPTER_JCOSERVER in SM59
RfcAdapter.fromXmb.poolsize=5
RfcAdapter.fromXmb.unicode=1
-> source system is Unicode installation (1) or not (0)
RfcAdapter.fromXmb.trace=2
5. SUBSECTION FOR ACCESS TO SERVER APPLICATION SYSTEMS
(one subsection per outgoing R/3 system; pre-allocated connection pools via service user)
RfcAdapter.targetBackend.host=db03
RfcAdapter.targetBackend.sysnr=00
RfcAdapter.targetBackend.poolsize=5
RfcAdapter.targetBackend.client=500
RfcAdapter.targetBackend.user=XIAPPLUSER
RfcAdapter.targetBackend.passwd=*******
RfcAdapter.targetBackend.lang=EN
RfcAdapter.targetBackend.trace=2
END OF RFC ADAPTER CONFIGURATION PROPERTIES
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%Log data for the adapter%%%%%%%%%%%%%%%%%%%%%%%%%%
Fri Sep 24 09:50:09 EDT 2004 *****
09:50:09 (6011): RFC adapter initialized
09:50:09 (6031): RFC adapter started
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%SM59 entries on the XI box%%%%%%%%%%%%%%%%%%%%%%%%%%
Name: AI_RFCADAPTER_JCOSERVER
Program ID: Xmb2RfcService
Action Type: Registered Server Program
Gateway: web03 (Local XI box)
Gateway Service: sapgw00 (00 is the system number)
Name: XI_SERVER
Program ID: Rfc2XmbService
Action Type: Registered Server Program
Gateway: db03 (R3 box)
Gateway Service: sapgw00 (00 is the system number for R3)
Both the entries are tested fine.

XI and RFC adapter

Hi
The RFC Adapter configuration has been done successfully and the adapter starts up successfully.
In our scenario, we attempt to receive an xml message from my local machine through a file adapter, and pass this along to the RFC Outbound adapter to execute a RFC on the CRM box.
The following error message is encountered in the XI monitoring tool.
==============================================================================================================
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
<SAP:Context />
<SAP:Code p1="connection closed (no data)" p2="" p3="" p4="">RFC_ADAPTER.SYSTEM_FAILURE_OUTBOUND</SAP:Code>
<SAP:Text language="EN">System error when calling the outbound RFC adapter (connection closed (no data))</SAP:Text>
</SAP:ErrorHeader>
===================================================================================================
I then stop the RFC adapter and attempt the scenario again. I get the following error message in XI monitoring tool.
================================================================================================================
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
<SAP:Context />
<SAP:Code p1="Exception in handleRequest of server Xmb2RfcService: java.lang.Exception: Bean n" p2="" p3="" p4="">RFC_ADAPTER.SYSTEM_FAILURE_OUTBOUND</SAP:Code>
<SAP:Text language="EN">System error when calling the outbound RFC adapter (Exception in handleRequest of server Xmb2RfcService: java.lang.Exception: Bean n)</SAP:Text>
</SAP:ErrorHeader>
==================================================================================================================

Hi Eduardo ,
Please check wether the following steps are done in BPM:
1.Async Recieve
A.Properties :
Please set the following
Message:Message 1
Mode:asynchronous
B.Container Data :
Declare Message 1 as asynchronous abstract interface with message type of outbound interface(File Structure).
2.Sync Send
Pre-Requisite:
Copy the inbound Syncronous Interface to Sync_interface_abstract by changing the direction in the message interface of Interface object in the Integration Repository.
A.Properties
Mode:Synchronous
Request:Message 1
Response:Message 2
Syncronous Interface:Sync_interface_abstract
Recievers From :Send Context
B.Container Data:
Message 2 should be declared as the asynchronous message interface with Response message type in inbound interface(Rec Syst Interface).
3.Async send
A.Properties:
Mode:Asynchronous
Message:Message 2
Acknowledgment:None
Recievers From :Send Context
Integration directory has to be configured to send data forth and back to BPM.
1.Send MESSAGE From Outbound interface to BPM.
OutBound and Abstract Interface needs to be mapped in the interface determination and Abstract interface has to be binded to Business Process Name in the repository.
Outbound->Your OutBound Interface(File Interface)
Abstract->Message 1
Reciever Service-> Your Business Process Name
2.Send MESSAGE From BPM to Inbound interface.
Abstract and Inbound interface needs to be mapped in the interface determination and Abstract Interface has to be binded to the Receiver Service/Business System.
Abstract->Message 1
Inbound->Your Inbound Interface(RFC)
Reciever Service-> RFC SYSTEM(SAP)
These are the general steps to follow for Async/sync pattern.
Please let me know if all the steps are configured.

Attachments with RFC adapter ?

Dear Experts,
I have a SOAP 2 RFC Synchronous Interface in my project, from sender side i.e from SOAP i am receiving data of 20 fields and also the attachment(the format of the file can be JPEG, EXCEL, WORD DOC or VIDEO Files) and these needs to be transferred to SAP R/3 System using RFC Adapter.
1. can RFC adapter able receive and send these format of attachments to r/3 server ? can you please suggest me on this...

Hi Raj,
Thanks..
The attachment will not go to the file system in ECC, as i stated that sender is sending the Data & attachments, at the ECC system a INCIDENT(SAP HSE) will be created by using the RFC, when you open the Incident in ECC system you should able to see the data in the Incident along with the attachment attached.
Regards,
Ravi

Problem with sender RFC adapter

Hi All
I have created one RFC adapter for which i have created wrong business system and all then i have deleted that and i have created on more RFC adapter but when i am testing my scenario its taking the old one which i have deleted from the Integration directory. I have refreshed the cache using sxi_cache and also in RWB. But still i m getting the same error...
Could you please tell me how to resolve this error

Hi
Yes i have configured RFC as sender communication channel. I have deleted the old one including the business system. but still in adapter monitoring i m getting the error "com.sap.aii.af.rfc.afcommunication.RfcAFWException: alternativeServiceIdentifier: party/service from channel configuration are not equal to party/service from lookup of alternativeServiceIdentifier (CPA party/service/channel ''/'Whirlpool_BS1'/'RFC_Source_CC', lookup of alternativeServiceIdentifier for party '', schema 'TechnicalSystem' with 'QN9#800' returned party/service of ''/'QN9')"
but i have deleted the whirlpool_bs1 business system.
Why still i m getting this error.
Thanks & Regards
SUN

Error in using XI-SOAP adapter, but no error with SAP-BC

Hi,
I am working on RFC->XI->Webmethod (.asp) scenatio.
I am using SOAP adapter.
Whin I am not using "Do not use SOAP Envelop".
I am getting "com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/HTML" Error in SXMB_MONI.
But when I am using "Do not use SOAP Envelop" then I am not getting any error. in SXMB_MONI status showing Successfully Processed. But the responce i am getting is "You are not authorized to view this page // HTTP 401.1 - Unauthorized: Logon Failed"
But same web-service is working fine while connected with SAP-BC.
Please Help why scenario is working with BC, but not with XI.
Thanks & Regards

Hi Bhavesh,
Thanks for reply.
I am getting all success in message monitoring, but still web-services sying they are not getting any message.
I am attaching all 4 logs for one synchronous communication of message monitoring.
I am not able to understand where message going and why XI showing success every where.
********1st(Sent Messages)
Success SOAP: response message leaving the adapter
Success Application attempting to send an XI message asynchronously using connection AFW.
Success Trying to put the message into the send queue.
Success The response message for message cf4fd921-4a74-11db-9312-001279933263(INBOUND) was successfully transmitted to the calling application.
Success The message status set to DLVD.
Success The application sent the message asynchronously using connection AFW. Returning to application.
********2nd (Sent Messages)
Success RFC adapter received sRFC for Z_PA_SAP_TO_Webservice from D02/230. Attempting to send message synchronously
Success Application attempting to send an XI message synchronously using connection AFW.
Success Trying to put the message into the call queue.
Success Message successfully put into the queue.
Success The message was successfully retrieved from the call queue.
Success The message status set to DLNG.
Success The message was successfully transmitted to endpoint http://XYZ.com:8000/sap/xi/engine?type=entry using connection AFW.
Success The application sent the message synchronously using connection AFW. Returning to application.
Success The message status set to DLVD
**********3rd (Received Messages)
Success Using connection AFW. Trying to put the message into the receive queue.
Success The XI response message for message d0372be1-4a74-11db-91d7-001279933263(INBOUND) was successfully returned to the calling application.
Success The message status set to DLVD.
**********4th (Received Messages)
Success The message was successfully received by the messaging system. Profile: XI URL: http://XYZ.com:50000/MessagingSystem/receive/AFW/XI
Success Using connection AFW. Trying to put the message into the request queue.
Success Message successfully put into the queue.
Success The message was successfully retrieved from the request queue.
Success The message status set to DLNG.
Success Delivering to channel: IF_O_502_WebserviceBusService_SOAP_In_02
Success SOAP: request message entering the adapter
Success SOAP: completed the processing
Success SOAP: response message received d0372be1-4a74-11db-91d7-001279933263
Success The message status set to DLVD.
Success The message was successfully delivered to the application using connection AFW.

Middleware problem -Outbound queue is stuck in SAP R/3 system with message

Hi Middleware gurus ,
We are stuck with a serious issue . We are trying to download Business partners from SAP R/3 4.6c system to SAP CRM 5.2 system using CRM Middleware
Previously we did a successful Initial download of 2 Business partners from SAP R/3 to CRM . Their BP numbers in CRM are 001 and 002 . The Delta load is working fine for the both the BPs which are already downloaded
Now , the real problem is when we are trying to download a new Business partner . When we set the Filter ( BP no 003 ) in MW adaptor object CUSTOMER_MAIN and start the Initial load again , we see that the Outbound queue is getting stuck with message STOP .
There are two queues generated in SAP R/3 system with names MASS_CRM_CUSTOME and R3AD_CUSTOME . The status for both the queues is STOP and when go for details it mentions sapsuck ..SAPMSSY1 -Message no. SR 053.
Even we checked the txn SMW01, the Bdocs message is "Recived ( Intermediate state) " for Bdoc type BUPA_MAIN.
We really dont as to why the Initial load worked fine with 2 BPs and later when want to do more BP Initial Load the Outbound queue is getting stuck
Also , by unlocking the 2nd queue R3AD_CUSTOME we are able to release it , but the first queue MASS_CRM_CUSTOME* is stuck
Please help us urgently
Regards
Dinesh and Ritvij
Email : [email protected]
Mobile -+91=9704933315

Hi Praveen and other Middleware gurus,
We checked on this . Actually the RFC is used for connecting to SAP R/3 system.
We also raised an OSS message on this and found a reply that in transaction CRMM_BUPA_MAP, we can map the required BP . But the SAP support guy recived an error received the error:
An RFC link is not maintained in the Middleware
Message no. CRM_BUPA_MAPPING051
We have set the RFC link , but still the problem continues!!!
Please help further..
Regards
Dinesh and Ritvij

Monitoring of older RFC Adapter messages - RFC API

Hi,
I have successfully implemented a number of scenarios (File to rfc & File to Idoc)that required external data lookup - using the RFC API (calling a customer RFC FM) (and parsing the response with DOM).
I am also using Global variables to store my lookup responses to help minimize the number of RFC calls invoked.
When trouble shooting - as expected the log in the communication channel for the RFC adapter shows the BAPI response. However the number of records is always restricted to 25.
If I process a message with 30 records, and lets say the first RFC Lookup fails but the remaining 29 are successfully - because the log is limited to 25 I lose a record of this error.
Am I missing another method of search?
Is this just a display restriction and perhaps I could report over the underlying tables myself?
Regards
Andrew

Communication channel monitoring is as i understood primarily für monitoring the module chain a message is eventually running through. Did you try monitoring via RWB->Message Monitoring or sxmb_moni? There also should be a reference to the response. Maybe I didn´t get you right, but as far as I remember RFC Calls are also listed there with a bigger history.
Thomas

Mapping Error - Dump source message to file adapter comm channel

Hi
Does anyone know of a way to dump the source message to a file adapter comm channel if - and only if - the message fails during mapping. For example, we receive a message from a trading partner that lacks an element that is mandatory during the mapping. When the mapping fails, the source message is sent - as is - to a file adapter comm channel.
I don't need anything more than the source message i.e. no need for any errors etc... to be included.
The kicker.. I would like to do this without using BPM if at all possible.
Any ideas greatly appreciated. Thx, Duncan

Hey Ram,
Go to Integration Directory and open the Receiver Determination for your scenario.
Check the configured receiver services. They are in a table-like area in the middle of the screen.
In this table of configured receiver services for that particular Sender Service/Interface, you should have the system that normally receives that message (your ERP or any other application system) and the service that contains the receiver file comm channel that will receive the message in case of error.
Check help.sap.com for help on condition editor on receiver determinations.
Now, the issue. You can only check whether a field exists, you can't check whether it doesn't exist (There's only a "EXIST" operator, and no negative operator). Thus, you can only do the following: always send messages to File, but you can avoid messages that dont have field from being sent to App System. Yeah, that sucks...
But don't fear, young padawan! There is a possible workaround. =D
In your message mapping, do the following for that particular field:
If field exists (check with Exist and IF standard functions) just bypass the field. Else, map the field with an impossible value (like string "$CREATED$"). Then, in your receiver determination, you will do the following conditions:
for App System: If field =/= $CREATED$
for File Receiver: If field = $CREATED$
Now, if the field doesnt exist, it will have value $CREATED$, thus the message will be sent to File and not to App System. If the field exists, the message will be sent to App and not to File.
Try that out.
Regards,
Henrique.

Restrict messages in RFC adapter or in source/sending (SAP R/3) system

Similar Messages

Maybe you are looking for