PeopleSoft Security Tables
PeopleSoft Security Tables
When conducting an audit of PeopleSoft, eventually you will need to run queries against the PeopleSoft
security tables. Listed below are the PeopleSoft delivered security table names, and a brief description of
the table contents.
PSOPRDEFN Operator ID and password information. Passwords stored are encrypted. Updated by
PSAUTHITEM Security Administrator.
PSAUTHSIGNON Menus, panels and items an Operator is authorized to access. Updated by Security
PSAUTHPRCS Administrator.
PSACCESSPRFL Records sign-on times for all Operators. Updated by Security Administrator.
PSOPRCLS Records process groups for all Operators. Updated by Security Administrator.
Security table used to allow a super-user to create an access profile that would
contain an Access ID and Access Password. Access ID and Passwords are used to
connect PeopleSoft to the underlying database. (only in version 7 and above)
Maps one Operator to multiple Operator Classes. (only in version 7 and above)
SECURITY SQLs
SQL to find out the users who have access to the page.
IN ('PV_ADM_SETUP_BU ',
'PV_ADM_SETUP_CODES',
'PV_ADM_ACCOUNTING ',
'PV_ADM_PROCUREOPTS',
'PV_ADM_VNDR ',
'PV_ADM_DEFINE_ITEM',
'PV_ADM_PROCU_USERS',
'PV_ADM_CATALOGS ',
'PV_ADM_MAIN2 ',
'PV_APP_MAN_PG ',
'PV_REQ_STATUS') ;
COMMIT;
SELECT *
FROM PS_DEPT_TBL E
Page:
begin-procedure Check-Combo
begin-SELECT
count(*) &count
FROM
ps_combo_data_tbl c
WHERE
end-SELECT
if &count = 1
else
end-if
end-procedure Check-Combo
How to Schedule a job from People Code (Education Cess will run 2 minutes after voucher post when the user
selects Voucher Post(FSTREAMLINE) from the Online page not by Navigation)
&RQST.ProcessName = "HEDCESS1";
&RQST.TimeZone = %ServerTimeZone;
&RQST.Schedule();
&PRCSSTATUS = &RQST.Status;
If &RQST.Status = 0 Then
&Inst = &RQST.ProcessInstance;
End-If;
End-If;
End-If;
Ideally, Canadian BU should point to CNSHR and all others should point to SHARE setid for
items.
Dynamic view is different from a SQL view because you need not build the view.
In dynamic view we cannot have EFFDT in a condition when it is a key field in the record that source the
view.
Where DERIVED is a Record name, can be used as a prompt table say %EDIT_ITEM_ID
If Prompt Table is some thing like %EDITTABLE30 means it is a dynamic prompt whose
prompt values are populated by PeopleCode. REQ_CNTRCT_SRH1, REQ_CNTRCT_SRCH
evaluate $Dbname
when = 'FNPRD84'
let $Mail_List = $Mail_List || '@hewitt.com'
let $Shell = 'mailx -s ' || $Subject || $Mail_List || ' < ' || $ROutPath
call system using $Shell #Unix_Status
break
when = 'FN84DEV'
let $Mail_List = $Mail_List || '@hewitt.com'
let $Shell = 'mailx -s ' || $Subject || $Mail_List || ' < ' || $ROutPath
call system using $Shell #Unix_Status
break
when = 'FN84QA'
let $Mail_List = $Mail_List || '@hewitt.com'
let $Shell = 'mailx -s ' || $Subject || $Mail_List || ' < ' || $ROutPath
call system using $Shell #Unix_Status
break
when = 'FN84SPRT'
let $Mail_List = $Mail_List || '@hewitt.com'
let $Shell = 'mailx -s ' || $Subject || $Mail_List || ' < ' || $ROutPath
call system using $Shell #Unix_Status
end-evaluate
PS_PO_ITM_STG
PS_PO_ITM_STG_VND
PS_PO_ITM_STG_UD
Subpage or Secondary
page ?
For your case, I don't see any usage of either of the pages as
you said its a custom component used to display multiple fields
information on several pages, I would go for a subpage having
key information displayed on the top of each page and then show
relevant information on subsequent pages.