cancel
Showing results for 
Search instead for 
Did you mean: 

Difference between Upgrade and Implementation Projects

Former Member
0 Kudos

Hi everybody,

are there any differences between an upgrade and an implementation project in the solution manager? does an upgrade project feature any functionality an implementation project doesn't and vice versa?

thx in advance

art

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Arthur,

The Upgrade Project has additional abilites. For one, you can put in the product you are upgrading to (i.e. SAP ECC) in the system landscape and then run the compare and adjust feature. This will tell you what items in the BPR changes when you upgrade your box.

regards,

Jason

Former Member
0 Kudos

Hi Jason,

thank you for your input. with regards to compare, i know how to compare a project to a template but i don't know such a feature with regard to a system landscape. what do you mean by the "compare and adjust feature" and where do I find it? what is being compared here?

thx in advance

art

Former Member
0 Kudos

Hi Art,

The Compare and Adjust only works if you leveraged some of the Business Process Repository to build your BPS. Then you can run the Compare and Adjust and it will flag the processes that change if you upgrade your system from one release to the next.

Basically the steps are:

1. Build the system landscape

2. Build the BPS leveraging some of the BPR

3. Add the logical component you will upgrade to, to the system landscape of the project (such as SAP ECC)

4. Go to SOLAR_PROJECT_ADMIN and highlight the project

5. In the top menu, I believe under Edit (maybe Goto), select Compare and Adjust

6. Go into your upgrade project in SOLAR01 and see the flagged processes

regards,

Jason

Former Member
0 Kudos

thx a lot

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Arthur,,

Three key benefits of upgrade are...

Stability and visibility

Historically, SAP upgrades consisted of large, comprehensive releases that compelled users to upgrade regularly in order to take advantage of new functionality. In contrast to this, SAP’s new policy for upgrading will consist of multiple, smaller releases of tightly focused functional enhancement packages. In essence, this means that the core mySAP platform will remain stable and unchanged for several years. This stability and consequent visibility protects customers from the cost and complexity inherent in monolithic upgrades while freeing them to innovate without fear of obsolescence.

Easier ROI

Second, by issuing smaller, less costly functional enhancement packages, SAP has made it substantially easier to build an ROI case for upgrading. By allowing customers to selectively pick and choose only those capabilities that align with their specific business needs, SAP’s new `a la carte upgrade policy is considerably less costly in terms of both money and resources. Customers have the flexibility to move forward at their own pace, enhancing the value of their ERP systems incrementally, which greatly simplifies the process of building a business case, performing a cost/benefit analysis and determining ultimate return-on investment.

Easier migration to SOA

Based on the NetWeaver platform, mySAP ERP 2005’s functional enhancement packages are inherently geared toward enterprise services. As such, SAP’s new upgrade policy presents an innovative, iterative approach for implementing service-oriented architecture (SOA). On this score, SAP is miles ahead of Oracle and is a considerably safer choice given the company’s proven heritage and organic SOA roadmap. In addition to the many functional enhancement packages issued directly by SAP on a regular basis, customers will also have available to them a wealth of industry-specific composite applications developed by the rapidly increasing number of SAP xApps Certified partners. In effect, SAP’s policy of providing upgrade enhancement packages serves well as a harbinger of how all enterprise system upgrades will happen in the dawning era of service oriented architecture

when it comes to UNICODE upgrade it has following benefits.

Unicode provides the solution to the problem of multiple, possibly incompatible code pages:

Unicode currently defines over 98,000 characters, with room for over 1 million characters.

Unicode defines each character only once

Unicode can be used for the system code page, front end, and printing

In a Unicode SAP system you can display and maintain character data from any language with any logon language. For example, you can logon to your system in Japanese and maintain Russian data.