1. Administrator's Guide
  2. Rule Functions
  3. Exp
  4. Exp and Dimension Intersection Considerations
  5. Invalid Intersections

Invalid Intersections

In these examples, the source and destination accounts each have an invalid intersection.

  • SourceAcct. Member002 and Member003 are valid, and Member001 is invalid.

  • TargAcct. Member001 and Member002 are valid, and Member003 is invalid.

In this example, Exp is used without specifying a Custom1 member on either side of the equal sign:

HS.Exp "A#TargAcct = A#SourceAcct"

Exp does not change data in the TargAcct account because Exp attempts to perform these operations:

  • TargAcct.Member001 = SourceAcct.Member001. SourceAcct and Member001 is an invalid intersection.

  • TargAcct.Member002 = SourceAcct.Member002. Since the intersection of SourceAcct and Member002 has a NoData status, the intersection of TargAcct and Member002 remains unchanged.

  • TargAcct.Member003 = SourceAcct.Member003. TargAcct and Member003 is an invalid intersection.

In this example, Exp is used with Member001 specified on the left side of the equal sign:

HS.Exp "A#TargAcct.C1#Member001 = A#SourceAcct"

TargAcct.Member001 remains unchanged because Exp attempts to retrieve data from an invalid intersection (SourceAcct and Member001).

In this example, Exp is used with Member003 specified on the right side of the equal sign:

HS.Exp "A#TargAcct = A#SourceAcct.C1#Member003"

The function puts this data into the intersections of the Custom1 members and the TargAcct account:

Custom1 Member Data Intersection

Member001

15

SourceAcct and Member003

Member002

15

SourceAcct and Member003

Member003

N/A

Not applicable. Member003 is an invalid intersection for the TargAcct account.