Suppressing Automatic Lookups for Improved Performance

Prompt table Exclusion List in Peoplesoft.
Improve prompt table performance in Peoplesoft

Many fields in PeopleSoft applications has lookup or prompts tables indicated by the magnifying glass. When you click on that icon you are taken to a lookup dialogue, but by default
the search fires automatically

However, in peoplesoft only the first 300 rows are retrieved into the component buffer, and only the first 100 rows of that set are shown on the first page. These results are almost certainly
useless to the operator who must then enter criteria into the lookup search dialogue and search again.

If we can suppress the automatic search performance of the prompt will improve. User can search the data after providing the search values and no.of rows returned will less and more usefull to the user.

Question is how can we suppress this ? from 8.44 peoplesoft has provided the Prompt table Exclusion List.

Peopletools >Utilites > Administration > Lookup Exclusion Table.

The tables in this list are stored in the Application server cache.
You don't have to restart any application servers before the behaviour of the lookup to change.

You should should for those prompt which usually takes more time.

The following query will identify all the records that are used as look-up records within a PeopleSoft system.

FROM pspnlfield p
, psrecfielddb f
, psrecdefn r
WHERE p.fieldname = f.fieldname
AND p.recname = f.recname
AND r.recname = f.edittable


Peoplesoft Training Videos

Overview PeopleSoft 8 steps

Starting with peoplesoft Application Desinger


How Peoplesoft Better than SAP - Why Peoplesoft ?


Books for Peoplesoft Applications


Useful Navigations of AWE Workflows components

Setup and configure workflow

1) Main Menu > Set Up HRMS > Common Definitions > Approvals > Register Transaction ----- Create Approval Process ID (Cross refernce table , Header table , App class ,Approval compoent is defined).

2) Main Menu > Set Up HRMS > Common Definitions > Approvals > Setup Process Definitions ----Create Definiation ID for the Process ID, Definaiton Criteria ,Stages ,paths ,steps

3) Main Menu > Set Up HRMS > Common Definitions > Approvals > Configure Transaction ----- Add Events and notifications to transaction.

4) Main Menu > Set Up HRMS > Common Definitions > Approvals > Workflow Transaction ----- Register workflow transactions.

5) Main Menu > Set Up HRMS > Common Definitions > Approvals > Maintain User Lists ------ Define the user list or hierarchy used for routing transactions for approval.

6) Main Menu > Set Up HRMS > Common Definitions > Approvals > Generic Templates ------ Maintain email templates.

7)Main Menu > Set Up HRMS > Common Definitions >Selfserivce > System workflow rules ------ Workflow rule for speicfic SETID.

Approvals and Delegation

1) Main Menu > Workforce Administration > Self Service Transactions > Add Delegation Request ----- Add a new delegation request on behalf of a delegator.

2) Main Menu > Workforce Administration > Self Service Transactions > Administer Delegation ----- Admin for the Delegation. Admin can delegate the transactions .

3) Main Menu > Workforce Administration > Self Service Transactions > Administer/Monitor Apporavals ----- AWE admin for the Approvals. Admin can apporve transactions.

4)Main Menu > Workforce Administration > Self Service Transactions > Approvals Audit Report ----- Apporvals Audit Report.

Delegation setup

1)Main Menu > Set Up HRMS > Common Definitions > Delegation > Installation settings ----- Configure AWE Admin Role , Enable Hierarcies , Duration to check for active proxies

2)Main Menu > Set Up HRMS > Common Definitions > Delegation > Configure Delegation Transactions ----- Configure Delegation Transaction.


%UpdateStats is not working or it is Ignored

PeopleSoft Application Engine replaces this meta-SQL construct with a platform-dependent SQL statement that updates the system catalog tables used by the database optimizer in choosing optimal query plans.
Peoplesoft intends that you use this construct after your
program has inserted large amounts of data into a temporary table that will be deleted before the end of the program run.

For databases that either execute an implicit commit for %UpdateStats or require a commit before and/or after this meta-SQL, PeopleSoft Application Engine skips %UpdateStats in the following circumstances:
• A commit is not allowed, as in within an Application Engine program called from
• The program issues a non-select SQL statement since the last commit occurred. In such a situation, data is likely to have changed.
• You are deferring commits in a select/fetch loop in a restartable program. PeopleSoft Application Engine skips %UpdateStats even if the previous condition is false.


Interview questions on Workflow Delgation framework in peoplesoft

Question # 1: What types of delegations are supported in 9.0?

Answer: The following delegations are supported:.

• Upward - delegating to your manager

• Downward - delegating to your subordinate

• Lateral - delegating to a peer Please note that cascading delegation is NOT supported (see question #2 for more information).

Question # 2: What is a cascading delegation?

Answer: Cascading delegation is the ability to delegate your delegated authority. For example:.

If Antonio delegates the ability to approve absence requests to Owen and Owen accepts the delegation, Owen cannot then re-delegate that same absence request approval authority to Will, Laura, or anyone else in the organization. Once a proxy has accepted a delegation request, he/she cannot delegate that authority to someone else and only the delegator (or the Delegation Administrator on behalf of the delegator) can revoke the request.

Question # 3: Does the application server need to be bounced when changes are made to the Delegation Installation Settings page?

Answer: No, the application server does NOT need to be bounced when changes are made to the Delegation Installation Settings page. Changes are reflected once the page has been saved.

Question # 4: What happens to any pending transactions when a delegation is revoked?

Answer: If there are pending transactions and a delegation is revoked, the pending transactions will be re-routed to the delegator.

Question # 5: How does delegation work with the Alternate User ID field on the User Profile component?

Answer: When new delegation requests are added, the system checks the User Profile - Workflow tab, so see if an Alternate User ID has been specified and if the dates overlap. If the dates overlap, the system will issue a warning to the user. The delegation request will override the User Profile Alternate User ID, but only for the transactions included in the delegation request.

Question # 6: Can a user delegate a transaction that they do not have access to?

Answer: No, a user cannot delegate transactions that they do not have access to. For example, an employee who is not a manager and does not have access to manager-level transactions would not be able to delegate manager specific transactions.

Question # 7: When searching for a proxy by hierarchy can you search up the hierarchy as well as down the hierarchy?

Answer: For any hierarchy chosen, the system will only drill up or down one level and return a set of employees. For example, the system will not show indirect reports or people above the user’s direct manager. This is by design.

Question # 8: What notifications are delivered for delegation?

Answer: The following notification templates are delivered as system data for delegation:

DelegationAccept - Accept Delegation

DelegationAdminAdd - Admin adds Delegation requests

DelegationAdminRevoke - Admin revokes Delegation

DelegationBatch - Batch to send email

DelegationError - Delegation Error

DelegationNotifyAdmin - Delegation Notify Admin

DelegationReject - Reject Delegation

DelegationRequest - Delegation Request

DelegationRevoke - Revoke Delegation

Question # 9: Where can I find all the Delegation related components?


For setting up Delegation, all components may be found at

Main Menu > Setup HRMS > Common Definitions > Delegation > Delegation Setup Center

. Users of these components should be functional analysts and technical implementers. For maintaining Delegation, all components may be found at

Main Menu > Workforce Administration > Self Service Transactions > Approvals and Delegation

. Users of these components should be delegation administrators or functional analysts. The set up and maintenance components for Delegation are located in two distinct areas of the application. It is recommended that delegation administrators be given access to the maintenance components but not the set up components because changes to set up data – inadvertent or otherwise – can impact the entire enterprise. Access to the set up Delegation components should be given to very few people in your organization. For manager and employee self service use of Delegation, the main component used may be found at

Main Menu > Self Service > Manage Delegation

. The Manage Delegation menu is available at the Employee Self Service level because employees (non-managers) may need access to this component to serve as a proxy and manage delegation requests they have received.

Question # 10: Can an inactive employee create a delegation request?

Answer: No. However, if the employee has multiple jobs and one of them is inactive and the other is active, the employee can still create delegation requests. Delegation uses user profiles which are created at the Employee ID level, not the Employee Record level.

Question # 11: Can a proxy initiate a transaction on behalf of him/herself?

Answer: No. In fact, when a proxy logs into the application to initiate a transaction on behalf of his/her manager (delegator), he/she will not be able to select his/her own name to process. This is by design

Question # 12: Can a manager use the Delegation self service UI to select an indirect report as a proxy?

Answer: No. For any hierarchy chosen, the system will only drill up or down one level and return a set of employees. For example, the system will not show indirect reports or people above the user’s direct manager. This is by design to avoid circular delegation.

Question # 13: What is the intended purpose of the Delegation Administrator role?

Answer: At least one person in your organization should be designated a Delegation Administrator. The Delegation Administrator monitors delegation requests and can quickly troubleshoot any requests that have been sitting in someone’s queue for too long. He/she may also create delegation requests on behalf of employees or managers who are absent and do not have access to the application for reasons beyond their control. He/she may also be responsible for reacting to proxies who become inactive or ineligible for whatever reason. It is not intended for the Delegation Administrator to approve each delegation request that is sent.

Question # 14: Can a proxy revoke an already accepted delegation request using the application’s self service UI?

Answer: No. Only the delegator can revoke an accepted delegation request using the application’s self service UI. If a proxy can no longer serve his/her delegator, he/she must contact the delegator and ask him/her to revoke the request If the delegator is no longer available, then the Delegation Administrator can handle revoking the request.

Question #15 : Can a manager assign multiple individuals as a proxy.

Answer: Yes. Each user can assign multiple people as a proxy and each proxy can have one or more transactions delegated to them. For example, as a manager I can delegate direct report Joe as my proxy for ePerformance transactions but delegate Nancy as my proxy for eProfile transactions. However, I cannot delegate the same transaction to more than one proxy.

Question #16 : Can an individual be a proxy for one or more managers?

Answer: Yes. We provide a self service page that provides the proxy with all the information pertinent to their responsibilities (delegation authorities).

Question #17: Can a manager delegate to one or all of his or her departments by role? Answer:

Delegation does not allow you to configure which departments may delegate and by which role. You can however configure which persons a manager may choose from to serve as his/her proxy.


XML Publisher - Performance improvement

Customers using functionality that does a lot of processing in Java (for example, XMLPublisher) should consider setting the JVM options for the application server. The default JVM options may not be optimal. In that case, we recommend adding the following setting to psappsrv.cfg or psprcs.cfg (in addition to the already existing options):
-server -Xms128m -Xmx512m



The benefits of PSAESRV versus PSAE are a popular topic of discussion. Our studies have shown that PSAE is as good as
PSAESRV for most practical purposes.
If you have an application engine job that runs longer than 10 seconds, PSAE is equivalent to PSAESRV. PSAE has the added
advantage of being recycled at the end of each application engine job, cleaning up any outstanding SQL cursors to the database
that may have been left behind. Because PSAE recycles after each use, PSAE does not have any possible memory leakage
problem that may occupy the precious system memory. In short, PSAE is a cleaner workhorse.
To shutdown PSAESRV, when you configure the Process Scheduler, you can change the default of the PSAESRV instance to 0.
Values for config section - PSAESRV
Max Instances =0
Recycle Count=1000
Allowed Consec Service Failures=2


Peoplesoft process run status

Here's a summary of the run status translates (from PeopleTools 8.49). Note that not all of these are active.
Value Status
1 Cancel
2 Delete
3 Error
4 Hold
5 Queued
6 Initiated
7 Processing
8 Cancelled
9 Success
10 Not Successful
11 Posted
12 Unable to Post
13 resend
14 Posting
15 Content Generated
16 Pending
17 Success with Warning
18 Blocked
19 Restart