Download / upload table data
With this function you can download and upload table data. For example this could be useful when you have to copy data from one system / client to another one.
For the "Download" option a "where condition" can be specified to reduce the data according selection criteria.
When choosing the "Upload" option you can decide whether already existing entries in the table should be overwritten with data (having the same key fields) of the data file.
The small "i" button right from the input field for the table offers a list of the table fields. A doubleclick on a line transfers the field name and a value pattern to the "where condition" in the dialog form.
You can also enter the field names manually. The specified field names are checked against the SAP data dictionary.
For offering as much flexibility as possible the input in the "where condition" is not syntactically checked.
Please enter the table and especially the "where condition" carefully - otherwise it could be that more data will be deleted than intended! In that case it could be that the SAP application will not work properly anymore.
Download and upload will be done via a file on your computer. As this requires the access of the SAP system to your frontend a SAPGUI has to be available and the user in the connection has to have dialog capabilities (type "A" or "S").
You can choose between different file types:
- Using filetype 'ASC' (ASCII) will export / import the data via a file where the data is represented in clear text, including conversion exits and a character conversion dependent of the character sets from the SAP system and the PC. If you have to modify the data between export and import, you can do this via a text editor. This option works only in case that for all fields in the table a "clear text" representation is possible. For example, this is not the case for fields of type "RAW". Table with those fields must not be handled using this file type!
- Using filetype 'BIN' (binary) will download / upload the data via a file where the data is stored in binary form without any character conversion. Assuming that the table used for download and upload have exactly the same structure and the systems used for download and upload have the same character set and endianess, the operation with this filetype works reliable.
- Using filetype 'DAT' (data) is similar to 'ASC'. The data is transferred column by column as text without processing conversion exits. The single columns are separated by tab characters. This format is suitable when the data is to be uploaded again and in source and target system the table structure is the same, but the 'BIN' format can not be used due to different character set and/or endianess.
Please enter the table and (if necessary) the "where condition". The small "i" button right from the input field for the table offers a list of the table fields.
The "where condition" is optional. In case you leave it empty the export will be done for every record of the specified client in the table.
In the "Preview" text area you can see the select statement that is built from your input. Have a look at it and check if it would do what you intended. Some basic knowledge about SQL and it's implementation in the ABAP programming language is strongly recommended!
If the table is not client-dependent, the "client specified" clause of the update statement must be avoided. For this enter the same client as used in the connection.
The "Upload" function is highly critical from security and data consistency point of view. Handle it with care and know exactly what you do, please!
It is also strongly recommended that you do a test in a test / quality system to ensure that the function works in the way you want to!
After the execution you will see a short log in a SAPGUI window with information about the number of exported / imported records.
If this short log does not come up something went wrong! The "upload" function is more sensitive than the "download" function. In case of an upload errors might occurr due to a not fitting data structure of the file to be uploaded or corrupted data in the file. Have a look at shortdumps (transaction ST22) in this case, please.
In case you upload data of a table containing a logical system name from another system / client: consider that for adjusting logical system names a BDLS run for the uploaded table might be necessary.
|
