Hi
We upgraded to a Unicode system and we have only English language and codepage 4103 installed. Previously the codepage was 1100.
If we call existing BAPIs, the calls are 100% okay, but as soon as an ABAPer makes a change to the BAPI, that BAPI is no longer found by jco?
One of the anomalies is that the Connection attributes from SAP sends back non-unicode attributes.. for instance the PARTNER_BYTES_PER_CHAR returned is still 1 instead of the Unicode 2. And the PARTNER_CODEPAGE received back is still the previous non-unicode value of 1100 instead of the new codepage of 4103? Even if we force the connectProperties to 4103
connectProperties.setProperty(DestinationDataProvider.JCO_CODEPAGE,"4103");
Please let me know if you have a solution or suggestion or require more input for analyses.
Thank you and best regards,
Adrian