GenerateComponentContentURL / GenerateComponentPortalURL return NULL / Blank

PeopleTools > Portal > Node Definitions

The Base URI (e.g. http://www.myserver.com/psp/mysite/) is only available automatically in the context of a web server. If a process is not signed in via the web (e.g. Application Engine), the Node definition specified in the function is checked for that Base URI. Open the Node Definition (PeopleTools > Portal > Node Definitions) and enter the Content URI (.../psc/...) and Portal URI (.../psp/...) on the Portal page. These are used by the GenerateComponentContentURL and GenerateComponentPortalURL functions, respectively. By default these fields are empty.

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.

SELECT DISTINCT r.recname
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




Introduction to peoplesoft



Component Interface Training Video



Peoplesoft 8



Starting with peoplesoft Application Desinger

How Peoplesoft Better than SAP - Why Peoplesoft ?

Peoplesoft (Oracle) VS SAP
Why Peoplesoft ?

A Comprehensive Study of the Costs and Benefits of PeopleSoft Enterprise Versus SAP

Weighing Your Options for Human Capital Management

A Brief Cost and Benefit Overview for SAP Customers

Choosing the Best Human Capital Management Suite

Books for Peoplesoft Applications

PeopleSoft HRMS Reporting by Adam T. Bromwich

PeopleSoft for the Oracle DBA (Oaktable Press) By David Kurtz

PeopleSoft Developer's Guide for PeopleTools and PeopleCode By Judi Doolittle - Oracle publication

The Expert Guide to PeopleSoft Security By Jason Carter

PeopleSoft Integration Tools By Stewart Miller

Developing with PeopleSoft's Application Engine 8 By Joseph Weessies, Steve Bollinger

Peoplesoft HRMS Interview Questions, Answers, and Explanations: Peoplesoft HRMS FAQ
By Galina Landres, Vlad Landers, Vlad Landres

Essential Guide to PeopleSoft Development and Customization
By Tony Delia, Galina Landres, Prakash Sankaran, Isidor Rivera

PeopleSoft 8.4 Developer's Sheet By Joseph Weessies

Advanced Tips and Techniques for PeopleSoft Application Engine 8 By Joseph Weessies

Sams Teach Yourself Peoplesoft in 10 Minutes By Timothy Buchanan

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
PeopleCode.
• 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.