Regarding content conversion parameter

Hi
I am doing content conversion in sender file adapter.I want to remove " " in target file.
I used row.enclosureSignEsc ""
but its not working.
can any one tell me how to use enclosure sign parameter.
Source Flat file looks like:
"A00",417,"SC9",20050101,100617,3229
"B01","EA",20041231,39.4,"ACT","F","D"
"B01","EA",20041231,38.7,"ACT","F","W"
"B01","EA",20050101,39.4,"TOD","F","D"
"B01","EM",20041231,39.3,"ACT","F","D"
"B01","EM",20041231,38.7,"ACT","F","W"
"Z99",50
In the target i want like this:
A00,417,SC9,20050101,100617,3229
B01,EA,20041231,39.4,ACT,F,D
B01,EA,20041231,38.7,ACT,F,W
B01,EA,20050101,39.4,TOD,F,D
B01,EM,20041231,39.3,ACT,F,D
B01,EM,20041231,38.7,ACT,F,W
Z99,50
Thanks&Regards
venkat.

>
venky adireddy wrote:
> Hi
> I am doing content conversion in sender file adapter.I want to remove " " in target file.
> I used row.enclosureSignEsc ""
> but its not working.
> can any one tell me how to use enclosure sign parameter.
>
> Source Flat file looks like:
>
> "A00",417,"SC9",20050101,100617,3229
> "B01","EA",20041231,39.4,"ACT","F","D"
> "B01","EA",20041231,38.7,"ACT","F","W"
> "B01","EA",20050101,39.4,"TOD","F","D"
> "B01","EM",20041231,39.3,"ACT","F","D"
> "B01","EM",20041231,38.7,"ACT","F","W"
> "Z99",50
>
> In the target i want like this:
>
> A00,417,SC9,20050101,100617,3229
> B01,EA,20041231,39.4,ACT,F,D
> B01,EA,20041231,38.7,ACT,F,W
> B01,EA,20050101,39.4,TOD,F,D
> B01,EM,20041231,39.3,ACT,F,D
> B01,EM,20041231,38.7,ACT,F,W
> Z99,50
>
>
>
> Thanks&Regards
> venkat.
THERE
there is no parameter to achieve what you want in FCC.
as mentioned earlier you will have to use a function to remove the "
you dont have to create a UDF you can use the standard text function available in XI - replaceString

Similar Messages

How to escape newline character(nl) in file content conversion parameter?

Hi Experts,
How to escape newline character(nl) in file content conversion parameter?
For example:
field1field2field3
field4field5field6
Means Item is splitted in two lines.
I want to SKIP new line character
and to collect all SIX fields.
What will be the file content conversion parameter?
Thanks in Advance..........

Hi,
as far as i know there is nothing in the standard. But the question is why dont you combine at mapping the fields into only structure?
Regards,
Udo

Content Conversion Parameter- Help

Dear Friends,
I have a quick question regarding content conversion paramter.
My structure is as follows
<MT_Root>
<Statement_response>
<row>
<Value1>ABC</Value1>
<Value2>CDE</Value2>
<Value3/>
</row>
<row>
<Value1>DATA</Value1>
<Value2>TEST</Value2>
<Value3/>
</row>
<row>
<Value1>CHECK</Value1>
<Value2>OUT</Value2>
<Value3/>
</row>
</Statement_response>
</MT_Root>
In the receiver adapter i'm using
Record Structure :MT_Root,Statement_response,row
row.fieldSeparator ,
Statement_response.endSeparator 'nl'
Statement_response.fieldSeparator 'nl'
Everything is fine , if you see the o/p file there are lot of spaces appened between each fields. I don't want the spaces.
If you guys help me out, I'll really appreciate it!!
Thanks,
raj.

hi,
possibly you could use small lengths while passing the data to file in FCC parameters.
i.e fixedfieldlengths.
also use the TooShortHandlingfield parameter with value "cut". it will ignore the large length of the fields and cut it down as per the values.
Plesae refer below link for usage of these parameters,
http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/frameset.htm
thnaks
Swarup

What are the right content conversion parameter in this receiver ?

Hi experts,
Can someone help me with setting right Content conversion parameter in the Receiver of File adpater(FCC).The output file must be fixed length text file.
Here is the receiver structure:
<Recordset>
    <Header>
       <f1>01</f1>
       <f2> </f2>
       <f3> </f3>
    </Header>
     <Body>
        <SubBody1>
              <field1 />
              <field2 />
              <field3 />
              <field4 />
              <field5 />
        </SubBody1>
         <SubBody2>
              <field6 />
              <field7 />
              <field8 />
              <field9 />
              <field10/>
        </SubBody2>
     </Body>
    <Trailer>
        <f1>03</f1>
        <f2> </f2>
        <f3> </f3>
   </Trailer>
</Recordset>
Also Body can occure multiple times in the file but still will have this structure...Header and Trailer can occure only once in file.
What are the right content conversion perameters in this case?
Appreciate your help asap!T
Thanks
Jon

<Recordset>
    <Header>
       <f1>01</f1>
       <f2> </f2>
       <f3> </f3>
    </Header>
     <Body>
         <SubBody>
              <field1 />
              <field2 />
          </SubBody>
          <SubBody>
              <field1 />
              <field2 />
          </SubBody>
          <SubBody>
              <field1 />
              <field2 />
          </SubBody>
        </Body>
    <Trailer>
        <f1>03</f1>
        <f2> </f2>
        <f3> </f3>
   </Trailer>
</Recordset>
if this is the input structure then FCC goes like this ....
Recordset:Header,Body,SubBody,Trailer
Header.fieldFixedLengths 10,20,30.. (based on you are structure fixed lengths)
Header.endSeparator - 'nl'
SubBody.fieldFixedLengths 10,20,20 (based on you are structure fixed lengths)
Body.endSeparator - 'nl'
Trailer.fieldFixedLengths 10,20,30.(based on you are structure fixed lengths)
Trailer.endSeparator - 'nl'
We might have to try out SubBody.endSeparator - 'nl' if Body.endSeparator - 'nl' does not insert a new line after each body record.
Cheer's

Need Content Conversion parameter help

Hi,
I need help regarding the Content conversion parameters.I have sent a IDOC and i could receive it as an XML file in my receiver end.
My XML files looks like this
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_IDoc2FILE xmlns:ns0="http://ffvendor">
<NAME>....</NAME>
<EMAIL>....</EMAIL>
<MOBILE>.....</MOBILE>
</ns0:MT_IDoc2FILE>
Please let me know how to convert this to a comma separated flat file
Regards,
Karthik

HI
FCC Paremeters:
nameA.fieldSeparator =~
nameA.endSeparator ='nl'
nameA.fieldNames =text1,text2,text3,text4
nameA.processFieldNames fromConfiguration
nameA.lastFieldsOptional Yes
nameA.missingLastFields Add
nameA.additionalLastFields ignore
ignoreRecordsetName: true
if endSeparator = newline, then
nameA.endSeparator = 'nl'
nameA.fieldSeparator =~
nameA.fieldNames = field1,field2,field3,field4
if endSeparator = #, then
nameA.endSeparator = #
nameA.fieldSeparator =~
nameA.fieldNames = field1,field2,field3,field4
1. NameA.missingLastfields
If the inbound structure has less fields than specified in the configuration then the XML outbound structure is created as follows:
○ ignore
Outbound structure only contains the fields in the inbound structure
○ add
Outbound structure contains all fields from the configuration; the fields missing in the inbound structure are empty.
○ error
Conversion is terminated due to the incomplete inbound structure. An error message is displayed.
2. NameA.additionalLastFields
If the inbound structure has more fields than specified in the configuration then the XML outbound structure is created as follows:
○ ignore
Outbound structure only contains the fields in the inbound structure
○ error
Conversion is terminated due to the incomplete inbound structure. An error message is displayed.
The default value is ignore. If you have defined the NameA.fieldFixedLengths parameter, the default value is error.
If you have defined the NameA.fieldFixedLengths parameter and do not set either of the parameters described above, apart from the default values, the conversion routine works the same as described under Handling Structure Deviations.
Only once you set one of the two parameters will the other parameter be evaluated with its default value.
To ensure a well-defined runtime behavior for variable inbound structures, we recommend that you always set both parameters.
File Content prameters for the Receiver Adapter
http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/frameset.htm
File Content prameters for the Sender Adapter
http://help.sap.com/saphelp_nw04/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm
Refer
File Receiver with Content Conversion
/people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
Configuring the Receiver File/FTP Adapter
http://help.sap.com/saphelp_nw04/helpdata/en/95/bb623c6369f454e10000000a114084/frameset.htm
File content conversion sites
http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm
Please see the below links for file content conversion..
/people/michal.krawczyk2/blog/2004/12/15/how-to-send-a-flat-file-with-fixed-lengths-to-xi-30-using-a-central-file-adapter - FCC
/people/michal.krawczyk2/blog/2004/12/15/how-to-send-a-flat-file-with-fixed-lengths-to-xi-30-using-a-central-file-adapter - FCC
File Content Conversion for Unequal Number of Columns
/people/jeyakumar.muthu2/blog/2005/11/29/file-content-conversion-for-unequal-number-of-columns - FCC
Content Conversion (Pattern/Random content in input file)
/people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file - FCC
/people/harrison.holland5/blog/2006/12/20/xi-configuration-for-mdm-integration--sample-scenario - FCC - MDM
XI in the role of a FTP
/people/shabarish.vijayakumar/blog/2006/04/03/xi-in-the-role-of-a-ftp - FCC
File to R/3 via ABAP Proxy
/people/prateek.shah/blog/2005/06/14/file-to-r3-via-abap-proxy - FCC
/people/mickael.huchet/blog/2006/09/18/xipi-how-to-exclude-files-in-a-sender-file-adapter - EOIO - File
http://help.sap.com/saphelp_nw04/helpdata/en/ee/c9f0b4925af54cb17c454788d8e466/frameset.htm - cc
http://help.sap.com/saphelp_erp2005vp/helpdata/en/95/bb623c6369f454e10000000a114084/content.htm - fcc cOUNTER
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/da1e7c16-0c01-0010-278a-eaed5eae5a5f - conversion agent
cheers

Receiver File Adapter: Problem with NewLine Content Conversion Parameter

Hello Everybody
On our SAP-XI (SAP NetWeaver 2004s, sp14) I have the scenario to send a price catalogue (IDoc PRICECATALOGUE.PRICECATALOGUE02) from SAP R/3 as csv PRICAT file to a file share.
In the receiver communication channel I have defined
Message Protocol = File Content Conversion
using the following RecordSet:
RecordSet = HeaderRow,MainBody
One header row is followed by one or more main body rows. The csv PRICAT message format demands that there is an empty row (i.e. one carriage return) between header and main body and another carriage return after the last main body row:
<Header Row>
carriage return
<MainBody 1>
<MainBody 2>
carriage return
As content conversion parameters I tried to use NewLine ('nl') to create the carriage returns in the file:
HeaderRow.fieldSeparator = ,
HeaderRow.endSeparator = 'nl'     " new line
MainBody.fieldSeparator = ,
MainBody.endSeparator = 'nl'
Using the settings I have been able to created the carriage return at the end of the file but not the one between header and main body.
As workaround I have used the following approach:
" Add the following XSLT mapping between header and body:
            <SeparatorLine>
                <value>
                    <xsl:value-of select=" '' "/>
                </value>
            </SeparatorLine>
RecordSet and parameters have been changed accordingly:
RecordSet = HeaderRow,SeparatorLine,MainBody
HeaderRow.fieldSeparator = ,
HeaderRow.endSeparator = 'nl'
SeparatorLine.fieldFixedLength = 0,0   " sic!
MainBody.fieldSeparator = ,
MainBody.endSeparator = 'nl'
Has anybody an idea why I failed to receive the first carriage return and has somebody a more elegant solution?
Kind Regards
   Uwe

Hi,
Thanks for reply. I have already used 'nl'.
When i open into the notepad it is showing [] boxes rather then new line.
e.g. 1 [] 2 []
but when we open into wordpad it opens properly.
Customer wants when he opens in notepad it should show line by line.
e.g.
1
2
How should i convince to customer ?

Content Conversion Parameter in File Receiver Adapter

Hi all,
I have created one File Receiver Adapter with Message Protocol 'File Content Conversion' and with the following configuration:
Recordset Structure: Message
Message.fieldFixedLengths: 1000
My Message Type is:
LogErro_MT
Message (Type: String) (Occurrence: 0..Unbounded) (Details: Min,Max Length: 1000)
But the file created by it has no data inside it. If I change the Message Protocol to 'File', the content of the file is the XML generated by the Outbound Proxy.
Would someone can help me?
Thanks in advance
Leo

Hi,
Please create a data type with
Records
Message ---0..unbounded
and hten MT for the same.
In the receiver file adapter:
Recordset Structure: Message
Message.fieldFixedLengths: 1000
Please check this weblog for the same:
/people/shabarish.vijayakumar/blog/2006/04/03/xi-in-the-role-of-a-ftp
IS this what you are trying to do.
Regards
Vijaya

Regarding content conversion

HI,
   I have a fixed length text file with data as
5000.00         399   060622       0010000110000000Job 50
2000.00         383   06062257688 0010000110060622Job 11
3000.00         383   0606227876   0010000110060622Job 30
I want to convert into xml format.How a sender adapter should be configured.

Hi,
Please have a look at this weblog for content conversion
/people/shabarish.vijayakumar/blog/2006/02/27/content-conversion-the-key-field-problem
Regards
Vijaya

Reciever Comm. Channel Content conversion parameter for deep level

I am doing a scenario from SAP to Legacy sytem ( Proxy to File Scenario).Target File to be generated is of for fixed length.
__My source strucure is as follows:__
DT_Source
--->Root_IS .......................................0.to..1
DC..............................................0..to..1.............................xsd:string
>Root_VT....................................0..to..unbounded
POY....................................0..to..1.............................xsd:string
PON....................................0..to..1.............................xsd:string
>Root_VR............................0..to..unbounded
POL.............................0..to..1.............................xsd:string
SF----
0..to..1.............................xsd:string
Here DT_source is Data type name,
Root_IS is structure under this we have one field DC,
Root_VT is second field of Root_IS but act a a Stucture for fields POY and PON,
Root_VR is a field of Root_VT but act as a structure for Fields POL and SF.
__My targert strucure is as follows:__
DT_Target
>Root_IS.......................................0.to..1
Key..............................................0..to..1.............................xsd:string
DC..............................................0..to..1.............................xsd:string
>Root_VT....................................0..to..unbounded
Key..............................................0..to..1.............................xsd:string
POY....................................0..to..1.............................xsd:string
PON....................................0..to..1.............................xsd:string
>Root_VR............................0..to..unbounded
Key..............................................0..to..1.............................xsd:string
POL.............................0..to..1.............................xsd:string
SF----
0..to..1.............................xsd:string
>Root_ZS............................0..to..1
Key..............................................0..to..1.............................xsd:string
Count...........................................0..to..1.............................xsd:string
Here DT_Target is data type for file reciever.In which i need to configure reciever communication channel with file content conversion parameters.File needs to be generated is of fixed length.Root_IS,Root_VT,Root_ZS are sructure on same level and Root_VR sructure is under Root_VT.
I tried to Configure File Content Conversion Parameters on reciever Comm Channel but getting comm channel error as follows:
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'java.lang.Exception: Consistency error: more fields found in XML structure than specified in conversion parameters! (Value 'VR')', probably configuration error in file adapter (XML parser error)': java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'java.lang.Exception: Consistency error: more fields found in XML structure than specified in conversion parameters! (Value 'VR')', probably configuration error in file adapter (XML parser error)'
Could not process due to error: java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'java.lang.Exception: Consistency error: more fields found in XML structure than specified in conversion parameters! (Value 'VR')', probably configuration error in file adapter (XML parser error)'
File content parameters i used as follows:
Root_IS.fieldNames                                      : Key,DC
Root_IS.fieldFixedLengths                           :(as per length mentioned)
Root_IS.endSeparator                                 :'nl'
Root_VT.fieldNames                                   :Key,POY,PON
Root_VT.fieldFixedLengths                        :(as per length mentioned)
Root_VT.endSeparator                              :'nl'
Root_VR.fieldNames                                  :Key,POL,SF
Root_VR.fieldFixedLengths                       :(as per length mentioned)
Root_VR.endSeparator                             :'nl'
Root_ZS.fieldNames                                 :Key,Count
Root_ZS.fieldFixedLengths                      :(as per length mentioned)
Root_ZS.endSeparator                            :'nl'

Please consider this one as new: i tried to explain it more as on privew everything gets shaked
I am doing a scenario from SAP to Legacy sytem ( Proxy to File Scenario).Target File to be generated is of for fixed length.
__My source strucure is as follows:__
DT_Source
--->Root_IS .......................................0.to..1
DC..............................................0..to..1.............................xsd:string
>Root_VT....................................0..to..unbounded
POY....................................0..to..1.............................xsd:string
PON....................................0..to..1.............................xsd:string
>Root_VR............................0..to..unbounded
POL.............................0..to..1.............................xsd:string
SF----
0..to..1.............................xsd:string
Here DT_source is Data type name,
Root_IS is structure under this we have one field DC as a child,
Root_VT(structure) is second field of Root_IS but act a a Parent Stucture for fields POY and PON,
Root_VR(structure) is a field of Root_VT but act as a Parent structure for Fields POL and SF.Means we have three structres Root_IS and under this we have Root_VT and under this we have Root_VR
__My targert strucure is as follows:__
DT_Target
>Root_IS.......................................0.to..1
Key..............................................0..to..1.............................xsd:string
DC..............................................0..to..1.............................xsd:string
>Root_VT....................................0..to..unbounded
Key..............................................0..to..1.............................xsd:string
POY....................................0..to..1.............................xsd:string
PON....................................0..to..1.............................xsd:string
>Root_VR............................0..to..unbounded
Key..............................................0..to..1.............................xsd:string
POL.............................0..to..1.............................xsd:string
SF----
0..to..1.............................xsd:string
>Root_ZS............................0..to..1
Key..............................................0..to..1.............................xsd:string
Count...........................................0..to..1.............................xsd:string
Here DT_Target is data type for file reciever.In which i need to configure reciever communication channel with file content conversion parameters.File needs to be generated is of fixed length.Root_IS,Root_VT,Root_ZS are sructure on same level as a first level subelements of DT_Target and Root_VR sructure is under Root_VT.
Root_IS have fileds: key,DC: Root_VT have Fields :Key,POY,PON:Root_VR have fields:Key,POL,SF and Root_ZS have Fields:Key and Counts.
I tried to Configure File Content Conversion Parameters on reciever Comm Channel but getting comm channel error as follows:----
>
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'java.lang.Exception: Consistency error: more fields found in XML structure than specified in conversion parameters! (Value 'VR')', probably configuration error in file adapter (XML parser error)': java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'java.lang.Exception: Consistency error: more fields found in XML structure than specified in conversion parameters! (Value 'VR')', probably configuration error in file adapter (XML parser error)'
Could not process due to error: java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'java.lang.Exception: Consistency error: more fields found in XML structure than specified in conversion parameters! (Value 'VR')', probably configuration error in file adapter (XML parser error)'
File content parameters i used as follows:
Root_IS.fieldNames                                      : Key,DC
Root_IS.fieldFixedLengths                           :(as per length mentioned)
Root_IS.endSeparator                                 :'nl'
Root_VT.fieldNames                                   :Key,POY,PON
Root_VT.fieldFixedLengths                        :(as per length mentioned)
Root_VT.endSeparator                              :'nl'
Root_VR.fieldNames                                  :Key,POL,SF
Root_VR.fieldFixedLengths                       :(as per length mentioned)
Root_VR.endSeparator                             :'nl'
Root_ZS.fieldNames                                 :Key,Count
Root_ZS.fieldFixedLengths                      :(as per length mentioned)
Root_ZS.endSeparator                            :'nl'

Regarding content conversion parameters

Hi,
Can anyone send me a blog that completely explains in detail about each and every content conversion parameters?Need complete info about ALL those parameters
Thanks in Advance

Hi Rambabu,
Try to implement scenarios in these weblogs...it cover almost all type of scenarios
/people/michal.krawczyk2/blog/2004/12/15/how-to-send-a-flat-file-with-fixed-lengths-to-xi-30-using-a-central-file-adapter
/people/jeyakumar.muthu2/blog/2005/11/29/file-content-conversion-for-unequal-number-of-columns
/people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
/people/prateek.shah/blog/2005/06/14/file-to-r3-via-abap-proxy
/people/venkat.donela/blog/2005/06/08/how-to-send-a-flat-file-with-various-field-lengths-and-variable-substructures-to-xi-30
Also go through this :
Converting File Content in the Sender Adapter:
http://help.sap.com/saphelp_nw04/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/frameset.htm
Converting File Content in the Receiver Adapter:
http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm
Thanks,
Maheshwari.

Regarding content conversion parameters at receiver side

Hi
In the recevier side I have 3 nodes.
like HEADER,BODY,TRAILER.
file receiver communication channel I mentioned
RecordsetStructure* HEADER,BODY,TRAILER
parmeters I mentioned
HEADER.fieldFixedLengths
HEADER.endSeparator
BODY.fieldFixedLengths
BODY.endSeparator
TRAILER.fieldFixedLenghths
TRAILER.endSeparator.
In runtime workbench it is showing "Channel has not been correctly initialized and cannot process messages"
Please tell me is there any other parameters I have to mention.
regards
venkat.

Venkat,
Pls refrer the below:
http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm
Regards,
Sameer!

REGARDING CONTENT CONVERSION IN SENDER SIDE

Hi
I have a flat file like this
column names NO NAME AGE
FLAT FILE IS   1#KIRAN#27
                       2###28
                       3#RAVI#28
in the second record the name field is also filled with #
so please tell me how can we handle this
thanks&regards
venkat

Hi Venkat ,
Use .fieldFixedLengths option if lenth is always unique,
If not you have to go for UDF..as i Know.
If you made a specification for .fieldFixedLengths, the length of the separator is not taken into account.
You must specify at least either NameA.fieldFixedLengths or NameA.fieldSeparator.
If you have only specified .fieldSeparator, the structures of the XML document can have differing numbers of elements that are added to each other separately in the text file by the value from .fieldSeparator. If you specify .fieldFixedLengths this is not possible since the number of columns is defined when the column widths are given.
BestRegards,
Ramesh.

Regarding content conversion paratmeters

Hi
In my scenario we are using in the receiver file format # as field
separator and in the same scenario we are using # for empty column field .
so please tell me can we use one operator for both requirements
regards
venkat.

Hi,
Technically it will work and you will get a ouput like this.
Sample output:(if you use # for both.)
field1#field2###field4
Sample output:(if you use # for empty field and tabdelimeter for seperator)
field1 field2 # field4
always look for a meaning full output.
Regards,
Saravanan.R

Inconsistent Data for File Content Conversion

HI XI Friends,
Its IDOC to File Scanario,
File is of .txt file..
my IDOC contains 14 segments
some times some segements will not come with Idoc..
first three characters represent segment numbers..
structure of txt file
00112345       address1 street1
00212345       office1      street1
00312345       homw2     city2     street2
if that IDOC doent contain 002..then .txt file should be..
00112345       address1 street1
00312345       homw2     city2    street2
all Segement in that idoc are optional..
if I use Fixed lengh in File Content Conversion then ther would be blank row for 002 if that IDOc doent Conatin
00112345       address1 street1
00312345       homw2     city2    street2
please guide me...how to use content conversion in this case..
regards
Munna

Hi ,
Thank you very much for your response..
.txt file is of fixed lenths with no field Seperator
IDOC contains number segements..
the resultant txt file if we created first 3 segements data..
00112345 address1 street1
00212345 office1 street1
00312345 homw2 city2 street2
if we create 001 segment and 003 segement the text file should be
00112345 address1 street1
00312345 homw2 city2 street2
but for new row of each segment ... endseperator 'nl' after first segemnt in Content conversion parameter and 002 segement values..and again endSeperator 'nl'...
if we are not sending 002 segement data in the IDOC ..then it will give blank
00112345 address1 street1
00312345 homw2 city2 street2
my requirement is if we dont send 002 segement data then no blank row .how to check if the segement is having data or not and also how to declare it in Content Conversion parameters of File Adapters.
please guide me
regards
Munna

Remove blank line after File Content Conversion

I have a File>Conversion on PI7.0 (SP10).
It seems to add a blank line. The XML is:
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:EPIWCountFile xmlns:ns0="urn:com.somewhere.overthere.nothere">
<Personal_Area>LU</Personal_Area>
- <detail>
<recordCount>17</recordCount>
</detail>
</ns0:EPIWCountFile>
The conversion is done:
recordset Structure=detail,
name=detail.fieldseparator ,
The output file is
17
Hopefully you can see the blank line before the number!???
I have changed the contexts while processing, and played with other options, but it always adds a blank line at the begin.
All this file is a count of the number of records processed. (The personal_area is for a variable name for file/folder creation)
How can I remove the blank line, as the target system fails due to this anomaly?

If you are in a development environment, try this
Make your target structure
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:EPIWCountFile xmlns:ns0="urn:com.somewhere.overthere.nothere">
- <detail>
<b><Personal_Area>LU</Personal_Area></b>
<recordCount>17</recordCount>
</detail>
</ns0:EPIWCountFile>
Content conversion parameter
detail.fieldFixedLengths 0,2
detail.fixedLengthTooShortHandling Cut
P.S: If you need <Pesonal_Area> tag only for File/Folder Name, then why dont you use Adapter specific Identifiers to achieve the same.
Regards,
Jai Shankar

Regarding content conversion parameter

Similar Messages

Maybe you are looking for