Activities while doing a prototype for an upgrade

[Former Member]

Hi,

Our client is planning to upgrade from 4.6C to ECC 6.0 and would like us to do a prototype (pilot) for 6 weeks.My doubts are:

1) What are the activities/tasks that we should carry out in these 6 weeks of assessment

2) The client would like us to give him the technical upgrade approach. Please advise what is and should be the technical upgrade approach.

3) What is SAP RBE (Reverse Business Engineering)? How do we execute this?

4) Is there any way to know the screen level changes that will happen due to the upgrade, before actually upgrading to ECC 6.0

5) What is PREPARE Script run? Who does this?

Any help would be gretaly appreciated.

Thanks,

Mick

[Former Member]

Hi ,

Cannot give the whold info but i would like to share some of the points i know.

Initially when doing the upgrade the existing land scape is copied into the new landscape.

SPAU & SPDD will be done for the repository . UCCHECK for all the code. Now the code has to be unicode compliant in ECC6.

SAMT will be done for the code in additional check in the standard code.

Now the technical upgrade approach will be the sequencing of operations of the above.

Intially there will be a different landscape apart from the usual D->Q->P LINE.

Once the repository is working fine in this the client will be shown to find the defects ,

Here the client checks with the old system with the current ongoing functionality and confirms with the new land scape in this scenrio. Once they are OK the same will be repilcated in the D->Q->P in the new ECC6.

Techncal upgrade approach will be in correcting the code for Unicode complaint. This will be the major task in the upgrade.

This is done in Normal ABAP code , Function modules , Interfaces , etc apart from your SPAU and SPDD of the system.

Apart from these there will be code page conversions that need to be taken care of . Implementing new oSS notes .

Screen level changes may happen to only 1-3% (Cannot comment on this since the module can be anything ).But there will be no major screen changes.

Prepare script run will be the modular wise blue print execution which will be done by the concept owners(Client) and by our module leads .

Br,

Vijay.

[Former Member]

Thanks Vijay (Sniper) for the very informative answer. Have awarded points.

Request you to give your valuable inputs on the following:

1) Do we do the correction to all the programs, function modules, etc in the pre-assessment of 6 weeks?

2) Can we know the screen level changes and the impact of the screen level changes before the upgrade? If not then how will we know after the upgrade?

3) Please explain in detail about script run.

4) What about SAP Script and Smartforms? Will they be impacted in any way?

Regards,

Mick

[Former Member]

Hi,

1.When you do the UCC check by feeding in all the programs (usually the list of active programs in Production of prev version)

the new system checks the program where there is a unicode problem and displays the error .

Not all programs have unicode problem but system prompts the error where it forsees a problem.

6 weeks is enough time to do the ucc . There will not be major code changes except few regular checks.

2.Screen level changes can be obseverd only after the spau and spdd is done in the upgraded version.As i said earlier no major changes will be there except some OSS note applications which can be known after the testing is done on the screens .

The testing will be in comparision with the previous and the current one. We never got a list of the changes to be brought in the screens in the upgrade only can detect the changes once the functional test starts.

3.Script run is just like the definite algorithm that the testing team prepares in the process layout. Generally in the preassesment we have the functioning of a program in series of steps . This is normally done by the concept owners and testing teams.

The steps for all the process are stored in a quality center (ex : mercury quality center )

.The tester follows these script run of a particular program from the QC.

4. Of course in the UCC check if the driver program has an ucc error it will be corrected. But in the form layouts we never use upload/download Fm's or move logics among the structures or hexa conversion logics , so the changes will be in the driver programs in scrpits .

Br,

Vijay

[Former Member]

Answered