Rule Mapping Assist

  • Published on Dec 1, 2025
  • 9 minute(s) read
  • AF
  • BG
  • John Munkberg
 Prev Next

Overview

Rule Mapping Assist is an AI-powered rule mapping assistant, designed to accelerate and standardize the migration mapping rule workflow by helping Migrate Mappers refine initial mapping rule descriptions into precise, structured definitions and enables Migrate Developers to generate rule SQL/DDL statements and ETL tasks (in case of complex rule) for the mapping rule per the SynitiONE Methodology.

Note

Rule Mapping Assist is available only for the Syniti Migrate ETL Tool and for Rule and RuleXref mapping actions.

Key Features

  • Refine Mapping Rule Description: Transform a user-provided mapping rule description and metadata into a precise mapping definition and a list of source fields to be used during implementation.

  • Generate Rule SQL/DDL: Generate proposed rule SQL or DDL from a refined mapping definition and metadata.

  • Preview & Validate: Run the generated SQL in-app to preview results before saving. Simple rules may persist to a field, while complex rules may generate SQL views and ETL jobs as part of the save process.

  • Iterative Edits: Re-run Refine Rule or Propose Rule DDL; only the saved outputs (refined definition, SQL/DDL) are persisted.

Note

To use Rule Mapping Assist, AI features must be enabled for your tenant. Contact your Administrator to enable AI features.

Data Security and Privacy

Only the information necessary for refining and generating queries (such as user input or source/target table metadata) is processed. Rule Mapping Assist does not access any data beyond what is explicitly provided in the mapping rule description.

Currently, Rule Mapping Assist preserves only last saved changes and are stored securely in the database.

Important!

Your conversations and any data you provide as context are used by Rule Mapping Assist solely to process your current request and generate a relevant response.

Always Review and Validate RuleSpeak AI's Response

Rule Mapping Assist generates a refined mapping rule description, including data source tables and fields information. Migrate Mappers should validate and ensure that the refined output is correct.

Rule Mapping Assist generates SQL/DDL according to the target environment’s conventions. Migrate Developers should validate and tune generated SQL/DDL, if needed.

Refine Mapping Rule Description

For the Rule and RuleXref mapping actions, Migrate Mappers can use Rule Mapping Assist to refine or rewrite an initial mapping rule description with metadata (source datasource tables/fields, if provided) into a precise rule definition, including suggested source fields to be used during implementation.

Rule Mapping Assist uses the working database and the source database (datasource) of the mapping field as the context for proposing source fields when none are provided.

Typical User Flow

  1. Author: Write an initial mapping description and add supplemental metadata for the target field.

  2. Refine: Click Refine Rule. Rule Mapping Assist ingests the mapping description plus the provided metadata (if added) and returns a concise, structured definition of the mapping rule with proposed source fields.

    Note

    Rule Mapping Assist might propose different Rule Descriptions, Datasources, and Fields for each iteration of the same mapping rule description. Ensure that you read the proposed information and proceed to the next steps only if it meets your requirements.

  3. Review: Validate the refined output, edit if necessary, apply the final output to the Mapping Rule field with correct data source fields.

  4. Map Complete: Set Map Status to Complete and save the Mapping to signal readiness for rule SQL/DDL development.

To update the refined mapping rule description, click Refine Rule again to update it from the last saved state.

For example,

nitial Rule Description

Refined Mapping Rule Description

(Simple)

First 40 chars only, anything over 40 will not be converted


+ Metadata, if provided

The DESCRIPTION_OPP in ttCRMD_OPPORT_H must be populated with the first 40 characters of the Name from t_CAN_XX_Opportunity. Any characters beyond the 40-character limit must not be included in the conversion.

(Complex - One View)

Set zActive_VBAK to 1 where zSO is 1, or zOpenSO is 1.

+ Metadata, if provided

The field 'zActive_VBAK' in the 'ttVBAK_PREP' table  must be set to 1 if either the 'zSO' field or the 'zOpenSO' field in the 'CUST_ITMDEL' table of the 'EUROMS' system is 1.

(Complex - Multiple Views in layers)

Street Address, City, State PostalCode' for USA addresses and 'Street Address, City, State, PostalCode, Country' for international addresses.

+ Metadata, if provided

Create a standardized formatted address by combining address components with proper formatting. First, resolve the state field by using State for USA addresses, otherwise use StateCode. Then build the street address by combining Street1 and Street2 when both are present, separated by a comma and space, but use only Street1 if Street2 is blank. Next, create the city-state combination using the resolved state field with proper comma separation and null handling. Then add the postal code with comma separation if present and not blank. Finally, append the country with comma separation, but only include it if it's not blank and not 'USA' (since USA is implied for domestic addresses). The final format should be: 'Street Address, City, State PostalCode' for USA addresses and 'Street Address, City, State, PostalCode, Country' for international addresses.

Note

Similarly, use Rule Mapping Assist to refine a very complex mapping rule description that require multiple ETL tasks or multiple layered ETL tasks to satisfy multiple rules.

Generate Rule SQL/DDL and Build ETL Tasks

For the fields that has Rule and RuleXref mapping actions with Map Status set to Complete, Migrate Developers can use Rule Mapping Assist to transform a refined mapping rule description into a usable rule SQL/DDL.

Typical User Flow

  1. Generate Rule SQL/DDL: Pick a field mapping where Map Status = Complete and click Propose Rule DDL.


    Rule Mapping Assist produces a draft SQL/DDL statement in the in-app SQL Editor tab aligned with the refined mapping definition, the database environment, and the SynitiONE methodology (such as View and ETL Task naming format). Each script tab shows the SELECT statement of the generated SQL or View DDL.

    Note

    Rule Mapping Assist might propose different solution approach and SQL/DDL statements for each iteration of the same mapping rule.
    If the solution approach does not meet your requirements, do not click Save . Instead, close the tab and click Propose Rule DDL again.

  2. Validate & Iterate: In the SQL Editor tab, run the SQL/DDL in the script tab to preview results against the configured working databases. Results will appear if those fields contain data.

    For complex rules with multiple views, this tab will display multiple script tabs, representing a separate view or layered view of the transformation, allowing the Migrate Developer to validate each step, review intermediate outputs, and ensure the final results align with the refined mapping rule.

    Note

    • Validate the rule SQL/DDL statements in the SQL Editor tab. However, if you need to access additional datasources (datastores), click the Open in SQL Editor button to use SQL Editor’s full set of features and comprehensive validation capabilities. This action will prompt you to save, which creates the views in the working database before accessing the SQL Editor. Refer to Working with SQL Editor for more information.

    • To revisit the Rule Mapping Assist’s proposed information, click the Info button.

  3. Save: When saving the finalized rule SQL/DDL:

    • Simple Rule: The SQL expression is saved to the Simple Rule field in the Mapping Action Details section.

    • Complex Rule: The save action creates one or more SQL views (depending on rule complexity) in the working database and creates ETL tasks for the mapped field.

      Note

      • In the case of a complex rule that requires layered views, Migrate creates an ETL task for the main view; however, the main view depends on the layered subviews.

      • If the mapping rule already has existing Views or ETL tasks, Migrate will override them with the updated View DDL and ETL Task definitions.

  4. Reorder ETL Tasks: New ETL tasks are added to the bottom of the Dataset Transform ETL Job. You may need to reorder the ETL tasks before building it.

  5. Build Complete: Build the Complex rule, if applicable and set the Build Status to Complete.

To update the proposed rule DDL, click Propose Rule DDL again to update it from the last saved state.

For example,

Initial Rule Description

Refined Mapping Rule Description

Generated SQL/DDL Statements

(Simple)

First 40 chars only, anything over 40 will not be converted


+ Metadata, if provided

The DESCRIPTION_OPP in ttCRMD_OPPORT_H must be populated with the first 40 characters of the Name from t_CAN_XX_Opportunity. Any characters beyond the 40-character limit must not be included in the conversion.

LEFT(t_CAN_XX_Opportunity.Name, 40)

(Complex - One View)

Set zActive_VBAK to 1 where zSO is 1, or zOpenSO is 1.

+ Metadata, if provided

The field 'zActive_VBAK' in the 'ttVBAK_PREP' table must be set to 1 if either the 'zSO' field or the 'zOpenSO' field in the 'CUST_ITMDEL' table of the 'EUROMS' system is 1.

CREATE VIEW srVBAK_PREP_EUROMS_CUST_ITMDEL_zActive_VBAKUpdSel

AS

SELECT zOpenSO, zSO, zActive_VBAK, 1 AS zActive_VBAKNew

FROM         stVBAK_PREP_EUROMS_CUST_ITMDEL

WHERE (zSO = 1) OR (zOpenSO = 1)

(Complex - Multiple Views in layers)

Street Address, City, State PostalCode' for USA addresses and 'Street Address, City, State, PostalCode, Country' for international addresses.

+ Metadata, if provided

Create a standardized formatted address by combining address components with proper formatting. First, resolve the state field by using State for USA addresses, otherwise use StateCode. Then build the street address by combining Street1 and Street2 when both are present, separated by a comma and space, but use only Street1 if Street2 is blank. Next, create the city-state combination using the resolved state field with proper comma separation and null handling. Then add the postal code with comma separation if present and not blank. Finally, append the country with comma separation, but only include it if it's not blank and not 'USA' (since USA is implied for domestic addresses). The final format should be: 'Street Address, City, State PostalCode' for USA addresses and 'Street Address, City, State, PostalCode, Country' for international addresses.

-- Multiple layered subviews to Satisfy one complex rule

-- Step 1: Resolve the state field

CREATE VIEW AV_LFA1_FOO_SUPPLIER_S_UPD_FORMATTED_ADDRESS_010 AS

SELECT

   *,

   CASE

       WHEN Country = 'USA' THEN State

       ELSE StateCode

   END AS ResolvedState

FROM AV_LFA1_FOO_SUPPLIER_S;

-- Step 2: Build the street address

CREATE VIEW AV_LFA1_FOO_SUPPLIER_S_UPD_FORMATTED_ADDRESS_020 AS

SELECT

   *,

   CASE

       WHEN Street2 IS NOT NULL AND Street2 != '' THEN Street1 + ', ' + Street2

       ELSE Street1

   END AS FormattedStreet

FROM AV_LFA1_FOO_SUPPLIER_S_UPD_FORMATTED_ADDRESS_010;

-- Step 3: Create the city-state combination

CREATE VIEW AV_LFA1_FOO_SUPPLIER_S_UPD_FORMATTED_ADDRESS_030 AS

SELECT

   *,

   CASE

       WHEN ResolvedState IS NOT NULL AND ResolvedState != '' THEN City + ', ' + ResolvedState

       ELSE City

   END AS CityState

FROM AV_LFA1_FOO_SUPPLIER_S_UPD_FORMATTED_ADDRESS_020;

-- Step 4: Add postal code and country

CREATE VIEW AV_LFA1_FOO_SUPPLIER_S_UPD_FORMATTED_ADDRESS_040 AS

SELECT

   *,

   CASE

       WHEN PostalCode IS NOT NULL AND PostalCode != '' THEN

           CASE

               WHEN Country = 'USA' THEN CityState + ' ' + PostalCode

               ELSE CityState + ', ' + PostalCode

           END

       ELSE CityState

   END AS CityStatePostal,

   CASE

       WHEN Country IS NOT NULL AND Country != '' AND Country != 'USA' THEN ', ' + Country

       ELSE ''

   END AS CountryPart

FROM AV_LFA1_FOO_SUPPLIER_S_UPD_FORMATTED_ADDRESS_030;

-- Final view: Combine all components (this is the main view that relies on layered sub-views)

CREATE VIEW AV_LFA1_FOO_SUPPLIER_S_UPD_FORMATTED_ADDRESS AS

SELECT

   *,

   FormattedStreet + ', ' + CityStatePostal + CountryPart AS FORMATTED_ADDRESS

FROM AV_LFA1_FOO_SUPPLIER_S_UPD_FORMATTED_ADDRESS_040;

```

Note

Similarly, use Rule Mapping Assist for complex rules that require multiple ETL tasks or multiple layered ETL tasks to satisfy multiple rules.

Related Articles