To create batch user accounts with concurrent programs:To create batches of users you must first write user hooks with your own custom logic.
See: Writing User Hooks to Create Batch User Accounts.
When you have created user hooks, you can run a set of concurrent programs to manage the batch creation of users on an ongoing basis.
You run the concurrent programs from the Submit Requests window.
To create batch user accounts with concurrent programs:Run the User Account Employee Extract Process
This program extracts employee records and creates a batch file of user accounts to be created or deactivated.
Run Data Pump Engine
This program uses the batch from the employee extract process and calls the HR API to create or deactivate user accounts.
Submit Data Pump Batch Exceptions Report
This program reports errors in the Data Pump Engine.
This extract process produces output records which are used by the Data Pump Engine. The Data Pump Engine calls the hr_user_acct_api to create or deactivate user accounts.
The batch name is written to the HR_PUMP_BATCH_HEADERS table. The extracted employee records are written to the HR_PUMP_BATCH_LINES table. The batch line table has defined generic attributes but for each API, the Data Pump generates a view on the HR_PUMP_BATCH_LINES table to reflect the parameters of the API.
The specific views tailored for the hr_user_acct_api are:
hrdpv_create_user_acct
Records for creating new user accounts can be mapped to this database view
hrdpv_update_user_acct
Records for terminated employees whose user accounts are to be inactivated can be mapped to this database view
Note: You must use a meaningful batch name. For example, run type and date range or another parameter. The batch name is the only way you can identify which batch to select in the Employee Data Pump process and the Data Pump Batch Exceptions Report processes.
To run the user account employee extract process:Access the User Account Employee Extract Process concurrent program.
Enter a batch name to identify the batch.
Enter the following date input parameters:
Start Date
defaults to SYSDATE. This parameter sets the start date from which the records are extracted
End Date
defaults to SYSDATE. This parameter is used in conjunction with the start date parameter to set a date range for the extraction of the records
Enter the following organization input parameters:
Organization
this parameter comprises a list of all the business group organizations that the responsibility is associated with. If you select an organization from the list of values, the program only extracts records from the selected organization.
Note: If you enter values in the Organization parameter, they are superseded by any values you enter in the Organization Hierarchy, Organization Hierarchy Version, and Parent Organization parameters. These parameters always take precedence and replace the values entered in the organization parameter and work together as a set.
Organization Hierarchy
organization hierarchy name for the responsibility's business group. This parameter contains an list of all the organizations hierarchies in the business group.
Organization Hierarchy Version
organization hierarchy version for the responsibility's business group. This parameter contains an list of the organization hierarchy versions selected in the organization hierarchy parameter.
Parent Organization
parent organization within the hierarchy. Selecting the parent organization will extract records from this organization and any organizations below the parent organization.
Enter the Run Type input parameters by selecting a processing option from the list of values. The processing options are:
Create User Account for New Hires
selects all employees hired between the start date and end date within the organization or organization hierarchy. This run type is used on an ongoing basis.
Create User Accounts for All Employees
selects all employees as of the end date, within the organization or organization hierarchy. The start date parameter will be ignored and employees terminated before the end date will not be selected either. This run type is used on the initial implementation and is usually used once.
Inactivate User Account for Terminated Employees selects all employees terminated between the start date and end date parameter within the organization or organization hierarchy. Once selected, the user account for the terminated employee or worker is end dated. This run type is used on an ongoing basis to end date accounts for terminated employees and workers within the date range.
Create and Inactivate User Accounts runs two queries. The first query selects all employees and workers hired between the start date and end date within the organization or organization hierarchy. The second query selects all employees and workers terminated between the start date and end date within the organization or organization hierarchy. This run type is used on an ongoing basis.
Note: Each employee or worker extracted from the database is recorded in the hr_pump_batch_line table. The hrdpv_create_user_acct view has been defined to map create user accounts to the hr_pump_batch_line table. The hrdpv_update_user_acct view has been defined to map inactivate user accounts to the hr_pump_batch_line table. You can access these views because the API column name is used to identify the record rather than the generic names used in the hr_pump_batch_lines table.
The Data Pump Engine will call the hr_user_acct_api to perform data validation and loading operations. The employee data is recorded in the hr_pump_batch_lines table.
Note: You must run the User Account Employee Extract Process before you run the Data Pump Engine process. The Data Pump Engine depends on the batch id the User Account Employee Extract process creates.
To run the Data Pump Engine concurrent program: Access the Data Pump Engine concurrent program.
Enter the following parameters:
Batch Name
you must enter the same batch name as you did in the Employee Extract Process. The Batch Name is the only information you have to identify which batch to run
Validation Mode
you can set two values, YES or NO. A YES value enables you to review errors in the batch, or related records in a batch, and change them before any are committed to the database.
A NO value will commit the data to the database if there are no errors. If there are errors the data will not be committed to the database and you can fix the errors and rerun the batch.
DataPump will set the Line Status to one of the following values:
E - Error
C - Completed
U - Unprocessed
V - Valid
Each person record is recorded in an individual batch line. The data pump exceptions report will show whether the error is from the batch header or batch line. You can identify which person record is in error from the person id in the exception report.
Note: You must run the User Account Employee Extract Process before you run the Data Pump Engine and Data Pump Batch Exception Report processes. The Data Pump Engine and Data Pump Batch Exception Report processes depend on the batch id the User Account Employee Extract process creates.
To run the Data Pump Batch Exceptions report: Access the Data Pump Process Exceptions Report concurrent program.
Note: You can run the Data Pump Engine and Data Pump Batch Exception Report processes in sequence. See: Overview of Concurrent Processes