Skills Profile - Enhance Web DynPro to handle Effective Date

We are working with the ESS BP on ECC 6.0 and have a requirement to enter an Effectivity Date for the start of a qualification.  The trouble is that the existing function for updating the qualification profile (XSS_SKL_APPLY_QUALI_PROFILE) does not allow for a beginning date to be passed in.  Instead it uses the current date (Sy-Datum) which is set on initialization of the SkillsApplication (via FM XSS_SKL_INITIALIZE_DATA).  I have tried to enhance the structure for the qualification profile (structure RHXSS_SKL_EMPLOYEE) but it is marked as Can Not be Enhanced by SAP.
Does anyone have any thoughts on a good way to add this functionality?  I'd hate to throw away all of SAP's work with the SkillsApplication and write one from scratch just for this small change, but it's looking like that might be my only option.

The following describes the changes required for adding the effectivity date to the Standard Skills Profile Web Dynpro Java screen.
ABAP Changes
1.  Get modification keys for hte following structures and change the enhancement category of the strucures to "Can Be Enhanced Deep".
     RHXSS_SKL_EMPLOYEE
     RHXSS_SKL_PROF_UPD
     RHXSS_SKL_QUALIPROFILE
2.  Add appends to each of the structures in step 1 for feidl ZEFFDATE
     RHXSS_SKL_EMPLOYEE - ZZEFFDATE type BEGDATUM
     RHXSS_SKL_PROF_UPD - ZZEFFDATE type String
     RHXSS_SKL_QUALIPROFILE - ZZEFFDATE type BEGDATUM
3.  Enhance the following function modules for setting/getting the values of ZZEFFDATE
     XSS_SKL_APPLY_QUALI_PROFILE
     XSS_SKL_CONFIRMATION_DATA
     XSS_SKL_GET_PROFILE_OVERVIEW
     XSS_SKL_GET_QUALI_DETAIL_DATA
4.  Enhance the following Includes using the Modification Assistant or Enhancement Framework for setting/getting
    LRHXSS_SKL_INTERFACEF01
    LRHXSS_SKL_INTERFACETOP 
Java Changes
Track:  Make a new track for the ESS Component.  A quick SDN search should produce for you a Cookbook for setting this up in the NWDI
DC:  esssklsap.com
1.  Reimport the Skills model to get the ABAP changes into WebDynpro
2.  Create a new Application (zSkillsApplication in my case)
3.  Modify the Application properties to tell the framework manager to use the CcSklConfiguration  component for navigation configuration
     Properties
     sap.authentication = true
     sap.xss.configurationComponentDC = sap.com/ess~skl
    sap.xss.configurationComponentName = com.sap.xss.hr.skl.CcSklConfiguration
4.  In the Interface Controller of Component CcSklConfiguration, modify the navigation Graph as follows
navigationGraph =
   new NavigationGraph(
    new NavigationPath[] {
     new NavigationPath("",IFPM.EVENT_START,"OVERVIEW"),
     new NavigationPath("OVERVIEW",IFPM.EVENT_EDIT,"DETAIL"),
     new NavigationPath("OVERVIEW",IFPM.EVENT_ADD,"SELECT"),
     new NavigationPath("OVERVIEW",IFPM.EVENT_REVIEW,"REVIEW"),
     new NavigationPath("OVERVIEW",IFPM.EVENT_REMOVE, "OVERVIEW"),
//begin replace ERICV - Go Straight to Review&Save
//     new NavigationPath("DETAIL",IFPM.EVENT_ADD, "OVERVIEW"),
     new NavigationPath("DETAIL",IFPM.EVENT_ADD, "REVIEW"),
//end replace ERICV - Go Straight to Review&Save    
     new NavigationPath("DETAIL",IFPM.EVENT_BACK, "OVERVIEW"),
     new NavigationPath("DETAIL",IFPM.EVENT_SELECT, "SELECT"),
     new NavigationPath("SELECT",IFPM.EVENT_EDIT, "DETAIL"),  >
5.  In the Component FcSklBusinessLogic, make the following changes:
        a.  Perform the context mapping of the new ZZEFFDATE field in the Interface Controller and Standard Controllier
        b.  Modify the insUpdSkill method of the Component Controller to populate the Effective Date
try {
   wdContext.nodeApply_Quali_Profile_Input().bind(
    (Xss_Skl_Apply_Quali_Profile_Input) model.createModelObject(Xss_Skl_Apply_Quali_Profile_Input.class));
   Xss_Skl_Apply_Quali_Profile_Input input = new Xss_Skl_Apply_Quali_Profile_Input();
   Rhxss_Skl_Employee insUpdVector = new Rhxss_Skl_Employee();
   insUpdVector.setSkill_Id(wdContext.currentContextElement().getQualiId());
   insUpdVector.setExist_Profcy(wdContext.currentContextElement().getProfDropDown());
   //Begin Insert ERICV - Add Effective Date to Skills Qualification
   insUpdVector.setZzeffdate(wdContext.currentContextElement().getZzEffDate());
   //End Insert ERICV - Add Effective Date to Skills Qualification
   input.addProfile_Ins_Tab(insUpdVector);
   wdContext.nodeApply_Quali_Profile_Input().bind(input);
   wdContext.currentApply_Quali_Profile_InputElement().modelObject().execute();
  } catch (Exception ex) {
   fpm.getMessageManager().raiseException(wdThis.wdGetAPI().getComponent(), ex);
6.  In the Component VcSklDetail make the following changes:
     a.  Context mapping of all relevant nodes to get the new ZZEFFDATE field in the context
     b.  Screen modifications to get the ZZEFFDATE on the screen
     c.  Modify the initDetail method of the Component Controller
if ((sklOutputElement.getExpiry_Date() == null) || (sklOutputElement.getExpiry_Date().equals(""))) {
   wdContext.currentContextElement().setLicenceVisibility(WDVisibility.NONE);
//begin insert ERICV - set the zzEffective Date
     //convert date to java.util.date
         SimpleDateFormat sdf = new SimpleDateFormat("mm/dd/yyyy");
  try {
   java.util.Date myDate = sdf.parse(wdContext.currentGet_Quali_Detail_Data_OutputElement().getStart_Date());
   sdf.applyPattern("yyyy-mm-dd");
   wdContext.currentContextElement().setZzEffDate(Date.valueOf(sdf.format(myDate)));
  } catch (ParseException e) {
   // TODO Auto-generated catch block
            e.printStackTrace();
//end insert ERICV - set the zzEffective Date
    //@@end

Similar Messages

  • Test of Web Dynpro Event Handling : GeoMap business graphics

    Hy guru's, i have this problem: on Test of Web Dynpro Event Handling page i tried to open the GeoMap web dynpro on Business Graphics section but i received this error:
    The URL http://.../sap/bc/webdynpro/sap/wdr_test_events/ was not called due to an error.
    Note
    The following error text was processed in the system BI7 : Exception condition "COMMUNICATION_ERROR" raised.
    The error occurred on the application server bi7-saplab_BI7_08 and in the work process 0 .
    The termination type was: RABAX_STATE
    The ABAP call stack was:
    Method: IF_GIS_VIEW~UPDATE of program CL_GIS_VIEW_IGS===============CP
    Method: IF_WDR_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/LBUSINESS_GRAPHICS======CP
    Method: IF_WDR_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/L8STANDARD==============CP
    Method: IF_WDR_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/L8STANDARD==============CP
    Method: IF_WDR_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/L7STANDARD==============CP
    Method: IF_WDR_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/L8STANDARD==============CP
    Method: IF_WDR_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/L8STANDARD==============CP
    Method: IF_WDR_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/L8STANDARD==============CP
    Method: IF_WDR_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/L7STANDARD==============CP
    Method: IF_WDR_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/L7STANDARD==============CP
    What can I do?
    If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system BI7 in transaction ST22.
    If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server bi7-saplab_BI7_08 in transaction SM21.
    If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 0 in transaction ST11 on the application server bi7-saplab_BI7_08 . In some situations, you may also need to analyze the trace files of other work processes.
    If you do not yet have a user ID, contact your system administrator.
    Error code: ICF-IE-http -c: 100 -u: AMARAVIGLIA -l: E -s: BI7 -i: bi7-saplab_BI7_08 -w: 0 -d: 20071119 -t: 232916 -v: RABAX_STATE -e: RAISE_EXCEPTION
    HTTP 500 - Internal Server Error
    Your SAP Internet Communication Framework Team
    Could you help me?
    Thank's a lot
    Sincerely yours
    Andrea Maraviglia

    Hi,
    did you install the IGS (see the <a href="http://help.sap.com/saphelp_nw70/helpdata/en/37/268841a79f1609e10000000a155106/frameset.htm">documentation</a>) and check if SAP note 1108034 helps?
    Regards, Heidi

  • No component usage created in enhanced web dynpro component

    Hi experts,
    I am facing the following problem:
    I'd like to enhance a web dynpro component in order to add a popup window. The popup is triggered by the process_event method. So far everything works just fine.
    But the popup needs to know some context attributes from the main component, and I cannot create a component usage in order to set the context mapping.
    Does anybody know how to solve this issue?
    Thanks and regards
    Jan Phillip Höft

    Hi!
    Thanks for your answers first of all.
    I need the popup to be a stand alone web dynpro component, so I guess the assistant class doesn't do the trick because I can not access it in the popup component.
    The popup is called when the business object is saved. So that the user is asked to notify other users that the document has changed. In this popup the user should fill in the message and click a button to send it and close the popup.
    So I tried the OBN approach as well but with two problems :
    1. I cannot close the popup component by coding (button click) because it has no direct parent component
    2. The save event is not run through properly so the document stays locked by the user. But I didn't look into this yet.
    So it would be perfect to have an embedded popup component which is based on a stand alone web dynpro application so it can be closed properly but it need at least access to the guid of the main component.
    Anybody got an idea for this?
    Thanks and regards
    Jan Phillip Höft

  • Web Dynpro Error Handling

    Hi all,
    i have an exception handling problem in web dynpro. For my app (WEB AS 6.40 SP 15) i need an exception handler to catch all exceptions before the overall errorpage is shown (because there you cannot log, clean up resources and show an individual error messages to the user).
    In case of such an exception handler i don´t have spread try/catch blocks all over the WD code to catch exceptions the app cannot recover from.
    Does anyone has a suggestion whether a hook or something else exists in web dynpro (e.g. something like the error page mapping in a servlet container?)
    Thanks for help
    Christian

    Hi Hugo,
    that is exactly what i´m looking for
    If you are building a desktop-app e.g. based on swing, you can use ThreadGruop.uncaughtException to handle ALL exceptions before the thread is closed by the VM.
    If you are using a Servletcontainer you can configure an error-page which is mapped to a special exception e.g. Throwable. This error-page can be implemented as a normal servlet so you can do ALL of your necessary error handling there.
    These are two ways to clean up resources and do some last logging in case an error occures the app cannot recover from.
    Is there anything comparable in WebDynpro?
    Regards,
    Christian

  • Exporting table data to MS-Excel Sheet(enhanced Web Dynpro Binary Cache)

    Hi experts,
    I am trying to implement the functionality of downloading the contents of a webdynpro screen to excel sheet. In order to implement the functionality of excel download i used the following blog.
    [/people/subramanian.venkateswaran2/blog/2006/08/16/exporting-table-data-to-ms-excel-sheetenhanced-web-dynpro-binary-cache ]
    In this blog they have used javaexcel api to implement the excel functionality. I face some problems
    while implementing it.
    i) The use of "Label label = new Label(0, 2, "A label record");
    sheet.addCell(label); " is not supported. It says that a constructor for label with
    (int, int, str) parameter is not available.
    ii) Then i implemented it with "Label label = new Label("A label record"); " Then i deployed it. I got a runtime exception saying that " java.lang.ClassNotFoundException: jxl.format.CellFormat ".
    This cellFormat is an interface available in the jar. I am using jexcelapi_2_6_9_1.4 version. Do i have to
    download some other versions.
    Please help. Thanks in advance.
    Regards
    Ramanan

    Hi,
    Please check the following steps while creating External Library DC:
    1) creating an Extneral library DC
    2) import the JARs to the libraries folder of the External Library DC project
    3) Right-click on each of the JARs imported to the project and add them to the public part.
    This DC is now ready to be used as a build-time reference that will allow CBS to build the "main" Web Dynpro application that will use the external libraries. Next, we have to create a new Web Dynpro DC to hold the class files here are the steps:
    1) Create a new Web Dynpro DC
    2) Create a new public part, selecting the "Can be packaged into other build results" option
    3) Rename the JARs as Zip files and extrct the full content (folders and class files) to your root folder
    4) Import the folders and files to the src/packages folder
    5) Expand the public part node that was created and select the "Entities" node, right-click it and choose Edit
    6) In the Entity Type list select the "Folder" option then in the selected entities tree pick each of the folders that you imported in step 5 (above)
    7) Now do a DC build and a DC deploy of the project
    Then check-in, activate, and release any activities you have associated with creating these two projects. In the DC perspective, refresh the Active DCs and Inactive DCs to ensure that both new DCs appear in the Active list. Now we have to setup the references to these DCs in our main Web Dynpro application. To do this, follow these steps:
    1) Open the Web Dynpro perspective and right click the Used DCs node then choose "Add Used DC.."
    2) Pick the public part of the External Library DC that we created (first) and set it to have a Build Time dependency
    3) Again, right click the Used DCs node and choose "Add Used DC.." then choose the public part of the Web Dynpro DC that we created and give it a Run Time dependecy (weak) and click finish.
    4) Now, due to what I think is a bug. You must right click on the Web Dynpro "used DC" that you just added in the previous step, and set the run time dependency again (it seems to revert to the default values for some reason)
    5) Now do a DC build and a DC deploy on the "main" web dynpro application.
    6) Check-in, activate, and release any activities associated with adding these references and then others on your team may use the classes in the external libraries within the Web Dynpro project.
    Regards.
    Rajat

  • Web Dynpro ABAP - ALV - insert data

    hi,
    I have got the following task.
    I need to insert a new row into an alv table that shall be editable (data to be edited in the table, where
    a) the other rows of the table, that already exist must not be editable
    b) some columns of the new row are to be initialized with values when creating new row
    can you help here?
    more precise description of the task/problem
    to a) all I found is the possibility to make columns editable, if I wanted to edit new inserted fields directly in the table. This would give the possibility to also edit the rows that are already there and where the data should not be modified...
    to b) I tried with a propriarity button in wddoinit.  DATA lr_btn_new TYPE REF TO cl_salv_wd_fe_button.
      DATA lr_fct_new TYPE REF TO cl_salv_wd_function.
      CREATE OBJECT lr_btn_new.
      lr_btn_new->set_text( 'Request New').
      lr_fct_new = lo_model->if_salv_wd_function_settings~create_function( id = 'BTN_NEW' ).
      lr_fct_new->set_editor( lr_btn_new ).
    and than call an on_function event handler, but now got the problem that I do not know how to insert the row to the table....

    Hi,
    Inserting new row is very simple,just modify your internal table which is attached to the ALV table in the onFunction Event handler method like.
    data: wa_tab type wd_this->elem_flights. "work area is of type context node(structure),now this is empty
    it_flights type table of wd_this->elem_flights,
    v_lines type i.
    Now read the context node data into internal table.
    navigate from <CONTEXT> to <FLIGHTS> via lead selection
      lo_nd_flights = wd_context->get_child_node( name = wd_this->wdctx_flights ).
    CALL METHOD LO_ND_FLIGHTS->GET_STATIC_ATTRIBUTES_TABLE
      IMPORTING
        TABLE  = lt_flights.
    Modify the internal table from workarea.
    describe table lt_flights lines v_lines.
    modify lt_flights from ls_flights index v_lines. This is to add empty row at the last in the table
    Now bind the internal table to context node.
    To make entire row is editable check this forum threads and articles which i already answered.
    Cell Edit/ Row Edit in ALV WDA
    How to make all columns of alv editable
    Also check this article for conditionally editable.
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0625002-596c-2b10-46af-91cb31b71393

  • ECM - Web dynpro changes to Saslary Data screen do not refelect

    Hi,
    We want to modify the compensationprofiles_salarydata iView. This iView is trigtgered when the hyperlink on the employee name is cicked on the compensation screens. We have done the required modifications like, deleting ( making visibility to NONE)  the non-essentail fields like ltes say all pay scale / pay grade fields.. But this does not get refleted in the Web applications.
    To make this work we have deleted all the fields from the VAC ( Visual applicaiton component ) and still it does not work. We cannot do personalizatioan as the iView preview does not show any fields but the message " select an employee first ..." kind of message
    any ideas if any one has encountered this issue earlier
    regards
    Raj

    Create a context attribute of Visibility type and assign it to the UI Element which you want to hide.....then in the Implementation Tab -> wdDoModifyView() method set the context attribute created earlier to invisible....
    Shikhil

  • Web Dynpro ABAP ALV On Data check

    Hi
    If i push the check button and i find an error in my on data check event and send an error message l_message_manager->REPORT_ATTRIBUTE_ERROR_MESSAGE. It will not check again when i am pushing of the check button again, i guess because no data has been changed. But if no data has been changed, the user will not have cleared the error for sure.
    Now as i write this i have an idea for an work around.
    But anyway. It seams to me that others should have faced this problem and i believe i am doing something wrong. I have tried to set the value again, but this will not trigger an change.
    So what i will try next is to save my error messages and just clear them when the data_check is done again. (I am not sure how to do this at the moment, but i will see.)
    Still does anybody know a better way, or how it's meant to be done?
    thanks.

    my solution is:
    on the data check event i save the changes to tables in my class.
    i have put an own check button in the alv, which is realy checking the data.
    the save button is then using my tables to do the actual changes to the dso.

  • Enhancement spot BADI in Web Dynpro

    Hi,
    is that possible to define a UI enhancement spot in Web Dynpro Layout to enhance an existing WDA? It is possible with classic ABAP GUI. With this, customers could add their custom UI modification to my application.
    Thanks
    Davy

    You can enhance Web Dynpro Components.
    select the web dynpro component that you want to modify. Click on the component controller.
    Click on the menu "Controller" and select Enhance (Ctrl + F4)
    Specify a name and text for your enhacement
    Similarly to enhace a view, double click the view and select enhance from the view menu.
    Regards,
    Reema.

  • In web dynpro i want explanation/definition for the following things

    Hi dudes,
             I want explanation *** definition for the following
    (1) web dynpro
    (2) Cardinality
    (3) methods
    (4) Nodes
    (5) Attributes
    (6) Interface
    (7) Views
    (8) Windows
    (9) Mapping
    (10)Binding
    (11)Model
    (12)Controller

    Hi,
    Here are the defintions for the terms you hav requested-
    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
    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.
    A Web Dynpro component is a reusable entity. It summarizes all components that are
    required as part of this programming unit for an executable Web Dynpro application.
    The Web Dynpro component concept offers a number of advantages:
    Structuring of the programming
    Creation of easily manageable application blocks
    Reusability of whole components
    Decoupling of software projects in both time and space
    The Web Dynpro component contains any number of windows and views and their
    corresponding controllers. Additional Web Dynpro components can also be referenced.
    View
    A view describes the layout and behavior of a rectangular area of a user interface.
    Every Web Dynpro application has at least one view. The layout of a view is made up of
    different user interface elements, which can be nested in each other. The positioning of
    interface elements in one view is supported by the supplied layout variants.
    In addition to the visible part, the layout, a view also contains a controller and a context. The
    data to which the elements of the view can be bound are stored and managed in the view
    context, enabling them to be represented or used on the screen. The view controller can
    contain methods for data retrieval or for processing user input.
    Window
    A window is used to combine several Views and View Sets (the concept of view sets is only
    offered in Web Dynpro for Java). A view can only be displayed by the browser if it has been
    embedded in a window. A window always contains one or more views, which are connected
    by navigation links. One of these views, or a view set, is specified as the start view and is
    displayed the first time the window is called.
    Windows have inbound and outbound plugs.
    Inbound Plugs and Outbound Plugs
    A window has one or several inbound or outbound plugs. Using these plugs, a window can be
    included into a navigation chain. The concept of these plugs corresponds to the concept of
    the plug for a view. Each plug of a window is visible within the entire window and can be used
    for navigating within this window. In addition, one or several plugs can be made accessible to
    the component interface so that they are visible even beyond the limits of the component in
    question. They thus belong to the interface view of the relevant window.
    They are used to navogate from one view to other and pass the data between the views. Which view to be called next from current view - the flow of views is descriebd here using Plugs.
    Controller
    Controllers are the active parts of a Web Dynpro application. They define how the user can
    interact with the Web Dynpro application. The data that a controller can access is defined in
    the corresponding context. Different instances of controllers and contexts exist within a Web
    Dynpro application.
    View Controller
    Each view has exactly one view controller, which processes the actions performed by the user in the view.
    A view also has exactly one view context, which contains the data required for the view.
    Interface Controller
    Each Web Dynpro component contains exactly one component controller. This controller is a
    global controller that is visible also outside the component. It is thus part of the interface of a
    Web Dynpro component.
    Context
    Definition
    The data used in the component or in the view are stored in the context. Read-write access to
    this data is available using the controllers as a starting point.
    Structure
    The data from the contexts is managed in a hierarchical structure. Each context has a root
    node, underneath which the individual data fields (attributes) are stored in a tree structure.
    You create this tree structure according to the structure of your application.
    CONTEXT is generally called as a ROOT Node.
    Each context has nodes and attributes also.
    Cardinatlity
    Each node contains data fields that represent one of the following:
    u2022
    An individual instance of an object type
    u2022
    A table of instances.
    This property of a node is known as its cardinality. The following table summarizes the
    possible cardinalities for a node:
    Cardinality Description
    1:1 The node contains only one element instance, which is instantiated automatically.
    0:1 The node contains only one element instance, which must not be instantiated.
    1:n The node can contain multiple element instances, of which at least one must always be
    instantiated (and is instantiated automatically).
    0:n The node can contain multiple element instances, of which none have to be instantiated.
    Further information about this and other properties of context nodes is available in the section
    Context-Nodes: Properties.
    Recursion Nodes
    Dynamic node nesting is possible within a context, creating what is called a recursion node.
    The node that is used for recursion is always a predecessor of the new node. The newly
    created recursion node is a reference to a predecessor node and therefore cannot be
    processed separately. Instead it takes on the structure of the node to be repeated.
    Data Binding and Mapping
    Within the Web Dynpro architecture, the contexts of the different controllers can be linked in
    different ways:
    u2022
    A UI element of the user interface of the view can be linked with an element of the view
    context.
    u2022
    A mapping can be defined between two global controller contexts, or from a view
    context to a global controller context.
    The context of a global controller can be linked to a Web Dynpro Model.
    Defining Mapping Between Two Contexts
    The elements of a view context can be locally defined. In this case (represented in the graphic
    below as a "Local Node"), all the contained attributes are only visible within the relevant view.
    When the view disappears, the attribute values are deleted.
    Event
    The component controller allows you to create events.
    Events are used to communicate between controllers and enable one controller to trigger
    event handlers in a different controller.
    Cross-component communication can be implemented using the interface controlleru2019s events.
    Events that were created in the component controller are visible within the component only.
    Inbound Plugs
    Inbound plugs in a view also react like an event. Therefore, when a view is called using an
    inbound plug, the event handler that is optionally available for the inbound plug is always
    called first. In this case event handling takes place within the current view controller.
    UI Element Events
    Some UI elements, such as the Button element have special events that are linked with user
    actions. These events are predefined and have to be linked with an action at design time.
    Actions for UI Element Events
    Some UI elements such as the button element can react to a useru2019s interaction: clicking on
    the corresponding pushbutton can trigger a handling method to be called within the view
    controller. Such UI elements are equipped with one or several general events, which can be
    linked with a specific action at design time (switching to a subsequent view, for example). If
    such an action is created, an event handler method for this action is created automatically. In
    this way, you can equip a UI element event (which has been inserted several times into a
    view) with different actions as necessary. The event is then processed by the corresponding
    event handler depending on the action that is linked.
    Interfaces of Web Dynpro Components
    Each component has an interface in order to enable communication between Web Dynpro
    components and to enable a component to be called up by a user. This interface consists of
    two parts:
    Interface View of a Window Contained in a Component
    The interface view of a Web Dynpro window is used to link a window with a Web Dynpro
    application that can be called by the user.
    Reward if helpful.
    Best Wishes,
    Chandralekha

  • Want docs for Web Dynpro ABAP

    Hi All ,
    Can anyone please send me the Docs or link for Web Dynpro ABAP .
    Thanks in advance
    Rahul

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

  • Web Dynpro concept

    Hi all,
    What is web dynpro concept in ABAP. What are the future scope for the same.
    Regards,
    John

    Hi,
    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 u2013 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
    http://help.sap.com/saphelp_nw04s/helpdata/en/77/3545415ea6f523e10000000a155106/frameset.htm
    Cheers,
    vasavi.v

  • Calling Web Dynpro application or URL from POWL

    Hi Friends,
    I need to call a Web Dynpro appl from a custom POWL. In my feeder class's method HANDLE_ACTION, i am not getting how to use e_portal_actions parameter for calling a URL of WD application. Pls help me out in this.
    Regards,
    Saud

    You can create a launchpad application through tran LPD_CUST and then in repsective method of POWL class you can launch your web dynpro application like this
    DATA ls_appl_param              TYPE APB_LPD_S_PARAMS.
      DATA lt_appl_param              TYPE APB_LPD_T_PARAMS.
      DATA lt_lpd_content             TYPE apb_lpd_t_content.
      DATA lr_lpd_content             TYPE REF TO apb_lpd_s_content.
      DATA lt_lpd_appl_params         TYPE apb_lpd_t_params.
      DATA lr_lpd_handle              TYPE REF TO cl_apb_launchpad_api.
      DATA lo_component     TYPE REF TO if_wd_component.
      DATA lr_provider      TYPE REF TO if_apb_lpd_provider.
      "Get launchpad handle
    lo_component = wd_comp_controller->wd_get_api( ).
    cl_apb_launchpad_api=>read_for_display( EXPORTING id_role = cl_oif_ui_assist=>sc_lpd_roles "Role Name
                                                       id_instance = cl_oif_ui_assist=>sc_lpd_instance " Instance Name for Launchpad
                                                       id_langu = sy-langu
                                                       ir_provider = lr_provider
                                                       ir_wd_component = lo_component
                                             RECEIVING er_launchpad = lr_lpd_handle ).
      CHECK lr_lpd_handle  IS BOUND.
      lt_lpd_content = lr_lpd_handle->get_content( ).
      READ TABLE lt_lpd_content REFERENCE INTO lr_lpd_content
                                WITH KEY link_text = cl_oif_ui_assist=>sc_lpd_link_text. "Link text for launchpad
          ls_appl_param-key = cl_oif_ui_assist=>wda_config_key.  "'SAP-WD-CONFIGID'. "app conf if any
          ls_appl_param-value = cl_oif_ui_assist=>CREATE_CONFIG_ID. "'MDG_OIF_CREATE_CONF'.
          APPEND ls_appl_param TO lt_appl_param.
          lt_lpd_appl_params = lr_lpd_content->application_parameter.
          "launch application
          lr_lpd_handle->launch_application(
            id_application_id         = lr_lpd_content->application_id
            it_application_parameters = lt_lpd_appl_params
            it_business_parameters =  lt_appl_param

  • Mass upload through Web Dynpro application possible?

    We want to develop a custom aplication with Web Dynpro ABAP for master data maintenance. About 90 % will be done manually but we also want to have the possibility to do mass uploads (comparable with LSMW's in SAP R3 for win gui transactions: users send us a spreadsheet and we load it for them using a LSMW). I found one option by building Adobe Interactive form offline scenario using xml messages but I don't want to be forced to use Adobe only to enable mass uploads that will only happen in 10 % of the cases.
    I am loking forward to your suggestions!
    kind regards
    Angelique Heutinck

    I got a very useful answer from Thomas Jung (SAP) via a site he did setup with a couple of other SAP experts, also see http://enterprisegeeks.com/blog/2009/03/31/abap-freak-show-april-1st-acf-updownload-in-web-dynpro-abap/comment-page-1/
    My question:
    I think this new UI element ACFUpDownload cannot be used to do mass uploads/updates of data that need to be stored in SAP tables?
    Answer Thomas:
    This UI element is just about the transfer of data from the client machine to the server. It has nothing to do with how the data is used or processed after upload. Think of it as the equal to the CL_GUI_FRONTEND_SERVICES class and methods GUI_UPLOAD and GUI_DOWNLOAD.
    My question:
    Is there a tool like LSMW, CATT, eCATT that we can use for recording webenabled transactions (applications developed in Web Dynpro ABAP)?
    Answer Thomas:
    You shouldnu2019t need a tool like LSMW, CATT, eCATT that is tied to the user interface. With WDA you should be using MVC to design your application. This is part of the reason for MVC so that you have a clear separation of the model - business logic. You should always have a reusable class that can be called to input and create data with the same validations without going through the user interface. This is the process that SAP is following as we create new WDA screens. We use the enterprise services and their implementation classes as the Model for the WD Components. This ensures that you always have a clear API to use to mass import data.
    Although we wouldnu2019t recommend doing any kind of mass data load via the user interface any longer - eCATT will be supported for automated testing of Web Dynpro ABAP applications as of NetWeaver 7.0 Enhancement Package 2.

  • Upload and Reading Excel File in Web Dynpro

    Hi all,
    I have a requirement in my application( in 04s), where in, i need to upload an excel from a client through a web dynpro application(using fileupload UI) and read each and every the content of that excel file in web dynpro and process the data accordingly.
    The format of the excel is fixed and pre-defined.
    I went through a lot of blogs, but could not find a direct and exact solution to this requirement.
    Please help me.
    Looking forward to your contribution
    Thank you,
    Gita KC.

    Reading Excel Sheet from Java without using any Framework
    Enhanced File Upload - Uploading and Processing Excel Sheets
    Reading Multiple Sheets of Excel Sheet from Java
    nikhil

Maybe you are looking for

  • HT4623 Please help me update my iPhone 4

    Help!  What does it mean when I get the error message "the iphone update software server could not be contacted."

  • Buying a Mac: 13" notebook dilemma demystified

    A note before we begin: This tip answered a notebook question mistakenly posted in a desktop forum.  Before posting your question or issue, you might want to check out where you are using the nav bar at the top of any forum thread.  If searching for

  • CRM survey extraction

    Hi Experts I am trying to extract CRM survey data from a CRM 3.1 system by using a BW 3.5 system. Surveys have been created and saved. I have set the Evaluate in BW setting for the survey in CRM. I do not get any data out when using RSA3 or by using

  • Black screen, ipod touch has black screen wouldn't charge

    My Ipod Touch screen has gone black. No activity. I have already tried to hold home /power for more than 10 second nothing come back. I even tried holding down arrow + home + pwer together. When I connect to my computer, sometime it says unable to in

  • Save Labview Class to file?

    Hi there, I am playing around with the new Labview classes and i am thinking working with classes is pretty cool. But i am not able to save the objekt to a binary file load them and use this data to initialize the Object with this data. Its no proble