Classic vs.Standalone scenario in EBP implementation

Classic vs.Standalone scenario in EBP implementation

My company is implementing an EBP 3.0 system and interfacing to an existing 4.6C R/3 backend (where SAP has been rolled out to the subsidiary company) or a non-SAP system (where SAP has not yet been rolled out). The scenario chosen is the 'Standalone' on the basis of this heterogeneous backend system landscape, and the fact that the synchronous RFC communication between EBP and R/3 in the Classic scenarios represents too much of a risk to the business. Is this a wasted opportunity to not take advantage of the ready-made EBP-R/3 integration of the Classic scenarios?

    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,
Hard to say with the amount of information here. Do keep in mind that there can be multiple scenarios that can exist in a single EBP implementation.

A lot of the implementations I've been on where we've dealt with a heterogeneous backend system landscape, we've considered implementing both Classic and Standalone scenarios, split by business rules.

I would definitely suggest to explore why you cannot have both classic for R/3 backends and Standlone for non-SAP backends.

Regards,
Sachin Sethi

This was first published in September 2004