SAP R/3 System analysis

[Former Member]

Hello!

Before the upgrade from R/3 4.6C to ECC 6.0 I would like to execute SAP R/3 system analysis.

The following functions should be included in this program:

- detailed analysis of system modifications (effort driver and risk factor during an Upgrade)

- comparison against a SAP ERP 6.0 reference system

- extension SAP tools, including RBE and conflict lists (SPAU/SPDD)

- syntax analysis of program code with respect of adjustement need

- quality control of own development

- control of amount of transports within different company areas

- control of user information, such a user type, logon date, etc.

- basic control, whether a sufficient authorization concept is available

- Identification of objects that should be considered for the archiving in oder to decrease the db-size

My question are:

<b>- which tasks can be convered with SAP standard transactions what are the names of the transactions?

- which effort do I investigate for these tasks?</b>

Thank you very much!

regards

[Former Member]

Dear Thom,

To know the functionality changes u can refer http://solutionbrowser.erp.sap.fmpmedia.com/

http://www.sap.com/solutions/business-suite/erp/pdf/BWP_ERP2006_Upgrade.pdf

http://service.sap.com/releasenotes and http://service.sap.com/upgrade for functional changes.

Need to consider the following things:

For Reports…it’s custom developed program …so unless there is any kind of change in requirement from the client regarding the layout…nothing needs to be changed…I think it will work fine in ECC 6.0 to…except few things may needs to be changed..so you need to discuss whether they want the reorts as it is right now…or want to change the layout (adding some new info/fields etc) of any report…so u need to modify the program for those…and estimate accordingly…for a medium complexity’s Report dev it takes approx 9 pd (FRSTDSCoding+Unit Testing)…so to modify it will be less than that (depending upon the scope of changes)

Now say for Batch Inputs(interface/Data Migration) using BDC…you need to see how many BDCs are there…again if the field lengths and layouts are not changing…then no need to change anything (except the main thing…..you need to change the obsolete function modules…there are some in 4.6 c like for data upload ws_upload_*** is there 4.6C but obsolete in ECC6.0…there are some new with enhanced functionality so you need to modify the BDCs…and many cases it happens that the whole transaction screen changes for process…in that case better to develop new BDCs…so you have to consider those parameter…look into and estimate accordingly…modifying a BDC should not take more than 1 PD…

Now say for Forms…there was no Smart form in 4.6C…form printer was there..though the same option is there in ECC 6.0 too..but better to go for/should go for Smart form…in that case…it’s complete new dev…so estimate accordingly…a medium complexity’s form should take 8 PD (FRSTDSCoding+Unit Testing)…you can take it as 10 PD too…even if client wants to keep it is as it was in older version…you have to redevelop the layout in ECC 6.0 again…as form printer is even client dependent…maximum you can copy the program associated with that form in the new version too…and your effort will be saved…again you have to consider if clients wants to change the layout too…

Now for enhancement…so in that case u need to see individual cases…for a medium complexity enhancement it should take max 15 PD (FRSTDSCoding+Unit Testing)…

One more important thing is that the Unicode Compatibility…this needs to be done….needs to change the code (variable name) accordingly….also Version management tool is used for the standard programs…

Also pls find the following forums:

/thread/317225 [original link is broken]

Hope it will help you.

Thanks,

Atin

<b><b>Reward points if it helps.</b></b>