ECC 6.0 Webdynpro for ABAP development environment

Hello,
We are currently running ECC 5.0 and ABAP stack is only available as of ECC 6.0. Is is possible to download and install just ECC 6.0 development environment?
Thanks,
Alex

The ABAP development environement and runtime are integrated into the Business Suite release. Therefore ECC 5.0 runs on top of NetWeaver 2004 (6.40) and ECC 6.0 runs on top of NetWeaver 7.0. There is no way to directly mix ECC/NetWeaver releases nor can you directly transport NetWeaver 7.0 objects (like Web Dynpro ABAP) to a 6.40 based system since the runtime wouldn't be present.
You can however install a standalone NetWeaver Systems. Then you would have a separate instance with the ABAP 7.0 developement and runtime environement. You can use RFCs and Web Service Calls from this standalone system to read and write data to/from your ECC 5.0 system. You give up some of the benefits (like the integrated DDic value-help).

Similar Messages

In webdynpro for ABAP alv table issue

hello gurus,
                  i am new for webdynpro for ABAP.i strucked at one point at designing time.anybody could you suggest me on this.
thanks in advance.
let me explain my scenario first.
in my webdynpro for ABAP developement i have one alv table having ten fields.i am featching the data for eight fields from one Ztabale and updating , for rest of two fields we need to fill after displaying output using the respective F4 help. Right now these two fields are in input editable mode.now i am getting the values successfully from F4 help and at the same time it is allowing MANUAL ENTRIES also but as per my requirement it should not allow any manual entries . for this i have made these two fields are in readonly mode as like as rest of fields to avoid the MANUAL ENTRIES but at this time i didnot get any F4 helpfor those two fields.
so how can i achive my goal in this thing could any one suggest me.
my final conclusion is we need to get only F4 help values into those two fields . it should not allow any manual values at any point of time.
best regards,
babu

ya hi harshit,
      my self also used same code in my action part . here i have one table with four fields carrid , connid , fldate , price.
for carrid i have created freely programmed search help.but if it is in display mode there is no F4 help in enable mode.
in context for attribute carrid
DATA lo_nd_flight TYPE REF TO if_wd_context_node.
DATA lo_el_flight TYPE REF TO if_wd_context_element.
DATA ls_flight TYPE wd_this->element_flight.
DATA lt_flight TYPE wd_this->elements_flight.
navigate from <CONTEXT> to <FLIGHT> via lead selection
lo_nd_flight = wd_context->get_child_node( name = wd_this->wdctx_flight ).
select connid fldate price from sflight into CORRESPONDING FIELDS OF TABLE
    lt_flight UP TO 20 ROWS.
@TODO handle non existant child
IF lo_nd_flight IS INITIAL.
ENDIF.
get element via lead selection
lo_el_flight = lo_nd_flight->get_element( ).
alternative access via index
lo_el_flight = lo_nd_flight->get_element( index = 1 ).
@TODO handle not set lead selection
IF lo_el_flight IS INITIAL.
ENDIF.
get all declared attributes
lo_el_flight->get_static_attributes(
   IMPORTING
     static_attributes = ls_flight ).
CALL METHOD lo_nd_flight->bind_table
EXPORTING
    new_items            = lt_flight
   set_initial_elements = ABAP_TRUE
   index                =
DATA: lo_cmp_usage TYPE REF TO if_wd_component_usage.
DATA: lo_interfacecontroller TYPE REF TO iwci_salv_wd_table.
    instantiate ALV component usage if necessary
lo_cmp_usage = wd_this->wd_cpuse_alv( ).
IF lo_cmp_usage->has_active_component( ) IS INITIAL.
    lo_cmp_usage->create_component( ).
ENDIF.
    pass reference to data node to instance of ALV usage
lo_interfacecontroller = wd_this->wd_cpifc_alv( ).
lo_interfacecontroller->set_data( r_node_data = lo_nd_flight ).
Configure ALV
DATA lr_config TYPE REF TO cl_salv_wd_config_table.
lr_config = lo_interfacecontroller->get_model( ).
**declerations
DATA: lt_columns TYPE salv_wd_t_column_ref,
        ls_columns TYPE salv_wd_s_column_ref,
        lr_input TYPE REF TO cl_salv_wd_uie_input_field,
        name TYPE string,
        lt_node_info TYPE wdr_context_attr_info_map,
        ls_node_info TYPE wdr_context_attribute_info,
        lv_tabix TYPE sy-tabix,
        lr_info TYPE REF TO if_wd_context_node_info.
TYPES: BEGIN OF ty_name,
          name TYPE string,
         END OF ty_name.
DATA: lt_name TYPE TABLE OF ty_name,
        ls_name TYPE ty_name.
**for getting node info
*Get the context node information
lr_info = lo_nd_flight->get_node_info( ).
lt_node_info = lr_info->get_attributes( ).
LOOP AT lt_node_info INTO ls_node_info.
    CASE ls_node_info-name.
      WHEN 'CARRID'.
        ls_name-name = ls_node_info-name.
        APPEND ls_name TO lt_name.
     WHEN 'REGIONALOFFICER'.
       ls_name-name = ls_node_info-name.
       APPEND ls_name TO lt_name.
     WHEN 'INSPECTORNAME'.
       ls_name-name = ls_node_info-name.
       APPEND ls_name TO lt_name.
    ENDCASE.
ENDLOOP.
*Logic for Table Horizontal Scrolling
lr_config->if_salv_wd_table_settings~set_visible_row_count( 13 ).
" lr_config->if_salv_wd_table_settings~set_width( '1085' ).
lr_config->if_salv_wd_table_settings~set_width( '100%' ).
lr_config->if_salv_wd_table_settings~set_scrollable_col_count( 8 ).
" lr_config->if_salv_wd_table_settings~set_fixed_table_layout( abap_true ).
lr_config->if_salv_wd_table_settings~set_first_visible_scroll_col( 'CARRID' ).
lr_config->if_salv_wd_table_settings~set_cell_action_event_enabled( abap_true ).
Set the table editable .
DATA: lr_table_settings TYPE REF TO if_salv_wd_table_settings.
lr_table_settings ?= lr_config.
lr_table_settings->set_read_only( abap_false ).
lr_table_settings->set_read_only( abap_true ).
DATA: lr_column_settings TYPE REF TO if_salv_wd_column_settings,
        lr_column TYPE REF TO cl_salv_wd_column.
DATA: lt_string TYPE STANDARD TABLE OF string,
        ld_string TYPE string,
        ld_int TYPE i,
        lv_index TYPE i.
Make few columns editable and attach inputfield, if permitted.
    DATA lr_input_field TYPE REF TO cl_salv_wd_uie_input_field.
    CLEAR lt_string.
    APPEND 'CARRID' TO lt_string.
    LOOP AT lt_string INTO ld_string.
      lr_column_settings ?= lr_config.
      lr_column = lr_column_settings->get_column( ld_string ).
      CREATE OBJECT lr_input_field
        EXPORTING
          value_fieldname = ld_string.
      lr_input_field->set_read_only( abap_true ).
      lr_column->set_cell_editor( lr_input_field ).
    ENDLOOP.
    CLEAR lt_string.

The new features avilable in webdynpro for abap with EHP5

Hi,
Currently our ECC 6.0 is upgraded with EHP5 from EHP3.
Could anyboy tell me the new featues available in webdynpro for abap for this EHP5. If i develop WDA objects in EHP3 environment and transport it to new system with EHP5 . What would be the problems i encounter. kindly suggest me..
thanks,
Raghu

I would expect in any case that there is no problem when you transport WDA build from ehp3 to ehp5 (Backward compatibility ).

Reqs for Webdynpro for ABAP

Hi All,
We are planning to integrate WebDynpro runtime environment in ABAP workbench.
We are currently on WAS 6.20. I wanted to know how can we upgrade to WAS 6.0. Will just applying patch would be enough...?? ..
What else we will need to set up developement environment for Webdynpro for ABAP..??
Thanks and regards.

Is this a standalone WebAS 620? In that case you would have to upgrade the entire system to Netweaver04S. There is no simple patch or add-in that you can install to give you Web Dynpro ABAP.
If this is an R/3 system running on top of WebAS 620 - that would R/3 Enterprise 4.7; then you would have to upgrade the entire application to ERP2005. ERP2005 is the "version" of R/3 (actually ECC 6.0) that runs on top of Netweaver04S. If this is any other application then you would have to upgrade to the appropriate release level that runs on top of Netweaver04S in a similar manner.

Webdynpro for ABAP versus Enterprise Services

Hi,
With ECC 6.0 the WebDynpro for ABAP will be available. After converting my well-known ABAP-dynpro screens to WebDynpro I will have the possibility to expose all R/3 functionality from within the portal.
Two years from now the Enterprise Services will be there. What will be the reason(s) for using enterprise services instead of WebDynpro for abap to make R/3 functionality available in the portal? I think at the end both functionalities can co-exist but what are the criteria to use one or both methods?
Greetings Theo

Theo,
This is not a discussion relegated to the bar...
First the short methodology is correct... Id the processes, expose major entry points as Services, orchestrate, publish Service Desc, endpoints, etc., repeat...
The real question remaining is, if I believe my entire process is incorporated with a single SAP system why would I expose Services (and add the additional layer)?
I agree with the comment where if a process completely executes in a single environment there is no need to change its strategy and force it to be an orchestrated set of Service interactions. That is not inconsistent with providing Service interfaces along the process so that it can be composed into other processes either not yet in place or requiring cross-system interaction. ESA is not saying "break open the container and make every little piece operate as Enterprise Services", instead it guides us to Service enable components so that others can consume them in a standard way, regardless of implementation / execution environment.
As we think about leveraging ESA for the benefit of our businesses (our enterprise and the ecosystem of business partners and customers) we have to acknowledge that we do not and will not know where every step of a busines process will execute throughout time. There may be tremendous value in executing part of a process that could be performed in that same SAP system in a completely different environment. The main benefit of Service enabling is business agility for a reasonable cost. I would argue that at least the main entry and exit points to major processes should have Service interfaces, followed by a more comprehensive assessment of internal process steps - looking for opportunities.
The other side of the equation is determining what additional consumers of the process could be found if major parts of the process exposed Service interfaces. To say, "my process executes inside this one system, so I should not expose it as a set of Services", ignores the potential benefit of other systems being able to incorporate that process in their execution (or parts of a process). As we expose more, well defined Services that represent aspects of enterprise business processes we create an environment where there is low cost, opportunistic integration based on standards.
Or put more briefly, make sure to execute your business process in an efficent computing manner, but do not let that constraint limit your thinking when it comes to Services. They are two different (yet related) issues. Services simply give us another way to leverage an asset we already have. Make the asset available and if it has value to the organization, it will be consumed.
Hope that helps...
David

How can we benefit from WebDynpro for ABAP over Normal ABAP

Dear Guru's,
Please guide me what are +Ves of WebDynpro over Normal ABAP. Once all Applications are developed how can we organize them. For Example In SD module there is sequence of Tcodes to be executed this is true for all modules . Is there any concept involved in this new technology.
For What purpose we can suggest someone to implement in an Organization.
Many Thanks in Advance.
Regards
Ram

Hi Ram,
Here Are some comparisions I made w.r.t Webdynpro for ABAP (also some benifits over Java):
1     "Pros:it will be easier to move your development project through the system landscape if both the UI and business logic are in the same development environment.(Update: This is is less of a concern now that CTS+ lets you bundle your WD Java UI developement with ABAP development objects into a single transport, with SPS13. )
2     tons of custom ABAP business logic is easier to access via WD for ABAP
3     WD for ABAP has a code wizard, so easy to build
4     SAP List Viewer and ALV handled better
5      The biggest thing is the NWDI. Most of the SAP customer have ABAP stack, but not everyone has the Java stack. To develop WD Java you need to set up the NWDI envrionment, like SLD, CMS, CBS, DTR, etc. which is a huge effort if you don't have them in place. While for WD ABAP, the environemnt is normally there as given for most of customers if they have the right version.
6     If your business is in SAP system, I would prefer WD ABAP. There are many WD components available in WD ABAP like select-option, Alv table, F4-help which are not available in WD Java. Beside in WD ABAP you can deal the context node in form of internal table which is much more performant than dealing with the contextelement which is the case for WD Java.
Regards,
Tanaya
Edited by: Tanaya A on Dec 10, 2009 6:19 PM

Eventing in Portal page between Team Viewer and Custom Webdynpro for ABAP

We are trying to implement a new Portal page that contains a Team Viewer Iview and a custom Webdynpro for ABAP iview.
The idea is that the when a manager select one of his direct report in the Team Viewer, the custom Webdynpro for ABAP would pick up the selection_changed event and retrieve the data for the selected employee.
We followed the instruction provided by SAP in note 1112733 and it worked in our development environment. When we moved the iviews to our testing environment it stopped working.
I also used the Diagnostic Iviews provided by SAP and I get the same result: Works in Dev, does not work in QA or in Prod.
We also followed the troubleshooting steps of note 945516 and it still did not help us. We can not find a difference in our system set up.
We are therefore looking for pointers as to what could be our problem.
Thanks!
Edited by: Benoit Fortin on Feb 20, 2009 2:28 PM

Problem was solved internally:
The reasons the eventing worked in Dev and not in QA or Prod, was that we had a different level of patch for ESS/MSS between instances, which I was not aware of.
Dev was on ESS/MSS version 600 SP14 and QA and Prod was on a different level. Once we implemented ESS/MSS SP 14 accross the board, everything was good.
Edited by: Benoit Fortin on Nov 13, 2009 11:57 AM

IS Webdynpro for ABAP/JAVA is same?

Hi Friends,
I'm a SAP technical consultant. I would like to learn webdynpro for ABAP. Can anyone of you tell me webdynpro for ABAP and webdynpro for JAVA are same? with webdynpro for ABAP Can we acheive what we can do with webdynpro for JAVA?
Thanks in advance,
venkat.

hi,
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
Web Dynpro is available both in the Java and the ABAP development environment.
Web Dynpro for Java
http://help.sap.com/saphelp_erp2005/helpdata/en/15/0d4f21c17c8044af4868130e9fea07/frameset.htm
Web Dynpro for ABAP
http://help.sap.com/saphelp_erp2005/helpdata/en/a5/1a1e3e7181b60ae10000000a114084/frameset.htm
best tutorials in wbdynpro for ABAP to start with :
https://www.sdn.sap.com/irj/sdn/developerareas/webdynpro?rid=/webcontent/uuid/fed073e5-0901-0010-4eb4-c9882aac7b11

Webdynpro for ABAP call non-SAP webservice

Hi,
We have a WAS 7.0 ABAP only, Can we use webdynpro for ABAP to call a Notes's webservice or Weblogic's webservice.
Where can I get the document link?
Edited by: Jeff Lien on Jan 8, 2008 10:47 AM
Edited by: Jeff Lien on Jan 8, 2008 10:49 AM

Hi this will help u.
Web Dynpro ABAP
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/db22242d-0701-0010-28a2-aeaa1fefd706
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.
/people/thomas.jung/blog/2006/06/20/web-dynpro-abap-demonstration-videos
http://help.sap.com/saphelp_nw04s/helpdata/en/77/3545415ea6f523e10000000a155106/frameset.htm
with regards,
Hema.
pls give points if helpful.

Webdynpro for ABAP materials

anyone please send me materials for webdynpro for abap which covers webdynpro architecture like mvc controller and everything

Hi Ganesh,
Welcome to Web Dynpro ABAP !
In web dynpro ABAP we follow MVC(Model View Controller) architecture.
In this object oriented ABAP is used to provide background functionality. Here, your ABAP skills can be utilized to the fullest. Programming in web dynpro ABAP is different than conventional ABAP programming. Here we strictly follow MVC architecture in terms of controller interface. Also there are many wizards available so that we can directly pick the code from wizards.
e.g We can call BAPI through a service call in web dynpro application. Thus automatically backgroud code for BAPI execution will be generated.
To start with Web dynpro ABAP you can try following tutorial:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a282c952-0801-0010-1eb5-87953e036712
You can start with tutorials and all. There are around six tutorials in SDN library.
Web Dynpro for ABAP
http://help.sap.com/saphelp_erp2005/helpdata/en/a5/1a1e3e7181b60ae10000000a114084/frameset.htm
best tutorials in wbdynpro for ABAP to start with :
https://www.sdn.sap.com/irj/sdn/developerareas/webdynpro?rid=/webcontent/uuid/fed073e5-0901-0010-4eb4-c9882aac7b11 [original link is broken]
1) This is basic Info of WD ABAP
As the name suggests Web Dynpro for ABAP uses exactly the same meta model as its cousin Web Dynpro for Java. A Web Dynpro component, a Web Dynpro view, a Web Dynpro model, a Web Dynpro controller have the same semantics both for ABAP and Java. The main difference is the designtime environment, the development infrastructure and the runtime environment.
The designtime environment is properly embedded in the ABAP Workbench where Web Dynpro artifacts are simply a new category like BSP applications or classical dynpro based applications before. Also no surprises regarding the development infrastructure. The correction and transport system keeps track on all changes that are done, versions them and helps to propagate the Web Dynpro application from development to production like you would do with ordinary BSP or dynpro-based applications.
Last not least the execution platform is the ABAP server that produces application content ready to be integrated in the NetWeaver Portal seamlessly. Features like portal eventing can be used between applications written in ABAP or applications developed with Java.
2 ) I can give you links that can help you a lot.
First of all start doing SAP SDN tutorials .
Create some compenents with BAPI , Component usage and ALV .
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/02e1fa45-0801-0010-10a0-f1cf47e8c943
/people/marilyn.pratt/blog/2005/12/20/web-dynpro-for-abap
Try to Download demo tutorials from SDN library & Try to search WebDynpro ABAP WebLogs .
Also, SAP has provided you with ample demo example of WD ABAP already bundled with SAP . Just Try out Components starting with WDR . I can tell you few like WDR_TEST_EVENTS ( It shows how every UI elments to use )
See packages like SWDP_DEMO , SALV_WD_DEMO
there are many more .
Hope I have helped you .
Cheers,
Darshna.

Comparison between WebDynpro for ABAP vs. WebDynpro for Java ??

Hi,
Can someone tell me when should we go for WebDynpro for ABAP and when WebDynpro for Java. Is there any link where SAP recommends the one for the other.
Thanks in advance
Regards
Mukesh

Hi Mukesh,
Both are having its own strengths!! )
I think it all depends on your project requirement and the availabel resources.
If the developer is good in OOPs ABAP then he must go for Web Dynpro ABAP. But if anyone is good in JAVA then that person should go for Web Dynpro JAVA.
*In Short almost all Features supported in webdynpro ABAP are also Possible in webdynpro Java.
1] Webdynpro Java
Supports,
webservice
RFC Models
Accessing Portal information in Java
Easy sending E-mail
Strictly follows MVC architecture which seperate Business logic and Process flow.
Webdynpro Java is webbased programming model to develop SAP Applications.
Easy to learn
Easy to integrate in Enter prise portals.
Dynanamic Programming
*Easy access to R/3 Via RFC technology (Models)
2] Web Dynpro ABAP
As the name suggests Web Dynpro for ABAP uses exactly the same meta model as its cousin Web Dynpro for Java. A Web Dynpro component, a Web Dynpro view, a Web Dynpro model, a Web Dynpro controller have the same semantics both for ABAP and Java. The main difference is the designtime environment, the development infrastructure and the runtime environment.
The designtime environment is properly embedded in the ABAP Workbench where Web Dynpro artifacts are simply a new category like BSP applications or classical dynpro based applications before. Also no surprises regarding the development infrastructure. The correction and transport system keeps track on all changes that are done, versions them and helps to propagate the Web Dynpro application from development to production like you would do with ordinary BSP or dynpro-based applications.
Last not least the execution platform is the ABAP server that produces application content ready to be integrated in the NetWeaver Portal seamlessly. Features like portal eventing can be used between applications written in ABAP or applications developed with Java.
Hope this helps and solve your Problem
Cheers,
Darshna.

What is used for WebDynpro for ABAP?

hi all friends,,
what is used for WebDynpro for ABAP?
Thanks,
S.Suresh.
Title was edited by:
        Alvaro Tejada Galindo

Hi
Web Dynpro for ABAP - Getting Started
Web Dynpro for ABAP is SAPs new standard UI technology for developing user interfaces in the ABAP environment. In the long term Web Dynpro for ABAP will be the successor of the traditional screen (Dynpro) based user interface technology which is based on the SAP GUI. Available with NetWeaver 7.0 (2004s) Web Dynpro for ABAP provides the same declarative UI development paradigm as Web Dynpro for Java directly out of the NetWeaver ABAP Application Server. Web Dynpro for ABAP allows the development of user interfaces directly within the ABAP Workbench (SE80) and the Web Dynpro runtime environment is a central part of the ABAP server and can be used in any SAP solution based on NetWeaver 7.0 (2004s) without the need of an additional server installation.
Web Dynpro for ABAP allows the development of user interfaces in a declarative way by providing a mighty framework which abstracts the rendering technology from the core UI definition tasks. The Web Dynpro developer declares the layout and behavior of the UI without caring about HTML, JavaScript, browser specifics or the HTTP protocol. Instead the focus lies on designing graphically Web Dynpro components based on the Model View Controller model, which enforces a clear separation between the UI layer and the underlying business logic.
This declarative Web Dynpro programming model enforces the developer to focus on the tasks of
Designing the layout of the visible views (where should the table be placed, do I need tabs, how should the button look?)
Declaring the flow and behavior of the application (flow between views, which event is triggered by which button click, etc)
Defining the data binding (which internal table is displayed in a specific table, etc)
Implementing the event handlers and controller methods.
Without making any assumption about the used rendering technology, like which browser should be supported or if the Web Dynpro application will be later displayed in a web browser via HTML at all or in another kind of client with completely different rendering capabilities.
The Web Dynpro Frameworks provides all important UI features directly out of the box:
All elements (tables, buttons, trees, dropdown list boxes, etc) necessary for state of the art user interfaces are provided by the Web Dynpro Framework in the form of predefined UI element libraries.
Complex features and behavior of UI elements.
Internationalization of the UI. All visible strings in a Web Dynpro ABAP UI are handled by the translation system and are translated in the same translation environment like other ABAP language dependent resources. All texts are displayed automatically at runtime, dependent of the users credentials.
Accessibility features are directly built into the framework and UI elements.
A unified rendering engine generates at runtime the data which is sent to the specific client application, which is not limited to browsers but includes the NetWeaver Business Client.
All this is available in the established environment of the ABAP application server and well known capabilities like the transportation and change management system, security environment, test and performance analysis tools or remote debugging can be used like in common ABAP development.
Learn about the Web Dynpro for ABAP technology with the resources below, and post your related questions and answers to the Web Dynpro forum.
Web Dynpro for ABAP: Sneak Preview
Download, License Key Documentation, and Installation Guide available here.
Web Dynpro for ABAP: Tutorials for Beginners
SAP NetWeaver Product Management provides this set of tutorials for getting started with Web Dynpro for ABAP technology.
SAP Help Portal: Web Dynpro for ABAP
This online SAP documentation goes into detail about Web Dynpro architecture and programming, Web Dynpro for ABAP administration and security, and more.
Web Dynpro - Not Just for Java Developers Anymore   (PDF 3.8 MB)
In this SAP Insider article, SAP Product Manager Karl Kessler describes the tools of Web Dynpro for ABAP and uses a simple flight report example to highlight new and updated tools in the familiar ABAP environment.
Community Contribution: WDA Tutorial I - Getting Started with Web Dynpro for ABAP   (PDF 2.5 MB)
Software Engineer Rich Heilman provides this step-by-step guide for developing a Web Dynpro for ABAP application.
Going into Details
Basic Concepts - Selection vs. LeadSelection
In this blog, Thomas Szuecs of the Web Dynpro for ABAP development team shows how selection and LeadSelection works in Web Dynpro for ABAP.
Web Dynpro for ABAP: Recreate the SE16 Data Browser   (PDF 386 KB)
In this tutorial, Thomas Jung of SAP NetWeaver Product Management shows how to create a data browser simulator using Web Dynpro for ABAP.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/80aef577-543f-2a10-d19c-d83a565efe37 [original link is broken]
<b><REMOVED BY MODERATOR></b>
Message was edited by:
        Alvaro Tejada Galindo

Follow-up webdynpro for abap using portal theme nw2004s, sp12

Hello,
I wanted to get a follow up to this thread,
Re: webdynpro for abap using portal theme nw2004s, sp12
We are having a problem with the way reports developed in Web Dynpro for ABAP displayed in the portal (the pop-ups and dropdowns look out of wack). The issue appears when we wrap the reports into portal themes (either standard or custom). As per the thread (the link for which I posted above), the suggestion was to apply WDFORCEEXTERNALSTYLESHEET parameter to the WDP, however our system doesn't have this parameter in the system, but it seems like I can create my own parameter. Can some on give me all of the properties assigned to WDFORCEEXTERNALSTYLESHEET in table WDY_APP_PROP_DEF.
Thank you

Hi Brad, I was trying to apply the note 1033496 but our ABAP servers does not have the WDFORCEEXTERNALSTYLESHEET parameter available in WDY_APP_PROP_DEF table. All other notes are not applicable to our issue.
The portal is NW2004s SP12, the ABAP server is NW2004 SP11
Regards.
Message was edited by:
Aleks Ozerov

Not able to integrate Payment Gateway with WebDynpro for ABAP

Hi,
   I am not able to integrate the Payment Gateway for Billdesk ( third party software) with Webdynpro for ABAP.
Summery of the Issue : -
(*) Data from PORTAL Application to PAYMENT GATEWAY is going Correctly but
(*) Data from PAYMENT GATEWAY to PORTAL Application is not going correctly.
Details about the Problem : -
   I have created 3 View in Webdynpro Application for ABAP.
View 1 -> Sales Order
View 2 -> Confirm Order
View 3 -> Success Message
When I am on the View 2 i,e Confirm Order, I have a UI Element ( LINK TO URL) on this View. When I click on the Link it successful takes me to the Bill desk site(Payment Gateway Integrator).After selecting the Card Type - > Master card, or Visa or Amex, I am routed to the Gateway Site of the Citibank, Where I have to enter the CARD details like Card Number, CVV Number, Expiry Date, and press the Submit Button.
Which now takes me to the final confirmation site, stating
1) Order Number
2) Bank ID
3) Merchant ID
4) Amount
5) Authorize ( APPROVED / NOT APPROVED)
Now once i click on the Submit button, It transfers the amount of the Customer to my bank account, correctly and goes back to the my portal application.
Till here it is working correctly, but 1 parameter is missing which is called "msg", and this parameter contains important information regarding the payment. This parameter is sent back form the Gateway Site to my Portal.
1) Authorize STATUS
2) Check Sum
etc... which will be finally required to decided whether I should go on to create the Sales Order for the Customer or not.
If the Authorize Status = '0300' then only create the Sales Order other wise if the status is any thing else lets say not equal to '0300' then gives the message that the Credit Card is not authorize to process the Sales Order.
Regards,
Saurabh Bhatnagar
E : [email protected]

Dear Sir,
we are implementing Retail POS (Point of sale) for one retail company. We need to integrate third party payment gateway.
it's name is PLUTAS. We have got developer kit from Plutas (For trial ) . we have installed that kit in our system.
In my program, I am triggering " PL_TriggerTransaction" using call method. After triggering method it executes method, control passes to third party software. But I am not able to catch return parameter (Responce).
So that would be great if you help me out with this issue.
I wrote following code.
REPORT ZTEST678.
INCLUDE OLE2INCL.
data : rc_plutus type ole2_object,
lpszTransData type string,
lTxnType type char4,
lpszTransData1 TYPE string,
ret_string TYPE string,
l_count TYPE i,
l_time TYPE sy-uzeit.
rc_gui type ref to CL_GUI_CONTROL.
lTxnType = '4001'.                        "----
transaction type
lpszTransData = '1234567'.          " -
trasaction data
*create object rc_gui.
create object rc_plutus 'PLUTUSEXCHANGE.EXCHANGEOBJ'(001) no flush. "no flush ."queueonly.
call method of rc_plutus 'PL_TriggerTransaction'(002) = lpszTransData1
exporting
#1 = lTxnType
#2 = lpszTransData.
wait up to 20 seconds.
write: ret_string.                        " <----
Value is not coming
write: lpszTransData1.            " <----
Value is not coming

Is DD/MM/YYYY supported in webdynpro for abap application

Hi All,
We are using 2 different time statements one developed in webdynpro for java and other in webdynpro for abap.date format in java is DD/MM/YYYY but in webdynpro for abap is DD.MM.YYYY.
is DD/MM/YYYY supported in webdynpro for ABAP application or even if user enters DD.MM.YYYY can we convert that to DD/MM/YYYY so that we will maintain uniformity in both the applications
Thanks
Bala Duvvuri

Hi Bala,
We can convert the date before saving ,even if the user enters the date as dd.mm.yyyy as mentioned below.
DATA: lv_indicator type XUDATFM .
CALL FUNCTION 'ISH_GET_USER_DATE'
EXPORTING
    USER_NAME         = SY-UNAME
IMPORTING
    DATE_FORMAT       = lv_indicator .
CASE lv_indicator.
    WHEN '1'.                                        " DD.MM.YYYY
      CONCATENATE p_date6(2) '.' p_date4(2) '.'
                  p_date(4)
         INTO p_result.
    WHEN '2'.                                        " MM/DD/YYYY.
      CONCATENATE p_date4(2) '/' p_date6(2) '/'
                  p_date(4)
         INTO p_result.
    WHEN '3'.                                        " MM-DD-YYYY.
      CONCATENATE p_date4(2) '-' p_date6(2) '-'
                  p_date(4)
         INTO p_result.
    WHEN '4'.                                        " YYYY.MM.DD
      CONCATENATE p_date(4) '.' p_date+4(2) '.'
                  p_date+6(2)
         INTO p_result.
    WHEN '5'.                                        "YYYY/MM/DD
      CONCATENATE p_date(4) '/'   p_date+4(2) '/'
                  p_date+6(2)
         INTO p_result.
    WHEN '6'.                                        "YYYY-MM-DD
      CONCATENATE p_date(4) '-' p_date+4(2) '-'
                  p_date+6(2)
         INTO p_result.
ENDCASE.
Regards,
Lakshmi.

ECC 6.0 Webdynpro for ABAP development environment

Similar Messages

Maybe you are looking for