LOADING A FLAT FILE INTO A STANDARD DATASTORE OBJECT

See more in our hbites Advanced DSO

Create a source system of type file, and a datasource having structure like the fields in the file to be loaded.
The main difference between loading from an SAP source system and an external system using flat files is the DataSource.

For an SAP source system, you define the DataSource in the source system and replicate it into SAP BW/4HANA.

If you load from an external system using flat files you define the DataSource in SAP BW/4HANA.

You have the option of loading data from any workstation into SAP BW.

For performance reasons, however, you should store the data on an application server and load it from there into SAP BW. This means that you can also load the data in the background.

If you want to load a large amount of transaction data into SAP BW from a flat file, and you can specify the file type of the flat file. Create the flat file as an ASCII file. From a performance point of view, loading data from an ASCII file is the most cost-effective method.

Loading from a CSV file takes longer because, in this case, the separator characters and escape characters must be sent and interpreted. In some circumstances, however, generating an ASCII file may involve more effort.

Text-type files contain only characters that can be displayed and read as text.

The defined field length in the file must be the same as the length of the assigned field in SAP BW/4HANA.

The following list gives some of the features of the SAP BW file adapter and file based DataSources:

● Automatic field proposals at design time
● Automated conversion of external data types and formats provided
● Preview option allows a double check of file parsing
● Fields can be selected as Not Transferred

The Proposal tab reads the header row and proposes field names and types based on what it finds. These proposed field names, sizes, and types can be changed on the second most important tab, the Fields tab.

The Internal/External format toggle tells the program if the data being sent is in the format that the user sees in an application or is it in the format stored on the database. An example might be the fiscal period 01.1999 (external) versus the period 1999001 (internal).

You must also correct the data type if system proposal is not correct.
You can use preview tab to see if the data is coming properly or not after you activate the DataSource.

Create transformation and DTP. Execute the DTP to load the data from file to adso.

See more in our hbites Advanced DSO