Skip to content

Configure SAP Data Sources in NCC Portal

This article describes how to configure and manage SAP server connections in the NCC Portal, following Microsoft Learn Fabric documentation style.

Prerequisites

Before you start, make sure you have:

  • Gateway cluster name
  • Connection name
  • Connection type (e.g., SAP Table Application Server)
  • Data source path (SAP connection details)
  • Authentication method
  • Username
  • Password

Step 1: Create an SAP Connection

To connect your SAP server to your Fabric tenant:

  1. Go to Manage Connections and Gateways and select + New to create a new connection.
  2. If required, create a private endpoint.
  3. Name your connection using the CON_NCC prefix (e.g., CON_NCC_SAPT_DVLM).

  4. Select SAP Table Application Server as the connection type and provide the SAP server details:

    Field Example Value
    Gateway cluster name dgwxgn01
    Connection name CON_NCC_SAPT_DVLM
    Connection ID c7ad3e42-ee54-4184-9797-4e4730572505
    Connection type SAP Table Application Server
    Data source path {"appServerName":"vhmvutstci.sap.enterprise.loc","systemNumber":"00","clientID":"300","languageCode":null}
    Authentication Username/Password

Step 2: Add a Data Source

  1. In the NCC Portal, navigate to Tenant Settings > Data Sources.
  2. Select Add DataSource.

  3. Complete the following fields:

    Field Description Example/Default Value
    Name Data source name in NCC SAP_Sales
    Data Source Type Type of data source SAP or SAP_HANA
    Namespace Prefix for storing data in Lakehouses SAP_Sales
    Code Identifier for pipelines SAP_01
    Description Description of the data source SAP server connection to SAP_Sales
    Connection Name of the connection in Fabric CON_NCC_SAPT_DVLM
    Environment NCC environment for the data source Development

Step 3: Create a Landing Zone Entity

  1. Go to Landing Zone Entities.
  2. Select New Entity.

  3. Fill in the required details:

    Field Description Example/Default Value
    Pipeline Not used PL_LDZ_COPY_FROM_SAP_01
    Data Source Data source for connection SAP_Sales
    Source schema SAP schema or table name SFLIGHT
    Source name SAP table or view name SFLIGHT
    Incremental Extract data incrementally False
    Has encrypted columns Indicates if the table contains sensitive data False
    Entity value Optional. Entity values reference See below
    Lake house Lakehouse for storing data LH_Data_Landingzone
    File path File path for data storage SAP_Sales
    File name File name for data storage SFLIGHT
    File type Expected file type Table

Example Entity value for SAP (Table or HANA):

Name Value Description
rfcTableOptions Expression for the RFC table select query; optional
customRfcReadTableFunctionModule Expression for custom RFC Read Table function module; optional
rfcTableFields Expression for columns to extract from RFC table; optional
partitionOption Expression for partitioning option; optional
partitionColumnName Expression for partition column name; required when partitioning is enabled
partitionUpperBound Expression for upper bound of partition column in hhmmss format; optional
partitionLowerBound Expression for lower bound of partition column in hhmmss format; optional
maxPartitionsNumber Expression for maximum number of partitions as a whole number; optional

Step 4: Create a Bronze Zone Entity

  1. Go to Bronze Zone Entities.
  2. Select New Entity.

  3. Enter the following information:

    Field Description Example/Default Value
    Pipeline Orchestrator pipeline for parsing PL_BRZ_COMMAND
    Landing zone entity Landing zone entity to be parsed SAP_Sales/SFLIGHT
    Entity value Optional. Entity values reference See above
    Column mappings Optional. Column mapping info
    Lake house Lakehouse for storing data LH_Bronze_Layer
    Schema Schema for storing data dbo
    Name Table name for storing data SFLIGHT
    Primary keys Unique identifier fields (Case sensitive) CARRID, CONNID, FLDATE

Step 5: Create a Silver Zone Entity

  1. Go to Silver Zone Entities.
  2. Select New Entity.

  3. Provide the following details:

    Field Description Example/Default Value
    Pipeline Orchestrator pipeline for parsing PL_SLV_COMMAND
    Bronze layer entity Bronze layer entity to be parsed dbo.SFLIGHT
    Entity value Optional. Entity values reference See above
    Lake house Lakehouse for storing data LH_Silver_Layer
    Schema Schema for storing data dbo
    Name Table name for storing data SFLIGHT
    Columns to exclude Comma-separated columns to exclude (Case sensitive)
    Columns to exclude from history Comma-separated columns to exclude from compare (Case sensitive)

Next steps