Unicode problem

[Former Member]

Hi.

Recently, Our company finished version-up project from 4.6C to ECC 6.0.

We solved almost problem. But, we can find same unicode problem contineously when we run standard program. For example, some infotype read(0009) or standard program(pa03) run.

I already looked after question and answer on this site. So, I knew how to solve

standard unicode problem (Unicode-compatible problem. Posted: Sep 19, 2007 12:23 PM)

Our problem is we found too many cases like that.

Until now,

-/1PAPA/FEAT110VDSK1

-/1PAPA/FEAT110PINCH

-/1PAPA/FEAT000P0003

-/1PAPA/FEAT000LDAYW

-/1PAPA/FEAT110NUMKR

-/1PAPA/FEAT110TIMMO

-/1PAPA/FEAT000P2011

-/1PAPA/FEAT110VTART

-/1PAPA/FEAT000DTAEL

-/1PAPA/FEAT000BIMAP

-/1PAPA/FEAT000ADRUN

-/1PAPA/FEAT110ALOAN

-/1PAPA/FEAT110TMSTA

-/1PAPA/FEAT000P0169

-/1PAPA/FEAT000DFSEX

-/1PAPA/FEAT000REPTA

-/1PAPA/FEAT000TIMTA

-/1PAPA/FEAT000REPTA

-/1PAPA/FEAT000I0005

-/1PAPA/FEAT000LVTYP

-/1PAPA/FEAT000MSN20

-/1PAPA/FEAT000PERNO

-/1PAPA/FEAT000PERNO...............

All is same unicode problem. We treated these cases with process(SE38 enter program name and go to attribute, activate unicode check box), . So, the status is good now.

As far as I know, I have tried to test and check funtion and problem to find same

problem. However, I'm Not sure. That's my question.

Do U know how to solve this problem at one time??

I'll wait for your solution.

Thank you in advance.

[Former Member · Accepted solution]

Hi Yong,

The list you have mentioned are the programs that get generated when a feature is activated. You can do a unicode activation for all this by using the Tcode UCCHECK and select the Object Name with "FEAT000" and try to check the attributes at one time.

Hope this helps you.

Regards,

Subbu.

[Former Member · Accepted solution]

Thank you for your advice.

But, I can't solve the problem yet. UCCHECK is possible for begin with Z* or Y*. It means Not standard but modified program. In case of me, all problem is standard program.

I refered Notes No. 655331.

So, I need to know more tip or advice.

Message was edited by:

Yong-il Park

[Former Member · Accepted solution]

Hi Yong,

Did you do the Unicode migration before upgrading your system from 4.6C to ECC 6.0?. If so did you proceed with all the standard procedure. Like

1. UCCHECK for Static Unicode Syntax Check

2. SCOV - ABAP Coverage analyser

3. SPUMG - Unicode Preconversion

Hope this helps you.

Regards,

Subbu

[Former Member · Accepted solution]

Dear Subbu,

Thank you for your kindness.

But, I can't solve my problem until now. We did SPUMG among T-code what you mentioned. UCCHECK and SCOV is for CBO program according to SAP Library.

However, all problem is standard in my cases. That is my problem.

Best regard, Yongil.

[Former Member · Accepted solution]

Hi Yong-il;

What is the status did you resolved your issues?

Please advice...

Best Regards,

Aslam Riaz

[Former Member · Accepted solution]

Dear, Riaz.

I guess that you have same porlbem with me. right?

I sent a OSS Message to SAP service center and received the answer.

I am worrying that you will be disappoint at the answer.

Attached full qeestion and answer.

I hope to my advice is good for you.

Best Regards,

Yong-il Park

-

---

Question :

Recently, Our company finished version-up project from 4.6C to ECC 6.0.

(I already sent e-mail to you by OSS)

We solved almost problem. But, we still find same unicode problem

contineously when we run standard program.

Our problem is we found too many cases like that.

Until now, Finding history.

-/1PAPA/FEAT110VDSK1

-/1PAPA/FEAT110PINCH

-/1PAPA/FEAT000P0003

-/1PAPA/FEAT000LDAYW

-/1PAPA/FEAT110NUMKR

-/1PAPA/FEAT110TIMMO

-/1PAPA/FEAT000P2011

-/1PAPA/FEAT110VTART

-/1PAPA/FEAT000DTAEL

-/1PAPA/FEAT000BIMAP

-/1PAPA/FEAT000ADRUN

-/1PAPA/FEAT110ALOAN

-/1PAPA/FEAT110TMSTA

-/1PAPA/FEAT000P0169

-/1PAPA/FEAT000DFSEX

-/1PAPA/FEAT000REPTA

-/1PAPA/FEAT000TIMTA

-/1PAPA/FEAT000REPTA

-/1PAPA/FEAT000I0005

-/1PAPA/FEAT000LVTYP

-/1PAPA/FEAT000MSN20

-/1PAPA/FEAT000PERNO

-/1PAPA/FEAT000PERNO...............

All is same unicode problem. We treated these cases with process(SE38

enter program name and go to attribute, activate unicode check box), .

So, the status is good now. As far as I know, I have tried to test and

check funtion and problem to find same problem. However, I'm Not sure.

That's my question.

Yesterday, I found new solution on SAP Network forum. T-code is UCCHECK

and SCOV.

However, this is just for begin with Z* or Y* and modified program(CBO).According to my cases, all problems are standard program.

I'll wait for your solution.

Thank you in advance.

-

---

Answer:

Sincere thanks for your contacting SAP support.

Yes,you are right.The solution you found on SAP Network forum,T code

UCCHECK and SCOV are only for the customizing programs Z* or Y* and

modified ones.

For the standards programs,I checked your query with the expertise in

the unicode area and I would like to confirm that your own solution is

correct.Most of SAP standard programs are working fine with unicode

check,but for some of them,which are not so often used sometimes,you

need to tick the unicode check box.

Thanks!

[Former Member · Accepted solution]

Activating features

In client 000, start the RPUMKG00 program (set parameter 'Type of activation' to '1'). The 'Unicode checks activate' indicator is set in the programs that are generated as a

result. If you change any features, repeat this action in the relevant clients

The above solved the problem...

Thanks