13th mass change for dummies

8/13/2019 13th Mass Change for Dummies

1/41


2/41

ROSS LEISTEN

Enterprise Business Systems Coordinator

Salisbury University

Provide inter-departmental analytical support for

all Student Administration areas

Liaison between end users and developers

Provide end user training for University staff,

faculty and students


3/41

SALISBURY UNIVERSITY

University System of Maryland affiliate located onMarylands Eastern Shore

4 academic schools housing 43 undergraduate/5post baccalaureate certificate/13 graduate

programsApproximately 8,000 student, 1,500 faculty and

staff

SU implemented PS HRSA and Financials v8beginning with HR and Admissions in 2002,finishing with CR in 2004.

SU currently uses Financials v8.9 and CS andHRMS v9. Financials upgrade occurred during the

Summer of 2006. CS and HRMS upgrades


4/41

RUMORS AND REALITIES

Rumors

Mass Change is going away!

Realities

Oracle has no timeline or plan for itsdiscontinuation

Similar to Query Manager, Mass Change is a

powerful tool for generating sql code andinteracting directly with the Oracle/PeopleSofttables. Mass Change can be used with otherdelivered engine processes or by itself


5/41

MASS CHANGE FOR DUMMIES

Just the Basics

This presentation covers only a very basic

introduction to Mass Change, why you might

want to consider using it, its component

pieces, setup and operation. The focus is on

two simple from scratch examples (no

delivered scripts, no groups, no complex joinconditions or operations, etc.).


6/41

BENEFITS

Mass Change processes

can be used in place of invasive system

modifications or projects

can be used to change or correct one or

many table values online and without the

use of behind the scene sql scripts

require little or no attention during patches

and fixes installations, and/or upgrades


7/41

ISSUES

Mass Change process

missteps can be deadly, especially for trigger-happy users

settings/runs involve several page and tabnavigations

settings are not validated

results must be validated by query (nocompanion reports)


8/41


9/41

ALWAYS DO THE OBVIOUS

Preliminary Research - should any othertable changes be made as a direct result

Trial Build - use a test environment for the

initial process build

Test - both the process and any/all online

processing that depends upon the changes

Involve a Developer - for research and build

Move/Copy To Productionwhen the

process is perfect


10/41

BUILDING BLOCKS

Types - define records andactions

Templates - define selectionfields

Permission List Security Definitionsdefine

selection criteria

Prompt Recordsmost

closely associated withDefinitions

Groupsone or moreDefinitions


11/41

PROBLEM SOLUTION #1

SU instructors grade online - graded rosters

are approved by instructors, posted by

Registrars office SU schedule of classes build is decentralized

across more than 20 academic departments

where Instructor Access is not always codedwith a consistent Approve


12/41

GRADE ROSTER ACCESS

Set Instructor Access to Approve


13/41

MASS CHANGE TYPE

Main Menu > PeopleTools > Mass Changes > Types


14/41

MASS CHANGE TYPE

Define Records/Tables and Actions


15/41

MASS CHANGE TYPE

Define Actions/add custom SQL


16/41

MASS CHANGE TEMPLATE

Main Menu > PeopleTools > Mass Changes > Templates


17/41


Select/define Criteria


18/41

MASS CHANGE SECURITY

Add Template to Users Perm List

Main Menu > PeopleTools > Security > Permissions and Roles > Permission

Lists


19/41

MASS CHANGE DEFINITION

Main Menu > PeopleTools > Mass Changes > Definitions


20/41


21/41


Generate SQL


22/41

PROMPT RECORDS

Define/link Prompt Records

Main Menu > PeopleTools > Mass Changes > Prompt Records


23/41

TRANSLATE VALUES

Main Menu > PeopleTools > Administration > Translate Values

Values defined within the translate table willautomatically become visible in the Translate

Mass Change View (XLAT_MC_VW)


24/41

RUN MASS CHANGE

Main Menu > PeopleTools > Mass Changes > Process Mass Change


25/41

GRADE ROSTER ACCESS


26/41

PROBLEM SOLUTION #2

SU frequently uses Student Groups for mass

transcript generation and enrollment

appointment purposes

After use, Student Group data is considered

useless

Although CS delivers a mechanism for

inactivating Student Group members inmass, no process for removing members

exists


27/41

STUDENT GROUPS


28/41

MASS CHANGE TYPE


29/41


30/41

MASS CHANGE TYPE


31/41



32/41



33/41



34/41



35/41



36/41

PROMPT RECORDS


37/41


38/41

STUDENT GROUP TABLE


39/41

RUN MASS CHANGE


40/41

STUDENT GROUPS


41/41

13th mass change for dummies

Documents