Issue with RFC Function RFC_READ_TABLE2

Gaurav Bhadauria 26 Reputation points


We are trying to connect to SAP ECC(Version 7.03) from ADF. Our user in Dev environment can connect to SAP from ADF and can extract the data however, same pipeline is not working in Production environment. We can connect to the production environment but when we try to extract the data, We are getting below error:

CreateFunction GetFunction/SAPDS/RFC_READ_TABLE2 with Repository encountered RfcBaseException.
Lookup of function /SAPDS/RFC_READ_TABLE2 metadata failed for destination

When we checked with our SAP team, they confirmed that dev SAP user has all access but this access right can not be replicated into SAP production environment. They mentioned that if we know which specific Object is responsible for access on data extraction, they can provide access to those specific objects and it will work.

Is it possible for someone to help us here?

Azure Data Factory
Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
9,768 questions
{count} votes

Accepted answer
  1. KranthiPakala-MSFT 46,427 Reputation points Microsoft Employee

    Hello @Gaurav Bhadauria ,

    Thanks for the question and using MS Q&A platform.

    Firstly, I'm not an expert of SAP, but in general ADF depends on RFC(/SAPDS/RFC_READ_TABLE2 or /BODS/RFC_READ_TABLE2), which belongs to PI_BASIS component. Users need to check in SAP system to make sure any of mentioned RFC exists/installed and install it if missing. For any reason if user not able to install it, they need to develop a custom RFC instead as explained in this doc: Create custom function module

    But if you are still blocked, I would recommend reaching out to SAP support team for further help, as this is on SAP side issue.

    Hope this info helps. Do let us know how it goes.


    • Please don't forget to click on 130616-image.png or upvote 130671-image.png button whenever the information provided helps you. Original posters help the community find answers faster by identifying the correct answer. Here is how

1 additional answer

Sort by: Most helpful
  1. Gaurav Bhadauria 26 Reputation points

    Hi Everyone,

    Our SAP team figured it out. We have some organizational security which was the cause. SAP team manually provided access and it worked. so Solution lies with your SAP Team.

    1 person found this answer helpful.