regarding unicode object

[Former Member]

Hi guys

After Upgrade Unicode Converstion, I found SAP standard objects(like Subroutine pool,Programs) which are not Unicode Check activated in Local objects($TMP). Could somebody know reason why it is.

And also i want to know whether we need to activate it manually for those objects.?

Because one of the SAP object(Subroutine pool) in localobject was dumping unicode compatible error. After manually checking the object unicode active, it works fine.

Suggestion please

regardss

Ambichan

[Former Member]

The Unicode Attribute flag for the custom objects can be set ising UCCHECK Tool.

The UCCHECK tool would set the Unicode Attribute flag for only those objects which appear in the green light in the UCCHECK output.

Steps:

Login & Execute transaction UCCHECK

A list would be displayed.

The GREEN LED OBJECTS would be flagged for Unicode Attribute once you tick the flag in UCCHECK screen & EXECUTE.

[Former Member]

hi Prashant,

I have no problem with Custom objects.

Now this problem is about Standard SAP objects, In unicode system all SAP standard objects need to be unicode active am i correct?

In local objects($TMP), i can see Standard objects for (User :SAP*) are not checked (Unicode active flag )even though its Unicode system. Was it not required to get unicode active flag checked?

regards

Ambichan

[Former Member]

The Unicode attribute for all standard ABAP is automatically set once the Unicode migration takes place. The development team would need to set this attribute for all the custom ABAP.

While upgrading, BASIS would get a popup to inform whether you want to go for Unicode Upgrade or not. I guess in your case, Unicode Upgrade was not selected. Hence standard programs are not flagged for Unicode.

[Former Member]

Hi Prasanth,

You are right, During Basis upgrade we selected Unicode check option for unicode migration.

And also we confirmed all SAP standard objects are unicode activated. but when we saw the Standard objects in LOCAL objects($TMP SAP*), it was not unicode activated.

We are surprised why only Local Object directory objects are not unicode activated by default. Can you tell me where might be the problem.

Because recently we found Program(subroutine pool) RMCX0048 in Local object is not unicode activated flag and it throughs dump(Not unicode compatible) during MB1B transactions.After we changed RMCX0048 program as unicode active it started working correctly.

Suggestion please.<b>Any comments please</b>

regards

Ambichan

[Former Member]

hi ambikumar,

even i have the same issue how did u made unicode check active for $tmp standard pragram is it thru taking access key or is there any standard program or not through which we can make all $tmp standard objects unicode active

Regards

Hemanth