Limitations of file adapter -urgent

Hi,
The file adapter is not picking a file in production which is having a size of more than 5MB in production.
Is there a limitation for file adapter ?
I heard it has a limitation. How can we resolve this ? Urgent.
Thanks,
John

Hi,
Look into below explanation...
check u r poll intervel and give more time in poll intervel and try...
The processing with huge amount of data with PI7.0
is possible with manipulating some of the parameters in communication channel or in SXMB_ADM or increasing JAVA stack etc.,
It all depends on the how many bytes does each record comprise of...
You can check sap notes for processing huge files.
some times you can increase the java heap size..
you can split the file if you feel it is required
/people/sravya.talanki2/blog/2005/11/29/night-mare-processing-huge-files-in-sap-xi
As you had said about Advanced Adapter Engine to support huge data in PI 7.0
is not available. this feature is in PI7.1 only.
Please go through below link for more details,
SAP NW 7.0 Process Integration - Adapter Framework & Adapter Strategy
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a0ee90b6-e726-2a10-528b-bd493ab5690d
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40faf9ae-1ce5-2910-f89c-f187628ea6a0
but you could achive this as per the below blog,
SAP XI acting as a (huge) file mover
/people/alessandro.guarneri/blog/2007/02/21/sap-xi-acting-as-a-huge-file-mover
the above weblog can help u in that..
OR
check the config parameters there.
What you could do is, poll for the file, and in the adapter, you could split the file and send 500 records each at a time.
This would reduce the load considerably.
here are some good discussion about it,
File Adpater: Size of your processed messages
File Adpater: Size of your processed messages
Night Mare-Processing huge files in SAP XI
plz award points
thanq

Similar Messages

Problem Using File adapter(Urgent)

Hi,
I have a simple ESB service where I have one Read File adapter for reading a file and other Write file adapter to write the same file to a folder.
I was able to deploy it to ESB instance successfully.
But when I put a file to read ESB is throwing
"OracleASjms/ESBDeferredTopic" error.
Can any one please help me.
Thanks
Rao.

We would be able to help you better if you provided the full error stack as this is very generic.
Generally the most common issue with the file adapter is permissions, make sure the SOA suite owner is able to read and write on the directory and the file.
otherwise post the error stack which may identify the real cause.
cheers
James

Sender File Adapter Problem when text document is a single line.

Hi All,
I have posted this question earlier too. But did not get a proper answer.
I am using File adapter to fetch data from a file system.
My input data is: AA123BB45678AA345BB78564.
It is just reading the first segment i.e.AA123 and not reading the remaining.
How can I configure my Sender File adapter to pick this pattern of data? It works fine if I have line break after each record that is if the input is as below.
AA123
BB45678
AA345
BB78564
In the above there is a Line break after each segment. So File adapter picks it fine.
I have also tried using xml.A.endSeparator equals to blank in the module configuration. But it does not work either.
Can anyone throw some light to this?

Abhi
I tried a different approach to send your file data In..
You can get each line in the source structure in separate row as
<?xml version="1.0" encoding="utf-8" ?>
- <ns:SingleRowDT xmlns:ns="http://xxxxx.com/xi/pocs/sriram">
- <Recordset>
- <row>
<rowElt>AA123BB45678AA345BB78564</rowElt>
</row>
- <row>
<rowElt>AA123BB45678AA345BB78564AA123BB45678AA345BB78564</rowElt>
</row>
- <row>
<rowElt>AA123BB45678AA345BB78564AA123BB45678AA345BB78564AA123BB45678AA345BB78564</rowElt>
</row>
</Recordset>
Now you can use a suitable mapping logic to split the individual records into the 2 field structure as expected in the target..
Trying your way would be a limitation on file adapter I think..Let me know if this helps..I can give you the content conversion config for this model..
its simply
RecordSet - Leave it empty
RecordSet Seq - Row, *
Recordsets/msg - *
row.fieldSeparator - 'nl'
row.endSeparator - 'nl'
row.fieldNames - 'rowElt
..So each line will be pulled into a single Row in the source structure and then u can apply a specific mapping to split into 2 fields for your target
Regards
Sriram V.
Regards
Sriram V.

Limiting the number of files being picked up by the sender file adapter

We are running a file adapter to collect xml files from a legacy system in a shared network location. The files are picked up, information is sorted and mapped, and then sent to a proxy on our CRM system to store the data. Very simple and not-complex.
Our initial data load will consist of somewhere in the neighborhood of 900k records, which is killing CRM.
A co-worker with a bit more experience was telling me that he believes there is a way to limit the number of files that will be pulled per iteration of the file communication channel. If this is the case, can someone share with me the parameters that need to be set?
My apologies if this is a duplicate post - I have tried to look for a good answer in the forums and have come up empty.
We are running PI 7.1, and I believe it is SP 6.
Thanks in advance for the help,
Ben

Hi Ben,
There is no standard way to limit the number of files to be processed by the communication channel.
On the Sender File CC, there is a parameter " Maximum File Size" which restricts the files bigger than the specific size, but this is just a prevention not a solution.
If you have a single big size file, then somehow you have to create small sized files out of it.
Thanks,
Pooja Pandey

Limitation of sender file adapter

Hi Gurus,
     I am working on a file to proxy scenario.Data is coming from MDM and goes to BW through PI. The question is approx. 1,70000 records will be passing from MDM through PI to BW. Is my File adapter is well versed to handle the said quantity of records at one shot? If,not what is the other alternative. If file adpater is not able to handle then i need to tell my clients with a valid proof.
Can anyone help me out.I have points for every valid answer.
Thanks
Veeru

>
viru srivastava wrote:
> Hi Gurus,
>      I am working on a file to proxy scenario.Data is coming from MDM and goes to BW through PI. The question is approx. 1,70000 records will be passing from MDM through PI to BW. Is my File adapter is well versed to handle the said quantity of records at one shot? If,not what is the other alternative. If file adpater is not able to handle then i need to tell my clients with a valid proof.
>
>   Can anyone help me out.I have points for every valid answer.
>
> Thanks
> Veeru
for the maximum file size that can be handled by XI ref File Adapter: SAP Note 821267
in case you have no content conversion happening, more file/record size can be easily handled by XI

Maximum record length in sender file adapter

Hi,
My requrement is to read a test file which contains the records of fixed length of 4096 charcters. I tried a quick test but sender adapter seems to be terminating the records.
Is there any limitation on the number of characters in records which file adapter can read? Please suggest. I am putting togather a prototype for a potential client and it will have a big impact on decision whether PI can be used in project or not.
Thanks for help!

Never tried this one. How ever, were you trying with content conversion? When you say the records are being truncated, can you tell after how many characters the adapter is truncating the record?
VJ

Restricting polling in sender file adapter

Hi friends,
I have a requirement where I need to poll a file from an FTP server. But, if the file is being edited (some other application is writing to it) I need to avoid picking that file. Plz tell me how i can achieve this...waiting for ur replies.
Regards,
Shilpa

Shilpa,
Check out this sap note :
[https://websmp230.sap-ag.de/sap(bD1kZSZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=821267|https://websmp230.sap-ag.de/sap(bD1kZSZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=821267]
File Locking / Incomplete Processing
Q: I sometimes observe that files are processed only partially, i.e., only a fragment from the file's start is converted into an XI message. Nevertheless, the file is usually archived completely. Does the File Sender Adapter honor if another process has locked a file for exclusive use?
A: Unfortunately, the J2EE 1.3 technology the File Adapter is built upon does not support file locking. This limitation affects the File Adapter's operation. Depending on whether the JRE implementation for the operating system under which the adapter runs uses mandatory file locking or advisory file locking, opening a file that is currently being written to by another process will fail or not.
If opening the file fails, no problem exists and the adapter will try to open the file each poll interval until it succeeds.
However, if opening the file is not prevented by the operating system, the adapter starts to process the file although it is still being modified. Since XI 3.0 SP11 / PI 7.0 there is a parameter named "Msecs to Wait Before Modification Check" in the advanced settings of the File Sender channel configuration to work around this issue. This setting causes the File Adapter to wait a certain time after reading, but before sending a file to the Adapter Engine. If the file has been modified (which is basically determined by comparing the size of the read data with the current file size of the input file) after the configured interval has elapsed, the adapter aborts the processing of the file and tries to process the file again after the retry interval has elapsed.
If this option is not available for the settings you would like to use, the following algorithm (to be implemented in your application) may be used to ensure that the File Adapter only processes completely written files:
Create the file using an extension, which does not get processed by the File Adapter, e.g., ".tmp"
Write the file content
Rename the file to its final name, so the File Adapter will notice its existence and pick it up
Hope this will help.
Thanks,
Nilesh

Receiver file adapter settings

Hi,
I have a scenario in which I need to generate a file in tab delimited format. But in the receiver file adapter configuration we have only text/binary file creation mode. By setting the File Type in TEXT mode will I be able to do a tab de-limited file?? Or is there any other configuration settings need to be done?
-Ken

Hi Amanda,
Thank you so much for the great info. I think I can find some stuff but still it would be helpful if you could forward the doc to [email protected] Also, yeah it looks like the receiving file format would be complex with header and footer. In the content conversion can we specify header and footer?? or is there any other way to define...FYI my source file also contains header and footer..I am just a little confused on how to set up the message types for mapping...
Many thanks..
-ken

File Adapter Polling issue(Is there critical value of File size )?

Hi
I use File adapter as the Activation to initialize a BPEL process instance .The source data is a kind of Delimited file format.On my PC, when the file size is less than 4M ,everything works fine ,But when the size increased. The BPEL process will not initialize the instance.When the source data is XML data , the "critical value " is about 12M. The error msg is below.
<2005-08-08 12:48:26,209> <INFO> <default.collaxa.cube.activation> <File Adapter::Inbound> Processing file : D:\Temp\WOSSystemIntegration\InBoundFiles\LOADPLAN_DATA_200508041708.xml
<2005-08-08 12:48:29,455> <INFO> <default.collaxa.cube.activation> <FileAdapter::Inbound> Sending message to Adapter Framework for posting to BPEL engine: { file=D:\Temp\WOSSystemIntegration\InBoundFiles\LOADPLAN_DATA_200508041708.xml
<2005-08-08 12:48:40,197> <ERROR> <default.collaxa.cube> <BaseCubeSessionBean::l
ogError> Error while invoking bean "cube delivery": Delivery callback message se
rialization failed.
An attempt to serialize the delivery callback messages for conversation "LocalGU
ID:d0b7ccf8e4242850:134b07e:10594606738:-7ffc", message "d0b7ccf8e4242850:134b07
e:10594606738:-7ffb" to binary format has failed. The exception reported is:
<2005-08-08 12:48:40,245> <ERROR> <default.collaxa.cube> <BaseCubeSessionBean::l
ogError> Error while invoking bean "delivery": Delivery callback message seriali
zation failed.
An attempt to serialize the delivery callback messages for conversation "LocalGU
ID:d0b7ccf8e4242850:134b07e:10594606738:-7ffc", message "d0b7ccf8e4242850:134b07
e:10594606738:-7ffb" to binary format has failed. The exception reported is:
<2005-08-08 12:48:40,245> <ERROR> <default.collaxa.cube.activation> <AdapterFram
ework::Inbound> [Read_ptt::Read(loadPlanCollection)] - JCA Activation Agent was
unable to perform delivery of inbound message to BPEL Process 'bpel://localhost/
default/P2E_WOS_LP~1.0/' due to: Delivery callback message serialization failed.
An attempt to serialize the delivery callback messages for conversation "LocalGU
ID:d0b7ccf8e4242850:134b07e:10594606738:-7ffc", message "d0b7ccf8e4242850:134b07
e:10594606738:-7ffb" to binary format has failed. The exception reported is:
<2005-08-08 12:48:40,245> <ERROR> <default.collaxa.cube.activation> <AdapterFram
ework::Inbound>
com.oracle.bpel.client.ServerException: Delivery callback message serialization
failed.
An attempt to serialize the delivery callback messages for conversation "LocalGU
ID:d0b7ccf8e4242850:134b07e:10594606738:-7ffc", message "d0b7ccf8e4242850:134b07
e:10594606738:-7ffb" to binary format has failed. The exception reported is:
at com.collaxa.cube.engine.delivery.DeliveryHandler.initialPostAnyType(D
eliveryHandler.java:328)
at com.collaxa.cube.engine.delivery.DeliveryHandler.initialPost(Delivery
Handler.java:219)
at com.collaxa.cube.engine.delivery.DeliveryHandler.post(DeliveryHandler
.java:83)
at com.collaxa.cube.ejb.impl.DeliveryBean.post(DeliveryBean.java:181)
at IDeliveryBean_StatelessSessionBeanWrapper22.post(IDeliveryBean_Statel
essSessionBeanWrapper22.java:861)
at com.oracle.bpel.client.delivery.DeliveryService.post(DeliveryService.
java:161)
at oracle.tip.adapter.fw.AdapterFrameworkListenerBase$DeliveryServiceMon
itor.send(AdapterFrameworkListenerBase.java:2340)
at oracle.tip.adapter.fw.AdapterFrameworkListenerBase.executeDeliverySer
viceSend(AdapterFrameworkListenerBase.java:478)
at oracle.tip.adapter.fw.AdapterFrameworkListenerBase.deliveryServiceSen
d(AdapterFrameworkListenerBase.java:535)
at oracle.tip.adapter.fw.jca.AdapterFrameworkListenerImpl.performSingleA
ctivation(AdapterFrameworkListenerImpl.java:699)
at oracle.tip.adapter.fw.jca.AdapterFrameworkListenerImpl.onMessage(Adap
terFrameworkListenerImpl.java:567)
at oracle.tip.adapter.fw.jca.messageinflow.MessageEndpointImpl.onMessage
(MessageEndpointImpl.java:121)
at oracle.tip.adapter.file.inbound.ProcessWork.publishMessage(ProcessWor
k.java:651)
at oracle.tip.adapter.file.inbound.ProcessWork.doTranslation(ProcessWork
.java:456)
at oracle.tip.adapter.file.inbound.ProcessWork.processMessages(ProcessWo
rk.java:200)
at oracle.tip.adapter.file.inbound.ProcessWork.run(ProcessWork.java:139)
at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:267)
at java.lang.Thread.run(Thread.java:534)
<2005-08-08 12:48:40,245> <INFO> <default.collaxa.cube.activation> <File Adapter
::Inbound> Failed to send message {D:\Temp\WOSSystemIntegration\InBoundFiles\LOA
DPLAN_DATA_200508041708.xml} to Adapter Framework.
<2005-08-08 12:48:40,245> <WARN> <default.collaxa.cube.activation> <AdapterFrame
work::Inbound> [Read_ptt::Read(loadPlanCollection)] - onReject: Sending invalid
inbound message to Exception Handler: file://D:/Temp/WOSSystemIntegration/Reject
edMessages
<2005-08-08 12:49:44,617> <FATAL> <default.collaxa.cube.activation> <AdapterFram
ework::Inbound> [Read_ptt::Read(loadPlanCollection)] - Resource Adapter requeste
d Process shutdown
<2005-08-08 12:49:48,676> <INFO> <default.collaxa.cube.activation> <AdapterFrame
work::Inbound> Adapter Framework instance: OraBPEL - performing endpointDeactiva
tion for portType=Read_ptt, operation=Read
<2005-08-08 12:49:48,676> <INFO> <default.collaxa.cube.activation> <File Adapter
::Inbound> Endpoint De-activation called in adapter for endpoint : D:\Temp\WOSSy
stemIntegration\InBoundFiles
<2005-08-08 12:49:49,042> <INFO> <default.collaxa.cube.activation> <AdapterFrame
work::Inbound> JCAActivationAgent::onStateChanged State is changed for process '
bpel://localhost/default/P2E_WOS_LP~1.0/', state=OFF
how can i solve this problem?can i predeploy some parameter? Is there some critical value of File size for the processing of File Adapter ?

Hi,
There is no specific parameters to specify the maximum file size to be read in. It is just limited by the heap size of the JVM running the BPEL engine.
If you have enough RAM on your machine you can change the current heap size from 512Mbyte to 1Go by editing the startorabpel.bat file
and modifying the line :
set MEM_ARGS=-Xms512m -Xmx512m -Xmn300m -XX:MaxPermSize=80m
to
set MEM_ARGS=-Xms512m -Xmx1024m -Xmn300m -XX:MaxPermSize=80m
But only do it if you have at least 1.5 Gb of RAM on your machine, otherwise ot will keep spawing and you will have very bad performance.
Speaking about performance, do you really need to have a BPEL payload of 4 to 12 Mb ?
Will the BPEL process really need to access it ? if so, the best solution would be using batching techniques to cut you file in pieces and process it piece by peice.
FB.

File adapter polling frequency is not consistent in SOA 10g!

Friends,
I have used file adapter for polling files in a service in SOA 10G env. with polling frequency 3600 secs. However, i have noticed file polling is not happening at 60 mins interval, instead some times files getting polled in less than 30 mins but again after sometime its polling correctly in 60 mins interval. I am not sure what could be the reason but i need a solution urgently. Please help!

Could be the managed servers in the cluster are not in sync.
I faced DB JCA adapter sync issues because of Oracle soa suite bug.
You could check whether any sync issues are there with File adapters.

Receiver file adapter not functioning

Hi guys,
We have developed some interfaces that are exporting some .txt files in ftp locations and therefore they make use of receiver file adapter. Although the receiver file adapter used to function properly some days ago, for some strange reason, it stopped receiving any files. This happens only in XI development system but not in XI production system. In XI development, in Runtime Workbench --> Communication Channel monitoring, I can see this communication channel's status as correctly configured and started, with a green sign on the right, but it is not responding when some files are sent to it, and therefore there are no output files in target directory.
Any ideas?? It is urgent.
Best Regards
Evaggelos

Udo,
Hi Amit,
I went into Message Monitoring for this interface and I can see all the messages for the last 24 hours that should be written into a file that have status "to be delivered".
When I go into Details -->Audit Log for a single message:
2007-06-13 11:49:33 Success Processing child message of multi-message with message ID ff896d50-198a-11dc-cdfa-00145e694b16
2007-06-13 11:49:33 Success Using connection File_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2007-06-13 11:49:33 Success Message successfully put into the queue.
And in Message Data there is the following information:
Status To Be Delivered
Repeatable Yes
Cancelable Yes
Error Category
Error Code
Start 13.06.2007 11:49:33
End
Sender Party
Sender Service TPBS_GR
Receiver Party
Receiver Service TPBS_GR
Interface http://famar.gr:LoyaltyDataMNSToSRS
MI_LoyaltyDataMNSToGR_IB
Quality of Service Exactly Once
Message b2685674-7626-5141-bfa1-13155ad0d25a
Reference
Conversation ID
Serialization Context
Direction INBOUND
Message Type Recv
Profile XI
Connection File_http://sap.com/xi/XI/System
Transport HTTP
End Point http://fmgralxi01:50000/MessagingSystem/receive/AFW/XI
Authorization
Sequential Number 0
Number of Retries 3
Failed 0
Retries 300000
Valid to
Persist Until 13.07.2007 11:49:33
Schedule Time 13.06.2007 11:49:33

Abap mapping and variable substitution in File adapter

Hi experts!!.
I am new in abap mapping, but I can do one abap mapping succesfully, but my problem is:
I need to do a variable substitution in my file receiver adapter:
Target directory = %cliente&/out
File Name Scheme = TC%Fecha%.EFI
¿Using abap mapping is this possible? How I can do it?.
Please is very urgent.
Thanks in advance, and best regarts.

Yes you can,.
DynamicConfigurationKey key = DynamicConfigurationKey.create(
    http://sap.com/xi/XI/System/File,
    FileName);
will become
DynamicConfigurationKey key = DynamicConfigurationKey.create(
    http://sap.com/xi/XI/System/File,
    Directory);
In the receive file adapter all you would need to do is select Adapter Specifc Attributes --> File Name and Directory and givce some dummy values for the filename and directroy. In the runtime values will be taken from the SOAP header which you set in the mapping.
Regards
Bhavesh

Sender File Adapter - FCC - No incoming field separator - How to do FCC?

Hi,
I have a sender File adapter and I need to do the File Content Conversion but there apparently no incoming field separator and the file ocntains just running text - no data records but just information.
For example the incoming file is something like:
                                The Hongkong and Shanghai Banking Corporation Limited                      27JAN2009       PAGE 1
                                Incorporated in Hong Kong with limited liability
ABC IAL LIMITED                                                               ABU DHABI, UAE
ABC MIDDLE EAST                                                               Account No.     001-8888888
ABU DHABI                                                                       Payment Set     AAA
BBB MAIL BOX NO.99                                                             Contact Person ABC LIMITED
                                               7777777777                      Telephone
                                                 AUTOPAY LIST - PROCESSED
                                                 (AUTOPAY-OUT SALARY)
Payment Date           27JAN2009
First Party Narrative .                             66666666
Second Party Narrative .
The Message type that I am mapping to contains:
MT_XXXX
     WA
          Item
          Item2
          Item3
This is so that the information can be mapped to different field areas and send across to the Receiver Mail Adapter. In the mail i receive, i get the running text. I tried giving the field separator as '0x09' but it is not working.
I have also tried WA..fieldContentFormatting to nothing but again no luck.
I have tried with Recordset Sequence with Ascending and variable and have also tried Recordsets per Message with * and blank - but it did not help.
Please advice.
Regards,
Archana

Hi,
I assumed that it was tab but when I made the change in FCC, it did not work.
I would still like to have a output where it looks like below if more than 2 types of information in 1 line as below:
ABC IAL LIMITED                     ABU DHABI, UAE
ABC MIDDLE EAST                  Account No. 001-9999999999999
and not something like:
ABC IAL LIMITED ABU DHABI, UAE
ABC MIDDLE EAST Account No. 001-999999999999
I am not sure what to do here.
Help please.
Regards,
Archana

File Content Conversion Problem: Sender File Adapter

Hi All,
In Sender File Adapter, how to spilt the single line into different lines using + as a separator. Plz see below my source file.
#SMESS=IV01:672633SAP:676968:::NL51:02:11+
COPS=678713:676968:070416:IV01'3:11IVFR=678713:PDA and'IND 2'9206 AD'Dtn'INIVDA=070416IVNR=6264008195:676968add1
#EMESS=0+
In above txt file there are 3 lines.
1st line starts with #SMESS
2nd line starts with COPS
3rd line starts with #EMESS.
In 2nd line, if u observe there are 3 lines separating by +. My task is, I have to spilt the 2nd line into 3 lines using + separator.
I already used the xx.endSeparator as '+' to spilt the line but it is not working....
Could anyone help me how to do this. This is very urgent
Thnx,
Kumar.

Hi Shankar,
1) My Expected XML Structure:
<?xml version="1.0" encoding="utf-8" ?>
- <ns:MT_IV01 xmlns:ns="http://ms.com/dev/ms">
- <Recordset>
- <DT_SMESS>
<D_9901>IV01</D_9901>
<D_9902>672633SAP</D_9902>
<D_9903>676968</D_9903>
<D_9904 />
<D_9905 />
<D_9906>NL51</D_9906>
<D_9907>02</D_9907>
<D_9908>11</D_9908>
</DT_SMESS>
- <DT_COPS_2>
<D_C022>678713</D_C022>
<D_C023>676968</D_C023>
<D_C008>070416</D_C008>
<D_C111>IV01'3</D_C111>
<D_H559>11</D_H559>
</DT_COPS_2>
- <DT_IVFR_2>
<D_C024>678714</D_C024>
<D_D333>PDA and'IND 2'9206 AD'Dtn'IN+</D_D333>
</DT_IVFR_2>
- <DT_IVDA_2>
<D_D365>070416</D_D365>
</DT_IVDA_2>
- <DT_IVNR_2>
<D_D189>6264008195</D_D189>
<D_H364>676968add1</D_H364>
</DT_IVNR_2>
- <DT_EMESS>
<D_D9901_1>0</D_D9901_1>
</DT_EMESS>
</Recordset>
</ns:MT_IV01>
2) I am not getting any error even if I use key Fields or Not becoz in the RecordSet Structure I mentioned DataType, 1 instead of DataType, *.
3) FCC Parameters:
Document Name: MT_IV01
Document Namespace: http://ms.com/dev/ms
Recordset Structure: DT_SMESS,1,DT_COPS_2,1,DT_IVFR_2,1,DT_IVDA_2,1,DT_IVNR_2,1,DT_EMESS,1
Recordset Sequence: Ascending
Key Field-type : String (Case-sensitive)
4) Error:
Conversion of file content to XML failed at position 0: java.lang.Exception: ERROR converting document line no. 2 according to structure 'DT_COPS_2':java.lang.Exception: ERROR in configuration: more elements in file csv structure than field names specified!

Sender File Adapter does not get files when there is a large number ( 300)

We are on XI 7.0 (SAPKB70015)
We have an issue picking up a large number of files from a particular server. We are trying to pickup the files based on a wildcard e.g. test
- we can retreive up to 200 files from the same server (using the same config) no problem
- we can pull lots of files (>3000) files from other servers (using the same config) no problem
- we can write an mget command (mget test) to reteive the files no problem
So the only issue is retrieving a large number of files from a parfticular server. We see no errors in the RWB.
To get this sorted out we need to find the exact commmands that XI executes to attempt to retrieve the files. Can anyone point me in the right direction on how to find this.
Thanks
Richard

It turned out that this was caused by a limitation on the ftp server.
The file adapter uses the dir command to get a listing of the files matching a specific mask. The dir command does not return any files if there are a large number (the ls command works fine but the file adapter uses dir instead of ls).
sap told me that 'According to this FTP server is no compliant with RFC 959 and that is
why DIR command returns an error.'
We were able to get this resolved by applying a patch on the ftp server.
Thanks
Richard

Limitations of file adapter -urgent

Similar Messages

Maybe you are looking for