|
User roles
Especially if you have an open architecture where users can access the entire catalog, you need to carefully evaluate what user roles must be established. It is highly recommended to leave the creation of certain object types to a "System Owner" type role.
This role will have the exclusive access to create or modify objects that will affect the entire user community. An example would be the creation of business event groups. Once you have your business event catalog in place, you do not want any user to be able to add, change. move or delete business event groups - because this will affect the "world". Hence, you should create a specific role that has the privilege of creating business event groups. You should assign this role to someone within production support or to the system owner, someone with a global view and perspective. If you allow all administrators to create their own business event groups, you will end up with an incoherent catalog, each portion only making sense to a specific training organization - but not to the rest of the user community.
The "System owner role" should also have the exclusive access to creating resource types and locations - again, users often do not pay attention and create locations twice or more times in the system, even though the object already existed. They might do the same with resource types.
Resource types have a multitude of relationships, which are prerequisites in order to use the resource reservation feature. Duplicate resource types will prevent you from using resource reservations properly. The same applies to duplicate location entries.
Next you will have the traditional training administrator role - typically these users create courses, events, book attendees and perform all the follow-up activities; they will have full T&E access - with the exception of the creation of business event groups, resource types and locations. You might also have a third role that will only perform booking activities - if you are a very large organization and have clerks that book attendees to events without actually creating events or performing any resource reservations etc, you might need this role.
ESS
If you choose to implement ESS in order to allow your employees to self-register for training courses via SAP's web enabled user interface, this will again impact the design of your naming convention and also of your business event catalog. The standard SAP ESS functionality for T&E does not actually display the training catalog to the user. Users can search for courses by name or location. This is why you need to be careful again when naming business event groups, business event types (courses) and locations - these names have to be searchable.
Alternatively, if you choose to enhance the existing ESS solution by displaying the business event catalog, bear in mind that the hierarchy you have chosen has to make sense to the students who are searching for courses. This emphasizes again the need to carefully plan the structure of your catalog, given the fact that it will be used by a very large number of employees who might self-register and an extensive administrator user group who will use it for course management.
|