DMEE output -> Same codepage for two formats in the settings but different output

[Former Member]

Dear Ladies and Gentlemen,

we have created two payment methods. Both are for our company in China. For both methods a file in .txt format needs to be created which is then uploaded to the banks homepage. The bank has the requirement that the txt* file has to be an UTF-8.

One payment method is domestic payments and carries chinese characters. In OBPM3 we have set the codepage "4110" as a codepage which stands for UTF-8. And it works: The file that is being created is shown as UTF-8.

The other payment method is for payments in foreign curreny and contains no chinese characters (-> only latin characters). Here we have also set the "4110" as acodepage. But the output is in ANSI!!!

And it becomes even more weird: When I take a look into the table REGUT even the files with the right output ( =UTF-8) have the entry "4103" (=UTF-16).

Any ideas?

Thank`s in advance

[cgilberg]

Hello Imer,

do you maybe have a user exit in the foreign payments DME tree which forces the change in output format, overriding the configuration settings? Other place would be a different setting/behaviour in an event module in OBPM3.

Regards,

Christoph

[Former Member]

No. We only have two exits implemented that create two different fields (picking some entries from the  ADRC table) in the domestic payments file. But the domestic file was even working correctly (=> correctly in this regard means the output was in UTF-8) before we implemented the exits.

Both files have exactly the same setings, even in OBPM3. Any other ideas maybe?