Skip to Content
Aug 04, 2008 at 02:36 PM

Files corrupted after upgrade to ECC and unicode change



we're using BSP element "file upload" to upload word documents. By function module SCMS_XSTRING_TO_BINARY the content of the upload was converted to binary. With FMs SO_OBJECT_INSERT and BINARY_RELATION_CREATE_COMMIT the document was uploaded to SAP and linked to a business object (purchase requisition in our case). This worked fine while running on WAS 6.40 and R/3 4.6C.

After the release change to ECC 6.0 (Basis 7.0, currently SP 14) the web application now directly runs on the ECC server and we've performed a unicode conversion. Now, the upload via web application still works, however, when trying to open the document out of the SAP GUI, the document cannot be opened since the file is corrupt. However, no exceptions are thrown during upload. It seems as if the format used for storing the data in the SAP database has changed.

Any experiences on a similar issue?

Many thanks & regards


Edited by: Wolfgang Mayer on Aug 5, 2008 1:58 PM


Update/Solution: Function module SCMS_XSTRING_TO_BINARY has to be called with a table capable of retrieving binary data, e.g. type SOLIX. Before unicode conversion, type SOLI was sufficient. FM SO_DOCUMENT_INSERT_API1 is capable of creating a document using binary data (instead of FM SO_OBJECT_INSERT).