Role of Developers in ECC 6.0

[naveenvishal]

Hi Gurus,

Our company have recently moved from 4.7 to 6.0.

1. What are the steps/points to be taken into considerations after the implementation, taking developer view into consideration...

2. In terms of tools, what 6.0 has offered us, apart from traditional abap programing...

3. Heard the thing that developers have more restricted use/value now in comarison to 4.7, are v , programmers in a danger of extinction, literally..

Thanx,

[Former Member]

Role of Developers in ECC 6.0

With every new version release SAP releases Version / Release note. You should check the changes made from release to release.

You can find the difference in release notes of each SAP version.

Here are the links.

http://help.sap.com/saphelp_47x200/helpdata/en/fc/e3003deddfae4de10000000a114084/frameset.htm

http://help.sap.com/saphelp_scm50/helpdata/en/28/b34c40cc538437e10000000a155106/frameset.htm

http://help.sap.com/saphelp_erp2005/helpdata/en/43/68805bb88f297ee10000000a422035/frameset.htm

Follow the life cycle of upgradation project:

Hi , plz find the high level design of the upgrade life cycle.

Activity

Description

SPDD adjustments (Adjustments in Data Dictionary objects)

Adjustment of data dictionary objects

Identify SPAU objects and Custom objects

Prepare the list of SPAU objects and Custom objects

Reassessment of effort for modification and adjustment activity

Reassessment of effort required for modification and adjustment activity

Object Tracking Sheet

Prepare the object tracking sheet

Modification and adjustments of

SPAU and Custom objects

Modification and adjustment activity

Object Testing (typically for custom objects)

Primary testing of object to avoid any short dump

QA Objects and documents

Quality Control of modification and adjustment

Release Request

Transport the request from DEV to QA system

Delivery of Objects to Client

Completed objects are delivered to the client

Integration Testing

Integration testing

Rework Objects

Objects requiring rework after integration testing by the client and receipt of feedback

There are two types of Upgradation:

1) Technical

2) Functional.

Technical: It is puerly relevant for ABAP development.

First they will prepare Business Process Master List.(BPML).

It contains what are the business process, transaction codes, programs etc.

They will cross check whether the business process, transaction codes, programs etc are functioning properly in the existing system. If not, they will go for

ABAP development in that System.

Then they will go for user document preparation and user training documentation & Scripts.(Nothing but templates).

While doing Upgrade You have to aware of all related program like BDC's , Screens related errors and all dictionary related problems.

Some function modules may become obsolete, and some screens will change

and some new fields will be added in the new versions etc.

Also take care of SPAU and SPDD tcodes.

You should be able to know about Unicode concept in sap.

check this

http://www.thespot4sap.com/upgrade_guide_v2.pdf#search=%22upGRADE%20STEPS%20-%20SAP%22

also chk these 2 notes in service.sap.com

Technical Upgrade is only a version upgrade without any functionality changes.

The objects that are needed to be upgraded are:

Includes

Function Groups / Function Modules

Programs / Reports

OSS Notes

SAP Repository Objects

SAP Data Dictionary Objects

Domains, Data Elements

Tables, Structures and Views

Module Pools, Sub Routine pools

BDC Programs

Print Programs

SAP Scripts, Screens

User Exits

Reward Points if useful.

[naveenvishal]

no, i was asking in terms of programmer/developer's perspective, not the whole SAP enhancements/addons..

kindly guide..

[matt]

Don't know about 1 and 2 - but I can tell you that 3 is complete rubbish.

matt

[Former Member]

See SAP Note 367676 - Release Upgrade from 4.6 to 6.1 for Customer Progs for more ABAP information.

Hope it helps.