Page tree
Skip to end of metadata
Go to start of metadata

CSV File on Application Server


Metadata retrieval: SUPPORTED Extraction Strategy: INDUVIDUAL SELECTION AND KEY BASED SELECTION Special Permissions: NONE


This source type was introduced with Solution Manager 7.2. You use it for data stored in comma separated files (CSV).


The following data is required:

Host nameSpecify the name of the application server
File PathSpecify the path on the SAP Solution Manager application server under which the CSV file containing the data to be compared is saved.
File NameSpecify the name of the CSV file. In no file name but only a path name is supplied, all files in the given path are processed. Moreover, the file name allows wild-cards *, +, $TODAY and $YESTERDAY. In case multiple files are selected, data from all these files is processed together.
Created from, Created to

Enter a time from when and a time until when files are considered. The following key words are possible for entering the times:

    • $TIMES – timestamp now with offset in seconds (example: $TIMES-10)
    • $TIMEM – timestamp now with offset in minutes (example: $TIMEM-30)
    • $TIMEH – timestamp now with offset in hours (example: $TIMEH-12
    • $TIMED – timestamp now with offset in days (example: $TIMED-1)
Header LineSpecify if the CSV files has a header line
Field SeperatorSpecify the field seperator of the CSV file


Enter any table name and the field names from the header line or any field names in case of no header line. There is no value help for table and field names, but you have to enter them manually.

CSV files supported

The source type supports different kinds of CSV files:

  • CSV files with or without header lines: The header line is not compared but determines the order how the fields are mapped.
  • CSV files with different field separators: A comma is used as default field separator, but it is possible to enter different field separators.
  • CSV files in different formats: The source type checks automatically if the file is in UTF-8 format. In UTF-8 format, a possible byte order mark (BOM) is skipped and not included in the comparison. In a non-Unicode system, the file is read without being converted. In a Unicode system, if the file is not in UTF-8 format, the characters of the file are handled in accordance with the non-Unicode code page that would be assigned at read time in a non-Unicode system, in accordance with the entry in the database table TCP0C of the current text entvironment.

  • No labels