1. Administrator's Guide
  2. Integrating Data
  3. Loading Data
  4. Using the Data Load Workbench
  5. Using the Workbench Data Grid
  6. Intersection Check Report Errors

Intersection Check Report Errors

When Intersection Check reports are generated as part of the data validation step, if errors are encountered, the Intersection check report provides information on the errors.

There are four Intersection Check Report errors:
  • Invalid Intersection
  • Cannot Write
  • Locked Intersection
  • Invalid Member

Invalid Intersection (highlighted in red)

Invalid intersection errors occur due to the following errors:

  • The intersection is not valid.
  • The ICP member is not valid for the account. The ICP must be a child of "TopCustom" in the ICP hierarchy.
  • The account does not allow intercompany activity. The ICP member value must be set to " ([ICP None])" or the account must be changed.
  • The entity does not allow intercompany activity. The ICP member value must be set to " ([ICP None])" or a valid ICP entity.
  • The custom member is not valid for the account. The custom member must be a child of "TopCustom" in the custom hierarchy.

Cannot Write (highlighted in purple)

Cannot write errors occur due to the following:

  • No read or write access. (Oracle Hyperion Financial Management cell status is no read access or no write access.)
  • Financial Management cell status can write and support line items, but the cell does not support IC transactions.
  • Financial Management cell status is derived.
  • Financial Management cell status is parent level input.

Locked Intersection (highlighted in green)

Locked intersection. (Financial Management cell status is locked.)

Invalid Member (highlighted in orange)

Invalid member mapping error due to the following:

  • The target member is not valid in Financial Management or the user does not have access to it in Financial Management.
  • Intercompany with self is restricted. The ICP dimension value must not equal the entity dimension value.