Views and Authorization Concept 

Use

This function is used to support different request category views reconciled for requesters and processors for Web requests (or reconciled for freely-definable applications). It can be used to define a selection of fields in the request data structure for each view.

Each view contains its own start page with the corresponding URL when the BSP Application is generated. You can define an authorization concept at request category view level.

Features

·        Defining the validity interval:

You define a validity interval for each request category view. By doing this, request forms receive a validity period and can therefore be changed, for example, due to legal changes or for data protection through selection.

If a change is made (for example, the request data structure is enhanced), define a selection for the old view using the validity interval of the new view. You must also generate the corresponding BSP pages for the new view. The layout elements of the old BSP pages can be used again for the newly generated BSP pages.

·        Role-specific Usages:

You define a role-specific usage for each request category. If the forms of a Web request for a person placing a request and a processor are the same, you could create just one view and choose the usage Person Placing Request and Processor.

The following usages are delivered with the standard delivery:

¡        Requester

¡        Processor

¡        Person placing request and Processor

¡        Processor for Requester

¡        Interaction Center

If the request exists for more views (for example, for multi-level processing), you can define customer-specific usages. For more information, see the implementation guide under Customer Relationship Management ® E-Service ® Web Requests ® Define Usages of Request Categories Views.

·        You can define whether the digital signature should be supported for each request category or not.

·        Setting up the authorization concept:

You can assign an authorization group for each request category and thereby prepare an authorization concept. The authorization group is part of authorization object CRM_VIEW (CRM Order – view of a request category).

You define the authorization groups for Web requests in the Customizing of CRM, under Customer Relationship Management ® E-Service ® Web Requests ® Create Authorization Groups for Request Category Views.

If you want to support multi-level processing with differentiated authorizations, you can do this using several self-defined processor usages and the corresponding authorizations for the different processor views.

Activities

...

       1.      You define the relevant views of a request category in the Customizing of CRM, under Customer Relationship Management ® E-Service ® Web Requests ® Define Request Categories.

       2.      You define an authorization group for each request category view.

       3.      You generate the BSP application for each request category view.

SAP recommends that you always use the same BSP application for all views of a request category. You do this by defining your own BSP start page for each view and always entering the same BSP application.

Result

The following BSP pages of the BSP application are created in addition to the URL of the request category view when a request category view is generated.

Overview of the BSP pages of a Web request

Start page	The ready-for-input page (request) of a Web request for each view.
Signature page (optional)	Only for Web requests for which the digital signature was selected.
Confirmation page	System feedback – for example, the service order number is displayed under which a Web request is created in SAP CRM.
start_exit page	Supports the controlled Start/Exit of the BSP application session of a Web request.