Solution : https://service.sap.com/sap/support/notes/857506 (SAP Service marketplace login required)
Summary :
In the context of SAP system behavior, an issue occurs where STRG fields, such as those in SPROXHDR and SPROXDAT, end with a halved number of x'00' bytes relative to their total length. This erroneous condition arises during the EXPORT process in UNICODE systems using R3load with SAPDB/MaxDB, where bytes and characters counts are mismatched, leading to doubled length allocation. Resultant problems include interface generation failures in SE80 and importation issues in transaction SE16. The ABAP report RSSDBSTRG, provided in Support Package 6.40 Basis SP14, rectifies this by verifying and correcting the data record alignment. Ensure SAPDB_FIX_STRG_LENGTH and the necessary patches are applied for resolution.
Key words :
internal database procedure sapdb_fix_strg_length, previously created export, sap service marketplace, sapdb/maxdb export, virtual interface sxidal_flightseat_avail_check, abap report rssdbstrg, 20 patch level lower, 40 patch level lower, 1930or sapdb dbsl 6, 40 sapdb dbsl-libs
Related Notes :
| 850827 | R3load: Length of STRING fields is incorrect (Unicode) |
| 19466 | Downloading SAP kernel patches |
| 13719 | Preliminary transports to customers (note for customers) |