Update Orphan Org Units
- Last updated
- Save as PDF
Level: System Administrator
An Org Unit or cost center that no longer appears in the org hierarchy is deleted from Serraview when the next Org Unit Import is completed. The exception to this rule is where the missing Org Unit is referenced (linked) to one of the following:
- Workpoint
- Asset (Storage, Lockers & Carparks)
- Person
- Service Request
In this situation, the Org Unit (which may or may not have a cost center) is assigned a parent of "Orphan Org Units".
Orphan Org Units are also created when a parent Org Unit is missing from the org hierarchy, any child Org Units are automatically assigned a parent of 'orphan Org Unit'.
Orphan Org Units Impact on Serraview data
The following information explains the impact of Orphan Org Units on your Serraview data.
Data |
Impact |
Resolution |
---|---|---|
Person |
The association of people with an orphan cost center is normally short-term and temporary. |
Resolved when the next person Import is completed. The import will contain the new arrangement of cost centers in the org hierarchy. |
Service Requests |
A Service Request may be instigated by or linked to someone who subsequently becomes a member of an orphaned cost center but the impact of this situation is minimal. |
Resolved by managing the orphan Org Unit in the Configuration area or in the VBS. |
Assets |
Assets like car parks and storage may become associated with Orphan Org Units. |
Resolved by migrating the Orphan Org Unit. |
Workpoints/Allocations |
Sometimes workpoints are allocated to a cost center that becomes an orphan. This needs to be corrected to ensure the accuracy of VBS reporting.
|
Resolved by managing the orphan Org Unit in the Configuration area or in the VBS. |
Scenario Move Project or BOS Move Project |
An old Move Project is using the orphan Org Unit. |
Resolved by managing the orphan Org Unit in the Move Project. |