Hierarchy
IS-PS-CA (Software Component) IS-PUBLIC SECTOR CONTRACT ACCOUNTING⤷
IS-HER-CM-AD (Application Component) Administration⤷
PMIQ (Package) Campus Management
IMG Activity
| ID | CM_XX_AKAL03 | Define Evaluation Paths for Specific Callup Points |
| Transaction Code | S_KK4_82000822 | (empty) |
| Created on | 20011115 | |
| Customizing Attributes | CM_XX_203_2_2 | Multiple Use: Non-Critical Optional Activity, IS-HER-CM-AD, ASAP 203 |
| Customizing Activity | CM_XX_AKAL03 | Define Evaluation Paths for Specific Callup Points |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | CM_XX_AKAL03 |
Use
In this IMG activity, you assign an evaluation path to specific callup points which the system can use instead of the default evaluation path.
The applications uses these evaluation paths at the given callup points to find the academic calendars (objects of object type CA).
You can only assign different evaluation paths to callup points which are flagged as relevant for the academic calendar in table T7PIQCHECKTP (Callup Points). This currently applies to the following callup points:
- 0001 - Module Booking (General)
- 0003 - Module Booking (Single)
- 0201 - Calendar Determination in Event Planning
- 0500 - Create Academic Work (Ext.Maint.Dialog)
If one of these callup points is not assigned an evaluation path, the system then uses the default evaluation path of the academic calendar for this callup point. The system does not use this setting if you specified that it should evaluate only the academic calendar assigned to the top organizational unit in the IMG activity Define General Evaluation of Academic Calendars.
Requirements
You have defined the required evaluation paths in Customizing for Campus Management under Campus Management Master Data -> Academic Structure -> Organizational Structure -> Organizational Management -> Basic Settings -> Maintain Evaluation Paths.
When you define evaluation paths for the academic calendar, do not set skip flags, and specify "*" as the priority. Evaluation paths should have a "bottom-up" logic (for example, module -> program -> organizational unit), and not vice versa.
Do not create evaluation paths in which one object type is linked to several object types (except in the object type CA). The system will only take into account the objects of the first object type it finds. If the system finds several objects of the same object type at the same level, it uses the object with priority 1 to determine the evaluation path. If none of the objects has priority 1, the system chooses the first object it finds.
Activities
If you have defined a different evaluation path for one of the given callup points, assign this evaluation path to the callup point.
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| 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 |
| V_T7PIQCALPATHTP | V - View | SM30 |
History
| Last changed by/on | SAP | 20040220 |
| SAP Release Created in | 464 |
