Hierarchy

⤷

⤷

⤷

IMG Activity
ID | CFMENUOLMEOMGSCK_1A | Check Release Strategies |
Transaction Code | S_P99_41000390 | (empty) |
Created on | 19991007 | |
Customizing Attributes | CFMENUOLMEOMGSCK_1B | Attributes for "Check Release Strategies" |
Customizing Activity | CFMENUOLMEOMGSCK_1C | Subobjects for "Check Release Strategies" |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | CFMENUOLMEOMGSCK |
In this step, you can check whether the basic settings for your release strategy are complete and correct.
Checks
The following checks are carried out for purchasing documents:
- Basic checks
The system checks whether the necessary release groups exist in the system. For example: Whether a release group has been deleted even though an associated release strategy still exists.
- Checks regarding release groups and release classes
The system checks whether the release groups and the assigned classes have been maintained correctly. For instance, whether
- A class has been assigned to the release groups and whether it exists in the system
- Characteristics - which exist in the system and are linked to the communication structure - have been assigned to the class
- A customer exit must be maintained for a characteristic
- Checks regarding release codes
The system checks whether the release codes have been maintained correctly
- Checks regarding release indicators
The system checks whether the release indicators have been maintained correctly. For example: Whether release indicators exist for the statuses "Blocked" and "Released".
- Checks regarding release strategies
The system checks whether the release strategies have been maintained correctly. For example, whether:
- Release codes have been assigned to the release strategy
- The relevant release indicators have been assigned to the initial and final statuses of a release strategy
- Checks regarding link to workflow
The system checks whether the link between your release procedure and workflow has been maintained correctly. For example, whether:
- A processor (member of staff responsible for processing) has been assigned to a workflow-relevant release code and is defined in the organizational plan
- A customer exit is necessary for the role resolution
Result
The result of these checks is displayed in a log. Further information is available in the Customizing activity under Help -> Application Help.
Example
Requirements
Standard settings
Recommendation
Activities
- Start the check by performing the Customizing activity.
- Check whether any error or warning messages are displayed.
- If necessary, correct your Customizing settings for the release procedure.
- Re-run the check after making corrections.
Further notes
Business Attributes
ASAP Roadmap ID | 899 | not to be assigned |
Mandatory / Optional | 2 | Optional 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 |
IMGDUMMY | D - Dummy object | OMGSCK | Check Release Strategies |
History
Last changed by/on | SAP | 19991007 |
SAP Release Created in |