PS Object Types

PeopleSoft stores object definitions types such as Record, Field and SQL definitions as numbers in PeopleTools meta-tables. Here is a list of what each number means with respect to its definition.

Definitions for Record Object Types

The following are stored on the PSRECDEFN table on RECTYPE field.
RECTYPE = 0
Corresponds to: SQL Table
Comments: The record will be built as an actuall database table.

RECTYPE = 1
Corresponds to: SQL View
Comments: The record will be built as an actuall database view.

RECTYPE = 2
Corresponds to: Derived/Work Record
Comments: This type of record provides a working storage in the component. This is NOT a database object.

RECTYPE = 3
Corresponds to: SubRecord
Comments: SubRecords are used to group fields together or other subrecords. Subrecords are added to records and they are not database objects.

RECTYPE = 5
Corresponds to: Dynamic View
Comments: Does not correspond to a database object. A dynamic view is an SQL executed by PeopleTools.

Definitions for Field Object Types

The following are stored on PSDBFIELD table on the FIELDTYPE field.
FIELDTYPE = 0
Data Type: Character

FIELDTYPE = 1
Data Type: Long Character

FIELDTYPE = 2
Data Type: Number

FIELDTYPE = 3
Data Type: Signed Number

FIELDTYPE = 4
Data Type: Date

FIELDTYPE = 5
Data Type: Time

FIELDTYPE = 6
Data Type: Date Time

FIELDTYPE = 8
Data Type: Image

FIELDTYPE = 9
Data Type: Image Refrence

Definitions for SQL Object Types

The following are stored on PSSQLDEFN on SQLTYPE field.
SQLTYPE = 0
Data Type: Stand alone SQL objects

SQLTYPE = 1
Data Type: Application engine step

SQLTYPE = 2
Data Type: SQL belongs to a view

SQLTYPE = 5
Data Type: These are querries for DDDAUDIT and SYSAUDIT (very interesting SQLs)

SQLTYPE = 6
Data Type: Application engine XML definition.

Pages, components, menus and other PeopleSoft objects are also stored as numbers in PSPROJECTITEM table (stores PeopleTools project objects).

If you ever queried PSPROJECTITEM table (stores PeopleTools project objects) then you have definitely noticed that object types are stored as a number and not with their names. For example, if you have a project with a component then your component on this table will be stored as object type number 7.

So, what are other object types stored as (Pages, Record PeopleCode, Menus....)? Well, the list below is your answer. Please don't hesitate to post a comment and "correct" me if I messed up somewhere while mapping numbers to names!

0 = 'Record'
1 = 'Index'
2 = 'Field'
3 = 'Field Format'
4 = 'Translate Value'
5 = 'Pages'
6 = 'Menus'
7 = 'Components'
8 = 'Record PeopleCode'
9 = 'Menu PeopleCode'
10 = 'Query'
11 = 'Tree Structures'
12 = 'Trees'
13 = 'Access group'
14 = 'Color'
15 = 'Style'
16 = 'N/A'
17 = 'Business process'
18 = 'Activity'
19 = 'Role'
20 = 'Process Definition'
21 = 'Server Definition'
22 = 'Process Type Definition'
23 = 'Job Definitions'
24 = 'Recurrence Definition'
25 = 'Message Catalog'
26 = 'Dimension'
27 = 'Cube Definitions'
28 = 'Cube Instance Definitions'
29 = 'Business Interlink'
30 = 'SQL'
31 = 'File Layout Definition'
32 = 'Component Interfaces'
33 = 'AE program'
34 = 'AE section'
35 = 'Message Node'
36 = 'Message Channel'
37 = 'Message'
38 = 'Approval rule set'
39 = 'Message PeopleCode'
40 = 'Subscription PeopleCode'
41 = 'N/A'
42 = 'Component Interface PeopleCode'
43 = 'AE PeopleCode'
44 = 'Page PeopleCode'
45 = 'Page Field PeopleCode'
46 = 'Component PeopleCode'
47 = 'Component Record PeopleCode'
48 = 'Component Rec Fld PeopleCode'
49 = 'Image'
50 = 'Style sheet'
51 = 'HTML'
52 = 'Not used'
53 = 'Permission List'
54 = 'Portal Registry Definitions'
55 = 'Portal Registry Structures'
56 = 'URL Definitions'
57 = 'Application Packages'
58 = 'Application Package Peoplecode'
59 = 'Portal Registry User Homepage'
60 = 'Problem Type'
61 = 'Archive Templates'
62 = 'XSLT'
63 = 'Portal Registry User Favorite'
64 = 'Mobile Page'
65 = 'Relationships'
66 = 'Component Interface Property Peoplecode'
67 = 'Optimization Models'
68 = 'File References'
69 = 'File Type Codes'
70 = 'Archive Object Definitions'
71 = 'Archive Templates (Type 2)'
72 = 'Diagnostic Plug In'
73 = 'Analytic Model'

Other useful upgrade action flags
Here are the values for the upgrade action field UPGRADEACTION:
CASE UPGRADEACTION
        WHEN 0 THEN 'Upgrade Action is Copy'
        WHEN 1 THEN 'Upgrade Action is Delete'
        WHEN 2 THEN 'Upgrade Action is None'
        WHEN 3 THEN 'Upgrade Action is CopyProp'
        ELSE UPGRADEACTION
END CASE

And here are the values for the Source status and Target status fields.
CASE SOURCESTATUS
        WHEN 0 THEN 'Unknown'
        WHEN 1 THEN 'Absent'
        WHEN 2 THEN 'Changed'
        WHEN 3 THEN 'Unchanged'
        WHEN 4 THEN '*Changed'
        WHEN 5 THEN '*Unchanged'
        WHEN 6 THEN 'Same'
        ELSE SOURCESTATUS
END CASE
-- TARGETSTATUS values are the save as above

No comments:

Post a Comment