ecc5

[Former Member]

Background

One of my clients is intending to rampup to ECC6.0 from 4.6C. I am assessing the efforts needed from a ABAP perspective. No new ABAP's are needed. I need to ensure that the following work well.

- Custom ABAP's (reports, interfaces, conversion)

- User Exits

- Smartforms

1. I am making a presumption that SAP code need not be checked. Maybe somebody can confirm.

2. From doing various searches, this Upgrade assessment can be done if we run the UCCHECK and the SCI transaction along with SAMT. I hear that these three tools should be enough from an assessment and identifying the right tools. Other who have gone through this experience can confirm that these three tools are all that are needed, and if there are other things that can facilitate the process, what they are.

3. SAMT is the only transaction available natively in SAP 4.6C. OSS note 543359 allows us to install SCI in 46C. I am unable to find the note that will allow me to run UCCHECK in 46C. Any information on identifying the correct note for installing UCCHECK on 46C will be appreciated.

4. Please feel free to share your experiences for conversion from 4.6C to 4.7 or ECC5.0 or ECC6.0 from an ABAP perspective.

[Former Member]

quite urgent plz reply....

Edited by: Chakradhar Dandu on Dec 22, 2007 9:07 AM

[Former Member]

Hi,

We did from 46c to 640

1st stuff is:

During upgrade should be done SPDD transaction. Data dictionary and tables/views correction.

2nd:

SPAU transation. Showing conflicts between standard programs/objects and same objects wich in some reason were changed by customer.

3rd:

After it you'll need to do all testing (End user testing) and get errors. There will be for sure. And then check thois errors and correct them, as it will be customer programs 'Z'.

Note: If you want to install something (somkind package like DIMP or IXOS) then it should be done before SPAU as it will rise new conflicts.

Note: Testing should starts only after all conflicts in SPDD and SPAU are solved.

anythig else? at this moment nothing else in my head

Reward if Usefull,

Chakradhar.

[Former Member]

We did from 46c to 640

1st stuff is:

During upgrade should be done SPDD transaction. Data dictionary and tables/views correction.

2nd:

SPAU transation. Showing conflicts between standard programs/objects and same objects wich in some reason were changed by customer.

3rd:

After it you'll need to do all testing (End user testing) and get errors. There will be for sure. And then check thois errors and correct them, as it will be customer programs 'Z'.

Note: If you want to install something (somkind package like DIMP or IXOS) then it should be done before SPAU as it will rise new conflicts.

Note: Testing should starts only after all conflicts in SPDD and SPAU are solved.

anythig else? at this moment nothing else in my head

reward if usefull

cheers,

siva.