Hierarchy

⤷

⤷

IMG Activity
ID | CM_XX_AUDIT17 | Define Subrequirements and Auxiliary Conditions |
Transaction Code | S_KK4_82001020 | (empty) |
Created on | 20021011 | |
Customizing Attributes | CM_XX_204_2_2 | Multiple Use: Non-Critical Optional Activity, IS-HER-CM-AD, ASAP 204 |
Customizing Activity | CM_XX_AUDIT17 | Define Subrequirements and Auxiliary Conditions |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | CM_XX_AUDIT17 |
Use
In this IMG activity, you define the subrequirements and auxiliary conditions you you need to set up your requirement catalogs.
You can assign the subrequirements and auxiliary conditions you define here to requirements in the Edit Requirement Catalog application (transaction code PIQRLCATM). (You can also create new subrequirements and auxiliary conditions in this application.)
When you create a subrequirement, you must define its category. The subrequirement category determines which subrequirement elements you can assign to the subrequirement. When you assign subrequirement elements to index-dependent and index-independent subrequirements, you must take into account the following differences:
- Elements of an index-dependent subrequirement:
- Performance indices and their target values
- Filters for selection of academic work objects
- Selection method for module proposals
- Elements of an index-independent subrequirement:
- Conditions
- Selection method for module proposals
If you specify filters or conditions, the system proposes the parameters you assigned to filters or conditions in the previous IMG activities. Each parameter is displayed in a separate line.
You must enter a value for all parameters which are not optional. Optional parameters can retain their initial value. If you defined input help for the parameter, the system offers this here.
When you create an auxiliary condition, you have to define key figures and specify the target values for these key figures. You can use auxiliary conditions and subrequirements to map degree or stage requirements in the system. The system saves the auxiliary conditions and subrequirements in the relevant requirements, technically speaking in the PD rule container object (object type RC) of infotype 1747. If only the auxiliary conditions of a subrequirement have to be fulfilled, and not the implicit condition ("100% of all subrequirements must be fulfilled for the requirement to be fulfilled) and the auxiliary conditions, you can switch off the implicit condition. If you do not switch it off, all subrequirements and auxiliary conditions have to be fulfilled.
Requirements
You implemented the required filters and conditions, and assigned the relevant parameters in the previous IMG activities.
You also implemented the required selection method in the IMG activity BAdI: Selection Method. The selection methods you want to use for subrequirements must be assigned to selection method group AUDS (selection method group for subrequirements). You can assign the relevant subrequirements to this selection method group in the IMG activity Assign Selection Methods to Selection Method Group.
You have defined the required key figures. You make this setting in Customizing for Campus Management in the section Campus Management Master Data -> Key Figures.
Activities
- To create a new subrequirement, leave the Subrequirement field on the initial Subrequirements screen empty, and choose Create.
The system automatically assigns the subrequirement the next available key. (Technically speaking, the system creates a rule module.)
- Enter a name for the subrequirement.
- Specify whether the subrequirement is index-dependent or index-independent.
- Assign the required subrequirement elements (see above).
Note: Enter a parameter value for filter or condition parameters that are not optional.
- Create a description for the subrequirement.
Business Attributes
ASAP Roadmap ID | 204 | Establish Functions and Processes |
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 |
PIQAUDSM | T - Individual transaction object | PIQAUDSM |
History
Last changed by/on | SAP | 20040226 |
SAP Release Created in | 471 |