The US PayMIX utility is not supported in Release 11i. BEE (Batch Element Entry) should be used instead; it has been upgraded to provide superior functionality.
However to support existing customers who have used PayMIX in earlier releases of Oracle Payroll, the following changes have been made to the PayMIX objects.
The PayMIX tables have all been renamed as <original tablename>_OLD for reference purposes, in case you ever need to check their contents.
| Previous Table Name | New Name |
|---|---|
| PAY_PDT_BATCH_CHECKS | PAY_PDT_BATCH_CHECKS_OLD |
| PAY_PDT_BATCH_EXCEPTIONS | PAY_PDT_BATCH_EXCEPTIONS_OLD |
| PAY_PDT_BATCH_HEADERS | PAY_PDT_BATCH_HEADERS_OLD |
| PAY_PDT_BATCH_LINES | PAY_PDT_BATCH_LINES_OLD |
| PAY_PDT_LINE_ERRORS | PAY_PDT_LINE_ERRORS_OLD |
The PayMIX batch header table PAY_PDT_BATCH_HEADERS has been replaced by a view on the BEE batch header table PAY_BATCH_HEADERS. Similarly the PayMIX batch lines table PAY_PDT_BATCH_LINES has been replaced by a view on the BEE batch line table PAY_BATCH_LINES.
Thus an insertion, update or delete into either of these PayMIX tables now causes an insertion, update, or delete in the BEE tables. If you have written a third party interface to manipulate PayMIX batches, creation of a batch using your interface now results in the creation of a BEE batch. To process this batch, you must use the BEE Batch Header window.
Due to various inconsistencies between the original PayMIX tables and the BEE tables, the following rules have been enforced in the views mapping the PayMIX tables to the BEE tables:
The batch_id given to a batch should be derived from the PAY_BATCH_HEADERS_S sequence.
The name given to a batch created via the views will be "Batch <batch_id>".
The following restrictions also exist:
As the batch is processed using the BEE engine, the PayMIX checks, exceptions and line_errors tables cannot be supported.
In previous releases, PayMIX identified, from the contents of the batch, whether additional Special Inputs element entries were required. It created them if necessary. Neither the BEE engine nor the PayMIX views perform this operation in Release 11i.
Therefore, processing a Deduction or Earning type batch does not result in the creation of Special Inputs element entries unless rows have been explicitly created in the batch for these entities.
Important: We strongly recommend that customers use the BEE tables directly to create new batches, rather than these views. The definitions of the views are extremely complicated and hence their performance is inferior to the BEE tables.
The PayMIX windows are provided in Release 11i but do not appear on the default menus. They have been altered to use the new views and support the majority of the functionality they provided for PayMIX in earlier releases. They may be used to create, select, update, and delete batches. However, you must query and process the batch in the BEE Batch Header window to transfer it to the Oracle HRMS Entries table.
So, for example, you can create a batch using your own third party interface, and then use the PayMIX windows to query and edit the batch. Remember that Special Inputs lines must be created manually if they are required within Deduction and Earning type batches.
Important: However we strongly recommend that you use the BEE windows to create and manipulate new batches.