search cancel

Orphan OBS Unit/Node Not Displaying in the Classic UI

book

Article ID: 258215

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

OBS unit(s) do not display in the Classic UI via Administration > Organization and Access > OBS > Organizational Breakdown Structures > [obs] > Units

When querying the database, the record does show, but not in the expected branch level.

Environment

Release : 16.0.1

Cause

There is a third party integrator that inserts records into the PRJ_OBS_TYPES and PRJ_OBS_UNITS tables.
This is what the UI uses to display the current obs assocations, however is not easy to see the path.

select
O.id, O.name OBSNAME, O.UNIQUE_NAME, O.IS_SECURITY, O.LAST_UPDATED_DATE OBS_LUD,
O.LAST_UPDATED_BY OBS_LUB, OU.ID unitid, OU.TYPE_ID, OU.UNIQUE_NAME, OU.PARENT_ID, OU.NAME UNITNAME, OU.DEPTH,
Ou.LAST_UPDATED_DATE OU_LUD, ou.last_updated_by ou_lub
FROM
PRJ_OBS_TYPES O,
PRJ_OBS_UNITS OU
where 1=1
and O.id = OU.TYPE_ID
and O.id = 5xxxxxx
   order by OU.TYPE_ID, OU.ID

Resolution

Run the Datamart Extraction job to see review the OBS paths.

1. Run the Datamart Extraction job.

2. Use the following query to review the unit branches

SELECT n.PATH, U.NAME, n.*
FROM nbi_dim_obs n, prj_obs_units u
WHERE n.obs_unit_id = u.ID
and N.OBS_TYPE_ID = 5xxxxxx
order by n.obs_unit_id 

3. Move the orphan node(s) to the needed unit path.

4. Rerun the Datamart Extraction job. Rerun the query to review if the nodes are in the correct node level.