This documentation supports the 9.1 version of Asset Management.

To view the latest version, select the version from the Product version menu.

Synchronizing the BMC Asset Inventory forms with BMC Atrium CMDB

For new classes added in the BMC Atrium CMDB that are relevant to BMC Asset Management, corresponding BMC Asset Inventory forms are required. The synchronization process updates the BMC Asset Inventory forms to include forms for any new classes added to the BMC Atrium CMDB.

To synchronize BMC Asset Inventory forms with BMC Atrium CMDB

  1. In the Application Administration Console, click the Custom Configuration tab.

  2. From the Application Settings list, select Asset Management > Advanced Options > Sync Asset UI with CMDB, and then click Open.


    When a custom class is created, it inherits the UI from the parent AST form. However, when you add fields on your new class, the fields appear on a hidden "custom" tab. You must move the fields to another area on the form to see and use them.

  3. In the Schema Name field, enter the name of the CMDB class for which you want to create a UI in Asset Management. For example AST:ChassisAST:FileSystem, and so on.

  4. Click Update Asset UI. The system generates or updates Asset UI for the CMDB class and its subclasses. The class and its subclasses are updated with changes in the BMC CMDB.


    The changes are partially reflected on Asset forms after running Sync Asset UI. For Enum fields, the alias values are not synced to the asset forms.

  5. To create an BMC Remedy Asset Inventory form, enter the form name in the Schema Name field.

  6. In the Update Changes From Date field, optionally enter the starting date and time for the changes to be updated. Leave blank to include any changes that occurred after the last update.

  7. Set the Has Asset UI field to Yes, to make the class available in the BMC Asset Management application.

  8. In the Proper Name field, enter the name to appear in BMC Asset Inventory forms.

  9. Click Update Asset UI.


    Sync Asset UI creates duplicate fields (with identical names but different field IDs) if it finds a field with the same name in the Asset Management form and in the CMDB form. 

    When the Sync Asset UI utility is triggered, it can take up to 30 minutes for records to start getting processed from the application pending form. This is because some of the notifications are lost before the utility is triggered.

    The synchronization activities are saved in the CMDBSynchronizeUI.log file. For details about this file, see Generating forms for other applications

    If you do not want to display certain relationships available from the menus (when relating one CI to another CI) then set the Show In Menu field to No.

    If you open the Schema Names form directly, it displays in Administrator view, by default. This view has Asset Management and Form Lookup tabs visible at the bottom of the screen. The fields on the Asset Management tab are no longer used by the Sync Asset UI, however they are still in use by some menus and workflows. A detailed description of the fields are shown in the following tables.

     Asset Management tab fields Description of fields used by BMC Asset Management records
    ContractsUsed in menus 
     People Used in menus and workflow
     Configuration Used in menus and workflow
     SLM Obsolete
     Schedule Not Used
     Financials Used in workflow
     Depreciation Used in menus and workflow
     Outage Used in workflow
     Return Used in workflow
    Purchase RequisitionUsed in menus and workflow
    In InventoryUsed in menus and workflow

    Form Lookup tab fields

    Description of fields used by all application records

    Form Code

    Used in workflow name specific to the form

    User Defined Prefix

    Used by Incident


    Field-id 179 used to store the record locale

    Workflow Transition Tag

    Used in menu

    Generated Entry ID

    Indicates main field for identifier

    Status Field ID

    Indicates which field tracks the state of the form

    Data Tags

    Stores a tag that identifies the system the form belongs to


Retaining custom classes after an upgrade

(For upgrade only) If you have added custom classes, after you run the Sync Asset UI utility, these custom classes might be deleted and lose their role based permissions. Follow the steps below to retain these custom classes:

  1. Open the BMC Remedy Developer Studio in the Best Practice Customization mode.
  2. From AR System Navigator, expand the Applications branch under the appropriate server.
  3. Double-click the BMC Asset Inventory application and from Filtering Options, click the Applications node.
  4. Make sure that the Type column is set to Deployable.
  5. Right-click the BMC Asset Inventory application and make sure that the Create Overlay option is disabled. If not, click Create Overlay.
  6. From the the Filtering Options of the BMC Asset Inventory application, click the Forms node.
  7. Right-click on each of the custom AST forms that you have created, and click Create Overlay.
  8. In BMC Remedy Developer Studio, click File > Switch Mode > Base Development. 
  9. From the Applications branch, select the BMC Asset Inventory application and make sure that the Type column is set to Deployable.
  10. In the Filtering Options of the BMC Asset Inventory application, click the Forms node.
  11. Right-click on each of the custom AST forms that you have created, and click Delete.

Was this page helpful? Yes No Submitting... Thank you


  1. Andreas Mitterdorfer

    On the Sync Asset UI with CMDB form, click Class Name, and then select the BMC Asset Inventory form (Class Name) to synchronize with BMC Atrium CMDB. From this form you can call the CMDB2ASSET function.

    You cannot select the "BMC Asset Inventory form" in class name field.

    Can you describe wheter there is a way to sync ALL classes with their localized views?

    Aug 23, 2017 10:00
    1. Mokshada Shivarekar

      Hello Andreas,

      Thank you for your comment. I will work with the SME and write back to you.



      Aug 28, 2017 03:25
    1. Aditya Kirloskar

      Hello Andreas,

      Apologies for the delay. I have modified the document with the required changes.



      Jun 29, 2020 08:59