Files as Destinations
You can select flat files in CSV format as open hub destinations.
The only file format that is supported for extraction to flat files is CSV. A control file with information about the metadata is also generated. You can either save the file on the application server or in a local directory.

If you save the file locally, the file size must not exceed 500 MB. When transferring mass data, you should save the file on the application server.

With User Account Control (UAC) in Windows 7 and Windows Vista, it can seem as though data is written to a local directory, but actually a file is not created. You therefore should not use a directory that authorizations are restricted for.
If you want to write the data to a BI application server, you have two ways of setting the file name:
● File name:
The file name is made up of the name of the HOME directory (DIR_HOME in transaction AL11), the technical name for the InfoSpoke and the filename extension CSV. You cannot change this name.
● Logical file name:
You can use
input help to select a logical file name that you have already defined in
Customizing. Create a logical path and assign a logical file name to it (see
Defining
Logical Path and File Names).

When defining a logical file name, you can also specify a data format. The InfoSpoke ignores this specification however. Extraction always takes place in CSV format.
A logical file name can be made up of fixed path information, but can also contain variables like calendar day and time. Logical file names can be transported.
If you save the file in a local directory, you cannot change the file name. It is made up of the technical name of the InfoSpoke and the filename extension .CSV. The associated control file also has the prefix S_.