Removing Mapped Data and Deleting Disclosure Management Objects

There is an important distinction between removing an XBRL map association and deleting a Disclosure Management object:

• Removing an XBRL Map Association—Refers to removing or dissociating mapped XBRL elements from data in an Office document. For example, you remove a unit map from a numeric value table cell; however, the unit definition remains.

• Deleting a Disclosure Management Object—Refers to deleting a defined object such as a context, unit, variable, or footnote. For example, users can delete a defined unit from the list of units. When a Disclosure Management object is deleted, the Disclosure Management object and any associated mappings are removed.

Note:

Taxonomy concepts cannot be deleted in the Mapping Tool UI. Any edits to the taxonomy concepts must occur in the taxonomy Designer template and then refreshed into the Mapping Tool UI.

Removing XBRL Maps

You can remove XBRL mappings of taxonomy concepts, contexts, units, and footnotes from:

• One data point

• Multiple data points (an Office document which spans over two or more mapped data points)

• Dimensions (which could be document level mapping associations)

• Tuples

When you remove a mapped item, the Remove Mappings dialog box displays the mapped items that can be removed. The number of items listed depends on the Disclosure Management object selected in the Disclosure Management Mapping Tool. For example, when a unit object is selected, the dialog box enumerates the document data points that are mapped to the unit object. After a mapping is removed, it cannot be undone, and you must remap the data to the Disclosure Management object to recreate the map. For taxonomy concepts, the mapping information is removed from the Mapping Repository and does not appear in the in Review mode. If the mapped concept has associated XBRL dimensions (document level associations), they are also removed from the Mapping Repository.

Options for mapping removal are:

• Suppress the taxonomy concept map from the selected data point in the Office document (the concept map is disassociated within the Office document, but not removed from the Mapping Repository). This is different from overriding a default mapping from a data point in an Office document.

• Permanently removing the taxonomy concept map from the member (the concept mapping is removed from the Mapping Repository). In this case, when a mapping is removed, it cannot be undone, and you must remap the member to the XBRL taxonomy concept to recreate the map. The taxonomy concept is removed from the Mapping Repository and does not appear in Review mode. Additionally, the XBRL mapping affects all existing Office documents in Oracle Smart View for Office, data derived from the same member.

Table 7-6 Remove Mapping Dialog Fields and Descriptions

Field	Description
Type	Shows the type of Disclosure Management object: Concept, Context, Unit, or Footnote
Mapping	Shows the XBRL taxonomy object to which the value has been mapped
Value	Shows the report value associated with the map

Deleting Disclosure Management Objects

You can delete a defined Disclosure Management object such as a context, unit, variable or footnote. For example, users can delete a defined unit object from the list of units. In this case, not only is the Disclosure Management object removed; any mappings within the Office document which are associated with the deleted object are also removed. Before a Disclosure Management object is permanently deleted, you can reset the procedure, However, after you permanently delete a Disclosure Management object by clicking OK, you cannot undo the action, and you must redefine the object and recreate the maps.

Note:

Taxonomy concepts cannot be deleted through the Disclosure Management Mapping Tool because they are defined in taxonomies. If the concept is part of an extension taxonomy, you can delete the concept in Taxonomy Designer. See Working with Taxonomy Designer.