SQR/SQC Modification Documentation

Modification standards have varied over time. This file documents what the current standard is. While it is desirable to have all changes within a file documented consistently, it is realized that to implement the current standard for previously submitted changes can create a substantial amount of additional work for the developer. It is at the developer’s discretion as to whether or not they retrofit the SQR to have previous changes conform to the current standard. If a developer decides to retrofit the file, they should remove all references to changes made prior to the implementation of the current version of PeopleSoft (currently 9.0 for HCM [May 2011]).

During code review, the SQR is looked at to determine if all the changes are documented and if the documentation conforms to the current standard.

Current Standard

Changes to an existing file should be documented in the Maintenance History section of the file. Each documented modification should be referenced by the date and modification number for that date in the format YYYYMMDD-##. The initials of the developer making the change should follow the modification date-number. Finally a clear description of the change should follow the developer’s initials. Each modification number should pertain to a single change. That change may cause updates to different lines throughout the file all referencing the same modification number. Other changes that are either significantly different than or unrelated to the other changes should receive their own modification number.

Adding, Deleting, or Changing Lines of Code

Comments relating to each change should be reflected on the line that the change is made, right justified as follows:

!20080531-01

Adding Procedures

When a procedure is added it is not necessary to add the modification date-number to each line added. The addition of a procedure will be referenced with the modification date-number right justified on the same line as the “Begin-Procedure …” code block as follows:

!======

Begin-Procedure Lookup-ID !20080531-02

!======

SQR FOM Deadlines

FOMs are performed daily as needed. FOMs occur in the afternoon. The exact timing of the FOM is based on the date/time needed as specified in the request. All FOMs that have all approvals by noon will be performed that same afternoon. If a request does not have all approvals by noon, but still needs to be moved on the same day, the word “EXPEDITE” is to be included in the subject line of the request. For expedited requests, after all approvals are received, the FOM will occur on the same day, the exact timing to be determined based on the date/time needed as specified in the request.

SQR FOM Submission Process Flow

After an SQR is validated and ready to move into PRD, the developer should change the name of the SQR in the Campus Repository directory (T:\pstech\Developers\CampusProduction\CS_9.0\cmp_sqr) by adding the version number to the filename in the form of .###. For instance, if the file being submitted is the first revision to the file, the current file in the Campus Repository should be renamed from example.sqr to example.001.sqr. Then the new file should be moved into both the Campus Repository and the 2FOM directory (T:\pstech\Developers\2FOM).

An email should be sent ,, and the functional and technical approver for the SQR.

The email subject must include the following:

  • “SQRFOM Request” – text describing the request
  • “EXPEDITE” – this is optional. Include if the request approvals are not received by noon but the FOM must still occur on the same day.
  • DEVELOPER – the responsible developer’s Bronco Name (part of their email before @csupomona.edu)
  • YYYY/MM/DD – The date the submission is made
  • #N – The submission number for the day. Will only be greater than 1 if the developer has multiple submissions on the same day.

The email body must include the following:

  • FUNCTIONAL MANAGER – The functional manager for the area the SQR was developed/modified for.
  • TECH – The technical person whose responsible for approving the SQR.
  • DATE/TIME NEEDED By – The date and time that the move needs to be completed by.
  • REQUEST TEXT – Request of what is to be done
  • DESCRIPTION – Description of the process or change to the process
  • VALIDATION – statement that testing was completed. This statement should include the instance where the testing occurred and the names of the people who performed the testing.
  • PATH – The path to the location where the file to be moved resides.

The following email example is not a standard, but the email must include all of the same information presented in a clear manner:

Subject: SQRFOM Request - DEVELOPER FOR 2008/07/07 #1

Body:

NAME, please provide functional approval.

NAME, please provide technical approval.

This request needs to be completed by 7/7/2008 at 5:30pm so that it is in place when the next scheduled execution of the process occurs.

Please move the following SQR to HPOMPRD during the next FOM window.

This update adds criteria to the STRM admin function specific query that

pulls info about the recipient. It does not affect any other Admin Function.

The change links the Plan to the Plan table to pull only those that are

PLAN_TYPE = 'MAJ'

This has been tested by NAME in INSTANCE.

T:\pstech\developers\2FOM\pomcc502.sqc

Maintenance History Documentation Example

!------

!

! Maintenance History

! ------

!

! Date Mod.# Initials Description

! ------

! 20080110-01 TJR Cloned POMCC501.SQR from HCM for Finance.

!

! 20080512-01 TJR Added Select-Parameters procedure to populate $ADMIN_FUNC

! before individual record processing begins.

!

! 20080303-02 TJR Added replace line to allow $oprid to be in the

! notification text.

!

!

! Notes

! -----

!

! Date Note# Initials Description

! ------

!

!

!------

Code Change Documentation Example

do Select-Parameters !20080512-01