PeopleSoft Learning

Jobcode in the Position data Management in Peoplesoft.
You can associate an jobcode to an position number only when the position management indicator for Job code is selected. Business unit in the position management table should map to the SETID in the Jobcode table through the Set control recrod.

BENEFIT_NBR field is not implement in the peoplesoft base benefit records.
EMPL_RCD in the Base Benefit Tables doesn't store EMPL_RCD instead store the Benefit record Number and Benefit number (BENEFIT_NBR) field in these records are dummy ( not implemented )and they always store zero. It's seems to be some sort of the design flaw in the Peoplesoft.

All the Base Benefit (Benefit Program participation , Health Benefit ..etc )
record's schema shows that it is keyed by EMPL_RCD. This is not logically or functionally accurate. Throughout all of Base Benefits, when in the context of benefit enrollment, EMPL_RCD must be interpreted as an alias for BENEFIT_RCD_NBR. All benefit enrollment-related records are logically keyed by BENEFIT_RCD_NBR, so here EMPL_RCD actually contains the value of the appropriate BENEFIT_RCD_NBR. It is CRITICAL that all joins, comparisons, and updates to this record be against BENEFIT_RCD_NBR. Thus a typical driving join for benefit participation is PS_PER_ORG_ASGN.BENEFIT_RCD_NBR = PS_BEN_PROG_PARTIC.EMPL_RCD, and a typical join for benefit enrollment is PS_PER_ORG_ASGN.BENEFIT_RCD_NBR = PS_HEALTH_BENEFIT.EMPL_RCD. The security and search views used in Base Benefits perform this "mapping" internally.

PER099 - Employees Record

PER099 - This Application Engine program re-fresh the snapshot of the employee data stored in the in PS_EMPLOYEES table and PS_EMPLOYEES_LNG

Employee - EMPLOYEES is a table populated by PER099 AppEngine process.

It is a snapshot of emploees' personal/demographic data, employment data, and job/salary data as of the date indicated when the program is run.

This table is primarily for reporting. Only employees with EMPL_STATUS (A,P,L,S,W) are included with all their EMPL_RCDs and the most current JOB row as of the ASOFDATE.

EMPLOYEES_LNG is the language record related to EMPLOYEES.

A related language record enables text fields on a table to be translated into various languages for use in other countries.

Note :- It is not preferred to modify these record during implementation. If you need custom fields for the reporting purpose create the child record with the same set of keys and the custom fields in to these and create Job process including the PER099 and custom process which populates custom field in the child record. Simple join on the Employees record and custom child record will give you all the fields for reporting purpose.

In the Installation table fill the the last assigned value with 9's.

Eg:- Last Employee ID Assigned field on the Last ID Assigned tab should be filled with only 9's.

(Applicable for most version of PeopleSoft HRMS 8 and for all version HRMS 8.3 and higher)

For these symptoms:

1. A user cannot view data that they have been granted access to on the Department Security Tree.

2. A user can view data they have not been granted access to on the Department Security Tree.

3. User is receiving "No Matching Entries Found" when using a search record

4. The PS_SCRTY_TBL_DEPT becomes empty

Here are the troubleshooting steps :

1. Have you run the app engine process HR_FASTVIEW (via Setup HRMS > Security > Department Security > Update Dept Security)?

2. Is the Update Row Level Security checkbox enabled when running the HR_FASTVIEW process (via Setup HRMS > Security > Department Security > Update Dept Security)?

3. Is the As Of Date designated on HR_FASTVIEW the same date as your current Department Security Tree?

4. Are the effective dates of your departments less than or equal to the effective date of your current Department Security Tree?

5. Does the SETID and TREE_EFFDT of your Department Security Tree appear via the following SQL after running HR_FASTVIEW -> SELECT * FROM PS_R_PER505 and is TREE_EFFDT equal to the effective of your tree via Tree Manager?

6. Is your Department Security Tree named "DEPT_SECURITY"?

7. If you've added a new department via the Department Table, have you also added it to the DEPT_SECURITY tree?

8. Do your users have the appropriate Row Security permission list assigned to their user profile (via PeopleTools > Security > User Profiles > User Profiles > General Tab > Row Security field)?

9. Does the Row Security permission list assigned to your user contain the appropriate setids and associated departments (the setid/departments per each department security tree that the user should have access to), and do the departments have Read/Write access (via Setup HRMS > Security > Department Security > Setup Security Access)?

10. If updating Fast Security, are all three checkboxes enabled via the Update Dept Security run control page (Re-Fresh Type 1, 2 and 3)?

11. Are there any departments via Setup HRMS > Security > Department Security > Setup Security Access (PS_SCRTY_TBL_DEPT) that do not exist on your department security tree (these need to be in sync)?

12. For an employee that isn't retrieved via Job Data (for example), sql PS_JOB for the employee (SELECT EMPLID, SETID_DEPT FROM PS_JOB WHERE EMPLID = 'xxx'). Does the employee's setid value in SETID_DEPT on PS_JOB equal the SETID of the department security tree(s) entered on the user's row security permission list (HRMS > Security > Department Security > Setup Security Access)?

A pay group consists of a group of employees who are paid together with the same pay characteristics ( pay period, same pay date, frequency, and so on). Pay group is used by payroll and payroll interface.

Although this information may seem specific to payroll processing - with either People Soft Payroll or your own system - you also need it for PeopleSoft Human Resources because it enables you to set up job records and Benefit program. serveral of the fields on the job data component contain default values that you specify on this table.

1)Employee Type Defualt
2)Default Benefit Program
3)Holiday Schedule.

Refresh Employee compensation

Workforce Administration, Collective processes, Refresh compensation, Refresh Employee Compensation.

Refresh Employee Compensation Process.

This process recalculates compensation based on the current values in the system and automatically populates the correct compensation amount by inserting a new job row (unless there is no change to an employee's compensation). The process replaces manual changes with the new default values.

The refresh employee compensation process executes the same steps as the default pay components button on the compensation page, but you can update several records at once.

1) Inserts a new job row when you click the add new effective Date options with the effective date you entered in the as of date field.
2) Updates the job that is effective as of date you selected in the As of Date field.
3) Updates any future rows (rows are considered to be future if they come into effect after the As of Date ) When you select the update future rows check box.

1) Peoplesoft Reporting
Connects 2 or more PS/Queries.
n level nesting,Schedulable.
Parent-Child relationships
Underlying structure for XML Publisher subreport support & XML Output.

2) PeopleSoft Query Access Services
Standard Web Services to run and create PS/Queries Planned for PT 8.50

How to choosse a particular reporting tool for developing the reports in Peoplesoft ?

What are the advantages / Disadvantages of
different Reporting Tools.

This picture gives information about which Reporting tool to be used based on the type of the report.

To make changes in the login page one has to change the signin.html page but all the text used by the .html is inside the text.properties

For miltilanguage instance it would be textXXX.properties

Example: To change the value of the login button from 'sign in' to 'developement' or something else one has to make changes in text.properties, signin.html & other few .html files refers text.properties for these values.

Unable to DrillDown in a nVision Report:

Set EnableDrillDownForFile=1 in the Process Scheduler Configuration File, then bounce & re-configure the process scheduler. This option will allow users to use the drill down option in the nVision report.

SQLNET.EXPIRE_TIME

Purpose

Use parameter SQLNET.EXPIRE_TIME to specify the time interval, in minutes, to send a probe to verify that client/server connections are active. Setting a value greater than 0 ensures that connections are not left open indefinitely, due to an abnormal client termination. If the probe finds a terminated connection, or a connection that is no longer in use, it returns an error, causing the server process to exit. This parameter is primarily intended for the database server, which typically handles multiple connections at any one time.


DEAD CONNECTION DETECTION

DCD is initiated on the server when a connection is established. At this time SQL*Net reads the SQL*Net parameter files and sets a timer to generate an alarm. The timer interval is set by providing a non-zero value in minutes for the SQLNET.EXPIRE_TIME parameter in the sqlnet.ora file. When the timer expires, SQL*Net on the server sends a "probe" packet to the client. (In the case of a database link, the destination of the link constitutes the server side of the connection.) The probe is essentially an empty SQL*Net packet and does not represent any form of SQL*Net level data,but it creates data traffic on the underlying proto .

If the client end of the connection is still active, the probe is discarded, and the timer mechanism is reset. If the client has terminated abnormally, the server will receive an error from the send call issued for the probe, and SQL*Net on the server will signal the operating system to release the connection's resources.