Skip to Content
0
Jun 10, 2009 at 09:24 AM

File to RFC scenario

142 Views

Hi,

I am working on a File to RFC scenario. Purpose of this interface is to update the values coming from File into the R3 database. I have configured this as asynchronous scenario.

Scenario is working fine. But I am facing validation issues. Sender field 'Country' from File has its corresponding receiver field 'MANCOUNT' in RFC/BAPI. It will accept values like 'IN','US','UK' , etc. only.

I have given value 'XX' in the sender field-Country. Receiver RFC adapter processed the message successfully in Communication Channel Monitoring logs. But nothing is updated in R3 as 'XX' for MANCOUNT will fail in BAPI. This is captured in BAPI.Response. But I have not mapped BAPI.Response as it is asynchronous Scenario.

Please suggest how to handle this situation. Do I need to map the BAPI.Response to fault messages?