User Community Service Desk Downloads
If you can't find the product or version you're looking for, visit support.ataccama.com/downloads

Execution Plan

Execution plan configuration allows you to specify the order of steps in the consolidation process, enabling fine-tuning of the MDM internal workflow for optimal performance.

The best way to alter the plan is to download one from the Admin Center (see MDM Admin Center Extras) and adjust the order of steps.

If the plan does not match the dependencies, MDM engine will reject the plan (but not fail) and use the default execution plan.

nme-consolidation-plan.xml
<?xml version="1.0" ?>
<executionPlanConfig>
<executionPlans>
    <plan taskId="MasterDataConsolidation">
        <steps>
            <step id="Cleanse(Party)" />
            <!-- more steps -->
            <step id="Match(Party)" />
        </steps>
    </plan>
</executionPlans>
</executionPlanConfig>

The plan element includes a taskId attribute, which uniquely identifies the execution plan. The steps element contains multiple step definitions that represent a specific operation within the execution plan, identified by its id attribute.

If the execution plan does not meet the constraints, the MDM engine ignores invalid input, logging warnings only in system logs. The same handling applies to situations where new entities or operations are introduced into the plan.

For optimal performance, operations should be sorted based on data volume and complexity. The most time-consuming operations need to be prioritized. The recommended order of operations is as follows:

  1. Cleansing

  2. Cleansing related copy columns

  3. Matching

  4. Aggregate or matching related copy columns

  5. Merging

  6. Related records

  7. Validate

Was this page useful?