After having training in how the 'user functionality' is configured, as mentioned above, you will also need to know how the user authorizations work and can be maintained (you do not want to have to stop planning to add or amend an authorization, for example if you have user-specific variables).
You need to know what mechanism is set up to effect locking - that is to prevent changes by users after the planning is supposed to be finished.
You need to know what admin tasks are required in addition to the tasks that users perform: for example before planning starts and after it ends, and whether the required functionality for the admin is in fact set up and has enough flexibility. You need to understand the meaning of all the BPS variables used.
It would also be good to be shown some techniques for solving problems in BPS ( where to look when investigating a problem; logs, traces, details of the data structure, fact table vs queries, using closed requests to test changes).
Were you involved in the testing? If not you should find out about the test plans, what problems occurred, if any are outstanding. Its important that the testing was thorough, and includes business-user testing in addition to other system/functionality tests.
You will need to know what reports are available, how users access them and who maintains them. (They may well not have been developed by the BPS team - but the users are not interested in that).
Regards
Stephen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.