Cerritos College

PeopleSoft Implementation

 

Customizations Naming Standards

 

 

1.       SQR Programs:

The SQR program name should follow the following format:

ZXXYNNN 

Z is a fixed character.

XX is the module two-character identification. Examples are:

CC for Campus Community

SR for Student Records

SF for Student Financials

AD for Admissions

FA for Financial Aid

HR for Human Resources

CR for Contributor Relations

FI for Financials

AA for Academic Advisement

Y is either “U” for Update for conversion, interfaces or any process which updates the

                       Database Or

                 “R” for Reports and processes which do not update the database

 NNN is a three-digit sequence number which matches the PDR number.

 The SQR name should match the process definition name in the process scheduler manager.

       The maximum number of characters allowed for the process definition name is 8.

       Example would be ZSRR001.sqr

2.       Process Definitions

 

The process definition name should follow the same naming standard as the SQR name.

 

The maximum number of characters allowed to be used in the process definition names is 8 characters.

 

Example would be ZSRR001as shown in the following screen shot.

 

Screen Shot in PeopleSoft

 

 

3.       Application Designer Objects:

 

·         Projects:

 

Project names should follow the following format:

 

1) CER_XXNNN_DESCR

 

Where XX is as defined above as the two letter module abbreviation

NNN is a three-digit sequence number that matches the PDR number.

DESCR is the project short description.

 

Example would be: CER_SR001_Transfer Evaluation Summary Report.

 

·         Fields

 

Field names should follow the following format: CER_Field_Descr where the Field_Descr is a short description of the new field.

 

o        Translate Values

If the new filed is a translate filed which will have new translate values, then the new translate values should be effective dated at “01/01/1901”.

 

The new translate value(s) should be added to the excel translate sheet and they should be inserted into the specific project.

 

 

·         Records

 

Records names should follow the following format: CER_XX_DESCR

Where XX is the module name as described above and DESCR is a short description of the object.

 

- Custom views should end with a “_VW” phrase.

 

- Custom search records should end with a “_SRCH” phrase.

 

- Work records should end with a “_WRK” phrase.

 

- Run Control Records should be CER_RUNCTL_XX_DESCR

 

When creating a new record; a tables pace should be assigned to that record upon creation. The tablespace assignment should be coordinated with the database administrator.

 

·         Pages and Components

 

Pages and Components should follow the following naming standard: CER_XX_DESCR

 

Where XX is the module name as described above and DESCR is a short description of the page or the component.

 

- Run Control Pages and Components should be CER_RUNCTL_XX_DESCR

 

  Reports or Processes Run control pages and components should match in names.

 

·         Menus

 

It is recommended to create a new menu for each functional area under the PeopleSoft Go (Home) menu.

 

The new menu names should follow this format: CER_XXLONG

Where XXLONG is the module full description and not the abbreviation:

For example:

 

CER_STUDENT_RECORDS

CER_STUDENT FINANCIALS

CER_FINANCIAL_AID

CER_HUMAN_RESOURCES

CER_FINANCIALS

 

The menu items names would be:

 

Cerritos Student Records

Cerritos Student Financials

Cerritos Financial Aid

Cerritos Human Resources

Cerritos Financials

 

Menus are NOT to be included in the upgrade projects as several developers may have items under development in the same menu and which are not yet ready to be migrated to the target database.

 

The new menu will look like this:

 

Screen Shot in PeopleSoft

                  

Screen Shot in PeopleSoft

 

                   

·         PeopleCode

 

When adding custom PeopleCode, make sure to place the proper documentation in the PeopleCode program to indicate the reason for customization and to help locate the new code easily during the upgrade process:

 

/* CCCDS. CER_SR001_Class Roster (Project name). */

/* By A.Omar on 06/02/03.                        */

/* Descr: Added one line of code to apply the    */

   /*        existing code to the custom component. */

 

4.       Objects outside the Application Designer:

 

·         Queries

Should follow the following format: CER_XXNNN__DESCR

Where XX is the module abbreviation, NNN is a sequence number and DESCR is a short description for the query.

Queries should be defined as Public Queries if intended to be used by users.

 

Database Agent Queries should follow this format: CER_DBAG_DESCR

Where DBAG is a database agent PeopleSoft delivered notation phrase.

 

·         Messages

When adding a new message in the message catalog, use a message set number of 25000 and then use the next message sequence number available with the appropriate message type (Message, Error, Warning or Cancel).

 

 

 

Placement of Custom Programs

 

It is recommended to create a new “CCCDS” folder under the current SQR folder for each PS Home (HDEV, HADM and HPRD). That folder would hold all custom SQR’s developed in house by Cerritos. The configuration manager should point to that folder as a first search path for SQR’s.  According to \\psdevweb\psoft$\legacy_data\PeopleSoft Development File Locations.doc document, the “CCCDS” folder path (UNC) is \\psdevapp\psoft$\pt819\sa801\sqr\CCCDS

 

Read/Write access to the above development CCCDS SQR folder should be given all developers to be able to move their SQR programs to that folder upon development completion.

 

Only Read access to the test CCCDS SQR folder would be given to developers once their programs are moved to the test file server area.