Forum Discussion

johnal67's avatar
johnal67
Contributor
2 months ago

Composite transformation rule with Scenario

I'm trying to do a Composite Rule to Bypass an account if it's part of a specific Scenario?  Can you use Scenario as part of an Account Composite Rule?  This is my statement "A#[525300]:S#[Budget_Dis...
Data Integration
Transformation
  • T_Kress's avatar
    T_Kress
    2 months ago

    If your scenario dimension at the data source level is defined from "Global Data Key Scenario" or "Current Data Key Scenario" (the latter is most typical), then it likely will not work in a composite map rule.  If instead the scenario is a column or field in the data source, then that composite should work.  I would first check how scenario is defined at the data source level.

    If scenario is a field in the data source then an alternative to a composite rule is you can concatenate Account_Scenario in your account dimension.  Then via mask or 1:1 mappings, you can handle account mappings. 

T_Kress's avatar
T_Kress
Contributor III

If your scenario dimension at the data source level is defined from "Global Data Key Scenario" or "Current Data Key Scenario" (the latter is most typical), then it likely will not work in a composite map rule.  If instead the scenario is a column or field in the data source, then that composite should work.  I would first check how scenario is defined at the data source level.

If scenario is a field in the data source then an alternative to a composite rule is you can concatenate Account_Scenario in your account dimension.  Then via mask or 1:1 mappings, you can handle account mappings. 

johnal67's avatar
johnal67
Contributor
2 months ago

You are my hero!  I was about to go crazy on that!  Thank you that was exactly what my issue was, I just had to make it a stored value on my Data Source which is okay for this situation, and it made the composite rule work.