PeopleCode Properties???

Sometime back, I had this question from my team mentioning – How do we determine when and who had customized this particular Record PeopleCode? The compare report showed that the PeopleCode was customized but there were no comments (bad practice!) in the code to show who touched it last.
In Application Designer the properties button is grayed out when you open the peoplecode. Also, the properties at the record level will not answer this question. Here is the SQL you can use to determine who last updated the code and when.

SELECT A.OBJECTVALUE1 RECORD, A.OBJECTVALUE2 FIELD, A.OBJECTVALUE3 EVENT, TO_CHAR(A.LASTUPDDTTM,’YYYY-MM-DD-

HH24.MI.SS.”000000″‘),

A.LASTUPDOPRID

FROM PSPCMPROG A

WHERE A.OBJECTVALUE1 = ‘&RECNAME’

AND OBJECTVALUE2 = ‘&FIELDNAME’

AND UPPER(OBJECTVALUE3) = UPPER(‘&EVENTNAME’)

/

RECORD FIELD EVENT TO_CHAR(A.LASTUPDDTTM,’YYY LASTUPDOPRID

——— ————— ——— ————————– ————

VOUCHER BUSINESS_UNIT RowInit 2006-11-13-18.25.23.000000 PPLSOFT

VOUCHER BUSINESS_UNIT RowInit 2006-11-13-18.25.23.000000 PPLSOFT

Read More about PeopleCode Properties

Good Practice for executing PSBUILD scripts

I have had change control call me several times in the past to restore a table because it was accidentally dropped when executing the SQL script generated using Application Designer. Whenever you use Application Designer to generate a script with “Alter by Table Rename” option checked, the script will have the following SQL’s

– Start the Transaction

– Create temporary table

– Copy from source to temp table

– CAUTION: Drop Original Table

– Rename Table

– Done

The risk of running this script As-Is is that if any of the above SQL encounters an error then the script will still proceed to run the next SQL in the script. So if there is an error while running any SQL prior to dropping the original table then we would have lost the table and all the data.

Hence the best practice for running any scripts created using Application Designer is to include ‘WHENEVER SQLERROR EXIT’ at the beginning of the script. This will ensure that the script will abort anytime there is an error. Making this part of our Change Control checklist has ensured that there is no reoccurrence of this issue.
Note:

Scripts generated using Change Assistant automatically have ‘whenever sqlerror exit’ at the beginning of the script.

Read More about  PSBUILD Scripts

Not able to view record in PeopleSoft Query Manager!!

Sometime back, I was approached with a request from a developer who had created a new record in Application Designer but was not able to view this record in Query Manager. So in this post, I will demonstrate the steps required to view a new or existing record in Query Manager. Below steps are from Tools version 8.47.02.

1. New record HX_TEST has been created and we would like to use it in our PS Query.
2. Navigate to PeopleTools > Security > Query Security > Query Access Manager
3. Search for the Tree which should have access to this record.

1. Click on the hyperlink and add the record HX_TEST

1. Open the appropriate Permission List which has access to HX_TEST_TREE and click on the Query tab

1. Click on Access Group Permissions

1. Verify the access

1. Open PeopleSoft Query Manager and you should have access to this new record.

 

Note that this activity is the realm of PeopleSoft Security Administrator since it needs careful analysis of the question