Refer to SAP Note 1319517 10. Is it possible to transport between a non-Unicode and a Unicode system?

In general, it is possible to transport between non-Unicode and Un icode systems. Restrictions apply for characters or language keys not supported in the non-Unicode system and in case of an MDMP system on the non-Unicode side. Transports between SAP systems on releases 4.6C or lower and Unicode systems ar e not possible. For detailed information, refer to SAP Notes 638357 and 330267. Release-dependent and Basis-Support-Package-dependent Unicode Conversion Guide and SAP Note 548016 (See also notes 551344, 1051576, 928729 or 959698). 20. What should be tested after the Unicode conversion? We recommend a full regression test with focus on language-specifi c texts (texts with special characters) comparable to the tests after an upgrade . Customer experiences do show that SAP standard programs work properly in most cases; therefore, the main testing areas should be tests on: a) Customer-specific programs b) Modified SAP standard programs c) Third-party solutions d) All interfaces

Note 1319517 - Unicode Collection Note Note 1322715 - Unicode FAQs http://scn.sap.com/docs/DOC-8616 se16 TCPDB 548016 Conversion to Unicode / Unicode System Copy Note 1051576 - Conversion of Single Code Page Systems to Unicode Troubleshooting Check SAP Note 765475. 1. Runtime Errors Date and Time SYSTEM_NO_ROLL 12.03.2007 08:44:27.

Solutions : It looks like the transaction used by the reporter is requesting for more memory.SYSTEM_NO_ROLL The dump analysis suggesst to change the following parameters. ztta/roll_area ztta/roll_extension abap/heap_area_total abap/heap_area_dia

em/initial_size_MB = 4092 ztta/roll_area = 3000320 ztta/roll_extension = 2000683008 abap/heap_area_total = 2100297728 abap/heap_area_nondia = 10485760 abap/heap_area_dia = 10485760