Selecting Files As Destinations

You can write data from the BW system to a file via the open hub destination.

1. Choose File as the type of destination. The file formats CSV, ASCII, and XML are supported during extraction to files. A control file with information about the metadata is also generated.
2. You can save the file either on the application server or in a local directory. For technical reasons, you can only select file format XML for files on the application server. If the file is located on the application server, you can schedule extraction in the background.
   Caution

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

   The User Account Control (UAC) in Windows 7 and Windows Vista can create the impression that data is written to a local directory, but no files are actually created. Do not use a directory with restricted authorization.

3. If you want to write the data to an application server from the BW system, you have two options for the file name:
   • File name: The file name is made up of the technical name of the open hub destination and the extension .CSV, .TXT or .XML. 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. To do this, you create a logical path and assign a logical file name to it. More information: Defining the Logical Path Name and File Name

     A logical file name can be made up of fixed path information and variables - such as calendar day and time. Logical file names can be transported.

4. If you save the file in a local directory, you cannot change the name of the file. It is made up of the technical name of the open hub destination and the extension .CSV, .TXT or .XML. The associated control file also has the prefix S_.
5. If you select data format XML, you can choose the following formats:
   • SAP Standard XML ist the default SAP XML format. It is optimized for data exchange between SAP and external systems in both directions.
   • SAP Binary Protocol XML is an internal binary SAP variant of asXML. It can only be used in the SAP system environment. With binary and structure compression however, it provides considerable performance and storage advantages compared to other XML options.

     The XML is generated using the CALL TRANSACTION command: http://ld9460.wdf.sap.corp:50000/sap/public/bc/abap/docu?sap-language=EN&sap-client=000&format=STANDARD&object=ABENABAP_XML_TRAFOS&tree=X

     Further information about asXML: d031428917434934.xml

6. You can select Default Setting or Direct Entry as the string setting. If you select Default Setting, the system code page is used. If you select Direct Entry, you can specify your own code page.