EndSeparator: '0x0D''0x0A'

Hi,
I am using file content conversion with fixed width in my receiver file communication channnel.
In the endSeparator, I am using '0x0D''0x0A'. This is end separator is not working.
Your help will be appreciated.
Thanks

Check this:
http://help.sap.com/saphelp_nw70/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm
To include a line break following the closing character, you must explicitly define it by attaching ´nl´ (including the quotation marks) to the string.
So you will have to specify 'nl' also with '0x20'
Thanks,
Beena.

Similar Messages

Not getting 0x0D 0x0A child record delimiter

Hi - I have a simple flat file schema with fixed length records and a Cr Lf delimiter at the end of every record. The map performs beautifully when I test it in VS2010 but I don't get the delimiter when I add the map to the inbound maps in the receive port.
Any Ideas - I have kind of bent my pick on this one for a while.
Thanks in advance
Harold
Harold Rosenkrans

Ok,update - I specified ASCII in the target charset for the File Assembly component of the Custom Send pipeline I am using. Still no respect for the outbound FF schema postfix 0X0D 0x0A to child records. the resulting flat file didn't have the CrLf record
delimiters.
So just for grins I explicitly appended the CrLf to each text string record in the Oracle procedure. The custom pipeline does not strip them out and the records in the resulting flat file have the CrLf (0x0D 0x0A) record delimiters.
So that leads me to conclude the problem is in the flat file XSD - the xml is well formed, it passes through the parser with no problems and as I mentioned earlier when I test the map with this schema the resulting test file has the 0x0D 0x0A child record
delimiters. I have investigated a good number of possibilities without success. I guess I should take comfort in a work-around but this should just work as defined. Am I missing something in the Flat File schema?
Thanks
<?xml version="1.0" encoding="UTF-16"?>
-<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://cf.S2K_SAP.s2k_sap_ar.schemas.sap_ar" xmlns:b="http://schemas.microsoft.com/BizTalk/2003"
xmlns="http://cf.S2K_SAP.s2k_sap_ar.schemas.sap_ar"> -<xs:annotation> -<xs:appinfo> <schemaEditorExtension:schemaInfo xmlns:schemaEditorExtension="http://schemas.microsoft.com/BizTalk/2003/SchemaEditorExtensions"
standardName="Flat File" extensionClass="Microsoft.BizTalk.FlatFileExtension.FlatFileExtension" namespaceAlias="b"/> <b:schemaInfo root_reference="APData" compile_parse_tables="false" allow_message_breakup_of_infix_root="false"
early_terminate_optional_fields="false" allow_early_termination="false" generate_empty_nodes="true" suppress_empty_nodes="false" lookahead_depth="3" parser_optimization="speed" count_positions_by_byte="false"
pad_char_type="char" default_pad_char=" " codepage="65001" standard="Flat File"/> </xs:appinfo> </xs:annotation> -<xs:element name="APData"> -<xs:annotation> -<xs:appinfo> <b:recordInfo
suppress_trailing_delimiters="false" preserve_delimiter_for_empty_data="true" sequence_number="1" child_order="postfix" child_delimiter="0xD 0xA" child_delimiter_type="hex" structure="delimited"/>
</xs:appinfo> </xs:annotation> -<xs:complexType> -<xs:sequence> -<xs:annotation> -<xs:appinfo> <groupInfo xmlns="http://schemas.microsoft.com/BizTalk/2003"
sequence_number="0"/> </xs:appinfo> </xs:annotation> -<xs:element name="APDataRecord" maxOccurs="unbounded"> -<xs:annotation> -<xs:appinfo> <b:recordInfo suppress_trailing_delimiters="false"
preserve_delimiter_for_empty_data="true" sequence_number="1" structure="positional"/> </xs:appinfo> </xs:annotation> -<xs:complexType> -<xs:sequence> -<xs:annotation> -<xs:appinfo> <groupInfo
xmlns="http://schemas.microsoft.com/BizTalk/2003" sequence_number="0"/> </xs:appinfo> </xs:annotation> -<xs:element name="RecordString" type="xs:string">
-<xs:annotation> -<xs:appinfo> <b:fieldInfo sequence_number="1" pos_length="240" pos_offset="0" justification="left"/> </xs:appinfo> </xs:annotation> </xs:element> </xs:sequence>
</xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> </xs:schema>
Harold Rosenkrans

File sender - carriage return and new line as endseparator

Hi All,
I'm stumbled with a problem to set carriage return and newline character as the endseparator (record delimiter)
Scenario: The input file PI is receiving has got few fields which has text in it and the content in this text has got newline characters. So to identify record separator, at the end of each record the combination of carriage return and new line is added.
In file sender content conversion I've set the folllowing parameters to achieve this:
Row.fieldSeparator : , (comma)
Row.endSeparator : '0x0D''0x0A'
Problem: In my sample input file, the first row has a text field with a newline character. When executed PI is splitting the record at the newline character in the text field (instead of combination of carriagereturn and newline which is set in the endSeparator paramter).
Pls advice on how to resolve this .
Happy Holidays!!
amar

Rajesh..Thanks for your quick response
I'm trying with the actual file being provided by the trading partner. I did not generate the file nor changed the file..
Before identifying the combination of carraige return and new line, the adapter is splitting the record when encountered with new line character within one of the text fields.
As you said it worked for you, you do have new line characters within fields in a record?..pls throw some light..let me know for any information..
Thank you
amar--

File Settings

Hi,
Currently this is my file sender configuration.
ProcOrdRecs.fieldSeparator            ","
ProcOrdRecs.endSeparator             "'0x0D''0x0A'
ProcOrdRecs.beginSeparator          "
The file got failed at the vendor side where he has given his inpus the following.
Your line endings are <CR><LF> NOT <CR><CR><LF>. You need to put the extra <CR> back in.
How can i add an extra <CR> to be generated in the file.

you need to create an output file with <CR><CR><LF> for the vendor?
In that case in your receiver adapter try
<XYZ>.endSeparator            '0x0D''0x0D''0x0A'

More fields in XML structure error in Adapter Monitor

Hi all
I am getting the following error in the adapter monitor
Error: Message processing failed: 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 ' ')', probably configuration error in file adapter (XML parser error)'
I am using FCC in the rx adapter. I have also checked the fields for any extra fields but there isnt any.
kindly suggest what could be throwing the error
regards
krishna

Hi raj
here are the CC parameters.
BEGIN.addHeaderLine     0
BEGIN.fieldFixedLengths     2,1,3,2,4,1,8,12,8,2,307,12,8,12,18
BEGIN.fixedLengthTooShortHandling     Ignore
BEGIN.endSeparator     '0x0D''0x0A'
CLIENT_RECORD.addHeaderLine     0
CLIENT_RECORD.fieldFixedLengths     2,12,9,4,15,15,4,20,12,9,8,1,1,25,10,1,25,10,1,6,1,1,1,1,1,10,8,1,25,2,1,1,1,106,12,38
CLIENT_RECORD.fixedLengthTooShortHandling     Ignore
CLIENT_RECORD.endSeparator     '0x0D''0x0A'
RELATION_RECORD.addHeaderLine     0
RELATION_RECORD.fieldFixedLengths     2,12,9,4,20,20,2,2,9,8,1,25,10,1,25,10,1,6,1,1,181,12,38
RELATION_RECORD.fixedLengthTooShortHandling     Ignore
RELATION_RECORD.endSeparator     '0x0D''0x0A'
ADDRESS_RECORD.addHeaderLine     0
ADDRESS_RECORD.fieldFixedLengths     2,12,9,4,20,20,2,2,5,6,8,24,24,2,35,15,4,15,4,70,8,8,1,50,12,38
ADDRESS_RECORD.fixedLengthTooShortHandling     Ignore
ADDRESS_RECORD.endSeparator     '0x0D''0x0A'
GIVING_REC.addHeaderLine     0
GIVING_REC.fieldFixedLengths     2,12,9,4,20,9,1,1,1,1,1,1,1,1,1,1,1,1,1,281,12,38
GIVING_REC.fixedLengthTooShortHandling     Ignore
GIVING_REC.endSeparator     '0x0D''0x0A'
ZIKT_REC.addHeaderLine     0
ZIKT_REC.fieldFixedLengths     2,12,9,4,20,9,2,3,2,8,1,1,277,12,38
ZIKT_REC.fixedLengthTooShortHandling     Ignore
ZIKT_REC.endSeparator     '0x0D''0x0A'
BEPER_REC.addHeaderLine     0
BEPER_REC.fieldFixedLengths     2,12,9,4,20,9,1,1,1,291,12,38
BEPER_REC.fixedLengthTooShortHandling     Cut
BEPER_REC.endSeparator     '0x0D''0x0A'
SCORE_BEPER_REC.addHeaderLine     0
SCORE_BEPER_REC.fieldFixedLengths     2,12,9,4,20,9,1,3,4,1,1,284,12,38
SCORE_BEPER_REC.fixedLengthTooShortHandling     Ignore
SCORE_BEPER_REC.endSeparator     '0x0D''0x0A'
INDBES_REC.addHeaderLine     0
INDBES_REC.fieldFixedLengths     2,12,9,4,20,9,9,2,2,8,8,8,1,256,12,38
INDBES_REC.fixedLengthTooShortHandling     Ignore
INDBES_REC.endSeparator     '0x0D''0x0A'
FUNCTIONAL_REC.addHeaderLine     0
FUNCTIONAL_REC.fieldFixedLengths     2,12,9,4,20,9,9,3,2,8,8,8,1,4,2,2,1,1,1,1,8,1,1,233,12,38
FUNCTIONAL_REC.fixedLengthTooShortHandling     Ignore
FUNCTIONAL_REC.endSeparator     '0x0D''0x0A'
ACT_REC.addHeaderLine     0
ACT_REC.fieldFixedLengths     2,12,9,4,20,9,9,3,2,8,3,5,1,263,12,38
ACT_REC.fixedLengthTooShortHandling     Ignore
ACT_REC.endSeparator     '0x0D''0x0A'
SCORE_REC.addHeaderLine     0
SCORE_REC.fieldFixedLengths     2,12,9,4,20,9,3,4,1,1,285,12,38
SCORE_REC.fixedLengthTooShortHandling     Ignore
SCORE_REC.endSeparator     '0x0D''0x0A'
ZFUNCTIONAL_REC.addHeaderLine     0
ZFUNCTIONAL_REC.fieldFixedLengths     2,12,9,4,20,9,9,12,3,2,8,8,5,1,8,8,8,4,2,2,1,1,1,1,210,12,38
ZFUNCTIONAL_REC.fixedLengthTooShortHandling     Ignore
ZFUNCTIONAL_REC.endSeparator     '0x0D''0x0A'
ZACT_REC.addHeaderLine     0
ZACT_REC.fieldFixedLengths     2,12,9,4,20,9,9,3,2,3,5,8,8,5,8,1,242,12,38
ZACT_REC.fixedLengthTooShortHandling     Ignore
ZACT_REC.endSeparator     '0x0D''0x0A'
COMMENT.addHeaderLine     0
COMMENT.fieldFixedLengths     2,12,4,140,1,191,12,38
COMMENT.fixedLengthTooShortHandling     Ignore
COMMENT.endSeparator     '0x0D''0x0A'
END_REC.addHeaderLine     0
END_REC.fieldFixedLengths     2,6,6,6,6,6,6,6,6,6,6,6,6,6,6,6,1,257,50
END_REC.fixedLengthTooShortHandling     Ignore
END_REC.endSeparator     '0x0D''0x0A'
REgards
krishna

Add header line to the text file in receiver file adapter

Hello Experts,
I have to add a new line to the text file generated at the receiver end.
My structure is
Record
   Item......0-unbounded
         field1
         field2
         field3
I have defined below parameters in receiver FCC.
RecordSet Structure : Record,Item
Item.fieldSeparator : ;
Record.fieldSeparator : nl
Record.endSeparator : '0x0D''0x0A' ( this is to get a carriage return at the end of the file)
Item.addHeaderLine : 1
With the above configuration, i am getting the desired output with NO header line.
Please help.
Thanks,
Swetha.

Hi, it looks like that the headerline "specification is only permitted if exactly one structure is defined." Please check [SAP help under Define Parameters for Recordset Structures|http://help.sap.com/saphelp_nw73/helpdata/en/44/686e687f2a6d12e10000000a1553f6/frameset.htm].
One solution would be to generate the header fields in the message payload. Generate an additional first line containing the header names, e.g.
<Item>
<field1>Header1
<field2>Header2
<field3>Header3

Content Conversion headerline with CRLF not working

I am using content conversion in my receiver channel. I have a header line (addHeaderLine=3 and headerLine=xxxxx). My xml.endSeparator='0x0D''0x0A'. However, the header line is not getting the '0x0D''0x0A'. It appears to only be getting the LF but not the CRLF that is requires for a Windows system. This causes issues because it concatenates the first line of data to the end of the header line. I have read of others having this same issue on SDN, but I haven't seen a solution except to separate the header in the receiver structure and map the header values in the message mapping. Is there any other way?

Check
http://help.sap.com/saphelp_nw70/helpdata/en/d2/bab440c97f3716e10000000a155106/frameset.htm
Instead of '0x0D''0x0A' you can use 'nl' directly.
Also check the syntax of parameter name
NameA.addHeaderLine = 3
NameA.headerLine = xxxxx
NameA.endSeparator = 'nl'
Regards
Raj

Conversion file adapter

Hi all,
I have the following xml:
<?xml version="1.0" encoding="UTF-8"?>
<ns:PayLinkV1 xmlns:ns="urn:basf:sa:fi:cash">
<payRecord>
    <recType>PAY</recType>
    <countryCode>032</countryCode>
    <payFlag />
    <filler />
    <invoice>
      <recType>VOI</recType>
      <countryCode>032</countryCode>
      <description>0001A0000GAL1</description>
      <filler />
    </invoice>
    <invoice>
      <recType>VOI</recType>
      <countryCode>032</countryCode>
      <description>0001A0000GAL2</description>
      <filler />
    </invoice>
</payRecord>
<payRecord>
    <recType>PAY</recType>
    <countryCode>032</countryCode>
    <payFlag />
    <filler />
    <invoice>
      <recType>VOI</recType>
      <countryCode>032</countryCode>
      <description>0001A0000CIT3</description>
      <filler />
    </invoice>
    <invoice>
      <recType>VOI</recType>
      <countryCode>032</countryCode>
      <description>0001A0000CIT2</description>
      <filler />
    </invoice>
</payRecord>
<trailer>
    <recType>TRL</recType>
    <qtyTransaction>000000000000000</qtyTransaction>
    <qtyAmount>000000000000000</qtyAmount>
    <qtyRec>000000000000000</qtyRec>
    <qtyRecNo>000000000000000</qtyRecNo>
    <filler />
</trailer>
</ns:PayLinkV1>
I need to convert it in one text file with this layout:
fields of payrecord
fields of invoice
fields of invoice
fields of payrecord
fields of invoice
fields of invoice
fields of trailler
In may file conversion type has the following configuration:
Recordset structure: payRecord,invoice,trailer
payRecord.fieldFixedLengths: 3,3,10,6,3...
invoice.fieldFixedLengths: 3,3,10,15...
trailer.fieldFixedLengths: 3,15,15...
But in the file adapeter occurs one error with this configuration.Anybody have an ideia to do it?
thanks!

I did file content conversion. I enclosed my message with a root in xml. Then my Recordsetstructure looks like
row,payRecord,invoice,trailer.
The following worked for me. I just modified my example for you with your values:
root.fieldSeparator:'0x0D''0x0A'
payRecord.addHeaderLine: 0
payRecord.fieldFixedLengths:3,3,10,15...
payRecord.fixedLengthTooShortHandling Ignore
payRecord.endSeparator '0x0D''0x0A'
invoice.addHeaderLine: 0
invoice.fieldFixedLengths:3,3,10,15...
invoice.fixedLengthTooShortHandling Ignore
invoice.endSeparator '0x0D''0x0A'
trailer.addHeaderLine: 0
trailer.fieldFixedLengths:3,15,15...
trailer.fixedLengthTooShortHandling Ignore
trailer.endSeparator:'0x0D''0x0A'
Also check the number of columns you have in your fieldFixedLengths and in the xml.
Regards
Venkat

FCC Sender Problems.

Hi,
This is my source file format.
"abc","asdf","1212","2323"
Source File Structure:
EAN
MaterialNo
Plant
MaterialDesc
I have just created a sender communication channel and given these parameters in the content conversion.
RecordSetName: ProcOrdRecs
RecordSetStructure: ProcOrdRecs,*
RecordSetSequence: Ascending
ProcOrdRecs.fieldSeparator ','
ProcOrdRecs.endSeparator "'0x0D''0x0A'
ProcOrdRecs.beginSeparator "
ProdOrdRecs.fieldNames EAN,MaterialNo,Plant,MaterialDesc
I am unable to start the channel itself as it gives me the following error
Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Mandatory parameter 'ProcOrdRecs.fieldNames': no value found
Though I have provided the field names, still it gives me the same error. I checked the spelling and number of fields and it seems quite ok.

There was a problem with extra space associated in the field names.

Carriage Return and Line Feed in Receiver FTP

Hi,
what parameter needs to be used in receiver File content conversion to accomodate <CR> and <LF>
The generated file from XI is CSV format and am now used only this option in the content conversion.
record.fieldSeparator ,
I did find something like record.endseparator '0x0D"0x0A' but not sure whether this is right

If I were creating an output file, it would look something like this (this is off top of head...not from my actual code, so bug removal might be required):
types: begin of outx,
            line(1024) type c,
         end of outx.
data: out_file type table of outx.
         out_line type             outx.
data: p_field(15) type p decimals 0,
         a_field(17).
constants: gc_tab type x value '09',
                 gc_crlf(2) type x value '0D0A'. "those are zeroes...
field-symbols: <fs> type (same as your internal table),
                       <fsx> type any.
loop at internal table assigning <fs>.
   if <fs> is assigned.
      do.
      assign component sy-index of structure <fs> to <fsx>.
    if sy-subrc ne 0. "end of row encountered...exit do loop
      exit.
   endif.
* insert logic to do any data conversions (i to p to a, etc.), like:
* if sy-index eq <somenumber>.
* P_field = <fsx>. " any I field.
* a_field = p_field.
* assign a_field to   <fsx> casting type char17.
*endif.
if sy-index eq 1.
   out_line-line= <fsx>.
else.
   concatenate out_line-line <fsx> into out_line-line separated by gc_tab.
endif.
enddo.
if outline-line is not initial.
concatenate outline-line gc_crlf into outline-line.
condense out_line-line. "add no-gaps if appropriate
append out_line to out_file.
clear out_line.
endif.
endif. "is assigned
endloop."internal table
Edited by: BreakPoint on Dec 1, 2010 3:39 PM
can't spell concatenate correctly.

Content Coversion in Receiver Channel to Windows platform adding xtra space

I am using SAP's content conversion module, MessageTransformBean, to build a file from a proxy. If I send the file to a UNIX platform, everything is ok. If I send the file to a Windows platform, an extra space is added at the end of each line, making the record length 1 character too long. I changed it to comma delimited, and the extra space was not added. Is there anything special I need to do when sending to a Windows platform?
fcc     Transform.Class                                                                                    com.sap.aii.af.sdk.xi.adapter.Conversion
fcc     Transform.ContentType                                                                                    text/plain;charset=utf-8
fcc     xml.ZH38CI_BN_US_DELTA_CA_DTL.fieldFixedLengths                          1,9,4,4,1,6,1,8,16,6,6,1,6,6,1,1,3
fcc     xml.ZH38CI_BN_US_DELTA_CA_DTL.fixedLengthTooShortHandling     Cut
fcc     xml.ZH38CI_BN_US_DELTA_CA_HDR.fieldFixedLengths                          1,2,4,30,29,10,4
fcc     xml.ZH38CI_BN_US_DELTA_CA_HDR.fixedLengthTooShortHandling     Cut
fcc     xml.ZH38CI_BN_US_DELTA_CA_TRL.fieldFixedLengths                          1,8,71
fcc     xml.ZH38CI_BN_US_DELTA_CA_TRL.fixedLengthTooShortHandling     Cut
fcc     xml.addHeaderLine                                                                                0
fcc     xml.conversionType                                                                                StructXML2Plain
fcc     xml.recordsetStructure                     ZH38CI_BN_US_DELTA_CA_HDR,ZH38CI_BN_US_DELTA_CA_DTL,ZH38CI_BN_US_DELTA_CA_TRL

I tried moving the module to every possible position, and I could not get it to work for receiver channel. Maybe I didn't have something correct, but I was able to use this solution in a sender channel. Thank you for that. FYI...I was able to get the my receiver channel working with the following parameter for each structure.
xml.XXXXXXXXXX.endSeparator     '0x0D''0x0A'

Empty Lines are not taking

Hi all,
    I am doing the scenarios File-File with FCC. My source file is as follows. But it is not picking the Empty lines which are there in the source file
So My structure as follows:
MT_BNK01 1..1
RECORD 0..Unbound
--Record_data 0..Unbound
So in the Sender CC i written as follows
Recordset Structure:: RECORD,1
FCC paramtetrs as follows
RECORD.fieldNames     RECORD_DATA
RECORD.fieldSeparator     '0x0D''nl'
ignoreRecordsetName     true
What i need to do extra to capture the empty lines from my source.
Thanks in Advance,
Best Regards,
Vijay

Hi Rajesh,
I did that one also. There is no effect. Currently i am using all the these FCC paramters:
RECORD.fieldNames     RECORD_DATA
RECORD.fieldSeparator     '0x0D''nl'
RECORD.endSeparator     '0x0D''0x0A'
ignoreRecordsetName     true
RECORD.fieldContentFormatting     nothing
RECORD.enclosureConversion     YES
The problem here , we given the 'nl' as the fieldSeparator. So if 2 consucutive 'nl' comes then there no value between them so it is suppressing. How to overcome this.
Warm Regards,
Vijay

Receiver File/FTP, SFTP, binary, endSeparator for CRLF ?

We are planning an interface using the Receiver File/FTP Adapter, using SFTP in binary mode.
The SAP PI runs on Unix, the other applications runs on Windows.
Can NameA.endSeparator be used to ensure that every line in this file ends on CRLF?
(As you know, Windows has the habit of ending lines in text files with CRLF - carriagereturn-linefeed, whereas Unix uses a singe LF - linefeed, also known as newline or nl).

Yes it can be done with '0x0D''0x0A' value which represents the CR and LF respectively...
which has been implemented succesfully in our interface...
HTH
Rajesh

Urgent: Suppressing unwanted Node Line in the target file

Hi all ,
I am doing simple file to file scenario in which i have following as my target structure.
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_IN007_IN xmlns:ns0="Http://xyz.pi.com/OTC/IN007_ABC_PQR">
   <OUTPUT>
      <HEADER>
         <ShipmentDate/>
         <FROMCompund/>
         <TOCompound/>
         <ShipmentNumber/>
         <Carrier/>
         <TruckNumber/>
         <TrailerId/>
         <ContainerCount/>
         <TotalNetWeight/>
         <OwnerId/>
      </HEADER>
      <DELIVERY>
                 <DeliveryNo/>
      </DELIVERY>
      <DETAILS>
         <TransactionType/>
         <ContainerNo/>
         <CheckDigit/>
         <Condition/>
         <RJRGrade/>
         <Belt/>
         <CropYear/>
         <Processor/>
         <ContainerNetWeight/>
         <ContainerType/>
         <ProductionDate/>
         <ProductionTime/>
         <ProcessorBaleId/>
         <DealerContainerId/>
         <CustomerPackageId/>
      </DETAILS>
   </OUTPUT>
</ns0:MT_IN007_IN>
I am using Delivery node for generating file with the name in its subfield Delivery_No with the help of variable substitution. I dont want the Delivery node to be appearing in my output file,so i am suppressing it in my communication channel as shown below:
OUTPUT.fieldFixedLengths    161
OUTPUT.fieldSeparator          'nl'
HEADER.fieldFixedLengths    8,4,4,2,15,15,15,3,5,1,3
HEADER.endSeparator          'nl'
DELIVERY.fieldFixedLengths 0
DELIVERY.fixedLengthTooShortHandling   Cut
DETAILS.fieldFixedLengths      1,8,1,3,10,2,4,3,4,1,8,6,14,6,15
DETAILS.endSeparator             'nl'
In the Output file I am not getting the delivery node but a line break for it which i dont want to be there.I can't even change the structure so dat line break comes at the end.
Please help
Thanks in Advance,
Amit

Hi Swaroop,
I tried putting the null value as you mentioned but it didnot work, it is giving me now following error in AUDIT LOG in message monitoring :
File adapter receiver channel CC_IN007_OUT is not initialized. Unable to proceed: null
Delivery of the message to the application using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Channel has not been correctly initialized and cannot process messages.
I only put the field seperator in my delivery node and removed fieldFixedLength parameters from it as below :
DELIVERY.fieldSeperator      '0x0D''0x0A'
Please help.
Thanks,
Amit

JMS sender adapter conversion prblem

Hi All,
I am sending this query again as I think there is some confusion in understanding my problem
Hi,
I am using JMS adapter to read data from MQ. The length of each segment is fixed.
The problem is there is <b>no new line</b> character at the end of each segment .So JMS adapter is just reading the first line and not reading the rest.
What I found out that if I place a <b>new line character</b> at the end of <b>each segment</b> (i.e. The program that is used to upload this data from a file to MQ appends a new line char at the end of each line), it works fine.
But for me I have a constraint that in MQ the source system cannot send a new line character at the end of each segment (i.e at the end of each line). So can any one tell me how can I solve this issue?
I tried using <b>xml.endSeparator '0x0D'</b> in the module processor also as per one gentle man's suggestion . But it also does not work.
The sample data that I am getting from MQ is:
AA12345
BBXYZXY
BB12300
Then in the module processor I have defined
xml.recordsetStructure NameA,1,NameB,*
xml.NameA.fieldNames MyKey,field-nameA
xml.NameA.fieldFixedLengths 2,7
xml.NameA.fieldNames MyKey,field-nameB
xml.NameB.fieldFixedLengths 2,5
We are using SP13.
The length of each segment is fixed.
Any help is appreciated

Hi Vishnu,
I have tried this too. But this does not work either.
What I believe, the system skips this separator (in this case 0x0D''0x0A'), when it processes the last column. (Otherwise the system would treat it as part of the last column).
But here there is no new line character coming. So do you think xml.endSeparator will be of any help.
I think if there is some way we can tell the adapter to read the first segment depending on the total value of length specified in xml.A1.fieldFixedLengths (instead of looking for a new line character) and then it should treat the next character as a part of next segment then that should resolve the problem.
Please suggest

EndSeparator: '0x0D''0x0A'

Similar Messages

Maybe you are looking for