Logic Apps: SAP RFC call not working after SAP added a new Parameter

Jeevi Danda 71 Reputation points
2023-06-06T20:34:03.6033333+00:00

Hi,

I am using logic apps 'SAP call RFC function' to call SAP. It's working fine so far. But our SAP team added one new input parameter and I am passing this new parameter from logic apps the same way I am passing all the other parameters. But I am getting the below error,

"message": "Parameter: 'I_FREIGHT' not found in the function metadata."

I validated these changes from other application and it's working fine but from azure I am getting this new parameter error. When I test my logic app without adding this new parameter, it's working.

Does logic apps save any of the old SAP RFC schemas? Not sure why it's not working from azure logic apps. Please suggest if I am missing anything.

Thanks,

Jeevi

Azure Logic Apps
Azure Logic Apps
An Azure service that automates the access and use of data across clouds without writing code.
3,543 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Sonny Gillissen 3,751 Reputation points Volunteer Moderator
    2023-06-09T03:26:31.7+00:00

    Hi Jeevi Dandaa

    Thanks for reaching out on Microsoft Q&A!

    This behaviour is caused by caching in the on-premises data gateway, in specific the SAP .Net (Nco) library. It keeps a copy of the function module for some time (not sure what time). Overnight it most likely should start working again.

    One way to force a “refresh” of the cache is by restarting the on-premises data gateway server.

    Please click ‘Accept answer’ when you think my answer is helpful. Feel free to drop additional queries in the comments below!

    Kind regards,

    Sonnt

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.