Archive for May, 2016


Shorthand keys on date field- PeopleSoft

Have you ever wondered how to get today’s date without selecting in People Soft

When we enter “T” or “t” on a date field, system will default to today’s date. This functionality has been coded at PT_EDITSCRIPT (HTML Object).

 

How to modify PeopleSoft Style Sheets?

Working on a People Soft style sheet is very challenging and interesting.

There might be several scenarios where in Companies want to have there own style sheets to represent there brand. People Soft provides limited choice to address most common styles.

PS Stylesheet can be created from scratch  or can even  be modified to reflect with our own styles.

To extend a default style sheet in PS , first we need to know details of stylesheet currently been used in our environment. It can be found from following location

PeopleTools >  Utilities  > Administration >  PeopleTools Options

You can then open the stylesheet object from Peoplesoft and add your custom style class to have your own effect in place.

Let me know your comments….Till then happy reading!.

 

 

To convert datetime to a formatted date time character in Oracle, we use TO_CHAR(Column,Format) function.

TO_CHAR (datetime) converts a datetime or interval value of DATE, TIMESTAMP, TIMESTAMP WITH TIME ZONE, or TIMESTAMP WITH LOCAL TIME ZONE datatype to a value of VARCHAR2 datatype in the format specified by the date format fmt. If you omit fmt, then date is converted to a VARCHAR2 value as follows:

  • DATE values are converted to values in the default date format.
  • TIMESTAMP and TIMESTAMP WITH LOCAL TIME ZONE values are converted to values in the default timestamp format.
  • TIMESTAMP WITH TIME ZONE values are converted to values in the default timestamp with time zone format.

SELECT  TO_CHAR(A.AUDIT_STAMP, ‘DD-MON-YYYY HH24:MI:SS’) FROM PSAUDIT A

PSAUDIT – SQL Issue

Problem Statement: While doing Field Level Audit in People Soft, we might come across below issue

“INSERT INTO PSAUDIT RESULTS IN SQL ERROR FOR VALUES LONGER THAN 65
CHARACTERS”

This issue does not exists in version 8.53 and above.

Solution:

Do impact analysis to find if PSAUDIT is been used across any modules.

Use App Designer to check the database for the use of PSAUDIT anywhere in metadata objects (Find Definition References) and SQL or peoplecode (Find In).
If PSAUDIT is not in the results, i.e. not being used at all, then the table can be dropped from the database (You will see a warning when running DDDAUDIT in the future on this though).

Vice versa, if you want to keep PSAUDIT and drop PSAUDITEXT, do the same above but search for PSAUDITEXT.

Starting in 8.52, PeopleTools internal code checks whether the tables exist before attempting to write to them, so there are no issues if one of them is
deleted.

Either way data exists in both records.
For reference, here is the actual data field definition difference between the two fields:

PSAUDITEXT
PTOLDVALUE VARCHAR2(254) NOT NULL Old Value
PTNEWVALUE VARCHAR2(254) NOT NULL New Value
PSAUDIT
OLDVALUE VARCHAR2(65) NOT NULL Old Value
NEWVALUE VARCHAR2(65) NOT NULL New Value