Receiver FCC

Hi All,
I am having an issue in reciever FCC, where my last field being 10 space and each record is separeted by a new line, the last field gets trimmed for the space, Could you provide your inputs.
For example, my output record shd be like, without trimming the spaces at the end.
1 2 3 4 5 6 <10 spaces>
1 2 3 4 5 6 <10 spaces>
1 2 3 4 5 6 <10 spaces>
1 2 3 4 5 6 <10 spaces>
Regards,
Nithiyanandam

Hi,
Thanks for your reply, Could you please provide more details. Do you want me to concat an constant (empty value) with another constant (10 spaces) and map to the target field.
Also could you please let me know the other parameter which you have specfied in receiver file adapter (FCC), under the processing tab (file type and encoding), Content conversion parameters (i have used only (Records.fieldFixedLengths and Records.endSeparator)
Also have you specified any other module like localejbs/AF_Modules/MessageTransformBean (under processing sequence), if so please provide the details.
Regards,
Nithiyanandam

Similar Messages

  • Tab Delimited File Using Receiver FCC

    Hi Experts,
    I need to generate a Tab Delimited File Using Receiver FCC. I have achieved the same by copying the tab length from a notepad and used the same in name.fieldSeparator parameter.
    The other below mentioned values for name.fieldSeparator didnu2019t produce the expected result:
    name.fieldSeparator=u2019htu2019
    name.fieldSeparator=u2019\tu2019
    name.fieldSeparator=u2019 0x09u2019
    So just need to know if my approach for achieving this is fine or not.
    Thanking you in advance.
    Aditya.

    Verma,
    name.fieldSeparator=u2019 0x09u2019
    I see a space after the first comma. Try removing it and give a try.
    '0x09' with no spaces.
    Regards,
    ---Satish

  • Problem in Receiver FCC

    Hi Experts,
                       We need to do a file content conversion in the Receiver File Adapter for a fixed length file, format of which is like:
    MT_Message
      Shipment..........1..1
         field1
         field2
         field3
    Order.................1..1
         field1
         field2
         field3
      Tare..................0..unbounded
         field1
         field2
         field3
         Item...............0..unbounded
            field1
            field2
            field3
    occurrence of all field level elements are 0..1. Shipment, Order and Tare are at the same level and Item is under Tare, which can occur multiple times.
    I have tried using the normal File receiver FCC, the localejbs/AF_Modules/MessageTransformBean bean and the StrictXml2PlainBean but am not getting the desired output, where each segment is to occur on a separate line.
    Any help would be highly appreciated.
    Regards

    Hi Sarkar,
    I think the structure you are using is not correct. It should have one root node above all these Segment, Order nodes etc.
    Probably like this:
    MT_Message
    <Recordset>
    Shipment..........1..1
    field1
    field2
    field3
    Order.................1..1
    field1
    field2
    field3
    </Recordset>
    check this blog as well
    File Receiver with Content Conversion
    Sachin

  • Put Date Before Header Line in Receiver FCC

    Hi,
    I have to create a csv file with format :
    Date : dd/mm/yyyy to dd/mm/yyyy
    PRODUCT_CODE,NAME,ADDRESS
    123,ABC,xyz
    123,ABC,xyz
    123,ABC,xyz
    123,ABC,xyz
    123,ABC,xyz
    How should i achieve putting the date before header line?
    What should be my target structure format?
    What parameters to enter in receiver FCC?

    Hi,
    have you tried..
    Have you tried:
    (http://help.sap.com/saphelp_nw04/helpdata/en/e3/94007075cae04f930cc4c034e411e1/frameset.htm)
    ● NameA.enclosureSign
    Specify a string that acts as a text delimiter.
    Text enclosed by such delimiters is transferred to the target structure unchanged, although the default setting is to remove all text delimiters. Separators within such texts are ignored.
    This parameter is optional. The default setting is an empty value (no text delimiter).
    ● NameA.enclosureSignEnd
    If the text delimiters for the beginning and end of the text are different, specify the text delimiter for the end of the text here.
    If you do not make an entry here, the entry from NameA.enclosureSign is used.
    ● NameA.enclosureSignEscape
    Specify a string that replaces the text delimiter if it occurs within a text that it delimits.
    When the text is transferred the string is replaced by the value specified in NameA.enclosureSign .
    ● NameA.enclosureSignEndEscape
    Specify a string that replaces the text delimiter for the end of the text if it occurs within a text that it delimits.
    When the text is transferred the string is replaced by the value specified in NameA.enclosureSignEnd.
    ● NameA.enclosureConversion
    To remove the delimiter upon transfer, or to replace it with escape characters, enter YES. This is the default value.
    To transfer the characters unchanged enter NO.
    Note
    If you specify xml.enclosureSign=“ and xml.enclosureSignEsc=““, text enclosed in quotation marks is transferred unchanged and the quotation marks are removed.
    If the escape character for a quotation mark (““) occurs in the text itself, it is replaced by the quotation mark during the transfer.
    Thanks,
    Vijaya.

  • Receiver FCC Structure For Header and Trailer

    Hi Guys ,
    I need to go for receiver FCC for header and trailer  in PI .How the FCC in communication channel needs to be configured if I am taking a separate node for header and trailer in mapping .Output of the file should be as the file attached.
    Thanks.
    Regards.

    Hi,
    If you are using File communication channel as a reciver you can go with FCC.
    Use record set structure as : Header,detail,trailer.
    https://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm
    Otherwise if you are going for SFTP to create the file ... follow the Indrajit suggestion..
    Still facing any issue.. Please let us know..
    Thanks,
    Sreenivas...

  • Diplaying segment name in output file using receiver FCC

    Hi,
    we have a idoc to file scenario. we are using FCC at the receiver. the flat file generated should have the segment names before the values .
    for example, if the structure is  something like this
    <root tag>
       <serment1>
          field1
          field2
       <segment2>
            field1
            field2
       <segment2>
               field1
               field2
    the output should be in the below format
    segment1   field1value,field2value
    segment2   field1value,field2value
    segment2   field1value,field2value
    can some one guide me how to achieve the same. Also if the segment repeats, in the output also it shoukld appear
    Best Regards
    Deepika

    In mapping, output structure, create an extra field at the beginning and
    map that field to a constant value same as the source segment name.
    In Receiver FCC, use following configuration.
       Recordset Structure:      segment1,segment2(specify all segments seperated by comma)
      segment1.fieldSeparator :   , (it is comma)
      segment1.endSeparator :'nl'
      segment2.fieldSeparator :   ,
      segment2.endSeparator :'nl'
    specify the same fieldSeparator and endSeperator for the other segments also

  • Removing the empty line during Receiver FCC!

    Hi, Guys,
    I used file content conversion in receive FCC. My data type is like this:
    <TextFromSAP_DT>
    <FileName>
      <FileName>abc.txt</FileName>
    </FileName>
    <Record>
      <TEXT>dasfafaf</TEXT>
    </Record>
    <Record>
      <TEXT>qqqqqqqq</TEXT>
    </Record>
    <Record>
      <TEXT>fgfffff</TEXT>
    </Record>
    </TextFromSAP_DT>
    I need to get file name from <FileName> and output a flat file with the value in <TEXT>. But I always got an empty line at the file beginning. And I tried to move <FileName> to the end. And I got an empty line at the file end. My custom said they are having trouble to read the file with the empty line no matter it is in the beginning or end.
    I followed sample as link below but does not work. 
    https://wiki.sdn.sap.com/wiki/display/profile/2007/07/30/Removing%20the%20empty%20line%20during%20Receiver%20FCC!
    Does any body can give a help?
    Thanks a lot!
    Meiying
    Edited by: Meiying Yang on Aug 14, 2009 11:16 PM

    Hi Yang,
    You create the value udf GetFileName with one input value say a. Add this code:
    Imports: java.*;
    Add this code:
       //write your code here
    DynamicConfiguration conf = (DynamicConfiguration)container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
    DynamicConfigurationKey key = DynamicConfigurationKey.create("http:" + "/" + "/" + "sap.com/xi/XI/System/File", "FileName");
    conf.put(key, a);
    return "";
    Map like this:
    FileName --> GetFileName(udf) --> target_mt
    Map other fields like:
    Record --> Record
    TEXT ---> TEXT
    Save it and activate it. When you test in mapping you will get an error so dont worry. I go the error like:
    RuntimeException in Message-Mapping transformation: Runtime exception during processing target field mapping /ns0:Target_MT. The message is: Exception:[java.lang.NullPointerException] in class com.sap.xi.tf._TestFileName_ method file1$[abc.txt, com.sap.aii.mappingtool.tf3.rt.Context@32dcebf1]
    Dont worry about this activate and do the rest of the configuration.
    In your receiver communication channel for file name put as FileName and check the file name in adapter specific message attributes. Then test it and it should work and you will get the file with file name abc.txt. I tested the whole end to end scenario and I am getting the file name abc.txt and the output what you want. If you still could not get it send me a m ail to my i d from my business card. I will send you the screen shots.
    Regards,
    ---Satish

  • Receiver FCC: Ignore first field

    Hi Experts,
    Is it possible to ignore only the first field in receiver fcc?
    Thanks,
    Vishal

    Hi Vishal,
    Always the best option is in this case to create a new segment and use it for varibale substituion and trim it in communication channel
    else
    Pass the value to a segment and you can use that in communication channel.
    Regards,
    ---Satish

  • Receiver FCC: endSeparator now working

    Hi,
    I am having an issue while doing file content conversion at receiver side.
    My XML structure is as below:
    <ROOT>
    <MASTER>
       <DATA1>data1</DATA1>
       <DATA2>data2</DATA2>
    </MASTER>
    <MASTER_DETAIL>
       <DATA3>data3</DATA3>
       <DATA4>data4</DATA4>
    </MASTER_DETAIL>
    <MASTER>
       <DATA1>dataA</DATA1>
       <DATA2>dataB </DATA2>
    </MASTER>
    <MASTER_DETAIL>
       <DATA3>dataC</DATA3>
       <DATA4>dataD</DATA4>
    </MASTER_DETAIL>
    </ROOT>
    Now entries in Receiver FCC were
    ROOT,MASTER,MASTER_DETAIL
    MASTER.fieldSeparator=|
    MASTER_DETAIL.fieldSeparator=|
    MASTER.endSeparator='nl'
    MASTER_DETAIL.endSeparator='nl'
    ROOT.endSeparator='nl'
    ROOT.fieldSeparator='nl'
    Output got:
    data1|data2|data3|data4
    dataA|dataB|dataC|dataD
    Expected output :
    data1|data2
    data3|data4
    dataA|dataB
    dataC|dataD
    Please let me know what to specify?
    Regards, Anirudh
    Edited by: Anirudh Vyas on Sep 17, 2008 3:05 PM

    Problem solved!
    I was supposed to do 2 stage mapping to map the parent and child segment of Idoc to Parent and child XML structure and then do mapping to have parent and child nodes as siblings of ROOT.
    As below
    MAP1: Idoc to XML1
    MAP2: XML1 TO XML2
    XML1:
    <ROOT> *
    <MASTER>
    <DATA1>...</DATA1
    <MASTER_DETAIL>*
    <DATA3>...</DATA3>
    </MASTER_DETAIL>
    </MASTER>
    </ROOT>
    XML2:
    <ROOT>*
    <MASTER>
    <DATA1>...</DATA1>
    </MASTER>
    <MASTER_DETAIL>
    <DATA3>...</DATA3>
    </MASTER_DETAIL>
    </ROOT>
    I was doing content conversion with XML1.
    I didn't add MAP2 in interface mapping.
    Now my output is as expected.
    Thank you all for your help.
    regards,
    Anirudh.

  • Error in Receiver FCC: Unknown structure ... found in document

    Hi Experts,
    I have a problem with the Receiver File Adapter. I want to use Content Conversion to generate a plain file.
    Input to receiver file adapter:
    <?xml version="1.0" encoding="utf-8" ?>
    <PlainFile>
      <filename>filename.txt</filename>
      <line>Line 1</line>
      <line>Line 2</line>
    </PlainFile>
    Wanted result: a file filename.txt with this content:
    Line 1
    Line 2
    FCC settings:
    RecordSet Structure: line, filename
    line.fieldSeparator:'nl'
    filename.fieldFixedLengths:0
    filename.fixedLengthTooShortHandling:Cut
    Problem is: the adapter throws error "Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'PlainFile' found in document'"
    If I use:
    RecordSet Structure: PlainFile, line, filename
    and add:
    PlainFile.fieldSeparator:'nl'
    ... the lines are printed, but also the unwanted filename. The XML input results from an 1:n mapping, therefore I want to set different filenames by variable substitution from the payload.
    Many thanks for your help,
    Ralf

    Since you want to the filename to be sent in the payload, check out the below Variable Substitution Method. This information is available in help.sap.com.
    Advanced Tab Page
    Variable Substitution (Target Directory/File Name Scheme)
    If you set the Enable indicator, you can enter variables for the Target Directory and File Name Scheme. Enter the names of the variables and references in the table.
    &#9679;      Enter each variable that you reference in the Target Directory and File Name Scheme fields without the surrounding percentage sign under Name of Variables in the table.
    The variables can refer to attributes of the message header or elements of the message payload.
    &#9675;       If the variables are to refer to an attribute of the message header, add the prefix message: to the name of the variable under Reference. You can specify the following attributes of the message header:
    sender_party, sender_service, receiver_party, receiver_service, interface_name, interface_namespace,
    message_id (message ID with hyphens, for example 9fbe1ff1-9a0d-11d9-8665-cbf10a126331)
    message_id_hex (message ID in hexadecimal format, for example 9fbe1ff19a0d11d98665cbf10a126331)
    For example, if you want to specify the interface name from the message header in the target directory or in the file name scheme, enter message:interface_name as the reference.
    Note
    If one of the message attributes contains characters that are not permitted in a file name, for example \, /, :, *, ?, ", <, >, |, then these characters are replaced by an underscore ("_").
    &#9675;       If the variable refers to an element in XML schema, add the prefix payload: to the information under Reference. The reference then comprises a pseudo path description in the form of a comma-separated list with the schema namea,na,nameb,nb,....
    namea,nameb,... corresponds to the element name and na,nb,... corresponds to the occurrence of the element name at the respective level in the document.
    The description begins at the root of the document and ends at the respective element.
    Example
    To reference the element that is in bold in the example, the following expression is used: payload:root,1,e1,1,e2,2
    The parser searches for the first occurrence of the root element at the first level. It then searches for the first occurrence of e1 at the second level and for the second occurrence of e2 at the third level. The content of the last element (“Example Value”) is set as the value for a specified variable.
    <?xml version="1.0" encoding="UTF-8" ?>
    <root>
      <dummy>
         <e1>
            <e2>Data_1</e2>
            <f/>
            <g attr="abc">text</g>
            <e2>Data_2</e2>
         </e1>
      </dummy>
      <e1>
         <e2>illegal/value</e2>
         <f/>
         <g attr="abc">text</g>
         <e2 attr="fghij">Example Value</e2>
      </e1>
    </root>

  • JMS Receiver FCC Problem After Upgraded from SP19 to SP22 in XI3.0

    Hello,
    I am facing a problem in my Receiver JMS adapter in FCC just after the upgrading it from SP19 to SP22 in XI 3.0 by our basis consultant. Before that everything was working perfect in DEV.
    I am getting the below mentioned error in CC monitoring.
    > MP: Exception caught with cause com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: 'java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.NullPointerException''; nested exception caused by: java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.NullPointerException'
    This problem is happening in other scenario too in our DEV system.
    But at the same time since we have not applied any upgrade in QA therefore same scenario is working fine.
    Regards,
    Sarvesh

    Ok Friends...
    I got the solution from SAP.. there was a problem in the SP22 for XI 3.0 which I donloaded from Service Market Place. Now I have applied the correct SP22 to my system and now it is working fine...
    I hope this may help you...
    Regards,
    Sarvesh

  • Sender and Receiver FCC

    Hi All,
    At sender side i have structure as
    <Recordset>       1--1
      <header>           0--1
        <id>
      </header>
      <details>           1---unbound
        <nameA>
        <nameB>
      </details>
      </recordset>
    i have used FCC at sender side but not able to create header in my message.
    Then at Receiver side i m using FCC for generating csv file. File is created successfully but i m not able to put heading to each column.
    Please guide me to solve this problem.
    Regards,
    Manisha

    Manisha Dahatonde wrote:
    > Hi All,
    >
    > At sender side i have structure as
    >
    > <Recordset>       1--1
    >   <header>           0--1
    >     <id>
    >   </header>
    >   <details>           1---unbound
    >     <nameA>
    >     <nameB>
    >   </details>
    >   </recordset>
    >
    > i have used FCC at sender side but not able to create header in my message.
    what is the header that you want? what is the FCC you have given?
    > Then at Receiver side i m using FCC for generating csv file. File is created successfully but i m not able to put heading to each column.
    >
    > Please guide me to solve this problem.
    >
    > Regards,
    > Manisha
    use the option
    NameA.addHeaderLine
    Specify whether the text file will have a header line with column names. The following values are permitted:
    ·        0 u2013 No header line
    ·        1 u2013 Header line with column names from the XML document
    ·        2 u2013 As for 1, followed by a blank line
    ·        3 u2013 Header line is stored as NameA.headerLine in the configuration and is applied
    ·        4 u2013 As for 3, followed by a blank line
    http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm

  • Query on Receiver FCC for nested structure

    Hi Friends,
    I want to  configure the Receiver side FCC for the below nested structure.
    Can you guide me how can i achicve it? or its not possible for nested structure?
    Seg100,Seg200.Seg300 and Seg400 are nested one below the other.
    <?xml version="1.0" encoding="UTF-8" ?>
    - <ns0:Test xmlns:ns0="http://hello.com">
    --<Seg100>
    --<field1>0000564.30</field1>
    --<field2>KG</field2>
    --<Seg200>
    ---<field3>1070</field3>
    ---<Seg300>
    <field4>5</field4>
    <Seg400>
    <field4>5</field4>
    </Seg400>
    ---</Seg300>
    --</Seg200>
    -</Seg100>
    </ns0:Test>
    Regards
    Venkatesh

    Hi,
      For nested structure we cont do the File content conversion.
      so that we need to convert it a flat structure in the mapping level and then we can go for FCC.
    Regards,
    Prakasu

  • Reg:Receiver FCC

    Hi ..
       Can you plese help in writing the Conversion Parameters for the below structure..
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:MT_FCC xmlns:ns0="http://krft.com/FCC">
       <Header>
          <Name/>
          <No/>
          <Location/>
       </Header>
       <Data>
          <Node1>
             <Name/>
             <CompanyId/>
             <CompanyLocation/>
          </Node1>
          <Node2>
             <Name/>
             <Department/>
             <Manager/>
          </Node2>
       </Data>
       <Trailer>
          <Name/>
          <Street/>
          <City/>
       </Trailer>
    </ns0:MT_FCC>
    In the above structure the field Data is repeted n number of times.
    Thanks,
    Leela

    /people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
    /people/shabarish.vijayakumar/blog/2007/08/03/file-adapter-receiver--are-we-really-sure-about-the-concepts
    intermediate structure solution /people/karthiknarayan.kesavan2/blog/2007/08/22/file-content-conversion-for-multi-hierarchical-structure

  • Problem with Receiver FCC

    Hi,
    Our receiver file has the following structure:
    <Record>
      <header>
         <head1>
         <head2>
         <Item>
              <item1>
              <item2>
         </Item>
      <header>
    </Record>
    I have defined my Receiver file adapter as:
    ReceordsetStructure: Header,Item
    header.fieldFixedLengths
    Item.fieldFixedLengths
    item.fieldSeparator
    item.endSeparator
    header.fieldSeparator
    header.endSeparator
    But when I test this it is throwing an error in Receiver CC saying that
    Error occurred while connecting to the FTP server :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 '8')', probably configuration error in file adapter (XML parser error)'
    The value '8' here is the first element in the Item node.
    Idon't know why it is taking only the header lelements and throwing error for Item node.
    can somebody throw a light on this.
    Thanks in advance
    With Regards
    Deepika.

    Hi Carme,
    Thanks for the reply.
    As you said with this it will work fine but my target file should be a fixed length file, means I should get empty spces if the data in the field is not matching with length of the field.
    My o/p data is as below:
    @12@23@56@89@45@12@65@98@458@87@12
    But I need it in this format:
    @      12@23@      56@    89@   45@12@    65@   98@   458@87@  12
    The empty spaces are getting trimmed if  fixed lengths are not used.
    Also I need header and item in seperate lines.
    With Regards
    Deepika.

Maybe you are looking for

  • Why doesn't my itunes library show all my music?

    It only shows recent purchases and nowhere near what I've got on my ipod. This means there's hardly any music I can sync to my iphone.

  • Does PSE 12 camera raw support my Fuji X-T1 camera?

    I get the following error message when trying to view a camera raw file from my Fuji X-T1 in PSE 12: "Could not complete your request because the file appears to be from a camera model which is not supported by the installed version of camera raw." T

  • My hard-drive is filling up

    I have a MAcBook Pro, with 320GB hard-drive. Checking my remaining disk-space, I notice that I have only 75GB free. According to "About my Mac" I have 120GB of Photos and 58 GB of movies, but using OmniDiskSweeper it only finds 17.5 Gb of Photos and

  • Repetritive manufacturing

    dear pp specialist in backflush(mfbf) in repetitive manufacturing system showing message"Argument SM not contained in table T437D" can any body explain why system showing this message. how we can resolve this message.

  • Problems after install driv

    Hi guys it's my first time here, soo i'm sorry if my english isn't the best i just finished to buy my creative zen v 2gb. I come home and installed all the dri'ves and all the CD stuff... after that when the installion asked to connect the device i c