4.6c -> ECC 6.0

[Former Member]

Hello Community,

1. faced with following question, where i can get SAP documentation about difference between 4.6c and ECC 6.0 from technical view.

2. please help me find any strong argument why i should convert system from MDMP to Unicode?

Thanks in advance.

[praveenkumar_kadi]

Hi,

For your first question,check

for your next question check

1>

2>https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/efd1dd90-0201-0010-e1b0-8437c998...

3>this might be the good pdf for the reason

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/fdbedb90-0201-0010-4483-b64ac397...

reward points if it helps

[Former Member]

Thank you, but it's not exactly what i need. describe more deeply current situation:

we have 3-tier landscape for CRM 4.0, BW 3.0, SCM 5.0 and R/3 4.6C; all of them are none-unicode systems. We're using only two languages English and Russian. Also we're going to upgrade R3 to ECC 6.0. Why we should convert ECC 6.0 to Unicode?

[praveenkumar_kadi]

Hi,

Seems you havn't completely read the pdf provided.

anyhow I will summarize it here.

The landscape you mentioned here are all non-unicode systems. so, different languages..am i right..!? If so, converting to Unicode gives following features you can add upon.

…allows text data from different languages to be

stored in one repository.

…enables a single set of source code to be written to

process data in virtually all languages.

…simplifies the <b>addition of new language</b> support to

an e-business application since character processing

and storage remains unchanged.

and the advantages you can see

&#56256;&#56377; Lower costs of implementation!

&#56256;&#56377; Faster speed to market!

&#56256;&#56377; Better customer satisfaction!

So, In short

If you want to have benefits like that above, then you should convert to Unicode.

It's depends on your requirements . think..!

Reward points if it solves