Demystifying PSPROJECTITEM – Part 1

As a DBA, I do not always trust Application Designer when it comes to following tasks.

• Merging projects – typical example is migration of 2 or more bundles using a merged project.
• Quickly changing the update flags based on KEEP/DROP decisions on a huge project
• Any other manipulations

Interpreting Data in PSPROJECTITEM can help you get one step closer to sailing through some of the above mentioned problems.
The following columns provided me with significant information to understand the data in PSPROJECTITEM table.

Column Name

PROJECTNAME

OBJECTTYPE

OBJECTVALUE1

OBJECTVALUE2

OBJECTVALUE3

OBJECTVALUE4

SOURCESTATUS

TARGETSTATUS

UPGRADEACTION

TAKEACTION

COPYDONE

The translation for OBJECTTYPE, SOURCESTATUS, TARGETSTATUS, and UPGRADEACTION are not present in the PeopleSoft database (unlike application translates which are available in PSXLATITEM). The translation for these columns exists in delivered upg.sqc.

In my next post, I will share with you a technique I use to quickly decode the data instead of having to refer back to upg.sqc.