SAP ABAP IMG Activity RMS_VRA_40 (Set Up User Status Profile)
Hierarchy
☛ EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
   ⤷ PLM-RM (Application Component) Recipe Management
     ⤷ CPPERCP (Package) RMS-RCP: iPPE Objects for Appl. Type RCP (Recipe, Header)
IMG Activity
ID RMS_VRA_40 Set Up User Status Profile  
Transaction Code S_XBA_46000031   IMG Activity CPPERCP 
Created on 20001010    
Customizing Attributes RMS_VRA_40   Set Up User Status Profile 
Customizing Activity RMS_RCP_21   Set Up User Status Profile 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name RMS_VRA_40    

In this IMG activity, you define the user status profiles for the scope of application for formulas and recipes. In this way, you add your own status profile to the system statuses defined in the standard system to map your company-specific processes onto the SAP System. The following system statuses are used in the standard system:

The user statuses of the scope of application represent a closed chain. They are inserted at the corresponding positions in the status network by the system (see above).
You must activate a user status profile before it can take effect. You can activate one status profile for formulas and recipes respectively. This status profile then applies to all formulas or recipes in recipe management.

When defining your status profile, note the following:

  • Status number:
    Recipe management only supports user statuses with a status number.
    The first user status in the status network is the status with the lowest status number. You determine the status sequence within the user status profile by specifying the status number of the lowest and highest allowed subsequent status for each user status. The next system status cannot be set unless the user status with the highest status number has been reached.
  • Initial status:
    This setting is not taken into account for the scope of application (see status network).
  • Position / Priority:
    Only one status can be active for a scope of application at a time. For this reason, only one status position is displayed. Assign position 1 with priority 1 to all user statuses.
  • Authorization key:
    This setting is not taken into account. For the scope of application, you do not assign the authorization to change statuses through the authorization object of the user status but through the authorization object EH&S: Scope of application instead.
  • Business transaction control:
    The scope of application does not support setting or deleting user statuses through business transactions.

Example

In the scope of application for your recipes, you specify for which plants the recipes are valid. You want production and quality assurance of the relevant plant and finally the head of quality control to check the recipes before they are released.
For this reason, you define and activate a user status profile with the following settings:

Status         Status no.     Lowest status no.    Highest status no.

CheckProd         1     1     2

CheckQM         2     2     3

CheckHdQM         3     1     3

You obtain the following status network:

Rejected

@HH@

Proc.closed @0F@     CheckProd @0F@     CheckQM @0F@     CheckHdQM @0F@     Released

    @HH@     @HH@     @HI@

    @HH@ @0G@ @0G@ @0G@     @0G@ @0G@ @0G@ @0G@     @0G@

The CheckProd status is set by production as the first user status. Quality assurance can then set CheckQM as the next status, which in turn permits the next status CheckHdQM. The recipe cannot be released for the scope of application unless the head of quality control has set this status.

Requirements

Standard settings

Recommendation

Activities

  1. Create a status profile (see Create Status Profile).
  2. Assign the status profile to the object type Recipe - Scope of application or Formula (see Assign Object Type).
  3. Define the required user statuses (see Define User Statuses). Bear the above-mentioned restrictions in mind.
  4. Translate the status profile and the user statuses into all languages required in your enterprise (see Translate Status Profile).
  5. Activate the status profile in the IMG activity Activate User Status Profile.

Further notes

You can also use user status profiles for the recipe header. For more information, see Recipe -> Set Up User Status Profile.

Business Attributes
ASAP Roadmap ID 203   Establish Master Data 
Mandatory / Optional 2   Optional 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 RMS_VRA_40 0 HLA0006251 Basic Data 
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
BSVS L - Logical transport object BS02  
History
Last changed by/on SAP  20001120 
SAP Release Created in 461