PeopleSoft Learning

1) To establish reporting hierarchies, you will need to create a top position that reports to itself. Once you have created a hierarchy, you can run POS006A, Build Position Tree Structure Codes, so that you can generate the Indented Position Hierarchy report, POS006, to report on your organizational chart.

2) To establish a top position, add the position, save your entries, then enter the same position number in the Reports To Posn field and press Save again.

3) You can generate the Vacant Position Report (POS007), which shows all vacant budgeted positions in the system, and the Position Status Report (POS001), which lists all positions and their status.

4)To generate a list of positions in the system, you can run the Active/Inactive Positions Report, (POS002).
You can generate the Incumbent History (POS003) report, which lists current and former incumbents in all positions in the system, grouped by department.

5)You can generate the Active Position History report (POS004), which shows data on all active positions in the system. If you choose, the report generates job requisitions for all active, vacant, and approved budgeted positions. As you update data in fields that match in the Position Data and incumbent Job Data panels, periodically you will want to check the data to ensure the system contains the right information in both places.

6)You can run an SQR audit, POS008, to determine any data that does not match in the two panel groups.

When PeopleSoft is set up to manage the workforce by employee, job codes are utilized to classify job data in general categories, such as Administrative Assistant, or Sales Representative. Employees are linked to a job code on their job data records, where other distinguishing information about the employee’s job is entered as well. In this scenario, many employees share the same job code, even though they might perform their work in different departments, locations, or companies.

When PeopleSoft is configured to manage the workforce by position, job codes are still used for general classification, but positions are employed to uniquely identify each role associated with the job code. In this instance, a position associated with the Administrative Assistant job code might be an Administrative Assistant in the Marketing Department in Cupertino or an Administrative Assistant in the Human Resources Department in Houston. Basic information about the job, such as salary plan and EEO classification, remain the same for each of these positions, but other characteristics can be different, and these differences are indicated on the position record. Employees are linked to positions, and all of the data elements, both job code and position-related, are defaulted to their job data records. Positions usually have a one-to-one relationship with employees, unlike job codes, which generally have a one-to-many relationship.

Options

Implement Workforce by Employee
If the organization is fluid, a broader groupings of employees is utilized, and new jobs are often created—then driving the system by employee would be the optimum choice. This method is useful if for organizations expanding rapidly, or for organizations that often have new projects requiring the creation new jobs or job types regularly.

Implement Full Position Management
If the organization is fairly static, jobs and job descriptions are mostly fixed, and people move in and out of them—then driving the system by position would be the optimum choice. For example, government agencies and hospitals, which budget by position, often well in advance of filling them, find this method very useful.

Implement Partial Position Management
In order to reap the benefits of both worlds, PeopleSoft can be set to optimize partial position management. In some areas of the organization, driving the system by employee is preferred, while in other areas of the organization, the business process requires driving the system by position. For example, you might find that driving the system by position serves well for only some departments or management levels in the company, and that driving the system by employee works well for others. PeopleSoft Human Resources provides the flexibility to use both. By selecting a setting on the installation table called partial position management either method can be utilized.

Impact of Implement Workforce by Partial Position Management
· Maintenance: Requires set up and maintenance of positions for those employees hired or transferred into position managed departments.
· Conversion: With this option, employee data records do not have to be associated with positions prior to conversion. This impacts Tandem, Digital and ASD. Positions could be assigned to employees post-conversion.
· Upgrade to future versions: Not an issue as this is current PeopleSoft functionality.

1) Set Up HRMS, Security, Core Row Level Security, Security Tree Audit Report, Department Tbl & Departmental

Use to create a list of discrepancies between the data you've entered in the Departments component and the departments you've added to the current security tree.

2) Main Menu > Set Up HRMS > System Administration >Database Processes
ID Change / ID Delete process

Actions that trigger Future-Dated Security Rows
Setup HRMS >Security > Security Intall Settings Page
Select the actions that will trigger the SavePostChange PeopleCode in the components using the JOB record to create a future-dated security row in SJT_PERSON when they are used in a future-dated row in the Job Data pages. The system will not create security rows for future-dated rows with actions other than those listed here.
To create future-dated rows, you need to select the Include Future Dates check box on the Security Type Table. This enables you to use future-dated security for some security access types and not others.

What are iScripts ?
IScript is PeopleCode that has access to the Request and Response objects. Just like JSP and ASP, you, the developer, writes code to read parameters from the request and write information, data, etc to the response. Unfortunately, just like ASP, the response object's write methods only render text.
How do you create an IScript?
IScripts follow the same design pattern as FUNCLIBS. An IScript is a PeopleCode function stored in a record definition. The record definition name must start with WEBLIB_. The function can be in any field event of the record definition. By convention, we generally use the field ISCRIPT1 and the event FieldFormula. The function name, however, must start with IScript_ and cannot take any parameters or return a value.
How do you call an IScript?
IScripts can be called a number of ways. How you call it depends on the purpose of the IScript. If your IScript is a pagelet, then you will create a CREF for your IScript in the portal registry under Portal Objects > Pagelets. If your IScript is called from JavaScript (Ajax, etc), then you call your IScript using a URL like http://server:port/psc/site_name/portal_name/node_name/s/WEBLIB_name.FIELDNAME.FieldFormula.IScript_name. To make it easier, you can generate an IScript URL using the PeopleCode built-in function GenerateScriptContentURL.
What is the difference between iScript Peoplecode other Peoplecode ?
iScript Peoplecode cannot refer to the component specific methods , functions and system variables. iScript executes out side the scope of the component buffer and uses respone and request objects. Non-iScript peoplecode has access to component buffer and they are invoked according to component process flow. iScript functions is invoked direclty by url which has response to browser.
see Enterprise PeopleTools 8.49 PeopleBook: PeopleCode API Reference > Internet Script Classes (iScript)).
you might be interested in looking at some examples. Chris Heller posted a couple of IScripts that can be used as Bookmarklets.