Setting Up Web Requests
Purpose
The following gives an overview of the steps necessary for setting up Web requests. Settings for a Web request are represented in a Request Category. All the required steps should be carried out in SAP CRM Customizing, under Customer Relationship Management ® E-Commerce ® E-Service ® Web Requests.
Prerequisites
It is advisable to make an exact plan for Web requests and the layout of these requests before the steps in the system are carried out. The following questions should be clarified:
· Which different Web requests do you want to provide?
· Should the Web requests be grouped?
You can limit the search for Web requests by using the request category group in the service order processing.
· Which fields should be included in a form and who can display these fields (person placing request and/or processor)?
You can create different request category views for each request category and define the selection of displayed fields for each view.
· Should an authorization concept be created?
You can define the authorization groups on the level of request category views.
For more detailed information on registering and deregistering for Web requests, see SAP Note 663615.
For more general information about logging on to BSP applications, see the SAP Library under mySAP Technology Components ® Business Server Pages ® User Concepts.
Process Flow
...
1. You can create a transaction type in the IMG activity Define Request Types and a request category in the IMG activity Define Request Categories. You can also use transaction types that have already been assigned to other request categories when defining request categories (assignment 1:n).
It is advisable to use the templates delivered by SAP when creating transaction types (see Templates for Web Requests):
Web request with item |
Transaction type SWRA Item category SWRP |
Web request without item |
Transaction type SWRB |
You can also define further optional settings in the basic data of the request category:
¡ the assignment of a request category group
¡ the definition of an activity reason if you want to use the function for partner determination and/or organization data determination
¡ the assignment of a product for billing-relevant service orders
2. You define all fields and their characteristics (attributes) that are relevant to the corresponding request form in the Request Data Structure. A special XML editor is available for defining the request data structure.
3. You can use the BAdI CRM_SERVICE_WEBREQ to implement customer-specific enhancements to:
¡ control the assignment of default field values or check entries
¡ influence the partner and organizational data determination by overwriting the activity reason
4. You define one or more request category views for each request category (see views and authorization concept).
...
5. You generate the BSP application for each request category view. Based on the request data structure created, each view receives its own start page and URL through which a BSP application can be called.
It is also possible to generate your own BSP application for each view by defining your own BSP application name for each view. However, it is not necessary to use several BSP applications for each request category.
6. You can maintain a detailed layout of the individual BSP pages to meet your requirements. For example, you can hide certain entry fields on the start page of the view of the person placing the request or adjust the request form for a user-defined look. You define these settings manually in the source text of the relevant BSP pages (see Layout Maintenance for Web Requests).
.
Result
You have generated a BSP application and your own start page for each page. You include the URL of the start page for the requester on your Web site for calling the Web request in the Web Application Server.
See also:
By default, SAP delivers the following sample request categories that give you an overview of functions. For more information, see SAP Demo Requests.