Conditional Mapping using a Mapping Script

With conditional mapping, source members are mapped to script expressions rather than to hard-coded target members. Conditional mapping is valid only for rule-based mapping (Between, In, and Like). You can activate conditional mapping by placing #SCRIPT or #SQL in the Target value column. Use #SCRIPT for Jython Script and #SQL for SQL script. Conditional mapping, in conjunction with dimension processing order, enables mapping that is based on the results of dimension mappings. That is, dimension mappings that have already been processed. See Using Mapping Scripts.

Note:

In Oracle Hyperion Financial Data Quality Management, Enterprise Edition, Jython script is not supported for conditional mapping (#SCRIPT cannot be used in the Target value column.)

To apply conditional mapping:

1. On the Workflow tab, under Data Load, select Data Load Mapping.
2. In Data Load Mapping, click Add.

   A blank row is added.

3. From Dimensions, select the dimension name.
4. Select either the Between, In, or Like tab.
5. Enter source values in the Source Value range.
6. In Target Value, enter #SQL.

   To use Jython script, enter #SCRIPT. For more information, see Using Jython Objects with Mapping Scripts.

   The pencil icon is enabled.

   
7. Click the pencil icon.
8. On the Edit Script screen, specify your SQL script.

   This sample script uses the SQL Cast statement to conditionally process assigned values for the target column.

   

   FDMEE does not perform an error check or validate the script. You need to test the script on your data files in a test environment and verify the results.

9. In Rule Name, specify the data load rule to use with the mapping script.
10. Click Save.