SAP ABAP IMG Activity SIMG_CMS_COB_ACT (Define Activities)
Hierarchy
☛ EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services
   ⤷ FS-CMS-MD (Application Component) Master Data
     ⤷ CMS_OMS_COMMON (Package) Collateral Management: Common Services for Object Systems
IMG Activity
ID SIMG_CMS_COB_ACT Define Activities  
Transaction Code S_PLN_62000726   (empty) 
Created on 20040510    
Customizing Attributes SIMG_CMS_OMS_ACT   Define Activities 
Customizing Activity SIMG_CMS_COB_ACT   Define Activities 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CMS_COB_ACT    

Use

In this IMG activity, you define the steps that you execute in business processes to control the behavior of a collateral object. Therefore, each activity that you define must be assigned to a control area and control key. Within an organization, the control area and control key determine the range of an activity. For each activity, you maintain the following:

  1. A plausibility check set to determine the possible business checks that must be performed for an activity.
  2. An activity category to determine the internal behavior of activities. The standard system provides activity categories that you can choose from. These are listed further on in this document.
  3. User interface (UI) features that determine how the screen will be presented for the activity. These include
    • Object screen - To determine the status of the fields on the screen. For example, for a specific activity, a field may be mandatory for input, or hidden for display.
    • UI activity - To determine the corresponding user interface activity for each activity.
    • Activity group - To specify if the activity is part of an activity group. This assignment determines the activities in the activity group, that must be executed in a sequence. For example, for an activity group Change, you can define the activities before release, in release and after release.
    • Sequence number if an activity is part of an activity group. This number will determine the position of an activity in the activity group. For example, for an activity group such as Legally Active defined for an agreement type, you can define the sequence in which activities appear, namely, Set legally active, Set Inactive and Reset Inactive.
  4. User status transition - Values that determine whether activity control is possible for the user status and The possible result of the activity. You can choose from three possibilities that may lead to a status transition:
    • Set - User status can be set for the object on completion of the business activity.
    • Delete - User status is deleted on completion of the business activity.
    • No influence - Use status is not changed on completion of the business activity.
  5. System status transition - The standard system allows you to define status transition for the system statuses namely, Legally active and Calculation relevant. You can determine:
    • If the business activity is allowed to control the system status transition.
    • If allowed, then should the specified system status be confirmed, deleted or have no influence on the status of the collateral agreement.

You can set the system status to:

  • Legally active : For all collateral objects, on which the business activities of activity category Release or On Release of change request are performed.
  • Calculation relevant : If you must consider the collateral objects for calculations purposes. If this status is not set, then the collateral objects will not be considered for calculation purposes.

  1. Message Severity - Each activity inherits messages of the plausibility checks of the check set assigned to it. You can choose to specify message type for the messages

    Note: If you do not specify a message type, the default message type assigned in the Customizing of plausibility checks will be used.

    The standard system provides the following message types:

    • Abort
    • Warning
    • Error
    • Success
    • Information
  2. GUI function codes - Screen elements such as the buttons that must be excluded from the screens of the activity.
  3. Flags to specify usage of the activity:
    • Default activity - To determine that this activity that is triggered each time the user selects a collateral object of the specified type in the hit list of the CMS workbench.
    • Change during release - To specify that the activity must be initiated in Change mode during release process
    • Display during release - To specify that the activity must be initiated in Display mode during release process
    • Create -To specify that this activity is to be used to create an object.

Requirements

In the relevant Implementation Guide (IMG) activities, you must define the Customizing entries that you require for assigning activities. These include activity groups, plausibility checks, plausibility check sets and object screens.

Standard settings

The standard system provides predefined settings for the following activity categories. You can change these default settings to suit your requirements.

  • Create
  • Change
  • Display
  • Release
  • Change after release
  • Set legally active
  • On release of change request
  • Reset inactive
  • Reject
  • Return
  • Set inactive
  • Send for release

Activities

Determine the various activities according to your business requirements. You must ensure that these activities belong to one of the activity categories provided by SAP.

Example

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 1   Mandatory activity 
Critical / Non-Critical 1   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_CMS_PCN_ACTVT_OMS C - View cluster SM34  
History
Last changed by/on SAP  20040510 
SAP Release Created in 500