Impact of U.S. Daylight Saving Time Changes in 2007 on peoplesoft

US DST changes may require updating the JRE used in Web/App/Batch servers. More information can be found in these links

http://java.sun.com/developer/technicalArticles/In...

http://www.hp.com/products1/unix/java/DST-US.html

Do you think it will also impact peopletools release as well. I do not see any documents on this on customer connection. Please share your thoughts on this issue.

I think this PeopleSoft Page and associated data stored in PSTIMEZONE and PSDSTTIME must be updated. I have seen one other record PSTZOFFSET which may need to be updated, if you are using this in your environment. The data in this table is not required by peoplesoft and can be used in query to simplify the access to timezone data. This makes the time zone information available in a format that can be easily accessed with SQL. (Exception : May be used by Time and Labor. Check your installation). You may also want to update only for the period 2007 and onwards after applying the updated timezone information.

PeopleTools -> Utilities -> International -> TimeZones and Hit the button Generate Query Offsets and enter the start and end date for which you want to generate the information. This will delete the old data and enter the new data. You may want to update the data only for the year 2007 onwards only.

Here is a link to peoplebooks -> Unserstanding Time Zones

Navigation for PeopleTools 8.4x

PeopleTools -> Utilities -> International -> Time zones
Menu: Utilities
Component: TIMEZONEPNLGRP
Page: TIMEZONEDATA, DSTDATA
Record: PSTIMEZONE, PSDSTTIME

Here is the SQL to update the record.

INSERT INTO PSDSTTIME VALUES ( '2FirstSunNov', 'N', '11', 1, '0', 2, 0, 'First Sunday in Nov, 2:00am' )
INSERT INTO PSDSTTIME VALUES ( '22ndSunMar', 'N', '3', 2, '0', 2, 0, 'Second Sunday in March, 2:00am' )
UPDATE PSTIMEZONE SET DSTSTART='22ndSunMar' WHERE TIMEZONE IN ('AKST','CST','EST','MST','PST');
UPDATE PSTIMEZONE SET DSTEND='2FirstSunNov' WHERE TIMEZONE IN ('AKST','CST','EST','MST','PST');

Define Optional Query Prompt/Criteria in PeopleSoft Query

To create a optional query criteria, in Peoplesoft Query create a prompt as expression as shown below
:1 OR :1 = ' '
Note their is a single space between two quotes. This will make query run with or without prompt. User can either provide the prompt value to return results for a specific value or leave it blank to return rows for all values.

Execute query from Lefthand Portal Navigation

You can run PeopleSoft Query from Lefthand Portal Navigation. This helps the end user to navigate to remember the query name easily.

Go to Portal -> Structure and Content

Navigate to  the folder under which you want to create the content reference.

Add a new content reference and fill following fields as follows

Check No Template check box. This will remove the portal Header and Left hand menu navigation.

URL information

Node Name : Always use Local or appropriate remote node name

URL Type : PeopleSoft Generic URL

Portal URL : q/?ICAction=ICQryNameURL=PUBLIC.YOUR_QUERY_NAME

Content Reference Attributes

Name: NAVNEWWIN

Uncheck Translate check box.

Attribute value: true

This will open the query results in a new window.

Go to Security Tab and add appropriate permission list and save the content reference.

You may have to refresh the homepage to be able to see this new portal content reference in Left hand  Navigation menu.

This is applicable for PeopleTools 8.4x only.

Target Operator ID has 'No Access' to Upgrade. (62,14)

when you try to copy a project from one database to anonther, you get a message Target Operator ID has 'No Access' to Upgrade. (62,14). This is despite you have correct permission list assigned to the userid in target database. This is due to bug in PeopleTools and is fixed in 8.46. Here is a workaround. Run this query in your target database.

SELECT * FROM PSAUTHITEM WHERE CLASSID IN
(SELECT OPRCLASS FROM PSOPRCLS WHERE OPRID='xxxxx') AND
MENUNAME='APPLICATION_DESIGNER' AND BARNAME='UPGRADE'

The operator class or permission list returned by very first row of query results, must have access to upgrade for that user. (AUTHORIZEDACTIONS = 4 for MENUNAME = APPLICATION_DESIGNER and BARNAME = UPGRADE).

Open Permission List, Go to PeopleTools Tab. Select Tools Permissions Link and Asign Full Access for Upgrade (at the bottom). Generally permission list PTPT1200 and Role PeopleTools has access to copy the project to target database.

Reset your PeopleSoft Password or AccessID Password

Many times you may get a request from user to reset his password and you can not login to PeopleSoft Web App to do that. Here is a way to reset the password using your database SQL utility. This assumes that you can login to your database using valid Peoplesoft db account or superuser account.

 

This resets the password = oprid

update psoprdefn
set operpswd = oprid,
encrypted = 0
where oprid = any_oprid;

Login to data mover (bootstrap mode or regular mode)
and run encrypt_password oprid;

2. For some reason, you login to Appdesigner and it gives following error message

SQL error. Stmt #: 2 Error Position: 0 Return: 404 - ORA-01017: invalid username/password; logon denied;

This indicated that your database password and password stroed in PSACCESSPRFL (Encrypted format in accesspswd) are not in sync.
Run the following command in your database SQL Utility

update PSACCESSPRFL
set accessid = 'peoplesoft_schema_id',
accesspswd = 'current_password',
encrypted = 0
where symbolicid = <your symbolic id>

Login to App designer and it will let you login again and also encrypt the password in PSACCESSPRFL

Another Application Designer is the Debugger. (143,7) error

If you are getting this error Another Application Designer is the Debugger. (143,7) error then try the following

Restart the application server after clearing the cache.

Crystal Report - Sub Report Unhandled Exception

If you are using sub reports in crystal Report and you want to suppress them, You must insert each sub report in a new section and suppress the section using the formula instead of suppressing the sub report directly. Otherwise it results in Unhandled exception error. This happens if the there are no rows returned by sub report for the last row of the main query. Assuming these sub reports are linked.