SAP ABAP IMG Activity DR_SCMGVC_STATPROF (Create Status Profile)
Hierarchy
FINBASIS (Software Component) Fin. Basis
   FIN-FSCM-DR (Application Component) Internal Collection Procedure
     UHC_COLL_CASE (Package) Collection Case
IMG Activity
ID DR_SCMGVC_STATPROF Create Status Profile  
Transaction Code S_SE3_50000163   (empty) 
Created on 20040123    
Customizing Attributes DR_SCMGVC_STATPROF   Create Status Profile 
Customizing Activity DR_SCMGVC_STATPROF   Create Status Profile 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name DR_SCMGVC_STATPROF    

Initial remark for SAP Debt Recovery Management for Public Sector

The standard delivery already contains status profile FCL_COLL that you can either use as it is or as a template for your own status profile.

As the integration with Contract Accounts Receivable and Payable does not support the use of process routes, you do not need to enter values in the Event column.

Use

In this IMG activity you can create a status profile. A status profile contains multiple status values that can be assigned to a case. Status is an attribute that the user can set for each case.

Requirements

Standard settings

Activities

The meanings of the columns of the status profile are as follows:

  • Status profile: Technical name of the status profile. You assign the status profile to a case type in the activity Define Case Types.
  • Status profile description: Description of the status profile.
  • You fill the columns "Status OT" (object type) and "Status Schema" only if you want to connect the central status management. In this case, you do not need to maintain status values for your status profile.
  • If you want to connect the central status management, you have to implement additional BAdIs:
    • Provided that the central status management has been set up, one BAdI (SCMG_SET_STATUS_S) has to be implemented for the initial status and one BAdI (SCMG_INIT_STATUS_S) for the status change. You can then use the central status management in Case Management. (You implement BAdIs by using transaction SE19, and view BAdI definitions in transaction SE18).
      You change the status by means of pushbuttons. On the front end, there is a BAdI available for including additional pushbuttons. The function code contains the business transaction according to the central status management. You change the status by using the function module of the central status management CRM_STATUS_CHANGE_FOR_ACTIVITY.

For each status profile you can define multiple status values. A case can have one current status only. (Multiple statuses cannot be active simultaneously.) The meanings of the columns of the status values are as follows:

  • Status: Number of the status, which you choose. The status with the lowest number is the initial status.
  • Status description: Description of the status, which you choose.
  • System status: SAP delivers system status values. You can use the input help to see which values are available. By entering a system status, you assign a particular system response to the status that you created. Some examples of system status values and their system response are as follows:
    • 003 (External Processing): The case is no longer ready for input. The user can change the status only by means of a pushbutton. Responsibility for the pushbuttons lies with the applications (Public Sector, FIN, CRM, and so on).
    • 007 (Completed): The case is no longer ready for input. The user can, however, convert the status. The status can be changed by means of a pushbutton only. Responsibility for the pushbuttons lies with the applications (Public Sector, FIN, CRM, and so on).
    • 008 (Confirmed): The case is no longer ready for input. The status can no longer be changed.
    • 009 (Canceled): The case is no longer ready for input. The status can no longer be changed.
  • System Status Description: Filled by the system automatically.
  • Low Status: Lowest previous status. The user can set the status only if the previous status is higher than or equal to the status that is entered here.
  • High Status: Highest previous status. The user can set the status only if the previous status is lower than or equal to the status that is entered here.
  • Auto: The user cannot convert the status manually (filled by the system automatically depending on the system status).
  • Event: Only relevant if you use the process route. The event is triggered when the status is set. The following events are available:
    • COMPLETED: The process route is completed.
    • CREATED
    • INPROGRESS: The process route is triggered.

Example

Status Schema:

Status     Description     System Status    Lowest Status    Highest Status

10    In Preparation    New/Open    0    10

20    New    New/Open    0    20

30    In Processing    In Process    0    40

35    In Legal Department    For Release    20    37

37    Cleared by Legal Department    Released    35    37

40    Processing Completed    Completed     30    40

50     Completed    Confirmed    40    40

Interpretation of the Status Schema:

The status controls the status transfers. A status can be set if the status of the current status is higher than or equal to the lowest status number and lower than or equal to the highest status number.

Example 1: The status "Cleared by Legal Department" can be set only if the lowest status is 35 ("In Legal Department") and the highest status is "Cleared by Legal Department". This means that the status "Cleared by Legal Department" can be set only if the current status is "In Legal Department".

Example 2: The current status is 30 ("In Processing"). Possible next statuses are all statuses to which the following applies: Lowest status < = current status < = highest status.
Valid next statuses in this example are "In Legal Department" and "Processing Completed".

Use

Requirements

Standard settings

Activities

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 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG DR_SCMGVC_STATPROF 0 SE31000081 Internal Collection Procedure 
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
SCMGVC_STATPROF C - View cluster SM34  
History
Last changed by/on SAP  20040123 
SAP Release Created in 300