Fact Sheet Mapping Between ServiceNow and SAP LeanIX

Fact Sheet Mapping

To configure mappings between fact sheet fields and ServiceNow tables, start by creating fact sheet mappings. After that, proceed to configure field mappings.

📘

Note

When you create a new ServiceNow configuration, it already contains default mappings. You can adjust the default configuration to suit your needs.

To view detailed information on mappings, you can download the mapping matrix.

Configuring a Fact Sheet Mapping

Follow these steps:

1. On the ServiceNow configuration page, navigate to the Mappings tab.

2. To create a new mapping, under Fact Sheet Mapping, click Add Fact Sheet Mapping. If the mapping you need already exists, select it and adjust the configuration as needed.

   

3. Configure mapping parameters.

   1. Define the fact sheet type, synchronization direction, ServiceNow table, and synchronization mode.
   2. Configure field mappings. For detailed information, see Field Mapping.
   3. Optionally, configure synchronization filters (constraints) to limit the number of synced records. For details, see Synchronization Filters.

4. To save a mapping without activating it, turn off the toggle next to the fact sheet type.

5. Save your changes.

Once you’ve added fact sheet mappings, you can modify, activate, deactivate, or delete them.

Fact Sheet Mapping Parameters

For each mapping, you can define the rules for syncing specific fields between SAP LeanIX fact sheets and ServiceNow tables.

The table below lists fact sheet mapping parameters.

Field Mapping

After setting up a fact sheet mapping, you can configure field mappings for it.

Configuring Field Mappings

Follow these steps:

1. Hover over a fact sheet mapping, then click Configuration under Field Mapping.

   

2. On the field mapping page, add mappings by clicking Add Fields, then configure mapping parameters. For more information on each parameter, refer to the following sections in this topic.

3. If relevant, set up matching rules to define how the integration identifies matching items. For more information, see Matching Rules.

   

4. Save your changes.

Field Mapping Parameters

The table below lists the parameters for configuring field mappings.

AI-Generated Field Mapping Suggestions

To streamline the process of configuring field mappings, you can use the AI capabilities optional feature. To learn how to activate this feature, see Activating AI Capabilities.

To generate field mapping suggestions using AI, on the field mapping configuration page, click Generate Fields. AI generates mapping suggestions based on common patterns and your system configuration. Before applying suggested mappings, review and adjust them as needed. You can edit fields manually as well as add or remove fields.

📘

Note

AI-generated field mapping suggestions can be inaccurate or misleading. Ensure to review suggestions and adjust them if needed before applying the changes.

Mapping Type

The following table contains mapping types.

To learn more about field types in ServiceNow, refer to the ServiceNow documentation..

Additional Configuration Details

Configure Details is a button that is only offered for some special mapping types to provide more configuration, like a mapping of fixed values for choices.

One example of the use of the Configure Details section is the VALUE_MAPPING. VALUE_MAPPING is used when fixed values from SINGLE_SELECT fields must be mapped to choices in the CHOICE field type in ServiceNow.

The example below shows VALUE_MAPPING configuration of SAP LeanIX's businessCriticality field with ServiceNow's business_criticality attribute.

Here the left side indicates the Meta Model name values of within the businessCriticality field in SAP LeanIX. Similarly, the right side is mapped to the value of the choices within the business_criticality attribute in ServiceNow.

👍

Tip

Use Fact Sheet configuration menu to get the meta model key of the fields in SAP LeanIX. Translations are not relevant in the VALUE_MAPPING section

The meta model keys are visible within brackets, as seen below -

Similarly, within ServiceNow, they can be seen by right-clicking on the field and selecting "Show Choice List"(Admin access required) -

Only the VALUES section is required for the mapping -

Each VALUE_MAPPING is validated when you save the configuration, and during every synchronization, to ensure only valid values are used for mapping from SAP LeanIX to ServiceNow.

🚧

n:1 Value Mapping Supported only when the source of truth is SAP LeanIX

Attaching multiple values in the SINGLE_SELECT field to 1 VALUE in the Choice List field in ServiceNow is supported, provided the source of truth is SAP LeanIX.

Synchronization Filters

Synchronization filters enable you to refine fact sheet mappings by limiting the number of records synchronized. The configuration of filters depends on which system is designated as the source of truth:

• If SAP LeanIX is the source of truth, add the necessary filters in SAP LeanIX.
• If ServiceNow is the source of truth, add the necessary filters in ServiceNow, then select these filters in SAP LeanIX. In this scenario, filters are referred to as constraints.

Additionally, you can configure graph rule constraints to determine whether a record should be synchronized based on a connection identified in ServiceNow.

Filtering from SAP LeanIX to ServiceNow

When SAP LeanIX is the source system, you can apply inventory filters to fact sheet mappings to only send specific fact sheet fields to the corresponding ServiceNow table. Here are examples of frequently used filters for application fact sheets:

• Approved quality seal: Only send applications that have an approved quality seal to ServiceNow.
• Active lifecycle phase: Only send applications that are in the Active lifecycle phase to ServiceNow.

To add a filter, follow these steps:

1. Hover over a fact sheet mapping where the synchronization direction is from LeanIX, then click Filters under Filter.

   

2. In the filter overlay that appears, select fact sheet attributes to be synchronized, then click Use Fact Sheet Filter.

3. Save your changes.

Filtering from ServiceNow to SAP LeanIX

When ServiceNow is the source system, you can add a filter in ServiceNow to limit the number of records that are sent to SAP LeanIX. These filters are also referred to as constraints.

To add a filter, follow these steps:

1. In ServiceNow, create a filter for the table from which data is synchronized. Once you save the filter, it appears in SAP LeanIX.

   You can create a filter by either impersonating an integration user or using an admin user. If you're impersonating an integration user, you can make the filter visible only to this user (me). If you're signed in as an admin, set the filter permission to everyone or group to ensure that the integration user can access the filter.

   

2. In SAP LeanIX:

   1. Hover over a fact sheet mapping for which you created a filter, then click Constraints under Filter.

      

   2. In the overlay that appears, select the filter that you created.

   3. Save your changes.

📘

Note

The number of filters available for a table in ServiceNow depends on the visibility of those filters to the integration user (for example, leanix.integration). By default, a user can only view filters created by the same user for a specific table.

If the user belongs to a user group and the filter_group role is assigned to the user, they can view filters created for that group as well as filters created for all users.

Graph Rule Constraints

A Graph Rule Constraint controls whether a record is synchronized at all based on a connection found on the ServiceNow side. Depending on the ServiceNow table used in a mapping from ServiceNow to SAP LeanIX, different or no Graph Rule Constraint might be applicable.

The configuration dialog for Sync Constraints is opened when ServiceNow is the Source, the configured ServiceNow Table supports the Graph Rules, and the 'Constraints' button is pressed.

Various types of Graph Rules are explained as follows -

The relations between applications and IT components are discovered in ServiceNow using Graph Rule Constraints. This information is abstracted by the integration, and only the abstracted information is pulled into SAP LeanIX. Then the relations between applications and IT components can be fetched using the GRAPH_RULE_CONSTRAINT relation. For more information, see GRAPH_RULE_CONSTRAINT.

Advanced Mapping Use Cases

In this section, you can find advanced use cases for configuring fact sheet mappings.

Mapping Multiple-Select Fields

The integration can sync between Multiple Select fields in SAP LeanIX with Glide Lists fields of ServiceNow that refer to a table in ServiceNow.

Prerequisites

• Multiple Select Field with values in SAP LeanIX
• GlideList field in ServiceNow, with the values of the records you wish to map to SAP LeanIX or the sys_id of the records in the referenced table in ServiceNow.

Within ServiceNow however, there can be two types of list fields -

• List fields that reference another ServiceNow Table

• List fields that do not refer to another ServiceNow Table and have a choice list defined

To map both of these fields, the Mapping Type of VALUE_MAPPING is used -

🚧

Make sure to fill in the extra fields section!

Mapping multiple select fields requires you to map the meta model name of the values of the multiple select field in SAP LeanIX with the values of either the sys_ids of the records or the values of the choices from the ServiceNow side.

• Example Extra field mapping when the field is referencing another table -

Collect the sys_id of all the records you wish to map with the multiple select values in SAP LeanIX, this can be done for multiple records by exporting or by selectively copying the sys_id as follows -

These collected sys_ids can be mapped to SAP LeanIX as follows -

🚧

Unmapped values will be ignored

If the extra field section does not fully cover the mappings, any additional values on each system will be ignored by the sync.

Once saved, the sync will automatically match the sys_ID with the respective record in ServiceNow. Similarly, it will also match the sys_ID with the mapped field in SAP LeanIX from the extra fields section.

Examples -

Mapping Lifecycle and Date Fields

This section provides an overview of the supported methods for syncing lifecycle and date fields between ServiceNow and SAP LeanIX. The following table details each scenario and the required configurations.

Mapping Multiple Fact Sheet Types to One ServiceNow Table

You can map multiple fact sheet types to the same ServiceNow table in the following cases:

• ServiceNow is the source of truth for mappings.
• Filters are set to ensure that there is no overlap in data synchronization.

An example scenario might involve records in ServiceNow that are not yet fully distributed across the appropriate tables, and instead, reside within a single table, such as the cmdb_ci_appl table. In this case, you can link this table to both applications and IT components, making ServiceNow the source of truth. To ensure accurate data synchronization, you also need to set appropriate filters.