Temporary Table processing failure during allocation phase

Usually,when an application engine is run it inserts a record corresponding to the RunControl Id and the process instance in the PS_AERUNCONTROL and a record in thePS_AETEMPTBLMGR if a temporary table is used and locked by an AE instance.Therefore, each Application Engine program must declare which temporary tablesit will use, saved in PSAEAPPLTEMPTBL, and how many instances of it will runconcurrently,stored in PSAEAPPLDEFN.A Temporary Record is created as anordinary database table, but Application Designer creates multiple copies ofthe table and uses the view PSTEMPTBLCNTVW to calculate the total number ofinstances of the temporary table required by all AE programs and afterwardsadds on the number of Global Instances, saved in PSOPTIONS.
If the AE runs out of instances of temporary tables, it uses the table withoutthe numeric suffix, and this one is treated as a shared temporary table. Thatis way all temporary records should have the field PROCESS_INSTANCE as a partof their unique key ( otherwise a warning will rise when you try to save themin Application Designer).
If the AE ends normally (not abended), both PS_AERUNCONTROL and PS_AETEMPTBLMGRrecords are cleaned (process instance corresponding records are deleted). Ifnot the temporary records (TAO,TMP) get stuck in the PS_AETEMPTBLMGR and therun control ids in the PS_AERUNCONTROL table.
AS a partial conclusion, one must take into consideration cleaning both thesetables (DELETE FROM PS_AETEMPTBLMGR;DELETE FROM PS_AERUNCONTROL;) when applyingmaintenance procedures (no users loged or processes run on the PS environment).
Secondly, one might, want to check if the values set in the table PSOPTIONS(SELECT TEMPTBLINSTANCES,TEMPINSTANCEBATCH,TEMPINSTANCEONLINE FROM PSOPTIONS )or on the page Home>PeopleTools>Utilities>PeopleTools Options are:

TEMPTBLINSTANCESTEMPINSTANCEBATCH TEMPINSTANCEONLINE
———————- ———————- ———————-
3 0 3
The TEMPTBLINSTANCES and the TEMPINSTANCEONLINE may vary according to yourapplication configurations needs, but TEMPINSTANCEBATCH should be set to “0″for all PeopleSoft implementations (eg:FSCM,HR), except for the EPM.In aditionone should ensure that the value of AE_LOCK in the PS_AELOCKMGR record is “N”.
Another aspect one might consider is to increase the number of AE temporarytable Instances. The number of temporary table instances may be increased for aspecific Application Engine program or may be increased globally – for ALLApplication Engine processes.
- To increase the number of Temporary Table Instances for a specificApplication Engine program , go to the Application Designer, open the affectedApplication Engine Program,then go to File>Definition Properties(ALT+ENTER), Temp Tables tab, increase the value in the “Instance Count”textbox, and save the AE program.
- To increase the number of Temporary Table Instances for all ApplicationEngine programs go to Home > PeopleTools > Utilities > Use PeopleToolsOptions and then increase the value of “Temp Table Instances (Total)” and thecorresponding value of “Temp Table Instances (Online)” will be automaticallyincreased to the same value.