Hierarchy
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials⤷
PLM-RM-REC (Application Component) Recipe⤷
RMSRCPMSC (Package) RMS-RCP: Miscellaneous
IMG Activity
| ID | RMS_MSCHNG_101 | Specify Status Change Profiles |
| Transaction Code | S_AEN_10000264 | (empty) |
| Created on | 20050112 | |
| Customizing Attributes | RMS_MSCHNG_101 | Specify Status Change Profiles |
| Customizing Activity | RMS_MSCHNG_101 | Specify Status Change Profiles |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | RMS_MSCHNG_101 |
Use
In this IMG activity, you define the status change profiles and specify the following for each status change profile:
- The specification types for which the defined status changes are made
- The conditions that must be fulfilled so that a status can be changed
- The status changes that the system makes when the conditions are fulfilled
You can choose the status change profiles defined here before you run the mass status change.
Requirements
Under Specify Mass-Change Services you have defined the mass-change service for the mass status change.
Standard settings
Default settings are supplied with the system.
Activities
- Specify the required mass change profiles under Change Profile. For each profile, specify whether you can change the sequence in which the system changes the statuses of the selected specifications before the mass change is run.
- Under Specification Types and Processing Sequence, for each profile specify for which specification types status changes are to be made, and specify in which sequence the system is to make the status change for specifications of the different specification types.
Note:
- When defining the sequence, note the settings that you made in Customizing for Recipe Management under Set Up Checks for Switching Status. For example, you can specify there that you can release a recipe only if all substances in the recipe are released. In this IMG activity, you must then specify that the system makes status changes for specifications of the specification type Real Substance before those for the various specification types of the specification category Recipe. In this case, we recommend that you do not allow changes to the processing sequence (step 1).
- Specify the following for each specification type under Changes to Scope-of-Application Status:
- The conditions that must be fulfilled so that the system changes the status
- The status changes that the system makes if the condition is fulfilled
The system makes the status changes defined here on the Scope of Application tab page (for recipes and formulas) or the Status tab page (for specifications of other specification categories). The system makes the status changes in the sequence that you specified in this IMG activity. That means if the condition is fulfilled that has the sequence 1, the system sets the corresponding status. If this status appears in the condition with the sequence 2 (or a higher number) and this condition is thus also fulfilled, the system sets the appropriate status that was defined for the condition with the sequence 2, and so on.
- Under Conditions for Recipe Status, specify the conditions for the specification types of the specification category Recipe that must be fulfilled before the system changes the recipe status on the Basic Data tab page. If you enter a system status and a user status, these are linked logically with AND, that is, a recipe must have both statuses for the condition to count as fulfilled.
- Under Changes to Recipe Status, specify for each condition you defined in the previous step the status changes that the system is to make on the Basic Data tab page if the condition is fulfilled. Note the following here:
- If you want the system to change the system status, you must specify the business transaction that is to trigger the required system status change.
- You can only define either a business transaction or a user status in one line. If you want the system to change the system status and the user status of a recipe, you must define this in two separate lines.
- If you specify a user status, you must define whether the user status is active or inactive after the status change, that is, whether the system is to set or cancel the user status.
For more information about mass status change, see SAP Library for the Recipe Management component under Mass Status Change.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 3 | Nonrequired 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_MSCHNG_101 | 0 | ALN0000101 | Recipe Management |
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 |
| RCPVC_MSC_STATUS | C - View cluster | SM34 |
History
| Last changed by/on | SAP | 20050112 |
| SAP Release Created in | 600 |
