Table of Contents
1. DOCUMEN !E"#E$...........................................................................................................................................% &. #N !ODUC #ON....................................................................................................................................................' %. PEOP(ESO) EN"#!ONMEN S.........................................................................................................................* '. NAM#N+ CON"EN #ONS..................................................................................................................................1, -. O!AC(E................................................................................................................................................................1* *. PA CHES. UP+!ADES. AND CUS OM#/A #ON..........................................................................................10 0. SO) $A!E 1UA(# 2 ASSU!ANCE...............................................................................................................&1 3. P!O+!AMM#N+ S ANDA!DS........................................................................................................................%% 4. APP(#CA #ON ES #N+....................................................................................................................................*' 1,. P!O5EC S ANDA!DS....................................................................................................................................0% 11. SECU!# 2..........................................................................................................................................................04 1&. DOCUMEN A #ON...........................................................................................................................................33 1%. PE!#OD#C !E"#E$.........................................................................................................................................1,, 1'. !EADE!6S COMMEN S.................................................................................................................................1,1 APPEND#7 A8 Modification (o9............................................................................................................................1,& APPEND#7 : ; +lossary.........................................................................................................................................1,% APPEND#7 C ; A<<reviations................................................................................................................................1,% APPEND#7 D C=stomer Connection !oadmaps and Sc>ed=les.........................................................................1,4 APPEND#7 E C=stomer Connection Updates and )i?es.....................................................................................11& APPEND#7 ) C=stomer Connection )ilin9 Cases...............................................................................................11' APPEND#7 + ;; People:oo@s................................................................................................................................11* APPEND#7 H !eport )ormat...............................................................................................................................114
"ersion 0.1
1. DOCUMENT RE !E"
1.1 AC#NO"$ED%EMENTS
Doc=ment !evieA <e9an on 4B&,B,0 and Aas completed on CCCCCCCCCCCC. !evieA eam8 PeopleSoft )inance Mi@e C>an9 PeopleSoft H!MS Mi@e (ovelady PeopleSoft St=dent Meredit> (a+rone Portal D Sec=rity S=sie $inters D:A D System Administration +race A. Davila
C>apterBSection 1. Doc=ment !evieA &. #ntrod=ction %. PeopleSoft Environments '. Namin9 Conventions -. Oracle *. Patc>es. Up9rades. and C=stomiEation 0. SoftAare 1=ality Ass=rance
3. Pro9rammin9 Standards 4. Application estin9 1,. ProFect Standards 11. Sec=rity 1&. Doc=mentation 1%. Periodic !evieA 1'. !eaders Comments Appendi?
Assi9ned o Mi@e (ovelady Mi@e (ovelady +race A. Davila All +race A. Davila +race A. Davila Mi@e (ovelady. Mi@e C>an9. Meredit> (a+rone. +race A. Davila Mi@e (ovelady. Mi@e C>an9. Meredit> (a+rone Mi@e (ovelady. Mi@e C>an9. Meredit> (a+rone Mi@e (ovelady S=sie $inters Mi@e (ovelady. Mi@e C>an9. Meredit> (a+rone Mi@e (ovelady Mi@e (ovelady All
Approved 2 2 2 2 2 2 2
2 2 2 2 2
&B0B,3 &B1'B,3
2 2
"ersion 0.1
Pa9e % of 114
&. !NTRODUCT!ON
&.1 '!STOR(
On Sep. 1. &,,1. University of Ho=ston System implemented PeopleSoft Applications for )inance. H=man !eso=rces. and St=dent Administration. )inance and H=man !eso=rces applications Aere distri<=ted to all components. St=dent Administration Aas implemented at t>e University of Ho=ston at Clear (a@e only. #n t>e fall of &,,%. t>e first Application Development Standards doc=ment Aas developed and distri<=ted to PeopleSoft application developers and D:As. Sessions Aere >eld Ait> <ot> 9ro=ps to acG=aint t>em Ait> t>e doc=ment and to reinforce t>e need to <e9in =sin9 t>ese standards for all f=t=re development. Efforts to retrofit previo=s development Aor@ to t>ese standards Aas not made d=e to <=d9etary constraints. As of April &&) &**+) E. S. application mana,ers and directors are responsible for ens-rin, t.at all f-t-re development complies /it. t.e standards contained /it.in t.is doc-ment. >is doc=ment represents t>e second release of Application Development Standards A>ic> Aas completed on Marc> 1%. &,,3.
&.1 AUD!ENCE
>ese standards are Aritten for University of Ho=ston System personnel developin9 or maintainin9 PeopleSoft and related softAare. >ese incl=de mana9ers. tec>nical specialists. application developers. and =sers >avin9 similar comp=ter responsi<ilities. >e reader is ass=med to <e tec>nically oriented and to >ave some e?pos=re to >i9>er; level lan9=a9es. data<ase mana9ement systems. and systems development of PeopleSoft administrative applications. >is Application Development Standards Doc=ment is availa<le on t>e Ae< at t>e folloAin9 U!( lin@. >ttp8BBAAA.=>.ed=Binfotec>Bp>pBtemplate.p>pHnonsvcCidI--0
&.& APP$!CA0!$!T(
>ese Application Development Standards are applica<le =ntil t>e Application Development Standards Committee specifies ot>erAise. >e Application Development Standards Committee is composed of application developers. mana9ers. andBor directors A>o are appointed to serve on t>e committee at t>e time of ann=al revieA.
&.1 PURPOSE
Standards define t>e 9eneral form of t>e softAare development environment. Standards serve as descriptive and instr=ctive patterns to folloA in order to ac>ieve t>e <est res=lts. and are criteria for meas=rin9 Aor@ G=ality. >e reasons for >avin9 standards incl=de t>e folloAin98 #nformation systems >ave developed into critical operatin9 and strate9ic reso=rces for s=ccessf=l commercial. 9overnment. and ed=cational instit=tions. >is means t>at >i9> G=ality control standards in comp=tin9 m=st prevail. C>an9es in comp=ter system >ardAare or neA softAare releases Aill >ave minimal ne9ative or9aniEational impact if pro9rams and proced=res are doc=mented and pro9rammers ad>ere to a familiar set of 9=idelines. StandardiEed proced=res and doc=mentation ena<le smoot> transition d=rin9 personnel c>an9es. NeA staff <e9ins prod=ctive Aor@ sooner if t>ey learn standard Aor@ proced=res and doc=mentation tec>niG=es. Pro9ram a=t>ors do not ta@e a system Ait> t>em A>en t>ey leave or are assi9ned to ot>er responsi<ilities. Understandin9 and en>ancin9 system f=nctions and proced=res are made m=c> easier t>ro=9> standard doc=mentation and comm=nication met>ods. )=rt>ermore. t>is =nderstandin9 is s>ared at all levels of mana9ement. =ser departments. proFect staffs and comp=ter operatin9 personnel. StandardiEed re=sa<le softAare components red=ce costs JreG=irements. desi9n. specification. codin9. testin9. and maintenanceK. increase application relia<ility. improve f=t=re maintenance efforts. and alloA personnel to concentrate on en>ancin9 applications and ot>er analysis Aor@. #nfle?i<le standards. >oAever. can <ecome a
"ersion 0.1
PeopleSoft Application Development Standards <arrier to meetin9 =ser needs ;; L$e canMt do t>at. #t doesnMt fit t>e Standards.L #nvo@in9 t>e standards as an e?c=se for not f=lfillin9 a reG=est is not accepta<le. Us=ally disc=ssion Ait> ot>er developers Aill reveal >oA t>e standards can meet =ser needs. #f a =serMs reG=est cannot <e accommodated <y c=rrent standards. t>en c>an9es to t>e standards s>o=ld <e considered. >e Standards Committee Aas esta<lis>ed to prepare. maintain. and revieA standards. >e folloAin9 proced=res >ave <een adopted8 All proposals for additions. deletions. or revisions to t>e Standards may <e s=<mitted to any mem<er of t>e Standards Committee. >e Standards Committee Aill revieA proposed c>an9es to t>e Standards. Aill Aor@ closely Ait> people affected <y t>e proposed c>an9es. and Aill s=<mit proposed c>an9es to t>e mana9ement team for final approval. >e Standards Committee c>airperson Aill <e responsi<le for ens=rin9 t>at Standards are p=<lis>ed and all concerned receive =pdates. Application developer teams Aill cond=ct revieAs of neA or e?istin9 systems. for ad>erence to standards. >e standards are 9=idelines for internally developed softAare only. A decision to =se e?ternally developed softAare is a decision not to comply Ait> standards. As s=c>. an effort to transform PeopleSoft to fit t>is standards doc=ment is not e?pected or realistic. >oAever. development and modification of PeopleSoft softAare m=st conform to t>ese standards.
&.2 EN3ORCEMENT
NOTE4 PeopleSoft Application mana,ers and directors and t.e D0A mana,er are responsible for t.e enforcement of t.ese standards.
"ersion 0.1
Pa9e - of 114
1. PEOP$ESO3T EN !RONMENTS
1.1 APP$!CAT!ONS
UHS p=rc>ased % applications as an enterprise Aide sol=tion for all camp=ses. >ese applications are PeopleSoft )inancials. PeopleSoft H=man Capital Mana9ement. JHCMK and PeopleSoft Camp=s Sol=tions JCSK. HCM and CS applications reside on t>e same data<ase and s>are ta<les Ait> eac> ot>er. PeopleSoft )inancials resides on a separate data<ase. Data feeds <etAeen HCMBCS to PeopleSoft )inancials are accomplis>ed t>ro=9> inte9ration <ro@er.
1.& DATA0ASES
>e Oracle data<ase environments listed <eloA are esta<lis>ed <ot> for )inancials and for HCMBCS. Eac> data<ase resides as a separate Oracle instance and is associated Ait> its oAn so=rce code tree. A>ic> is accessi<le via $indoAs E?plorer. !eference Section %.' for more information on so=rce code trees. >ere are m=ltiple data<ases =sed <y Enterprise Systems for development. testin9. trainin9. prod=ction. etc. namin9 convention is Prefi? N PeopleSoft version N environment. >e prefi? can <e8 )S )inancial Acco=ntin9 data<ase SA St=dent Academic and Administration data<ase N H! data<ase PA Portal Data<ase =sed to provide sin9le si9n;on to PeopleSoft applications UH C=stom Application Data<ase >e environment can <e8 CN" conversion data<ase DE" development data<ase DMO demo data<ase P!D prod=ction data<ase !P reportin9 data<ase S:7n sand<o? data<ase S test data<ase !N trainin9 data<ase UA =ser acceptance test data<ase UP+ release =p9rade data<ase DCn Date c>an9e data<ase (OAD (oad testin9 Data<ase >e
>e dia9ram of t>e prod=ction and development environments can <e fo=nd at8 Ess>areO on mis'=8PPeoplesoftPArc>itect=rePPSCEnvironments.vsd
"ersion 0.1
Pa9e * of 114
PeopleSoft Application Development Standards 1.&.1 Sandbo5 Environments >e Sand<o? data<ases are copies of t>e prod=ction data<ase. >ey provide special tro=<les>ootin9 for f=nctional and tec>nical staff. >e Sand<o? environments are not intended to <e development or trainin9 data<ases. D=rin9 t>e application patc>in9 process. one Sand<o? environment may <e @ept on t>e same patc> level as prod=ction. >e Sand<o? environment Aill <e =sed for emer9ency prod=ction s=pport. Data<ase lin@s to prod=ction environments are not 9enerally esta<lis>ed in t>e sand<o? environment. 63SnnS078 >e )SnnS:7 sand<o? data<ase is a copy of t>e financials )SP!D data<ase. 6SAnnS07n8 SAnnS:7n sand<o? data<ase is a copy of t>e st=dentB>=man reso=rces prod=ction data<ase. 6SAnnDC58 SAnnDC? alloAs t>e c>an9in9 of system date on t>e server for special date sensitive process testin9. 1.&.& Demo 63SnnDMO) SAnnDMO) SAnnDMOP8 >e demo data<ases are =sed <y t>e data<ase administrators to import patc>es and maintenance pac@s from PeopleSoft. A PeopleSoft demo data<ase is an application data<ase t>at does not contain any c=stomer JUHSK c=stomiEations or modifications. A Peoplesoft Comparison !eport is r=n a9ainst a UH c=stomiEed data<ase and t>e PS demo data<ase in order to identify t>e differences in PeopleSoft modified o<Fects. >e comparison reports do not identify differences <etAeen PeopleSoft e?ternals JS1!. S1C. Crystal. etc.K. After patc>es and =p9rade comparison reports are revieAed. t>e patc>es contin=e t>ro=9> t>e mi9ration pat> and are applied to t>e development data<ase. 1.&.1 Development 63SnnDE ) SAnnDE 8 >e development data<ase is A>ere application developers create c=stomiEations to t>e PeopleSoft application. $>en patc>es or maintenance pac@s are applied to t>e c=stomiEed PS application. developers are reG=ired to revieABreapply previo=s c=stomiEations to t>e affected o<Fects Ait>in t>e development data<ase. All modifications and patc>es m=st <e =nit tested <y t>e developer <efore mi9ratin9 t>e c>an9es to t>e ne?t data<ase. 1.&.2 Test 63SnnTST) SAnnTST8 >e test data<ase is A>ere f=nctional =sers test patc>es. maintenance pac@s. and c=stomiEations. >e test data<ase can also <e =sed for system testin9 and inte9ration testin9. Developers are not a=t>oriEed to ma@e c>an9es to t>e test environment. 1.&.9 Prod-ction 63SnnPRD) SAnnRD8 >e prod=ction data<ase is A>ere end =sers >ave a=t>oriEed access to t>e PeopleSoft application. Users are 9ranted access to maintain application data and processes. Developers do not >ave access to ma@e c>an9es in t>e prod=ction environment. PeopleSoft delivers a G=ery =tility Ait> t>eir prod=ct t>at can <e =sed <y anyone to G=ery data from t>e data<ase and A>o >as <een 9ranted 1=ery access. Developers may >ave read access to Oracle prod=ction data<ases. 1.&.: Reportin, Database 63SnnRPT) SAnnRPT8 >e reportin9 data<ase is refres>ed ni9>tly from t>e prod=ction data<ase. #t does not contain dynamic real;time data. >e reportin9 data<ase is read only and e?ists to provide s=pport for reportin9 and G=eryin9 of data and to red=ce t>e Aor@load on t>e prod=ction data<ase environment. 1.&.; Trainin, 63SnnTRN) SAnnTRN8 rainin9 data<ases are =sed for f=nctional and tec>nical trainin9. M=ltiple copies of a trainin9 master data<ase may <e created to accommodate a partic=lar class. rainin9 data<ases are refres>ed =pon reG=est. 1.&.+ Sta,in, Database 6D"STA%E8 >is is a standard Oracle data<ase and not part of t>e PeopleSoft application. >is data<ase can typically =sed as a sta9in9 data<ase for data conversion.
"ersion 0.1
Pa9e 0 of 114
1.&.< Conversion 63SnnCN ) SAnnCN 8 Conversion data<ases are =sed for conversion of le9acy data to PeopleSoft ta<les. (e9acy data may >ave <een stored in intermediate ta<les in D$S A+E. 1.&.1* Up,rade Database 63SnnUP%) SAnnUP%8 NeA application releases often reG=ire a parallel set of data<ases Jdemo. development. and testK to facilitate t>e =p9rade process and not conflict Ait> t>e e?istin9 development environments. 1.&.11 User Acceptance Test Database 6SAnn=AT) 3Snn=AT8 D=rin9 a maFor application =p9rade. a data<ase may <e desi9nated as t>e Qmaster6 tools PS application data<ase. Developers may need to mi9rate any revisions to 1A data<ase.
"ersion 0.1
Pa9e 3 of 114
"ersion 0.1
Pa9e 4 of 114
2.& PRE3!7ES
UHS developed PeopleSoft internal o<Fects s>all >ave t>e prefi? of RUHSS. Use an =nderscore c>aracter RCS folloAin9 t>e prefi? if space alloAs. UHS developed PeopleSoft e?ternal o<Fects JS1C. S1!. Crystal !eports. etc.K s>all >ave t>e prefi? of RUS.
2.1 SU33!7ES
S=ffi?es s>o=ld alAays <e preceded <y an =nderscore RCS. >e folloAin9 PeopleSoft standard s=ffi?es Aill <e =sed for field names8 AM Amo=ntT n=meric val=e of c=rrency type CD CodeT =ser defined val=e from t>e ranslate or ot>er ta<le CN Co=ntT n=meric val=e containin9 a constant D Date fieldT format DD;MMM;2222 D M Date; ime fieldT format DD;MMM;2222 and HH8MM8SS #D #dentificationT Je.9. emplid. deptidK PC PercentT stored as a decimal Ji.e. -,U I .-K ! !ateT a n=meric field e?pressin9 an amo=nt per =nit Je.9. payrateK M imeT format JHH8MM8SSK >e folloAin9 PeopleSoft standard s=ffi?es Aill <e =sed for records names8 AE Application En9ine State !ecords D"$ Dynamic "ieAT a record definition t>at is implemented <y definin9 a dynamic S1( vieA Jt>is @ind of vieA is not a p>ysical ta<leK. S:! S=<records S!CH Searc> "ieAT a vieA t>at is =sed to select specific records to <e displayed to t>e =ser on a searc> panel. Searc> vieAs can <e =sed to add department level sec=rity to S1! reports. :( a<leT a record definition t>at contains data t>at controls t>e application as opposed to <ein9 maintained <y t>e application. A RreferenceS ta<le or R9eneralS ta<le. MP or emporary or $or@T a ta<le t>at is created eit>er temporarily or permanently for a specific $!V p=rpose. Data is normally lost or tr=ncated at t>e <e9innin9 of a process eac> time t>e process is ran. "$ "ieAT a record definition t>at is p>ysically implemented <y definin9 an S1( vieA
Appl )S )S )S )S )S )S )S )S )S )S )S )S )S H! H! H! H! H! H! H! H! H! H! SA SA SA SA SA SA SA SA SA SA SABH!
Mod=le CMS DM E7 )#N )! +( #N M! P(S PO S)S E !C A:S APP :EN :UD ( PA2 PE! POS A7 !N AD AA C! C: )A #S ME P! S) S! CC
Description Catalo9 Mana9ement System Ded=ction Mana9ement E?pense )inancials )inancial !eports +eneral (ed9er #nventory Mana9ement !eports Plannin9 P=rc>ase Order Prod=ction !eport ravel and E?pense reas=re Cas> Mana9ement A<sence Applicant :enefits :=d9et ime and (a<or Payroll Personnel Position a? !eportin9 rainin9 Admissions Advisement Advancement Contri<=tor !elations Coordinatin9 :oard )inancial Aid #nternational Sc>olars Meas=rement D Eval=ation P!OMES St=dent )inancials St=dent !ecords Camp=s Comm=nity
>e proFect name may incl=de t>e CS! n=m<er assi9ned in S A for easy identification. JE?ample8 =>sC1&%'K. Eac> proFect m=st >ave t>e description field pop=lated =nder )ile. ProFect Properties. 2.9.& 3ields Note4 C.an,in, PeopleSoft delivered internal obBects is disco-ra,ed and reC-ires mana,ement approval. M=ltiple records and panels =se t>ese fields. PeopleSoft fields can <e cloned =sin9 t>e namin9 convention standards descri<ed Ait>in t>is doc=ment. >e folloAin9 namin9 convention Aill <e =sed for UHS developed fields8 U'SEdescEsf5 A>ere RUHSS is t>e desi9nated prefi?. and t>e desc is a free format description folloAed <y a s=ffi?. 2.9.1 Records G S-brecords Note4 C.an,in, PeopleSoft delivered internal obBects is disco-ra,ed and reC-ires mana,ement approval. >ese records are =sed <y m=ltiple processes. #f necessary. PeopleSoft delivered records can <e cloned. >e folloAin9 namin9 convention Aill <e =sed for records8 U'SEdescEsf5 Jfor records A>ic> are not =sed for r=n controlK U'SERCEdesc Jfor records =sed for r=n controlK Eac> record m=st >ave t>e description field pop=lated in record properties. 2.9.2 State Records Application En9ine employs t>e =se of state records as a means of passin9 data <etAeen application en9ine processes. >e state record m=st folloA t>e folloAin9 namin9 convention8 &;di9it Prod=ct #dentifier WW RCS WW Description RCS QAE 6. Name can <e mi?ed case. 2.9.9 Pa,es G S-bpa,es >e folloAin9 namin9 convention Aill <e =sed for pa9es and s=<pa9es8 U'SEdesc A>ere RUHSS is t>e desi9nated prefi?. and t>e desc is a free format description. 2.9.: Components >e folloAin9 namin9 convention Aill <e =sed for components8 U'SEdesc A>ere RUHSS is t>e desi9nated prefi?. and t>e desc is a free format description. 2.9.; Men-s >e folloAin9 namin9 convention Aill <e =sed for men=s8 "ersion 0.1 114 Enterprise Systems ; UHS Pa9e 1& of
U'SEdesc A>ere RUHSS is t>e desi9nated prefi?. and t>e desc is a free format description. 2.9.+ Process Definitions >e process definition name m=st matc> t>e PeopleSoft e?ternal o<Fect to <e e?ec=ted JsGr. Co<ol. or Crystal. etc.K 2.9.< Aob Definitions Namin9 convention is U??????? >e Fo< definition s>o=ld <e9in Ait> RUS. 2.9.1* =-er@ Namin9 conventions do not e?ist <eca=se t>e f=nctional comm=nity is free to name t>em anyt>in9 t>ey Aant. Developers s>o=ld create G=eries <e9innin9 Ait> UHS. )or 1=ery =sed <y Crystal !eports t>e description field can <e t>e Crystal !eport id <ein9 invo@ed.
>e UHS namin9 convention for PeopleSoft e?ternal o<Fects or so=rce code. Ait> t>e e?ception of Co<ol. is
Pa9e 1% of
PeopleSoft Application Development Standards Uni5 reC-ires all e5ternal obBects s.o-ld be named in lo/er case.
X X
2.;.& Trace 3iles race files are created A>enever a developer t=rns trace on. race files trace t>e pro9ram code <ein9 e?ec=ted and is =sed for de<=99in9 p=rposes. race files s>o=ld not <e t=rned on in normal prod=ction r=ns. race files may create e?tremely lar9e files t>at may ca=se pro<lems d=rin9 e?ec=tion time or post;e?ec=tion A>en t>e developer attempts to edit t>e trace file. "ersion 0.1 114 Enterprise Systems ; UHS Pa9e 1' of
>e format for report files created or maintained <y <atc> pro9rams pro9ramid.trc A>ere pro9ramid is t>e name of t>e sGr A>ic> created t>e trace file. 2.;.1 Data 3iles Data files are flat files t>at may <e imported or e?ported to <atc> processes. Data files are not report files. E?cel files. or MicroSoft Access files. >ey typically do not contain col=mn >eadin9s or report >eadin9s. >e namin9 convention is a free format =sin9 an e?tension of .dat. desc.dat A>ere desc is a free format description. Ot>er files may <e created for t>e e?press p=rpose of loadin9 into E?cel. Access. or $ord. etc. As s=c>. appropriate file e?tensions may <e =sed.
Pa9e 1- of
9. ORAC$E
>e PeopleSoft environment reG=ires t>e =se of a relational data<ase mana9ement system J!D:MSK. At UHS PeopleSoft Oracle data<ases are maintained <y t>e Data<ase Administration staff in Enterprise Systems.
!nternal ObBect Compare Report is a spreads>eet created <y t>e D:A <y r=nnin9 sGl after t>e Compare !eports >ave <een created. >e S1( =ses ta<les =pdated <y t>e compare reports to indicate o<Fects t>at Aere c>an9ed. Application developers are responsi<le for revieAin9 t>e #nternal O<Fect Compare !eport. >e S(SAUD!T report is an a=dit report of discrepancies <etAeen PeopleSoft and Oracle system ta<les. >e S2SAUD# report is created only A>en installin9 maintenance pac@s. >e DDDAUD!T report is an a=dit report of discrepancies <etAeen PeopleSoft and Oracle application ta<les. vieAs. and inde?es. >e DDDAUD# report is created only A>en installin9 maintenance pac@s.
:.& PEOP$ETOO$S
PeopleSoft releases =p9rades to People ools appro?imately every G=arter. A People ools =p9rade =s=ally involves c>an9in9 t>e str=ct=re of People ools ta<les. As of version 3. t>ere are ools str=ct=ral c>an9es Ait> eac> minor ools release. >e release n=m<erin9 sc>eme is identified as folloAs8 3.14.1& or 3.'&.1% >e first di9it represents t>e version of application and tools softAare yo= are on. >e second tAo di9its represent t>e maFor version of tools and t>e last tAo di9its represent t>e minor release or patc> level of tools. Minor c>an9es are released more often in response to =r9ent fi?es t>at come from PeopleSoft. >e People ools =p9rade is installed <y t>e D:A staff. All maFor =p9rades m=st <e doAnloaded from t>e PeopleSoft Ae<site. >ey also send cd pac@a9e Ait> t>e softAare =pdates on it. All doc=mentation can <e doAnloaded from PeopleSoft6s C=stomer Connection Ae< site. Minor releases of t>e =p9rade can <e doAnloaded as Aell from t>is Ae< site alon9 Ait> t>e correspondin9 doc=mentation. >e folloAin9 steps are performed <y t>e D:A staff. >oAever. it is important for t>e Application Mana9ers to <ecome familiar Ait> t>e preparation p>ase of t>e =p9rade and =nderstand t>e fi?es and en>ancements t>at Aill <e availa<le Ait> t>e =p9rade. :.&.1. PREPARAT!ON Application Mana9ers Aill 9ive t>e approval to load People ools from t>e Demo to Dev to est and t>en to t>e Prod=ction environment. performin9 testin9 alon9 t>e Aay. >ey Aill also determine t>e sc>ed=le in A>ic> it Aill move from data<ase to data<ase. A People ools =p9rade Aill reG=ire t>e application servers. process sc>ed=lers and Ae< servers to <e <ro=9>t doAn. reconfi9=red andBor recreated to incorporate t>e c>an9es. >e CO:O( pro9rams Aill need to <e recompiled as Aell. >e D:A staff is responsi<le for t>ese tas@s. Once t>e =p9rade >as <een completed. t>e Application Mana9ers are notified.
D:A D:A D:A D:A Developers Developers D:A )=nctional Users D:A
Determine A>ic> patc>es to doAnload and <=ilds patc> set spreads>eet. DoAnload patc> set. <=ndle. maintenance pac@ to t>e demo data<ase. Create a=dit and compare reports sends o=t to developers for revieA Mi9rate patc>es to development data<ase. Compile CO:O(. !eapply c=stomiEations to PeopleSoft delivered o<Fects. Perform =nit tests. Mi9rate patc>es to test data<ase. Perform system and inte9ration tests. Mi9rate patc>es to prod=ction data<ase.
Data<ase Administrators Aill maintain a proced=re man=al for installation of patc>es and =p9rades. PeopleSoft application patc>es are doAnloaded every & % mont>s from t>e PeopleSoft Ae< site for )inance. St=dent Administration. H=man !eso=rces. and People ools. >e D:A team applies t>e patc>es. >e D:A analyst applyin9 patc>es s>o=ld <e familiar Ait> PeopleSoft Application Desi9ner. Data Mover. S1(N. CO:O( compiler tools. and Oracle. Uni? and N environments. #t is recommended t>at data<ase administrators applyin9 patc>es complete People ools # and Data Mana9ement B Up9rade classes offered <y PeopleSoft. :.1.1. PeopleSoft Patc.es PeopleSoft patc>es m=st <e e?tracted from PeopleSoft C=stomer Connection. Searc> criteria for t>e vario=s applications and mod=les are presented in Appendi? D. :.1.& PS Maintenance Sc.ed-le >e application mana9ers determine t>e PS Maintenance Sc>ed=le. >e D:As Aill Aor@ from t>e PS Maintenance Sc>ed=le to determine doAnload dates. apply to demo data<ase and deliver compare reports dates. Eac> p>ase of t>e patc> set move reG=ires application mana9er notification. Occasionally. <=siness process dates Aill conflict Ait> a patc> set ma@in9 it to prod=ction in a timely manner and t>e sc>ed=le slides a <it. :=siness processes co=ld ca=se t>e sc>ed=le to slide. All sc>ed=le conflicts m=st 9o t>ro=9> t>e application mana9ers. :.1.2 Testin, G Retrofittin, a Patc. set After patc>es >ave mi9rated to t>e tar9et data<ase. t>e tec>nical s=pport mana9er s>o=ld <e notified via email. Application developers can <e9in reapplyin9 c=stomiEations and =nit testin9. CS!s are created for application developers to doc=ment and mi9rate retrofits. :.1.9 Patc. set Mi,rations Once t>e application mana9er approves t>e mi9ration of t>e patc>es to t>e tar9et data<ase. t>e D:A Aill perform t>e move. An email Aill <e sent to t>e D:A listserv after t>e move is completed. Patc> mi9rations to t>e tar9et data<ase Aill occ=r d=rin9 t>e S=nday maintenance. after >o=rs. or d=rin9 t>e day. Patc> set mi9rations to t>e prod=ction data<ase Aill occ=r d=rin9 t>e S=nday maintenance AindoA. #n addition to t>e mi9ration reG=est. t>e D:A mana9er m=st complete a c>an9e notification form and present to t>e C>an9e Mana9ement Committee.
:.2 CUSTOM!IAT!ONS
:.2.1 !nternal ObBects A patc> set or application release Aill often modify PeopleSoft internal o<Fects. As s=c> c=stomiEations made to PeopleSoft delivered o<Fects Aill <e lost and m=st <e reapplied <y t>e application developer. o mana9e t>is. tAo tools are availa<le to developers8 1. Compare !eport &. O<Fects Spreads>eet
Pa9e 14 of
Compare Reports Compare reports identify A>ic> internal o<Fects Aere c>an9ed <y PeopleSoft <y comparin9 a so=rce JdemoK data<ase and a tar9et JdevelopmentK data<ase. >ese reports identify detailed c>an9es to PeopleSoft internal o<Fects and s>o=ld <e caref=lly revieAed <efore applyin9 patc>es to t>e development data<ase. Application developers are responsi<le for revieAin9 compare reports. ObBects Spreads.eet After t>e compare reports are created. t>e D:As Aill r=n a S1( process to create an o<Fects spreads>eet. >is S1( =ses compare report ta<les. >e D:As Aill also enter e?ternal o<Fects t>at need to <e retrofitted. >e spreads>eet can <e filtered for o<Fects c>an9ed. t>e last person to =pdate t>at o<Fect. etc. After patc> sets are mi9rated to t>e development data<ase. application developers may <e9in t>e retrofit process of reapplyin9 c=stomiEations and testin9. At t>is point. it is only necessary to cond=ct =nit testin9. )=ll testin9 Aill <e cond=cted <y f=nctional =sers after t>e patc> set mi9rates to t>e test environment. Developers s>o=ld place any internal or e?ternal o<Fects t>ey retrofit into a CS! Ait>in S A . :.2.1 Previo-s ersions $>en D:As install a maintenance pac@. t>ey Aill copy t>e c=rrent SAnnDE"BUSE! directory to SAnnDE"BUSE!CO(D and copy SAnnDE"BUSE!CO(D O SAnnDE"CUSE!CO(DE!. >e SAnnDE"BUSE! directory Aill <e refres>ed from SAP!D. >e old directories are for reference only or co=ld <e =sed to <rin9 c=stom process in pro9ress <ac@ to t>e SAnnDE"BUSE! directory. Note4 PeopleSoft delivered obBects t.at /ere modified s.o-ld not be copied bacH from old directories. T.e obBects s.o-ld be retrofitted instead. :.2.& Cr@stal) n ision) MicroSoft "ord ObBects >e D:A Aill copy Crystal !eports. n"ision. and $in$ord o<Fects directly into t>e B=ser directories on t>e data<ase so=rce code tree. #f any of t>ese o<Fects >ave <een c=stomiEed. developers s>o=ld refer to previo=s versions and reapply c=stomiEations. :.2.1 Unit Testin, Unit testin9 of internal and e?ternal o<Fects in t>e patc> set or application release is cond=cted in t>e development environment <y t>e application developers. Unit testin9 ens=res t>at t>e o<Fect Aill e?ec=te and desired o=tp=ts are prod=ced. De<=99in9 and verification of o=tp=t res=lts are performed <y t>e developer. $>en =nit testin9 >as completed. t>e patc> set can mi9rate to test. :.2.2 S@stem Testin, System testin9 is performed <y f=nctional =sers and @ey f=nctional =sers in t>e test environment. System testin9 incl=des testin9 of complete processes incl=din9 =pstream and doAnstream processes as applica<le. System testin9 may also incl=de inte9ration testin9 <etAeen tAo or more applications and load testin9 to verify t>at t>e >ardAare and netAor@ infrastr=ct=re can s=pport t>e c>an9es <ein9 made.
Pa9e &, of
Functional lead su"mits request for enhancement or modification to tech appl mgr#
(nalysis ) $esign
Coding
Unit Test
Migrate to test
Migrate to production
roduction !erification
$e%eloper %erifiies migration &or'ed successfully# Email is sent to functional lead/security administrator to update menu security#
>is process is mana9ed <y a prod=ct from 1=est called S A . All C>an9e Service !eG=ests JCS!K are ro=ted t>ro=9> S A . S A is self;doc=mentin9. #t Aill record c>an9e reG=ests. trac@ t>e c>an9e service reG=est JCS!K as it moved t>ro=9> t>e sta9es. and provides necessary approvals from f=nctional and tec>nical mana9ers <efore final mi9ration to prod=ction. S A also provides version control for PeopleSoft internal o<Fects s=c> as pa9es. components. records. etc. and e?ternal o<Fects s=c> as S1!s. CO:O(. etc.
Pa9e &1 of
PeopleSoft Application Development Standards rainin9 for f=nctional and tec>nical staff is reG=ired <efore =sin9 S A . >is doc=ment is not intended to <e a trainin9 doc=ment for S A <=t Aill provide <asic information at t>e concept=al level.
Pa9e && of
Pa9e &% of
Upon completin9 t>e initial CS!. t>e reG=estor m=st enter a User#d <efore t>ey can save t>e pa9e. >e User#d defa=lts to t>e tec>nical mana9ers s=pportin9 t>at application. Upon savin9 t>e pa9e. an email Aill <e sent to t>e c=stomer and to t>e tec>nical mana9er notifyin9 t>em t>at a reG=est >as <een entered into S A . ;.&.& STAT "orHflo/ Once t>e CS! >as <een created. S A Aill create a Aor@floA to mana9e movement of t>e CS! and attac>ed o<Fects. Only t>e person to A>om t>e CS! is assi9ned or a mana9er can =pdate t>e CS! and move it to t>e ne?t step in t>e Aor@floA.
Pa9e &' of
#n t>e e?ample a<ove. t>e CS! is in RAcceptedS stat=s Aaitin9 to <e moved to RDevelopmentS and assi9ned to a developer. As t>e CS! moves to vario=s stat=ses. t>e CS! Aill <e assi9ned to t>e ne?t person A>o is to perform t>at activity. #f approvals are reG=ired. S A Aill restrict movement of t>e CS! to t>e ne?t stat=s =ntil t>e approvals are made electronically Ait>in S A . ;.&.1 !nitial Approvals >e E. S. ec>nical Applications Mana9er is responsi<le for revieAin9 t>e reG=est and decidin9 A>ic> action m=st <e ta@en. >e reG=est may <e denied. placed on >old. moved to an RAcceptedS stat=s Aaitin9 for reassi9nment to a developer. or moved to RDevelopmentS stat=s and assi9ned to a developer. >e E. S. ec>nical Applications Mana9er determines if t>e reG=est >as received approval from t>e Application AdvisoryB(eaders>ip +ro=p or t>eir desi9nee. All reG=ests for processes to access. retrieve. or =pdate data on prod=ction data<ases reG=ire t>e approval t>e Application AdvisoryB(eaders>ip +ro=p. >e E. S. ec>nical Applications Mana9er is responsi<le for mana9in9 t>e Aor@ and priorities of >is staff s=<Fect to priorities set <y t>e Application AdvisoryB(eaders>ip +ro=p. ;.&.2 Approval b@ t.e Application Advisor@?$eaders.ip %ro-p >ere are t>ree Application AdvisoryB(eaders>ip +ro=ps representin9 H=man !eso=rce Mana9ement System. )inancials. and St=dent Academics and Administration. Eac> Application AdvisoryB(eaders>ip +ro=p s>all define its oAn proced=res for >oA reG=ests Aill <e approved internally <y t>e Application AdvisoryB(eaders>ip +ro=p. >e E. S. ec>nical Mana9er or t>e Application )=nctional (ead Aill determine A>et>er a reG=est m=st <e presented to t>e Application AdvisoryB(eaders>ip +ro=p for clarification andBor approval.
Pa9e &- of
PeopleSoft Application Development Standards Note4 A s=ita<le notification to Application AdvisoryB(eaders>ip +ro=p Ao=ld <e a 9ro=p e;mail referencin9 t>e identification n=m<er of t>e Development !eG=est. $>enever possi<le. t>at e;mail notification s>o=ld <e made at least &' >o=rs prior to t>e meetin9 so t>at t>e team mem<ers >ave a c>ance to revieA and print o=t any relevant information. As a practical matter. t>e !eG=estor s>o=ld also confirm t>at especially relevant team mem<ers >ave received notification and t>at t>ey >ave any necessary doc=mentation. >e E. S. ec>nical Application Mana9er is responsi<le for presentin9 material reG=ests to t>e respective Application AdvisoryB(eaders>ip +ro=p. Specifically incl=ded in t>e revieA are areas affected <y t>e c>an9e and t>e reG=estMs priority and tentative implementation sc>ed=le. >e Application AdvisoryB(eaders>ip 9ro=p may ta@e any of t>e folloAin9 actions8 Approve t>e development reG=est !efer t>e development reG=est to t>e E?ec=tive Mana9ement Committee for approval !efer t>e development reG=est to t>e ec>nical Application Mana9er for more information or for impact and cost analysis Deny t>e reG=est >e ec>nical Application Mana9er is responsi<le for comm=nicatin9 t>e stat=s of t>e reG=est to t>e reG=estor. ;.&.9 Approval 0@ T.e E5ec-tive Committee >e Application AdvisoryB(eaders>ip +ro=p is acco=nta<le to t>e E?ec=tive Mana9ement Committee and as s=c> s>all determine A>ic> reG=ests reG=ire approval <y t>e E?ec=tive Mana9ement Committee. S=c> referrals may <e <ased on political. policy. environmental. f=nctional application processes. or cost considerations. ;.&.: Mi,rate 3rom Prod-ction To Development >e E. S. ec>nical Application Mana9er may <e reG=ired to develop an impact or cost analysis of t>e reG=est <efore any f=rt>er Aor@ is completed. >e CS! s>o=ld <e moved to RHoldS stat=s =ntil s=c> analysis is complete. $>en development Aor@ is ready to <e9in. t>e E. S. ec>nical Application Mana9er Aill move t>e CS! to RDevelopmentS and assi9n t>e CS! to a developer via S A Aor@floA. S A Aill send an email notification to t>e developer. Once t>e Development !eG=est is approved. t>e tec>nical mana9er or application developer Aill develop tec>nical specifications. a test plan. and identify A>ic> o<Fects. ta<les. or files Aill reG=ire modification. S A provides t>e a<ility for an application developer to attac> a PeopleSoft o<Fect to t>e CS! and Rloc@ o=tS ot>er CS!s from =sin9 t>is o<Fect. >is loc@o=t occ=rs only Ait>in S A . NOTE4 Alt.o-,. obBects are locHed in STAT) t.is onl@ prevents anot.er developer from mi,ratin, t.ose obBects via STAT. T.ere is not.in, to prevent a developer from modif@in, obBects locHed b@ anot.er developer in STAT. T.is practice is not approved or enco-ra,ed. Developers s.o-ld locH obBects in STAT before modification be,ins to prevent ot.er developers from mi,ratin, obBects t.e@ are /orHin, on. S A Aill copy t>e prod=ction o<Fects to <e modified to development environment to ens=re t>ey are Aor@in9 on a c=rrent prod=ction copy.
Pa9e &* of
S A mi9rations are a &;step process8 1. >e o<Fect is copied from t>e so=rce data<ase to a S A arc>ive data<ase. &. >e o<Fect is copied from t>e S A arc>ive data<ase to t>e tar9et data<ase. "ersion 0.1 114 Enterprise Systems ; UHS Pa9e &0 of
#f a developer needs to move a previo=s version of A>at t>ey >ave modified to t>e tar9et data<ase. t>ey simply mi9rate from appropriate arc>ive set to t>e tar9et data<ase. >e S A :aseline Set is a copy of t>e o<Fects from t>e prod=ction data<ase prior to ma@in9 any modifications. >e <aseline set is stored in t>e S A arc>ive data<ase and copied to t>e development environment. $>en t>e o<Fects are moved to prod=ction and t>e ori9inal version needs to <e restored. t>e <aseline arc>ive set can <e =sed to move t>e o<Fects <ac@ to prod=ction. HO$E"E!. t>is m=st <e done <efore t>e D:As move t>e CS! to a completed stat=s A>ic> removes t>e o<Fects from t>e CS! and releases t>e loc@. NOTE4 Once t.e CSR is closed and t.e locHs on t.e obBects released) it is not possible to install previo-s versions of t.e obBects via STAT. ;.&.; Development Activit@ >e development activity <e9ins Ait> analysis and desi9n <y t>e application developer. After t>e tec>nical specifications are completed. t>e application developer <e9ins development activities. s=c> as codin9 and testin9. folloAin9 t>e standards contained Ait>in t>is doc=ment. D=rin9 t>e development p>ase. t>e application developer is responsi<le for8 Development of t>e tec>nical specifications Pro9rammin9 activities codin9. de<=99in9. and testin9 Performin9 =nit testin9 #nitiatin9 a development Aal@t>ro=9> B tec>nical revieA of t>e c>an9e Ait> t>e reG=estor. J!eference C>apter 0.*K #n some cases t>e application developer Aill perform some of t>ese tas@s Ait> t>e assistance of t>e f=nctional =sers. ;.&.+ Mi,ration to Test Environment Mi9rations to t>e test environment is a &;step process performed Ait>in S A <y t>e developer. 1. Mi9rate PeopleSoft o<Fects from development data<ase to t>e test data<ase &. Move t>e CS! via Aor@floA to R estS stat=s and reassi9nin9 t>e CS! to t>e f=nctional analyst A>o Aill cond=ct t>e testin9. S A Aill a=tomatically send email notification to t>e f=nctional analyst t>at t>e CS! >as <een reassi9ned to t>em. Application Developers s>o=ld not >ave access to ma@e men= sec=rity c>an9es in test or prod=ction environments. Application Developers s>o=ld not <e a<le to r=n =pdate S1( in test or prod=ction environments. D:As can r=n S1( if instr=cted to do so Ait>in t>e CS!. NOTE4 Do not .ave Application Desi,ner open /.en mi,ratin, obBects in STAT. Application Desi,ner /ill a-tomaticall@ add obBects to a proBect @o- .ave open in STAT. T.e developer /o-ld -nHno/in,l@ mi,rate obBects t.at do not belon, to t.e proBect and .ave been modified and possibl@ -ntested. After completin9 =nit andBor system testin9. t>e f=nctional analyst can perform tAo actions 1. !et=rn t>e CS! to t>e developer for f=rt>er modifications &. Approve t>e CS! to <e moved to prod=ction and move t>e CS! to RMana9er ApprovalS stat=s. ;.&.< User Acceptance Testin, >e test data<ase is t>e standard defa=lt test data<ase for f=nctional =sers. >e sand<o? data<ase. A>ic> is refres>ed Aee@ly. may <e =sed for =nit. system. or =ser acceptance testin9 <eca=se t>e test environment does not contain t>e complete prod=ction environment data set. >ere are & additional data<ases. DC1 and DC&. A>ic> can <e =sed for testin9 time sensitive processes. >e dates can <e c>an9ed on t>e servers s=pportin9 t>ese data<ases.
Pa9e &3 of
PeopleSoft Application Development Standards System and inte9ration testin9 are cond=cted at t>is point. )=nctional =sers are responsi<le for developin9 a test team and cond=ctin9 =ser acceptance testin9 in t>e test environment. Vey f=nctional =sers Aill provide t>e test team Ait> t>e test plan and scripts to <e =sed d=rin9 t>e =ser acceptance test. >e testin9 team may s=pplement t>ese test plans and scripts Ait> standard andBor specific tests relevant to t>e c>an9e. #f additional c>an9es are reG=ired. t>ey are ret=rned to t>e application developer for reAor@ in development. at A>ic> point t>e process of mi9ratin9 to t>e test environment m=st repeat itself. >e folloAin9 tests s>o=ld <e considered andBor cond=cted8 Complete system testin9 of t>e application processes and Complete system testin9 of application interfaces to ot>er applications or e?ternal applications. Complete system testin9 of voice and data netAor@s (oad testin9 User acceptance testin9 s>o=ld <e completed prior to approvin9 t>e CS! and movin9 it to RMana9er ApprovalS stat=s. ;.&.1* Mi,ration to Prod-ction Once t>e CS! is in RMana9er ApprovalS stat=s. t>e E. S. ec>nical Application Mana9er can approve t>e CS! and move t>e CS! to RMove o Prod=ctionS stat=s. Email notice is a=tomatically sent to all D:As via S A to indicate t>at t>e CS! is ready to mi9rate. )inal mi9rations are performed Ait>in S A <y a D:A. After t>e o<Fects >ave <een mi9rated. t>e D:A Aill ro=te t>e CS! eit>er to sec=rity for men= sec=rity =pdates or to a RCompletionS stat=s. An email notification Aill <e sent to t>e c=stomer and t>e E. S. ec>nical Applications Mana9er A>en t>e CS! stat=s is completed. A completion stat=s Aill remove t>e loc@s on PeopleSoft o<Fects attac>ed to t>e CS!. >e folloAin9 matri? identifies t>e & types of mi9rations and A>en t>ey can occ=r. Normal Mi,ration ype # E?ternal O<Fects can mi9rate at any time. E?tra approval not reG=ired. ype ##. #nternal O<Fects Aill mi9rate on =e. D >r. after 0 p.m and <efore 0 a.m. on t>e folloAin9 day and on S=n. d=rin9 t>e S=nday maintenance AindoA. All app servers Aill <e <ro=9>t doAn prior to mi9ratin9 o<Fects and t>en <ro=9>t <ac@ =p. No e?tra approvals reG=ired. nBa Emer,enc@ Mi,ration ype # E?ternal O<Fects can mi9rate at any time. E?tra approval not reG=ired ype ##. #nternal O<Fects Aill mi9rate on after 0 p.m and <efore 0 a.m. on t>e folloAin9 day. All app servers Aill <e <ro=9>t doAn prior to mi9ratin9 o<Fects and t>en <ro=9>t <ac@ =p. !eG=ires approval from tAo tec>nical mana9ers. ype ##. #n e?treme emer9encies. #nternal O<Fects may mi9rate d=rin9 <=siness >o=rs. All app servers Aill <e <ro=9>t doAn prior to mi9ratin9 o<Fects and t>en <ro=9>t <ac@ =p. !eG=ires approval from t>e Associate "ice President of Enterprise Systems
)=nctional =sers may desi9nate a reG=est as an emer9ency. $it>in S A . t>is is done <y settin9 t>e c=stomer priority to RUr9entS. >e process for movin9 t>e CS! and mi9ratin9 o<Fects for emer9ency CS!S is no different t>an re9=lar CS!s. >e process is simply e?pedited. NOTE4 D0As s.o-ld not perform emer,enc@ mi,rations -ntil t/o tec.nical mana,er approvals .ave been received.
Pa9e &4 of
PeopleSoft Application Development Standards Emer9ency mi9rations s>o=ld <e avoided if at all possi<le <eca=se t>e application server services may <e restarted A>ic> res=lts in temporary =navaila<ility of t>e application or application server cac>e may need to <e re<=ilt. Emer9ency c>an9es s>o=ld not violate t>e inte9rity or t>e intent of c>an9e control processes. >e E. S. ec>nical Mana9er is responsi<le for notifyin9 >is s=perior and peers t>at an emer9ency mi9ration t>at Aill ca=se a disr=ption of service is a<o=t to occ=r. >e E. S. ec>nical Mana9ers t>at Aill <e affected <y t>e mi9ration are responsi<le for contactin9 @ey f=nctional personnel providin9 t>e time disr=ption is e?pected to occ=r and for >oA lon9. Email notification is s=fficient. >oAever. t>e tec>nical mana9er may Aant to provide a ver<al notification as Aell. ;.&.11 3ailed Mi,rations To Prod-ction Occasionally. it is not possi<le for t>e D:A to mi9rate o<Fects to prod=ction. >is co=ld <eca=se t>e o<Fects are not loc@ed in S A . =nclear instr=ctions Ait>in t>e CS!. etc. Application developers are reG=ired to enter t>eir >ome p>one and cell p>one in t>e description area of t>e CS! <efore movin9 t>e CS! o=t of development. #n t>e event t>e D:As are =na<le to mi9rate a CS!. t>ey s>all immediately call t>e application developer to notify t>em of t>e pro<lem. #f necessary. t>e D:As Aill ret=rn t>e CS! to t>e developer. Application developers may indicate in t>e description area of t>e CS! t>at t>e CS! is not critical and t>ey s>o=ld not <e called. ;.&.1& Special !nstr-ctions for "in"ord Mi,rations Only =sers in t>e PS;Dev;$in$ord and PS;Dev;D:A $indoAs access 9ro=ps >ave access to Arite to P8PSAnn S P$inAord and P8PSAnn S P=serPAinAord directories. >is Aas introd=ced to alloA camp=s st=dent administration staff to ma@e minor modifications to t>eir letters and p=t into t>e prod=ction environment directly. Ait>o=t D:A assistance. Sec=red =sers Aill test t>eir modifications in P8PSAnn S PAinAord directory and r=n a9ainst t>e SAnn S data<ase. and once t>ey are ready to move t>e letter to prod=ction. t>ey copy it to p8PSAnn S P=serPAinAord. P8PSAnn S P=serPAinAord is replicated >o=rly to t>e prod=ction code tree. Developers do >ave access to p8PSAnnDE"PAinAord and p8PSAnnDE"P=serPAinAord directories. $>en r=nnin9 $in$ord from a PeopleSoft panelBprocess. t>e $in$ord doc=ment m=st reside in t>e P$in$ord directory and NO in P=serP$in$ord. P=serP$in$ord is =sed to @eep a copy for reference and maintain consistency Ait> t>e development environment Ji.e. @eep all t>e modified codes in P=serP..... directoryK. :eca=se =sers can modify t>e letter Jin t>e SAnn S SAP!DB$in$ord <efore modifyin9 t>e letter. code treeK. t>e latest version s>o=ld <e copied from
;.&.11 STAT Doc-mentation CS!s can easily <e vieAed t>ro=9> stat=s and t>ro=9> vario=s filters incl=din9 CS! stat=s and assi9nment G=e=e. >is alloAs f=nctional mana9ers. tec>nical mana9ers. and developers to researc> previo=sly completed CS!s. S A also provides a variety of canned reports.
Pa9e %, of
Pa9e %1 of
PeopleSoft Application Development Standards S A also maintains a >istory of anyone A>o made c>an9es to t>e CS!. STAT 'istor@ Pa,e
Pa9e %& of
+. PRO%RAMM!N% STANDARDS
+.1 TRA!N!N% RE=U!REMENTS
Minim=m tec>nical trainin9 reG=irements for entry level application developers is S1(. S1!. 1=ery. People ools #. Additional tec>nical trainin9 may incl=de People ools ##. PeopleCode. application en9ine. component interface. application messa9in9.
Never delete a delivered men=. #f t>e men= is not desired. =se operator sec=rity to >ide t>e men=s from all operator id6s and operator classes.
Pa9e %% of
PeopleSoft delivered men=s s>o=ld not <e modified. UHS c=stom men=s s>o=ld <e =sed. Men=s s>o=ld <e or9aniEed lo9ically accordin9 to t>e men= 9ro=p it is in and t>e nat=re of t>e application. #f t>ere are several components associated Ait> an application. t>ose components s>o=ld <e 9ro=ped to9et>er.
Men= (a<els s>o=ld <e in Mi?ed Case. Men= item names s>o=ld <e descriptive of t>e process so t>at t>ey are easily identifia<le in sec=rity administrator. +.&.9 Mi5ed Case Mi?ed case te?t is easier to read. All neA applications s>o=ld =se mi?ed case for non;varia<le te?t. s=c> as col=mn >eadin9s and la<els. =nless t>e te?t is a mnemonic or an acronym. Decisions re9ardin9 case on e?istin9 applications s>o=ld <e made in t>e manner t>at is t>e least disr=ptive to t>e =ser. #f a neA screen is added to an application t>at employs =pper case. factors s=c> as t>e overall aest>etic effect of t>e mi?t=re. as Aell as t>e li@eli>ood t>at t>e remainin9 screens Aill <e revised in t>e near f=t=re. s>o=ld <e considered. No sin9le screen s>o=ld =se <ot> mi?ed case and =pper case for la<el and col=mn >eadin9s. #n addition. screens s>o=ld provide for t>e inp=t of mi?ed case data A>ere appropriate ;; for e?ample. descriptive te?t t>at is not =sed for a searc>.
+.1 PEOP$ECODE
+.1.1 Codin, Standards PeopleCode is commonly =sed to c=stomiEe PeopleSoft. Code s>o=ld <e commented to facilitate t>e maintenance of PeopleCode. >ese comments are critical A>en PeopleSoft patc>es are installed. $>en PeopleCode is Aritten. t>e editor enforces t>e str=ct=re of t>e code. )or disc=ssions on Aritin9 PeopleCode see t>e PeopleCode Class Man=al and t>e PeopleCode People:oo@s. >e =se of t>e )ield)orm=la event is primarily =sed to store f=nctions. :eca=se code in t>is event alAays processes. it s>o=ld only <e =sed for f=nction li<raries and Ae< li<raries. +.1.& Code Doc-mentation >e application developer is responsi<le for code level comments in all cases. Commentin9 r=les are as folloAs8 Comments need to <e incl=ded Ait> all codin9 tas@s. s=c> as neA development. en>ancementsBmodifications and <=9 fi?es. JE?ample 1K #ncl=ded in all comments s>o=ld <e a RUHSS ta9. CS!Y. date of modificationBcreation. developer name. and e?planationB<ac@9ro=nd of t>e neABmodified code. JE?ample 1K Code s>o=ld <e <ro@en =p into lo9ical <loc@s. and at eac> maFor step in t>e application lo9ic a neA comment s>o=ld <e created. $>en t>e <loc@ is complete an end comment s>o=ld <e created. $>en code is c>an9ed. t>e ori9inal code needs to <e commented o=t and replaced Ait> t>e =pdated code. o ma@e it easier to identify. t>e commented code needs to <e a<ove t>e modified code. o provide f=t=re reference. do not delete t>e old code. JE?ample &K
UHS Modified Code8 #f UPanel+ro=p I LMA#N A#NCPOCC)L >en "ersion 0.1 114 Enterprise Systems ; UHS Pa9e %' of
PeopleSoft Application Development Standards BZ UHS. CS!;1&%'.,%B,1B&,,&. Start. )Snnnnn. [developer name >ere\ ZB BZ Description of t>e c>an9e <ein9 made. ZB BZ DAM "CH! I POC"c>rCAmtCActiveJPOC(#NEC)S.:US#NESSCUN# . POC(#NEC)S.POC#D. POC(#NEC)S.(#NECN:!. ,. ,KTZB DAM "CH! I POC"c>rCAmtCActiveJPOC(#NECD#S !#:.:US#NESSCUN# . POC(#NECD#S !#:.POC#D. POC(#NECD#S !#:.(#NECN:!. POC(#NECD#S !#:.SCHEDCN:!. POC(#NECD#S !#:.D#S !#:C(#NECNUMKT BZ UHS. ,%B,1B&,,&. End ZB End;#fT E5ample & 6 Commentin, o-t e5istin, code and addin, c-stom code8 Ori9inal Code8
If %PanelGroup = "MAINTAIN_PO_CF" Then &AMTVCHR = PO_Vchr_Am _Ac !"e#PO_$IN%_F&'()&IN%&&_)NIT* PO_$IN%_F&'PO_I+* PO_$IN%_F&'$IN%_N(R* ,* ,-. %n/0If.
DAM "CH! I POC"c>rCAmtCActiveJPOC(#NECD#S !#:.:US#NESSCUN# . POC(#NECD#S !#:.POC#D. POC(#NECD#S !#:.(#NECN:!. POC(#NECD#S !#:.SCHEDCN:!. POC(#NECD#S !#:.D#S !#:C(#NECNUMKT
12 )H&* ,51,314,,4* %n/ 21 %n/0If.
Pa9e %- of
PeopleCode and S1( codin9 conventions s>o=ld <e folloAed A>en placed Ait>in an App En9ine pro9ram.
Crystal !eports
Microsoft E?cel
1=eries created in PeopleSoft can <e directly sent to Microsoft E?cel. :y r=nnin9 G=eries to a spreads>eet. yo= can manip=late t>e data =sin9 t>e feat=res and form=las availa<le Ait> Microsoft E?cel. 2o= Ao=ld typically c>oose t>is reportin9 option if yo= do not >ave PSBn"ision and Aant to =se t>e data for analysis p=rposes. PeopleSoft n"ision ena<les yo= to create <=siness reports in Microsoft E?cel. >is tool alloAs yo= to incl=de an a99re9ate val=e from a selected G=ery in yo=r report. >ro=9> PSBn"ision. yo= control >oA t>e report loo@s <y desi9nin9 t>e layo=t and format of t>e report. >is reportin9 tool is commonly =sed to <=ild s=mmary reports =sin9 a99re9ate f=nctions s=c> as S=m or Avera9e. A>en yo= Aant to create c>arts or 9rap>s. and Ait> mail mer9e doc=ments. S1! is a very poAerf=l and comple? reportin9 option <=t also >as t>e a<ility to manip=late data and ta<les. S1! reports are 9enerated <y application developers. #n most cases. one of t>e ot>er reportin9 options e?plained Ao=ld provide t>e information t>at yo= need.
PeopleSoft n"ision
Reportin, Tools %eneral Criteria SQR Unlimited or requires multiple selects Unlimited Ro&s returned /er%er Comple*ity of reporting 1 /peed of process 11 $rilldo&n E*cel Format Charts ) 7raphs E*tension Uni* /er%er or +T /er%er 2 3 +o 6es 6es $efined "y program# Report output defined "y rocess scheduler# Crystal nVision PS Query , (- is the U./ recommended limit) (pp ser%er time limit App Server JUni?K 5 5 +o 6es +o +/a
, rocess scheduler time limit +T /er%er 3 2 6es +o 6es #08/, R T, $F Report output defined "y rocess scheduler#
, rocess /cheduler time limit E*cel 0imit +T /er%er 4 2 6es 6es 6es #90/, $F Report output defined "y rocess scheduler#
Pa9e %0 of
+.: S=R
S1! JStr=ct=red 1=ery !eport$riterK is delivered Ait> t>e PeopleSoft system. S1! is =s=ally t>e tool of c>oice for comple? <atc> reports and processes. Additionally. PeopleSoft delivers vario=s listin9 reports t>at detail t>e contents of a 9iven ta<le s=c> as t>e valid val=e for fields. Note t>at S1!s can <e e?ec=ted from Ait>in t>e PeopleSoft on;line environment via t>e Process Sc>ed=ler. o=tp=t Aill <e Aritten to t>e report repository directory. >e
+.:.1 S=R Pro,rammin, Standards $>en vanilla reports reG=ire c=stomiEation. t>e S1! s>o=ld <e copied and placed in t>e =serBsGr directory A>ere modifications are made. E?cept A>ere c>an9es are minimal. neA pro9rams s>o=ld <e created rat>er t>an modifyin9 delivered vanilla pro9rams =sin9 t>e standard namin9 convention contained Ait>in t>is doc=ment. #n order to ease porta<ility yo= s>o=ld resist =sin9 platform;specific S1( f=nctionsBe?pressions. A>ere possi<le. +.:.& S=R Performance OptimiJation >e performance of an S1! pro9ram is 9reatly affected <y t>e performance of t>e S1( =sed in t>e pro9ram. >e main S1( para9rap> s>o=ld contain t>e ma?im=m n=m<er of Foins necessary to o<tain t>e primary data as opposed to >avin9 a feAer n=m<er of Foins and callin9 s=<ro=tines to perform additional selects t>at co=ld <e accomplis>ed in t>e ori9inal select. Ot>er met>ods of en>ancin9 performance incl=de creation of additional inde?es on t>e ta<les involved and t>e =se of Oracle >ints. Many tools. incl=din9 S1( E?pert. alloA yo= to o<tain t>e Oracle plan of e?ec=tion for t>e S1( <ein9 performed. >e plan of e?ec=tion determines and demonstrates t>e efficiency of t>e S1( <ein9 e?ec=ted. +.:.1 S=R Mod-larit@ Proced=res s>o=ld <e coded in t>e order :e9in;Set=p :e9in;Pro9ram JNote8 :e9in;!eport >as <een replaced Ait> :e9in;Pro9ramK do #nit;Date ime do #nit;N=m<er do +et;C=rrent;Date ime do #nit;!eport do Process;Main do !eset do Stdapi; erm End;Pro9ram :e9in;Headin9 :e9in;)ootin9 :e9in;Proced=re Process;Main :e9in;Proced=re ????? Jcalled from Process;Main or ot>er proced=resK X. JContin=in9 from >i9>est to loAest levelK X. X. +.:.2 S=R Pro,ram Str-ct-re Proced=res local to t>e S1! s>o=ld appear in a lo9ical order. S1! files m=st >ave an e?tension of .sGr A>ile e?ternal proced=res are stored in files Ait> an e?tension of .sGc. "ersion 0.1 114 Enterprise Systems ; UHS Pa9e %3 of
>e UHS standard >eadin9s and standard trailers s>o=ld <e =sed Ait>in UHS c=stom S1! pro9rams. folloAin9 S1Cs s>o=ld <e =sed for standard report titles and >eadin9s. SA UHSHD+,,1 !eport <y <=siness =nit for mont> endin9 H! UHSHD+,,1 !eport <y <=siness =nit for mont> endin9 UHSHD+,,& Standard >eadin9 Ait> <=siness =nit D dept name optional UHSHD+,,% Uses UHSHD+,,& Ait> AsOfDate incl=ded )S UHS)SHD+,1 Standard Headin9 UHS)SHD+,& Uses UHS)SHD+,1 Ait> <=siness =nit
>e
+.:.9 !nteraction "it. T.e PeopleSoft Application S1! pro9rams m=st alAays <e Application Process #nterface JAP#K aAare in order to properly =pdate t>e PeopleSoft Process Sc>ed=ler. >e PeopleSoft delivered proced=re STDAP!K!nit is called to initialiEe parameter val=es. STDAP!KTerm performs end of report processin9. do #nit;N=m<er do #nit;Date ime do +et;C=rrent;Date ime do StdapiK!nit do #nit;!eport do Process;Main do StdapiKTerm #f t>e S1! enco=nters an error condition. t>e process stat=s m=st <e =pdated in order for t>e Process Sc>ed=ler to reco9niEe t>e error and for t>e Process Monitor to display t>e correct stat=s. An e?ample Ao=ld <e as8 #f ]error condition^ !O((:ACV (et OMs9 I M#nvalid X ; A<ortM SHO$ OMs9 #f YprcsCprocessCinstance \ , (et YprcsCr=nCstat=s I YprcsCr=nCstat=sCerror (et OprcsCmessa9eCparm1 I OMs9 #f OprcsCinC=pdateCprcsCr=nCstat [\ M2M Do Update;Prcs;!=n;Stat=s Jt>is proced=re >as a commit coded Ait>in it. >is Aill commit all =pdates =nless a roll<ac@ is performedK End;if End;if S OP End;#f +.:.: S=R !ncl-de Proced-res S1! incl=de proced=res are contained in mod=les calls S1Cs. >e PeopleSoft delivered S1C Rsetenv.sGcS s>o=ld <e incl=ded in all S1!s. #t defines data<ase specific parameters. >ese appear immediately <efore R<e9in; pro9ramS. ypically all ot>er incl=de S1Cs Aill appear at t>e <ottom of t>e S1! and s>o=ld <e in loAer case. All proced=res implemented as e?ternal re=sa<le pro9ram mod=les s>o=ld pass all val=es into and o=t of t>e proced=re =sin9 parameters. Avoid =sin9 9lo<al varia<les in re=sa<le proced=res. !e=sa<le proced=res t>at pass no parameters s>o=ld <e declared (OCA(.
Pa9e %4 of
:e9in;Proced=re !eportCData (ocal _ X End;Proced=re #f a proced=re passes parameters. it is considered to <e local. :e9in;Proced=re !eportCData JODataCSelectionCParamK _X End;Proced=re
Proced=res specific to a pro9ram may =se 9lo<al varia<les. <=t t>is practice is recommended only for t>e smallest of pro9rams. >ese proced=res s>o=ld <e declared Ait>in t>e pro9ram file Jnot Yincl=dedK. As UN#7 is case;sensitive. all S1Cs s>o=ld <e saved =sin9 loAercase names to ens=re t>at m=ltiple copies of t>e S1C do not e?ist on t>e server. Any LY#NC(UDEL needed <y a re=sa<le pro9ram mod=le s>o=ld <e added to t>e <ottom of t>e S1!.
+.:.; S=R !np-tKData erification #f t>e =ser is to enter an inp=t andBor o=tp=t file. t>e pat> s>o=ld not <e >ard coded. as part of t>e inp=tBo=tp=t file name.
#f inp=t parameters are <ein9 specified =sin9 a r=n control record. t>e inp=t data s>o=ld <e validated <y t>e proced=re t>at is selectin9 t>e parameter data. >is en>ances mod=larity and alloAs improved pro9ram maintenance. +.:.+ S=R Sortin, :=<<le Sort. #nsertion Sort and !ec=rsive Sort J1=ic@SortK are several met>ods t>at may <e =sed to sort S1! internal arrays. E?ample code for t>ese sortin9 tec>niG=es may <e fo=nd <y searc>in9 online S1! so=rces. An alternative to sortin9 internal arrays is to =se an operatin9 system command to sort a flat file. >e UN#7 system >as a command called RsortS JCall System Usin9 Qsort t8 N% file1.dat \ file&.dat6 Ystat=sK. >is met>od mi9>t <e =sed as an alternative to accessin9 t>e data<ase m=ltiple times F=st to order t>e data correctly. as Ao=ld <e t>e case Ait> nested SE(EC para9rap>s. +.:.< S=R Database $inHs Data<ase lin@s are not t>e preferred met>od for retrievin9 information across data<ases. >oAever. t>ey can <e =sed Ait> director approval. >e #nte9ration :ro@er s>o=ld <e =sed instead. +reat care s>o=ld <e e?ercised A>en =tiliEin9 D: lin@s. as t>e pro9ram Aill noA <e affectin9 tAo data<ases. Code =tiliEin9 D: (in@s s>o=ld <e caref=lly crafted to <e t>e most efficient possi<le. $>en r=nnin9 pro9rams Ait> D: (in@s on t>e server. it is important to note t>at t>e access time alloAed to t>e lin@ is limited. C=rrently it is set in t>e nei9><or>ood of &, min=tes. $>en selectin9 from a lar9e ta<le across a lin@. provisions for t>is timeo=t may >ave to <e made. See D:A to create or =se an e?istin9 D: lin@. Additional lin@s may <e esta<lis>ed =pon demand to assist developers and f=nctional =sers in testin9 processes. D: lin@s s>o=ld <e =tiliEed dynamically in S1!. >e <est sol=tion is to pop=late a ta<le in PeopleSoft Ait> t>e environment as t>e @ey and t>e lin@ name as t>e data. >e S1( select can t>en <e <=ilt dynamically =sin9 t>is information.
Pa9e ', of
(et OPS;UHS;Cost;Center I MPSCUHSCCOS CCEN E!`M WW O)S;D:;(in@ SE(EC ZZZZZZ )rom aOPS;UHS;Cost;Centerb UCC +.:.1* S=R Error 'andlin, $>en a S OP or S OP 1U#E is =sed to terminate a pro9ram Ait> =ns=ccessf=l completion. t>e S1! reserved varia<le Yret-rnKstat-s m=st <e set to a positive val=e 9reater t>an Eero. Care s>o=ld also <e ta@en not to call LS=ccessf=l;eoFL or ot>er clean=p ro=tines t>at Aill set Yret-rnKstat-s <ac@ to Eero. !efer to t>e prior section on #nteraction Ait> t>e PeopleSoft Application for additional information. #n t>e code <eloA. t>e S1! OPEN command iss=es an instr=ction to t>e OS to open a file for Aritin9. :y incl=din9 t>e RStat=sS parameter in t>e command. t>e OS Aill ret=rn t>e s=ccess or fail=re of t>e command. A tr=e val=e indicates a fail=re. >e #) statement eval=ates t>e ret=rn and Aill set varia<les and call t>e error code if fail=re is tr=e. Open O)tpscript as 4 )or;$ritin9 !ecordI&-, Stat=sIYOpenStat #f YOpenStat [\ , (et OErrorC e?t I !trimJMError openin9 M WW O)tpscript. M MK (et Y!etCcode I YOpenStat Do )ileCError End;#f #n t>e folloAin9 e?ample a proced=re is invo@ed to =pdate t>e process monitor in t>e event of an error. #t Aill =pdate t>e process stat=s as Aell as insert a messa9e as to t>e nat=re of t>e error in t>e process monitor. >is alloAs t>e =ser to <etter =nderstand t>e reason for t>e error. $A!N#N+ ; A COMM# #S #SSUED :2 HE UPDA E;P!CS;!UN;S A US P!OCEDU!E_ Developer s>o=ld consider iss=in9 a !O((:ACV prior to callin9 t>is proced=re. ROLLBACK IIIIIII May Aant to !O((:ACV to prevent =nAanted data from <ein9 Committed.
:e9in;Proced=re )ileCError S>oA OErrorC e?t #f YprcsCprocessCinstance \ , (et YprcsCmessa9eCsetCn<r I YprcsCms9CsetCn<r (et YprcsCmessa9eCn<r I %, _ Set to <lan@. (et YprcsCr=nCstat=s I YprcsCr=nCstat=sCerror (et YprcsCrc I Y!etCCode (et OprcsCmessa9eCparm1 I OErrorC e?t _c=stom error messa9e (et YprcsCcontin=eFo< I , Do Update;Prcs;!=n;Stat=s _ in stdapi.sGc IIIIII #SSUES A COMM# _ S OP 1U#E End;Proced=re )ileCError
Pa9e '1 of
PeopleSoft Application Development Standards +.:.11 S=R Codin, Practices Never c>an9e a pro9ram t>at e?ists in t>e PS delivered PsGr directory. >is directory s>o=ld remain =nto=c>ed and vanilla. PeopleSoft delivered S1!s A>ic> reG=ire modification s>o=ld <e moved to t>e B=serBsGr directory in t>e code tree. Avoid =sin9 strin9s to store and manip=late dates. "aria<les in t>e S1! date data type are alAays stored internally =sin9 a ';di9it year. Dates in strin9 format are reG=ired A>en comparin9 dates in an #f statement or Eval=ate statement. Dates s>o=ld <e in a date format A>en =sed in a sGl statement J$>ere cla=seK. o maintain platform independence. avoid callin9 operatin9 system commands from Ait>in yo=r S1!. Use an eG=ivalent S1! f=nction instead. #f t>at is not possi<le. c>ec@ t>e OsGr;platform S1! predefined varia<le and e?ec=te t>e appropriate operatin9 system commands <ased on its val=e. No line s>o=ld contin=e past t>e 3,t> position in t>e file for t>e sa@e of porta<ility. Place de<=99in9 statements in yo=r S1! as yo= Arite it. Usin9 t>e DE:U+ S1! command fla9 Aill alloA t>ese de<=99in9 statements to <e e?ec=ted A>en desired. <=t ot>erAise i9nored <y t>e compiler. ;DE:U+ command can <e e?panded to alloA developers to t=rn on and off individ=al sections of code for de<=99in9 <y identifyin9 sections. E?ample ; Yifdef de<=9? display MEnterin9 DA EMA H.S1C8 Convert; o;D U;DateM display M #np=t OdateCin8 M noline display OdateCin Yend;if Yifdef de<=9a display M ODD(/ero modified. Pro<a<ly assi9ned from n=meric.M Yend;if #n t>e a<ove e?amples. t>e R7S code Ao=ld <e displayed <e enterin9 ;DE:U+7 in t>e S1! Command fla9 line. o display <ot>. enter eit>er DE:U+ or DE:U+A7. +.:.1& S=R S@nta5 Data<ase ta<le and col=mn names A>en =sed in varia<le names or proced=re names s>o=ld not <e a<<reviated or c>an9ed e?cept A>ere necessary. >is more clearly associates t>e varia<le or proced=re Ait> t>e so=rce col=mn or ta<le. and ma@es it easier to searc> for affected code A>en c>an9in9 a ta<le or col=mn. S1! is case;insensitive. HoAever. case may <e =sed to improve a pro9ram6s reada<ility. Usin9 =nderscores and das>es serves a similar f=nction. !ecommendations for t>e =sa9e of case. =nderscores and das>es are8 Avoid =se of t>e >yp>en L;L in varia<le names. Use t>e =nderscore LCL instead. >e >yp>en is sometimes conf=sin9 Je.9.. Yco=nt;1 is "E!2 different from Yco=nt ; 1K. Also. =ser;defined varia<les may <e more easily distin9=is>ed from S1! predefined JreservedK varia<les t>at do =se a >yp>en <etAeen Aords. L:e9in;Set=pL. L:e9in;Pro9ramL. L:e9in;!eportL. L:e9in;Proced=reL. and L:E+#N;SE(EC L sections s>o=ld <e9in at t>e left mar9in as Aell as t>eir correspondin9 LEndL statements. Eac> level inside t>e S1! s>o=ld >ave an indentation of % spaces. $>en contin=in9 a statement. t>e contin=ation s>o=ld <e indented eit>er % spaces. or eno=9> to ali9n Ait> semantically eG=ivalent portions of t>e previo=s line. i.e.
Pa9e '& of
PeopleSoft Application Development Standards let ]varname^ I ]statements.............^ ]contin=ed statements...^ do ]proced=re name^ J]ar91^.]ar9&^....]ar9?^. ]ar9?N1^..........K LifL. LA>ileL. and Leval=ateL sections increase t>e indentation <y % spaces. LelseL. Lend;ifL. Lend;A>ileL. LA>enL. LA>en;ot>erL. and Lend;eval=ateL s>o=ld >ave t>e same indentation as t>eir correspondin9 LifL. LA>ileL. or Leval=ateL. Usin9 L9o toL is not recommended. +.:.11 S=$ 3ormattin, No LmovesL =nless necessary. #n ot>er Aords. donMt MO"E every Dvaria<le into a Ovaria<le or Yvaria<leT only move t>ose t>at are reG=ired <y t>e lo9ic of yo=r pro9ram. Processin9 code s>o=ld <e fo=nd <etAeen t>e :E+#N;SE(EC and t>e LfromL of t>e Select para9rap>. S=< S1( statements s>o=ld folloA t>e same form. <=t indented. All @ey Aords in t>e str=ct=re s>o=ld stand o=t. L >ere are & r=les of precedence. M=ltiply <efore yo= add and =se parent>eses everyA>ere else.L Jparap>rase from OM!eilly and Assoc.K +.:.12 0oolean E5pressions Define t>e val=es r=e and )alse for =se in :oolean tests rat>er t>an =sin9 t>e inte9ers , and 1. >is >elps self; doc=ment t>e code and alloAs less potential for error. #t is more diffic=lt to accidentally assi9n r=e A>en yo= mean )alse t>an it is to assi9n 1 A>en yo= mean ,. )=t=re maintenance of t>e pro9ram Aill <e made easier <y t>is practice.
Pa9e '% of
PeopleSoft Application Development Standards +.:.19 S=R 'eader >e >eader portion of t>e S1! incl=des 9eneral information a s=<seG=ent pro9rammer Ao=ld need to refer to8
<2222222222222222222222222222222222222222222222222222222222222222222222222222222 < )P%R,53= %R& TO )H A//re99 +IFF%R%NC% R%PORT 2 <2222222222222222222222222222222222222222222222222222222222222222222222222222222 < +e9cr!p !on= Rea/9 f!le from %R& an/ repor 9 /!fference9 !n emplo>ee9 2 < A//re99 ;e ?een %R& an/ HRM&' 2 <2222222222222222222222222222222222222222222222222222222222222222222222222222222 < Mo/ +a e Au hor C&R@ Mo/ +e9cr!p !on 2 < AA1AA1AA AAAAAA AAAA AAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA2 <2222222222222222222222222222222222222222222222222222222222222222222222222222222
+.:.1: S=R Code Doc-mentation Proced-re Doc-mentation Doc=mentation pertainin9 to a called proced=re is optional. Developers s>o=ld alAays s=pply doc=mentation to provide clarification as needed. >e :e9in;proced=re statement s>o=ld folloA t>e proced=re doc=mentation. E?ample8
<2222222222222222222222222222222222222222222222222222222222222222222222222222222 < Proce/ure= :e _ erm_/e9cr#B9 rm* =B9 rm_/e9cr2 < +e9c= Th!9 proce/ure re r!e"e9 he erm /e9cr!p !on from P&_T%RM_T($' 2 < I !9 calle/ from ;e:!n0hea/!n: an/ ma!n' Th!9 !9 a local proce/0 2 < ure' 2 < 2 < B9 rm !9 pa99e/ ;> "alue 2 < B9 rm_/e9cr !9 pa99e/ ;> reference 2 <2222222222222222222222222222222222222222222222222222222222222222222222222222222
:e9in;proced=re 9etCtermCdescrJOstrm. OstrmCdescrK Code Doc-mentation Doc=mentin9 c>an9es to lines of code s>o=ld ad>ere to t>e folloAin9 r=les8 1. Never delete lines of code. Comment t>em o=t instead. &. Use <e9in and end doc=mentation statements to indicate A>ere c>an9es <e9in and end. %. Use t>e same <e9in and end str=ct=re as indicated in t>e e?amples <eloA. '. o en>ance reada<ility. lar9e sections may reG=ire commentin9 o=t A>en m=ltiple c>an9es >ave occ=rred Ait>in a section. -. >e mod n=m<er does not refer to t>e n=m<er of c>an9es Ait>in a S1! <=t t>e n=m<er of times t>e S1! Aas c>an9ed. One mod can >ave m=ltiple c>an9es to t>e code. >e mod reference is t>e same for all of t>em. E?ample 18 C>an9in9 a line of code _ UHS :e9in Mod ,1 pro9rammer initials ,*B&-B&,,& _ Ydefine nonCde9reeC=9rdCs=mrCtranCenrl MNONDE+M Ydefine nonCde9reeC=9rdCs=mrCtranCenrl MNONDE+SM! M _ UHS End Mod ,1 _ E?ample &8 Deletin9 Code _ UHS :e9in Mod ,& _ (E O: I OC _ (E OA I O: (E OA I OC _ UHS End Mod ,&
Pa9e '' of
Pa9e '- of
o coordinate data t>at cannot ot>erAise <e lin@ed. o present different vieAs of t>e same data in a sin9le report.
+.;.9 Cr@stal Criteria >ere may <e times A>en it is necessary to filter o=t =nAanted data in Crystal instead of 1=ery. +.;.9.1 Select E5pert >e Select E?pert in Crystal is t>e eG=ivalent of t>e Criteria ta< in PSB1=ery. +.;.9.& Parameter 3ields >e Parameter field in Crystal is t>e eG=ivalent of t>e r=n time Prompts of PSB1=ery. to r=n t>e same report Ait> different val=es. >is alloAs m=ltiple =sers
Note8 Usin9 selection criteria and parameters. all roAs of data Aill <e retrieved from t>e data<ase and filtered in crystal. >is may ca=se some performance iss=es. #t is recommended to do all filterin9 of data in G=ery A>enever possi<le.
#nformation in t>e >eadin9 of yo=r report most often contains varia<les Je.9. report title. date. and operator #DK. +.+.1 Met.ods for sec-rin, PS?n ision Reports PSBn"ision =tiliEes several met>ods in sec=rin9 data presented on a PSBn"ision report. #ss=es s=c> as performance and ease of implementation need to <e considered <efore determinin9 t>e met>odJsK to =se. !oA level Sec=rity ree;<ased Sec=rity 1=ery Sec=rity NetAor@ Sec=rity Uses a=t>oriEation ta<le in conF=nction Ait> a data ta<le to restrict t>e data t>e =ser is alloAed to access. Usin9 trees to create a=t>oriEation ta<les com<ines ease of =se Ait> efficiency in implementin9 sec=rity provisions. Used in G=ery reports PSBn"ision report reG=est Aor@s to9et>er Ait> netAor@ sec=rity in alloAin9 only a=t>oriEed =sers t>e a<ility to access t>e report instances Ait>in directories.
+.< CO0O$
Modifications to CO0O$ pro,rams s.o-ld onl@ be done /.en absol-tel@ necessar@. >e reason for t>is is CO:O( pro9rams are m=c> more diffic=lt to maintain in PS d=e to patc>es. $>en a modification to an e?istin9 CO:O( pro9ram is done =pdate t>e RMOD#)#CA #ON H#S O!2S section of t>e pro9ram. >is section s>o=ld <e delivered in t>e pro9ram. Add a neA s=<section RUHS ModificationsS at t>e end of t>e Modification History. >e information placed >ere is t>e CS!Y. mod Y. date. developer name. and comments. P=t a description of t>e modification in t>e comments section. Example: ****************************************************************** * * * MODIFICATION HISTORY * * * * Mod Date Author CSR# Mod Description * * ======== ====== ==== === =================================* * 04/16/02 LEM 1234 01 Added code to process session * * Adjust Until Dates. * ****************************************************************** +.<.1 CO0O$ Code Doc-mentation >e folloAin9 is code Ait>in t>e CO:O(. proced=re descriptions and modifications. #f code is replaced. t>e ori9inal code s>o=ld also <e commented and not removed so t>e lo9ic of t>e c>an9e can <e folloAed. Z;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;Z Z Proced=re8 9etCtermCdescrJOstrm. 8OstrmCdescrK Z Z Desc8 >is proced=re retrieves t>e term description from PSC E!MC :(. #t is Z Z called from <e9in;>eadin9 and main. >is is a local proced=re. Z Z Z Z Ostrm is passed <yval=e Z ZJ 8OstrmCdescr is passed <y reference Z Z;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;Z Z Z =>s <e9in csrY mod ,1 pro9rammer ,*B&-B&,,& Z Ydefine nonCde9reeC=9rdCs=mrCtranCenrl MNONDE+M Ydefine nonCde9reeC=9rdCs=mrCtranCenrl MNONDE+SM! M Z =>s end Mod ,1 Z "ersion 0.1 114 Enterprise Systems ; UHS Pa9e '0 of
PeopleSoft Application Development Standards Z Z =>s <e9in csrY mod ,1 pro9rammer ,*B&-B&,,& T added ]nonCde9reeC=9rdCs=mrCtranCenrl^ to t>e list Z AND :.ACADCP(AN #N J]nonCde9reeC=9rdCtranCenrl^. ]nonCde9reeC9radCtranCenrl^. Z]nonCde9reeC=9rdCs=mrCtranCenrl^K Z =>s end Mod ,1 +.<.& CO0O$ DMS >e CO:O( DMS is a file t>at is r=n <y Data Mover to load t>e PSCS1(S M C :( Ait> all of t>e S1( statements t>at Aill <e =sed <y t>e CO:O( pro9ram. >e pro9ram does not >ave to <e compiled A>en c>an9es are made to t>e DMS. >e Data Mover can only <e r=n <y t>e D:As in all environments e?cept Development. Any c>an9es made to t>e fields selected andBor t>e criteria =sed m=st matc> A>at t>e CO:O( pro9ram is e?pectin9. E?ample8 CO:O(Je?ampleK8 ,% !EPO! ;ON(2 P#C 7J,1K "A(UE SPACES. ,% S!"C;#ND;CD P#C 7J,%K "A(UE SPACES. Z UHS :e9in Mod -*1 Z ,% $# HD!A$;)(A+ P#C 7J,1K "A(UE SPACES. Z UHS End Mod -*1 Z DMSJe?ampleK8 .!EPO! CON(2 .S!"CC#NDCCD Z UHS :e9in Mod -*1 Z .$# HD!A$C)(A+ Z UHS End Mod -*1 Z )!OM PSC!UNCCN (CCA(C $HE!E OP!#D I 81 AND !UNCCN (C#D I 8& $>en a modification to a DMS file is made. it Aill <e commented at t>e top of t>e file and t>e neA code Aill commented Ait> <e9in and end mar@ers. >e comments at t>e top of t>e DMS file Aill contain t>e CS!Y. t>e modification n=m<er. developer name. date. and description of t>e c>an9e. E?ample8 ;; ;; UHS CS!Y Mod -*1 (EM 1* SEP ,1 Added L$# HD!A$C)(A+L field to S)PC(CANCSC!UNC ( C>an9e Sort order of S)PC(CANCSCEN!O(( ;; >e comments mar@in9 t>e modified code m=st contain R:e9inS or REndS. Modification n=m<er. developer name or initials. date. and description. E?ample8 ;; UHS :e9in MOD -*1 (EM 1* SEP ,1 Added L$# HD!A$C)(A+L field to Select S O!E S)PC(CANCSC!UNC ( SE(EC :A CHC#D .:US#NESSCUN# .CANCE(C 2PE .S !M .SESS#ONCCODE "ersion 0.1 114 Enterprise Systems ; UHS Pa9e '3 of
.)AC# EMC+!OUP .)!OMC E!MC)#NA#D . OC E!MC)#NA#D .!EPO! CON(2 .S!"CC#NDCCD .$# HD!A$C)(A+ )!OM PSC!UNCCN (CCA(C $HE!E OP!#D I 81 AND !UNCCN (C#D I 8& ;; UHS End MOD -*1 (EM 1* SEP ,1 Added L$# HD!A$C)(A+L field to Select T Comments cannot <e im<edded Ait>in t>e S1( statement. Comments descri<in9 A>at Aas c>an9ed. added. or removed m=st <e placed <efore or after t>e S1( statement. >ese comments m=st incl=de fields added. #f any part of t>e S1( statement needs to <e removed. it Aill only <e commented o=t. E?ample8 ;; UHS :e9in MOD -*1 (EM * NO" ,1 ;; C>an9e S1( to sort co=rses in t>e order t>ey Aere enrolled in ;; Comment o=t folloAin9 delivered code ;; S O!E S)PC(CANCSCEN!O(( ;; SE(EC ;; :.C(ASSCN:! ;; .:.SESS#ONCCODE ;; .:.UN C:#((#N+ ;; .:.C!SEC+!ADECO)) ;; )!OM PSCS DN CCA!C E!M A ;; . PSCS DN CEN!( : ;; . PSCC(ASSC :( C ;; $HE!E A.EMP(#D I 81 ;; AND A.:#((#N+CCA!EE! I 8& ;; AND A.#NS # U #ON I 8% ;; AND A.S !M I 8' ;; O!DE! :2 :.C!SEC+!ADECO)).:.EN!(CADDCD DESC. :.C(ASSCN:! ;; UHS Commented o=t precedin9 delivered code S O!E S)PC(CANCSCEN!O(( All comments m=st <e prefi?ed Ait> RUHSS. >is Aill simplify findin9 any University of Ho=ston code c>an9es.
Pa9e '4 of
PeopleSoft Application Development Standards 1. A <atc> process is =sed to process lar9e vol=mes of information. )or e?ample. a <atc> process is needed to perform a mont>ly acco=ntin9 close or to 9enerate payroll c>ec@s and =pdate t>e payroll >istory A>ereas an interactive process mi9>t <e =sed to prod=ce one payroll c>ec@. A <atc> s=<mission pa9e Aill <e =sed to define t>e reG=ired parameters and to s=<mit Jr=nK a <atc> Fo<. >e parameters collectively are stored in t>e r=n control record defined <y t>e panel and accessed <y t>e <atc> Fo<. A <atc> process may <e appropriate for small data vol=me if pro9ram comple?ity is s=c> t>at maintainin9 <ot> on;line and a <atc> version of t>e pro9ram is not advisa<le. A <atc> process may <e =sed to provide a report t>at is comple? eno=9> t>at a PeopleSoft 1=ery Aill not s=ffice. #n some cases. <atc> process is a Aay to avoid loc@in9 a Aor@ station A>ile t>e transaction process is completed.
&. %. '.
:atc> processes r=n on t>e Process Sc>ed=ler. :atc> processes t>at =pdate t>e data<ase m=st provide t>e a<ility to recover from cras>es Ait>o=t data corr=ption. Since a <atc> Fo< may repeat t>o=sands of times A>at an on;line screen does once. efficient processin9 and cras> recovery are of t>e =tmost importance. >e li@eli>ood t>at a process Aill not finis> s=ccessf=lly s>o=ld <e red=ced <y t>oro=9>ly trappin9 errors. E?ceptions or minor pro<lems not critical to s=ccessf=l application =se s>o=ld <e reported <=t s>o=ld not stop t>e process. >e doc=mentation Ait>in t>e <atc> pro9ram s>o=ld e?plain t>e recovery process. especially critical A>en Aritin9 <atc> =pdate pro9rams8 1. ransaction lo9icT and &. A<ility to <e recovered. Ao considerations are
+.1*.1 Transaction $o,ic As a <atc> process iss=es S1( commands to insert. =pdate. or delete records from t>e data<ase. t>e record c>an9es are stored in an area called Rt>e roll<ac@ se9ment.S $>en a commit command is iss=ed. t>e records in t>e roll<ac@ se9ment are applied to t>e data<ase. #f a roll<ac@ command is iss=ed. t>e records in t>e roll<ac@ se9ment are deleted and t>e data<ase records are not =pdated. A LtransactionL refers to t>e =nit of Aor@ t>at m=st <e accomplis>ed in its entirety to maintain t>e lo9ical consistency of t>e data<ase. A lo9ical transaction may reG=ire =pdates to one or more different records. or even different data<ases. all of A>ic> comprise a sin9le transaction or =nit of Aor@. #n an on;line pa9e. a lo9ical transaction is =s=ally all of t>e =pdates associated Ait> a sin9le press of t>e save icon. Eit>er everyt>in9 t>e =ser reG=ested is committed and Aritten to t>e data<ase or none of it is. $it> S1(. a lo9ical transaction is terminated Ait> a COMM# statement. A sin9le commit is A>en a sin9le commit is iss=ed after A(( transactions are processed. >e sin9le commit Aill Arite all t>e transactions to t>e data<ase at a sin9le time. #f a S1! does not contain a sin9le commit. it Aill a=tomatically perform a sin9le commit A>en t>e S1! process completes s=ccessf=lly. >e advanta9e of =sin9 a sin9le commit is t>at it ma@es restart and recovery m=c> easier. >e <atc> process is simply rer=n from t>e <e9innin9. #f yo= are processin9 a lar9e vol=me of data or if it ta@es a very lon9 time for t>e process to r=n. t>is may not <e practical. Commits may need to <e placed lo9ically Ait>in t>e <atc> process. #f so. a commit s>o=ld never <e iss=ed =ntil at t>e end of a lo9ical transaction. $>en t>e commit is iss=ed. t>e developer s>o=ld consider A>at is necessary in t>e event t>at t>e process needs to <e rer=n. >e <atc> process s>o=ld <e9in from t>e point of t>e last commit <efore t>e process terminated. >e !O((:ACV command can <e =sed to release any records >eld for =pdate. Any inserts. deletions. or =pdates t>at occ=rred prior to t>e !O((:ACV Aill <e lost.
Pa9e -, of
PeopleSoft Application Development Standards NOTE4 Once t.e COMM!T command .as been e5ec-ted) t.e rollbacH command cannot restore records -pdated prior to t.e commit. #n order to determine t>e optimal timin9 of t>e COMM# statement. t>e <atc> developer m=st compromise amon9 t>e folloAin9 conflictin9 criteria8 1. COMM!Ts are reso-rceKintensive. Unnecessary commits can increase r=n time si9nificantly. &. Sin,le commits s.o-ld be -sed /.enever possibleL >oAever. records t>at >ave <een stored. =pdated. or deleted. are placed in roll<ac@ statement =ntil t>e ne?t COMM# . Holdin9 too many records co=ld res=lt in r=nnin9 o=t of space for t>e roll<ac@ se9ment ca=sin9 t>e pro9ram to a<ort. and may ca=se ot>er processes to fail as Aell. #f m=ltiple commits are reG=ired. commits s>o=ld <e placed at t>e end of a lo9ical transaction. %. Records cannot be .eld lon,er t.an t.e Transaction TimeKo-t parameter for t.e database. At t>e time t>e standards Aere compiled. t>e transaction time;o=t parameter for all data<ases Aas set at - min=tes. >e ransaction ime;o=t meas=res elapsed time. and elapsed time for different r=ns of t>e same process Aill vary accordin9 to t>e c=rrent load on t>e system. '. T.e COMM!T m-st not conflict /it. t.e lo,ical -nit of /orH Ja transactionK reG=ired to maintain data consistency. )or e?ample. a pro9ram mi9>t iss=e a COMM# for every acco=nt. or every &, acco=nts. <=t not in t>e middle of =pdates for an acco=nt. -. A RO$$0AC# command s>o=ld <e iss=ed A>enever an error is detected in t>e <atc> process. #f an S1! errors. it Aill a=tomatically iss=e a roll<ac@ command. +.1*.2 0atc. Recover@ $>en a <atc> =pdate process a<orts <eca=se of a system error or incorrect pro9ram lo9ic. in t>e case of pro9rams =sin9 m=ltiple commits. rer=nnin9 t>e same pro9ram mi9>t create d=plicate =pdates or missin9 records. >erefore. it is important t>at all <atc> pro9rams provide lo9ic and instr=ctions for recovery. i.e.. t>e steps to <e ta@en in order to <rin9 t>e Fo< to a s=ccessf=l completion. +.1*.2.1 Recover@ Options >ere are tAo approac>es to complete a Fo< t>at >as a<normally terminated for some reason. #n eit>er case. A>en t>e Fo< >as completed s=ccessf=lly all of t>e =pdates s>o=ld >ave <een completed. and none of t>em d=plicated or s@ipped. 1. !er=n ;; a Fo< stream is r=n A>ic> Aill start t>e failed process over from t>e <e9innin9 and r=n to t>e end. >e rer=n Aill reprocess all t>e data processed <y t>e a<orted Fo< step. &. !estart ;; a Fo< is s=<mitted A>ic> Aill restart t>e a<orted Fo< step from t>e point of fail=re and proceed to t>e end. Data. A>ic> Aere processed <y t>e a<orted Fo<. Aill not <e reprocessed. !ecovery may <e accomplis>ed a=tomatically or Ait> man=al intervention. NOTE4 Re,ardless of t.e met.od c.osen) all batc. -pdate pro,rams m-st provide for some Hind of recover@ t.at does not reC-ire pro,rammer intervention. >e a<ility to recover a <atc> pro9ram is essential to alloA =sers to perform t>eir oAn prod=ction control. #n t>is Aay. if t>e <atc> =pdate Fo< does not finis> s=ccessf=lly. it can <e easily recovered Ait>o=t reG=irin9 emer9ency ad >oc <atc> data<ase repairs. :atc> Fo<s t>at s=pport deadline;critical processes s>o=ld also incl=de a mec>anism Ait>in t>e lo9 file for determinin9 t>e c=rrent stat=s of t>e Fo<. )or e?ample. completion stat=s and s=mmary statistics may <e Aritten to t>e lo9 file after eac> maFor step. +.1*.2.& Restart Recover@ >e reso=rces reG=ired <y a <atc> Fo< Aill infl=ence t>e c>oice of recovery met>ods. NOTE4 0atc. processes reC-irin, si,nificant reso-rces s.o-ld be pro,rammed to start from point of fail-re) rat.er t.an rer-nnin, from t.e be,innin,.
Pa9e -1 of
PeopleSoft Application Development Standards >e folloAin9 9=idelines offer 9eneral s=99estions t>at s>o=ld <e =sef=l for most <atc> processes. HoAever. eac> <atc> pro9ram m=st <e individ=ally analyEed and s=pplied Ait> c=stom restart lo9ic. One sol=tion does not fit all. All <atc> Fo<s s>o=ld <e9in <y retrievin9 t>e r=n control parameters from t>e r=n control record. s>o=ld <e Aritten immediately to t>e lo9 file to aid in tro=<les>ootin9 if t>e Fo< cras>es. A restarta<le <atc> Fo< m=st determine t>e c=rrent Fo< stat=s ;; initial r=n or recovery r=n. determine point of fail=re. >e parameters
)orcin9 a <atc> process to s@ip steps andBor initiate data<ase access loops from varia<le startin9 positions reG=ires t>at t>e pro9ram <e desi9ned in separate p>ases. Eac> p>ase can <e performed independentlyT and. in many instances. some p>ases can <e started from t>e point of fail=re. )or e?ample8 P>ase 18 Master )ile Update loop ;; read t>e master file and =pdate for eac> transaction andBor Arite report data for eac> transaction. P>ase &8 Sort t>e report data file. P>ase %8 !eport loop ;; read t>e sorted data file and 9enerate t>e report. P>ase 1. t>e master file =pdate. m=st =pdate t>e restart control record Ait> c>ec@point information <efore every COMM# . )or instance. =se t>e @ey information. #f @ey fields are modified. t>en <ot> t>e old @ey and t>e neA @ey m=st <e stored. #t can <e =sef=l to store t>e operator id. process id. date. and r=n time in t>e restart control record. as Aell as t>e name of eac> flat file as it is opened. #ncl=de relevant information for eac>. s=c> as >oA many records >ave <een Aritten or read. and A>et>er processin9 of t>e file is complete. $>en t>e Fo< >as finis>ed. t>e restart control record s>o=ld <e properly fla99ed for s=ccessT or. it s>o=ld <e deleted. so t>at t>e ne?t r=n of a periodic <atc> Fo< Aill start fres>. #f t>e pro9ram determines t>e process a<orted in p>ase 1. t>e =pdateBdata collection step. recovery mi9>t incl=de t>e folloAin98 1. !ead t>e old o=tp=t data file created in p>ase 1 and Arite it a to neA o=tp=t file. >en t>e s=<seG=ent lo9ic Aill contin=e to =pdate t>is neA file Ait> t>e additional o=tp=t data. Or t>e o=tp=t data file created <y t>e neA process co=ld <e appended to t>e old data file at t>e end of p>ase 1. &. Enter t>e master =pdate loop <y startin9 Ait> t>e record @ey from t>e restart control record. #f t>e record @ey is not =niG=e. reFect records =ntil t>e @ey from t>e control record >as <een s@ipped. $>en t>e Fo< >as finis>ed. t>e control record s>o=ld <e properly fla99ed for s=ccessT or. it s>o=ld <e deleted. so t>at t>e ne?t r=n of a periodic <atc> Fo< Aill start fres>. A restart Aill =se t>e same control record to mana9e t>e restart process. #f t>e pro9ram determines t>e process a<orted in p>ase 1. t>e =pdateBdata collection step. recovery mi9>t incl=de t>e folloAin98 1K !ead t>e old o=tp=t data file created in p>ase 1 and Arite it a to neA o=tp=t file. >en t>e s=<seG=ent lo9ic Aill contin=e to =pdate t>is neA file Ait> t>e additional o=tp=t data. Or t>e o=tp=t data file created <y t>e neA process co=ld <e appended to t>e old data file at t>e end of p>ase 1. &K Enter t>e master =pdate loop <y startin9 Ait> t>e record @ey from t>e control record. #f t>e record @ey is not =niG=e. reFect records =ntil t>e @ey from t>e control record >as <een s@ipped. Ot>er met>ods for ma@in9 a <atc> =pdate process recovera<le incl=de8 1. Perform t>e Fo< in tAo Lpasses.L On t>e first pass. create a transaction ta<le t>at contains t>e desired c>an9es for t>e transaction. On t>e second pass. =pdate t>e master record from t>e transaction ta<le. A recovery co=ld r=n <ot> passes. or start Ait> t>e second pass. dependin9 on A>ere it a<orted. &. P=t a special field in t>e record to indicate A>et>er a roA >as <een processed ;; for e?ampleT store t>e date or set a fla9 in a field t>at >as <een incl=ded in t>e record for t>at p=rpose. >e select statement t>at identifies t>e roAs to <e processed for =pdate Ao=ld =se t>at field in t>e selection criteria. %. Use a restart control record. At t>e <e9innin9 of t>e <atc> pro9ram. if t>e control record does not e?ist. create one. Use t>e instance n=m<er as part of t>e @ey. Update t>e control record Ait> t>e val=es of @ey fields from "ersion 0.1 114 Enterprise Systems ; UHS Pa9e -& of
PeopleSoft Application Development Standards t>e select statement t>at p=lls t>e pop=lation to <e =pdated. #f t>ere Aas a pree?istin9 control record. A>ic> indicates t>at t>is is a re;r=n. start t>e processin9 Ait> t>e first employee A>ose n=m<er is 9reater t>an t>e employee n=m<er in t>e control record. #n t>is manner. not only d=plicate =pdates <=t also d=plicate effort Aill <e avoided. +.1*.9 Error 'andlin, Proper error >andlin9 is essential in <atc> processin9. Any error t>at ca=ses t>e <atc> process to a<normally terminate s>o=ld <e trapped and displayed in t>e lo9 file. report file. and t>e Process Monitor. >e <atc> process s>o=ld incl=de mail notifications to <e sent to appropriate staff. Possi<le <atc> errors co=ld <e system errors ca=sin9 t>e process to terminate or an error t>e developer >as identified in t>e pro9ram code and does not Aant processin9 to contin=e if a partic=lar error condition e?ists. +.1*.: Rec-rrin, 0atc. Processes :atc> processes may <e sc>ed=led to r=n on a rec=rrin9 <asis. )or e?ample. a <atc> process co=ld <e sc>ed=led to r=n daily at a partic=lar time. >is is accomplis>ed t>ro=9> t>e Process Sc>ed=ler. Special preca=tions m=st <e ta@en A>en c>an9in9 t>e rec=rrence parameters for <atc> processes. M=ltiple <atc> processes can s>are t>e rec=rrence name. NOTE4 !f t.e rec-rrence date and time is c.an,ed) it affects all processes -sin, t.at rec-rrence. #f a <atc> process6 parameters t>at control date ran9es or semester terms s>o=ld <e calc=lated for eac> r=n rat>er t>an s=pplied as constants <y t>e s=<mittin9 =ser. instr=ctions s>o=ld state A>et>er a date B term field may <e left <lan@ and A>at approac> t>e pro9ram Aill =se to comp=te t>e date B term in t>at case. )or e?ample. a mont>ly report co=ld =se t>e c=rrent system date to determine t>e date of t>e previo=s mont>. #f t>is approac> is =sed. t>e =ser Aill >ave t>e option to specify t>e date ran9e as a constant for a non;periodic r=n of t>e Fo<. in case it is necessary to rer=n for older data. Care m=st <e e?ercised for periodic <atc> A>ic> =ses restart lo9ic JSection 0.%.'.1K for t>e recovery of a<orted Fo<s. !estart control records and t>e parameters stored in t>em m=st <e created in s=c> a Aay t>at eac> lo9ical r=n is distin9=is>a<le. )or t>is reason. it is recommended t>at control records <e deleted or renamed =pon s=ccessf=l completion. >e process m=st <e a<le to distin9=is> <etAeen importBe?port files t>at Aere intended for a previo=s r=n and t>ose for t>e c=rrent r=n. A namin9 convention m=st <e devised A>ic> =niG=ely identifies t>e fileJsK created <y t>e <atc> process from files created from previo=s r=ns. #deally t>e process instance n=m<er s>o=ld <e =sed as part of t>e file name. S1! E?ample8 stdapi &ill populate <prcs=process=instance# 8n this e*ample, the %alue is >>>5342?-@ 0et AFile+ame B Ca"c=e*tractD 0et AFile+ame B Efilename=E FF edit(<prcs=process=instance,E>>>>>>>>>>E) FF E#t*tE !es=lt8 O)ileCname I Qa<cCe?tractC,,,1&%'-*0.t?t6 +.1*.; Ad .oc Updates Ad >oc <atc> processin9 a9ainst t>e prod=ction data<ase can <e done in one of tAo Aays8 1K =sin9 S1( scripts and a =tility s=c> as S1(N to e?ec=te t>ose scriptsT &K =sin9 S1!. NOTE4 Application developers are not allo/ed to directl@ e5ec-te S=$ scripts or ad .oc S=R t.at /ill -pdate prod-ction databases. All scripts t>at =pdate prod=ction data<ases reG=ire f=nctional =ser approval. Ad >oc reG=ests are made <y creatin9 a CS! in S A . >e CS! Aill provide instr=ctions to t>e D:A on t>e script to r=n and e?pected res=lts.
Pa9e -% of
PeopleSoft Application Development Standards Ad >ocs may <e Aritten to create a one;time report. S=c> reports are Aritten in S1! or may <e Aritten in S1( as G=eries Ait> o=tp=t t>at can <e inp=t to E?cel spreads>eets. >e developer does not need special a=t>oriEations to r=n t>ese reports. +.1*.+ Process Sc.ed-ler >e Process Sc>ed=ler is t>e mec>anism to s=<mit a pro9ram for e?ec=tion in a <atc> environment. >e S1! s>o=ld incl=de t>e stdapi.sGc for providin9 a comm=nications lin@ to t>e Process Monitor. S1! pro9rams s>o=ld call stdapi to indicate t>e S1! is processin9. !o=tines in stdterm.sGc s>o=ld <e =sed to indicate t>e process s=ccessf=lly completed. #f t>e S1! enco=nters an error. t>e appropriate stdapi fields s>o=ld <e =pdated to provide any =sef=l information. Alert messa9es s>o=ld <e sent to t>e s=<mitter notifyin9 t>em t>at t>eir Fo< >as a<orted. A Fo< is a set of processes t>at may r=n seG=entially or conc=rrently. >e Process Sc>ed=ler alloAs =sers to sc>ed=le t>eir Fo<s to r=n in t>e f=t=re. 5o<s and processes can <e sc>ed=led to r=n daily. Aee@ly. etc. =sin9 rec=rrence definitions. >e Process Sc>ed=ler provides report distri<=tion and t>e a=tomatic ro=tin9 of reports to m=ltiple recipients. >e Process Sc>ed=ler cannot split a report file into separate reports and ro=te t>e individ=al reports to vario=s recipients. +.1*.< Process Monitor >e Process Monitor alloAs =sers to monitor <atc> processes t>ey >ave s=<mitted. )rom t>e Process Monitor =sers can cancel c=rrently r=nnin9 or sc>ed=led <atc> processes. Users can also monitor <=t not c>an9e <atc> processes s=<mitted <y ot>er =sers. A snap s>ot of t>e Process Monitor is provided <eloA8
Pa9e -' of
+.1*.1* $o, 3iles (o9 files are created A>enever a <atc> process r=ns. :atc> lo9 files are important for tro=<les>ootin9 pro<lems. Pro9rams s>o=ld print messa9es to t>e lo9 file to identify errors A>en t>ey occ=r d=rin9 processin9. Also. processes t>at >andle t>o=sands of records s>o=ld periodically Arite stat=s information to t>e lo9. >e D#SP(A2 or SHO$ statement is =sed for t>is p=rpose. >e lo9 file s>o=ld not <e =sed to o=tp=t information t>at is part of t>e re9=lar processin9 reG=irements of t>e Fo< or to provide information t>at t>e =ser reG=ires for validation or verification. #t is not formatted in a =ser;friendly fas>ion and is not intended as an end;=ser report. Use a report file for t>is p=rpose. +.1*.1*.1 $o, 3ile $ocation >e lo9 file Aill <e copied to t>e report repository. >e S1! Aill create a lo9 file Ait> t>e process instance as part of t>e file name. (o9 files are a=tomatically deleted A>en t>ey are older t>an %, days in prod=ction and 1, days in non;prod=ction environments. +.1*.11 Data 3iles G Uni5 Directories $>en r=nnin9 <atc> processes on t>e server. data files may <e directed to Uni? directories t>at alloA developers access to sec=red directories. >e p=rpose of t>e Uni? directories is to facilitate importBe?port file interfaces via ) P. Uni? systems administrators are responsi<le for maintainin9 sec=rity to Uni? directories. Users Aill >ave indirect access t>ro=9> t>e application via s=<mission of a <atc> process. ftp process. etc. Developers Aill >ave direct and ftp access. One Uni? directory Aill e?ist for eac> application area. >e tec>nical application mana9er is oAner and may create s=<directories as needed. >e processes s=<mitted from t>e PeopleSoft financials application Aill lo9on Ait> t>e psftfs lo9on id and from t>e st=dentB>r application Ait> t>e lo9on operator id. >e application lo9on ids >ave Arite permissions to t>e folloAin9 directories. Application developers >ave also <een 9ranted privile9es as indicated <eloA. >e folloAin9 directories Aill <e esta<lis>ed on Uni? servers in development. test. and prod=ction environments. Blo9sBfinanceBX ; for e?cl=sive =se <y )inancials. Developers >ave read. Arite. e?ec=te. and control. Blo9sB>rmsBX ; for e?cl=sive =se <y H!MS. Developers >ave read. Arite. e?ec=te. and control. Blo9sBst=dentBX ; for e?cl=sive =se <y St=dent Academic Administration. Developers >ave read. Arite. e?ec=te. and control. +.1*.1& Reports S1!. Crystal !eports. $in$ord. and n"ision are t>e primary means to create reports. forms. and letters. +.1*.11.1 Report Contents A report typically contains t>e folloAin9 sections8 Title Area incl=des r=n date. r=n time. report titleJsK. pro9ram id. As Of Dates. )rom D >r= Dates. :=siness Unit. Deptid and name. Standard S1Cs >ave <een developed Ait>in eac> application area to provide a standard appearance to t>e report. >e developer m=st analyEe t>e S1C to determine A>ic> fields need to <e pop=lated to appear in t>e itle Area. Col-mn 'eadin,s eac> col=mn of data s>o=ld contain a col=mn >eadin9. Eac> col=mn >eadin9 s>o=ld <e =nderlined or =nderscored for reada<ility p=rposes. Report Detail data t>at appears in eac> col=mn of t>e report. #f <rea@ processin9 is =sed for s=<totals or pa9e <rea@s. t>e sort and <rea@ fields s>o=ld appear as t>e first col=mns on t>e report and s>o=ld <e listed in t>e order in "ersion 0.1 114 Enterprise Systems ; UHS Pa9e -- of
PeopleSoft Application Development Standards A>ic> t>ey are sorted. >e e?ception to t>is Ao=ld <e col=mns t>at are descriptions of id or code fields. A>ic> may appear Ait> t>e sorted fields. )or e?ample. a report <rea@in9 on colle9e id and deptid. Ao=ld <e arran9ed in t>e folloAin9 order8 colle9eid. colle9e name. deptid dept name. emplid. employee name. detail col=mnsX S-btotals are optional and typically appear in t>e middle of t>e report. Pa9e <rea@in9 is not reG=ired <efore a s=<total occ=rs. S=<totals s>o=ld >ave a <lan@ line precedin9 and folloAin9 t>e s=<total line. S=<total fields s>o=ld ali9n =nderneat> correspondin9 detail fields. Pa,e Totals are optional and appear at t>e <ottom of eac> pa9e. Pa9e totals contain totals for t>e detail col=mns on t>at pa9e. Pa9e total fields s>o=ld ali9n =nderneat> correspondin9 detail fields. %rand Totals are optional and appear at t>e end of t>e report. +rand totals are printed after t>e last s=<total line on t>e report. +rand total fields s>o=ld ali9n =nderneat> correspondin9 detail fields. +.1*.12 S=$ OptimiJation :atc> processes s>o=ld <e analyEed to see if t>ey co=ld <e optimiEed for e?ec=tion speed and minim=m data<ase access. )or daily r=n or time critical processes. optimiEation is especially important. OptimiEation s>o=ld incl=de a revieA of t>e S1( statements to see if t>ey are as efficient as possi<le. Oracle6s E?plain Plan can <e =sed to determine >oA a S1( statement is <ein9 e?ec=ted.
Pa9e -* of
:atc> inp=t processin9 s>o=ld apply all verification edits. #f t>e inp=t data contain errors. t>e process may reFect t>e <ad transactions or t>e entire feed. #n eit>er case. if possi<le. t>e reFected transactions s>o=ld eit>er <e stored in t>e tar9et ta<le Ait> a Ls=spenseL stat=s. or stored in a separate L>oldin9L ta<le. An on;line maintenance pa9e for processin9 t>e s=spended or >eld transactions s>o=ld <e provided for correctin9 errors in t>e feed data. o ens=re t>at t>e correct file can <e reco9niEed and d=plicates avoided. especially for periodic feeds8 1K >e so=rce application s>o=ld name t>e file to =niG=ely identify eac> feed. &K >e tar9et application may post to a ta<le A>en eac> feed is processed. so t>at it can determine A>ic> files >ave already <een fed. >e tar9et application s>o=ld rename or delete t>e file after s=ccessf=l completion of t>e process. application s>o=ld retain a copy of t>e feed file. >e so=rce
+.11.: !nterface Controls E?tract files s>o=ld contain one or more control records A>ic> provide control co=nts and dollar amo=nts Jif applica<leK for verification. >e inp=t process s>o=ld Provide co=nts of records read Ait> <rea@doAns <y vario=s 9ro=ps to matc> control record co=nts. Compare record co=nts a9ainst control record co=nts. Provide co=nts of records inserted. =pdated. not =pdated. otal n=m<er of records inserted. =pdated. or not =pdated s>o=ld matc> total control co=nt. #f co=nts do not matc>. send email notification as s=c>. End process in an error state. )or records not =pdated. co=nts for reasons A>y not =pdated. Eac> inp=t record can >ave m=ltiple edits t>at failedT t>erefore. t>ese co=nts may not matc> ot>er co=nts. Provide detail information for records =pdated. Jres=lts can <e stored in a c=stom ta<le.K Provide detail information for records not =pdated. Jres=lts can <e in a c=stom ta<le.K E5ample4 E?tract file contains one control record for eac> camp=s and a 9rand total control record. UH &,,, UHC 1,,, UHD 1,,, UH" -,, +rand otal '-,, !ecords !ead8 UH UHC UHD UH" otal !ecords #nserted !ecords Updated !ecords Not Updated otal !easons Not Updated8 #nvalid 5o< Code #nvalid Position #nvalid Emplid otal "ersion 0.1 114 &,,, 1,,, 1,,, -,, '-,, 1,,, %,,, -,, '-,, &,, ',, %,, 4,, Enterprise Systems ; UHS Pa9e -0 of
Pa9e -3 of
Pa9e -4 of 114
Stores t>e neA val=es of t>e field for a=dit c>an9e and delete actions. Stores t>e old val=es of @ey fields in order of appearance on t>e record definition. PSAUD# s=pports =p to 1- different @eys fields. eac> Ait> a ma?im=m field len9t> of =p to -, c>aracters.
+.1&.: Record $evel A-dit Table A-dit 3ield Name AUD# COP!#D AUD# CS AMP AUD# CAC N !ECNAME )ields of ta<le <ein9 a=dited. for e?ample8 EMP(#D NAME ADD!ESS1 ADD!ESS& Etc. +.1&.; A-dit Action al-es Action A C D V N Description Add C>an9e Delete Vey c>an9e Old record Vey C>an9e NeA !ecord Comment >e a=dit record contains t>e roA of data t>at Aas added to t>e ori9inal ta<le. >e a=dit record contains t>e roA of data as it Aas <efore t>e c>an9e Aas applied to t>e ori9inal ta<le. >e a=dit record contains t>e record t>at Aas deleted. >e a=dit record contains t>e record t>at >as t>e ori9inal @ey information >e a=dit record contains t>e record t>at >as t>e neA @ey information. P-rpose #dentifies t>e operator A>o ca=sed t>e system to tri99er t>e a=dits. eit>er <y performin9 an add. c>an9e. or delete to an a=dited field. #dentifies t>e date and time t>e a=dit Aas tri99ered. #ndicates t>e type of action t>e system a=dited #dentifies t>e name of t>e record definition a=dited. JOptionalK >is field is =sed A>en more t>an one data ta<le may <e =sin9 t>is a=dit record.
Pa9e *, of 114
PeopleSoft Application Development Standards Maintenance of 1=ery rees is located in People ools. Sec=rity. 1=ery Sec=rity. 1=ery Access Mana9er.
Access 9ro=ps are =sed <y PeopleSoft sec=rity to restrict access for a vieA or a record to a partic=lar set of =sers. M=ltiple access 9ro=ps may <e created for a G=ery tree. Users sec=red to an access 9ro=p can access any vieAs or records <elon9in9 to t>at access 9ro=p. NeA access 9ro=ps s>o=ld lo9ically descri<e t>e 9ro=p and <e9in Ait> t>e UHSC prefi?.
Pa9e *1 of 114
PeopleSoft Application Development Standards $it>in an access 9ro=p. trees can <e lo9ically se9re9ated into smaller 9ro=ps as s>oAn <eloA8
>e application developer m=st <e concerned Ait> 1=ery sec=rity and A>ic> set of =sers Aill need access to a vieA or a record <efore t>e vieA or record can <e placed on a 1=ery tree. Some data is sec=rity sensitive and m=st <e restricted to a=t>oriEed personnel. )or e?ample. access to personal <an@ acco=nts. 9rades. or credit card information s>o=ld <e very restricted or per>aps not made availa<le at all via 1=ery. Application developers m=st coordinate Ait> sec=rity administrators and f=nctional =sers <efore addin9 a vieA or record to a G=ery tree. !ecords are added as nodes to t>e tree. #n order for =sers to vieA t>e 1=ery trees. 1=ery Access (ist Cac>e m=st <e r=n.
+.12 TREES
ree str=ct=res and definitions may vary <etAeen data<ase environments. Note4 Trees as a r-le s.o-ld never be mi,rated bet/een environments. ree Mana9er ena<les yo= to or9aniEe tree str=ct=res =nder >i9> level 9ro=pin9s. called cate9ories. cate9ory names are s=99ested. :=d9et Defa=lt !eport ools UHS :=d9et related Access +ro=ps are placed =nder t>is cate9ory. >is is a PeopleSoft delivered Cate9ory. UHS developed reportin9 related access 9ro=ps are placed in t>is cate9ory. People ools D $or@floA related Access +ro=ps are placed in t>is cate9ory. >is cate9ory >as Access +ro=ps for UHS a<les. >e folloAin9
Pa9e *% of 114
>ere are tAo primary met>ods for cond=ctin9 tests8 Pro9ressive s>o=ld <e applied A>en cond=ctin9 tests.
PeopleSoft Application Development Standards #f a mod=le is to <e restarta<le. t>e restart and recovery m=st <e tested. <.&.1Unit Test Proced-res >e developer s>o=ld ta@e t>e folloAin9 steps8 1K +o <ac@ to t>e ori9inal pro9ram specifications and ma@e s=re every condition >as <een ta@en into acco=nt as far as Aritin9 t>e pro9ram is concerned. &K Set =p test data. AlAays try to =se e?istin9 prod=ction pro9rams to set =p test cases =nless impossi<le. Every scenario descri<ed in t>e specifications s>o=ld <e part of t>e test scenarios. %K $>en testin9. alAays t>in@ a<o=t testin9 for standard f=nctions. 'K $>en =pdatin9 critical information. test for a<normal termination and eval=atin9 restart possi<ility. -K Ma@e efforts to distri<=te a G=ality prod=ct8 for e?ample. report >eadin9s s>o=ld <e centered or consistently F=stifiedT dates and times need to folloA standard formatsT col=mns s>o=ld <e ali9ned on pa9es and evenly spaced Ji.e.. do not leave too many <lan@s at t>e end of a line. instead distri<=te spaces <etAeen col=mnsK.
Pa9e *- of 114
PeopleSoft Application Development Standards <.:.1 S@stem Test Proced-res 1K Developers and f=nctional =sers are responsi<le for t>e eval=ation of performance and recovery capa<ility of comp=tin9 processes. &K )=nctional =sers are responsi<le for t>e testin9 of <=siness processes and reG=ired f=nctionality.
Pa9e ** of 114
Additional testin9 reG=irements and information on t>e testin9 proced=res may <e imposed <y tec>nical mana9ers dependin9 on t>e de9ree of criticality of any 9iven application. <.11 TEST P$ANS est plans are a val=a<le aid to <ot> t>e application developer and t>e f=nctional analyst A>o Aill <e performin9 vario=s tests. >e test plan identifies ype of test JUnit. #nte9ration. SystemK. Complete list of testin9 scenarios. Set=pBconfi9=ration reG=irements for eac> scenario. Person A>o Aill perform t>e test. Date t>e test Aas completed. and est res=lts.
A t>oro=9> test plan Aill >elp ens=re t>at t>e application Aas t>oro=9>ly tested <efore it is mi9rated to prod=ction. Eac> type of test s>o=ld >ave its oAn separate test plan and <e maintained <y t>e developer. f=nctional analyst. andBor <=siness process oAner. A>oever is appropriate for t>e type of test. est plans s>o=ld <e retained after mi9ration or implementation into t>e prod=ction environment =ntil s=c> a time as t>e application >as <ecome sta<le and G=estions concernin9 application testin9 >ave <een satisfied. At a minim=m test plans s>o=ld <e @ept at least for & cycles of t>e ann=al application revieA done in late s=mmer B early fall coincidin9 Ait> fiscal year end activities. ests plans s>o=ld <e desi9ned to ansAer t>e folloAin9 tAo G=estions8 1. Does t>e application Aor@ as intendedH &. Can t>e application <e <ro@enH
Pa9e *0 of 114
PeopleSoft Application Development Standards <.11.1 Test Plan Template >e folloAin9 is an e?ample of a test plan template. >is can easily <e done in E?cel. CS!Y ?????? CS! itle ????????????????????????????? Developer8 ?????????????????????????????? )=nctional Analyst8 ???????????????????????????????????? SeGY est Description Set=p E?pected !es=lts ested :y est Date est !es=lts Stat=s
Pa9e *3 of 114
Pa9e *4 of 114
PeopleSoft Application Development Standards %K 'K -K *K 0K 3K Print o=t t>e so=rce code and pa9es and report samples. and distri<=te to t>e !evieA eam. Sec=re t>e revieAers to t>e application in development. :rin9 a copy of t>e Application Development Standards man=al to all meetin9s. Ens=re t>at t>e meetin9 room is availa<le and adeG=ately eG=ipped. Notify all participants s>o=ld meetin9s <e canceled or resc>ed=led. !evieA Ait> yo=r mana9er any additional development Aor@ reG=ired as a res=lt of t>e applicationMs Aal@t>ro=9>. (OUR APP$!CAT!ON MA( NOT 0E MO ED TO TEST OR PRODUCT!ON "!T'OUT T'E CONSENT O3 (OUR RE !E"ERS. >e revieAers may reG=ire a folloA;=p Aal@t>ro=9>. >e revieAers s>all limit reG=ests for c>an9es to pro9ram L<=9sL and to violations of t>e Standards. #ss=es of desi9n or performance trade;offs s>all not <e dictated <y t>e revieAers A>en s=c> iss=es are ot>erAise compliant Ait> t>e Standards. >oAever. t>e developer s>o=ld ta@e noted iss=es into consideration. !evieAers >avin9 stron9 feelin9s a<o=t s=c> iss=es s>o=ld Aor@ to 9et t>e Standards c>an9ed. 4K Disc=ss any s=99ested c>an9es to Standards Ait> t>e C>airman of t>e Application Development Standards Committee. 1,K Once all s=99ested c>an9es >ave <een made to t>e pro9rams. >ave t>e revieAers si9n and date t>e modification form prepared <y t>e !ecorder. >e form Aill 9o to yo=r mana9er. #f revieAers c>oose to record comments in t>e L!easonsL section of t>e form. t>ey m=st <e very specific. Simple 9eneral comments li@e Las disc=ssed in t>e meetin9L are not accepta<le. <.12.2 Revie/ $eaders $>ile t>e s=ccess of t>e revieA is t>e responsi<ility of eac> team mem<er. t>e !evieA (eader >as t>ese additional responsi<ilities8 1K +=ide t>e tone and pace of t>e revieA meetin9sT &K Ens=re t>at everyone >as an opport=nity to contri<=teT %K Poll for consens=sT 'K erminate a meetin9 in case of lac@ of preparation <y or a<sence of revieAer. len9t> of meetin9. tone of t>e revieA. etc. <.12.9 Revie/ Recorder >e !ecorder also >as o<li9ations <eyond <ein9 prepared. attendin9 and participatin9 in t>e revieA. >ese incl=de8 1K !ecord t>e findin9s of t>e Aal@t>ro=9> committee on t>e appropriate formT &K Ens=re t>at t>e 9ro=p >as reac>ed a definite concl=sion <y revieAin9 t>e iss=es as recordedT %K :e a<le to Arite notes in LrealL time as t>is may infl=ence t>e pace of t>e revieAT 'K !etain revieA notes =ntil t>e application andBor t>e pro9rams =nder revieA >ave <een approved for transfer to Prod=ction. <.12.: Revie/ Participants >e folloAin9 list of r=les and 9=idelines applies to all revieA participants8 1K :e prepared JrevieA materials in advance. <rin9 t>em to t>e revieA Ait> a copy of standardsKT &K :e Aillin9 to associateT %K $atc> yo=r lan9=a9eT 'K !aise iss=es and ma@e s=99estionsT -K Avoid side<ar disc=ssionsT *K Stic@ to standards ;; or 9et t>e standard c>an9edT 0K !ecord all iss=es in p=<licT 3K Stic@ to tec>nical iss=esT 4K !emem<er ed=cation Jt>is is t>e maFor lon9;term <enefit of revieAsKT 1,K Do not eval=ate t>e developerT 11K Distri<=te t>e report as soon as possi<leT 1&K (et t>e developer determine A>en t>e application is ready for revieAT 1%K )ail=re to attend or lac@ of preparation for t>e revieA is ca=ses for t>e revieA leader to cancel t>e revieA meetin9. <.12.; "alHt.ro-,. Proced-res 3or S-pervisors >e revieA process is a revieA amon9 peers. )rom a S=pervisory point of vieA t>e o<Fective of t>ese revieAs is to8 1K Move G=ality;control responsi<ilities to t>e pro9ram developers doin9 t>e Aor@T
Pa9e 0, of 114
PeopleSoft Application Development Standards &K %K 'K -K Cross;ed=cate developers so t>at development activities and pro9ress are o<served and =nderstood <y all team mem<ersT )oc=s individ=al creative ener9ies =pon t>e =sersM =niG=e application needs rat>er t>an =pon iss=es common amon9 =sers and already addressed <y t>e StandardsT Develop a >i9>ly;motivated comm=nity of application development professionals s=pportin9 one anot>er to <=ild inte9rated yet diverse applications Ait>in one consistent environmentT Determine A>et>er a neAly developed application meets Standards for transfer to prod=ction. AN APP$!CAT!ON MA( NOT 0E MO ED TO TRA!N!N% OR PRODUCT!ON "!T'OUT T'E CONSENT O3 RE !E"ERS. A standards compliance certification form m=st <e si9ned <y revieAers and @ept on file Ait> ec>nical Services.
Pa9e 01 of 114
"A$#T'ROU%' MOD!3!CAT!ON 3ORM APP(#CA #ON8CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC DE"E(OPE!8 CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC CHECV ONE8 CCC Desi9n !evieA CCC Code !evieA P!O+!AM
CCCCCCCCCCCC CCCCCCCCCCCC CCCCCCCCCCCC CCCCCCCCCCCC CCCCCCCCCCCC CCCCCCCCCCCC CCCCCCCCCCCC CCCCCCCCCCCC CCCCCCCCCCCC CCCCCCCCCCCC CCCCCCCCCCCC CCCCCCCCCCCC CCCCCCCCCCCC CCCCCCCCCCCC CCCCCCCCCCCC CCCCCCCCCCCC CCCCCCCCCCCC CCCCCCCCCCCC CCCCCCCCCCCC CCCCCCCCCCCC
MOD#)#CA #ON
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
COMP(E ED
CCCCCCCCCCCCCCC CCCCCCCCCCCCCCC CCCCCCCCCCCCCCC CCCCCCCCCCCCCCC CCCCCCCCCCCCCCC CCCCCCCCCCCCCCC CCCCCCCCCCCCCCC CCCCCCCCCCCCCCC CCCCCCCCCCCCCCC CCCCCCCCCCCCCCC CCCCCCCCCCCCCCC CCCCCCCCCCCCCCC CCCCCCCCCCCCCCC CCCCCCCCCCCCCCC CCCCCCCCCCCCCCC CCCCCCCCCCCCCCC CCCCCCCCCCCCCCC CCCCCCCCCCCCCCC CCCCCCCCCCCCCCC CCCCCCCCCCCCCCC
(EADE!
!ECO!DE!
MEM:E!
Pa9e 0& of 114
Pa9e 0% of 114
%. '. -. *. 0. 3. 4.
1,. Doc=ment !epository for reference <ot> d=rin9 t>e proFect and after t>e proFect >as <een closed 11. :riefin9s as sc>ed=led in t>e mont>ly ProFect :riefin9 for=m of proFect mana9ers. pro9ram mana9ers. A"Ps. and t>e C#O.
Doc-ments4 Ao types of Doc=ment (i<raries can created =nder Doc=ments8 1. Doc=ment (i<rary to contain des@top doc=ments s=c> as $ord or E?cel &. H M( (i<rary to contain >tml doc=ments. >e proFect mana9er can dynamically create doc=ment li<raries as reG=ired. Pict-res contain Pict=re (i<raries. $ists contain primarily E?cel lists A>ic> can <e maintained eit>er an attac>ed E?cel file. or <y a datas>eet editor Ait>in t>e EPM tool itself. Disc-ssions are =sed to create topics and trac@ correspondence pertainin9 to a partic=lar topic. >is alloAs correspondence to <e 9ro=ped to9et>er and prevents =sers from >avin9 to di9 t>ro=9> email >istory to find relevant email. S-rve@s can <e created to poll =sers to t>e Ae< site. >e middle of t>e Ae< site is simply doc=ments or lists t>at are most freG=ently =sed. >is area is can <e confi9=red <y t>e proFect mana9er. >e ri9>t side can also contain doc=ments or lin@s for G=ic@ reference. Under lin@s. it is possi<le to add a lin@ to a MicroSoft ProFect. >is reG=ires t>at t>e proFect <e created in MicroSoft ProFect Professional and t>en mi9rated to t>e EPM proFect server. )or instr=ctions on >oA to =se t>e EPM Ae< site. contact t>e man9er of #. . $e< ProFect team.
Pa9e 0- of 114
1*.2.1 Demand Mana,ement Demand Mana9ement consists of 1. &. Opport=nities and Needs ProFect Plannin9 Creatin9 opport=nities and need definitions and assessment Definin9 t>e scope of t>e proFect. develop t>e ProFect C>arter. Statement of $or@. ProFect :=d9et. ProFect Sc>ed=le. Approval of ProFect. Approval of ProFect )=ndin9.
1*.2.& ProBect Deliver@ ProFect Delivery consists of 1. &. %. '. -. Analysis Desi9n Constr=ction estin9 #mplementation Developin9 !eG=irements Definitions. Comm=nication !eG=irements. doc=mentation !eG=irements. rainin9 !eG=irements. and S=pport !eG=irements. Creatin9 Sol=tion Desi9n. Conversion Desi9n. Comm=nications Desi9n. rainin9 Desi9n. and S=pport Desi9n Sol=tion Development. Developin9 Unit est Plans. Develop drafts for Comm=nication. rainin9. and S=pport #ncl=des Pilot rainin9. #nte9ration estin9. System estin9. User Acceptance estin9 and refinin9 doc=mentation on Comm=nications. rainin9. and S=pport. #ncl=des !eadiness Assessment. #mplementation Approval. S=pport staff s>o=ld <e trained as Aell as end =sers. Post implementation tas@s incl=de proFect eval=ation and lessons learned.
1*.2.1 S-pport S=pport consists of 1. #ss=e #dentification and Escalation #ss=es are PrioritiEes. Sol=tions are tested and doc=mented. #ncl=des C>an9e Mana9ement and S=pport Development.
Pa9e 0* of 114
1*.9.1. ProBect C.arter >e ProFect C>arter contains t>e folloAin9 information8 E?ec=tive S=mmary :=siness Case Scope of $or@ Ot>er #nformation MaFor Milestones Or9aniEation :=siness OAners c=stomers A>o Aill <e mana9in9 proFect D are most affected <y t>e proFect. ProFect Sponsors individ=als providin9 financial. material. or staff reso=rces for t>e proFect. Pro9ram Mana9er individ=al responsi<le for f=nctional or9aniEation and =ltimate acco=nta<ility for t>e proFect. ProFect Mana9er person responsi<le for mana9in9 t>e proFect6s activities and delivera<les. eam Mem<ers individ=als or roles needed on t>e team. Sta@e Holders individ=als or or9aniEations A>o may <e impacted <y t>e proFect. S=mmary :=d9et ProFect :=d9et !ec=rrin9 Costs :=d9et Approvals :=siness OAner ProFect SponsorJsK Pro9ram Mana9er ProFect Mana9er ProFect templates can <e provided <y t>e #. . ProFect eam. 1*.9.2 Comm-nication Plan HoA Aill correspondence specific to t>e proFect <e comm=nicated to team mem<ers. proFect mem<ers. =ser comm=nity. e?ternal entities. etc.HP $>at forms of comm=nication need to ta@e place and for A>ic> 9ro=psH JneAsletters. neAspapers. emails. disc=ssion for=ms. list servs. etc.K 1*.9.9. Doc-mentation Plan $>ere Aill doc=mentation resideH $>at directory str=ct=res need to <e created and >oA Aill t>ey <e desi9ned for easy navi9ationH $>ic> doc=ments are reG=iredH JProFect c>arter. proFect iss=es. maFor milestones. analysis doc=mentation. f=nctional specs. tec>nical specs. <=siness process specs. etc.K $>at form Aill doc=ments <e retained J$ord. PD). E?cel. PoAerPoint. etc.K Are standardiEed form doc=ments reG=iredH #s a proFect Ae< site reG=iredH HoA Aill revisions to t>e proFect <e doc=mentedH HoA Aill approvals <e doc=mentedH 1*.9.:. Trainin, Plan Separate rainin9 plans may <e reG=ired for t>e folloAin9 9ro=ps of people8 ProFect team Analysis eam Development eam estin9 eam S=pport eam
Pa9e 00 of 114
End =sers
>e trainin9 plan addresses $>at 9ro=ps need to <e trainedH $>at type of trainin9 Aill eac> 9ro=p reG=iredH $>o Aill cond=ct trainin9H $>at trainin9 materials are reG=iredH $>at trainin9 media s>o=ld <e =sed Jcomp=ter <ased trainin9 JC: K. instr=ctor led trainin9. Ae<casts. etc.K #s e?ternal trainin9 reG=iredH $>at are t>e costs associated Ait> trainin9H 1*.9.; S-pport Plan >e S=pport Plan addresses iss=es of providin9 contin=al s=pport after t>e proFect is implemented. HoA Aill s=pport iss=es <e reported and to A>omH HoA Aill s=pport iss=es <e doc=mentedH HoA Aill s=pport iss=es escalate in priorityH $>ere s>o=ld s=pport staff <e locatedH $>at tools or eG=ipment Aill s=pport staff reG=ireH $>at trainin9 Aill s=pport staff needH
Pa9e 03 of 114
11. SECUR!T(
11.1 0AC#DOOR PO$!C( 3OR PRODUCT!ON AND REPORT!N% DATA0ASES
:ac@door access to prod=ction data<ases is limited to developers. tec>nical mana9ers and D:As. :ac@door access may <e provided to % rd party application data<ases <=t reG=ire approval and contin=al s=pervision <y t>e tec>nical application s=pport mana9ers. No f=nctional person Aill >ave <ac@door access to t>e data<ase. Developers and tec>nical mana9ers Aill >ave read;only access to t>e prod=ction data<ases. Access to a non; prod=ction data<ase Aill <e determined <y t>e tec>nical mana9ers and access 9ranted t>ro=9> t>e D:A 9ro=p. #f a prod=ction o<Fect needs to <e =pdated via t>e <ac@end. t>e developer Aill reG=est t>e c>an9e via S A and t>e D:A Aill e?ec=te t>e c>an9e. #f t>e e?pected res=lts of t>e script do not matc> t>e mi9ration form res=lts. t>e D:A Aill inform t>e developerBtec>nical mana9er and t>e D:A Aill not commit t>e c>an9e to t>e prod=ction data<ase =ntil t>e reG=estor >as validated t>e res=lts.
11.2 USER!D
User #D creation and creation of t>e initial temporary passAord is an a=tomated process for H! and SA applications. H! >as a c=stom process A>ic> r=ns ni9>tly to create neA =serids for neA employees. NeA =serids are not created for ret=rnin9 employees. retirees. or for st=dents or persons of interest A>o are <ecomin9 employees. >e H! create =serid process assi9ns one sec=rity role to alloA t>e employee access to employee self;service P.A.S.S. An email is sent to t>e employee notifyin9 t>em of t>eir neA =serid and temporary passAord. >e SA application =ses a PeopleSoft delivered process called mass c>an9e to create neA =serids for st=dents. #t does not create a =serid if t>e person already e?ists in t>e system. #t assi9ns defa=lt roles for self;service access. >e sec=rity administrator for t>e )S application man=ally creates neA =serids in )S. >e PeopleSoft Sec=rity Administrators are responsi<le for r=nnin9 t>e H! and SA ni9>tly processes. >e H! ni9>tly process also resets t>e description on =serprofile to matc> t>e person6s primary name in PeopleSoft. >is is done to facilitate searc>es for a person6s =serid.
Pa9e 04 of 114
11.9.&. C.an,in, Pass/ords After t>e =ser receives t>eir neA User #D and passAord. it is t>eir responsi<ility to c>an9e t>e passAord. NeA =sers s>o=ld >ave read and si9ned t>e University of Ho=ston Confidentiality Statement +=idelines. >e PeopleSoft Sec=rity Administrator Aill @eep a si9ned confidentiality statement on file for eac> =ser t>at >as <een 9iven access to PeopleSoft applications.
Pa9e 3, of 114
PassAord c>an9es are made <y clic@in9 on RMy System ProfileS on t>e main men=.
Pa9e 31 of 114
PeopleSoft Application Development Standards 11.9.1. 3or,otten Pass/ord 3-nctionalit@ )or9otten passAord f=nctionality >as <een added to PeopleSoft applications to alloA =sers to reG=est neA temporary passAords at t>eir convenience. >e passAord Aill <e emailed to t>e address A>ic> appears =nder t>eir sec=rity profile. 11.9.1.1. Pass/ord 'ints PassAord >ints are =sed in for9otten passAord f=nctionality. PassAord >int G=estions and ansAers may <e c>an9ed <y t>e end =ser as folloAs8 PassAord >ints may <e c>an9ed <y clic@in9 on RMy System ProfileS on t>e main men=.
Pa9e 3% of 114
Select A>ic> G=estion is to <e as@ed <y clic@in9 on t>e doAn arroA of t>e list <o?. >en enter t>e ansAer to t>e G=estion =nder response. >e =ser Aill <e e?pected to enter t>e response A>en =sin9 for9otten passAord.
PeopleSoft Application Development Standards 11.9.1.1. Usin, 3or,otten Pass/ord Clic@ on R!eG=est A NeA PassAordS on t>e PeopleSoft lo9on pa9e.
Enter t>e ansAer to t>e passAord >int and clic@ on REmail NeA PassAordS.
Pa9e 3- of 114
An email Ait> t>e neA passAord Aill <e emailed to t>e =ser.
>e neA passAord is app messa9ed from t>e application data<ase to t>e portal data<ase. >is normally ta@es one min=te. <=t if t>e G=e=e is <ac@ed =p. it co=ld ta@e several >o=rs.
Pa9e 3* of 114
Pa9e 30 of 114
1&. DOCUMENTAT!ON
!ecommended practices for eac> type of doc=mentation Ait>in t>e PeopleSoft environment are disc=ssed <eloA.
Pa9e 33 of 114
1&.; PEOP$E0OO#S
People:oo@s are doc=mentation delivered Ait> t>e PeopleSoft prod=cts. >ey are availa<le online t>ro=9> t>e Help men= item. People:oo@s s>o=ld not <e =pdated directly. since t>ey are replaced Ait> neA releases from PeopleSoft. Additional doc=mentation s>o=ld <e incl=ded in t>e =ser6s 9=ide or t>e tec>nical reference. >e direct lin@ to People:oo@s is located at >ttp8BBAAA.=>.ed=Binfotec>Bp>pBtemplate.p>pHnonsvcCidI--0
Pa9e 34 of 114
PeopleSoft Application Development Standards 1&.+.1 Application Desi,ner All Application Desi9ner o<Fects >ave properties J)ile O<Fect PropertiesK consistin9 of Description. Comments. OAner;id. (ast Updated DateB ime. (ast Updated User. Enter t>e Description and Comments on all c=stom o<Fects and =pdate t>e Comments on all modified delivered o<Fects. Comments s>o=ld descri<e t>e p=rposeBf=nction of t>e o<Fect. Note t>at t>e Edit )ind O<Fect !eferences feat=re is a G=ic@ Aay to find relations>ips <etAeen different o<Fects. >e folloAin9 list incl=des some of t>e o<Fects A>ic> can <e opened <y Application Desi9ner. Activity App En9ine Pro9ram Approval !=le Set :=siness #nter(in@ :=siness Process Component Component #nterface )ield a)ile ; O<Fect Propertiesb s=pport translate val=es for c>aracter fields of siEe ' or less )ile (ayo=t H M( #ma9e Men= Messa9e Messa9e C>annel Messa9e Node Pa9e a"ieA "ieA Pa9e PeopleCodeb s=pports field level edits ProFect !ecord a"ieA ; Edits Displayb and a"ieA ; PeopleCode Displayb s=pport field level edits S1( Style S>eet 1&.+.& Process Sc.ed-ler Mana,er >e s>ort description field is displayed to t>e end =ser A>en t>ey sc>ed=le a process and s>o=ld contain a title or description of t>e process t>at is <ein9 r=n. O<Fects t>at can <e defined in t>e Process Sc>ed=ler are s>oAn <eloA. >ave a description field. Process ype Definitions Process Definitions Z 5o< DefinitionsZ !ec=rrence Definitions Z Server Definitions Z !eport Node Definitions 5o< Definitions !ec=rrence Definitions Z Server Definitions Z !eport Node Definitions 1&.+.1 Tree Mana,er PeopleSoft provides delivered trees to provide or9aniEational str=ct=re and to mana9e processes. C=stom trees may also <e defined. Access +ro=p nodes >ave a description t>at can <e pop=lated =nder aEdit Datab. !ecord nodes do not. node description displayed in ree Mana9er comes from t>e record o<Fect properties. >e record >e Process Sc>ed=ler o<Fects mar@ed LZL
Pa9e 4, of 114
PeopleSoft Application Development Standards ree A description field can <e pop=lated =nder aEdit ree Definitionb. 1&.+.2 PS =-er@ UHS Developers s>o=ld =se t>e description and comments area =nder )ile Properties. 1&.+.9 C-be Mana,er >e C=<e Mana9er is a =tility t>at Aill alloA t>e creation of t>ree dimensional ta<les and is =sed for drill doAn and dia9nostic tec>niG=es. C=<e Mana9er provides description fields on t>e folloAin9 o<Fects8 Dimensions Definitions C=<e #nstances 1&.+.: Messa,e Catalo, >e messa9e catalo9 is a ta<le providin9 messa9es A>ic> can <e =sed for on;line and <atc> processes. #t can <e fo=nd in People ools. Messa9e Catalo9. PeopleSoft reserves messa9e sets from 1 to 14.444. UHS messa9e set n=m<ers s>o=ld <e &,.,,, or >i9>er. >e Messa9e Catalo9 provides a description field Ait>in t>e Messa9e Set.
Pa9e 41 of 114
Searc. Criteria Selectin9 t>e O<Fect Cross reference in t>e O<Fect #nventory men= Aill display t>e >omepa9e t>at contains lin@s t>at t>e =ser can select dependin9 =pon A>ic> o<Fects >eBs>e Aants to searc> =pon. Dependin9 =pon t>e o<Fects t>e lin@s are named say.
After t>e =ser selected t>e initial searc> criteria t>e =ser Aill <e prompted to limit t>e searc> <ased =pon fo=r criteria 1. &. %. '. O<Fect Name JpartialBf=ll name of t>e o<FectK Data<ase JpartialBf=ll name of t>e data<aseK System Name JpartialBf=ll name of t>e systemK (ast Update User #D JpartialBf=ll name of t>e User A>o last =pdated t>e o<FectK
>e system name denotes t>e <asic p=rpose of t>e data<ase A>et>er it is a St=dentBH! data<ase or )inancial data<ase so t>e e?istin9 system names S@stem Name St=dentBH! )inancial Name St=dent )inancial
Searc. ProBects User A>o Aants to searc> proFects s>o=ld clic@ on ProFects in t>e >omepa9e. Enter t>e additional searc> criterion A>ic> restricts t>e proFects A>ic> yo= are searc>in9. A 9rid <o? pop=lates Ait> all t>e proFects matc>in9 yo=r criteria. Select t>e desired proFect to find its detailed description.
Pa9e 4% of 114
After a partic=lar proFect >as <een selected. a pa9e Ait> n=m<er of ta<s opens =p. Eac> ta< si9nifies ProBect MenComponent Pa,e Record 3ield Details a<o=t t>e proFect selected (ists t>e men=s t>at are incl=ded in t>is proFect (ists t>e Components t>at are incl=ded in t>is proFect (ists t>e pa9es t>at are incl=ded in t>is proFect (ists t>e records t>at are incl=ded in t>is proFect (ists t>e fields t>at are incl=ded in t>is proFect
>e Associated E?ternal files in t>e proFect ta< lists all t>e e?ternal o<Fects t>at are incl=ded in t>is proFect li@e CO:O(6s. S1!6s. etc... #f yo= Aant to 9o any specific o<Fect Ait> in t>e proFect Jsay yo= Aant to @noA t>e details a<o=t a partic=lar men=Bcomponent... Ait>in t>e proFectK. Select t>e partic=lar O<Fects ta< Jsay Men= a<K. >e 9rid provides a +O O <=tton for eac> o<Fect A>ic> ta@es yo= to t>at partic=lar o<Fect.
>e Home lin@ on eac> pa9e ta@es yo= to t>e O<Fect #nventory >ome pa9e.
Pa9e 4- of 114
PeopleSoft Application Development Standards Searc. Men-s Users A>o Aant to searc> men=s s>o=ld clic@ on Men= in t>e >omepa9e. Enter t>e additional searc> criterion A>ic> restricts t>e men=s A>ic> yo= are searc>in9. A 9rid <o? pop=lates Ait> all t>e men=s matc>in9 yo=r criteria. Select t>e desired men= to find its detailed description.
After a partic=lar men= >as <een selected. a pa9e Ait> n=m<er of ta<s opens =p. Eac> ta< si9nifies MenComponent ProBect Descri<es t>e selected men= (ists t>e components t>at are incl=ded in t>is men= (ists t>e proFects t>at contain t>is men=
#f yo= Aant to 9o to partic=lar componentBproFect Ait>in t>e men= select t>e ComponentBProFect ta< and clic@ t>e +O O <=tton for t>e desired o<Fect. Searc. Components Users A>o Aant to searc> components s>o=ld clic@ on Component in t>e >omepa9e. Enter t>e additional searc> criterion A>ic> restricts t>e components A>ic> yo= are searc>in9. A 9rid <o? pop=lates Ait> all t>e components matc>in9 yo=r criteria. Select t>e desired component to find its detailed description.
Pa9e 4* of 114
After a partic=lar component >as <een selected. a pa9e Ait> n=m<er of ta<s opens =p. Eac> ta< si9nifies Component Pa,e ProBect Descri<es t>e selected component (ists t>e pa9es t>at are incl=ded in t>is component (ists t>e proFects t>at contain t>is component
#f yo= Aant to 9o to partic=lar pa9eBproFect Ait>in t>e component select t>e Pa9eBProFect ta< and clic@ t>e +O O <=tton for t>e desired o<Fect. Searc. Pa,es Users A>o Aant to searc> pa9es s>o=ld clic@ on Pa9e in t>e >omepa9e. Enter t>e additional searc> criterion A>ic> restricts t>e pa9es A>ic> yo= are searc>in9. A 9rid <o? pop=lates Ait> all t>e pa9es matc>in9 yo=r criteria. Select t>e desired pa9e to find its detailed description.
Pa9e 40 of 114
After a partic=lar pa9e >as <een selected. a pa9e Ait> n=m<er of ta<s opens =p. Eac> ta< si9nifies Pa,e Recor d 3ield ProBec t Descri<es t>e selected Pa9e (ists t>e records t>at are accessed in t>is pa9e (ists t>e fields t>at are accessed in t>is pa9e (ists t>e proFects t>at contain t>is pa9e
#f yo= Aant to 9o to partic=lar recordBfieldBproFect Ait>in t>e pa9e select t>e !ecordB)ieldBProFect ta< and clic@ t>e +O O <=tton for t>e desired o<Fect. Searc. Records Users A>o Aant to searc> records s>o=ld clic@ on !ecord in t>e >omepa9e. Enter t>e additional searc> criterion A>ic> restricts t>e records A>ic> yo= are searc>in9. A 9rid <o? pop=lates Ait> all t>e records matc>in9 yo=r criteria. Select t>e desired record to find its detailed description.
Pa9e 43 of 114
After a partic=lar record >as <een selected. a pa9e Ait> n=m<er of ta<s opens =p. Eac> ta< si9nifies Recor d 3ield ProBec t Descri<es t>e selected record (ists t>e fields t>at are contained in t>is record (ists t>e proFects t>at contain t>is record
#f yo= Aant to 9o to partic=lar fieldBproFect Ait>in t>e record select t>e )ieldBProFect ta< and clic@ t>e +O O <=tton for t>e desired o<Fect. Searc. 3ields Users A>o Aant to searc> fields s>o=ld clic@ on )ield in t>e >omepa9e. Enter t>e additional searc> criterion A>ic> restricts t>e fields A>ic> yo= are searc>in9. A 9rid <o? pop=lates Ait> all t>e fields matc>in9 yo=r criteria. Select t>e desired field to find its detailed description.
Pa9e 44 of 114
After a partic=lar field >as <een selected. a pa9e Ait> n=m<er of ta<s opens =p. Eac> ta< si9nifies 3ield Definition Names Translate val-es ProBect Descri<es t>e selected field (ists all t>e valid names for t>at field #f e?ists. lists t>e translate val=es for t>at field (ists t>e proFects t>at contain t>is field
#f yo= Aant to 9o to partic=lar proFect Ait>in t>e field select t>e ProFect ta< and clic@ t>e +O O <=tton for t>e desired o<Fect.
APPEND!7 0 K %lossar@
AP# :olt;On C=stomiEation Delivered En>ancement Modification #nte9ration estin9 P#A SOA S1A System estin9 Unit estin9 User Acceptance estin9 "anilla Application Pro9rammin9 #nterface. >is is t>e interface <etAeen PeopleSoft <atc> processes r=nnin9 on t>e Process Sc>ed=ler and t>e Process Monitor. >e AP# =pdates t>e process stat=s. #s a term A>ic> refers to f=nctionality. code. or o<Fects A>ic> are added to PeopleSoft delivered f=nctionality. code. or o<Fects. C=stomiEation refers to any R<olt;onS c>an9es to PeopleSoft applications. >ese Ao=ld incl=de neA o<Fects created <y UHS application developers. !efers to PeopleSoft delivered internal and e?ternal o<Fects. !efers to any improvement to t>e delivered prod=ct eit>er <y modification or c=stomiEation. Modification refers to modifyin9 a PeopleSoft delivered f=nctionality. code. or o<Fect. #nte9ration testin9 is testin9 a process and all =pstream and doAnstream processes t>at are affected <y or related to t>at process. >ese ot>er processes may incl=de data interfaces Ait> ot>er PeopleSoft applications or %rd party applications. PeopleSoft #nternet Arc>itect=re. P#As often refer to t>e vario=s set=p and confi9=ration reG=ired to r=n PeopleSoft on t>e Ae<. Service Oriented Arc>itect=re. >is refers to t>e overall application desi9n to <e en9ineered toAards meetin9 t>e service needs of t>e =sers. SoftAare 1=ality Ass=rance. !efers to t>e standards and practices to ens=re softAare G=ality ass=rance to t>e end =ser. System testin9 refers to testin9 all f=nctionality. <ot> delivered and <olt;on. #t incorporates inte9ration testin9 as part of t>e system test. Unit testin9 refers to testin9 an individ=al process or f=nction. User acceptance test is t>e final testin9 to <e cond=cted <y end =sers A>o =se t>e application. #s a term to reference =sin9 PeopleSoft o=t of t>e <o? as delivered Ait>o=t modification or c=stomiEation.
APPEND!7 C K Abbreviations
A::! AC ACAD ACC AC AC N ADD ADD! ADM AM ANN( APP( A!C ASSO A MP AU H :AC :A) A::!E"#A #ON ADD!ESS CON"E! E! ACADEM#C ACCOUN AC #"# 2 AC #ON ACC#DEN A( DEA H AND D#SA:#(# 2 ADD!ESS ADM#SS#ONS AMOUN ANNUA( APP(#CA #ON A!CH#"E ASSOC#A O! A EMP ED AU HO!#/A #ON :ACV :US#NESS A))A#!S
:A( :EN :#( :(D+ :O :A : H :UD :US CA( CAND C:E CD CH+ CH!+ C# C(ASS#) CMP CN C !( CN ! CN 2 CO( CO(( C$"! CO!!ES C!D C!S C ! C !2 C 2 CU!! C2 C2 D D: DD DEC#S DE( DE(#N1 DE(#" DEMO DEP DEP #D DESC D ( DE" D#SC D#SP D(2 DOC D D H E)) "
:A(ANCE :ENE)# S :#(( :U#(D#N+ :O OM :A CH :#! H :UD+E :US#NESS CA(CU(A E CAND#DAC2 C!ED# :2 E7AM#NA #ON CODE CHAN+E CHA!+E C# A #ON C(ASS#)#CA #ON CAMPUS COUN CON !O( CEN E! COUN 2 CO((E+E CO((EC #ONS CON !AC D $A#"E! CO!!ESPONDENCE C!ED# COU!SE COUN E! COUN !2 C# 2 CU!!EN CA(ENDA! 2EA! CA(ENDA! 2EA! O DA E DE:# DA2 DEC#S#ON DE(E E DE(#N1UENC2 DE(#"E!2 DEMO+!APH#CS DEPA! MEN DEPA! MEN #D DESC!#P #ON DE A#( DE"E(OPMEN D#SCA!D D#SP(A2 DA#(2 DOCUMEN A #ON DA E DEA H E))EC #"E
EMP( EMP(#D EN+( EN!(;CD EN!( E!S E HN E S E7EC )ED )#N )(D )(+ )$D )!M! )S )2 )2 D +EN +( +MA +PA +!AD +!AD +!D +!E +!P HD! HH H#S H(P H( H H! H!#S H!MS HS #D #D7 #N)O #N# #NS ( #NS CAD" #N ( #N" (ED+ () (#C (OC (SA ( D ( ! ("( MA#N
EMP(O2EE EMP(O2EE #D EN+(#SH EN!O((MEN CODE EN!O((MEN EMP(O2EE !E #!EMEN S2S EM E HN#C# 2 EDUCA #ONA( ES #N+ E7ECU #"E )EDE!A( )#NANC#A( )#E(D )(A+ )O!$A!D )O!ME! )#NANC#A( S2S EMS )#SCA( 2EA! )#SCA( 2EA! O DA E +ENE!A( +ENE!A( (ED+E! +!ADUA E MANA+EMEN +!ADE PO#N A"E!A+E +!ADUA E +!ADUA #ON +!ADE +!ADUA E !E1U#!EMEN +!OUP HEADE! HOU! H#S O!2 HE(P HEA( H HUMAN !ESOU!CES HUMAN !ESOU!CE #N)O!MA #ON S2S EM HUMAN !ESOU!CES MANA+EMEN S2S EM H#+H SCHOO( #DEN #)#E! #NDE7 #N)O!MA #ON #N# #A(#/E #NS A((MEN #NS # U #ONA( AD"ANCEMEN #N E!NA #ONA( #N"O#CE (ED+E! (E) (#CENSE (OCA #ON (A$ SCHOO( ADM#SS#ON ES (ON+ E!M D#SA:#(# 2 (E E! (E"E( MA#N ENANCE
MA5 M H MA7 M+ M#N M#N! MM MM MO MO! MS+ M D M H M H(2 NA ( N:! NCAA NME N7 O)C O)C! OP O!D O!P PA! PA2 PD PE! P+M PHONE P#N PM PO POS P!CS P!D P!E" P!) P!+E P!V P!OC P!OD P! PU! 1 D !A! !E) !E+ !E+ !EP !E1S !E1 !ESP
MA5O! MA HEMA #CS MA7#MUM MANA+EMEN M#N#MUM M#NO! M#NU ES MON H MON H MO!E MESSA+E MON H; O;DA E MON H MON H(2 NA #ONA( NUM:E! NA #ONA( CO((E+#A E A H(E #CS ASSOC#A #ON NAME NE7 O))#CE O))#CE! OP #ONA( O))#C#A( !EPO! #N+ D OP #ONA( !E #!EMEN P(AN PE!SONNE( AC #ON !E1UES PA2!O(( PA#D PE!SONNE( P!O+!AM E(EPHONE PE!SONA( #DEN #)#CA #ON NUM:E! PA2MEN PU!CHASE O!DE! POS# #ON P!OCESS P!ODUC #ON P!E"#OUS POS# #ON !E1UES )O!M PU!+E PA!V#N+ P!OCEDU!E P!ODUC #ON P!#N PU!CHAS#N+ 1UA! E!; O;DA E !E+#S !A #ON AND ACA !E)E!ENCE !E+#S !A #ON !E+U(A! !EP(2 !E1UES !E1U#!EMEN !ESPONS#:#(# 2
!E !+ !O C !P !S !S ! N SAA SA SCHED SCHO( SEC SE( SEM SESS S)A SM!2 SPC( SP! S!C S!CH S!"C SS SSN S S A S S A S D S D S P S U SU:M SU:M SU:S SUM SUM& SUM% SUM' SUM1 SUPP( SUSP S$ S2S ASP :( DA ECH ES MP OE)( O
!E U!N !#+H !ESE!"E O))#CE! !A#N#N+ CO!P !EPO! !ESE !ES A! !OU #NE S UDEN ACADEM#C AND ADM#N#S !A #ON SCHO(AS #C AP # UDE ES SCHEDU(E SCHO(A!SH#P SEC #ON SE(EC SEMES E! SESS#ON SCHO(A!SH#PS AND )#N#NC#A( A#D SUMMA!2 SPEC#A( SP!#N+ SOU!CE SEA!CH SE!"#CE SECONDS SOC#A( SECU!# 2 NUM:E! S A E S A US S !EE S A #S #CS S ANDA!D SHO! E!M D#SA:#(# 2 S OP S UDEN SU:M#SS#ON SU:M# SU:S#D#A!2 SUMME! SUMME! ## SUMME! ### SUMME! #" SUMME! # SUPP(EMEN SUSPENSE S$# CH S2S EM EN HS O) A SECOND E7AS ACADEM#C SV#(( A:(E A7 DE)E!!ED ANNU# 2 ECHN#CA( ES #N+ EMPO!A!2 ES O) EN+(#SH AS A )O!E#+N (AN+UA+E O A(
!ACV !A#N !ANCODE !N !NSCP !S U# UH UHC UHD UHS UH" "A "CH! "E "#O( $#P $V(2 $PE $ HD!$ 7)E! 7M# 2!(2 2 D 22 2222
!ACV#N+ !A#N#N+ !ANSAC #ON CODE !ANSAC #ON !ANSC!#P EACHE! !E #!EMEN S2S EM U# #ON UN#"E!S# 2 O) HOUS ON CEN !A( UN#"E!S# 2 O) HOUS ON C(EA! (AVE UN#"E!S# 2 O) HOUS ON DO$N O$N UN#"E!S# 2 O) HOUS ON S2S EMS UN#"E!S# 2 O) HOUS ON "#C O!#A "E E!ANMS ADM#N#S !A #ON "OUCHE! "E E!AN "#O(A #ON $O!V #N P!OCESS $EEV(2 $!# #N+ P!O)#C#ENC2 $# HD!A$A( !ANS)E! !ANSM# 2EA!(2 2EA!; O;DA E 2EA! & D#+# 2EA! ' D#+#
:=ndles. maintenance pac@s. and releases Aill <e displayed for t>at prod=ct line <y G=arter. 2o= can clic@ on t>e year ta< and retrieve t>e com<ined list for all G=arters.
Clic@ on RApply to !eleaseS to doAnload patc>es. <=ndles. maintenance pac@s. Clic@ on R a? UpdatesS to doAnload payroll ta? =pdates.
Enter t>e report id if @noAn. Ot>erAise. yo= can searc> for all patc>es. <=ndles. maintenance pac@s. or ta? =pdates t>at >ave <een released. >ese can <e doAnloaded to t>e Aor@station. >is process is normally performed <y a D:A.
Select RCreate NeA S=pport CaseS to open a neA case. PeopleSoft Aill email yo= Ait> t>e name of t>e s=pport person and t>e case n=m<er. Select RMana9e E?istin9 CasesS to revieA cases already filed Ait> PeopleSoft.
PeopleSoft can comm=nicate to A>oever opened t>e case eit>er via email or <y addin9 notes to t>e case itself Ait>in C=stomer Connection.
APPEND!7 % KK People0ooHs
People:oo@s provides >elpf=l f=nctional and tec>nical doc=mentation for PeopleSoft applications. #t addresses items from application set=p. processes. confi9=ration. etc. o vieA People:oo@s clic@ on t>e folloAin9 lin@8 >ttp8BBforna?.fast.=>.ed=83,3,Bpeople<oo@sBinde?.>tml
>is lin@ Aill provide access to a variety of People:oo@s A>ic> are stored in pdf format as s>oAn <eloA. Clic@ on t>e lin@ of interest and t>e People:oo@ Aill open =p.
$>en clic@in9 on one of t>e People:oo@ lin@s. anot>er set of lin@s related to t>at area open =p. #n t>e e?ample to t>e ri9>t. t>e H!MS People:oo@ Aas opened.
Upon clic@in9 on one of t>e lin@s a<ove. t>e People:oo@ pdf opens. 2o= can <roAse t>e ta<le of contents. refer to t>e inde?. or searc> on @ey Aords.
col=mn % col=mn ' col=mn col=mn * col=mn 0 ???????????????????????????????????????????? 444.444.44 ;444.444.44 ;444.444.44 ;444.444.44 ???????????????????????????????????????????? 444.444.44 ;444.444.44 ;444.444.44 ;444.444.44 ???????????????????????????????????????????? 444.444.44 ;444.444.44 ;444.444.44 ;444.444.44 444.444.44 ;444.444.44 ;444.444.44 ;444.444.44 444.444.44 ;444.444.44 ;444.444.44 ;444.444.44 444.444.44 ;444.444.44 ;444.444.44 ;444.444.44 )n!"er9! > Repor Repor Repor Of T! T! T! Hou9 on &>9 em le le 4 le 5 Pa:e= nnn
E5ample & s.o/s report in report form Repor I/= CCCCCCCC Run +a e= mm1//1>>>> Run T!me= hh=mm=9
(u9' )n! = CCCCC CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC +ep = CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC Col=mn 1 col=mn & ????????? mmBddByyyy ????????? mmBddByyyy ????????? mmBddByyyy Dept otals8 :=s Unit otals8 +rand otals8 col=mn % col=mn ' col=mn ???????????????????????????????????????????? 444.444.44 ;444.444.44 ???????????????????????????????????????????? 444.444.44 ;444.444.44 ???????????????????????????????????????????? 444.444.44 ;444.444.44 444.444.44 ;444.444.44 444.444.44 ;444.444.44 444.444.44 ;444.444.44 col=mn * col=mn 0 ;444.444.44 ;444.444.44 ;444.444.44 ;444.444.44 ;444.444.44 ;444.444.44 ;444.444.44 ;444.444.44 ;444.444.44 ;444.444.44 ;444.444.44 ;444.444.44