Alert in BSPs

Hi,
I have a question regarding BSPs.
how can we include a Java script inside a BSP application??
now, my requirement is that, I have done a page(HTML) in the front page.
thing is that, I copied the code(with validations) into the BSP application.
it is giving errors...I think, I have not included the Javascript properly into the BSP application.
could any one of u who has got some idea, can pls help me over this matter??
problem:
suppose,I have taken an input tag like :<input type="text" name="param1" value="">.
now, I validated this field(in Front page) as :
if(form.param1.value==0){
alert("pls enter some value for name");
now,
I want to copy the same code in the BSP application and should be able to see
the alert in this BSP application.
it is happening now....can u tell the solution for this??
Thanks in advance.
Best Regards,
vamshi

hI Vamshi,
Make changes to your code to look something like this:
<%@page language="abap" %>
<%@extension name="htmlb" prefix="htmlb" %>
<head>
<SCRIPT language="JavaScript">
function validate()
if(document.form1.param1.value==0)
alert("pls enter some value for name");
</SCRIPT>
</head>
<htmlb:content design="design2003" >
<htmlb:page title="Java Script for date " >
<htmlb:form id = ""form1>
This should help you.
Regards,
Ravikiran

Similar Messages

Getting exception when trying to open Alert Configuration in RW

Hello friends,
I am getting the following exception when i am trying to open the Alert Configuration/Alert Inbox in RWB.
Exception:
com.sap.aii.rwb.exceptions.BuildLandscapeException: No central monitoring server in exchange profile
        at com.sap.aii.rwb.core.MonitoringServer.(MonitoringServer.java:77)
        at com.sap.aii.rwb.agent.server.SLDAgentBean.buildMonitoringServer(SLDAgentBean.java:799)
        at com.sap.aii.rwb.agent.server.SLDAgentBean.getMonitoringServer(SLDAgentBean.java:1462)
        at com.sap.aii.rwb.agent.api.SLDAgentObjectImpl0.getMonitoringServer(SLDAgentObjectImpl0.java:999)
        at com.sap.aii.rwb.agent.api.SLDAgent_Stub.getMonitoringServer(SLDAgent_Stub.java:1931)
        at com.sap.aii.rwb.agent.client.EJBAgent.getMonitoringServer(EJBAgent.java:493)
        at jsp_alert_inbox1204719699497._jspService(jsp_alert_inbox1204719699497.java:28)
        at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
        at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:544)
        at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:186)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
        at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
        at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
        at jsp_FC_Secure1204104271605._jspService(jsp_FC_Secure1204104271605.java:24)
        at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
        at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:544)
        at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:186)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
        at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
        at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
        at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
        at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
        at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
        at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
        at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
        at java.security.AccessController.doPrivileged(Native Method)
        at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
        at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Could you please help me out in solving this problem?
Thanks & Regards,
Senthil

From your error, maybe your profile parameter for alert message server is not properly configured:
I just came cross a post elaborating alerting configuration from Aashish Sinha, hope it helps,
Liang
=====Post from Aashish Sinha=======
Prerequisites
The following prerequisites have to be met in order to use the Alert Management (ALM):
· For using the Alert Inbox (BSP based display program of ALM), the corresponding service has to be activated in the service maintenance transaction SICF. Choose Default_host ? sap ? bc ? bsp ? sap ? alert inbox, and Activate in the context menu.
· For customizing or administration of the Alert Management the corresponding authorization role has to be assigned. The end users do not need any additional authorization.
· The central alert server must be maintained as an RFC destination in transaction SM59 in the local system. If there is no suitable user, you have to create a user for the RFC connection in the central alert system in transaction SU01. To make this RFC destination known as the RFC destination of the Alert Management System in the local system, the central alert server must also be selected as the RFC destination in transaction SALRT1 of the local system or in Settings ? RFC-Destination of Alert Server.
If the central alert server is running on the local system in the same client, you do not have to maintain an RFC destination. In this case, you can simply enter NONE in transaction SALRT1.
· If external communication types, such as e-mail, SMS, and fax are used, these communication types must be correctly configured in SAPconnect, because the alerts are then sent from the central alert system via SAPconnect.
Process Flow
The following describes the process flow from alert configuration (transaction ALRTCATDEF) to alert display and confirmation (for example in the alert inbox transaction ALRTINBOX):
1. Optional: You can define alert classifications. These are useful to group alert categories. For example, you can create an alert classification CRM that contains alert categories referring to CRM. Alert classifications can now have subclassifications. This enables you to build up your own classification hierarchy. Especially, if you use the Alert Mangement (ALM) extensively, classification and subclassification help you to organize your ALM alert landscape and to have a clear overview.
2. For different types of alerts you have to define different categories. The category contains various properties and other specifications that define the alerts within that category, for example expiry date, or the escalation recipient. You can define an alert category to suit your business requirements and assign the category to the corresponding classification. For example, for the alert classification CRM you can create the alert categories Contract Cancelled and Decrease in Sales. When the critical situation defined in the alert category arises, the system recognizes this and sends an alert instance of this category to the recipients determined. The alerts can always be found in the display programs configured for the recipient (UWL, application-specific program, or alert inbox). Additionally, the alerts are sent via eventual external communication channels, such as e-mail, sms, or fax.
3. You have to determine recipients so that the Alert Management knows who the recipients of alerts of a particular category are and that the correct parties are informed.
4. You can configure the way how alerts are processed. For the general use of the Alert Management you do not have to change the default settings. However, if for example you want to send alerts to third-party systems, or to be able to confirm alerts by SMS/Internet mail, or to have logs written, then you have to configure alert processing.
5. There is a number of Alert Management administration reports that you must schedule according to your requirements. For example, report RSALERTPROC must be executed in order to enable escalation.
6. Alerts of a particular category must be triggered by an application at runtime. Triggering alerts can be done in various ways. You can call a function module directly or use middleware components that trigger alerts, such as the Business Object Repository (BOR), Post Processing Framework (PPF), SAP Workflow, or CCMS.
7. Recipients can view the alerts assigned to them in the UWL of Enteprise Portal, in application-specific display programs, or in the alert inbox. In addition, alerts can be received as e-mail, SMS, or fax, if these external communication channels are configured in SAPconnect.
8. If the problem causing the alert is solved by a recipient, the recipient can confirm the alert, this means its status is changed and it will not be delivered, escalated, or displayed anymore. Alerts are generally confirmed by the recipient in the display program, such as the UWL or Alert Inbox. However, if an alert is sent by Internet mail or SMS message, it is also possible to confirm it by sending an Internet mail or SMS message back to the SAP system. Alert Management uses inbound processing for this.
Hope this will help you.
Regards
Aashish Sinha
============End of the Post=======================

Authorization to Create the Alert Rules?

Hello All,
I created the Alert category in ALRTCATDEF transaction, now when i want to create the Alert rules in RWB.
Add Rule and Change Rule is in disable mode. my user have SAP_XI_ADMINISTRATOR authorization,
please tell me any other authorization role required to create the alert rules in RWB.
Thanks and Regards,
chinna

Hi,
Steps of alert configuration :
Prerequisites
The following prerequisites have to be met in order to use the Alert Management (ALM):
u2022 For using the Alert Inbox (BSP based display program of ALM), the corresponding service has to be activated in the service maintenance transaction SICF. Choose Default_host ® sap ® bc ® bsp ® sap ® alert inbox, and Activate in the context menu.
u2022 For customizing or administration of the Alert Management the corresponding authorization role has to be assigned. The end users do not need any additional authorization.
u2022 The central alert server must be maintained as an RFC destination in transaction SM59 in the local system. If there is no suitable user, you have to create a user for the RFC connection in the central alert system in transaction SU01. To make this RFC destination known as the RFC destination of the Alert Management System in the local system, the central alert server must also be selected as the RFC destination in transaction SALRT1 of the local system or in Settings ® RFC-Destination of Alert Server.
If the central alert server is running on the local system in the same client, you do not have to maintain an RFC destination. In this case, you can simply enter NONE in transaction SALRT1.
u2022 If external communication types, such as e-mail, SMS, and fax are used, these communication types must be correctly configured in SAPconnect, because the alerts are then sent from the central alert system via SAPconnect.
Process Flow
The following describes the process flow from alert configuration (transaction ALRTCATDEF) to alert display and confirmation (for example in the alert inbox transaction ALRTINBOX):
1. Optional: You can define alert classifications. These are useful to group alert categories. For example, you can create an alert classification CRM that contains alert categories referring to CRM. Alert classifications can now have subclassifications. This enables you to build up your own classification hierarchy. Especially, if you use the Alert Mangement (ALM) extensively, classification and subclassification help you to organize your ALM alert landscape and to have a clear overview.
2. For different types of alerts you have to define different categories. The category contains various properties and other specifications that define the alerts within that category, for example expiry date, or the escalation recipient. You can define an alert category to suit your business requirements and assign the category to the corresponding classification. For example, for the alert classification CRM you can create the alert categories Contract Cancelled and Decrease in Sales. When the critical situation defined in the alert category arises, the system recognizes this and sends an alert instance of this category to the recipients determined. The alerts can always be found in the display programs configured for the recipient (UWL, application-specific program, or alert inbox). Additionally, the alerts are sent via eventual external communication channels, such as e-mail, sms, or fax.
3. You have to determine recipients so that the Alert Management knows who the recipients of alerts of a particular category are and that the correct parties are informed.
4. You can configure the way how alerts are processed. For the general use of the Alert Management you do not have to change the default settings. However, if for example you want to send alerts to third-party systems, or to be able to confirm alerts by SMS/Internet mail, or to have logs written, then you have to configure alert processing.
5. There is a number of Alert Management administration reports that you must schedule according to your requirements. For example, report RSALERTPROC must be executed in order to enable escalation.
6. Alerts of a particular category must be triggered by an application at runtime. Triggering alerts can be done in various ways. You can call a function module directly or use middleware components that trigger alerts, such as the Business Object Repository (BOR), Post Processing Framework (PPF), SAP Workflow, or CCMS.
7. Recipients can view the alerts assigned to them in the UWL of Enteprise Portal, in application-specific display programs, or in the alert inbox. In addition, alerts can be received as e-mail, SMS, or fax, if these external communication channels are configured in SAPconnect.
8. If the problem causing the alert is solved by a recipient, the recipient can confirm the alert, this means its status is changed and it will not be delivered, escalated, or displayed anymore. Alerts are generally confirmed by the recipient in the display program, such as the UWL or Alert Inbox. However, if an alert is sent by Internet mail or SMS message, it is also possible to confirm it by sending an Internet mail or SMS message back to the SAP system. Alert Management uses inbound processing for this.
Refer these links :
Check these Usefull BLOGs also
/people/bhavesh.kantilal/blog/2006/07/25/triggering-xi-alerts-from-a-user-defined-function
/people/michal.krawczyk2/blog/2007/04/26/xipi-throwing-generic-exceptions-from-any-type-of-mapping
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step - Alert Configuration
I tried to format it..But Dunno why it's appearing this way...**
Edited by: Sainath Chutke on Aug 12, 2010 8:43 AM

How to create alerts in xi

hi friends,
pls help on this topic creation of alterts.
ravi

Hi,
Alert Configuration
You use the alert configuration to have the system inform you of errors during message processing. You can receive the alert by e-mail, fax, or SMS. In each case you will also find the alert in your alert inbox.
Prerequisites
The following prerequisites have to be met in order to use the Alert Management (ALM):
·        For using the Alert Inbox (BSP based display program of ALM), the corresponding service has to be activated in the service maintenance transaction SICF. Choose Default_host ® sap ® bc ® bsp ® sap ® alert inbox, and Activate in the context menu.
·        For customizing or administration of the Alert Management the corresponding authorization role has to be assigned. The end users do not need any additional authorization. You find more information under Authorization Concept.
·        The central alert server must be maintained as an RFC destination in transaction SM59 in the local system. If there is no suitable user, you have to create a user for the RFC connection in the central alert system in transaction SU01 (see User Administration and Authorization Concept). To make this RFC destination known as the RFC destination of the Alert Management System in the local system, the central alert server must also be selected as the RFC destination in transaction SALRT1 of the local system or in Settings ® RFC-Destination of Alert Server.
If the central alert server is running on the local system in the same client, you do not have to maintain an RFC destination. In this case, you can simply enter NONE in transaction SALRT1.
·        If external communication types, such as e-mail, SMS, and fax are used, these communication types must be correctly configured in SAPconnect, because the alerts are then sent from the central alert system via SAPconnect.
Process Flow
The following describes the process flow from alert configuration (transaction ALRTCATDEF) to alert display and confirmation (for example in the alert inbox transaction ALRTINBOX):
       1.      Optional: You can define alert classifications. These are useful to group alert categories. For example, you can create an alert classification CRM that contains alert categories referring to CRM. Alert classifications can now have subclassifications. This enables you to build up your own classification hierarchy. Especially, if you use the Alert Mangement (ALM) extensively, classification and subclassification help you to organize your ALM alert landscape and to have a clear overview.
       2.      For different types of alerts you have to define different categories. The category contains various properties and other specifications that define the alerts within that category, for example expiry date, or the escalation recipient. You can define an alert category to suit your business requirements and assign the category to the corresponding classification. For example, for the alert classification CRM you can create the alert categories Contract Cancelled and Decrease in Sales. When the critical situation defined in the alert category arises, the system recognizes this and sends an alert instance of this category to the recipients determined. The alerts can always be found in the display programs configured for the recipient (UWL, application-specific program, or alert inbox). Additionally, the alerts are sent via eventual external communication channels, such as e-mail, sms, or fax.
       3.      You have to determine recipients so that the Alert Management knows who the recipients of alerts of a particular category are and that the correct parties are informed.
       4.      You can configure the way how alerts are processed. For the general use of the Alert Management you do not have to change the default settings. However, if for example you want to send alerts to third-party systems, or to be able to confirm alerts by SMS/Internet mail, or to have logs written, then you have to configure alert processing.
       5.      There is a number of Alert Management administration reports that you must schedule according to your requirements. For example, report RSALERTPROC must be executed in order to enable escalation.
       6.      Alerts of a particular category must be triggered by an application at runtime. Triggering alerts can be done in various ways. You can call a function module directly or use middleware components that trigger alerts, such as the Business Object Repository (BOR), Post Processing Framework (PPF), SAP Workflow, or CCMS.
       7.      Recipients can view the alerts assigned to them in the UWL of Enteprise Portal, in application-specific display programs, or in the alert inbox. In addition, alerts can be received as e-mail, SMS, or fax, if these external communication channels are configured in SAPconnect.
       8.      If the problem causing the alert is solved by a recipient, the recipient can confirm the alert, this means its status is changed and it will not be delivered, escalated, or displayed anymore. Alerts are generally confirmed by the recipient in the display program, such as the UWL or Alert Inbox. However, if an alert is sent by Internet mail or SMS message, it is also possible to confirm it by sending an Internet mail or SMS message back to the SAP system. Alert Management uses inbound processing for this.
Please refer http://help.sap.com/saphelp_nw04/helpdata/en/49/cbfb40f17af66fe10000000a1550b0/frameset.htm for more details. This link contains everything about Alerts.
Hope this will solve your query.
Regards
Aashish Sinha
PS : reward points if helpful and don't forget to close this thread.

How to send XML Messages in XI

Using XI 3.0, XDV
Tcode XSMB_MONI
Display all errors, how to sent automatically in email
please tell me step by step procedure....
Thanks

Hi,
You have to configure alert for you requirement.
Prerequisites
The following prerequisites have to be met in order to use the Alert Management (ALM):
·        For using the Alert Inbox (BSP based display program of ALM), the corresponding service has to be activated in the service maintenance transaction SICF. Choose Default_host ® sap ® bc ® bsp ® sap ® alert inbox, and Activate in the context menu.
·        For customizing or administration of the Alert Management the corresponding authorization role has to be assigned. The end users do not need any additional authorization.
·        The central alert server must be maintained as an RFC destination in transaction SM59 in the local system. If there is no suitable user, you have to create a user for the RFC connection in the central alert system in transaction SU01. To make this RFC destination known as the RFC destination of the Alert Management System in the local system, the central alert server must also be selected as the RFC destination in transaction SALRT1 of the local system or in Settings ® RFC-Destination of Alert Server.
If the central alert server is running on the local system in the same client, you do not have to maintain an RFC destination. In this case, you can simply enter NONE in transaction SALRT1.
·        If external communication types, such as e-mail, SMS, and fax are used, these communication types must be correctly configured in SAPconnect, because the alerts are then sent from the central alert system via SAPconnect.
Process Flow
The following describes the process flow from alert configuration (transaction ALRTCATDEF) to alert display and confirmation (for example in the alert inbox transaction ALRTINBOX):
       1.      Optional: You can define alert classifications. These are useful to group alert categories. For example, you can create an alert classification CRM that contains alert categories referring to CRM. Alert classifications can now have subclassifications. This enables you to build up your own classification hierarchy. Especially, if you use the Alert Mangement (ALM) extensively, classification and subclassification help you to organize your ALM alert landscape and to have a clear overview.
       2.      For different types of alerts you have to define different categories. The category contains various properties and other specifications that define the alerts within that category, for example expiry date, or the escalation recipient. You can define an alert category to suit your business requirements and assign the category to the corresponding classification. For example, for the alert classification CRM you can create the alert categories Contract Cancelled and Decrease in Sales. When the critical situation defined in the alert category arises, the system recognizes this and sends an alert instance of this category to the recipients determined. The alerts can always be found in the display programs configured for the recipient (UWL, application-specific program, or alert inbox). Additionally, the alerts are sent via eventual external communication channels, such as e-mail, sms, or fax.
       3.      You have to determine recipients so that the Alert Management knows who the recipients of alerts of a particular category are and that the correct parties are informed.
       4.      You can configure the way how alerts are processed. For the general use of the Alert Management you do not have to change the default settings. However, if for example you want to send alerts to third-party systems, or to be able to confirm alerts by SMS/Internet mail, or to have logs written, then you have to configure alert processing.
       5.      There is a number of Alert Management administration reports that you must schedule according to your requirements. For example, report RSALERTPROC must be executed in order to enable escalation.
       6.      Alerts of a particular category must be triggered by an application at runtime. Triggering alerts can be done in various ways. You can call a function module directly or use middleware components that trigger alerts, such as the Business Object Repository (BOR), Post Processing Framework (PPF), SAP Workflow, or CCMS.
       7.      Recipients can view the alerts assigned to them in the UWL of Enteprise Portal, in application-specific display programs, or in the alert inbox. In addition, alerts can be received as e-mail, SMS, or fax, if these external communication channels are configured in SAPconnect.
       8.      If the problem causing the alert is solved by a recipient, the recipient can confirm the alert, this means its status is changed and it will not be delivered, escalated, or displayed anymore. Alerts are generally confirmed by the recipient in the display program, such as the UWL or Alert Inbox. However, if an alert is sent by Internet mail or SMS message, it is also possible to confirm it by sending an Internet mail or SMS message back to the SAP system. Alert Management uses inbound processing for this.
Hope this will help you.
Regards
Aashish Sinha
PS : reward points if helpful

PI 7.0 Alert Configuration Problem BSP Page Error

Hello,
We are facing the issues for the alert configuration tab in Runtime workbench for PI 7.0.
We have added the fully qualified domain name in exchange profile and 8000 port is also updated for RWB.
We have activated all the SICF services by the report
RSXMB_ACTIVATE_ICF_SERVICES and all the services are activated successfully.
But still When we click on Alert configuration we can see the page but we when we try for
any function, its giving the following error.
Error log is:
Access via 'NULL' object reference not possible.
the termination type was : RABAX_STATE
http://s71cam.corp.wrgrace.com:8000/sap/bc/bsp/sap/sxms_alertrules/main.do was not called due to error
Also in ST22 I can find the following dump:
Dump:     OBJECTS_OBJREF_NOT_ASSIGNED
Error analysis
    You attempted to use a 'NULL' object reference (points to 'nothing')
    access a component (variable: " ").
    An object reference must point to an object (an instance of a class)
    before it can be used to access components.
    Either the reference was never set or it was set to 'NULL' using the
    CLEAR statement.
Please help.

Hi deepak
follow these sap notes
Note 771317 - BSP call terminates with RABAX_STATE
https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=771317
Note 992800 - "RABAX_STATE" dump is coming while paging
https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=992800
Note 643933 - RABAX_STATE: Conversion overflow
https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=643933
https://www.sdn.sap.com/irj/sdn/advancedsearch?query=rabax_state&cat=sdn_all
thanks
sandeep
if hepful rewartd points

E-Mail Alerts Configuration in PI ... BSP error

Hi All
Am configuring alert framework. Process till getting them in Alert Inbox is done. Now I wanna direct the alerts to my e-mail ID.
Steps that i am doing :
1. E-Mail ID added in SU01.
2. SCOT configuration is done.
3. Now under Alert Inbox(RWB) when i try to use the Personalization tab it throws a BSP error stating :
BSP exception: Cannot start application sap/alertpersonalize_rules. Use transaction SICF to create application node. gsknoten an.
*Error type: *
Your SAP Business Server Pages Team
Now I don't have enough time to contact the team(Honestly I don't even know if there's such a team :P ). Hence thought of doing it myself. Am not bothered about accesses. I have any access required at my disposal. But I need the exact steps to be followed in SICF.
Tried following this : http://help.sap.com/saphelp_nw04/helpdata/en/49/cbfb40f17af66fe10000000a1550b0/frameset.htm But am lost now.
Kindly suggest me how to get this Personalization tab (in RWB) activated.

Did not see any settings required on Personalization tab at least in this document
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/00e97ba2-85ce-2b10-20bc-bc05cd172154&overridelayout=true
Please check if it helps.

How to display an alert message on click of link in tableview

Hi,
Following is the code for a tableview in layout section of a BSP( i have specified only one tableview column here). The requirement is to display an alert message on click of link in the first column that is "evbeg". Can anyone please help me how to achieve this? Appreciate quick response on this.
CREATE OBJECT lr_dateiterator TYPE cl_lso_bsp_it_trdates
            EXPORTING im_application = application
            im_tform = trainingform.
        <htmlb:tableView id            = "dates"
                             table         = "<%= dates %>"
                             iterator      = "<%= lr_dateiterator %>"
                             width         = "100%"
                             rowCount      = "<%= lp_len %>"
                             footerVisible = "FALSE"
                             sort          = "SERVER" >
              <htmlb:tableViewColumn columnName    = "evbeg"
                                     type          = "user"
                                     title         = "<%= otr(LSO_FRONTEND/schedule) %>"
                                     tooltipHeader = "<%= otr(LSO_FRONTEND/schedule) %>"
                                     sort          = "TRUE" >
              </htmlb:tableViewColum>
Thanks and Regards,
Archana.

you have to code in the iterator for this.
in the render_cellstart method of the iterator you need to code.
this is for a column.
when 'MATNR'.
data: text type string.
text = 'disp_alert()'.   "this java script i placed in the page
data: lo_link type ref to cl_htmlb_link.
create object lo_link.
     lo_link->id = p_cell_id.
     lo_link->onclientclick = text.
     lo_link->text = <fs>-matnr.
     p_replacement_bee = lo_link.
below is the java script i added in my page..
< sc ri   pt type="text/javasc ript"   >
f u n ction disp_alert()
a l e rt("helloworld");
< /s c ript >

SSO to BSP

Hi everybody,
I've tried to perform SSO to an BSP from Portal through the AppIntegrator Generic iView Template.
So I didn't used the BSP Template.
First I created a system from par file sap.com.portal.howtos.webapp and made all the settings.
After that I have sat the user mapping for the created system.
Next I created an iView from the com.sap.portal.appintegrator.sap.Generic. I performed all the settings.
As URL Template: <System.protocol>://<System.server>:<System.port>/<System.uri>?<Authentication>
URl template for user mapping:
login=<MappedUser>&passwd=<MappedPassword>
When I tested the BSP, I first got the browser message that session management will not work. After I turned the alert off in Support - > SAP Application, I got to the logon of the BSP Application, so SSO didn't worked.
So, is it att all possible to set SSO to a BSP like for normal Web Applications? And if yes what could be wrong?
Regards

Hi Praveen,
I solved the problem described above. This means I am now able to perform SSO to an BSP with UIDPW like to any other Web Application.
But I've done this through an Gereric AppInt iView not through the BSP template. The reason therefore is that I tried to establish SSO between the portal and the R/3 system. I've done all the settings in the System. Imported the certificate nad set the profile parameters. In transaction SSO2 I saw that the system is ready to accept logon tickets from my Portal server.
In the system landscape I've created an " SAP System with connection string", because I'm accessing the system through an SAProuter. But when I try to test the connection through
Support - > SAP Application I get the message "host ? unknown".
so my guess is that the connection string is not ok. But I am using the same one as in the SAP GUI where it works? So maybe some tipps.
Maybe I can also use an "dedicated system"?
Regards

How to return values from a BSP page to Javascript

Hi All,
I want to call a BSP page which reads a single value from a table and returns that value I want the Javascript in the HTML code to get the value from the BSP page.
Can you kindly let me know how I can return the value from the BSP page to JavaScript.
Kindly please provide me a simple code of a BSP page and the Javascript
Thanks
Karen

Hi,
you need 3 elements to make the javascript code read the value in any field in the table: table´s name, line and column. This is how your code could look like:
script language="javascript>
   var row = 0;
   function display(){
      row = row + 1;
      campo = 'tabla1_' + row + '_4';                 " <-- table, line, column
      valor = document.getElementById(campo).value;
</script>
ROW works as a counter. You have in variable valor the value of the field and can do with it what you want, perhaps display it with ALERT. I am reading the values from field 1 to n in column 4 in table TABLA1. Pay attention to the '_' in the concatenation of field´s name. The table in my BSP is very simple:
<htmlb:tableView id                = "tabla1"
                       table             = "<%= mytable %>"
                       width             = "100%"
                       allRowsEditable   = "X"/>
and somewhere I must call function display in my javascript code:
<htmlb:button id="boton" text="Texto aqui" onClientClick="display()" />
So, give it a try.

How to deal the timeout session in BSP application

Hello everybody,
inside a BSP application, I want to inform the user that he is near to reach the timeout of its session.
So I wonder how to know the lifetime of the session and how to calculate the time from its connection.
Anyone of you can help me on his topic?
Thanks in advance.

Starting point: <a href="/people/mark.finnern/blog/2003/09/24/bsp-in-depth-confusion-between-stateless-stateful-and-authentication">BSP In-Depth: Confusion between Stateless, Stateful and Authentication</a>
The trick will be to after each roundtrip set a JavaScript timer tied to a alert statement. The weblog gives you ideas of what values you want to look at.

Error while opening Alert Configuration

Dear All,
When I am trying to open Alert Configuration from RWB then it is giving me the following error:
<b>URL http://sapxiprd.nissap.com:8000/sap/bc/bsp/sap/alertinbox/index.htm call was terminated because the corresponding service is not available.
Note:
The termination occurred in system XPR with error code 403 and for the reason Forbidden.
The selected virtual host was 0 .
ErrorCode:ICF-NF-http-c:000-u:SAPSYS-l:E-i:SAPXIPRD_XPR_00-v:0-s:403-r:Forbidden
</b>
Kindly help me what is the error and how this can be resolved.
Warm Regards,
N.Jain

Hi,
Go to Transaction SICF and check for the activeness of Service called /bc/bsp/sap/alertinbox.. if not make it active.
Also check this SAP note: -517484
Hope this helps,
rgds,
Moorthy

Handling error in XI with CCMS and Alert Monitor

Hello,
I have configured the CCMS for handling XI error and use the auto-reaction method CCMS_Send_Alert_to_ALM for sending an alert when i have for exemple a mapping error.
The issues are :
1) When an alert is catched I can send an email or having a notification in the alertinbox but not the both.
2) When an alert is catched in the CCMS, this alert is in an active status and i can't receive a second alert if another error occurs in XI until i have completed manually the first alert. Is it possible to complet this alert automatically or having more than one alert active for the same node in the CCMS ?
Regards,
Vincent.

Gopesh
The alerts are displayed to the recipient in one of the following programs:
.In the Universal Work List (UWL of the Enterprise Portal) as of SAP NetWeaver 04
· In an application that accesses the alerts using an API
· In the Alert Inbox. The Alert Inbox is an application based on Business Server Pages (BSP),which can be called using the transaction ALRTINBOX or the corresponding URL
(http:///sap/bc/bsp/sap/alertinbox).
There are also a number of external communication methods available. You can configure these in SAPconnect (transaction SCOT) and use them in addition to inform the recipient of an alert about the problem: Internet mail, SMS, and fax.
Just to cross check have you configured your alerts using the below urls:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/aeeda66b-0a01-0010-6884-876fac1c4a2d
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/be79a16b-0a01-0010-51b8-9b6d1968338d
Regards,
---Satish

BPM Alerts not sending email notifications

Hello Experts,
I've successfully configured BPM within SolMan and alerts are being generated but I'm not receiving any email notifications. In the setup of Business Process Monitoring, "Contacts" have been maintained within the Solution Directory as well as the notifications section of the monitoring type with a sender and a valid recipient address . Both yellow and red alerts are being generated but no email notifications are being sent. Thresholds have also been maintained.
Researching other threads regarding this same issue points to tcode RZ20->SAP CCMS Technical Expert Monitors ->All Monitoring Contexts->BPM->Activate Maintanance Function-> and assiging Central auto reaction methods to MTE Class BPMRoot Context and the other BPM_APPMON_* MTE classes. Is there something that I am missing in order to have these alerts send email notifications when the alert threshold is reached?
I also defined the new Central Auto Reaction method and maintained the parameters properly which calls FM DSWP_BPM_SEND_ALERT. Please assist as I have exhausted all options. Please provide a step by step guide to setup alert notifications if possible.
Thanks
Mike

These notes might help you
[https://websmp130.sap-ag.de/sap%28bD1lbiZjPTAwMQ==%29/bc/bsp/spn/sapnotes/index2.htm?numm=543414]
[https://websmp130.sap-ag.de/sap%28bD1lbiZjPTAwMQ==%29/bc/bsp/spn/sapnotes/index2.htm?numm=546981]
check the timezone settings also [https://websmp130.sap-ag.de/sap%28bD1lbiZjPTAwMQ==%29/bc/bsp/spn/sapnotes/index2.htm?numm=572608]
regards
Naveen

Problem acccessing alertinbox or alert-configuration in RWB

Hi forum,
I have a problem acccessing alertinbox or alert-configuration in RWB,
because, whenever i click the button "alertinbox" or "alert-configuration"
it gives an BSP error page:
<b>Business Server Page (BSP) error
Calling the BSP page was terminated due to an error.
The following error text was processed in the system:
BSP Exception: the Application Name sap in URL /sap/bc/bsp/sap/alertinbox/index.htm?sap-client=400&sap-sessioncmd=open is invalid.</b>
pls help,

Hi,
Once you restart your Java engine.
The way of doing this is go to transaction SMICM-->Administration>J2EE Instance (Local) -> Send Soft Shitdown--
> With Restart.
Reward with points if helpful
Regards
Sai Ganesh

Alert in BSPs

Similar Messages

Maybe you are looking for