Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
ME0C (Package) Customizing R/3 Purchasing
IMG Activity
| ID | CFMENUOLMEOMGQ_A | Check Release Strategies |
| Transaction Code | S_P99_41000391 | (empty) |
| Created on | 19991007 | |
| Customizing Attributes | CFMENUOLMEOMGQ_A | Attributes for "Check Release Strategies" |
| Customizing Activity | CFMENUOLMEOMGQ_A | Subobjects for "Check Release Strategies" |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMGCFMENUOLMEOMGQCK |
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 purchase requisitions:
- 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.
Note
The following checks are carried out for item-wise and overall release and the results displayed separately.
- Checks regarding release group and release class
The system checks whether the release groups and the associated classes have been maintained correctly. For example, 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 | OMGQCK | Check Release Strategies |
History
| Last changed by/on | SAP | 19991125 |
| SAP Release Created in |
