cancel
Showing results for 
Search instead for 
Did you mean: 

UNICODE ERRORS

Former Member
0 Kudos

Hi

Create a PO (Process Purchase Order) and Order it . It goes to errors

.In Monitors you can see that it has failed due to UNICODE

ERRORS

Reason--

We have custom fields added to PO in R/3 standard sap structure

CI_EKKODB

The Standard SAP Code is falling when we have some date or integer

field as custom fields already added in CI_EKKODB in R/3.

But we are passing only character fields from SRM still it is

considering the time and integer customer fields of R/3 PO which we

have not defined in SRM.

Any Advice ???

SEKHAR

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

to some extent answered

ashwin_mundkur
Advisor
Advisor
0 Kudos

Hi Sekhar,

Could you please check note 944534? This reverts the changes of note 850082 .

Can you check the note 945335 (consulting note) for this issue. This note replaces the changes proposed by note 850082, which in later Plug-in (PI) support packages will be reversed (through note 944534).

The purpose of this note is to extend the customer fields allowed to be transferred to the backend to types:

C, N,D, T and P, for extended classic scenario. This can only be achieved by modification mentioned in the note 945335. Please do the changes manually. Also, its not a good idea to use customer fields of type 'P'.

thanks,

Ashwin

Do reward points for useful suggestions