Cognos FSR UTR Update: This update will allow FSR to comply with XBRL Unit Type Registry standards issued by the SEC

Flash (Alert)


Abstract

The SEC has begun checking for EFM Rule 6.5.35 within the EDGAR Submission Portal. For further reference, visit http://xbrl.org/units-registry or review the Edgar filling manual version 22 at http://www.sec.gov/info/edgar/edgarfm-vol2-v22.pdf.

Content

Affected Versions
The following versions of FSR are affected:

  • IBM Cognos FSR 6.6.1 GA
  • IBM Cognos FSR 6.6.1 FP1

Please note that this filing requirement is only applicable to customers using USGAAP 2012 for SEC filing.


Description
Currently in FSR, one can define units using their company prefix (custom) within XBRL Configuration. For example, for a client named ABC Company, the custom prefix "abc" was used for a unit of measure known as "Barrels", resulting in "abc:bbl."

When a fact was tagged with this unit, the application was able to produce an instance. However, EDGAR Submission Portal returned the following error message:

WRN: XBRL ERROR MESSAGE
MSG: Error: [utre:error-NumericFactUtrInvalid] Unit Barrel disallowed on fact
us-gaap:GasImbalanceVolumeAmount of type volumeItemType - abc-20130213.xml

Custom units that are tagged with elements using the following Item Types will results in validation message stated above:
    areaItemType
    energyItemType
    lengthItemType
    massItemType
    volumeItemType
    memoryItemType
    FrequencyItemType
    powerItemType
    pureItemType
    durationItemType
    voltageItemType
    electricCurrentItemType


Remediation
Please apply the appropriate update to remediate these issues as per this table. This is a non-cumulative update and can be applied regardless of hotfix level without impacting other fixes.

Product Version Remediation
IBM Cognos FSR 6.6.1 GA Release Link to Fix Central Download Link
IBM Cognos FSR 6.6.1 FP1 Link to Fix Central Download Link

Once the update is implemented, users have will have the ability to review their existing units and document any units that match against the Unit Type Registry. For those units, the prefix as originally defined can be modified with the "utr" prefix via the XBRL Configuration Menu.

For example, if company ABC defined barrels as "abc:bbl", this can now be changed to "utr:bbl" since it is part of the Unit Type Registry. However, the Name aspect of the Unit SHOULD NOT be changed or re-tagging efforts will be required for elements using these units.

In some cases, there will be circumstances where custom units cannot be mapped to the ones listed in the Unit Type Registry. If users choose to leave their custom units, changes will be needed to made to the Item Types of associated elements that are used as part of tagging. Users will run into these possible scenarios:
  1. Custom units associated to a custom element with an Item Type NOT listed above will be unaffected and no change is required.

  2. Custom units associated to a custom element with an Item Type listed above will be affected for which the following action should be taken:
    1. Load the appropriate Taxonomy into XET and navigate to the problematic elements. Change the Item Type to an alternative Item Type not listed above. Often xbrli:decimalItemType is suitable. FSR will prompt users to update all tags associated with this element for which one should select "NO" to all.

      Generate to Database: Generate the selected taxonomy to database. Navigate back to the XBRL module and re-tag all the elements that were updated in XET for ItemType. Users can also generate the “view tagging” report to filter all elements by objects, making elements easier to locate. Lastly, navigate to the XBRL menu and build instance.

      Generate to Folder: Generate the selected taxonomy to a folder. Navigate out of the XET module and update XBRL configuration to include your newly generated taxonomy. Once complete, re-tag all the elements that were updated in XET for ItemType. Users can also generate the “view tagging” report to filter all elements by objects, making elements easier to locate. Lastly, navigate to the XBRL menu and build instance.

    2. As an alternative, users can change the units to be one of those appropriate for that Item Type in the UTR.

      Validate the taxonomy by conducting a test filling through the SEC portal.

  3. Custom units associated to a US_GAAP element with an Item Type NOT listed above will be unaffected and no change is required.

    Validate the taxonomy by conducting a test filling through the SEC portal.

  4. Custom units associated to a US_GAAP element with an Item Type listed above will be affected for which the following action should be taken:
    1. Load the appropriate Taxonomy into XET and navigate to the problematic elements. Change the Item Type to an alternative Item Type not listed above. Often xbrli:decimalItemType is suitable. FSR will prompt users to update all tags associated with this element for which one should select "NO" to all.

      Generate to Database: Generate the selected taxonomy to database. Navigate back to the XBRL module and re-tag all the elements that were updated in XET for ItemType. Users can also generate the “view tagging” report to filter all elements by objects, making elements easier to locate. Lastly, navigate to the XBRL menu and build instance.

      Generate to Folder: Generate the selected taxonomy to a folder. Navigate out of the XET module and update XBRL configuration to include your newly generated taxonomy. Once complete, re-tag all the elements that were updated in XET for ItemType. Users can also generate the “view tagging” report to filter all elements by objects, making elements easier to locate. Lastly, navigate to the XBRL menu and build instance.

    2. As an alternative, users can change the units to be one of those appropriate for that Item Type in the UTR.

      Validate the taxonomy by conducting a test filling through the SEC portal.

  5. UTR units associated to Custom elements with an Item Type not listed above. No change has to be made.

  6. UTR units associated to Custom elements with an Item Type listed above. No change has to be made provided the Item Type is appropriate according to the UTR entries.

  7. UTR units associated to US_GAAP elements with the correct Item Type. No change has to be made.

  8. UTR units associated to US_GAAP elements with the incorrect Item Type. Users will have to use an alternative Unit to associate with the element being tagged. It should reflect the Item Type shown for the us-gaap element.


Additional Notes
Prior to the update, users will not see the appropriate namespace or measures being defined correctly within the instance document. After the update, when the instance is generated, FSR will add a new namespace "http://www.xbrl.org/2009/utr" and prefix "utr" for non-custom measures in the instance document.


Example:
    Unit:

    <xbrli:unit id="UTRBarrels">
      <xbrli:measure>utr:bbl</xbrli:measure>
    </xbrli:unit>

Namespace:
    xmlns:utr=http://www.xbrl.org/2009/utr

Validations messages:
When generating the instance validating against the EFM rules. FSR will continue to throw false warnings for UTR pre fixes which should be ignored. A future hot fix will address this issue.

Workaround
The taxonomy and instance files can be manually modified after generation to accommodate this requirement. This does require specific XBRL expertise. Lab services can be engaged to assist with the manual workaround.

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Cognos Financial Statement Reporting

Software version:

6.6.1

Operating system(s):

Windows

Reference #:

1625709

Modified date:

2013-02-22

Translate my page

Machine Translation

Content navigation