File to SOAP,error in sender file adapter

Hi,
I am doing a scenario FILE to SOAP where In file adapter I am using Quality od service as Exactly once in order.I am getting the below error.It works fine when I use QOS=Exactly once.Not sure why,can you guys please help me.Can we really use QOS-EOIO for sender file adapter,where exacly do we use it.
Thanks
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/HTML</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Edited by: guest xi on Apr 16, 2008 11:55 AM

Hi,
Thanks for your replies guys.I diid give the queue name ,I dont know what is causing the error.Now even QOS=EO which was working fine before is throwing an error.I am using the same file name for both
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/HTML</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

Similar Messages

System error when send file with Sender File Adapter

Hi all,
I have configured a "File To ABAP Proxy" scenario. After configuring, i executed a "Test Configuration" in Integration Directory and it's all OK. But this file unable to reach into ABAP Proxy Target. In the Runtime WorkBench\Message Monitoring, I get an error message in below:
Engine: Adapter Engine
Status: *System Error     *
Start: 15.08.2008 14:04:01
End: 15.08.2008 14:19:01
Sender Service: BS_XI_SERVER
Interface Servic: urn://FILE_TO_PROXY
MI_EMPLOYEE_OB
In this case, I don't know why my Sender File Adapter is error and why status is "System Error" and why it can't reach into Target System. Can it concern a role user?
( For more clearly: I configured the source file and the path correctly. And i used the xml file with the content and the document name correctly. In general, the Sender Adapter File don't convert the sender file and its content is same as the Payload in the "Test Configuration", i think it is all OK.)
Could anyone please help me to resolve this problem, anyone can explain this error, how can i resolve this error?
Thanks a lot in advance,
Vinh Vo

Hi Chirag,
1.I source structure is very simple as below:
<ns0:MT_MATERIAL xmlns:ns0="urn://FILE_TO_PROXY">
   <MATERIAL>
      <WERKS>1000</WERKS>
      <MATNR>MAT00001</MATNR>
      <MAKTX>Chemical Material</MAKTX>
   </MATERIAL>
</ns0:MT_MATERIAL>
2. the Communication Channel Monitoring in Runtim WorkBench\Adapter Engine is OK for my Sender File Communication Channel, it's in Blue Light.
However, i don't know what's FCC?
Thanks and best regards,
Vinh Vo

How to pick files from multiple directories via Sender File Adapter?

Hi guys,
I have a scenario File to IDOC. The Sender File Adapter has to take all files: .xml from Source directory E://Current/.
Actually directories are like
E:/Plant1/Current/
E:/Plant1/History/
E:/Plant2/Current/
E:/Plant2/History/.
Can I have one Sender File Adapter to pick all *.xml files
from
E:/Plant1/Current/ and
E:/Plant2/Current/ and how can I write it in Source Directory of Communication Channel?
Or do I have to have a Sender File Adapter for each Plant?
Any suggestion please?
Kind regards,
Danijela Zivanovic

Hey
You might wanna have a look at "Additional selection for source file" parameter in sender file adapter.
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/singleSenderFileCC4MultipleDirectories
XI/PI: how to exclude files in a sender File adapter?
Even though this method works but there are some constraints,please check help.sap.com for constraints.
Thanx
Aamir

Seeburger AS2 resent of files in state "Error on send, will be retried"

Hi,
I have a few AS2 files in state "Error on send, will be retried" in the Seeburger AS2 monitor, which does not seem to be sent.
How can I trigger the files to be sent again or delete so we can resent the files from the backend.
Daniel Graversen
[Figaf|http://figaf.com]

Hi,
we have some messages in this status but none of them is displayed in the recovery monitor..
Any other idea?
Thank you,
Peter

Archive file with errors in sender file adapter not working! please help!

Hi Experts,
I have a file to RFC scenario. the input is a XML file. I have setup the flag in sender file adapter channel for archiving the input files with errors. But it is not working.
For testing I have used an invalid xML file for example without the main XML tag. I have also tested with a MSWORD file saved with.xml extension. But in both the cases the files are not getting archived.
My archive location permissions are fine and in fact normal archive operation is happening. That is, if I select the processing mode as "Archive" and gave the Archive directory then files are getting archived. The problem is only with the "Archive faulty source files" option.
What am I missing? DO I need to do some more configurations?
What are the prerequisites if any for this option?
How to test this?
Please help me! I will be greatfull to you all!
Thanks & Regards
Gopal

and go thru this links
Creating a Single Archive of the Version Files
http://help.sap.com/saphelp_nw04/helpdata/en/79/1e7aecc315004fb4966d1548447675/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/31/8aed3ea86d3d67e10000000a114084/frameset.htm
Note: reward points if solution found helpfull
Regards
Chandrakanth.k

Error in sender file adapter: source directory does not exist

Hi,
The PI system is 7.11
I've created sender file adapter with following details:
Transport Protocol : File System
Source directory: /interfaces/In
I checked in AL11 that this path really exists and it does. (I can even see the .txt file that should be processed.)
But still i get in Communication Channel Monitoring the following error:
"Configured Source directory "/interfaces/In" does not exist.
(i also tried to give the source directory as "interfaces/In" and as "//interfaces/In" but still the same error.
Any suggestions as to what is wrong?
kr
Robert

Actually, Need to use forward slash (/) to separate directory names in accordance with the Java specification.
But wanted to try if that works..
Also check directory name , path again as this is case sensitive...
--Divyesh

'Source Directory doesn't exist' error in sender file adapter

Hi All,
I m getting the error 'Source Directory doesn't exist' in sender file adapter.
The source file directory doesn't exist in XI Server. Its in a different system.
gone through other sdn t hreads.
the options seems to be
1. either to mount the Source Directory on the XI Server.
2. Install a FTP server and use FTP protocol.
My doubt is that, could nt we give necessary access rights to the XIAFUSER whihc will access the Source Directory?
Wont it be sufficient?

Hi Aarthi,
If you are using system other than XI, then you have to use FTP server
else check you have proper authorization of read/write to the source directory...
and check the name of it as well, as it is case sensetive and you have provided the proper details of server.
check these blog as well...
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
/people/shabarish.vijayakumar/blog/2006/08/01/along-came-a-file-adapter-mr-ftp-and-rest-of-the-gang
Sachin
Edited by: Sachin Dhingra on Mar 24, 2009 12:16 PM

File to Soap error in RWB

Dear Friends,
I am working on File to Soap scenario,In this scenario File is picking succssfully and posting to target side I got the error in RWB like
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to read request. ---> There is an error in XML document (1, 2205). ---> Input string was not in a correct format.
How to correct the input string , Please suggest how to resolve this issue.
Thanks & Regards,
Shalini Shah.

This error occurs when:
1) Incorrect data structure is send to the SOAP application ..... compare the payload that you are sending to the SOAP application with the WSDL structure that you have imported in IR .... both should match exactly....also confirm that the WSDL you are using the latest one.
2) Target URL/ Action is not properly configured in the receiver SOAP channel
3) Is your target system up and running?
Regards,
Abhishek.

File To Mail - Error in sender CC

Hi All,
I am trying out a File to mail scenario following the Blog /people/michal.krawczyk2/blog/2005/03/07/mail-adapter-xi--how-to-implement-dynamic-mail-address
I am getting the following error in the File Sender Comm Channel :
Mail: error occurred: com.sap.aii.af.mp.module.ModuleException caused by: com.sap.aii.messaging.srt.BubbleException: Failed to call the endpoint [null "null"]; nested exception caused by: java.io.IOException: no sender address specified
I could also see the payload is empty in the Receiver Mail CC
Now can anybody help getting me the mail ...
Thanks in advance

Hi Bhavesh,
I get a checkered flag in Moni ,
But the response has only SOAP header and Body with out payload , I Mail package is checked and base64 is selected ..
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">Party normalization: sender</Trace>
<Trace level="1" type="T">Sender scheme external = XIParty</Trace>
<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
<Trace level="1" type="T">Sender party external =</Trace>
<Trace level="1" type="T">Sender party normalized =</Trace>
<Trace level="1" type="T">Party normalization: receiver</Trace>
<Trace level="1" type="T">Receiver scheme external =</Trace>
<Trace level="1" type="T">Receiver agency external =</Trace>
<Trace level="1" type="T">Receiver party external =</Trace>
<Trace level="1" type="T">Receiver party normalized =</Trace>
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- 
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
<Trace level="1" type="T">COMMIT is done by XMB !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = XIL</Trace>
<Trace level="1" type="T">client = 002</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PIAFUSER</Trace>
<Trace level="1" type="Timestamp">2006-09-14T09:48:04Z CET</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = 1DC20B0043D611DBC937000D60D4EDB5</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="1" type="T">Queue name : XBTI0009</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0009</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="1" type="T">system-ID = XIL</Trace>
<Trace level="1" type="T">client = 002</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PIAFUSER</Trace>
<Trace level="1" type="Timestamp">2006-09-14T09:48:04Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC">
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
<Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
- 
<Trace level="1" type="T">number of receivers: 1</Trace>
<Trace level="1" type="T">Single-receiver split case</Trace>
<Trace level="1" type="T">Post-split internal queue name = XBTO3___0001</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Persisting single message for post-split handling</Trace>
<Trace level="1" type="T" />
<Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="1" type="T">system-ID = XIL</Trace>
<Trace level="1" type="T">client = 002</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PIAFUSER</Trace>
<Trace level="1" type="Timestamp">2006-09-14T09:48:04Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
- <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
<Trace level="1" type="T">Interface Mapping http://sap.com/xi/XI/Mail/30 GK_File2Mail_IM</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
<Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV" />
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_CALL_ADAPTER">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
- <Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
<Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP" />
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Async processing completed OK.</Trace>
<Trace level="1" type="T">system-ID = XIL</Trace>
<Trace level="1" type="T">client = 002</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PIAFUSER</Trace>
<Trace level="1" type="Timestamp">2006-09-14T09:48:05Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>

Consistency check error in sender file content conversion

Dear Experts,
I am trying one simple File to File scenario in which i have only fields 1>salesorder_number 2>Description
I created a txt file with line items "100,crudeoil" with file name as salesorder.txt
In the sender file adapter i have configured the file convertion paramenters as follows:
Document name : mt_salesorder_sender
Document namespace : http://se.com.sa/sec-sa-qax "Namespace of message type
Recordset Structure : document,*
document.endSeparator : 'nl'
document.fieldSeparator: ,
document.fieldNames : salesorder_number,Description
So after this if i run the scenario In file adapter i am getting the error like "Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Parameter 'document.fieldFixedLengths' or 'document.fieldSeparator' is missing Consistency check: no. of arguments in 'document.fieldFixedLength' does not match 'document.fieldNames' (0 <> 2) "
Please let me know where i am going wrong.
Regards,
Santhosh

Hi,
please maintain the order as
Recordset Structure : document,*
document.fieldNames : salesorder_number,Description
document.fieldSeparator: ,
document.endSeparator : 'nl'
Rgds
joel

Error in sending file using FCC

Hi all,
i am doing the file content conversion scenario from saptechnicalcom
my message type is as follows:
MT_File_Cont_Conv
     Record
        Emp_Header
          Key
          Emp_Id
          Emp_Name
File is not picked up by the sender file adapter and in RWB communication channel monitoring i am getting the following error:
Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Mandatory parameter 'Emp_Header.keyFieldValue': no value found
anybody plz provide me some input to rectify this error
regards
sandeep sharma

>
sandeep sharma wrote:
> hi
> FCC parameters are as follows
>
> Document Name:                    MT_File_Cont_Conv
> Recordset Name:                      Record
> Recordset Structure:                   Emp_Header,1
> Recordset sequence:                    Ascending
> Recordset per message:                 1
> Key Field Name:                         Key
>
>
>
>
> Emp_Header.fieldFixedLengths                   1,6,10
> Emp_Header.endSeparator          'nl'
> Emp_Header.fieldNames          Key,Emp_Id,Emp_Name
> Emp_Header.keyFieldValue                      1
> Emp_Header.keyFieldInStructure                 ignore
make sure there is no white space before or after
Emp_Header.keyFieldValue and also the value 1
Even a single whitespace can cause an issue

Picking file in sequence/Queuing   in sender SFTP adapter.

Hi Experts,
I am using SFTP adapter in sender side, it has no option of quality of service ( EOIO) and queue name as we have in FTP adapter configuration .Is there any predefined module provided by Sap which i use in the modules Tab in communication channel configuration to get the functionality of queuing ? just like we use strictXMlto plain bean etc.
I have 3 files which needs to proccess in a sequence one after another in order.I CANT USE BPM or Even FTP because of Security reasons.
please share you ideas.
Regards,
Anika

Hi all,
I have tried using AF_Modules/DynamicConfigurationBean in module tab present is the sender SFTP adapter with the attribute qualityOfService.
parameter name                  Parameter value
     key.0                         insert http://sap.com/xi/XI/System/Messaging qualityOfService
    value.0                        ExactlyOnceInOrder
But in Moni i dont see the 3 messages didnt go in the same queue.But when i double click and open the dynamic configuration present in the soap header section i can see the values which i given in the module parameter.
Is there any way i can change the quality of service to EOIO at runtime ? how to change the default EO to EOIO.
Regards,
Anika

Error in Sender File Channel

Dear all,
I'm trying to execute a File to File scenario.But I'm getting this error in the sender file channel.
"Putting message into send queue failed, due to: com.sap.aii.af.ra.ms.api.DuplicateMessageException: Message ID a0ff7230-8793-11dc-a4d5-001558e4827d(OUTBOUND) already exists in database: com.sap.sql.DuplicateKeyException: NWMssSQLServer JDBC DriverSQLServerViolation of PRIMARY KEY constraint 'PK__XI_AF_MSG__2B090089'. Cannot insert duplicate key in object 'dbo.XI_AF_MSG'.."
The file is not getting picked, the processing mode is set to "Delete". Please help me out in resolving it.
Any hep would be rewarded.
Regards,
Younus

Hi,
Check whether you have given the filename to other communication channel as well. Because it seems to execute another interface where you have a JDBC been used.
If so change the file name in CC and in your file and check it once again.
Regards,
Nithiyanandam

How to process a text file (mail attachment) using the sender mail adapter?

Hi guys,
Is it possible to process mail attachments using the sender mail adapter? Let's say I have a structured text file (attachment) which needs to be mapped and sent to target system.
Post please any thoughts or experience.
Thanks,
Olian

Hi Olian,
Have a look at these helpful links -
1. http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/9e6c7911-0d01-0010-1aa3-8e1bb1551f05&overridelayout=true
2. http://www.riyaz.net/blog/xipi-configuring-the-sender-mail-adapter/
3. http://help.sap.com/saphelp_nw70/helpdata/en/23/c093409c663228e10000000a1550b0/content.htm
Regards,
Sunil Chandra

How to process files one by one using sender file adapter

Hi,
I have to process file one by one using my file adapter (sender), because while doing the G/R materials get locked, if the same materal exist in other files.
I have maintained QOS as "Exactly Once in Order" & processing Sequence as "by date".
Processing sequence come in which tab? What will be the Queue name?
Thanks,
krishna

It will come under Processing tab
Here you need to select the first parameter QOS as EOIO
Then QUEUE name and processing sequence will be enabled.
NOTE: This will work only for NFS protocol not for FTP.

File to SOAP,error in sender file adapter

Similar Messages

Maybe you are looking for