Skip to Content
avatar image
Former Member

wd for aba

Hi

thanx for ur kind reply,

i have few more doubts

1.how many types of navigation links r to navigate from one view to another view.

2.How to pass a value between one view to other view using parameters.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Nov 05, 2008 at 06:08 AM

    Hi,

    1.how many types of navigation links r to navigate from one view to another view.

    There are no types of naviagtion.We can do navigation from one view to other onAction of any UI element and using OutboundPlug.We will use inbound plug in the second view to handle the action.

    http://help.sap.com/saphelp_nw04s/helpdata/en/7e/77a8af020ffa4596aad94019de8de7/frameset.htm

    2.How to pass a value between one view to other view using parameters.

    You can pass by using the outbound plug or create controller context node.

    Add comment
    10|10000 characters needed characters exceeded

  • Nov 05, 2008 at 08:22 AM

    Hello Karuna,

    There are no different types available in navigation links. We use the navigation links to join together different outbound and inbound plugs. Whenever you create an outbound plug the system does actually fire an event called as the Navigation event. So linking of an inbound plug to an outbound plug means registering the inbound plug event handler method to the navigation event, called by firing an

    outbound plug. Hope that this makes you clear about this navigation link concept.

    You can pass data in between 2 views using 2 methods:

    Using the Outbound plugs and event handler methods related to the inbound plug:

    Outbound plugs and event handler methods related to the inbound plug can have parameters, allowing you to pass data between the views. This might sound complex but think it in the OO-ABAP sense. When you define an event you define your events signature with all the parameters. The event handler method for this event can just use the same events and it cannot define any other parameter of its own. Similarly as how said earlier an outbound plug raises an navigation event so outbound plugs have the parameters defined in here. The corresponding inbound plug can just receive these parameters.

    By maintaining the data at component controllers context level

    By maintaining the data at component controller context. As you know the component controller is

    a global controller which is visible to all other controllers. So if you want to share any data in between different views then you create this data as nodes & attributes in the component controller context. So suppose you have to access these nodes/attributes in a view you will have to go to the context of that view & copy the corresponding nodes & attributes from the component controller's context to the views context. This process is known as Context mapping. Once you have done this context mapping you can use the corresponding getter/setter methods to work with the context data.

    Regards,

    Uday

    Add comment
    10|10000 characters needed characters exceeded