Solution : https://service.sap.com/sap/support/notes/1255556 (SAP Service marketplace login required)
Summary :
When preparing for Unicode conversion either in an MDMP system or a Single Codepage System, issues arise related to DBTABLOG such as unassignable language in vocabulary and corrupted data in DBTABLOG-LOGKEY post-conversion. DBTABLOG functions as a container table storing structured data. Proper handling prior to Unicode conversion involves creating necessary container control information. This information should be verified or added via SE38 executing UMG_INSERT_CONTAINER. If discrepancies in package level hinder the acquisition of this information, manual addition might be required, ensuring compatibility by considering alternative types and requisite R3load patch levels. Efforts should also include resetting and re-scanning in SPUMG post corrections.
Key words :
owner tablename container type underly, tabname eno additional action, basis support package level, ref logtypes dbtablog logkey, unicode conversion takes place, create container control information, execute report umg_insert_container, called container table, container control information, fields dbtablog-logkey
Related Notes :
| 1319517 | Unicode Collection Note |