Portal Eventing calls BAPI - result FAILURE!

Hi All,
I have an interesting delima.
BAPI_SALESORDER_GETSTATUS - using portal eventing to set "Salesdocument" model/mapped context value. When executing Bapi, no results display in my table (mapped to the output values).
In further testing, I added an InputField that was mapped to "Salesdocument" to see that it was being set properly before the Bapi execution. That worked so I could see that portal eventing was working correctly. Still no results though.
When I changed the "onEnter" event of the InputField to use my method that executes the Bapi, then the results showed up just fine. It appears that somehow the results only display if a InputField submits the value it is looking for.
Any ideas on how to get the results to display? I thought maybe it had to do with the data type, but the context only asks for a string value.
Max reward points for the person(s) who help me the most.
Much Thanks,
Cameron

Hi Cameron,
If I understand you correctly, the parameter dataObject in the action handler onActionGetSalesDocument
refers the value the you want to pass to the Import parameter SALESDOCUMENT.
If yes, then try doing the following two modifications.
Define a new parameter dataObject of type String for the method execute_Bapi_Status_Details_GetList
Change the action handler onActionGetSalesDocument as follows.
public void onActionGetSalesDocument(IWDCustomEvent wdEvent, String dataObject)
wdContext.currentContextElement().setSalesDoc(dataObject);
wdThis.wdGetStatusDetailComponentController()
.execute_Bapi_Status_Details_GetList(dataObject);
wdThis.wdFirePlugToDetailView();
Add a line of code to the execute_Bapi_Details_Getlist as follows:
public void execute_Bapi_Status_Details_GetList(String dataObject){
try{
 wdContext.currentStatusDetailsModelElement()
.setSalesDocument(dataObject);
 wdContext.currentStatusDetailsModelElement()
.modelObject().execute();
 wdContext.nodeOutput().invalidate();
}catch(Exception e){
 wdComponentAPI.getMessageManager.raiseException(e.getMessage(), true);
Bala

Similar Messages

Calling Portal event from ABAP class

Hi Experts,
I need a following clarificatrion, Please help,
1. Is it possible to call a webdynpro method from a normal ABAP class?
2. If no, we need a functionality of a class 'CL_WDR_HTTP_EXT_MIME_HANDLER' having method 'DO_DOMAIN_RELAX_HTML'.
Is there any alternative method which can be used in ABAP having the same functionality.
3. Is there any ways with which we can call portal event from ABAP class?
Thanks,
Shabir

>1. Is it possible to call a webdynpro method from a normal ABAP class?
I wouldn't necessarily recommend this approach. You shouldn't try to trigger events or any of the standard WDDO* methods from outside the WD Component itself. That said, you can pass the object reference (like the WD_COMP_CONTROLLER object reference or the View Object Reference) into methods of normal classes. Be careful if you are finding yourself calling a lot of your added methods from outside WD. This is probably a sign that these methods should be in the Assistance Class or some other Class functioning as a Model Object.
>2. If no, we need a functionality of a class 'CL_WDR_HTTP_EXT_MIME_HANDLER' having method 'DO_DOMAIN_RELAX_HTML'.
Is there any alternative method which can be used in ABAP having the same functionality.
What exactly do you want to do here? Do you just want to get the relaxation script? For what purpose? You should never need to inject the relaxation script into WDA.
>3. Is there any ways with which we can call portal event from ABAP class?
To what purpose. Do you just want to delegate the triggering of the event that is inside WD Component to be called from a class? If so you can pass the portal API object reference into a class from the WD Component. However this only works while running within WD.
How is this class used? Are you running in WD? Are you trying to generate some HTML code that runs in the portal independent of WD?

How can I use ONE Text search iView to event/affect mutliple Result Sets?

hello everyone,
i have a special situation in which i have 6 flat tables in my repository which all have a common field called Location ID (which is a lookup flat to the Locations table).
i am trying to build a page with a free-form text search iView on Table #1 (search field = Location ID). when I execute the search, the result set for Table #1 is properly updated, but how do I also get Result Set iViews for Tables #2-6 to also react to the event from Text Search for Table #1 so that they are updated?
i don't want to have to build 6 different text search iViews (one for each table). i just want to use ONE text search iView for all the different result set tables. but, in the documentation and iView properties, the text search iView doesn't have any eventing.
if you have any suggestions, please help.
many thanks in advance,
mm

hello Donna,
that should not be a problem, since you are detailw with result sets and detail iviews because custom eventing can be defined for those iviews.
Yes, it says "no records" found because an active search and record selection havent' been performed for it (only your main table does).
So, yes, define a custom event, and pass the appropriate parameters and you should be fine.
Creating a custom event between a Result Set iView and an Item Details iView is easy and works. I have done it.
See page 35 of the Portal Content Development Guide for a step-by-step example, which is what I used.
For my particular situation, the problem I'm having is that I want the Search Text iView's event (i.e., when the Submit button is pressed) to be published to multiple iViews, all with different tables. Those tables all share some common fields, which is what the Search iView has, so I'd like to pass the search critera to all of the iViews.
-mm

Alter a BAPI Result Table, how to get into the display "loop" ?

Hello all,
i have a problem regarding the result rows of a RFC/BAPI Call.
There are three views, let's say 1,2,3. In View 1, i call a BAPI, and display the results in a table in View 2. I added a button in each row, which calls View 3 and displays some details concerning the selected row.
I now want to store a flag for each row, that has been displayed in this way.
In View 3 i store the key value of the displayed row in an own value node in the context.
When i go back from View 3 to View 2, i want to see that flag (in an extra column) in every row, that has been selected in this session.
So i do not know, how to alter a single row in the BAPI result table, how to get into the "loop" that is used by WD to display the table.
already tried a supply function, but i was not able to alter single rows.
Any suggestions/tips or perhaps code fragments of working supply functions ?
Thank you !

Hello,
I'm not sure whether I understood your problem correctly, but I will try to give an answer.
The easiest way I see is to copy the RFC Results to a Component Controller Context structure with an additional Flag field. You can use WDCopyService for copying.
Then on the event of selecting you set your flag as appropriate for you (e.g. if you want to use an image as flag you set the Image path) on the current element of your table. Then display View 3.
On going back View 2 should show now the new flag values...
The trick is to copy the values (as at Time structures can not be expandend with new fields) and set the Flag on the onSelect event.
Hope this helps,
Frank

Portal eventing in WD ABAP

Hello ,
We have an requirment to pass values from one WD ABAP application iView to another in the Enterprise portal.Is there any configuration that needs be done in WD ABAP or is there any setting in EP that we need to do ??
Rahul

Rahul,
Though most of this stuff is of web dynpro for java. You can just replace java Code with ABAP.
You need to use eventing functionality.In the SAP Enterprise Portal, different application types in specific iViews can be arranged on one page. To communicate between the different iView types the portal provides the Enterprise Portal Client Framework (EPCF), also known as client-side eventing. This document describes how Web Dynpro applications can use EPCF.
http://help.sap.com/saphelp_nw04/helpdata/en/24/243ca46e1c334f8a6f8b0792656bc7/content.htm
The following code shows the signature of the subscribe method:
WDPortalEventing.subscribe(java.lang.String nameSpace, java.lang.String event, IWDAction action);
for example
WDPortalEventing.subscribe (urn:com.sap.tc.webdynpro.test.portal,
    TestEvent,
    wdThis.wdGetTestEventAction());
You have to define the events name and its namespace. The combination of these two names must be unique.
The third parameter is the Web Dynpro action, which should be mapped to the portal event. The action event handler is called if the Web Dynpro application receives the specified portal event on the client side. The mapping between a portal event and a Web Dynpro action is done automatically and it is completely transparent for the Web Dynpro application developer.
You can reuse a Web Dynpro action for several portal events. If you want to receive the portal events data you have to define the following parameters for your Web Dynpro action:
·        dataObject
The dataObject parameter contains the portal event parameter.
·        nameSpace
The namespace parameter contains the portal events namespace.
·        name
The name parameter contains the portal events name.
It is useful to add the nameSpace and nameparameters to the Web Dynpro action if the action is reused for several portal events because you can use this information to differentiate between the portal events.
Note: In the current version a portal event subscription is valid for a Web Dynpro view. Therefore you should add the required Java coding, for example in the wdDoInit() method of the generated view class. If you navigate between different views, you have to subscribe to every view for the portal event required.
Unsubscribe from a portal event
Unsubscribing from a portal event is very similar to subscribing. The following code shows the signature of the unsubscribemethod:
WDPortalEventing.unsubscribe(java.lang.String nameSpace, java.lang.String event, IWDAction action);
for example
WDPortalEventing.unsubscribe (urn:com.sap.tc.webdynpro.test.portal,
    TestEvent,
    wdThis.wdGetTestEventAction());
Note: You must unsubscribe every Web Dynpro view, because subscription and unsubscription is valid only for the current view.
Raise a portal event
The following example shows how to raise a portal event. The signature is:
WDPortalEventing.fire(java.lang.String nameSpace, java.lang.String event, java.lang.String parameter);
for example
WDPortalEventing.fire (urn:com.sap.tc.webdynpro.test.portal,
     TestEvent,
    AParameter);
You can fire a portal event anywhere in your Web Dynpro application. The event is sent to the client with the next response. You can also raise more than one portal event in a request-response cycle. Typically, you will fire a portal event in a Web Dynpro action event handler (for example, as a response to pressing a button).
The following step-by-step example shows how to carry out portal eventing within two simple Web Dynpro example applications.
Example Description
The user can enter an arbitrary string in an input field. If the user presses the pushbutton Click here in the sender view, the input string will be displayed in a TextView UI element of the listener application.
Prerequisites
You have built two Web Dynpro applications. How to build Web Dynpro applications is described in Creating a Simple Web Dynpro Application. In each application you have created a Web Component with a view that uses the portal eventing.
You can find the detailed procedure describing how to insert UI elements into a view in Creating a Simple Web Dynpro Application.
Further information about the integration of a Web Dynpro application into the SAP Enterprise Portal can you find under Running a Web Dynpro Application in SAP Enterprise Portal.
Procedure
Creating the Web Dynpro applications
       1.      Create the Web Dypro project. Call it webdynproexample_portal_eventing.
       2.      Create two Web Dynpro components. Call them:
                            a.      EventSenderComponent
                            b.      EventListenerComponent
       3.      Create two Web Dynpro applications. Call them:
                            a.      EventSenderApplication
                            b.      EventListenerApplication
Creating the necessary views:
Create the layout of the EventSenderView in the EventSenderComponent as follows:
Create the context structure of the EventingSender View:
The context value attribute Name must be of type String.
Create an action Show
Define the data binding of corresponding UI element properties:
The appropriate properties of the UI elements must be bound to the context that contains and displays the data.
       4.      Define a text, for instance, Enter a text: for the label UI element (ID: NameLabel) using the property text.
       5.      Bind the property value of the input field (ID: NameInputField) to the context attribute Name.
       6.      Bind onAction of the button (ID:ShowButton) to the corresponding action Show.
Implementation of the view controller
       7.      If you create an action declaratively within the SAP NetWeaver Developer Studio, the Web Dynpro framework automatically generates an onAction method in the controllers implementation. The generated method enables you to write code to fetch the input string and to fire the portal event. The fire method of WDPortalEventing passes the data and the name of the event that should be handled by the second application as parameters. The following code shows the implementation of onActionShow method:
public void onActionShow(com.sap.tc.webdynpro.progmodel.api.IWDCustomEvent wdEvent )
    //@@begin onActionShow(ServerEvent)
   String name = wdContext.currentContextElement().getName();
    WDPortalEventing.fire("urn:com.sap.tc.webdynpro.example.portaleventing",
                       "Show",
                       name);
    //@@end
Create the layout of the EventListenerView in the EventListenerComponent as follows:
Create the context structure of the EventingListenerView:
The context attribute Name must be of type String.
Create an action, for example, ReactPortalEventing which should be mapped to the portal event.
       8.      Create an action ReactPortalEventing.
       9.      Add the parameter dataObject. It should have the type java.lang.String.
Define the data binding of the corresponding UI element properties:
The corresponding properties of the UI elements must be bound to the context that contains and displays the data.
10.      Define a text for the NameLabel for example, The entry is displayed in a TextView UI element:
   11.      Bind the property text of the TextView UI element (ID: TextViewShow) to the context attribute Name.
Implementation of the views controller
   12.      You have to subscribe to the event within the wdDoInit method. You have to define the namespaceof the event and the name of the event, for example Show. The third parameter is the Web Dynpro action, which should be mapped to the portal event.
   13.      You have to implement the action (ReactPortalEventing) that passes the dataObjectand fills the context with data. The following code shows the implementation of the wdDoInit and the reactPortalEventing methods:
public void wdDoInit()
    //@@begin wdDoInit()
    WDPortalEventing.subscribe("urn:com.sap.tc.webdynpro.example.portaleventing", "Show",
    wdThis.wdGetReactPortalEventingAction() );
    //@@end
public void onActionReactPortalEventing(com.sap.tc.webdynpro.progmodel.api.IWDCustomEvent wdEvent, java.lang.String dataObject )
    //@@begin onActionReactPortalEventing(ServerEvent)
    wdContext.currentContextElement().setName(dataObject);
    //@@end
Deploying the Web Dynpro Application
Before you can call the Web Dynpro application, you have to build the Web Dynpro project and deploy the application on the J2EE Engine.
Simple Testing of the Portal Eventing and Calling the Web Application
   14.      Create two iViews in the newly-created example folder as described in Running a Web Dynpro Application in SAP Enterprise Portal.
   15.      Create a page and add the two iViews to the newly-created page.
To preview the Web Dynpro applications, choose the button Preview in the Portal Content Studio.
   16.      Enter your input and choose button Click here.
Result
A page preview will demonstrate portal eventing.
Also, Please refer to these links,
http://help.sap.com/saphelp_nw04/helpdata/en/c6/21fc3f82c2e469e10000000a155106/content.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webdynpro/portal integration of web dynpro applications.pdf
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cfb80249-0801-0010-3eaa-829afeac170f
Please let me know whether its useful.
Thanks,
Raj.

Portal Eventing JSP TreeView

I am trying to refactor a piece of code that was originally designed using HTMLB to create a tree view role menu that invokes an event in another iView.
My question is, can portal eventing be done with traditional JavaScript as opposed to using HTMLB? We are not using WebDynPro for this project.
I would like to use a jsp treeview to re-engineer the existing htmlb tree structure, but wanted to get some feedback on the options...thanks

Hi Ryan,
> whether or not the eventing
> has to be done on the server side
The eventing between iViews is done by EPCF, and this is, as said, a pure JS framework. Often it might be senseful for the iView which gets "informed" by some other iView about some event with some event data, to use this data and to refresh itself. This depends on the concrete use case.
Having this said, it is obviously totally independent if you usue EPCF from some portal HTMLB-JSP, a "pure" JSP without HTMLB or a BSP - all of these things end up in HTML with the possibility to include JS - the EPCF calls.
See http://help.sap.com/saphelp_nw04/helpdata/en/82/04b340be3dff5fe10000000a155106/frameset.htm for further details.
> Can all of this be done without post backs
> to the server,
As said before, the eventing through EPCF works on client side, but in many cases it makes sense to refresh some iView with some data sent by the event.
Imagine a List-Details iView combination. The user has one iView with a list of products and another iView with the details of one product. By choosing one product in the list iView, this iView could raise an event, which is subscribed by the details iView, for example passing some product-ID. Now it would make sense to refresh the details iView with the ID given. The alternative would be to load all details data and only to show up the chosen details and to switch on the event. Two disadvantages: It's much harder to code and you may have a very long transmission/network time for the inital call of this iView.
> without using htmlb using JSP not BSP
See above, it's independent from the HTML-Layer.
> can you store a result set in a client side object,
> like a cookie, and if so, how?
For sure, somehow you can (at least some representation). But here I'm unsure again, in which direction this question aims, if this is really helpful.
Hope it helps
Detlev

Problem in calling BAPI on HTML screen

Hi all,
i have an input tag on the html screen and ~event linked to the form is say Confirm.
so when anyone clicks on button so it calls BAPI for the online form. it is making the server slow and after some time it gives the internal server error.
say
 <event name="Confirm" next_state="Confirm"/>
 <state name="Confirm">
 <module name="ZV_FUNC_CCK_CONFIRM_ORDER" type="RFC" stateful="1">
 <result next_template="ZV_CCO_CONFIRMED_ORDER">
 <expr>RET == ""</expr>
 </result>
 <inputmapping source="Contract" target="CONTRACT"/>
 <inputmapping source="SHIP_TO" target="CUSTOMER"/>
 <inputmapping source="CONT_ITEM" target="ITEM"/>
 <inputmapping source="RET" target="RET"/>
 <inputmapping source="TRANSPORT" target="TRANSPORT"/>
 <outputmapping source="ITEM" target="CONT_ITEM"/>
 <outputmapping source="RET" target="RET"/>
 <outputmapping source="SALESORDER" target="SALESORDER"/>
 </module>
 </state>
thanks
ekta

Thanks
Ekta

Portal eventing between Java WD iview to ABAP WD iview?

HI Experts ,
I have requirement on which,
The manager can select an employee from the EE Search iView (Object and Data Provider). All other iViews react on the selection and display data of the selected employee. Technically the personnel number is transferred from the search iView to the other iViews on the portal page, also to the related activity iView. This mechanism is called Eventing. The applications, started via the related activity iView, are launched with the personnel number as parameter. With other words the application, e.g. Manage Objects on Loan, can be directly started for the employee selected from the EE Search iView.
The Employee Information page is based on WD Java whereas the Objects on Loan application described in this specification is based on WD ABAP...........Due to different technologies used how to do the Pernr number transfer between these iviews?
If anybody have done this let me know the steps
Thanks in Advance,
Dharani

Hi Dharani,
You can use portal events to enable iViews running on the same page to communicate with each other. You just have to find out which event is fired by the WD Java iView and then you will have to register and handle the event in your WD ABAP application : http://help.sap.com/saphelp_nw70ehp1/helpdata/en/f6/7d6f4151dc5758e10000000a1550b0/frameset.htm
You can use HttpFox (firefox plug-in) to find the details of the fired event (name, namespace...) by looking at the eventQueue parameter in the HTTP POST request.
Regards,
Pierre
Edited by: Pierre DOMINIQUE on Jul 9, 2009 11:16 AM

Call BAPI in Web Dynpro

I want to call a BAPI using web Dynpro.
In my case, the BAPI without input parameter, it only give out a out table after execute.
So that I include this Bapi in the model and directly call it in wdDoInit like this :
wdContext.nodeZbapi_Outvendor_Input().currentZbapi_Outvendor_InputElement().modelObject().execute();
wdContext.nodeZbapi_Outvendor_Input().invalidate();
However, no any result can see. Anybody could tell me what is the correct way to call BAPI in WD?
Thanks!

Hi,
Don't invalidate the zbapi node...
If your output can be recieved from the node say.., output from the bapi side and you mapped it to controller to node say OutVend...
Then use this code
wdContext.nodeOutVend().bind(wdContext.nodeZbapi_Outvendor_Input().currentZbapi_Outvendor_InputElement().modelObject().getOutput());
Any queries revert back.
If this is not working post your context structure in your reply and tell where you are expect the output
Best Wishes,
Idhaya R

Portal Eventing in Webdynpro ABAP

Hello,
I am trying to implement Eventing in Webdynpro ABAP using 2 components ,Com1 serving as the source component and Com2 serving as Target. In Com1 I created a Inputfield and a button ,and then tied an action to the button and called the FIRE method of the IF_WD_PORTAL_INTEGRATION and sent the value in the Inputfield as the eventing parameter.
In Com2, i subscribed to the event in the wddoinit() method and then defined an action for the same and got the parameter value sent in the Com1 and set the value in the context attribute in the Com2 which is bound to the inputfield.
But still the value sent in Com1 is not displayed in the Com2 Inputfield.
Any help would be highly appreciated.
Thanks.

>
SAPEPDeveloper wrote:
> Hello,
>
> I am trying to implement Eventing in Webdynpro ABAP using 2 components ,Com1 serving as the source component and Com2 serving as Target. In Com1 I created a Inputfield and a button ,and then tied an action to the button and called the FIRE method of the IF_WD_PORTAL_INTEGRATION and sent the value in the Inputfield as the eventing parameter.
>
> In Com2, i subscribed to the event in the wddoinit() method and then defined an action for the same and got the parameter value sent in the Com1 and set the value in the context attribute in the Com2 which is bound to the inputfield.
>
> But still the value sent in Com1 is not displayed in the Com2 Inputfield.
>
> Any help would be highly appreciated.
>
> Thanks.
Hi I assume the following, please correct me if my understanding is not correct.
1.First of all you try this in Portal.
2.The moment you fire the event, the comp-2 view is active and subscribed to the portal event.
If the above are true then tell me if the portal eventing enter into the action ?Have you checked in bebug that your action is triggerred on portal_event ?
If portal event is action handler is called then if you have a importing parameter portal_event_parameter then your input value should be there.

Events in Bapi

Hello,
How do Handle the "Events in Bapi "?
Where do we write the code to trigger the Events ?
Please explain me clearly.
Thanks in Advance.

Hi,
The Event inside the BAPI (Business Object) can be called by following Function Module:
CALL FUNCTION 'SWE_EVENT_CREATE'
EXPORTING
 objtype = 'ZWOCONT' " Business Object Name
 objkey = v_objkey " Document Number i.e. Input Parameter
 event = 'ZWEMODIFIED' " Event Name in the BAPI to be called
EXCEPTIONS
 OBJTYPE_NOT_FOUND = 1
 OTHERS = 2
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
Rgds,
Ramani N

Portal Eventing in WebDynpro Java Pros and Cons

Does anyone have a link to an article that discusses th epros and cons of using portal eventing between dynpro development components between iViews rather than using one larger web dynpro application. I am clear that reuse can be an issue if you don't make each view t's own development component but I also find portal eventing to be very lacking. What do others think about on this issue and is that an SAP recommendation?
Shawn

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a3c57e19-0d01-0010-ad8b-9edde6d1fae7
Please read the restriction section.
I will make much more sense if we need a high degree of data interchange between WDP components, to use context mapping and thus internal WDP calls rather than portal eventing.
hth

Can i call BAPIs with explict commit uisng xi

I have a RFC which has 3 BAPI's inside it . Each Bapi is using an explict commit. Can i call this RFC from XI .

Hi,
You have 2 options..
In the RFC Receiver Communication channel set the Advanced Property - "Commit Control for Individual BAPI Calls"
the description in help is as follows -
Commit Control for Individual BAPI Calls
If you want to use this communication channel to call BAPIs as remote-enabled function modules that change data in the database, set the indicator.
If executed successfully, the transaction is written to the database by calling the function module BAPI_TRANSACTION_COMMIT explicitly. If an error occurs, the transaction is rolled back by BAPI_TRANSACTION_ROLLBACK.
The result is determined by the value of the field TYPE in parameter RETURN. If successful, the tables are empty and the values , S, I, and W are displayed. All other values are regarded as errors.
To change this setting, set the indicator BAPI Advanced Mode.
In the Successful RETURN-TYPE Values table, enter the values that should lead to a successful execution.
http://help.sap.com/saphelp_nw04/helpdata/en/c8/e80440a832e369e10000000a155106/frameset.htm
or
you can include the commit in the RFC(if it is a custom one...)
Thanks,
Renjith

WD Abab - Portal Events from Employee Search

Hi guys,
I want to get the PERNR selected in Employee Search.
I have two ivews,
Employee Search and WD Abap.
I´m using this source to subscribe the portal event.
method WDDOMODIFYVIEW .
data l_api_component type ref to if_wd_component.
data l_portal_manager type ref to if_wd_portal_integration.
l_api_component = wd_comp_controller->wd_get_api( ).
l_portal_manager = l_api_component->get_portal_manager( ).
data l_wd_view type ref to if_wd_view_controller.
l_wd_view ?= wd_this->wd_get_api( ).
call method l_portal_manager->subscribe_event    exporting
      portal_event_namespace = 'urn:com.sap.pct.hcm.orgmanagement:CurrentObject'
      portal_event_name      = 'objectChanged'
      view                   = view
      action                 = 'PORTAL_EVENT'.
endmethod.
What´s the action I have to implement ?
And How I could get the PERNR selected ?
Best Regards,
Silvio Galery

Do i understand you correctly that you are not getting the portal event ?
This can be several reasons ?
Both portal system and WDA server has to be in same domain and same proptocol to communicate with Portal event.
Please check in that direction and search posts on this topic.

Calling BAPI in Webdynpro or EP

Hi
any one can u send how to store data in r/3 when we submit the form in either webdynpro or EP . i mean how to call BAPIs
Regards
sunil

Hi Sunil
Refer to
<a href="https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/16244247-0a01-0010-3294-d81c21e7e86e">VC</a>
2)
<a href="https://www.sdn.sap.com/irj/sdn/developerareas/webdynpro?rid=/library/uuid/49f2ea90-0201-0010-ce8e-de18b94aee2d">Webdynpro</a>
SDN :-https://www.sdn.sap.com/irj/sdn/howtoguides
Check for RFC there
Thanx
Pankaj

Portal Eventing calls BAPI - result FAILURE!

Similar Messages

Maybe you are looking for