What to look out for while testing both classic and extended classic scenarios

What to look out for while testing both classic and extended classic scenarios

Our customer wants to upgrade their back-end R/3 system from 4.6C to ECC 5.0. They have mySAP SRM 3.0 (technical) and EBP 4.0 (functional) versions live systems for the Indirect Materials Procurement. I am part of the pre-study for ECC 5.0 upgrade to test the functionalities of existing business processes in R/3 back-end for EBP.

They have classic scenario implemented and planning to roll out extended classic scenario soon. The tricky situation is they are planning for ECC 5.0 upgrade as well as for the extended classic scenario.

I would like to know what to look out for while testing in ECC 5.0 both for classic and extended classic (for the future). Also, are there any important aspects we should keep in mind when testing?

Another situation is we are given a sandbox of ECC 5.0 without connected EBP and HR (They have SAP HRMS rolled out for all the countries). Hence, we need to check the technical side more as we don't have any system to test the shopping carts, etc.

    Requires Free Membership to View

    When you register, you will start receiving targeted emails from my award-winning team of editorial writers. Our goal is to keep you informed on the hottest topics and biggest challenges faced by SAP professionals today.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSAP.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSAP.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

Hi there,
You pose a good question but it's a tough one to answer in a "one size fits all" situation.

This dilemma requires a good understanding of the organization's current environment along with looking at the functionality in place for the SRM solution overall.
Going from an SRM classic to extended classic is a significant undertaking. The normal blueprint phase would provide for the analysis of the current functionality deployed in a classic mode and then mapping it to the extended classic functionality.

For example, if reservations are being created from SRM shopping carts in extended classic mode, that would have to be achieved via some BADI development. Similarly each functionality needs to be revisited. Delivery addresses, ship-to addresses, POrgs, PGrps, plants. The complete organization structure attribute setup -- and a lot more. These are just a few quick thoughts.

My best advice to you would be to look at the upgrade guide for SRM and utilize that as your guiding principle. You can download that at http://service.sap.com.

This was first published in June 2005

Join the conversationComment

Share
Comments

    Results

    Contribute to the conversation

    All fields are required. Comments will appear at the bottom of the article.