Configuring Temporary Tables for Batch Processing

When you run batch processes in parallel, you risk data contention and deadlocks on temporary tables. To avoid this, PeopleTools enables you to dedicate specific instances of temporary tables for each process. When PeopleSoft Application Engine manages a dedicated temporary table instance, it controls the locking of the table before use and the unlocking of the table after use.

When you decide how many temporary table instances to dedicate for a process, consider the number of temporary tables that the process uses. More instances result in more copies of the temporary tables on the system. For example, if a process uses 25 temporary tables and you have 10 instances for a process, you will have 250 temporary tables on the system.

If you run processes in parallel and all of the dedicated temporary table instances are in use, the performance of the process decreases. You need to find a balance that works for your organization.

Note: When you specify the number of instances, PeopleSoft Application Designer displays a list of the temporary tables for the process. Use the list to determine how many temporary tables each process uses.

Specify how many temporary table instances to dedicate for each of the following batch processes that can run in parallel in PeopleSoft Payables:

  • Voucher Build (AP_VCHRBLD).

  • Matching (AP_MATCH).

  • Pay Cycle (AP_APY2015).

  • Voucher Posting (AP_PSTVCHR).

  • Payment Posting (AP_PSTPYMNT).

  • Document Tolerance (FS_DOC_TOL).

  • Payables to Assets Interface (INTFAPAM).

The PeopleTools documentation discusses the usage of temporary tables in detail and describes how to specify the number of instances.

If you run any of the PeopleSoft General Ledger COBOL processes, also configure the temporary tables for those processes. The PeopleSoft General Ledger documentation discusses how to do this in detail.