As tutorials E2.2 and E2.3 each have only 20 and not 25 places, they can only absorb 90 module bookings and not 100.
During module booking, capacity can be checked at three levels:
It is often necessary to check the capacities at the event and event package level, but it is acceptable for the module to be overbooked. Using this process means that the system does not need to perform the module- level capacity check. This allows for a more efficient module booking process.
This function is available if you have activated the business function SAP Student Lifecycle Management: Implementation Accelerator (ISHERCM_604_EXIAP_M).
In this IMG activity, you can switch off the capacity check at the module level.
During module booking, the system checks the capacity at module, event package and event level. This ensures that the module, event package and event are not overbooked.
The event or event package must not get overbooked, but it is acceptable for the module to be overbooked. Therefore, the capacity check at the module level is optional.
By default, the capacity check at the module level is carried out.
T o s w i t c h o f f t h e c a p a c i t y c h e c k , e n t e r t h e s e t t i n g v a l u e ' X ' f o r g r o u p ' M O D R E G ' a n d s e t t i n g ' N O _ S M _ C A P A See Customizing for Student Lifecycle Management under ' .
Prerequisites which are defined by means of relationship 529 ( () contain a conditional booking option. This also applies to conditions which are stored in rule containers. This option enables you to book modules conditionally.
) or 533
In cases where a prerequisite or corequisite is open (unfulfilled) when a module is booked, you or the system can book this module conditionally by setting the conditional booking indicator.
© 2009 SAP AG
| bpx.sap.com 106