Outbound plug Firing

Hi Friends,
I am New to WebDynpro programming. In My component I am using Select-options Component,My Component also has out bound plug TO_V1.
after the selection-screen is created, the out bound plug is fired.( WD_THIS->FIRE_TO_V1_PLG( ).)
in window, it is not configured to any inbound plug.
When I checked in Debugger, it is calling the view WND_SELECTION_SCREEN.
But i am confused where it could be configured?
Could,you please provide me your Valuble Inputs?
Regards,
Xavier.P

i xavier,
For example:
In the main view their selection screen and search button when you enter the made the selection for
this selection-screen and enterd the search button..it should go to the next view i.e(view1) displaying
data in table format..
for the main view it is outbound plug and for view1 it is inbound plug
main to view1( OB_main)...outbound plug.
view1 to main(ib1_view1)...inbound plug.
Incase after this you want to get back to the main view then from view1 it would the outbound plug and
for the main view you should create the inbound plug.
View1 to main(ob1_view1)...outbound plug.
Regards,
Sravanthi

Similar Messages

Fireing outbound plug of interface view from within component

Hi all,
is there a better way of firing an outbound plug of an wd component interface view than from within the interface view controller itself?
The problem is, that you easly get a cyclic reference if you evaluate inbound component plugs in the interface controller (usage from int view ctrl --> int ctrl needed) and then try to fire an outbound plug from this interface controller (usage comp int --> comp int view usage needed).
One workaround is to use some custom controller with usage of the interface view, but this doesn't seem to be a nice solution.
So is it possible to fire outbound comp plugs from, lets say the component controller - without any usage releation to the comp int view - instead, maybe via wdComponentAPI? If yes, could you provide a code snippet?
Thanks you and best regards,
Christian

Hi Christian,
this is not possible by using the public API only, i'm afraid. It is of course possible, if you decide to forget about the possible drawbacks of using methods and classes reserved for internal use. But you have to use it at your own risk. I hacked this together some weeks ago, don't know whether it still works
* Fires an outbound plug of an interface view with parameters.
* @param wdComponentAPI Component API "owning" the interface view.
* @param windowName Name of window
* @param plugName Name of outbound plug
* @param callerParameterMap optional Map of plug parameters.
public static final void fireOutboundPlug(
IWDComponent wdComponentAPI,
String windowName,
String plugName,
Map callerParameterMap)
throws WDRuntimeException {
// Find window requested
IWDWindowInfo windowInfo = wdComponentAPI.getComponent().getComponentInfo().findInWindows(windowName);
if (windowInfo == null) {
    throw new WDRuntimeException(
      "Can't find window: " + windowName + " in component: " + wdComponentAPI.getQualifiedName());
// Get info of interface view
IWDInterfaceViewInfo ifViewInfo = windowInfo.getInterfaceView();
if (ifViewInfo == null) {
    throw new WDRuntimeException("Window: " + windowName + ", no interface view info found");
// Find outbound plug
IWDOutboundPlugInfo outboundPlug = ifViewInfo.findInOutboundPlugs(plugName);
if (outboundPlug == null) {
    throw new WDRuntimeException(
      "The interface view: " + ifViewInfo.getName() + " has no outbound plug: " + plugName);
// Parameter passing
Collection plugParameters = outboundPlug.getParameters();
// TODO make check optional, check caller map parameter keys against existing
if (plugParameters == null || plugParameters.isEmpty()) {
    // No caller parameters allowed.
    if (callerParameterMap != null && !callerParameterMap.isEmpty()) {
      throw new WDRuntimeException(
        "The outbound plug: " + plugName + " has no parameters, callerParams must be empty/null.");
// TODO This is a hack, use of internal WD runtime classes and methods (don't use productive).
InterfaceView ifViewController =
    (InterfaceView) ((Component) wdComponentAPI.getComponent()).getController(ifViewInfo.getName());
ifViewController.navigate(outboundPlug.getName(), callerParameterMap);
Please remember, that not everything which is technically possible, makes sense
Regards
Stefan

Problem in construct_url and firing outbound plug data passing

Fnds,
I have been posting this but no one was able to help me specifically.
I am calling other WDA2 from WDA1.. i used construct_url, and called the outbound plug which is type suspend.
so wda2 is opening in same browser. .good.
but i want to send a value to the URL .. basically i can see parameter in outbound plug as url..
but how to pass the value to URL..
and in WDA2, how to read this value... pls plsssssss..
i know its simple, but i need some sampel code or example which reads this value of URL.
kindly help me..
Niraja

Hi Nirja,
You must have done this coding to call WDA2.
DATA lv_url TYPE string.
CALL METHOD cl_wd_utilities=>construct_wd_url
    EXPORTING
      application_name = 'ZWDA2'
    IMPORTING
      out_absolute_url = lv_url.
CONCATENATE lv_url '?sap-client=' sy-mandt '&sap-language=' sy-langu '&PARAM1=' <P1> '&PARAM2=X'
INTO        lv_url.
wd_this->fire_out_plg( url = lv_url ).
here out is suspend plug of WDA1.
now here is the code u need to do the coding in HANDLEDEFAULT method of default window of WDA2 to get the parameter passed by WDA1.
DATA ls_url TYPE LINE OF tihttpnvp.
DATA lt_url TYPE tihttpnvp.
wdevent->get_data(
EXPORTING
    name = if_wd_application=>all_url_parameters
IMPORTING
    value = lt_url ).
LOOP AT lt_url INTO ls_url .
    CASE ls_url-name.
      WHEN 'PARAM1'.
        <your logic to handle value of param1
      WHEN 'PARAM2'.
        <your logic to handle value of param2
      WHEN OTHERS.
    ENDCASE.
ENDLOOP.
moreover you need to fire simpel exit plug in WDA2 to get back to WDA1. And obviously you will have to define resume plug in WDA1.
Hope you will be having enough clarification.
-Haresh
Edited by: Khandal Haresh on Nov 7, 2008 5:00 AM

Browser Closes when outbound plug is fired

Hi Experts,
If I have a Adobe pdf file in my view and I click on a UI Button element which invokes the outbound plug of the view, then all the browsers close. There is no error message.
If I use UI elements and invoke the outbound plug then the application works fine.
Can anybody help me solve this problem
Regards
Abdullah

Problem was in ACF

How to fire outbound plugs of a window?

I have a component which I want to re-use in applications. The component should have 2 outbound (interface) plugs which can be wired into parent applications. When the user clicks buttonA in the component it should fire outboundPlugA, likewise for buttonB we have outboundPlugB. My problem is that I can only seem to fire outbound plugs of the view and not of the window.
Until now, we've solved this by firing interface events of the component controllers but it seems plugs would be more elegant.
How does one fire outbound plugs of the window?

OK, I've done what you said and have the following in the event handler (action of a button) in my view:
DATA:l_ref_test TYPE REF TO ig_comp1_window.
l_ref_test = wd_this->get_comp1_window_CTR( ).
The compiler error message is:
Method "GET_COMP1_WINDOW_CTR" is unknown or PROTECTED or PRIVATE.
This method does not exist as far as I can see.

View controller active after navigating via outbound plug, is this normal

Hallo,
I have two components (comp_a,comp_b).
comp_a->grid_view_a : fires a event.
comp_b->grid_view_b : subscribe to the above event.
My observation is that
When comp_a->grid_view_a fires a event and comp_b->grid_view_b listen to that event and the Grid is filled accordingly.
Now i navigate from comp_b->grid_view_b to comp_b->display_view_b firing a outbound plug.
Now if i change the selection in comp_a->grid_view_a and it fires a event. I was expecting that nothing happens in comp_b as the subscribed comp_b->grid_view_b is not in the assembly. But to my surprise, the event handler is called and processed while the user still watching/working on the comp_b->display_view_b.
Has anyone encountered with this problem ?. I was not having this problem a month ago. Could have been introduced in one of our Kernel/Sp updates.
Your reply is highly appreciated.

Hallo,
I have two components (comp_a,comp_b).
comp_a->grid_view_a : fires a event.
comp_b->grid_view_b : subscribe to the above event.
My observation is that
When comp_a->grid_view_a fires a event and comp_b->grid_view_b listen to that event and the Grid is filled accordingly.
Now i navigate from comp_b->grid_view_b to comp_b->display_view_b firing a outbound plug.
Now if i change the selection in comp_a->grid_view_a and it fires a event. I was expecting that nothing happens in comp_b as the subscribed comp_b->grid_view_b is not in the assembly. But to my surprise, the event handler is called and processed while the user still watching/working on the comp_b->display_view_b.
Has anyone encountered with this problem ?. I was not having this problem a month ago. Could have been introduced in one of our Kernel/Sp updates.
Your reply is highly appreciated.

Fire WindowInterfaceView outbound plug

For my webdynpro I use cross-component navigation.
From ComponentA, ViewA i'm using a plug to navigate to ComponentB, ViewB.
Now I want to navigate back to ComponentA, ViewA when the user press Cancel.
I created a outbound plug in my WindowInterfaceView with a link to the inbound plug from viewA.
How can I fire this plug in the WindowInterfaceView from ViewB?
Regards,
Björn

Hallo B.
what's the problem? You just apply the same technique twice. You navigate back to CompB from CompA just like you navigated from CompB to CompA before?
You declare an additional outbound plug on the interface view of CompB and link it to an interface view inbound plug of CompB.
Firing the outbound plug from WindowInterfaceView (you mean ComponentInterfaceView which is 1:1-related with a Window inside the component) is explained in the tutorial:
public void onActionNavigateBackToUICompB( com.sap.tc.webdynpro.progmodel.api.IWDCustomEvent wdEvent, int targetView )
//@@begin onActionNavigateBackToUICompB(ServerEvent)
wdThis.wdGetUICompAInterfaceViewController() .wdFirePlugBackToOtherCompOut(targetView);
//@@end
I allready adapted the code to your question.
Regards, Bertram

Why does fire outbound plugs sometimes don't work

Hello.
Can someone of you tell me what the reasons are that sometimes the firing of a outbound plug don't do the navigation?
Many thanks,
Mathias

Check in the window if you have created the navigation link between the views. After defining the plugs, only if the navigation link is created, the plug will be fired properly. This could have been missed, have a look.
Regards,
Nithya

Help Needed-Doubt in Outbound Plug Delegation

Hi Experts,
We had a requirement to create a view for displaying opportunities and provide navigation to the same from the view.
We were getting exceptions for incorrect implement and we solved it using the delegation concept.
Doubt:
In our Z component window we have Outbound Plugs namely navigate_display,navigate_create and navigate_edit.
But in our component usage we are using BT111M_OPPT component which has an OP DOCFLOW that need to be delegated as well for proper navigations to happen. The OPs of BT111M_OPPT navigate_display and navigate_create has been delegated to OPs navigate_display and navigate_create of our Z component window respectively.
Since we do not have a DOCFLOW OP in our Z component, is it correct if we delegate it to an available OP(say,navigate_display - this has been currently done and it is working fine now) or should we create an OP and den fire DOCFLOW OP within the same in our z component window?
Any pointers would be highly appreciated.

Hi,
Thanks for the reply.
My doubt is now about the flow of the firing.
While using navigational link concept,it just finds source and target as defined and navigates accordingly...but in this case
i am unable to arrive at such a conclusion.
My Z component had OPs in window : A,B,C.
I embedd a std. component in my z component. Std. component has window OP D.
I delegate the window OP of the std. component(D) to my Z component window OP(A).
Which OPs should be triggered within D and A(param iv_outbound_plug value to be passed to the fire method)?
So what would be the flow of the firing in two cases : 1. If i am navigating to the embedded view ?
2. If i navigate back to z component view?
Like i am not clear about the basic flow concept on the firing of OP of window and so i am confused about the usage.
Please help if you knwo any link where i can get an idea about the same.
I searched sdn but not to much avail.
Thanks
Swapna

Error while trying to create a outbound plug

Hi ,
I am getting an error message while trying to add an outbound plug to a component .any suggestions

Hi Vaibhav,
The best thing to do is to create the desired outbound plug manually. We do it many times when this error comes, it will not take much time and easy to do, just replicate the exact steps for creating op which is already there in your system or component.
I strongly suggest you not to delete any existing enhancement. Please let me know if you want me to explain the process of creating op manually.
Regards
Bhushan

ABAP webdynpro app not redirecting using Outbound plug in portal

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

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

Not defined outbound plug in Window or View but exists in NavigationLink

Hi Experts,
In NavigationlLink of standard component 'BSPWD_ADVSEARCH' contains the outbound plug 'SavedSearchEdit'.
But I am not able to find where the outbound plug is defined since it is not defined in its window or view.
Please explain me where the OUTBOUND plug is defined.
Thanks in Advance

Hi Raj,
The Outbound plug is defined for the bsp component - BSPWD_ADVSEARCH.
You can check the same in SPRO settings by following the path:-
SPRO->CRM->UI FRAMEWORK->TECHNICAL ROLE DEFINITION -> DEFINE WORKAREA COMPONENT REPOSITORY.
Here select the BSP component - BSPWD_ADVSEARCH & select INBOUND PLUG DEFINITION option on the left side.
You'll see 2 IPs defined along with their Target IDs.
- Dedeepya

Trigger GP process by giving process URL in Interface View outbound plug

Hi,
My Requirement is,
I have 1 GP process implemented in webdynpro.
From 1 of my view I am calling the process completeion(executionContext.processingComplete();) code, written in interface controller.
After this code I need to start the same process once again, without clicking any link.
For this I have created 1 outbound plug in the interface view of my window(out blug for WebDynproCOInterfaceView with parameter "Url").
Then after calling executionContext.processingComplete();, I gave
wdThis.wdGetWebDynproCOInterfaceViewController().wdFirePlugGotoUrl("Process Instantiation URL"); in my view.
but it is giving error,"WDRuntimeException: Cannot navigate from view WebDynproCOInterfaceView via non-existent outbound "
Also I tried to start the gp process througn coding also
what I tried is,
IWDClientUser wdUser = WDClientUser.getCurrentUser();
IUser user1 = wdUser.getSAPUser();
IGPUserContext userContext = GPContextFactory.getContextManager().createUserContext(user1);
IGPProcess process = GPProcessFactory.getDesigntimeManager().getActiveTemplate("EB0B28E08B6011DB0145EB416E0",userContext);
EB0B28E08B6011DB0145EB416E0 is the process ID.
This code I have tried by giving before and after the completion of the previous process(process9executionContext.processingComplete();)
But this also didn't work..No error came. But process didn't start again after thecompleted once.
Please help me out.
Thanks
smitha

Hi Rupam,
thanks for the reply
I have given EXIT type of outbound plug only. But it won't work if the view is in portal.
When I tried to create the process using GP API the process is creating in Background. For me , after the completion of one process , automatically next should trigger and the corresponding view should be visible for the user.
Process is triggering using GP API but, the view is not visible to user.
Please help me
Thanks
Smitha

Outbound plug, confusing error message: no navigational link attached

Hello,
I just finished the WebDynpro Quiz tutorial and deployed the application. Unfortunately when pressing the start button the application dumps and I get a stack trace
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException:
Cannot navigate via outbound plug StartQuizOut of view WelcomeView
because there is no navigational link attached to it
at com.sap.tc.webdynpro.progmodel.view.View.navigate(View.java:349)
indicating that there was no navigational link attached to my plug StartQuizOut. However the link is definitly there.
As sources are not provided I cannot debug into the class named in the trace.
Could someone please give me a hint. I think I did everything according to the tutorial, but I am stuck now.
Regards,
Sebastian Kamp
P.S. I searched this forum for "no navigational link attached"; there are some threads with a similar problem description, but no solution is provided.

Hi Zita,
thanks for your answer. I kind of solved the problem. When following the Tutorial I ended up for some reason with two versions of/references on (?) the WelcomeView - one was embedded in the QuizViewSet, the other directly in the Quiz-Window - don't ask me how that happend. Anyway, both were identical except the navigation links. The embedded view had all the navigation links required, the other didn't. So eventually in despair I deleted this view.. and now it works fine.
Regards,
Sebastian

Multiple inbound and outbound plugs

Hi Experts,
Can anybody give an example scenario where we compulsorily need multiple inbound and outbound plugs for a view??

Hi snakar rao ,
Suppose we have three views, a , b, c. Suppose we have a requirement like we need a button move_to_b on a, a button back in b which will move back to a, a button move_to_c on b and a button move_to_initial screen on c.
in this case
we need one out bound plug in a which will be connected to inbound of b
one out bound plug in b which will be connected to inbound of c.
in this case a needs two inbound plugs, one is for navigating from b and the other is for navigating from c
if there is a requirement like we need to navigate from a to c directly also, in this case c need one more inbound plug thats to connect the inbound plug from a.
Regards
Sarath

Outbound plug Firing

Similar Messages

Maybe you are looking for