Skip to Content

When reading from a flat file source or loading into flat files, delimiters’ specification including text, column and row delimiters are essential to ensure that the data is not corrupted due to lack of delimiters. One such example is the text delimiter. The absence of text delimiter can cause the data read to be interrupted or result in error on cases where the data in a given field entry contains multiple lines thus having row delimiter in a given cell. The screenshots below provide an illustration of using the text delimiter in flat file.

The illustration in Fig 1 below shows that the absence of the text delimiter in the file format causes the reading of the flat file resulted in error.

fig 3.jpgFig 1

The illustration in Fig 2 below shows that after introducing a text delimiter in the file format

Fig 4.jpg Fig 2

There are several scenarios other than the one illustrated above where the delimiter setting in the flat file format can help in ETL involving flat file data from legacy systems or flat file targets.

To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Former Member



    I am facing the same issue, actually client doesn’t have any idea about his data.

    How should we handle when a delimiter is present in the source data (Flat File) through BODS.


    We are on SAP BW 7.4 & BODS 4.2.


    Any solution on same…? Its very argent.

    Thanks in advance 🙂

        1. Raghunathan Balasubramanian Post author

          Hi Swati,

          If you do not want a delimiter you can choose fixed width as the option under Type as shown below. This might serve the purpose if you are expecting to have the entire length of the column displayed without any delimiters between them.

          Fig 1.jpg

          Do let me know if you have any further queries.

          kind regards



Leave a Reply