SAP ABAP IMG Activity COOMCCA_VC_SCENARIO (Define Own Scenarios for Request to Change Master Data)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ KS0C (Package) Customizing R/3 Cost Accounting
IMG Activity
ID COOMCCA_VC_SCENARIO Define Own Scenarios for Request to Change Master Data  
Transaction Code S_ALR_87100748   (empty) 
Created on 19991126    
Customizing Attributes AC_COOMCCA_N_U_A_AT   Define Scenario for Changing Cost Center Master Data 
Customizing Activity COOMCCA_CHANGEREQ_OB   Define Scenario for the Request of a Change to Cost Center Master Data 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name COOMCCA_CCREQUEST_DC    

In this IMG activity, you define scenarios for the request to change master data.

Standard settings

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

For requests to change master data, the following notification types are provided in client 000:

  • Notification type 50 for requests for cost centers, orders, and G/L accounts.
  • Notification type 70 for requests for vendors and customers.

    Note

    To be able to use these notification types, you need to transfer the settings from client 000 using the QISR_SM29 transaction. Then you need to process number ranges for the notification types.

    The notification type contains information on whether the request must be approved, and if so, by whom. Note that you can use a notification type for more than one scenario.

Requirements

SAP recommends that you use the scenarios provided for master data changes as a reference for creating your own scenarios, and then to adapt the copy as required.

Activities

  1. To copy a scenario, select is and choose Copy.

    To create a scenario, choose New entries.

  2. Enter a key and a description for the scenario.

    Caution

    The scenario key must not be in the SAP (S*) namespace.

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

  4. Transfer the scenarios from notification type 50 or 70 accordingly.

    Note that you initially need to transfer the settings for the notification types from client 000 using the QISR_SM29 transaction. Then you need to process the number ranges for the notification types.

    Note

    Check whether the follow-up activities provided on the activities menu bar match your requirements. We recommend that you use the follow-up activities supplied by SAP.

  5. Use Entry with form as the entry type.
  6. You only need to specify an ITS service if you choose the Entry with form entry type. You use an HTML form specially designed for the scenario. You also need to assign an Internet service to the scenario that contains the required HTML templates, ITS (Internet transaction server) and language-dependent resources. In addition, there is a choice of business add-ins (BADIs) that you can use, in which you can define specific requests.

    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
      When you generate the Internet service, if you specify a scenario with an existing Internet service as a reference, the system copies it to the new Internet service name.
    • Generate internet service without reference
      If you do not specify a scenario with an existing Internet service as a reference, the system copies the default Internet service SR00. An internet service created in this way contains all settings required for immediate testing of the scenario definition. The system automatically inserts a request data area with corresponding entry fields, for the request-specific characteristics that were defined in the scenario.

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.

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

    Caution

    SAP recommends that you use the F4 Help to transfer the corresponding Business Add-In from the scenario for requests to change master data. In this case, the existing interfaces to the SAP system are used automatically.
    Each Business Add-In provided ensures that all of the fields defined in the SAP system (which you use on your request form) are integrated with the SAP system, for example, for the purpose of consistency checks. You can also copy and enhance the Business Add-In if necessary.

  2. Do activate the Cost incurring indicator.

    The scenarios for changing master data do not incur costs.

  3. Choose Transfer.

    In the next dialog box, choose Copy all. The selection list now provides the scenario that you copied.

  4. Flag your scenario and choose Characteristics in the selection area.
  5. Enter the fields that you require for the request form.

    Next, select Dictionary category and transfer the structure for each request. All the fields are contained here that you can use for the form. You can carry out a search via structure name ISR*.

    In the basic data you use ITS to determine which fields appear on the form, and in which order they should appear. You use a Business Add-In to control which fields are filled as default.

  6. Choose Tasks in the selection area.

    You specify the processing procedure in the SAP System for the request to change master data by using the workflow or worklists.

  7. Transfer a task for each scenario.
  8. Enter a processor or a standard role.

    This data is automatically provided when you call up the request form.

    SAP provides you with standard roles for the various requests to change master data. It is recommended that you copy these and adapt the copy accordingly.

  9. Note
    You can use the partner role to control whether a single processor (task processor) is defaulted in the request form, or a whole department (department responsible). For more information on the role, see the SAP Library under Basis -> Business Management -> Organizational Management -> Integration Into The Workflow -> Role Breakdown -> Role Definition -> Define Responsiblity Roles.

    Example
    SAP provides the standard role 3100014 for requests to change cost center master data.

Further notes

More information on master data adjustment requests is available in the SAP Library under Financials -> CO Controlling -> Cost Center Accounting -> Master Data in Cost Center Accounting -> Processing Master Data -> Master Data Adjustment Requests viaInternet/Intranet.

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  20000125 
SAP Release Created in 46C