SAP ABAP IMG Activity COOMCCAP_VC_SCENARIO (Define Scenarios for Request for Adjustment Posting)
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 COOMCCAP_VC_SCENARIO Define Scenarios for Request for Adjustment Posting  
Transaction Code S_ALR_87100779   (empty) 
Created on 19991130    
Customizing Attributes AC_COOMCCAP_N_U_A_AT   Define Scenario for Adjustment Postings 
Customizing Activity COOMCCAP_VC_SCENARIO   Define Scenario for Request of an Adjustment Posting 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name COOMCCA_PCREQUEST_DC    

In this IMG activity, you define scenarios for the request for an adjustment posting.

Standard settings

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

SAP provides notication type 60 in client 000.

Note
To be able to use this notification type, you need to transfer the settings from client 000 using the QISR_SM29 transaction. Then you need to process the number ranges for the notification types.
The notification type contains the 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 copy the scenarios for master data changes as a reference for your own scenarios, and then to adapt the copy accordingly.

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 notification type 60 according to the scenario.

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

  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.
  7. 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 (SR31) for requests to make an adjustment posting. In this case, the existing interfaces to the SAP system are used automatically.
    If you want to use the fields provided in the SR31 scenario for your request form, the SR31 Business Add-In ensures that the corresponding values are transferred from the SAP system for these fields. You can copy and extend the Business Add-In if required.

  8. Do not activate the Cost incurring indicator.

    The scenario for an adjustment posting does not cause any costs.

  9. Choose Transfer.

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

  10. Select your scenario and choose the Characteristics selection area.

    You select fields in characteristics that are to be provided in the request form.

    Recommendation

    Accept the structures suggested for the adjustment posting request. Fields are contained within the structures that you can use for the form. You can add further characteristics via New entries.

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

  11. In the selection area choose Tasks.

    Using the workflow or worklists, specify the processing procedure for the adjustment posting request in the SAP System.

  12. Give each task in the processing procedure a description.
  13. If you want to use tasks for evaulation, store a key.

    Follow-up actions are filled automatically according to the choice of key. A follow-up action is carried out automatically when the form is sent. Thus, with the adjustment posting request, update occurs in the footer between the incorrect document for which the correction was requested and the message generated when the form was sent.

  14. Enter a processor or a standard role.

    The system automatically provides this information when you call up the request form.

    SAP supplies the standard role 20000102 for the adjustment posting request. It is recommended that you copy this, and adapt the copy accordingly.

    Note
    The partner role is used to control whether an individual processor (task processor) or an entire department is put forward in the request form (responsible department). You can find more information on roles in the SAP Library under Basis Components -> Business Management -> Organizational Management -> Integration with SAP Business Workflow -> Role Resolution -> Role Definition -> Define Roles using Responsibilities.

Further notes

For more information on adjustment posting requests, see the SAP Library, for example, under Financials -> CO Controlling -> Cost Center Accounting -> Manual Actual Postings -> Request for Adjustment Posting in the Internet.

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 QISR_PCR60  
History
Last changed by/on SAP  20000127 
SAP Release Created in 46C