Configure an Organizational Breakdown Structure

An Organizational Breakdown Structure (OBS) is a hierarchical representation of your company that you can use to align resources, projects, and investments. With an OBS, you can perform these tasks:
ccppmod1551
An Organizational Breakdown Structure (OBS) is a hierarchical representation of your company that you can use to align resources, projects, and investments. With an OBS, you can perform these tasks:
  • Categorize objects for filtering and reporting purposes.
  • Associate groups of resources with partitions.
  • Grant access rights to users for object instances based on their OBS membership.
You can define the type, level, and units of each OBS.
  •  
    OBS Type: 
    Specifies the type of OBS. For example, an OBS named Location defines an OBS type for geographical locations.
  •  
    OBS Levels: 
    Specifies the structure of the OBS hierarchy. For example, a location OBS can have Country as level 1, State as level 2, and City as level 3.
  •  
    OBS Units: 
    Specifies a unit in the OBS hierarchy. For example, a location OBS can use the names of countries, states or regions, and cities as OBS units. An OBS unit can be an ancestor, descendant, or both in relationship to other OBS units.
    OBS unit, department, and location names cannot contain the following special characters:
    • Slash (/)
    • Colon (:)
    • Double quotes (")
    • Less than (<)
    • Greater than (>)
 
 
2
 
 
OBS Example
The following image shows a location OBS with levels and units in each level.
Image showing a location OBS with levels and units in each level
Image showing a location OBS with levels and units in each level
As shown in the following table, you can set up a financial or non-financial OBS:
 
Set Up a Financial OBS
 
 
Set Up a Non-Financial OBS
 
Set Up a Financial OBS
Review the Prerequisites for Creating a Financial OBS
To complete the steps in this article, you need the following access rights:
  •  
    Administration - Access
     
  •  
    Administration - Application Setup
     
  •  
    Financial Maintenance - Financial Organizational Structure
     
  •  
    Department - Create
     
  •  
    Location - Create
     
  •  
    Object Administration
     
  •  
    Administration - XOG
     
Video: Why Are Attributes Deleted When Creating a Financial OBS?
The following video is provided by CA Technologies.
 

 
 To play this video in full-screen mode, click the YouTube logo at the bottom. 
Create Department and Location OBS
Create an OBS to define levels and units that are associated with the organization. The following OBS types are used for financial planning:
  •  
    Department OBS
     which represents an organizational chart. 
    Clarity PPM
     administrators define the Department OBS type and its OBS levels. Department managers are primarily responsible for creating departments. When a department manager creates a department, an OBS unit is also created in the OBS hierarchy. The hierarchy is based on the selected entity and, optionally, a parent department.
  •  
    Location OBS
     which represents the geographical location of a department within an organization. A financial administrator is responsible for creating locations as part of the financial setup. When a location is created during the financial setup, an OBS unit is created in the OBS based on the selected entity.
In this article, create a financial Department OBS and a financial Location OBS with two levels. For example, create a financial Department OBS named CA Dept with Department at level 1 and Team at level 2. Similarly, create a financial Location OBS named CA Loc with Country at level 1 and State at level 2.
 
Follow these steps: 
 
  1. Click 
    Administration
    Organization and Access
    OBS
    .
  2. Click 
    New
    .
  3. Complete the fields in the 
    General Information
     section.
    Give the OBS a descriptive name that indicates how you plan to use it.
  4. Enter labels in the 
    Levels
     section.
  5. Perform one of the following steps:
    • To associate objects with the OBS, click 
      Save
    • To create another OBS, click 
      Save and Return
      .
Associate Objects with the OBS
Associate the objects with an OBS to enable the OBS capabilities, such as security or reporting for that object. Although you can associate a custom object with the Department or Location OBS, you cannot use these objects for time entry or financial transactions.
When you associate an object with a financial Department OBS, the following actions happen:
  • The associated object appears as a hyperlink under the 
    Associated Objects
     section on the 
    OBS Properties
     page. Click the hyperlink to view the attribute that is created on the 
    Object Attribute
     page. On this page, you can set the Default value and also make the OBS field Read-Only.
  • An attribute that is named 
    Department OBS
     of 
    OBS Entity - Lookup Data Type 
    is created on the associated 
    Object Attribute
     page. This 
    Data Type
     is reserved only for the OBS attribute and is not available for the custom attribute creation.
     The hyperlink and the Department OBS attribute are not created for the following objects: Company, Incident Category, Job/Report, Page, Portfolio, Portlet, Process Definition, Release, Release Plan, and Requirement.
  • The Department OBS attribute is created only on the first association of an object with the financial Department OBS and not for the subsequent associations. As a result, you have only one Department OBS attribute in the attributes list of the associated object.
When you associate an object with the Location OBS, the associated object does not have a hyperlink. The attribute is not created in the attributes list of the associated object.
The following table represents the Financial OBS attribute data that is created after the association.
 
OBS Name
 
 
Object Name
 
 
Attribute Name
 
 
Attribute ID
 
 
Data Type
 
CA Dept
Project
Department OBS
odf_obs_fin_dept
OBS Entity - Lookup
CA Loc
Project
Not Applicable
Not Applicable
Not Applicable
In addition to a project, other object types are acceptable in the Object Name column. However, the object cannot be a company, incident category, job, report, page, portfolio, portlet, process definition, release, release plan, or requirement.
 
 
Follow these steps:
 
  1. Click 
    Administration
    Organization and Access
    OBS
    .
  2. Open the OBS and click 
    Add
     under the 
    Associated Objects 
    section.
  3. Select the objects to associate with the OBS and click
     Add
    . For example, associate the project object with the CA Dept and CA Loc OBS units.
  4. Select 
    Association Mode
     to select the OBS units present at all levels or only the ones that are present at the lowest level.
    Values:
     
 
Any Unit:
 If an OBS has multiple levels, all units from all levels are available for selection.
 
Lowest Unit
: If an OBS has multiple levels, only units in the lowest level are available for selection.
You cannot change the Association Mode of an object that is associated with the Department OBS from Any Unit to Lowest Unit if any instance of the associated object has the department unit set to any value which is not at the lowest level. 
 If the default, override default, or both are set to any value other than the 
Lowest Unit
, then the values for both these fields become blank when you change the 
Association Mode 
from 
Any Unit
 to 
Lowest Unit
.
    • If any instance of the associated object has a unit which is not set to 
      Lowest Unit
      , an error message appears.
    • When the read-only and mandatory fields are set and you change the 
      Association Mode
       from 
      Any Unit
       to 
      Lowest Unit
      , an error message appears.
If the 
Association Mode
 for any associated object is set to 
Lowest Unit
, you cannot add sub-departments after the lowest level.
When you disassociate an object from a financial OBS, the Department OBS attribute is deleted. If the object is associated with more than one financial OBS, then the Department OBS attribute is deleted only after the object is disassociated from the last OBS.
Associate the Roadmap Object with an OBS Unit
Before performing these steps, create an OBS for roadmaps. For example, create an OBS named 
Portfolio Roadmap OBS.
 
: The following steps apply to Release 15.6 or higher.
 
Follow these steps:
 
  1. Click 
    Administration
    Organization and Access
    OBS
  2. Open the OBS and click 
    Add
     under the 
    Associated Objects 
    section.
  3. Search for Roadmap and click 
    Add
    .
    Roadmap object is added under the OBS.
  4. Add units under the OBS
    Refer to the 
    Create the OBS Units
     section and add units under the OBS.
  5. To view the OBS attribute in the New User Experience, enable the API alias for the attribute. Navigate to the attributes page of the Roadmap object.
    An attribute is automatically created under the Roadmap object, with the display name of the OBS created (
    Portfolio Roadmap OBS)
  6. Click the 
    Portfolio Roadmap OBS attribute. 
    Enter the
     API Attribute ID 
    and save the changes.
  7. Assign OBS level access rights to a resource, for Portfolio Roadmap OBS. For example, if Mike has OBS level access rights as 
    Roadmap - Edit
    , he can see and edit all roadmaps linked to the 
    Portfolio Roadmap OBS 
    in the New User Experience. To view and update OBS units for the linked roadmap objects, refer to 
    Link Roadmap to OBS 
    in New User Experience: Top-Down Planning with Roadmaps.
Create the OBS Units
You can create OBS units at each level. For example, create a unit that is named IT at level 1 and Development and QA as child units at level 2 for CA Dept OBS. Similarly, create units for the CA Loc OBS. You can move OBS and the descendants to other branches or levels without losing any access to objects and resources when you reorganize your organization. 
You cannot create or delete units from an OBS that is linked to an entity. Instead, create the OBS units before associating the OBS with an entity.
 
Follow these steps:
 
  1. Click 
    Administration
    Organization and Access
    OBS
    .
  2. Open an OBS and click 
    Units
    .
  3. Click 
    New 
    and complete the fields to create units at level 1.
  4. To create child units for the existing units, select the 
    Parent
     field. To create multiple units at once, use 
    Quick Create
    .
  5. To attach an instance of the associated object, click 
    Save and Continue
    . You can attach an object instance to an OBS unit to control the resources that have access to the instance using the Attached Instances tab. You can select instances of any object that is associated with the OBS. 
  6. To add more OBS units, click 
    Save And Return
    .
Create an Entity
You can create financial plans and can establish costs for investments after you define an entity. Each entity has its own set of locations and departments and is associated with only one Department OBS and Location OBS. To establish the financial boundary, associate entities with a geographical OBS for locations and an organizational OBS for departments.
When you create an entity, the selected Department and Location OBS get converted to financial OBS and the non-financial OBS attributes are deleted from the associated objects. A financial OBS attribute that is named 
Department OBS
 is created in the objects that are associated with the Department OBS. However, the OBS attribute is not created for the following objects: Company, Incident Category, Job/Report, Page, Portfolio, Portlet, Process Definition, Release, Release Plan, and Requirement.
If you are setting up financial management for the first-time, first create the Department and Location OBS, and then create an entity. When you associate an OBS with an entity, the OBS automatically enables access rights management. The OBS cannot be deleted and their structure cannot be edited directly from the OBS.
When you create an entity, the default values are populated if you have previously defined system defaults. For example, Investment Class, Company Class, and WIP Class are populated by default. If a cost/rate matrix exists for resources (labor, material, equipment, and expense), by default all transactions for these resources use the matrix to determine costs and rates. You can override this default by entering a different cost and rate in the transaction properties.
 You cannot create the OBS units from the 
OBS Units
 page after an entity is created.
In this article, create an entity that is named CA Entity by associating with the CA Dept and CA Loc OBS.
 
Follow these steps:
 
  1. Click 
    Administration
    Finance
    Setup
    .
  2. Click 
    Entities
     and click 
    New
    .
  3. Complete the fields in the 
    General 
    section:
    •  
      Fiscal Period Type
      Defines the fiscal time period type for the entity. This value sets the default fiscal time period type for all new cost plans created for the entity. You can change this default in the cost plan.
      Values: Monthly, Quarterly
       , 
      Annually
      Weekly
      Semi Monthly
      13 Periods
       
    •  
      Home Currency
      Defines the home currency for the entity. You cannot update this field after the entity is created. You can only select currencies if the currency option is selected when the product is installed.
    •  
      Default Billing Currency
      Defines the default billing currency for viewing cost plans.
    •  
      Reporting Currency
      Defines the default currency for reporting. You cannot update this field after the entity is created.
    •  
      Location OBS 
      Defines the existing Location OBS to be associated with the entity.
    •  
      Department OBS
      Defines the existing Department OBS to be associated with the entity.
    •  
      Default
      Defines the default entity for the system. The field appears only after you save the required information for the entity. If this is the first entity you are creating, it is automatically set as the default one. You can undo the default setting by clearing the field. If you have multiple entities, you can only set one entity as the default.
      : The Default field is not required but if you do not set a default entity, it impacts the Staffing and Roadmaps capabilities in the 
      New User Experience
      .
  4. Complete the fields in the 
    Defaults
     section:
    •  
      Investment Class
      Categorizes work logically within an organization. For example, you can use investment classes to categorize investments.
    •  
      Company Class
      Defines the default company class. A Company class categorizes clients, vertical markets, or lines of business within your financial organization and is required when financially enabling a company.
    •  
      WIP Class
      Categorizes companies and investments. WIP is also used to indicate methods of revenue recognition. You can use the WIP class to define the rates and costs for transactions, and to group transactions for posting to the general ledger. You can also use them to calculate recognized revenue for projects.
  5. Complete the fields in the 
    Labor Rate and Cost Defaults
    Material Rate and Cost Defaults
    Equipment Rate and Cost Defaults
    , and 
    Expense Rate and Cost Defaults
     sections:
    •  
      Rate Source
      Defines the cost or rate matrix that is used to calculate the benefit amount of the transaction entry.
    •  
      Cost Source
      Defines the cost or rate matrix that is used to calculate the cost amount of the transaction entry.
    •  
      Source Location 
      Defines the source for the rate and cost as coming from either the resource location or project location. The value that you select here controls the cost plan population for the department and location grouping attributes. For example, select Resource as the source location for your entity for both labor and non-labor resources. Later, you auto-populate a cost plan from investment team or task assignment and group the details by department, location, and resource. Then, all the resources (labor and non-labor) show their department and location values based on the resource financial properties (not the project financial properties).
    •  
      Exchange Rate Type
      Defines the exchange rate type for project transactions and is displayed only when multiple currencies are available. When the project is approved, you cannot modify the exchange rate type.
      Values:
      Average: 
      The blended derived rate over a period: weekly, monthly, or quarterly.
      Fixed:
       
       
      The fixed rate that does not change over a defined period.
      Spot
      :
       
      The variable rate that changes frequently, say daily.
  6. Save your changes.
Associate the Departments and the Locations
You can associate the Department and Location OBS units with each other. The association helps in defining which department belongs to which location.
You can associate a department with multiple locations. The locations must be from the same entity as the department. You can view these locations and can add a location to a department. You can remove the locations from a department only if the location is not used in any instance.
 
Follow these steps:
 
  1. Click 
    Home
    Organization
    Departments
    .
  2. Open the department that you want to associate with the locations.
  3. Click the 
    Properties
     tab and click 
    Locations
    .
  4. Click 
    Add
     to display the locations.
  5. Select the locations to associate and click 
    Add
    .
Associate the Locations with the Departments
You can associate a location with one or more departments. First verify that you have created departments and associated them to the same entity as the location.
 
Follow these steps:
 
  1. Click 
    Administration
    Finance
    Setup
    .
  2. Click 
    Locations
     in the 
    Organizational Structure
     section.
  3. Open the location that you want to associate with the departments.
  4. Open the 
    Properties
     menu, and from 
    Main
    , click 
    Departments
    .
  5. Click 
    Add
     to display the departments.
  6. Select the departments to associate and click 
    Add
    .
(Optional) Configure the OBS Attribute
After the OBS attribute is created, you can configure it like other existing attributes. Here are some examples of how you can configure the OBS attributes:
  • Make the OBS field mandatory.
  • Make the OBS field read-only.
  • Set the OBS field so that the value is entered only once.
  • Set the default value for the OBS field.
  • Set the override default value for the OBS field.
  • Hide the OBS field.
  • Change the label for the OBS field.
  • Move the OBS section to another subpage or a secured subpage.
  • Rename the OBS section.
  • Delete the OBS section.
  • Move the OBS fields out of the OBS section to any other section.
  • Configure the OBS attributes on the list page.
  • Use inline editing.
  • Enable audit trail for the OBS attributes.
  • Use auto-suggest for the OBS fields.
  • Use language translation for the OBS fields.
  • Use an OBS field in the system or manual action of a process definition.
The OBS section can be deleted like other existing section. If you reassociate an object with any OBS section, the OBS section reappears on the General Properties page of the object only with the OBS with which the object is reassociated.
 
  • You cannot update an attribute value that is read-only from the user interface. However, when the Department attribute is updated on the financial subpage, the 
    Department OBS
     attribute gets updated even if it is read-only. This behavior happens because the 
    Department OBS
     and the Department attribute values should remain in sync.
Video: Why the OBS Section Appears When Deleted from Views
The following video is provided by CA Technologies.
 

 
 To play this video in full screen, click the YouTube logo to the right of Settings at the bottom of the video. 
Set Up a Non-Financial OBS
Review the Prerequisites for Creating a Non-Financial OBS
To complete all tasks in this article, you need the following access rights:
  •  
    Administration - Application Setup
     
  •  
    Administration - XOG
     
  •  
    Object Administration
     
Create an OBS
You can create an OBS to represent departments or locations that are not used for financial planning. Create an OBS to define the levels and units that are associated with the organization. You can name the OBS with a qualifier to indicate that the OBS is used for purposes other than entity association. For example, an OBS named Geographies defines an OBS type for geographical location.
In this article, create an OBS named Resource Pool with two levels. For example, Country at level 1 and State at level 2.
 
Follow these steps: 
 
  1. Open 
    Administration
    , and from 
    Organization and Access
    , click 
    OBS
    .
  2. Click 
    New
    .
  3. Complete the fields in the 
    General Information
     section.
    Best Practice:
     Name the OBS with a descriptive name that describes how you plan to use the OBS.
  4. Enter labels in the 
    Levels
     section.
  5. Save your changes.
Associate Objects with the OBS
Associate the objects with an OBS to enable OBS capabilities, such as security or reporting for that object. When you associate an object with the OBS, the following actions happen:
  • The associated object appears as a hyperlink under the 
    Associated Objects
     section on the 
    OBS Properties
     page. Click the hyperlink to view the attribute that is created on the 
    Object Attribute
     page. On this page, you can set the Default value and also make the OBS field Read-Only.
  • An attribute with the OBS name and 
    OBS - Lookup Data Type
     is created on the associated Object Attribute page.
    The hyperlink and the OBS attribute are not created for the following objects: Company, Incident Category, Job/Report, Page, Portlet, and Process Definition.
The following table represents the attribute that is created after the object-OBS association:
 
Non-Financial OBS
 
 
OBS Name
 
 
Object Name
 
 
Attribute Name
 
 
Attribute ID
 
 
Data Type
 
Resource Pool
Project
Resource Pool
odf_<first four valid characters of OBS_ID>_ <#code of the OBS ID>
OBS - Lookup
In addition to a project, other object types are acceptable in the Object Name column. However, the object cannot be an incident category, job, report, page, portlet, or process definition. By default, the OBS Name, and Attribute Name are the same when the object is associated with a non-financial OBS.
In this article, associate the Project object with the Resource Pool OBS.
 
Follow these steps:
 
  1. Open 
    Administration
    , and from 
    Organization and Access
    , click 
    OBS
    .
  2. Open the OBS and click 
    Add
     under the 
    Associated Objects 
    section.
  3. Select the objects to associate with the OBS and click
     Add
    .
  4. Select 
    Association Mode
     to select the OBS units present at all levels or only the ones that are present at the lowest level.
    Values:
     
  5.  
    Any Unit
    . If an OBS has multiple levels, all units from all levels are available for selection.
    •  
      Lowest Unit
      . If an OBS has multiple levels, only units in the lowest level are available for selection.
  6. Save your changes.
You cannot change the 
Association Mode
 of an object that is associated with the Department OBS from 
Any Unit
 to 
Lowest Unit
, if any instance of the associated object has the department unit set to any value which is not at the lowest level.
If the default, override default, or both are set to any value other than 
Lowest Unit
, the values for both these fields become blank when you change the 
Association Mode 
from 
Any Unit
 to 
Lowest Unit
. When the read-only and mandatory fields are set and you change the 
Association Mode
 from 
Any Unit
 to 
Lowest Unit
, an error message appears.
When you disassociate an object from an OBS, the OBS attribute is deleted with all the related information such as views, database tables, and instance level data. After the dissociation, the objects do not appear on the OBS Properties page.
Create the OBS Units
In this article, create the OBS units at each level. For example, create a unit that is named United States at level 1 and California and Texas as child units at level 2.
 
Follow these steps:
 
  1. Open 
    Administration
    , and from 
    Organization and Access
    , click 
    OBS
    .
  2. Open the OBS for which you want to add the units and click 
    Units
    .
  3. Click 
    New 
    and complete the fields to create units at level 1.
     Select the 
    Parent
     field to create child units for the existing units. Use 
    Quick Create
     to create multiple units at once.
  4. To attach an instance of the associated object, click 
    Save and Continue
    . You can attach an object instance to an OBS unit to control the resources that have access to the instance using the Attached Instances tab. You can select instances of any object that is associated with the OBS. to add more OBS units, click 
    Save And Return
     .
Configure the OBS Attribute
After the OBS attribute is created, you can configure it like other existing attributes. Here are some examples of how you can configure the OBS attributes:
  • Make the OBS field mandatory or read-only.
  • Set the OBS field so that the value is entered only once.
  • Set the default value for the OBS field.
  • Set the override default value for the OBS field.
  • Hide the OBS field.
  • Change the label for the OBS field.
  • Move the OBS section to another subpage or a secured subpage. You can move an OBS and the descendants to other branches or levels without losing any access to objects and resources when you reorganize your organization.
  • Rename the OBS section.
  • Delete the OBS section. The OBS section can be deleted like any other existing section. If you reassociate an object with any OBS section, the OBS section reappears on the General Properties page of the object only with the OBS with which the object is reassociated. 
  • Move the OBS fields out of the OBS section to any other section.
  • Configure the OBS attributes on the list page.
  • Use inline editing.
  • Enable audit trail for the OBS attributes.
  • Use auto-suggest for the OBS fields.
  • Use language translation for the OBS fields.
  • Use an OBS field in the system or manual action of a process definition.
Upgrade Impacts on OBS Properties
The following changes happen after you upgrade to this release:
  • Any occurrence of the braces {} symbol in the OBS name changes to the parentheses () symbol.
  • The pre-installation check fails while upgrading if the OBS name contains any of the following special characters:
    • Slash (/)
    • Colon (:)
    • Quotation marks (" ")
    • Less than (<) and greater than (>)
Constraints on the Audit Trail-Enabled OBS Attributes
From this release, you can leverage an audit trail for the OBS attributes. However, you cannot delete an OBS attribute that is audit trail-enabled. If you attempt to delete the OBS attributes, you receive an error.
Here are some actions that you cannot perform when the OBS attribute is audit trail-enabled:
  • Delete a non-financial OBS
  • Disassociate the objects from the OBS
  • Create an entity
  • Delete an entity
Configure the OBS Section
You can configure, move, or delete an OBS section like any existing section. When you associate an object with an OBS for the first time, an OBS section is created with the OBS attribute in the 
Create View
 and 
Edit View
 of the object. For every subsequent association, an OBS attribute is added to the 
Selected
 column of this section.
When you reassociate an object with any OBS section after you delete an OBS section, the OBS section reappears on the General Properties page of the object only with the OBS with which the object is reassociated.
You can move the OBS section to any subpage and can use 
Restore Defaults
 to move the section back to the original location. When you restore the default, the OBS section moves back to the 
General Properties
 subpage with all of the OBS attributes in the 
Selected
 column.
 The System Partition can have only one OBS section at any time.
Consider the actions in the following table to understand the result of the Restore Defaults action:
 
Action
 
 
Result
 
The administrator has not configured the OBS section and the user is using the default view configuration.
No changes in the OBS section views.
The user sees the same OBS section view with attributes on the General Properties page.
The administrator configures the OBS section by moving either some of the OBS attributes or the entire section to another subpage.
The OBS section moves back to the General Properties subpage.
All the OBS attributes are added back to the Selected column in the order in which they were created.
The object is associated with a partition model.
The changes in the OBS section are removed and the configuration of the parent partition is restored.
No impact on the OBS section view for its ancestor.
The partition model is disassociated from the object after the OBS section is configured.
The view reflects the OBS section that is configured for the System Partition.
No changes to the instances that were created when the partition model was associated with the object.
XOG Impact
You can move the OBS section to any subpage like other existing sections using XOG. When you XOG in an OBS with the associated objects, attributes are created in the objects and they are added to the OBS section. When you XOG out the object views, the OBS section appears in the XOG output like other sections. The OBS section has an attribute named 
code
 with the value ODF_OBS_SECTION.
When you XOG in, the views in the XOG source file replace the views on the target system. If the 
version
 attribute value (representing the product release number) in the XOG file is less than 13.2, the OBS section on the target system is preserved because there was no OBS section in earlier releases. If the 
version
 attribute value is 13.2 or higher, and the OBS section is not present in the XOG file, the OBS section is deleted on the target system.
You can copy an OBS section multiple times for a particular view in the XOG file. The XOG in happens only for the last instance of the OBS section in the XOG file as there can be only one OBS section in the System Partitioned view. However, you can XOG in multiple OBS sections to other partitions.
Add-ins XOG
If the 
version
 attribute value (representing the product release number) in the XOG file is less than 13.2, the OBS section on the target system is preserved after add-ins XOG. If the 
version
 attribute value in the XOG file 13.2 or higher, and if the OBS section is not present in the source file of the add-ins, then the OBS section is deleted on the target system.
To preserve the OBS section, a new attribute named 
complete
 with a default value of 
false
 is added in the Property Views XOG. If the value is set to preserveOBS in the XOG file, the OBS section is preserved irrespective of the 
version
 attribute value in the XOG file.
The following snippet shows the 
complete
 attribute and the 
section code
 in the XOG file:
<property code="custCreate" componentId="odf" complete="preserveOBS" objectCode="cust" partitionCode="NIKU.ROOT" type="create">
<section code="ODF_OBS_SECTION" currentState="collapsed" sequence="3"> ... ... </property>
Entity XOG
The entity XOG behavior is the same for the configurable OBS. When you XOG out an entity from the source system and XOG in to the target system, an entity is created on the target system.
Delete OBS Types
You can delete OBS types. If you enabled an OBS for access rights, remove the access rights association before you can delete the OBS. An OBS associated with a financial entity cannot be deleted.
 
Follow these steps:
 
  1. Open Administration, and from Organization and Access, click OBS.
  2. Select the check box next to each OBS, and click Delete.
  3. Click Yes on the confirmation page.