Show TOC

Define Scenarios

In this IMG activity, you define scenarios for internal service requests.

By defining a scenario, you standardize the request and execution of each service request.

Example

You want to define a scenario for the internal service request to move offices.

You can now specify all details that

Store a contact person for the office move scenario in the basic data.

You decide on the entry type for the request.

As an office move is a cost relevant service, store the means by which the service is to be allocated. If necessary, use a template to define the allocation.

In the characteristics, store the fields in the form for the internal service request are to be called up.

In the tasks specify how the internal service request is to be processed.

Requirements

You need notification types for defining scenarios. In the notification type, you specified whether the service request needs to be approved, and if so, who by. The SAP System provides numerous notification types - to use these, you need to transfer the settings from client 000, using the QISR_SM29 transaction. Then you need to process the number ranges for notification types . If the notification types in client 000 are not sufficient, you can create your own . The same applies to catalogs.
Note that you can use a notification type for more than one scenario.

Standard Settings

All scenarios provided by SAP are in the S namespace.

Activities

1. Choose New entries.
2. In the general data, make the required entries.
Take this opportunity to store a long text for the scenario. This description is displayed as an explanation when you call up the form. You can also use this description to find a corresponding form in the intranet. When you enter the text, you do not have to enter key words as the search engine filters the text using not only the words, but also their conjugation or declination. Word groups are also used for the search.
For more information on the search engine, see the SAP Library under Financials -> Controlling -> Cost Center Accounting -> Information System -> Interactive Information System, and then see Report Documentation under Document Search Using The Retrieval System.
3. In the details on the form, choose how the internal request can be requested.
You can choose from the following:
4. You only need to specify an ITS service if you selected the Entry with form entry type. You enter the request using a an HTML form designed especially for the scenario. You also need to assign an internet service to the scenario, which contains the HTML templates, ITS (Internet transaction server) and language-dependent resources required for the request. You also have a choice of buisness add-ins (BADIs), in which you can define specific requests.
You can assign an Internet service to a maximum of one scenario.
There are two options for this:
This type of Internet service creation is only possible using Customizing for scenarios in internal service requests.
Note
Before you can test the Internet service, you need to publish it manually. This takes you automatically to the Internet service processing in the development workbench, where you can publish the entire Internet service. Then you can test the ITS service from Customizing using Test.
5. To modify forms, choose Business Add-Ins. You can now change the implementation (create, change, delete and so on).
If you require special initialization or checks on the request for the scenario, you can use a business add-in (BADI QISR1). For more information on BADIs, see Basis -> Change and Transport System - Overview -> Transactions and Tools -> BC Changes to SAP Standards -> Business Add-Ins.
6. Decide whether running this scenario incurs costs.
If you activate the Cost incurring indicator, you can either specify estimated costs , or a template, which determines the values for the cost allocation from the details in the form. If you have not prepared a template, choose Create template.
You then also need to specify a costing variant and a fixed account assignment object .
If you decide to use a template for the costing, use Easy Cost Planning.
For more information on Easy Cost Planning see the SAP Library under Financials-> Controlling -> Product Cost Controlling -> Product Cost Planning -> Easy Cost Planning and Execution Services.
7. In the selection area, choose Characteristics, specify the fields that you want to have in the form for the scenario.
You can choose between:
Characteristic with up to 250 characters
Existing characteristic from the dictionary
For data elements, the system transfers the system category and characteristic description from the dictionary. For structures, it uses all data elements within the structure.
Note
The following restrictions apply to the definition of the scenario characteristics:
8. Choose Tasks from the selection area. Use the workflow or worklists in the SAP System to specify the processing of the internal service request.
9. Give each task in the processing a description.
10. If you want to use tasks for evaluation, store a key. An action is always filled by choosing a key.
11.
12. To determine the correct processor of the task, store a standard role.
In the PFAC transaction you can define your own standard roles. In the container, you store the characteristic names, or a field name from one of the following tables:
The characteristics or fields stored there mean that in the form you can determine the correct processor using the standard role. If you make an entry in one of the fields (in the form) that was stored in the container, then the correct processors are determined during runtime.
If you want the system to use your user-defined fields (that are not in the table mentioned above) for determination of standard roles, then use business add-in QISR3.
For more information on roles, see the SAP Library under Basis -> Business Management -> Organization Management -> Integration with The Business Workflow -> Role Resolution -> Role Definition -> Define Roles for Responsibilities.
For more information on business add-ins see the SAP Library under Cross-Application Components -> Internal Service Request -> Preparation of The Internal Service Request -> Definition of a Scenario -> Business Add-Ins.
1. For a cost-incurring scenario, you can store a subtemplate. This enables a structure in your own template for more than one task. This structure enables you to assign items correctly using the subtemplate.