Evolve ERP data extract ETL’s to become SAP compliant
In previous posts we highlighted the risks of SAP Indirect Access and the increasing stringent nature of SAP licence audits in this area. As it turned out from the UK ruling in the SAP vs Diageo case – all SAP clients are at risk of unlicenced Indirect Usage access potentially exposing your organization to significant additional fees/penalties if their NON-SAP applications initiate access to SAP functions / services and those users behind the 3rd party application are not covered by appropriate named user licenses of the SAP system.
Think of any regular data warehouses or SAP connected BI systems, where ETL tools use SAP’s RFC_READ_TABLE or similar proprietary SAP functions to access and pull data from SAP ERP in order to feed the NON-SAP users with data. Most of these ETL tools use a shared “technical” SAP user account to connect to SAP, and no individual governs how the actual DWH / BI users are licensed on SAP in most cases.
Does this sound like your DWH / BI environment?
VirtDB can help to mitigate the risk of indirect access claims by enhancing your existing data management / ETL processes. We will use screenshots from Talend Open Studio as an example of the average SAP extractor ETL jobs – and will advice where to change those to remain compliant – but the same method should work for almost all ETL tools (think of Informatica, Oracle, IBM, Alteryx, Microsoft data integration).
Most likely you have workflows like this below (maybe a little more complicated) – an SAP component pulling out data from the ERP system and additional components doing something with the extracted data, like filtering, transforming, combining it and loading / writing to somewhere your end-users can access.