File Adapter Append issue

Hi Iam trying to write a write a file in append mode using a file adapter(on a file which already exits)...but it says...file already exists...What might be the issue...?
Thanks in advance!
Larry

Hi Guys,
I shall explain the issue Iam having...Iam using the File Content Parameters..and the output is a plaint text file(Flat File).We are using Dynamic file configuration to populate the file name as per our requirements.When I dont use the dynamic config...(giving the name in the communication channel) the file is created @ the first time and its getting appended the next time..But when I use the Dynamic Configuration the file is not getting appended and it leaves an error saying the file is already there and cannot be overwritten...
Please advise!
Thanks in advance!

Similar Messages

  • File adapter - APPEND not working

    Hi Everyone,
    I want to append a text file on the target side. I am using FCC on the receiver side and the file construction mode is "APPEND" and file type is "TEXT". When i test my scenario, the file gets created for the first time and for the next time onwards, I get an error : "Target file already exists and must not be overwritten".
    Kindly help me to solve this issue.
    Thanks,
    Laawanya

    Check the below thread for the same:
    Have you checked overwrite box?
    It should be checked as well, and also check for necessary authorizations for this.
    Appending data in receiver file adapter
    Divyesh Vasani

  • File Adapter Archiving Issue

    Hi,
    THe file adapter archives the file, it doesn't save the entire contents of the file in the archive folder, but saves the first recordset (row) only in XML format. Did any body face similar issue, and what's the resolution to archive the contents of the file, the way it was sent.
    Thanks
    Pandari

    Hi Anil,
    Refer Archiving concepts in below links.
    http://help.sap.com/saphelp_nw73/helpdata/en/44/682bcd7f2a6d12e10000000a1553f6/content.htm?frameset=/en/44/6830e67f2a6d12e10000000a1553f6/frameset.htm
    http://scn.sap.com/docs/DOC-35572
    Warm Regards,
    DNK Siddhardha.

  • Receiver File adapter Append Mode

    Hi
    I have scenario where i am sending multiple idocs to file ...when i putting the file construction mode to append i can put multiple idoc in to file but i wanna do it on daily basis Means i wanna send the newly crated or changed Idoc on a daily basis to a single file ..
    How can i achieve that
    SV

    Hi
    You can achieve this using dynamic file names.
    Every day different files
    FileName-<DD>-<MMM>
    chk these
    /people/michal.krawczyk2/blog/2005/11/10/xi-the-same-filename-from-a-sender-to-a-receiver-file-adapter--sp14
    /people/sameer.shadab/blog/2005/09/23/an-interesting-usage-of-variable-substitution-in-xi
    /people/sravya.talanki2/blog/2005/08/11/solution-to-the-problem-encountered-using-variable-substitution-with-xi-sp12
    rgds
    Arun

  • File Adapter: FTP issue

    Hello,
    There is a problem with the file adapter of the XI30 SP14:
    It is set to get a file from a server X using a FTP protocol.
    INT_001_V01_COM_CTDCLNT600_FILE_SENDER
    Sender Adapter v2300 for Party '', Service 'CTDCLNT600':
    Configured at 2006-01-16 15:13:52 EST
    History:
    - 2006-01-16 15:23:54 EST: Polling interval started. Length: 60.000 s
    - 2006-01-16 15:23:54 EST: Processing finished successfully
    - 2006-01-16 15:23:52 EST: Processing started
    - 2006-01-16 15:22:54 EST: Polling interval started. Length: 60.000 s
    - 2006-01-16 15:22:54 EST: Processing finished successfully
    It seems everything is working fine, but the in the SXMB_MONI transaction, no message appears.
    I have accessed the FTP manually and I have downloaded the file, so the connectivity issue is descarted.
    Any suggestion.
    Jesus Barba Lobaton

    Hello all,
    The current configuration of the Sender file adapter is:
    Transfer protocol: FTP
    Message protocol: File Content Conversion
    Adapter Engine: Integration Server
    Source Directory: /out
    File: D_P.DAT
    In FTP: the file D_P.DAT is placed under /out directory
    Server: Server Internal IP
    Port: 21
    Connection security: None
    User: userX
    Pass: FTPuserX
    Quality of Service: Exactly once
    Poll Intervals: 60
    Processing mode: Delete
    File Type: Binary
    How can I verify a log of the processing process? as the SXMB_MONI transaction does not show anything.
    The most frustrating of all, is no error message appears. I have verified the XI, APPS and default trace logs with log viewer but there is nothing.
    I have also checked this thread but none of the solution provide solved the issue
    Pbm in File adapter..Post Sp14
    OS: Windows 2003
    Any idea?
    Jesus

  • Socket connection time Out - Sender File adapter (Intermittent Issue )

    Dear FrIends,
    In our sender file adapter i am getting the following issue:
    I have already places timout : 120 secs.
    This isssue is occuring intermittently.
    Error occurred while connecting to the FTP server "100.142.131.30:21": java.net.ConnectException: Socket connection timed out: 100.142.131.30:21

    Hi Renu,
    You need to increase the timeout Seconds and check.
    Run the report RSFTP002.
    and check whether the connection to FTP works. Provide the below parameters:
    user = <your ftp user>
    pwd = <your ftp pwd>
    host= <your ftp host/ip>
    command1 = <ls>
    RFC Dest = SAPFTP
    Compress = N
    If the issue still exists, then check  with your BASIS Team.
    http://www.sap2048.com/socket-and-connection-issues-in-java-web-services-1351.htm
    Thanks,

  • File adapter Deployment issue

    Hi,
    I have a process that use a file adapter which polles a certain directory.
    I am developing on windows XP and I am deploying to a Linux
    I can't leave the path of this directory as it is since it will not be recognized in the linux server
    How do I solve this issue?
    Amit

    You can specify the Logical Name of the directory from which you want to read the file from. In the BPEL partner link of the bpel.xml file, you then provide the physical parameter value for the Logical Name. This resolves the mapping between the logical directory name and actual physical directory name.
    For example you can specify Logical Name as InputFileDir and in the bpel.xml specify the physical value against the partner link for that file adapter, as following :
    <property name="InputFileDir">C:/ora_home/integration/bpm/samples/tutorials/
    121.FileAdapter/ComplexStructure/InputDir/</property>
    So while development, you can specify the physical directory as in your Windows system, and at deployment you can specify the directory as in your linux system.
    Rahul

  • 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 Format Issue:.csv target

    Hello
    When i am trying to write information from DB to a file as a CSV format it is always writing into xml format, though it is named with .csv extension.
    When you want to write the File as html target i need to do a html encoding but how to do it in another format like .csv?
    Appreciate your help on this

    you can refer this..
    http://docs.oracle.com/cd/B31017_01/integrate.1013/b28994/nfb.htm#CCGEGFDB
    You need to create "JCA File Adapter with NXSD format definition" as mentioned in above link.

  • File adapter - Archive issue with adapter module

    Hi All,
    I have 2 issues here. We are currently using PI 7.11 EHp1 SP02.
    1. Arhival with "add time stamp" wont work. It just gives us an error message saying simpledate format exception.
    I have gone through the OSS note 1265534 and thought this will resolve the issue. But our BASIS team believes this note is only applicable for PI 7.1 SP01. Can you one using PI 7.11 SP02 comment on this?
    Note: Archive option with out add time stamp works fine.
    2. When I use adapter module in my sender file configuration, the archive option itself does not work. Read the official SAP help which says "To archive source files where a permanent error occurred during processing, set the indicator.
    A permanent error occurs either during the conversion of the file content, or in a module in the module processor."
    So the question here is, how do we make the error permanent? The only way to throw error from adapter module is using the ModuleException. It has 4  different constructors. I have used both
    ModuleException me = new ModuleException ("My error Msg"); and
    Module Exception me1 = new ModuleException ("Error String", new Throwable("My error Msg");
    In both the cases, the archival wont happen.
    Any ideas welcome.
    Thanks
    Jai

    Hi,
    I am using NFS protocol here not FTP. Sorry I dint mention that earlier.
    Thanks
    Jai
    Edited by: Jaishankar on Apr 1, 2010 9:55 AM
    Edited by: Jaishankar on Apr 6, 2010 11:10 AM

  • File Adapter-Append

    Dear all,
    When I select APPEND in the communication channel in file processing parameters with the below source files
    <?xml version="1.0" encoding="UTF-8"?>
    <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:ns0="http://ehro.eds.com">
    <EMP_DETAILS xmlns:"http://ehro.eds.com/PSPC/JDBCrec">
       <EMP>
          <FirstName>sree</FirstName>
          <LastName>Phani</LastName>
          <ENO>1</ENO>
          <Sal>121231243</Sal>
          <desg>Manager</desg>
       </EMP>
    </EMP_DETAILS>
    <?xml version="1.0" encoding="UTF-8"?>
    <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:ns0="http://ehro.eds.com">
    <EMP_DETAILS xmlns:"http://ehro.eds.com/PSPC/JDBCrec">
       <EMP>
          <FirstName>Ravi</FirstName>
          <LastName>Phani</LastName>
          <ENO>2</ENO>
          <Sal>121231243</Sal>
          <desg>Manager</desg>
       </EMP>
    </EMP_DETAILS>
    The output appended file is getting apended but <?xml version="1.0" encoding="utf-8"?> is also getting appended to each message which is appended in the file.
    Kindly let me know how to maintain a single <?xml version="1.0" encoding="utf-8"?> so that this file contents may be appended to my dtabase.
    Thanks,
    Srini

    Hi,
    To have the data to be appended we should have File content conversion at the receiver.Otherwise there will be a conflict with the nodes.
    Thanks,
    Zabiulla

  • Receiver File Adapter - Encoding issue.

    Hi Everybody,
    The file format (encoding) is different to the format generally we used to get.
    Currently we are get the flat files in DOS format.The current file when we are downloading it we are getting it in the UNIX or other format.
    For eg: 20 has been changed to 0D in the file.
    Can somebody help me on the same.
    Thanks,
    Zabiulla

    Hi,
    Check on this for file adapters
    Text
    Under File Encoding, specify a code page.
    The default setting is to use the system code page that is specific to the configuration of the installed operating system. The file content is converted to the UTF-8 code page before it is sent.
    Permitted values for the code page are the existing Charsets of the Java runtime. According to the SUN specification for the Java runtime, at least the following standard character sets must be supported:
    &#9632;       US-ASCII
    Seven-bit ASCII, also known as ISO646-US, or Basic Latin block of the Unicode character set
    &#9632;       ISO-8859-1
    ISO character set for Western European languages (Latin Alphabet No. 1), also known as ISO-LATIN-1
    &#9632;       UTF-8
    8-bit Unicode character format
    &#9632;       UTF-16BE
    16-bit Unicode character format, big-endian byte order
    &#9632;       UTF-16LE
    16-bit Unicode character format, little-endian byte order
    &#9632;       UTF-16
    16-bit Unicode character format, byte order
    Regards
    Vijaya

  • TargetFilename in the Outbound File Adapter

    Hi all,
    I have created an interface that sends projects form SAP PS (by tRFC) to a file directory (using an outbound file adapter). Each project is created as a individual file. All this works well, but the filenames created for the files are not very intuitive for the users looking at the files at the receiver point since there are quite a lot of similar files only distinguished from each other by a timestamp (usualy only separated by milliseconds).
    Is there a way to make the file adapter append data from one XML tag in the file name? I.e:
    file.TargetFilename='<project></project>'.txt
    file.writeMode=addTimeStamp
    giving i.e a file '1234567_timestamp.txt'
    This way I can include i.e. the project number + timestamp as filename making it user friendly for the people using the files.
    Any suggestions will be appreciated.
    Best Regards
    Odd Hilt

    HI
    Read the file without using key field. Just define the FCC parameters Header and Items PI will pick the file.
    DT_Source
       Record
         Header 0..1
           PO_Number String 0..1
         Items  0..unbounded
           Items String 0..1
    Do the FCC
    Header.fieldnames PO_Number
    other config for Header
    Items.fieldnames Items
    other config for items
    Thanks
    Gaurav
    Edited by: Gaurav Bhargava on Nov 12, 2008 10:27 AM
    Edited by: Gaurav Bhargava on Nov 12, 2008 10:27 AM

  • Base64Binary OSB and File Adapter Issue

    Hi all,
    I am converting an xml to flat file after that i want to write the flatfile to a file using File Adapter in OSB.
    So using java callout we converted the binary content to base64 string and we are able to write the data using file adapter .
    But the file contains as extra line in between each line which my legacy system wont accept.
    I printed the base64 string in the output file and when i decode that file using the website as safe decode as text i am able to get the correct file.
    So where is the problem ? File Adapter ? Why i am getting extrace line in between each line . How to write safely using file adapter.
    If i use file transport of OSB i am able to write without any issues but i want to write dynamic location so i am looking for file transport of OSB.
    Thanks
    Phani

    Hi Anju,
    Thanks for the response . If i decode the base64 binary data using this website if i use Notepad++ i cant see an extra line in the notepad++ it showing as below
    Its a fixed length file 1 to 513 then next line so for the file transport it showing as below
    ISA ............................
    1 to 513 CRLF
    For file adapter it is showing as below in the same notepad++ editor
    ISA..........................
    1 to 513 CR
    CRLF
    an extra CR so an extra line .
    I used MFL and converted the xml to non-xml ( flat file fixed length file) for file transport i am i created another proxy message type Text .It is working fine
    Added to the above problem i have another few questions on the file transport
    How can append to an exiting file using File transport ?
    How to change the File directory dynamically ?

  • File adapter issue in Linux enviornment

    hi'
    I am deploying BPEL in Linux enviornment, and with the file adapter read operation I am reading a test.xml file this file is internally refering to emp.xsd (files are below), now the issue is the file adapter is reading XML file even if it is invalid, this was not the case in windows XP enviornment, please advice why it is behaving like this.
    Also the path of my XSD is "/home/wsfbpel/public_html/XSD" and the file has all read write permission (chmod 777 filename)
    XSD
    *<?xml version="1.0" encoding="windows-1252" ?>*
    *<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"*
    xmlns="http://www.example.org"
    targetNamespace="http://www.example.org"
    elementFormDefault="qualified">
    *<xsd:element name="readfile">*
    *<xsd:complexType>*
    *<xsd:sequence>*
    *<xsd:element name="name" type="xsd:string"/>*
    *<xsd:element name="empid" type="xsd:string"/>*
    *</xsd:sequence>*
    *</xsd:complexType>*
    *</xsd:element>*
    *</xsd:schema>*
    XML (this is clearly invalid with respect to XSD it is refering to)
    *<?xml version="1.0" encoding="utf-8"?>*
    *<!-- Created with Liquid XML Studio Developer Edition (Trial) 8.1.2.2399 (http://www.liquid-technologies.com) -->*
    *<tns:readfile xmlns:tns="http://www.example.org"*
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.example.org /home/wsfbpel/public_html/XSD/emp.xsd">
    *     <tns:name>yatanveersingh</tns:name>     *
    *     <tns:empidname>6499</tns:empidname>* +(incorrect element name)+
    *</tns:readfile>*
    thanks
    Yatan

    Hi,
    My problem got resolved.
    There was some access issue to see the txt files at the File Directory.
    Thanks.

Maybe you are looking for