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

Similar Messages

Webdynpro for abap using portal theme nw2004s, sp12

Hello,
we use on instance 03 portal on netweaver2004s, sp12, which calls webdynpros with iview for abap on intstance 02, where ist netweaver 2004s sp12, abap stack.
The problem is that the webdynpro is no more rendered with portaltheme. In the prevoius version of abap (netweaver2004s sp9) it was rendered with the portal theme.
Abap- and portal-server are in the same domain.
Where is the solution?
Best regards
Oliver Prodinger

Hello Brad,
SAP-Note 1033496 is the solution.
The problem was, that I have added the parameter WDFORCEEXTERNALSTYLESHEET falsely in iview-configuration and not as parameter to webdynpro.
Remarkable is, that portal and webdynpro-abap-backend have the same neteweaver2004s, sp12.
Best regards
Oliver Prodinger

Webdynpro for ABAP and Portal Integration

Hi Experts,
we created a WebDynpro for ABAP application for portal. The application will modify/update few fields in backend sap HR table PA0006 (infotype 6) . The end user (portal user) should be able to update his data in backend with the iview created on this application.
I have below two questions in my mind.
1. Do we need portal eventing for this? It's a single iview in portal which will fetch and update his data through this WebDynpro for ABAP application.
2. It is for 10 countries of almost 1000 users (with same userid in portal and backend). How can I make sure that the enduser updates and fetch his records only. The SSO is already set up between Portal and Sap ECC system. Do I need to again pass the enduser portal id to the sap in coding to fetch and update the data or sso will take care of itself.
Thanks
Ajay

1. Do we need portal eventing for this? It's a single iview in portal which will fetch and update his data through this WebDynpro for ABAP application.
Answer: If you use, for exemple ITS to access this Webdympro, you will not need any action on portal for sure. Actually you will just need actions on portal, if you want to make some customization on portal side. If you want just show the Webdympro how it is, your action are all on backend..
2. It is for 10 countries of almost 1000 users (with same userid in portal and backend). How can I make sure that the enduser updates and fetch his records only. The SSO is already set up between Portal and Sap ECC system. Do I need to again pass the enduser portal id to the sap in coding to fetch and update the data or sso will take care of itself.
If you access via ITS, te custome will acess the backend with the user you have set on the SSO or user-mapping. The portal there is nothing to do in this regards, you must just take care of this on backend.
Please evaluating the answer you are contributing for the SDN keep growing.
Edited by: Fabio Sarmento on Sep 19, 2011 2:41 PM

How authentication and authorization works in webdynpro for abap and portal

Hi Experts,
I have to create an webdynpro abap application for portal which will update the user information in the backend HR standard table.
The SSO (certificate)setup is already doen between portal and backend sap system . Do I need to pass the portal userID to the webDynpro ABAP application, via IView created to update the table. OR SSO will take care itself.
Thanks and regards,
Ajay

Dear Ajay
If SSO is configured as you have mentioned, then all is ok and you don't need do pass the user ID.
It will be done automatically.
Just try for yourself - create a simple WD ABAP and put it inside an iView.
Then have this WD to write the SY-UNAME on the screen.
That way you will confirm what I'm saying
Kind Regards
/Ricardo Quintas

Portal using Webdynpro for ABAP

Hi Gurus!
    I am using one portal using 'Webdynpro For ABAP'. It contains Contextual Panel as well as ViewUIContainer. Contextual Panel contains all the reqd options available for user; while ViewUIContainer contains diff views as requested.
   Now, I'm trying to make a copy of that Webdynpro with some other name. What happens is --
Application is not there and when I try to make one - it says
"Interface View Does Not Exists."
Further, when I try to make an Interface View with the new name - it says
"Interface View Does Not Exists."
   Therefore, what I could conclude about the case is -- may be Interface View is default to certain Webdynpro components/interface. Hence, my question is how can I make use of same webdynpro application with some other name. This requirement arises due to the fact that we have to add some more functionalities to that and I dont want to play with the efforts made so far.
Kumar Saurav.

Issue Resolved.
Kumar Saurav.

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

Portal integration of Webdynpro for ABAP application

Hi all,
Can anyone provide me with the steps for <b>integrating a Webdynpro for ABAP application with portal?</b>
Regards,
Bino

Hi Bino
Check out the following link
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webas/webdynpro/portal integration of web dynpro applications.pdf
Regards
Rajeev.
Do award points for helpful answers in SDN.

Do we need to be in unicode to use webdynpro for abap in ECC6 ?

Hello,
we study migration to SAPR3 46C SR2 to ECC6.
a question is: Do we need to be in unicode to use webdynpro for abap in ECC6 ?
Our SAPR3 are in non unicode
thanks

The problem, if you backend system is not unicode, can be, that user with the browser accessing the Webdynpro page, can enter data of any codepage (because browser is Unicode), the data will then be stored with a wrong codepage in the system and will be destroyed.
Additionally all successor versions of ERP will be Unicode only.
And on top of that, if you plan to use Java components (such as a portal), the backend must be Unicode (see Note 975768 - Deprecation of Java features with non-Unicode Backend).
Markus

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

Offline Interactive PDF Forms Using EMail with WebDynpro for ABAP

These is a tutorial on implementing Offline Interactive PDF Forms using Email to both send out and receive the form back using WebDynpro for Java.
Is it possible to implement the same using WebDynpro for ABAP, specifically receiving the forms via email server.
Regards,
Mark

Hi Mark,
Check this out :
https://www.sdn.sap.com/irj/sdn/interactiveforms-elearning
Go to section :
Send, Receive, and Process Interactive Forms via Email in SAP NetWeaver Application Server ABAP (RIG session 4A)
and for the ABAP WebDynpro :
SAP Interactive Forms by Adobe in Web Dynpro for ABAP (Session 3A) .
I managed to make it work in my internal sytem.
Goodluck.
Cheers,
Danny

Portal Password Reset Application In webdynpro for ABAP

Hello Friends,
I am new to WDA . I want to create a Password Reset application in WDA like this
[http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0c09b9d-52e0-2d10-3981-86bfa8e19dc3?quicklink=index&overridelayout=true]
Can someone pls give the solution , how to start??
Thanks in advance
Himani

I am afraid that this is not going to be possible for you. From WebDynpro for ABAP, you do not have portal API's to do that.
May be an idea ,If you have SSO in place you could try to call some FM's in r3 side to change the password in r3 system and this would synchronize the UME in portal.

How to create interactive forms using Webdynpro for ABAP

Hi All,
I have worked on Webdynpro for ABAP, and now I want to start creating adobe interactive forms using Webdynpro for ABAP. Please provide me with basic examples to start.
Also Please provide me introduction as how interactive forms are related to ISR senarios.
Thanks in Advance.
Phani

Hi Varun!,
Can you please send me also the above said step by step tutorial on [email protected]
and can you please also guide me any configurations to be done on Sneak Preview SP12 before developing the interactive forms.
Thank you in advance.
regards
Ravi

Simple application using WebDynpro for ABAP

Hi All,
I want to Build a simple application using WebDynpro for ABAP..
Thank you,
Karan

Hi Mr.Karan,
Pls Go through the link [Application|http://****************/Tutorials/WebDynproABAP/SimpleApplication/SimpleApp1.htm]..
Let me know if need any help...
Thank you,
Srini.S

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

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.

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

Similar Messages

Maybe you are looking for