Hierarchy
SAP_FIN (Software Component) SAP_FIN⤷
CO (Application Component) Controlling⤷
QISR (Package) Internal Service Requests
IMG Activity
| ID | CO_ISR_QISRCONF | Define Scenario with ISR Wizard |
| Transaction Code | S_AC0_52000723 | (empty) |
| Created on | 20050311 | |
| Customizing Attributes | ACC_CO_N_U_A_AT | Create Internal Service Request |
| Customizing Activity | CO_ISR_QISRCONF | Define Scenario with Wizard |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | CO_ISR_QISRCONF |
Use
In this IMG activity, you can define an Internal Service Request (ISR) scenario using the ISR wizard step by step. The wizard settings are initially only temporarily saved, even if you complete a subwizard. Only when you activate the scenario are the settings defined in the corresponding Customizing tables as a usable scenario.
The ISR wizard is divided into several subwizards for different topic areas. The individual subwizards are in part dependent on each other. A dependent subwizard can only be called up providing all the other required wizards have been completed. Until all of the previously required subwizards have been processed, the dependent subwizard is indicated with a lock symbol.
You can choose from the following subwizards:
- Form Definition: you define the essential elements of the form (can be executed independently of the other subwizards)
- Partners Involved: you determine the partners involved in the business process for the service request, and assign users (is independent)
- Form Layout: you determine the rough layout of the form and generate a preliminary version (is dependent on wizard 1).
- Worklist: you determine how the partners involved find their service request (is dependent on wizard 2)
- Notification Processing: you determine the transaction functions for processing the service request in the back end.
- Log Notification Actions (Optional): you specify how and whether activities for notification processing in the notification are documented (is dependent on wizard 2 and wizard 5)
- Service Costs (Optional): you can monitor the costs of a service request (is independent)
If a subwizard has not yet been processed, it has the status Open . If a subwizard has been partly processed but not yet completed, it has the status In Process. Once is it completed, it receives the status Processed. Once all subwizards that are not optional have been completely processed, you are able to activate the scenario.
Following activation, you are no longer able to process the scenario in the wizard, but only in the actual IMG activities for the ISR. Which wizard steps correspond to which IMG activities is described in the Task List, that the system creates for every scenario created and activated in the wizard. This list also contains a description of the steps that you have to carry out manually after the activation of the scenario.
You can find an overview of all ISR scenarios created in the wizard in the IMG activity Overview of the Scenarios Created in the ISR Wizard or by choosing Overview.
Requirements
Standard settings
Activities
- Create the scenario in the wizard.
- Process all of the subwizards until the whole scenario has the status Processed.
- Activate the scenario.
- Execute the additional activities, and also any changes required in the IMG activities that are described in the task list.
Example
Business Attributes
| ASAP Roadmap ID | 259 | Establish Forms and Messages |
| Mandatory / Optional | 3 | Nonrequired activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| IMGDUMMY | D - Dummy object | QISRCONF |
History
| Last changed by/on | SAP | 20050517 |
| SAP Release Created in | 600 |
