TimeXtender Azure Data Factory SAP Table data source

General change to Data Factory data sources:

All connection settings now includes a property "Destination integrated runtime" which will be applied to the destination linked service if it has been set.

Logon

There are two options Application Server and Group

You can read about the group option in the following link

Configure and use logon group (ABAP)

SNC options

This is about how the communication is being done. There is an explanation of it here

Secure Network Communications (SNC)

Connection

You need to fill out the various fields.

• Client ID is where you add the client id for your company.
• In the Language field EN is equal to English, so that would normally be what you would add.
• AS4 version can be kept as the default value. Specify the version if you are using another.
• The Username is an user with access to the server.
• The Password is the password for the user account used.
• The Integration runtime name is the integration runtime that runs on the server that connects to the SAP server.
• The Command timeout is the default timeout set. It is set to 1440 seconds.

Table name and column naming

You can state a conversion of the table names by clicking on the Translate table and column names button and then adding a Translation language in the appearing field.

SAP uses multiple codes to represent a language. In the SAP GUI you will usually see a two or four letter code like EN, DE or enUS, deDE for English / German. But internally, SAP uses 1char to store the language code [0…9], [A…Z], and [a…z].

Table T002 contains these languages and their codes. Please find the list in the hidden section below.

Example: Serbian (Latin) is SH, or shYU, or d.

Z2 and Z3 are reserved for Customer languages. So you can setup these with e.g. your own “test” languages.

Table selection

The connection setup in the portal contains two type of table selection

• Module selection
• List of tables

Modules to include

Selecting a module will automatically make tables associated with the module available in the Ingest instance.
Find what the different modules contains see: SAP Important Tables per Common Modules.csv
Be aware that the list contains none extractable objects which are left out in the data source.

Tables to include

Simply enter the names of the tables you want to include from SAP.

Partitioning:

The implementation includes a default partitioning setup which can be found in the file Partitions.json that is attached.

Override default partitioning is checked the user will need to provide the path to the file containing the custom partitioning setup. The file needs to be structured like in the SAP table partition settings defaults

[
    {
        "Column": "CPUDT",
        "LowerBound": 197001,
        "MaxNumberOfFiles": 683,
        "PartitionType": "Month",
        "Table": "BKPF",
        "UpperBound": 202612
    },
    {
        "Column": "BUDAT",
        "LowerBound": 197001,
        "MaxNumberOfFiles": 683,
        "PartitionType": "Month",
        "Table": "BSEG",
        "UpperBound": 202612
    },
    {
        "Column": "ERDAT",
        "LowerBound": 197001,
        "MaxNumberOfFiles": 683,
        "PartitionType": "Month",
        "Table": "VBAK",
        "UpperBound": 202612
    },
    {
        "Column": "ERDAT",
        "LowerBound": 197001,
        "MaxNumberOfFiles": 683,
        "PartitionType": "Month",
        "Table": "VBAP",
        "UpperBound": 202612
    },
    {
        "Column": "AEDAT",
        "LowerBound": 197001,
        "MaxNumberOfFiles": 683,
        "PartitionType": "Month",
        "Table": "EKKO",
        "UpperBound": 202612
    },
    {
        "Column": "AEDAT",
        "LowerBound": 197001,
        "MaxNumberOfFiles": 683,
        "PartitionType": "Month",
        "Table": "EKPO",
        "UpperBound": 202612
    },
    {
        "Column": "ERDAT",
        "LowerBound": 197001,
        "MaxNumberOfFiles": 683,
        "PartitionType": "Month",
        "Table": "AUFK",
        "UpperBound": 202612
    },
    {
        "Column": "ERDAT",
        "LowerBound": 197001,
        "MaxNumberOfFiles": 683,
        "PartitionType": "Month",
        "Table": "AFKO",
        "UpperBound": 202612
    },
    {
        "Column": "UDATE",
        "LowerBound": 197001,
        "MaxNumberOfFiles": 683,
        "PartitionType": "Month",
        "Table": "CDHDR",
        "UpperBound": 202612
    },
    {
        "Column": "UDATE",
        "LowerBound": 197001,
        "MaxNumberOfFiles": 683,
        "PartitionType": "Month",
        "Table": "CDPOS",
        "UpperBound": 202612
    }
]

Azure Data Factory - SAP Table

The data source currently supports moving data to Data Lake gen2 storage.
It supports all currently functions for an Azure Data Factory data source.

The setup is as for all other Azure Data Factory data sources. 

The new Destination integrated runtime field is a field that allows you to choose a specific Azure integration runtime, instead of just a location runtime. If you aren’t specifying one the default AutoResolveIntegrationRuntime will be used.