This documentation supports the 9.1 version of Asset Management.

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

Configuring BMC Asset Management settings

  1. From the Application Administration Console, click the Custom Configuration tab.
  2. From the Application Settings list, choose Asset Management> Advanced Options> Asset Management Settings, and then click Open.
    The Asset Management Settings form appears.
  3. On the Asset Management Settings form, to show the current settings, click Show Settings.
  4. From the Action on CI Submit, select one of the following options:
    • Modify Individual — The CI form closes and then reopens in modify mode.
    • None — The CI form remains open in submit mode after the CI is submitted.
  5. From the Dataset Name list, select the production dataset for the application.
  6. From the Sandbox Dataset Name list, select the sandbox dataset.


    If multiple sources of data provide updates to BMC Atrium CMDB, you must specify a sandbox dataset.

    This dataset is used to stage updates to a production dataset. You are required to use reconciliation rules to move the data to production.


    If you change the production or sandbox datasets on this form, in the Reconciliation Engine you must update the underlying reconciliation rules BMC Asset Management - Sandbox" to use the new datasets. Without this change, the data cannot be reconciled to the new production or sandbox datasets.

    If you use a sandbox dataset, BMC Asset Management users cannot set their application preferences to display the CI immediately after creating it.

  7. If the sandbox dataset is used in a development-to-production environment, select Yes from the Sandbox Enabled list. The default is No.


    If the Sandbox setting is set to Yes (Asset Management Settings AST:AppSettings) and in the BMC:ASSET.SANDBOX dataset if you want to be able to submit CIs with categorization that is unapproved in the Product Catalog, and be able to merge the changes into the golden dataset, then in the Normalization Dataset Configuration (NE:DatasetOptions) form, change UnapprovedHandling from Reject to Accept for the BMC:ASSET.SANDBOX. If you want only CIs created with approved categorization to be merged to the golden dataset, keep the Reject setting. You can create the CI (with unapproved categorization) in BMC:ASSET.SANDBOX, but the changes will not be moved to the golden dataset. In this case you will need to change the Product Catalog entry to Approved before creating CIs with that categorization so the categorization is supported.

  8. From the Sandbox Job Calls list, select the value to specify when you want the reconciliation job to start. The options are:
    • Inline - (Default) The reconciliation job starts immediately.
    • Scheduled - The reconciliation job starts as per the configured sandbox schedules. You must use this option outside of the heavy use hours to avoid performance issues.
    • Continuous - The reconciliation job runs continuously as per the interval specified for continuous jobs in the Reconciliation Engine. For more information, see Creating a continuous reconciliation job .
  9. From the Sandbox Job Calls for People list, select the sandbox dataset reconciliation method for People to CMDB Person. The options are:
    • Inline — Calls are processed immediately.
    • Scheduled — Calls are processed in accordance with any sandbox schedules.
    • System Default — The client type is used to automatically detect the method for sandbox job calls.
  10. From the Server Date Format list, select the date format to use when calculating CI depreciation dates.
    This setting must match the date format on the BMC Remedy Action Request System (BMC Remedy AR System) server. If you change this setting, you must restart your BMC Remedy AR System server.


    If the date format does not match the BMC Remedy AR System server date format, then there can be errors when calculating CI depreciation dates.

  11. From the Default Company list, select a company name.
    If multi-tenancy mode is enabled, a default company must be configured.

  12. To save the settings, perform one of the following steps:
    • If you are saving the settings for the first time, click Add.
    • If you are modifying existing settings, click Modify.

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


  1. Kavita Durge

    Kavita Hi Team, We have a issue where OOTB Sandbox reconciliation job which is supposed to be run as scheduled runs inline when relationship is added in asset.

    As per KB – 000072971

    It is referred as designed and workaround was to disable the filter which start the job manually.

    This should be added as a note in document so we are aware that even though OOTB sandbox reconciliation job is set to schedule and if we donot want it to be triggered by any user updates then disable these workflow.

    Regards, Kavita

    Apr 25, 2019 09:46
    1. Aditya Kirloskar

      Hi Kavita,

      Thank you for your comment. In version 9.1.1, in Asset Management Settings a new setting, Sandbox Job Calls, is added that you can use to control when you want to run the reconciliation job. I have updated the document with this information.

      Hope this helps.



      Sep 13, 2019 04:47
  2. Pratiksha Sharma

    Hi Team,

    If we don’t want a dataset to create its own Asset Record, how do we set it in tool. Scenario – in case of bulk record, we need only one attribute to get updated and don’t want to create a new record with additional info.

    Dec 23, 2020 01:25
    1. Aditya Kirloskar

      Hi Pratiksha,

      Thank you for your question. Are you referring to a bulk sandbox, because a bulk sandbox creates an entry and deletes it everytime the reconciliation job runs. But in the case of a regular sandbox the entry is not deleted and hence it's not created everytime

      Hope this helps.



      Dec 29, 2020 08:27