Previous Topic: View Superseded CIs from the ScoreboardNext Topic: CI Transaction Ambiguity Example


Review and Modify Inbound Data Using Transaction Work Area (TWA)

You can stage CI and relationship transactions before execution, by copying data into the TWA staging area. Once in the staging area, you can manipulate CIs and relationships by using the web interface or native SQL.

You also can validate the CI transactions to prevent the creation of new CIs when you should update existing CIs. In this approach, you view each transaction and the potential CIs that it can update so that you can reconcile the transaction manually to the target CI. Likewise, relationship transactions can be validated to reference the correct CIs.

The ambiguity index is an operational measure of the potential nonuniqueness of a configuration item (CI) or a CI transaction item, based on its identifying attributes. The ambiguity index measures the probability of one or more CIs representing the same real business object, or the probability that a CI transaction has more than one possible target CI.

Review and modify ambiguous CI transactions using the following process:

  1. Identify ambiguous CI transactions.
  2. Determine if the identifying attributes for each CI transaction reconcile to the intended CI.
  3. Resolve the ambiguous CI transactions with one of the following actions:

More information:

CI Transaction Ambiguity Example

How to Identify an Ambiguous CI Transaction

How to Resolve Ambiguous CI Transactions

Transaction Work Area

Populating the TWA

How to Use the Web Interface to Update Data in the TWA

Stage CI Transactions Before Loading into CMDB

How To Load Transactions into the CMDB

Manual Reconciliation

TWA Administration