View Only
  • 1.  Regarding OBS_Write.xml

    Posted Jul 25, 2017 12:16 PM



    We are updating the OBS using staging tables (data flushed into staging tables from external systems). We need the OBS to be only 3 levels deep.

    Some OBS are having 4th Level. How can I delete the 4th level using XOG?

    Any suggestions...




  • 2.  Re: Regarding OBS_Write.xml

    Posted Jul 25, 2017 01:59 PM

    The complete="true" argument in the OBS XOG write allows you to "delete" levels in an OBS, BUT we have to provide the complete view of the entire OBS in the XML (rather than just the changes).

  • 3.  Re: Regarding OBS_Write.xml

    Broadcom Employee
    Posted Jul 25, 2017 11:26 PM

    I would recommend to take OBS related table backup before perform activity.







  • 4.  Re: Regarding OBS_Write.xml
    Best Answer

    Posted Jul 26, 2017 02:27 AM

    Just wondering again if there is a simple way of seeing the fourth level units and then deleting t

    The GUI typically displays one parent and the immediate children. So you would have to navigate through all level 3 units in the GUI.

    Using the graphical OBS portlet would allow to pick all of them at once. See 

    If the staging tables store the info as parent child data that is not any easier to locate the units to be removed.

    The PRJ_OBS_UNITS has the level, but does not tell in which branch the unit to be deleted is.

    Combining that to the OBS path query would give the units fairly quickly if the results are filtered eg. in Excel. See

    Reporting: How to get the OBS path of a resource. 

    Once you got the units to be removed you would need the stripped xml.

    One way to do that is create the  xml from scratch.

    Because of the levels adding the tags is more complicated than in a case where there is just one level.

    You must have already  something for that if you are currently updating your OBS from the staging tables so the modification is less work. Further  you would have to modify your process for the future to transfer only three levels.

    The output from XOG read would serve also as a backup. One time to edit the file to remove all level four units (and below)  is not too much work if you already know which units and where they are.

  • 5.  Re: Regarding OBS_Write.xml

    Posted Nov 14, 2017 11:21 AM

    Thank you urmas.

    That helped a lot.

  • 6.  Re: Regarding OBS_Write.xml

    Posted Nov 15, 2017 04:05 AM

    Just wondering again...

    If that was the answer how did you apply it?

  • 7.  Re: Regarding OBS_Write.xml

    Posted Nov 15, 2017 04:33 AM
    1. We added another step to the existing process to find if any level 4 orgs being created (using the PRJ_OBS_UNITS table).
    2. If Yes, we de-associate the Projects to the OBS L1/L2/L3/L4 (using Project XOG) - This step is included because we cannot remove any OBS if it's linked to any Project/Resources
    3. Remove the L4 from the OBS Units (by creating an OBS XOG from the scratch)
    4. Update the Project(s) (obtained from step 2) OBS Association to L1/L2/L3

  • 8.  Re: Regarding OBS_Write.xml

    Posted Nov 15, 2017 04:46 AM


  • 9.  Re: Regarding OBS_Write.xml

    Posted Nov 15, 2017 04:55 AM

    You're welcome