Component : Logistics -

Solution : https://service.sap.com/sap/support/notes/1448532 (SAP Service marketplace login required)

Summary :
After converting to Unicode, runtime error CONVT_NO_NUMBER, resulting from the misassignment of variables during variant data retrieval in transactions (CN or CNS), arises due to variants stored in non-Unicode in the previous system format. The solution involves the implementation of manual corrections via the newly introduced report RCN_SAVE_VARIANT and transaction SNOTE. Followed by executing RCN_SAVE_VARIANT with specific parameters for variant adjustment. This process exclusively targets logistic information system reports of the project system, excluding certain RCN* reports. Ensure to execute the manual pre-implementation steps for each relevant system prior to importing the correction.

Key words :
software component   sap_appl                      sap application, manual pre-implementation step manually, konvertiere variante nach unicode, manual pre-implement, executable program application, classic overview transactions, runtime error convt_no_number, exception cx_sy_conversion_no_number occur, logistic information system, projekt info system

Related Notes :

1536359
1478263	PSIS: dumps loading variants; servers w/ little & big endian
1319517	Unicode Collection Note
1310720	Collection Note for Unicode Systems with different endianess