- Purging the data in the AA$BATCH_DETAIL & AA$BATCH_HEADER tables as part of regularly scheduled maintenance, once a week is recommended although it can be as often necessary
- Keep e.g. the records that pertain to jobs that still have corresponding WorkList lines. This will allow to research e.g. an Auto Allocation that was in Approved status on the WorkList and the records in the batch tables may still be needed for review purposes
The below SQL to purge would look like this:
Delete from AA$BATCH_HEADER where job_key not in (select aa_job_nbr from worklist);
- Another good rule of thumb is to remove anything not needed to generate reports on anymore
- There is a foreign key constraint on AA$BATCH_HEADER that will do a cascade delete through AA$BATCH_DETAIL for all records deleted in the parent table
Administrator Guide (Admin.pdf) mentions that these tables require routine cleanup and that Auto-Allocation does not maintain these tables. A script to clean up the tables based on whatever criteria is chosen (date, etc) need to be created.
Administrator Guide (Admin.pdf):
Reporting records all major events to the report tables as Auto-Allocation proceeds. There are two tables, AA$BATCH_HEADER and AA$BATCH_DETAIL. All machines running Auto-Allocation from the same schedule table report to the same centralized reporting table.
Oracle Forms or another Oracle report reading tool to view these reports can be used.
The header table includes the status field with major status information, such as approved or released. The detail table lists any assumptions that were made or errors encountered. This table is specific to Auto-Allocation, and is not the detail table used by JDA Allocation.
These tables require routine cleanup. Auto-Allocation does not provide maintenance on these tables.
