|
|
|
|
|
What is a node and how do they relate to department ids?
Nodes are like folders which hold department ids. Nodes can also contain other nodes in a
hierarchical structure. The hierarchical structure of the finance department tree (bdxlate_deptid)
is as follows:
The highest level (or node) is the Amherst Campus.
The next level contains the executive area nodes followed by division nodes,
mbu nodes, department nodes, and finally the segment nodes.
It is the segment nodes that actually contain the department ids. In order to determine what department ids
belong to a particular department node, you must look at all the department ids in each of the segments
which are in that department node.
When discussing a department, it is important to be clear whether you mean department node(which
can contain many department ids) or a detail department id.
|
|
|
|
Do HR and Finance use the same department tree?
No. HR and Finance have their own distinct department trees, but they are syncronized as much as
possible at the department node level. HR uses a tree named dept_security and Finance uses the
bdxlate_deptid tree. The primary function of the dept_security tree, as the name implies, is to
control HR security. Timekeepers are assigned a group id which translates to a node on the
dept_security tree. Timekeepers have access to record time for all employees associated to the
deptids which are in their assigned group id’s nodes.
The bdxlate_deptid tree is used for budget translation (budgets can be at a higher level, such
as the MBU node, while actual expenses are incurred at the detail deptids) as well as security.
This tree is also used to summarize financial reports by “rolling-up” to higher nodes.
|
|
|
What do I need to consider when moving a node or detail deptid under a different node?
- Do you need to adjust Financial report security? (anyone that has access to the new parent
nodes will inherit access to the new deptid)
- Do you need to adjust PO Approval workflow? (anyone that has access to the new parent nodes
will inherit access to the new deptid)
- Do you need to adjust Time & Labor security?
- Are there any funds that budget at a level higher than the new node? (Ex. If you are moving
a Department Node under a new MBU Node, you should check for funds that budget at the MBU or
Exective Node so that these budgets are moved too.)
|
|
|
What do I need to consider when creating a new detail deptid in finance?
- Speedtypes need to be created for any funds that will be used in the deptid.
- If there will be payroll in the deptid then an HR Account code must be created and
a PA form submitted
with an effective date of the Monday after the first pay-period.
- Budgets must be loaded where appropriate.
- Ensure that finance security is configured so that the right people will be able
to view the financial reports. (anyone that has access to a parent node will inherit
access to the new deptid)
- Ensure that PO Approval is configured appropriately. (anyone that has access to a
parent node will inherit access to the new deptid)
- If any existing purchase orders should be paid out of the new deptid, then the POs
should either be closed out and re-entered with the new distribution, or the charfield
distribution should be changed.
|
|
|
What do I need to consider when inactivating a detail deptid in finance?
- If there is currently payroll in the deptid, then
a PA form needs
to be processed to replace the old HR Account code with a valid one. The effective
date should be the day after the first pay period of the new fiscal year*. (July 10th, 2007)
If necessary, HR can retroactively move the first nine days of payroll off the old department
and onto the new one. *-The effective date needs to be after the first pay period
because PeopleSoft splits the first pay period between fiscal years. If the PA effective
date were 7/1, then when PeopleSoft split the payroll, charges would be posted to the new
deptid in the old fiscal year. And since the new deptid doesn't exist in the old fiscal
year, it will fail.
- Any automatic recharges should be stopped. (Telcom, Mail Services)
- If there are any existing purchase orders on any deptids being inactivated, then the POs should
either be closed out and re-entered with the new distribution, or the charfield distribution
should be changed.
- Budgets should be frozen. (after the above 2 steps are completed)
- Speedtypes and HR Account codes should be inactivated.
|
|
|
|
