File Adapter FCC Error

Hi team
i am getting the following errors in the File Adapter when i am using the FCC Parameters.
1)Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Mandatory parameter 'xml.keyfieldName': no value found
2)Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Mandatory parameter 'Detail.keyFieldValue': no value found
My FCC parameters are
Header.fieldNames,Header.fixedLengths,Detail.fieldNames,Detail.fixedLengths
i am receiving a file from the FTP server; the file structure has header and detail records.
Please help me out
tahnx a lot in advance

Hi,
Your header and details lines in the file will contain the first value which differentiates them.
That field becomes your Keyfiled.
Add the following to the configuration:
xml.keyfiledName - the 1st field name from the header and detail
header.keyFieldValue - vakue from the header line
detail.keyFieldValue - value from the detail line
Regards,
Pragati

Similar Messages

RECEIVER FILE ADAPTER FCC ERROR

Hi team
My scenario is a text file has to be picked up by PI, has to processe it and the receiver is Proxy and it has to get updated and sent back to FTP location.
i am using Sender File Adapter with FCC and Also receiver File Adapter with FCC.
Both the sender and receiver structures are same; i am using the same FCC parameters for both the sides.
in Receiver File Adapter i am getting the following errors
1) Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found:
Parameter '.fieldFixedLengths' or '.fieldSeparator' is missing
2)Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found:
Parameter '1.fieldFixedLengths' or '1.fieldSeparator' is missing
please help me out
thank you
Edited by: vemugantivn on Aug 16, 2010 12:19 PM

Hi,
> 1) Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found:
> Parameter '.fieldFixedLengths' or '.fieldSeparator' is missing
> 2)Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found:
> Parameter '1.fieldFixedLengths' or '1.fieldSeparator' is missing
It is saying that you are not using the fieldSeparator parqameter.
have you provided the field separator parameter? if not then give like below
order_row.fieldSeparator : , (give what ever the separater you are using)
or
order_row.fieldSeparator : 10,5,... (if you are using fixed length)
Regards
Ramesh

Sender File Adapter FCC to Hierarchial MT Coversion

Hi,
   I have MT with structure as follows
Header               1..1
    F1          string 1..1
    F2          string 1..1
    SUB              1 to unbounded
       S11       string 1..1
       S12       string 1..1
Can you anybody help me out how to convert the a CSV file to Convert the structure mentioned above using sender File Adapter FCC.
Regards,
Daniel.LA

Hi,
There is no suc h direct way to get the data from csv fiel with conversion.
Either you can use JAVA Mapping for it or use the adapter module to read csv files.
How to process CSV data with XI file adapter
/people/sap.user72/blog/2005/01/06/how-to-process-csv-data-with-xi-file-adapter
"JAVA MAPPING", an alternate way of reading a CSV file
/people/rahul.nawale2/blog/2006/07/18/java-mapping-an-alternate-way-of-reading-a-csv-file
There is one way that you could bypass IR (Integration Repository) for any type of files, see below link
/people/william.li/blog/2006/09/08/how-to-send-any-data-even-binary-through-xi-without-using-the-integration-repository
Making CSV File Lookup Possible In SAP XI !!!
/people/sundararamaprasad.subbaraman/blog/2005/12/09/making-csv-file-lookup-possible-in-sap-xi
This will help you
Thanks
Swarup

How do i extract Delimited falt file-Sender File adapter FCC Parameters

Hello,
I'm trying to extract data from a flat file. The file is built as tab delimited. I cant find the option of tab delimited in the XI Sender File adapter FCC Parameters. How do i extract tab delimited file?
Please Advice,
Rajesh

HI,
You can use Fieldseperator as '0X09'...
Look at this blog...........you can solve this problem...
NAB the TAB (File Adapter)
Thanks,
Madhu
Edited by: Madhu sudhan Reddy on Jul 28, 2008 9:02 AM

Error in Receiver File adapter - FCC

Got error message as "File Adapter Receiver Channel CC_OB_REQ: Not initialized - cannot proceed: null"
My requirement is to send IDOC to file which consists of 4 fields, My target message interface is
MT_REQ
FILE_STRUC
    FILE_OP
       AAA (Field1)
        BBB(Field2)
       CCC(Field3)
       DDD(Field4)
Output file should contain the above 4 fields with fixed lengths 20,1,1,2
So I declared FCC in File Adapter as
I tried many options
RecordSet Structure: MT_REQ,FILE_STRUC,FILE_OP
FILE_STRUC.fieldSeparator - 'nl'
FILE_OP.fixedFieldLengths - 20,1,1,2
FILE_OP.fieldSeparator - 'nl'
FILE_OP.endSeparator - 'nl'.
Please let me know where is the problem?
Thanks in advance,
Krishna

Hi Ramakrishana,
In FCC fixed length file format when your XML payload is goes to Adaptor engine, it should contain all fields in XML. Otherwise its throw error in FCC channel. Please check receiver payload at SXMB_MONI or message monitoring of Run time work bench. In that payload you will find that some of the fields is not generated in target payload.
Field in receiver payload is not generated means from sender payload corresponding field is not coming. As per my past experience this generally happens in IDOC sender.
solution:- In message mapping in every field from IDOC to file use mapWithDefault node function with null value. Due to this though if any field do not generates in IDOC, corresponding field will generate in File Payload and it will not throw error in FCC.
Regards,
Prashant

File Adapter gets error while deleting the file

Hi,
We are running on PI 7.0 SP6. I built a simple integration scenario where a file is picked up from a certain directory on the server (PI server itself) and get processed according to some mapping rules and again put to an other directory. I used the file adapter for picking and putting the file with 2 different communication channels.
My integration works fine. File is picked up processed and put into its new location.
But the file adapter cannot work in archiving or deletion mode. So the file (to be picked up by PI) remains in its original location.
I am getting the following error:
Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File##com.sap.aii.adapter.file.File2XI.deleteFile(FileHandle)#J2EE_GUEST#0####18a971f3338011dbcde800145e69a8d4#XI AF File2XI[:EBI:File_from_EBI_to_EXS]##0#0#Error#1#com.sap.aii.adapter.file.File2XI#Java###Deleting of file failed - cannot proceed#1#E:
SCENARIOS
EBITOEXS
RFID
GELEN
tagdata22082006035719.xml#
#1.5#00145E69A8D4005B0000004700000A6400041BC49A1D56D3#1156431120046#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0####18a971f3338011dbcde800145e69a8d4#XI AF File2XI[:EBI:File_from_EBI_to_EXS]##0#0#Error#1#com.sap.aii.adapter.file.File2XI#Plain###File 'E:
SCENARIOS
EBITOEXS
RFID
GELEN
tagdata22082006035719.xml' - deleting after processing failed - retry#
I tried everything but upgrading to a higher SP level and will do so unless anyone has an other suggestion.
Thanks a lot,
Murat Gölcü
[email protected]

Hi,
These are a few things you can do:
Check the permissions of the folder where the file is being Placed. (it will mostly have only read permission, this is what i could understand from your explanation)
If you are doing Content conversion, please can you just remove it and see if the XML file is getting generated.
Also, please check if it's picked up by any other application when you place it on the server.
Regards,
Abhy

File Adapter - Exception / Error handling

We are using File Adapter in BPEL process to read multiple records from the file. Additionally, we have also handled rejectedMessageHandlers & fatalErrorFailoverProcess exception to lunch custom BPEL process. The process is running fine and also successfully launches custom handler processes too.
Need help / direction in addressing following issues.
1. While reading from file, if a records errors out, the custom BPEL process is launched (as specified in rejectedMessageHandlers property). In such instance, the previously read valid records are processed but remaining records are marked as errored out. Our requirement is to make entire record set as invalid and would like to perform rollback of entire process.
2. Whenever an error occurs during reading the records using File adapter, the associated data file is being deleted from the input directory and also NOT available in archive directory also.
Are we missing any set up ? We are on 10.1.3.1
thanks
-Yj
Sample Log file:
<2009-04-20 11:46:14,080> <INFO> <default.collaxa.cube.activation> <AdapterFramework::Inbound> JCAActivationAgent::init - Initializing the JCA activation agent, processId='bpel://localhost/default/TestFileRead~1.0/
<2009-04-20 11:46:14,080> <INFO> <default.collaxa.cube.activation> <AdapterFramework::Inbound> JCAActivationAgent::initiateInboundJcaEndpoint - Creating and initializing inbound JCA endpoint for:
process='bpel://localhost/default/TestFileRead~1.0/'
domain='default'
WSDL location='Read.wsdl'
portType='Read_ptt'
operation='Read'
activation properties={portType=Read_ptt, rejectedMessageHandlers=bpel://default|AdapterError2|initiate|payload}
<2009-04-20 11:46:14,096> <INFO> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Adapter Framework instance: OraBPEL - endpointActivation for portType=Read_ptt, operation=Read
<2009-04-20 11:46:14,143> <INFO> <default.collaxa.cube.activation> <File Adapter::Inbound> Endpoint Activation called in File Adapter for endpoint: c:\temp\yj
<2009-04-20 11:46:14,143> <INFO> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Adapter Framework instance: OraBPEL - successfully completed endpointActivation for portType=Read_ptt, operation=Read
<2009-04-20 11:46:30,580> <WARN> <default.collaxa.cube.activation> <File Adapter::Inbound> PollWork::run exiting, Worker thread will die
<2009-04-20 11:47:14,158> <INFO> <default.collaxa.cube.activation> <File Adapter::Inbound> Translated inbound batch index 1 of file {testdata6.txt} with corrupted message count = 1
<2009-04-20 11:47:14,158> <INFO> <default.collaxa.cube.activation> <File Adapter::Inbound> Sending message to Adapter Framework for rejection to user-configured rejection handlers : {
fileName=C:\temp\yj\testdata6.txt, startLine=3, startColumn=1, endLine=-1, endCol=-1, Exception=ORABPEL-11168
Error while reading native data.
[Line=3, Col=5] Expected "|" for the data starting at the specified position, while trying to read the data for "element with name C2", using "style" as "terminated" and "terminatedBy" as "|", but not found.
Ensure that "|", exists for the data starting at the specified position.
<2009-04-20 11:47:14,158> <WARN> <default.collaxa.cube.activation> <AdapterFramework::Inbound> [Read_ptt::Read(Root-Element)]onReject: Sending invalid inbound message to Exception Handler: bpel://default|AdapterError2|initiate|payload
<2009-04-20 11:47:14,315> <INFO> <default.collaxa.cube.activation> <File Adapter::Inbound> Setting last error record to : -1
<2009-04-20 11:47:14,658> <ERROR> <default.collaxa.cube.activation> <AdapterFramework::Inbound> onBatchFailure: Batch 'bpel://localhost/default/TestFileRead~1.0//testdata6.txt_1240205493408' (C:\temp\yj\testdata6.txt) has failed due to: ORABPEL-11168
Error while reading native data.
[Line=3, Col=5] Expected "|" for the data starting at the specified position, while trying to read the data for "element with name C2", using "style" as "terminated" and "terminatedBy" as "|", but not found.
Ensure that "|", exists for the data starting at the specified position.

Any light / idea on the following issue ?
1. While reading from file, if a records errors out, the custom BPEL process is launched (as specified in rejectedMessageHandlers property). In such instance, the previously read valid records are processed but remaining records are marked as errored out. Our requirement is to make entire record set as invalid and would like to perform rollback of entire process. Even, if we do not configure rejectedMessageHandlers, the behavior is that valid rows are processed with the rest of BPEL process and for Invalid rows, the records are rejected. Our requirement, is that, even if there is one invalid record, the entire set of record should NOT move ahead with the BPEL process
2. Whenever an error occurs during reading the records using File adapter, the associated data file is being deleted from the input directory and also NOT available in archive directory also. Note, in case of all valid record the file is available in archive directory

Sender file adapter conversion Error!!

Hello every one....
I am stuck with a problem...in my scenario,, there are possiblities that file may contain more than required paramters... in such case,,, paramters defined in conversion should go ahead and others should be ignored...
for this very purpose i added the paramter:
row.fieldSeparator                 ,
row.fieldNames                     orderno,authcode,status
row.endSeparator                  'nl'
row.additionalLastFields      ignore
the scenario works fine if the file contains thrree comma separated values but it raises an error if no of paramters increase as :
Conversion of file content to XML failed at position 0: java.lang.Exception: ERROR converting
document line no. 1 according to structure 'row':java.lang.Exception: ERROR in configuration: more
elements in file csv structure than field names specified!
we are using PI 7.... does it require some more configuration in additoin to paramter row.additionalLastFields
any help in this regard would be highly appreciated...
thanx

this parameter is already set, and this is the exact behavior i want from adapter engine... but the problem
here is different... the exception is raised at communication channel's conversion routine level,,, the retry
interval is not the one defined in visual admin but infact the interval (polling) time defined in communication
channel.... the system does'nt stop after 3 attempts,, but infact keep on trying to read it....
one peice of information i have found is in sap note:821267 , which states:
*Q35:*
Q: I have configured a File Sender channel with File Content
Conversion or a custom-developed module, which may throw an
exception. When the File Adapter encounters an invalid file, which
triggers a conversion error or an exception in a module, the
adapter will enter a retry interval and upon each following
processing attempt try to process the faulty file. This basically
prevents the File Adapter from picking up files that are located
after the fauilty file according to the configured sort order. How
can I change this behavior?
o A: This is by design. When the File Adapter encounters an invalid
file, manually remove this file from the configured source
directory. You can configure an alerting rule to get notified each
time this occurs.
We are currently evaluating possible solutions that could be used
to skip this manual interaction.
now can there be a way around to make communication channel read the file only 3 times (value defined in adapter engine profile in visual admin)
I have thaught of writing of module.... but the error is raised even before calling module !!
any further clue ???

Sender File adapter FCC

Hi
I have an excel file which I save as a csv extension. If I use FCC in Sender File Adapter, I need to add a module in my communication channel. Can anyone provide me with that?
Is this module generally deployed on XI server beforehand or do I have to write a java code and deploy it myself?
I have already had a look at this blog
/people/sap.user72/blog/2005/07/04/read-excel-instead-of-xml-through-fileadapter
Vaibhav

You will have to create a module in this case.there is no standard module available for this fuctionality as of now.
Ref: https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/02706f11-0d01-0010-e5ae-ac25e74c4c81 to help create a module.

File Adapter: Initialization error: Conversion initialization failed

Hi all,
I'm trying to establish a file adapter (FTP, File Content Conversion).
In the adapter monitor I' ve got the following error:
Sender Adapter v1325 for Party '', Service 'BS_ACN_PCS_A':
Configured at 14:49:34 2005-08-29
Initialization error: Conversion initialization failed with java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found:
Format error in 'xml.recordset' argument: incomplete structure (name,number) pair
My content conversion parameters are:
BP_BusinessPartnerMasterData_IncomingData.fieldFixedLengths:
20,50,50,1,10,50,10,50,5,20,20,15,15
BP_BusinessPartnerMasterData_IncomingData.fieldNames: Number,Name2,Name1,Gender,Birthdate,City,Postcode,Street,
HouseNo,PhoneNumber,Fax,BankId,BankAccount
BP_BusinessPartnerMasterData_IncomingData.fieldContentFormating:
trim
BP_BusinessPartnerMasterData_IncomingData.keyFieldInStructure:
ignore
What could be the error or where I have to look for it?
Thanks,
Fabian

Yes,
Recordset name: BP_BusinessPartnerMasterData_IncomingData
Recordset structure: BP_BusinessPartnerMasterData_IncomingData
The corresponding Message Type:
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://pcs.acn.com/basicdata" targetNamespace="http://pcs.acn.com/basicdata">
     <xsd:element name="BP_MasterDataIncomingFil" type="BP_BusinessPartnerMasterData_IncomingData" />
     <xsd:complexType name="BP_BusinessPartnerMasterData_IncomingData">
          <xsd:annotation>
               <xsd:appinfo source="http://sap.com/xi/TextID">
               f323a4b018a911da9fd9000bcd69ce64
               </xsd:appinfo>
          </xsd:annotation>
          <xsd:sequence>
               <xsd:element name="Number">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8500fe111da89f2d1210a87220d
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         Id from Sender for BP
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="20" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="Name2">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8510fe111dacfd7d1210a87220d
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         Last name or Company name
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="Name1">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8520fe111da94bad1210a87220d
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         First name or Company name 2
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="Gender">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8530fe111da99add1210a87220d
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         m or f or blank
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="1" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="Birthdate">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8540fe111dab156d1210a87220d
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="10" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="City">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8550fe111daa58cd1210a87220d
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="Postcode">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8560fe111dac0c2d1210a87220d
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="10" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="Street">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8570fe111dabbd3d1210a87220d
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="HouseNo">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8580fe111dab63fd1210a87220d
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="5" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="PhoneNumber">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8590fe111dac782d1210a87220d
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="20" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="Fax">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e85a0fe111daa9ebd1210a87220d
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="20" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="BankId">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e85b0fe111dace1ed1210a87220d
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="15" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="BankAccount">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e85c0fe111da8801d1210a87220d
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="15" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
          </xsd:sequence>
     </xsd:complexType>
</xsd:schema>

Sender File Adapter FCC Question

Hello folks!!
I am trying to configure a FCC for Sender file adapter and wanted to consider a Line feed Carriage return line which will look as below to be a empty tag in XML. After Line 4 there will be a blank line which identifies the start of next record. I tried using Field.MissingLastFields , Field.endSeparator etc., Perhaps I am not using the correct value. Any help appreciated.
Line1
Line2
Line3
Line4
Line1
The expected XML is as below:
<Record>Line1</Record>
<Record>Line2</Record>
<Record>Line3</Record>
<Record>Line4</Record>
<Record></Record>
<Record>Line1</Record>

Hi Greg
Thanks for your feedback. I tried and it didn't work. below is the FCC i have in sender adapter
RecordSetName      =   RecordSet
RecordSetStructure =    Dummy,*
Dummy.fieldNames   = Record
Dummy.endSeparator = 'nl'
Dummy.missingLastfields = add
Dummy.ignoreRecordsetName = true
Dummy.fieldSeparator = 'nl'   and also I tried with Dummy.fieldFixedLengths = 255 .
Still I don't get the empty tag for the blank line in the file, so my output is still same . Please note the blank line doesn't have a space so if I place the cursor and move to next in blank line it will go to next line ( Carriage return and line feed).
Please suggest .

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 Adapter - FTP Error

Hi,
I have a Sender File Adapter using FTP which polls a server every 60 seconds looking for a file. Intermittently the adapter will connect and pick up the waiting file. However, more often than not it gives an error:
An error occurred while connecting to the FTP server 'xx.xx.xx.xxx:21'. The FTP server returned the following error message: 'com.sap.aii.adapter.file.ftp.FTPEx: 426 Unexpected reply codeConnection closed; transfer aborted.'. For details, contact your FTP server vendor.
The connect mode is Permanently and the transfer mode is Binary.
Any ideas ?
PaulC.

Monica,
Can you explain the difference between ACTIVE and PASSIVE and why changing to ACTIVE may get rid of this issue ? Have looked at the help.sap.com and it doesn't give too much detail on these settings.
Thanks
PaulC.

SENDER FILE ADAPTER (FTP) ERROR

Hi,
Iam getting the following error in sender file adapter:
Could not process due to error: com.sap.aii.adapter.file.ftp.FTPEx: 550 *** ERROR *** NO BATCHES FOR TRANSMISSION
Could anyone help me in this.
Thanks &Regards,
Kiran

Hi Kiran,
This problem is not related to PI but rather related to FTP server settings.
Try changing the name of the file in your adapter settings to a string without any dots and ".
Try this and let me know if its successful.
Regards,
Divya

Sender File Adapter - No error, but not generating any message

I am working on a file to RFC scenario. The sender file adapter is using content conversion to read a comma delimited file. The file is being picked up and archived correctly, and the adapter monitor does not show any errors. However, the process disappears at this point. I don't see any messages in SXMB_MONI, and there is no sign that the process is reaching the RFC adapter. Has anyone ever had this happen before?
I have four line types for Buildings, Additions, Floors, and Rooms.
I list all four in the recordset structure, and I identify a key for each with the keyFieldValue parameter. I list a fieldSeparator of ',' and an endSeparator of 'nl' for each row. And i have a list of the fieldnames in the fieldnames parameter.
The only thing i'm not sure about is the keyFieldinStructure parameter. I have specified ignore there, because I don't want that field in my XML. Do I still need that field in my sender datatype, even if I'm ignoring it, or can I leave it out?
Thanks for any help. Please don't just list blogs unless they have something you think is helpful with my specific problem. I have already read all of the blogs that deal generally with the sender file adapter and file content conversion, and I need more specific help at this point.

I made one error before, it IS showing up in the Recovered Adapter Audit Log (it took that log about 10 minutes to open that particular tab so I didn't notice them there).
Here is what it says there:
2006-06-12 11:22:59 Success Channel CC_S_File_FIPM_Buildings: Entire file content converted to XML format
2006-06-12 11:22:59 Warning Channel CC_S_File_FIPM_Buildings: Empty document found. Proceed without sending message
2006-06-12 11:22:59 Success File "/interfaces/one line building.txt" archived after processing
Here are my parameters in the file content conversion:
Buildings.fieldNames     RecordType,PLTXT,STORT,STREET,POST_CODE1,CITY1,REGION,PARNR,X_COORD,Y_COORD,ASSIGN_SQ_FT,BLDG_NUM,CAMPUS,GR_SQ_FT,NET_SQ_FT
Buildings.keyFieldValue     'B'
Buildings.fieldSeparator     ','
Buildings.endSeparator     'nl'
Buildings.keyFieldInStructure     ignore
Additions.fieldNames     RecordType,ASSIGN_SQ_FT,BLDG_ABBR,CAMPUS,ADDITION,BLDG_USE,BLDG__NUMBER
Additions.keyFieldValue     'A'
Additions.fieldSeparator     ','
Additions.endSeparator     'nl'
Additions.keyFieldInStructure     ignore
Floors.fieldNames     RecordType,BLDG_ABBR,CAMPUS,ADDITION,FLOOR,ASSIGNABLE_SQUARE_FOOT,BLDG_NUMBER
Floors.keyFieldValue     'F'
Floors.fieldSeparator     ','
Floors.endSeparator     'nl'
Floors.keyFieldInStrucutre     ignore
Rooms.fieldNames     RecordType,SHTXT,MSGRP,ADDITION,ASSIGNED_DEPT,BLDG_ABBV,FLOOR_CAMPUS,AREA,RCD_CODE,DEPT_CODE,BUILDING_NUMBER,ROOM_COMMON_KEY
Rooms.keyFieldValue     'R'
Rooms.fieldSeparator     ','
Rooms.endSeparator     'nl'
Rooms.keyFieldInStructure     ignore
And here is my data type:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_FIPM_BuildingUpdate xmlns:ns0="urn:XXXXXX:FIPM:Buildings:SYS">
   <Buildings>
      <PLTXT/>
      <STORT/>
      <STREET/>
      <POST_CODE1/>
      <CITY1/>
      <REGION/>
      <PARNR/>
      <X_COORD/>
      <Y_COORD/>
      <ASSIGN_SQ_FT/>
      <BLDG_NUM/>
      <CAMPUS/>
      <GR_SQ_FT/>
      <NET_SQ_FT/>
   </Buildings>
   <Additions>
      <ASSIGN_SQ_FT/>
      <BLDG_ABBR/>
      <CAMPUS/>
      <ADDITION/>
      <BLDG_USE/>
      <BLDG_NUMBER/>
   </Additions>
   <Floors>
      <BLDG_ABBR/>
      <CAMPUS/>
      <ADDITION/>
      <FLOOR/>
      <ASSIGNABLE_SQUARE_FOOT/>
      <BLDG_NUMBER/>
   </Floors>
   <Rooms>
      <SHTXT/>
      <MSGRP/>
      <ADDITION/>
      <ASSIGNED_DEPT/>
      <BLDG_ABBV/>
      <FLOOR/>
      <CAMPUS/>
      <AREA/>
      <RCD_CODE/>
      <DEPT_CODE/>
      <BUILDING_NUMBER/>
      <ROOM_COMMON_KEY/>
   </Rooms>
</ns0:MT_FIPM_BuildingUpdate>
I'm going to recheck everything again, but maybe you guys will see something? I don't.
Vanda

File Adapter FCC Error

Similar Messages

Maybe you are looking for