You can enter information in a batch for as many elements and assignments as you require. You can enter defaults for any value to speed up data entry, and you can change the defaults as you work through a batch. You choose which element input values to display in the Batch Lines window.
You can add your own validation procedures to the standard process. For example, you can set up control types, such as record counts, and write a validation procedure to check that the batch matches the control totals you enter for each type. You can also add any business validation you require, for example to check that amounts entered for a bonus do not exceed a maximum, or that an assignment's paid time off entitlement is sufficient to cover time taken.
When the batch is ready for transfer to the database, you run the BEE transfer process from the Batch Header window. This process first performs the same checks as the validation process. If it finds no errors, it transfers the element entries from the temporary tables to the Entries table in Oracle HRMS.
You can choose whether the transfer process automatically purges the entries from the temporary tables after transfer. You can also run a separate purge process.
|Valid||All of the lines, control totals, and header are valid.|
|Transferred||All of the lines, control totals, and header have been transferred.|
|Unprocessed||At least one line, control total, or the header is unprocessed.|
|Error||At least one line, control total, or the header is in error.|
|Status Mismatch||The combination of statuses in the header, lines, and batch is not consistent. For example, it is inconsistent for some, but not all, of the lines to have the status Transferred.|
Note: A status mismatch is not possible if you always use the Batch Header and Batch Lines windows to enter and maintain a batch.
Validating a BEE Batch
Transferring a BEE Batch
Purging a Batch from the BEE Tables
Rolling Back a MIX Process