Define Scenario (SAP Library - Internal Service Requests)

Define Scenario

Use

You standardize the application and execution of a service request when you define its scenario.

Course Prerequisites

You need to create notification types first. In the notification type, you have specified whether the service request requires approval, and if so, who is to approve it. Note that you can use a notification type for more than one scenario.

Check whether all notification types from client 000 are in client 003. If you need notification types that are missing, import them using the QISR_SM29 transaction from client 000. If these are not sufficient, then you can create your own notification types. The same procedure applies to catalogs.

For more information, see Customizing under Cross-Application Components ® Internet / Intranet Services ® Scenario Definition ® Prepare General Notification ® Notification Creation ® Notification Type.

Procedure

Note

All of the scenarios provided by SAP are in the S.namespace.

In Customizing, choose Cross-Application Components ® Internet-/Intranet Services ® Internal Service request ® Scenario Definition ® Define Scenarios.

Choose New entries.

In the general data, enter the data required.

Use this opportunity to store a long text for the scenario. The system displays this description as an explanation when you call up the request form. You can also use this description to find a suitable request form in the intranet. You do not need to restrict your text to key words when you enter it. The search engine does not just filter the text using the words, but also includes their grammar, and uses word families for the search.
For more information on the search machine, see the SAP Library under Financials ® Controlling ® Cost Center Accounting ® Information System ® Interactive Information System, then in Report Documentation, search under the Document Search Using The Retrieval System.

In the details for the form, decide how the internal request can be entered.
You can choose between:

Text entry alone

Entry with form
Entry with notification transaction.

If you chose Entry with form, then the following procedures apply.

You only need to specify an ITS service if you selected the Entry with form entry type. You use an HTML form especially designed for the request scenario to enter the request. To do this, you need to assign an internet service to the scenario. This internet service must contain the HTML templates and language-dependent resources that are required for the request. There is also a choice of business add-ins (BADIs) available, in which you can define specific requirements.
You can assign an Internet service to maximum one scenario.

To create a new Internet service, choose Generate.
You have two options:

Generate Internet Service With Reference
If you specify a scenario with an existing Internet service as a reference when you generate the Internet service, then this is copied to the new Internet service name.

Generate New Internet Service (SAPDesign)
If you do not specify a scenario with an existing Internet service as a reference when you generate the Internet service, then the system copies the standard Internet service SR00. An Internet service generated in this way contains all the settings required for immediate testing of the scenario definition. The system automatically inserts a Request data area (with the corresponding entry fields) for the request-specific characteristics defined in the scenario.

Generate New Internet Service (Plain HTML)
The same conditions apply as for generation using SAPDesign.

Caution

This type of Internet service creation is only possible using Customizing for scenarios for internal service requests.

You need to manually publish the Internet service before you can test it.
After generation, the processing screen for the Internet service in the Development Workbench automatically appears, where you can publish the entire Internet service. Next you can test the ITS service when in Customizing, by choosing Test.

To add processing logic to forms, choose Business Add-In.
If you need special initializations or checks for the request, you can use a business add-in (BADI QISR1). For more information on BADIs, see the SAP Library, under Basis ® Change and Transport System - Overview ® Transactions and Tools ® BC Changes to SAP Standards ® Business-Add-In.
As a standard measure, each scenario has its own BADI implementation (from the QISR1 BADI definition) assigned to it. However, you can use a BADI implementation for more than one scenario if required.

Assigning a BADI implementation to more than one scenario
Referencing a scenario to the BADI of another scenario
This is particularly recommended, as you do not need to modify any existing BADI implementation.

To change the action box that appears in request processing, choose Activity box.
All follow-up activities that were defined for the notification type appear. You can now add follow-up activities that are scenario-specific, or delete ones already defaulted for this scenario.
For more information on the action box, see Action Box.

Decide whether executing this scenario incurs costs.
If you activate the Cost incurring indicator, you can either specify estimated costs, or store a template with costing variant and strategy, which determines values for the cost allocation using the details in the form.
For more information on the template, see Create Template.

If you have not yet prepared a template, choose Create template.
If you decide to use the costing with template, you can use the Easy Cost Planning functions.
For more information, see the SAP Library under Financials ® Controlling ® Product Cost Controlling ® Processing Costing Variants And Assigning Attributes.

Choose Characteristics from the selection area.

Now enter the fields that you want to have in the form for the scenario.
You can choose between:

Uncategorized characteristics
Characteristic with up to 250 characters
Dictionary Type Characteristics
Characteristic from the dictionary

For data elements, the system transfers the category and description of the characteristic from the dictionary. For structures, the system takes all the data elements from the structure.
The characteristic category is automatically included in the form.

Caution

The following restrictions apply to the definition of scenario characteristics:

Characteristic names or structure names must be unique within a scenario.
Characteristic names or structure names may not begin with ISR_
Characteristic names or structure names should not be named as HTML business indicators, for example LABEL, NAME, VALUE, DIM, MAXSIZE, TYPE, EXISTS, ENABLED or VISSIZE.
The length of the characteristic names or structure names should have a maximum of 28 characters.
The data length of the characteristic or structure fields is restricted to 250 characters.

Choose Tasks from the selection area.
Use the workflow or worklists in the SAP System to specify the processing of the internal service request.
For more information on tasks, see: Tasks.

Give each task in the processing a description.

If you want to evaluate tasks, store a key.
Follow-up activities are automatically filled if you choose a key. A follow-up activity is an action that is automatically executed when the task is processed.

You can store a subtemplate for a cost-incurring scenario
For several tasks, a subtemplate enables you to group and assign the rules for the template to the task. You can assign items correctly using the subtemplate during Easy Execution.

To find the correct processor for the task, you can store a standard role. You can define some standard roles in the transaction PFAC.
In the container, you store characteristic names or field names from one of the following tables:

TQ80

VIQMEL

VIQMSM

The stored fields enable the correct processor to be found, using the standard role. If one of the fields stored in the container is filled in the form, then the correct processor is found during runtime.
If you want your user-defined fields (not in the tables named above) to be used for standard role determination, use the business add-in QISR3.
For more information on roles, see the SAP Library under Basis Components ® Business Management ® Organizational Management ® Integration With SAP Business Workflow ® Role Resolution ® Role Definition ® Define Roles Using Responsibilities.

See also:

Definition Of The Form