Oracle Applications Training
There are two types of Oracle applications training - system training and process training.
System training covers the basic functionality of the application, what I can form and function. A user will get introduced to the different screens they will encounter and the basic functionality provided by the application. The training topics tend to be general and built around the functionality available. System training is OK is you just want to get a feel for an application, but really doesn't convey how the applications is used in the business environment.
Process training requires the instructor to cover and use Oracle applications functionality as it is encountered during the business process. Another words, the process drives the direction of training.
You can tell when you are in system training because the topics and agenda have a top down approach according to the menu driven application. Many instructors start with the layout of the screen, then the main menu options starting with File, Save, Print, etc. and finally creating and editing information. But there is no connectivity between the steps. It's as though you are learning a bunch of disconnected unrelated topics. Users with a strong applications background can connect the dots easier than typical end users. System training can be great for technical users. This type of training design generally requires more data seeding as the exercises do not feed off one another.
With process training, the topics are tied sequentially to each other. For example, with Oracle Purchasing training, you would first cover the topic "Creating a Requisition" before you covered the topic "Creating a Purchase Order from an approved Requisition". By following the standard business process during training, the tasks are now related to each other instead of being disconnected tasks. Process training is usually accomplished by staging the tasks sequentially in the order they would happen during the normal business cycle.
This type of training design generally requires less data seeding as each exercise is built on using the data from a previous exercise. If planned correctly, the Purchasing exercises can be built on to the iProcurement exercises and the Payables exercises can be built on to the Purchasing exercises.
In addition to less work setting up the training environment, by connecting the exercises around a business process, students easily apply the tasks they are learning to their real world daily activities. Process training is the simplest way to communicate day in the life of training.
System training covers the basic functionality of the application, what I can form and function. A user will get introduced to the different screens they will encounter and the basic functionality provided by the application. The training topics tend to be general and built around the functionality available. System training is OK is you just want to get a feel for an application, but really doesn't convey how the applications is used in the business environment.
Process training requires the instructor to cover and use Oracle applications functionality as it is encountered during the business process. Another words, the process drives the direction of training.
You can tell when you are in system training because the topics and agenda have a top down approach according to the menu driven application. Many instructors start with the layout of the screen, then the main menu options starting with File, Save, Print, etc. and finally creating and editing information. But there is no connectivity between the steps. It's as though you are learning a bunch of disconnected unrelated topics. Users with a strong applications background can connect the dots easier than typical end users. System training can be great for technical users. This type of training design generally requires more data seeding as the exercises do not feed off one another.
With process training, the topics are tied sequentially to each other. For example, with Oracle Purchasing training, you would first cover the topic "Creating a Requisition" before you covered the topic "Creating a Purchase Order from an approved Requisition". By following the standard business process during training, the tasks are now related to each other instead of being disconnected tasks. Process training is usually accomplished by staging the tasks sequentially in the order they would happen during the normal business cycle.
This type of training design generally requires less data seeding as each exercise is built on using the data from a previous exercise. If planned correctly, the Purchasing exercises can be built on to the iProcurement exercises and the Payables exercises can be built on to the Purchasing exercises.
In addition to less work setting up the training environment, by connecting the exercises around a business process, students easily apply the tasks they are learning to their real world daily activities. Process training is the simplest way to communicate day in the life of training.
Category: software
0 commentaires