SAP ABAP IMG Activity CO_VC_SCENARIO (Define Scenarios)
Hierarchy
SAP_FIN (Software Component) SAP_FIN
   CO (Application Component) Controlling
     QISR (Package) Internal Service Requests
IMG Activity
ID CO_VC_SCENARIO Define Scenarios  
Transaction Code S_ALR_87100737   (empty) 
Created on 19991124    
Customizing Attributes ACC_CO_N_U_A_AT   Create Internal Service Request 
Customizing Activity CO_ISR_OB   Create Internal Service Request 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name CO_ISR_CREATE_DC    

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

By defining a scenario, you standardize how each service request is requested and executed.

Example

Suppose you want to define a scenario for the internal service request office move.

You now specify all parameters that:

  • Characterize the scenario
  • Are the same for all applicants in this scenario

You enter a contact person for the scenario in the basic data.

You decide on the entry type for the request.

Since an office move involves costs, you specify the means by which the service is to be allocated. If necessary, you use a template to define the allocation.

In the characteristics, you specify which fields are to be called in the internal service request form.

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

Requirements

You need notification types to be able to define scenarios. In the notification type, you have specified whether the service request requires approval and if so, by whom. A large number of notification types are provided. To be able to use them, you need to transfer the settings from client 000 using transaction QISR_SM29. 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 procedure applies to catalogs.
Note that you can use a given notification type for more than one scenario.

Standard settings

All scenarios provided by SAP are in namespace S.

Activities

  1. Choose New entries.
  2. Enter a technical name and also the application to which the scenario is to relate.

    The following applications are available:

    • Standard Application (no value in Application field) - Application for standard scenarios for the Internal Service Request
    • HCM Processes and Forms (value H in Application field) - You can link a scenario with this application to a form scenario in HR Administrative Services. For additional information, in Customizing choose Personnel Management -> HR Administrative Services -> Configuration of Forms/Processes -> Configuration of Forms.
    • Simplified Interactive Forms (value S in Application field) - Application for simplified forms that can be integrated in Express Planning. For additional information, see the SAP Library under Cross-Application Components -> Express Planning -> Planning Services -> Planning Services with Close Linkage-> Adobe Form Service.
  3. Choose Version and create a new version of the scenario using New Entries.

    The first version of a scenario has version number 0 (zero). The version number is automatically assigned sequentially when you create a new version.

  4. Specify a validity period for the scenario version.

    New requests can only be entered within the validity period. You can continue to process requests after the validity period expires. To enable the version to be used without time restrictions, set the active indicator and do not specify a validity period. The validity periods of different versions must not overlap.

  5. 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.

  6. Under Action Box, enter information on the subsequent activities of the processor.
    You can specify one of the following generic function modules and program the subsequent activity with the BAdI

Execution of a Function in the Action Box (QISR4).

  • ISR_ACTIVITY_EXECUTE_TASKDOC
  • ISR_ACTIVITY_EXECUTE_ACTIONDOC
  • ISR_ACTIVITY_EXECUTE

  1. Under Automatic Update you specify whether the applicant and approver are allowed to execute individual activities for automatic update.

    The activity is executed when you send the form. Only those activities are offered for automatic update that are not a follow-up activity or dependent activity, meaning that do not require a preceding activity. The automatic activity must be run through in the back end without interaction, that is, without output or display on screens. The activity must not, or example, branch to the transaction for displaying or changing an object, but the call should be implemented using BAdI QISR4 (Method EXECUTE_FUNCTION), for example using BAPIs or SELECTs.

  2. Specify how the internal request should be created.
    You can choose between:
    • Text entry only
    • Entry using notification transaction
    • Entry using Adobe PDF (for detailed information, see step 9)
    • Entry using ITS service (for detailed information, see step 10)
    • Entry using BSP (if you select this type of entry, you must define a BSP application. An example application is ISR_DEMO1.)
    • Entry using JSP iView (the scenario is used as an iView in the Enterprise Portal. You can generate a JSP iView. To do this, choose Additional Data for Scenario. Enter an existing portal component or generate a component.)
  3. You only need to specify an Adobe PDF form if you selected the entry type Entry Using Adobe PDF.

You can generate a form. If you do not enter a name for the form, one will be created automatically when you generate the form. The name will be ISR_FORM_XXXX (XXXX = technical name of scenario). You can generate a form using a template. You can use either a standard SAP form or a form from another scenario.

During generation, the characteristics of the scenario are automatically transferred to the interface and the context of the form. You can switch to the Form Builder and change the layout. If you define new fields in the layout, you can transfer these automatically as characteristics to scenario Customizing when you exit the Form Builder. When you do this, the data binding of the new fields is also automatically stored in the layout.

For more information about the Form Builder, choose Help -> Application Help in the Form Builder.

For more information about the use of Adobe PDF forms in ISR scenarios, see the ISR cookbook on the SAP Service Marketplace under service.sap.com/isr.

You only need to specify an ITS service if you selected the entry type Entry Using ITS Service. You enter the request using an HTML form specially designed for the scenario. To do this, you need to assign an internet service to the scenario. This internet service must contain the HTML templates, ITS (Internet Transaction Server), and language-dependent resources required for the request. You also have a choice of business add-ins (BADIs) in which you can define specific requirements.
You can assign an Internet service to only one scenario. To create a new Internet service, choose Generate.
You have three options:

  1. Generate Internet Service Using Reference
    If you specify a scenario with an existing Internet service as a reference when you generate the Internet service, the system copies it to the new Internet service name.
    • Regenerate Internet Service (SAP Design)
      If you do not specify a scenario with an existing Internet service as a reference when you generate the Internet service, the system creates a copy of the default 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.
    • Regenerate Internet Service Plain HTML)
      The same conditions apply here as for generation in SAP Design.

      The last two ways of creating Internet service requests is only possible using Customizing for scenarios for 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.
  2. To modify forms, choose
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
VC_SCENARIO C - View cluster SM34  
History
Last changed by/on SAP  20000118 
SAP Release Created in