topic Re: Effort estimate (ABAP) during Unicode Conversion project in Application Development and Automation Discussions

Effort estimate (ABAP) during Unicode Conversion project

Former Member — Tue, 03 Jun 2008 04:55:44 GMT

Hi ,

I am working on a CU&UC (Combined Upgrade and Unicode Conversion) project from 46C to ECC6.

We are having 8 different codepages (MDMP SYSTEM) and around 10000 custom objects.

Does anyone have any experince in doing such kind of project ? I am looking at the effort estimate on technical side (ABAP) and functional side.

Any inputs of Technical effort in such a project with related number of codepages and custom objects will be useful (in man days & project duration).

Thanks

Dilip

Re: Effort estimate (ABAP) during Unicode Conversion project

Former Member — Thu, 05 Jun 2008 07:41:29 GMT

Hi Dilip,

the main effort from ABAP side seems to be testing of the new system and creating the Unicode vocabulary. You need test teams and test plans for all locations and for the vocabulary you need people for all your languages. ABAP coding itself is probably not your biggest problem. You have to switch your system to unicode and then check all your sources. This could be done by a report or transaction (check the documentation regarding the Migration). From my point of view this is the main effort you'll have, testing and building the vocabulary. How big this effort is depends on your system. I think six month are a good time frame for the whole project (I assume you migrate a landscape of 3 systems). Because I'm working in the Basis administration I could not tell you the exact man days, but I would estimate up to two weeks for the vocabulary per language. You should have the numbers for the system tests from previous upgrades.

The technical migration effort depends on your hardware and time requirements. If your system is big (TBytes) and your downtime is very limited it could be necessary to tune the migration by testing it several times. If your requirements are not that high, then a single test migration could be sufficient. I've done two bigger migrations with 2.5 and 3.5 TB in less than 24 hours but therefore you have to have fast hardware and you have to tune your process well. If you have a single huge table this could destroy all efforts reaching your time target, if for example the index build could not be done in less then your time target. If you have enough hardware resources and time to tune your migration you could reach almost any time (which makes sense - some hours).

Best regards

Ralph Ganszky

Re: Effort estimate (ABAP) during Unicode Conversion project

Former Member — Mon, 09 Jun 2008 19:55:53 GMT

Hi Dilip,

I have a similar requirement, and I would like to know how did you find out all the custom objects,, you said you have more than 1000 custom objects,

Please help me out in finding, how and on what basis you selected those custom objects and what are they?

Thanks in advance

Re: Effort estimate (ABAP) during Unicode Conversion project

Former Member — Tue, 10 Jun 2008 09:46:05 GMT

Hi,

How did you assess the project?

The Objects should be divided in to High Medium Low Complexity based on some criteria and time is allocated for each object depending on priority.

For Unicode it is 40 errors per day per resource.

For more clarifications contact me.

Thanks.

Re: Effort estimate (ABAP) during Unicode Conversion project

Former Member — Fri, 13 Jun 2008 08:24:39 GMT

Six month of a basis administrator, and some developers 3 months.....

The vocabulary is a very large task, you have to create the vocabulary correctly and it can take hours and hours.....may be two weeks....

Regards,

Alfredo.