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 Lease Administration:

  • Critical Date Notification Generator (RE_CRDT_GEN)

    The Critical Date Notification Generator process uses these temporary tables:

    • RE_CDNT_TAO

    • RECDNTID_TAO

  • FAS-13 Schedule Generator (RE_FASB_GEN).

    The FAS-13 schedule Generator process uses this temporary table (RE_FASB_TAO).

  • Recurring Transactions Schedule Generator (RE_GENTRANS).

    The Recurring Transactions Schedule Generator process uses these temporary tables:

    • RE_GENDTL_TAO

    • RE_GENTXN_TAO

    • RE_PROVAR_TAO

    • RE_TRMAMT_TAO

    • RE_LS_EXP_TAO

    • RE_LSXBU_TAO

  • Send Billing Transactions to TBP (RE_INTFC_TBP).

    The Send Billing Transactions to TBP process uses these temporary tables:

    • RE_INTFC_TAO

    • RE_TXN_TAO

  • Lease Admin Pagelet data (Summary Tables) Collector (RE_PGLT_DATA).

    The Lease Admin Pagelet Data (Summary Tables) Collector process uses this temporary table RE_SPCUTL_TAO.

  • Request for Employee Location Assignments from CAFM (RE_REQ_ELOC).

    The Request for Employee Location Assignments from CAFM process uses this temporary table RE_EMPLOC_TAO.

  • Request for Property Size and Occupancy from CAFM (RE_REQ_PROP).

    The Request for Property Size and Occupancy from CAFM uses this temporary table RE_PROP_TAO.

  • Post FASB Schedules to GL (RE_STGL_POST).

    The Post FASB Schedules to GL process uses these temporary tables:

    • RE_STGLS_TAO

    • RE_STGLT_TAO

  • Rent Variance Extract (RE_RENT_VAR)

    The Rent Variance Extract process uses these temporary tables:

    • RE_PRIRNT_TAO

    • RE_PRIVAL_TAO

    • RE_RNTSCH_TAO

    • RE_RNTTRM_TAO

    • RE_RNTTXN_TAO

    • RE_RNTVAR_TAO

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, you should also configure the temporary tables for those processes. The PeopleSoft General Ledger documentation discusses how to do this in detail.

PeopleTools: Application Engine