The Batch Interface Event (BIEVNT) page is used to specify information required to run the Batch Interface Pre-Processor job. The BIEVNT table stores information used to match against the input files to the job. The table can also be used to track how many table records or transactions are imported or submitted using the System Maintenance Utility (SysManUtil) or Multi Process Submit job against a specific interface run.
Before running the Batch Interface Pre-Processor job, you need to create the corresponding BIEVNT record to indicate the expected count and/or total that will be processed for the Batch ID, Department, Unit, Import Date, and Transaction or Table combination. If pre-approval is required, you need to approve the BIEVNT record before running the job. You cannot edit the Expected Received Date, Expected Transactions, or Expected Total after approving the record.
When the Batch Interface Pre-Processor job is run, the BIEVNT record is updated to reflect the results of the matching. You can run the Interface Batch Demand Report process to see the processed BIEVNT records and their corresponding processed interfaced transaction counts on a given day. Refer to the Batch Interface Pre-Processor and Interface Batch Demand Report run sheets in the CGI Advantage - Financial Utilities Run Sheets guide for more information.
When a specific interface run involves importing table records, overlaying table records, importing transactions, or submitting transactions, and an action is performed using the System Maintenance Utility (SysManUtil) or Multi Process Submit job with the BiEvntStatsListener and relevant parameter information, the BIEVNT record is updated to reflect the import or submit counts. Refer to the “System Maintenance Utility Listener” topic and the “Multi Process Submit” run sheet in the CGI Advantage - Financial Utilities Run Sheets for more information.