Microsoft Fabric Mirroring

This page shows how to set up and use the Microsoft Fabric Mirroring destination. This destination enables users to continously map SAP data to a datalake using Microsoft Fabric's open mirroring feature.

About Open Mirroring

Microsoft Fabric's Open Mirroring allows users to replicate existing data directly into Fabric's OneLake from a variety of external databases and other data sources. The data is written into an open mirroring landing zone, where it is processed by the mirroring replication engine of Microsoft Fabric. Mirroring delivers the data incrementally in a parquet format that is used to merge the data in OneLake.

For more information, see Microsoft Documentation: Open mirroring in Microsoft Fabric.

Note

Note that Microsoft Fabric Open Mirroring is still in preview. During preview, not all Fabric regions support Mirroring. For more information, see Microsoft Documentation: Microsoft Fabric preview information.

Workflow

Follow the workflow below to set up Open Mirroring with Xtract Universal:

Create a mirrored database in Microsoft Fabric.
Create a Microsoft Fabric Mirroring destination in Xtract Universal.
Create a TableCDC extraction and assign the Microsoft Fabric Mirroring destination.
Run the extraction to initialize the delta mechanism and optionally load the fist data to Microsoft Fabric.
Schedule the extraction to run in an interval of your choice.

Requirements

An active and running Fabric capacity is required. A paused or deleted capacity affects Mirroring so that no data is replicated.
The Landing Zone URL of a mirrored database in Microsoft OneLake is required, see Microsoft Tutorial: Configure Microsoft Fabric open mirrored databases.
The Microsoft Fabric Mirroring destination is currently only supported by the Table CDC extraction type. Table CDC requires the installation of the corresponding custom function modules in SAP. Also note that Table CDC is licensed and purchased separately from other extraction types.
The Microsoft Fabric Mirroring destination uses Microsoft Entra ID (formerly Azure Active Directory) with OAuth 2.0 for authentication. Make sure the authentication uses the following settings:
- Register Microsoft Fabric OneLake as a Mobile and desktop application, see Microsoft Documentation: Configure platform settings:
- Add the following API permissions:
  - Azure Storage - user impersonation
  - Microsoft Graph - User.Read

Tip

You can also use the regular Table extraction type to extract the initial full load of the Table.

Create a new Microsoft Fabric Mirroring Destination

Follow the steps below to add a new Microsoft Fabric Mirroring destination to Xtract Universal:

In the main window of the Designer, navigate to Server > Manage Destinations. The window “Manage Destinations” opens.
Click [Add] to create a new destination. The window "Destination Details" opens.
Enter a Name for the destination.
Select the destination type Microsoft Fabric Mirroring from the drop-down menu. A list of connection details opens.
Fill out the destination details to connect to the destination.
Click [OK] to confirm your input.

The destination can now be assigned to extractions.

Destination Details

The destination details define the connection to the destination.

Destination-Details

Authentication

The Microsoft Fabric Mirroring destination uses Microsoft Entra ID for authentication. Register Microsoft OneLake as an application in Entra ID and configure OneLake to use the registered application.

Tenant ID

Enter the Directory (tenant) ID of the registered app.

Client ID

Enter the Application (client) ID of the registered app.

Tip

You can copy the tenant ID and client ID in the Microsoft Entra admin center or the Azure portal, where the app is registered.
xu-azure-blob-con-3

Authenticate using Entra ID

Click [Authenticate using Entra ID]. The window "Entra ID" opens.
When prompted, sign in with your Microsoft credentials.
After the sign in, a list of requested permissions is displayed, see Knowledge Base Article: Authentication via Microsoft Entra ID.
Click [Accept] to establish a connection to the storage account.

If the connection is successful, a "Connection successful" info window opens.

Warning

The window "Entra ID" shows a blank screen.
If the window "Entra ID" shows a blank screen, the content is likely blocked by the Internet Explorer ESC (Enhanced Security Configuration) on Windows servers.
To disable the Internet Explorer ESC, refer to the instructions in the Microsoft Documentation: How to turn off Internet Explorer ESC on Windows servers.

Landing Zone

URL

Enter the URL of the Microsoft Fabric Mirroring Landing Zone. The URL uses the following format:
https://onelake.dfs.fabric.microsoft.com/<workspace id>/<mirrored database id>/Files/LandingZone/

You can copy the URL from the Microsoft Fabric portal. The Landing Zone URL is displayed in the details section on the Home screen of the mirrored database.

mirroring-landing-zone-url

Example: https://onelake.dfs.fabric.microsoft.com/12345678-aaaa-bbbb-cccc-123456789abc/12345678-dddd-ffff-gggg-123456789abc/Files/LandingZone

Connection Retry and Rollback

Connection retry is a built-in function of the Microsoft Fabric Mirroring destination. The retry function is activated by default.

Connection retry is a functionality that prevents extractions from failing in case of transient connection interruptions to Microsoft Fabric Mirroring. Xtract Universal follows an exponential retry strategy. The selected exponential strategy results in seven retry attempts and an overall timespan of 140 seconds. If a connection is not established during the timespan of 140 seconds, the extraction fails.

The retry function is applied after receiving one of the following HTTP errors or exceptions:

503 Service Unavailable
504 Gateway Timeout
WebExceptionStatus.ConnectionClosed
WebExceptionStatus.ConnectFailure
WebExceptionStatus.Timeout
WebExceptionStatus.RequestCanceled
WebExceptionStatus.SendFailure
WebExceptionStatus.NameResolutionFailure

Assign the Microsoft Fabric Mirroring Destination to an Extraction

Extractions write data to their assigned destination. Follow the steps below to assign a destination to an extraction:

In the main window of the Designer, select an extraction.
Click [ Destination]. The window “Destination Settings” opens.
In the “Destination Settings” window, select a destination from the dropdown list.
Optional: edit the destination settings.
Click [OK] to confirm your input.

When running the extraction, the extracted SAP data is now written to the destination.

Destination Settings

The destination settings only affect the extraction that the destination is assigned to. To open the destination settings, select an extraction in the main window of the Designer and click [ Destination]. The window "Destination Settings" opens.

Destination-settings

File Name

Determines the name of the target table. The following options are available:

Option	Description
Same as name of SAP object	Copy the name of the SAP object.
Same as name of extraction	Adopt the name of the extraction.
Fully qualified extraction name	Adopt the name of the extraction, including the path of the extraction. This option avoids conflicts, when the extraction names are not unique. Use the fully qualified extraction name when the same extraction name is used in multiple extraction groups.
Custom	Define a name of your choice.

Append timestamp

Add the timestamp in the UTC format (_YYYY_MM_DD_hh_mm_ss_fff) to the file name of the extraction

Note

If an object's name does not begin with a letter, the prefix 'x' is automatically appended, e.g., _namespace_tabname.csv is renamed to x_namespace_tabname.csv upon upload.
This ensures compatibility with Azure Data Factory, Hadoop, and Spark, which require names to start with a letter or handle certain symbols differently.

Use Script Expressions as Dynamic File Names

Script expressions can be used to generate a dynamic file name. This allows generating file names that are composed of an extraction's properties, e.g. extraction name, SAP source object. This scenario supports script expressions based on .NET and the following XU-specific custom script expressions:

Input	Description
#{Source.Name}#	Name of the extraction's SAP source.
#{Extraction.ExtractionName}#	Name of the extraction.
#{Extraction.FullyQualifiedExtractionName}#	Name of the extraction. If the extraction is part of an extraction group, the name of the extraction group is included in the extraction name. This option avoids conflicts, when the extraction names are not unique.
#{Extraction.Type}#	Extraction type (Table, ODP, BAPI, etc.).
#{Extraction.SapObjectName}#	Name of the SAP object the extraction is extracting data from.
#{Extraction.Timestamp}#	Timestamp of the extraction.
#{Extraction.SapObjectName.TrimStart("/".ToCharArray())}#	Removes the first slash '/' of an SAP object. Example: /BIO/TMATERIAL to BIO/TMATERIAL - prevents creating an empty folder in a file path.
#{Extraction.SapObjectName.Replace('/', '_')}#	Replaces all slashes '/' of an SAP object. Example /BIO/TMATERIAL to _BIO_TMATERIAL - prevents splitting the SAP object name by folders in a file path.
#{Extraction.Fields["FISCPER"].RangeSelections[0].LowerValue}#	Lower value of the range selection.
#{Extraction.Fields["FISCPER"].RangeSelections[0].UpperValue}#	Upper value of the range selection.
#{Extraction.Context}#	Only for ODP extractions: returns the context of the ODP object (SAPI, ABAP_CDS, etc).
#{Extraction.Fields["[NameSelectionFiels]"].Selections[0].Value}#	Only for ODP extractions: returns the input value of a defined selection / filter.
#{Odp.UpdateMode}#	Only for ODP extractions: returns the update mode (Delta, Full, Repeat) of the extraction.
#{TableExtraction.WhereClause}#	Only for Table extractions: returns the WHERE clause of the extraction.

Convert dates

Converts the character-type SAP date (YYYYMMDD, e.g., 19900101) to a special date format (YYYY-MM-DD, e.g., 1990-01-01). Target data uses a real date data-type and not the string data-type to store dates.

Year 0

Converts the SAP date 00000000 to the entered value.

Year 9999

Converts the SAP date 9999XXXX to the entered value.

Invalid values

If an SAP date cannot be converted to a valid date format, the invalid date is converted to the entered value. NULL is supported as a value. When converting the SAP date the two special cases 00000000 and 9999XXXX are checked first.

Last update: March 28, 2025