Solution : https://service.sap.com/sap/support/notes/1390229 (SAP Service marketplace login required)
Summary :
SAP Note clarifies the requirements for a correct UNICODE conversion specifically for systems utilizing double-byte characters in payment run identifications. It mainly focuses on payment programs SAPF110S and SAPF111S and their related tables and fields. Critical insights include the maintenance of payment process status during conversion, the handling of report RFZALI20 variants, and issues related to the fields REGUH-EMPFG and REGUP-EMPFG which may contain double-byte characters. Requirements for successful conversion include specific steps that must be completed or uninitiated before conversion, and the need to re-save certain settings post-conversion.
Key words :
report rfzali20 converted correctly, problem-free unicode conversion, current support package, unstructured character string, double-byte characters, found1369349 f111 parameters, -character-type values, existing report variants, payment run identifications, payment run identification
Related Notes :
| 1583568 | RFZALI20: Unicode conversion for report variants |
| 1381270 | RFZALI20 no data after UNICODE conversion |
| 1370861 | F110 ... Incorrect payment runs in F4 help |
| 1369349 | F111 Parameters of payment runs are not found |
| 1357527 | F110 parameters of payment runs are not found |
| 1319517 | Unicode Collection Note |
| 1303172 | F110: Existing payment runs are not displayed |