The user experience in the Business Suite was transformed from this: Quick launch, which makes it easy to find transactions, WD applications, and third-party content….Put together, these two innovations offered a whole lot more: However, in 2011 ECC6.0 EHP 6 was released, followed by NWBC 4.0 in September 2012. So originally the choice was easy:ĭo your end users work mainly on SAP GUI? YES -> SAP GUI standaloneĭo they work with both SAP GUI and Web-based applications? YES -> NWBC OK, here goes: NWBC was originally developed to enable end users to consume both SAP GUI applications and Web-based content (Web Dynpro or third-party) in one environment. Again, if your experience is different, or if you think I’ve left something out, please feel free to say so in the comments. What I do want to do is clarify our strategy – this is how we position the two products, and this is what we think they are best suited for. I’ll start with the one I probably get asked about most: SAP GUI standalone versus NWBC with SAP GUI embeddedĪctually, this first section was the hardest one to write – the danger is, it will sound like marketing, which is not what I want to do here. SAP NetWeaver Business Client and Other Clients. ![]()
0 Comments
Leave a Reply. |