Escolar Documentos
Profissional Documentos
Cultura Documentos
With the Manage Positions business process, you can create reporting relationships among positions,
showing how they look in hierarchical form. Use this information, either through a report or online, for
organizational planning.
Human Resources provides two ways to view positions in hierarchical form:
R By entering supervisory position numbers in the Reports ToPosn (position) field in the Position
Data - Description page, you can generate reports that show position hierarchies.
R If you want to see part of your organization chart online, use PeopleSoft Tree Manager to create
a position tree, which illustrates position hierarchies.
This section discusses how to:
R Establish position hierarchies in Position Data.
R Maintain position hierarchies in PeopleSoft Tree Manager.
When Position Management is set to O in the Installation Table and the Reports to Position
and the Supervisor ID fields contain values in Position Data, both fields appear in Job Data until you enter
a value in one or the other.
Currently, if you save a position without selecting a position number in the
O field, the
system issues a warning message. pou don¶t have to enter a position number after you acknowledge the
message. But if you want to require this field for all positions, change the warning message to an error
message. The system won't allow you to save the data without an entry in this field.
Review the PeopleSoft Tree Manager documentation for a full, detailed discussion about
PeopleSoft Tree Manager before you attempt to modify or create Position Trees.
This section discusses using PeopleSoft Tree Manager to define and maintain Position Trees in Human
Resources but is an exhaustive discussion about the use of PeopleSoft Tree Manager.
Within PeopleSoft Tree Manager you can also view incumbent and position data in the context of the
department or other part of the organization you¶re viewing. To do so, click a position number to display
the Position Data pages.
PeopleSoft recommends that you use the Tree Manager for position trees only if your company is
small or, if your organization is large, you plan to only represent a few levels of management. pou can
also create separate position trees that incorporate small portions of your organization. Otherwise,
generate the report, POS006, to manage and view your reporting hierarchies.
!
"#
$
#
$
!
"#$
%
s s
Once you¶ve created the basic tree structure, add the nodes. In a position tree, each node represents a
position, defined on the Position Data table. The first node is known as the root node, and is the highest
level in the hierarchy or reporting structure.
s
O O
O
h
s
Once you enter all the reporting relationships among positions, run the Build Position Structure SQR to
link the positions in the system and create an organizational hierarchy. Run this utility at the following
times:
R When you first enter the reporting relationships.
R Any time that you add new positions.
R When you change reporting relationships among existing positions.
pou can generate a report listing the relationships in an indented organizational chart format, the
Indented Position report.
This section discusses how to run the Organizational Structure Report.
s sh
s
()
*
$
!,&( & (
-
# $
*
/$
+
.
# 0(112&3 /$
'
(
-
#*
()
#
$
$
!,(112 (
-
# $
(
-
0(1123
(
-
.
#
$ + (
-
#
(
-
$ # #
#
-
0/$3
&
*
Y
!!"#s
$c ss
After you enter all the reporting relationships among positions in the Position Data component, run this
SQR. The Build Position Structure report enters a value in the ORG_CODE field and defines the position
in the hierarchy. When you run the Build Position Structure report the system updates the position
structure with data valid before or on the As of Date you specify.
pou should run this report when you first enter the reporting relationships, any time you add new
positions, and when you change reporting relationships among existing positions. pou must run this SQR
before you can run the Indented Position Hierarchy report, POS006.
When you run Build Position Structure, the system may generate one or more diagnostic messages to
help you understand the utility output. They are as follows:
R If the utility doesn't find a root position (a position that reports to itself), it displays an error
message. If you do not have a root node, the utility can not produce a report.
R If you have circular reporting conditions, such as when position 1 reports to position 2, and
position 2 reports to position 1, the utility displays a warning message and the positions will not
appear in the report.
R If you do not have data in the Reports To Position field for a position, the utility displays a warning
message. These positions will not appear in the report.
s
E!%%#c
&s$ s
The report provides the following information regarding the origin of the seniority rate code:
R If the worker receives a seniority pay component as a result of belonging to a group associated
with a seniority rate code, the report displays the corresponding group ID for the seniority rate
code.
R If a worker receives the seniority pay component because the seniority rate code is associated
with all workers, the report displays as the origin of the seniority rate code.
R If a worker receives the seniority pay component because you manually added it, the report
displays
as the origin for the seniority rate code.
s
Administering Seniority Pay
s
Managing Citizenship and Visa or Permit Information
The Supervisor Level tree that the system uses for sorting is the one used for the Appointment
Notification and Appointment List reports. It must be named SUPERVISOR_LEVEL if the system is to use
it. If you have not defined a Supervisor Level tree with that name, sorting will be in alphanumeric
supervisor level order.
!!-#Ex(
0 $c ss
pou can print incumbent job data where you have prevented automatic cross-updating from occurring
(overrides), or you can print only exceptions where the incumbent job and position data is out of sync for
other reasons (exceptions).
The Exception/Override report lists the position name and the name of the worker assigned to the
position and shows the data in the fields that match in the Position Data component and Job Data
component. The report displays those workers whose HR Status is
or
O
When you run this report for exceptions and the Business Title in the incumbent Employment Data
doesn't match the Position Title in Position Data, the report prints an asterisk (*) next to the Position Title.
The report also prints
or
in the Mail Drop column, depending on whether the data is the
same in the incumbent job and position data.
s
Verifying Position Data
The FBT Reconciliation Report includes values calculated during the Package Expense
Calculation. To ensure that you get accurate totals included in the FBT Reconciliation report, execute the
Package Expense Calculation at the end of the FBT pear for which to run the FBT Reconciliation report.
pou must complete this before running the report.
s
Running Salary Packaging Reports
)!55$
2 2 s$c )
&s
The Organization and Group Goals report is an optional report that you can run before or after the goal
measurement period. This report provides the plan goal weights for the variable compensation plan ID
and period ID and a list of all organization and group weighted goals in the plan with their weighting
percent and attainment percent.
This report provides the following information:
R The Plan Goal Weights for the variable compensation plan ID and period ID.
R A list of all organization weighted goals in the plan with their weighting percent and attainment
percent.
R A list of all group weighted goals in the plan by group with their weighting percent and attainment
percent.
If the group does not have goals, the report indicates that the child group¶s goals are the parent group¶s
goals.
s
Running the Organization and Group Goals Report
s
Reporting on Award Payout and Distribution
s
O
O
s
O
O
!!,#
E0 $ ss
This report provides data about COBRA beneficiaries at the Event Level. The report will list all workers to
whom an event has occurred. The qualified status indicates whether the qualified beneficiary is Qualified
(QL), Not Qualified (NQ), Not qualified/duplicate (ND) or QE (Qualify Error).
s
O
O
!!6#
$ ss
This report displays information on: Employees enrolled in Active and COBRA Health Coverage;
Employee and Spouse (or other dependent) electing health benefits for the same Dependent ID; and
workers who have overage dependents.
pou can use this report to analyze whether there is an overlap in COBRA and Active coverage, whether
dependents are being covered by more than one EMPLID or whether an overage dependent has not
been detected.
s
O
O
!!-#
&s E $ ss
This report displays information about errors that result from running the COBRA process. The errors
include COBRA event conflict, no eligible benefit program or more than one eligible benefit programs, or
duplicate COBRA events.
pou can use the COBRA Administration Error Report to identify and troubleshoot errors that surface as a
result of COBRA processing. pou can also identify these errors online. pou might want to print the report
and request that staff check off each error as they determine a resolution, thereby creating an audit trail
for verifying that all errors have been analyzed.
s
O
O