Advantages of ABAP Webdynpros over BSP??

Hi,
We are currently in ECC6.0. Is ABAP Webdynpro advantageous over BSP for any UI development ECC6.0 onwards in general?
Specific requirement for which BSP is needed - we need a single application for a Help Desk team to handle calls from customers. The application will have multiple screens with data flowing into this application from multiple sources.
Need inputs on the above....
TIA,
Regards
Deepthi

>Both webdynpro and BSP call ABAP function modules from HTTP. The BSP interface does this via programming in SE80, the webdynpro does this via programming in the Java development workbench. The BSP enters the SAP systenm via the ICM and is 'routed' to ICF where call are then made to executre ABAP (a good example is we use SOAP BSP's). Webdynpro routes via the ICM to the Java engine which then executes the Java to call the functions via an RFC interface called a JCo connection.
There are many incorrect statements in your posting. You appear to be compairing BSP to Web Dynpro Java - not Web Dynpro ABAP. Why would you do this in a Web Dynpro ABAP forum posting? Of course everything you stated about Web Dynpro running on the Java engine and using JCo and being programmed in the Java development workbench is totally wrong if you are comparing to Web Dynpro ABAP.
Here is the explaination of the differences from the SAP Press Book: Next Generation ABAP development (page 303):
Web Dynpro ABAP is SAPu2019s new UI strategy, which was introduced in SAP
NetWeaver 7.0. It is based on the Model View Controller (MVC) paradigm
that separates business logic from the user interface logic. Developers, like
Russel, can use this tool to develop robust business applications quickly and
easily, without ever having to deal with the inner coding of the user interface
elements.
The Web Dynpro ABAP framework provides a WYSIWYG view editor (What
You See Is What You Get) where the developer simply drags and drops the UI
elements into the view. This means that there is no coding of the UI elements.
This is not the case when working with Business Server Pages (BSP),
where the developer must know some HTML or JavaScript in order to code
the user interface.
The Web Dynpro framework approach can be viewed in a number of ways.
If a developer is not proficient in HTML or JavaScript, the Web Dynpro
ABAP tool looks pretty good. He doesnu2019t have to worry about coding the UI
and he can focus more on the business application logic. On the other hand,
if the developer wants to add his own look and feel or some additional UI
functionality to the Web Dynpro ABAP UI, he canu2019t. The UI implementation
is hidden from the developer and cannot be manipulated, such as adding
your own HTML or JavaScript. The reason for this protection is that Web
Dynpro was developed to provide a standard business application user interface
across all applications that leverage this tool.
There is another advantage to the client abstraction approach that Web Dynpro
takes. When you design a user interface in Web Dynpro, what is saved is
just a metadata representation of the layout and elements. In other words,
Web Dynpro is not tied to just HTML and JavaScript as its output medium.
The Web Dynpro runtime analyzes the type of client that is making a request and responds with the appropriate rendering output. Today that means web browsers are making the request and receiving HTML and JavaScript. But, in the future, when the next great UI revolution occurs, you wonu2019t necessarily
have to recreate your applications to take advantage of it. Already you can see examples of a smart client and Adobe Flex based rendering engines for Web Dynpro. Switching to these alternative presentation tools requires no coding changes within the applications themselves.

Similar Messages

EP over BSP...

Hi,
We use BSP to grab the R/3 data and dispaly on browser. I guess we do the same stuff with EP too.
So whats advantages of Enterprise protals over BSP or vice a versa?
Thanks.
Regards,
Tushar

Hi,
check this link, you will get to know all about EPs.
https://www.sdn.sap.com/irj/sdn/developerareas/ep?rid=/webcontent/uuid/4b0c105e-0501-0010-bcb0-92478a4b2a17">enterprise [original link is broken] [original link is broken]
Hope this will help.
Regards,
Amit
Do not forget to close the query once it is solved and also reward the suitable answer.

Your opinion on: BSP or Java Webdynpro or ABAP Webdynpro?

Could you please give me your opinion on the business scenario we have here:
We are implementing SRM 4.0 with backend R/3 4.6C, WAS 6.4 and Portal 6.0. SRM has its typical shopping cart applications mainly for procurement and the workflow trail displaying the approval. The client wants us to build a few custom forms on the web frontend of SRM (or may be in Portal). The idea is to store these forms and display when needed with the status info just like a shopping cart.
<b>Now the requirements for these forms are as follows:</b>
1. These forms will have multiple fields which need to have the F4 kind of help. (the F4 options will reside in SRM or R/3)
2. The form should have some kind of a ALV grid (autoexpanding feature) which will allow the user to put in multiple line items so that they could submit more items on one form.
3. Users need to be able to attach a spreadsheet to the form which should not be editable once the form is submitted. The attached spreadsheet should be stored. (We are planning on using Archivelink Filenet for this)
4. Upon submission, a workflow will be kicked off as per the defined Org structure for approval of the form.
5. After submission, the user should be able to go and view the approval status of the form and also print the summary of the values that he entered in the form. (may be a smartform could be provided for this)
We looked at different options to accomplish this task:
<b>BSP:</b>
Creating BSP pages and giving access as links to the user on the webfrontend of SRM. Now, if we go the BSP route, we need to develop in SRM as the R/3 4.6 c does not have BSP development capabilities. If we take this approach, I am not sure if all the above requirements (specially like attaching spreadhseets) will be met with BSP pages.
SAP Webdynpro Java:
It seems that the Webdynpro is easier to use because of the graphical tools available. But the only problem if we go this route is that we will have to find a java guy.
SAP Webdynpro ABAP:
We currently have WAS 6.4. As per the documentation, the ABAP Webdynpro development tool is available from NW04s onwards. So, we are still not sure if we could use it. But, we want to push towards upgrading if necessary. Being an old time ABAPer, developing ABAP Webdynpro seems do-able. (i know it may not be that easy).
Last but not the least, DIALOG Program:
Creating a dialog program in R/3 or SRM seems fairly simple. Then, an iview could be created on the portal for this transaction, though at this point I am not sure how a spreadsheet could be attached and stored within a dialog program.
The creation of the workflow may not be that bad after the original form is designed. The graphical display of the approval trail might be difficult, but we might get away with a report for that. For printing the details of the form, I guess I could develop a smartform and put out a button on the screen to print it out in the display view.
Could you please give me your opinion / best approach for accomplishing this task, keeping in mind the complexities of these new dimension products?
Thanks
Sri

I would say that all four solutions to solving your tasks are technically feasible. Here are some thoughts that I had however:
First ABAP Webdynpro: it is true that ABAP webdynpro is only available with Netweaver04s. 04S is still in ramp-up which means that only a subset of the customer base is allow to implement it. It will not become generally available until later this year (check the service marketplace for current release estimates). That being said, it probably elimintes WDA as a possiblity for your project unless you are will to wait and to upgrade.
However having worked with WDA for a while it is probably the best tool to custom develop what you describe. It has excellent built-in F4 value help. It also has a damn fine ALV grid implementation. The spreadsheet could be just as simple as file upload in binary or your could try your hand at office integration. Finally for the form you could use Adobe Interactive Forms which also has very nice integration into WDA.
Now to Dialog Programming: You could of course use dialog programming. It seems a little bit of a waste to custom build something so large if WDA is in your near future. There are obvious disadvantages (little OO structure, no MVC, etc). You would have ALV grid, office integration and of course F4 help. You could still use Adobe forms if you implement this on the 640 system. However there are integration points with dialog and Adobe Interactive Forms. You could still use printed forms however. If you did the dialog program on the 640 system, you could use the integrated ITS to expose it to the web. The integrated ITS in my experience has quite nice performance although the look and feel remains just like the SAPGui.
The Java Webdynpro route: Well you hit the nail on the head - if you don't have a Java programmer already and you don't have the bandwidth to invest in learning Java, this can be a problem. The Java Webdynpro environment is quite nice. There are some things I like better than ABAP and some things that ABAP is defintely still better at. However when it comes to heavy integration with an ABAP backend - ABAP Webdynpro is still the way to go. Java Webdynpro does have a help feature (OVS), but it isn't "for free" or nearly as nice as the ABAP Webdynpro (perhaps it will get there some day). That is one of the major advantages of WDA - its closeness to the business data brings several framework advantages like F4 and field help. WebDynpro Java in 640 also doesn't have an ALV grid implementation. I am sure that this is something both environments will eventually have, but right now ABAP has the advantage. On the other hand, Webdynpro Java has equal support when it comes to office integration, file upload, and Adobe Forms support. You would have a more difficult time integration SmartForms however.
Finally we come to BSP. Honestly if I were in your position I would probably choose BSP (unless you could wait for the ABAP Webdynpro upgrade). You could build a nice MVC OO application using BSP (stateful or stateless). The BSP product is mature and quite well documented thanks to SDN. You have the BSP Extensions which when used in Design2003 use the Unified Renderer. That means that your output will look nearly identical to the same UI elements in Webdynpro. Also BSP supports portal integration (session management, eventing, and themes).
The downside to BSP is that it isn't a full framework (also one of its advantages). You can insert all your own html and javascript (unlike webdynpro). But this also means that SAP doesn't delivery as many framework services. For instance there is no ALV or Value Help. There is no Office Integration or Adobe Forms integration. There is some farily good Smart Forms integration. Now the upside- many people have already hit these limitations and overcame them. In the weblogs on SDN and in a certain SAP Press book (cough, cough) you will find out of the box solutions for many of these problems. You can find ready to use solutions for Adobe Integration, Office Integration (using Microsoft Office Web Controls), and F4 help. It will mean investing a little more time up front to get this "home grown framework" up and running - but it is perfectly feasible.
There is a learning curve to all these new technologies however. This sounds like an abmious project. I wouldn't want to try and tackle this project in any of these technologies if I was new to them. With Webdynpro or BSP - consider giving yourself time to learn the environment and cut your teeth on some demo apps before jumping into such a huge development.

Calling an ABAP WebDynpro Popup from a BSP view

I need to know if the following is possible.
I have a requirement to call an ABAP WebDynpro Popup from a BSP view.
When the Popup is triggered (eg via pushbutton) the BSP will pass data to the Popup, before the Popup is closed the Popup will pass data back to the BSP to be displayed in the BSP view.
I do not want to rely on Portal Events as Portals may not be used, would really appreciate a clean simple solution.

Hi,
any webdynpro application has a URL behind it. Haven´t you tried to call that URL with Javascript code ??
script language="Javascript"
url = "test_page.htm" + "?field=" + param;
window.open(url, "F4window", "width=400, height=400");
/script
You can pass data to the WD application using parameters as I show you after the "?".

Advantages of netweaver(webdynpro abap) comparing to sap(abap

plz tell me the advantages of netweaver(webdynpro abap)comparing sap

Hi,
Broken link removed
Also, I have the official Web Dynpro for ABAP documentation. Please let me know if I should send it to you.
Hope that the following also helps you.
Web Dynpro for ABAP (WD4A, WDA) is the SAP standard UI technology for developing Web
applications in the ABAP environment. It consists of a runtime environment and a graphical
development environment with special Web Dynpro tools that are integrated in the ABAP
Workbench (SE80).
Web Dynpro offers the following advantages for application developers:
● The use of declarative and graphical tools significantly reduces the implementation
effort
● Web Dynpro supports a structured design process
● Strict separation between layout and business data
● Reuse and better maintainability by using components
● The layout and navigation is easily changed using the Web Dynpro tools
● Stateful applications are supported that is, if the page is changed and the required
data remains intact so that you can access it at any time throughout the entire
application context.
Note that stateless applications are not possible.
● Automatic data transport using data binding
● Automatic input check
● Automatic operation of the Web Dynpro application using the keyboard
● User interface accessibility is supported
● Full integration in the reliable ABAP development environment
Web Dynpro Architecture
Definition
Web Dynpro is the SAP NetWeaver programming model for user interfaces (UIs).
The Web Dynpro model is based on the Model View Controller paradigm, and has the
following features that build on the classic dynpro model:
● Clear separation of business logic and display logic
● Uniform metamodel for all types of user interfaces
● Execution on a number of client platforms.
● Extensive platform independence of interfaces
Structure
Metamodel Concept
Web Dynpro provides support for developing Web representation of a business application.
You use specific tools to describe the properties of a Web Dynpro application in the form of
Web Dynpro metadata. The necessary source code is then generated automatically and
executed at runtime. In addition to the events offered by the framework, you can also define
your own events for a Web Dynpro application. However, the event handling must always be
programmed in separate source code areas which are executed automatically when the event
is triggered at runtime.
In Web Dynpro, each user interface is always made up of the same basic elements. These
elements of the metamodel can be statically declared using Web Dynpro tools.
It is also possible to implement elements of the metamodel at runtime and to change them or
reintegrate them at runtime. Using these implementations, you can make any changes or
enhancements to a user interface that has been created by declarative methods by
generating new interface structures at runtime.
This means that you can combine declarative processes and the implementation of source
code.
Graphical Development Tools
To support this declarative concept, both the SAP NetWeaver Developer Studio and the
ABAP Workbench contain a range of Web Dynpro tools. You can therefore generate a large
proportion of a Web Dynpro application using the tools provided, without having to create your
own source code. This applies to the following parts of the application:
● Data flow between the front end and back end
● Layout of the user interface
● Properties of user interface elements
The Web Dynpro tools enable you to create source text areas manually within generated
source texts. These areas are not changed if the source code is regenerated.
Separation of Business and Application Logic
Using Web Dynpro enables a clear separation of business logic and display logic. A Web
Dynpro application runs on the front end and has local or remote access to the back end
system via a service. This means that the display logic is contained in the Web Dynpro
application, while the business logic and the persistence of the business objects run in the
back end system. The following options are currently available for connecting Web Dynpro
applications and the back-end system:
● An interface generated using adaptive RFC, through which BAPIs of an SAP system
can be called
● An interface for calling Web services
● A self-generated interface
The source code required for connecting the Web Dynpro application can be generated
from a UML definition of the Web Dynpro interface. A UML definition can be imported
into the Web Dynpro tools as an XML file.
Conversion of the Model-View-Controller
Conversion of the Model-View-Controller Programming Model
Every Web Dynpro application is structured according to the Model View Controller
programming model:
● The model forms the interface to the back end system and thus enables the
Web Dynpro application access to data.
● The view is responsible for the representation of the data in the browser.
● The controller lies between the view and the model. The controller formats
the model data to be displayed in the view, processes the user entries made by the
user, and returns them to the model.
Web Dynpro ABAP Demonstration Videos
Regards,
Sree
Edited by: Jason Lax on Feb 2, 2012 4:44 PM

BSP and ABAP webdynpro

Hi wizards,
I am planning to start working on POC (Proof of concept). This requires BSP to be integrated with ABAP webdynpro. Can some throw some light on how this integration can be done. ie sharing the context values between both applications.
regards
Vivek Nidhi.

Well BSP and Web Dynpro ABAP are very different when it comes to internal architecture. Just because they both run in a browser doesn't mean they can be integrated like you describe. You could run both a BSP and Web Dynpro ABAP application in separate frames within the browser; however to the backend server these would be two completely separate processes running in their own memory space.
First of all you couldn't directly share the context values. BSP doesn't even have the concept of a context. You could pass some keys via URL parameters or Server Cookies. You might even be able to pass larger amounts of data. However the eventing becomes a bit of problem. The exception here is if you use the NetWeaver Portal. Then you can use Portal Eventing to pass data and events between the two applications.

Pass value from webdynpro abap application to bsp application

Hello,
I want call api bsp javascript from WDA exchanging values between the two applications.
I have a solution but it is with portal integration.
I would like a procedure without using the portal.
Webdynpro and BSP only.
How can I do this ?
Thanks for your help.

Hi,
Refer these threads-
Re: Passing Object ref to Webdynpro Application while calling from BSP screen
Both BSP and WDA has an URL associated with it.
In the WDA, create an LinkToUrl UI element upon which triggers the BSP application and pass the parameters to this BSP application. Check for this BSP application has also parameters in it.
Refer this link Re: Read SICF URL
Regards,
Lekha.

ABAP webdynpro app not redirecting using Outbound plug in portal

Scenario-
There is one Abap webdynpro application APP1 calling another abap webdynpro component Comp 2 through outbound plug on a button click. This is working fine if service is tested independantly.
SAP ECC system is having a webispatcher and the application should be accessed using webdipatcher only i.e. ECC should not be called directly.
SSL has been configured b/w ECC and webdipatcher.
The Abap webdynpro application APP1 is integrated into portal using Abap webdynpro iview.
Setting in Portal system are reffering to Webdipatcher for ECC system instead of ECC system directly.
Issue-
App1 is loading successfully into portal and all the data is coming properly but when trying to navigate to second component on button click it is not navigating. iview is getting refreshed but not redirecting to required component and is still on the same application.
Please suggest the reasons and solutions if anyone has clue about it.
Regards
Deepak

Hi,
Please refer to these links -
How to secure WDA over an external facing portal
WebDynpro ABAP and Portal Navigation
WebDynpro ABAP and Portal Navigation problem
Please check for the portal eventing between the applications.
Regards,
Lekha

How to display HTML files using ABAP Webdynpro?

Hi,
I have a html index file and a bunch of other files accessed by the index file in a specific directory on the SAP server. I'd like to display the index file via ABAP webdynpro and allow the users to click on what they need to see. How can I achieve this using utilizing the ABAP webdynpro technology ?
Thanks!

Hi Thomas,
Thanks for taking the time to answer my question.
I have the main html file and all other files needed by the main file in one directory on the application layer of SAP. I'd like to provide the user with a link, by clicking on which they should be able to get to the main html file using the browser. This is just a standalone application.
I can try the approach using BSPs, however, I'm new to that area. Could you point me in the right direction to get started?

ABAP webdynpro or webservices

hi all,
I have an question. I have a system where i can use the ABAP webservices or the ABAP webdynpro to send data to a flex application.
But which of those 2 is the best solution? Or doesn't it matter which one i choose?
Do you have found some (dis)advantages for the solution with the webservices or do you have found some (dis)advanteges found with the solution with the ABAP webdynpro?
Kind regards,
Anton Pierhagen

Hi Anton,
If comparison done between Web Dynpro having Flash Island for Flex components and Independent Flex application communicating with R/3 via RFCs then in many aspects Web Dynpro is better option.
If backend is R/3 then anyways you have all required infrastructure in place no need of any other servers in case of WD. But if you go for 2nd option then may be for hosting swf files you need WAS or any other server.
There might be some cases where you need to fetch lots of data from DB then using SOAP way i.e. RFCs could give you time-out during data retrival at Flex frontend ( very rare case but there is possibility).
You can use your WD to handle all business logic and Flex components only for presentations like charts, interactive components etc.
One majot advantage of WD will be security aspect which can be handle very easily ( even with Single-Sign-On) whereas in independent Flex application you might end-up with extra security inception other than basic authentication of RFCs on load.
these are few differences out of many others which i can tell you.
Though both options you are thinking are good and feasible but i would suggest Web Dynpro. (Anyways being SAP Partner also we should promote SAP investments )
Regards,
Vivek
Edited by: vivek khedekar on Sep 23, 2010 6:08 AM

Print button in ABAP WebDynpro

Hello all,
The client has requested a 'Print' button in our webdynpro application - ie a simple button that triggers the browser command Ctrl P.
I have searched the forum, and it seems that this is not possible, because WebDynpro cannot execute browser commands (or indeed, javascript).
Can someone please suggest a solution - OR - confirm that this functionality is not possible?
thanks
Paul
Note: Note: We do NOT want to use ALV, Adobe or Smartforms. We just want to print what's on the webdynpro screen.

Micky,
I thank you for that clear response: It is not possible to print from ABAP WebDynpro.
> What should that printbutton do?
We want it to do the same as Ctrl P, which is to print the entire web page. (We don't have frames etc)
>WD4A is normally intended to be used with Adobe Interactive forms
This is news to me! Is this an accepted view in the SAP communit... that WebDynpro requires Adobe to achieve full functionality? That is disappointing, to say the least. And a step back from BSP.
We are building multiple online calculators, and it would be a huge overhead to have to develop (and maintain) an Adobe form for each calculator, simply to enable the user to print the contents of the screen....
I have read in SDN that you can invoke a browser Print command from Java Webdynpro. A class WDPrintService has been provided.
Printing in Web Dynpro, finally
How can it be that this functionality is "not possible" for one flavour of WebDynpro, but plainly available in the other....?
cheers
Paul

Calling Javascript from ABAP webdynpro application

Hai All,
I want to call a Javascript from ABAP-Webdynpro application. If anyone has done this. Please let me know.
Thanks & Regards,
H.K.Hayath Basha.

go to window
create suspend outbound plug and resume inbound type
when create an outbound plug of Suspend type a parameter Url is automatically created,
fire the outbuond plug with the Url to a BSP page where you have JavaScript.
and fromt he BSP navigate back to WDA again which you can do using by reading the url parameter sap-wd-resumeurl, which contains the WDA URL
Abhi

WebDynPro vs BSP

Hi,
As far as I can tell, WebDynPro and BSP are competing technologies. They both basicly accomplish the same goals although in different ways. So how do I know which technology is best for my company? Should I base it on our internal goals & strategies and look at the technologies or should I be looking at other factors?
-John

Hi John,
Well, I am not working for SAP. But what I see right now, is that everything is moving to WebDynpro. As an example, Personnel Change Requests - MSS (available for ITS, BSP, JSP and Adobe) are moving to an encapsulated WebDynpro application with Adobe Forms in it.
What I expect is that over a few years WebDynpro is the standard, and BSP is old technology.
To make sure your decision will be based on a strategy decision, maybe a customer message will help you further.
Regards,
Noel
PS. Did you know that if you are satisfied with my help, you can award points by clicking on the star?

BAPI or RFC Required to in ABAP webdynpro

Hi All,
I am new to the ABAP webdynpro. But i have experience in JAVA webdynpro. In JAVA WD , will access the back system functionality using RFC. But if comes to ABAP WD, is it required the RFC or BAPI?
If required why it is required? what is the advantage of using the BAPI or RFC in ABAP webdynpro? Because ABAP WD is running on the same system.
If not required ? what is the advantages of with out using BAPI's
Please let me know what are pros and cons for the using the BAPI or RFC in ABAP WD.
Regards
Vijay

Hi vijay,
Firstly welcome to our webdynpro learning world . :). As you said you are already aware of the wendynpro java . Almost all same functinality it follows as webdynpro abap, the thing which it differs is
for java to interact with the RFC or the Bapis u need to interact with the other engine but since u are working into the same area line webdynpro abap need not calll any other specific engine as the RFC or teh BAPI s reside in the same workspace . Simple!.
Hope you are aware of the MVC functionality which our webdynpro follows so these bapis and RFCs firstly they are reusable and the other importance is generally we run our webdynpro applications by embeding our applications into portal so for that sake we make our (rfc and BAPI s )are remote enabled.
such that our webdynpro applications run .
Hope it would help you .
Happy learning. Have a Good Day!
Regards,
Sana.

WebDynpro or BSP ?

Hi all,
when should i use WebDynpro and when BSP ?
What is the prefered Environment to write Internet Apps for SAP ? Will BSP have a future or is it old style development and we should use WebDynpro for our future Development ?
Henning

This topic has been discussed quite alot here, check these three links for all information.
BSP vs WebDynpro (ABAP)
[url=Re: BSP going to be obsolete?]BSP going to be obsolete?[/url]

Advantages of ABAP Webdynpros over BSP??

Similar Messages

Maybe you are looking for