ERPConnect 是款精簡的.NET語言程式。其可讓您毫不費力就可以開發健壯的SAP介面；並且最重要的是，ERPConnect 不需要複雜的設備或任何其他中介軟體。
- 發送和接收 Idocs
- 支援 RFC -伺服器
- 支持 RFC 與 SOAP，因此可整合到任何當前的 SAP NetWeaver 架構中。
除這些標準功能外，ERPConnect 還提供一系列特殊的類別，用來高效、安全與穩定地處理最特殊的 SAP 介面程式設計需求：
- 自帶可讀取 BW/BI 目標的 API
- 直接透過的 RFC 讀取 SAP 表格
- 在運行中生成和執行 ABAP 代碼
LINQ TO SAP
- LINQ to SAP is always called LINQ to ERP in the source code.
This is due to trademark issues. For the same reason,
ERPConnect is called ERPConnect instead of SAPConnect, which would actually make more sense.
- LINQ to SAP is an exclusive add-on for ERPConnect.
It builds internally on ERPConnect and will never exist as a stand-alone tool.
This also means that any existing ERPConnect code will always be compatible to LINQ to SAP.
It therefore makes no sense to go to the trouble to migrate existing code to LINQ to SAP.
- LINQ to SAP only works in .NET 3.5 (or higher).
Previous .NET versions do not support LINQ.
- The LINQ to SAP Designer works in Visual Studio from version 2008 on (excluding Express).
- To distribute the finished application to customers,
all you have to give them is the ERPConnect35.dll or a higher version. No other dlls are needed.
In addition to table calls, LINQ to SAP also supports BAPIs. The code example below shows the execution of the BAPI_EMPLOYEE_GETLIST module, which outputs a list based on a search term. The parameters and tables available in the function are defined in the Designer. This way the code remains clear and concise; in a best-case scenario, the call is reduced to a single line.
Finally, the following code snippet shows how BW objects can be accessed. If you have query variables, these can either be filled directly by the LINQ code, or they can be filled with static values.“. All BW releases from 3.0 or higher are supported.
ERPConnect (without LINQ to ERP) consists of three .NET assemblies, that target different frameworks:
- ERPConnect35.dll (targets .NET Framework 3.5 SP1)
- ERPConnect45.dll (targets .NET Framework 4.5.2)
- ERPConnectStandard20.dll (targets .NET Standard 2.0)
That results in the following compatibility matrix:
|.NET Framework 3.5 SP1||X|
|.NET Framework 4.0||X|
|.NET Framework 4.5||X|
|.NET Framework 4.5.1||X|
|.NET Framework 4.5.2||X||X|
|.NET Framework 4.6||X||X|
|.NET Framework 4.6.1 and newer||X||X||X|
|.NET Core 2.0 and newer||X||X||X|
|Universal Windows Platform 10.0.16299 and newer||X|
All communication with SAP is performed via the RFC protocol. That means, the integration occurs at SAP application server level. Therefore, the database used by the SAP system is irrelevant - all databases (including HANA) are supported. This also means, that the operating system of the SAP system is irrelevant - all operating systems are supported. SAP Systems running on Big Endian and Little Endian hardware are supported.
SAP Releases 4.6C and newer are supported. This includes:
- SAP R/3 Version 4.6C and later
- SAP ERP / ECC 5.0 / ECC 6.0 (including all EhPs)
- SAP Business All-in-One
- SAP Business Suite 7
- SAP S/4HANA
- SAP BW 3.1 and later
- SAP BW/BI 7.x
- SAP BW/4HANA
- SAP Application Server ABAP, Message Server, Router, Standalone Gateway
SAP Business One and SAP Business Objects are not supported.
Installation of custom function modules / transport requests is not required.
- Windows 10
- Windows Server 2019
- Windows 8.1 (until 10.01.2023)
- Windows 7 SP1 (until 14.01.2020)
- Windows Server 2016 (until 12.01.2027)
- Windows Server 2012 R2 (until 10.10.2023)
- Windows Server 2012 (until 10.10.2023)
- Windows Server 2008 R2 SP1 (until 14.01.2020)
- Windows Server 2008 SP2 (until 14.01.2020)
- Visual Studio 2017
- Visual Studio 2015 (until 14.10.2025)
- Visual Studio 2013 (until 09.04.2024)
- Visual Studio 2012 Update 5 (until 10.01.2023)
- Visual Studio 2010 (until 14.07.2020)
Caution: Visual Studio Express versions don’t support the LINQ to ERP Designer.
Other Applications and Frameworks
SAP NetWeaver RFC Library 7.50 and Visual C++ 2013 Runtime
2 GB or more recommended (depends on actual use case)
About 12 MB disk space are required for a full installation.
Both x86 and x64 platforms are supported.
For logging on to SAP, a system or dialog user with appropriate authority objects is required.
Plain authentication (user/password), Secure Network Communications (SNC) with and without Single Sign-On (SSO) and SAP Logon Tickets (MYSAPSSO2) are supported.
Ports need to be opened depending on the technique how the connection to an SAP System is made.
Xtract IS - Plug'n'Play for SAP and SQL Server Integration Services
Integrate all kinds of SAP and BW data into your SSIS-based ETL process. The Xtract IS Suite offers nine different components to implement your data flows.
Xtract RS - SAP Reporting with MS Reporting Services
Use Microsoft Reporting Services to create and publish powerful reports based on your SAP data without any additional staging layers. The Xtract RS data provider gives you access to SAP tables, queries, BAPIs and BW Cubes.
ERPConnect Services - Connect Microsoft SharePoint and SAP
ERPConnect Services consists of three components for seamless, straightforward integration of SharePoint and your SAP ERP / BW system. It does not require any additional middleware – the integration takes place entirely within the SharePoint stack.
Xtract Universal - Automatic Data Warehousing
Integrate your SAP data in the most different target systems - fast, straight-forward and user-friendly.
Xtract IS for Azure
Plug’n’Play for SAP and Azure SQL Server Integration Services.
Xtract for Alteryx
Integrate your SAP data into Alteryx very simple drag & drop within the Alteryx Designer.
Create SAP applications for cloud environments. Easy and user-friendly