Skip to Content
0

Input parameter RFC lookup does not exist

Nov 01, 2016 at 08:32 PM

207

avatar image

Hi All,

In PI an existing successful scenario and was working fine in all environments - Idoc to Proxy xml , where RFC lookup been used to fetch the data from back end system and used in message mapping.

All of a sudden, in PI we are getting an error in mapping "input parameter RFC lookup does not exist"

Nothing has been changed in PI and as well as no patching upgrades been done.

I have done full cache refresh

I have stopped and started the channel

I have even done the dummy changes in the channel and activated

Still the issue persists - Please suggest/help me out from this ASAP, as this issue is in production system and the messages are not transmitting further.

Kind Regards,

Pramod.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

Dan Kennedy Nov 01, 2016 at 10:48 PM
0

Even though you say nothing has changed in PI - I would double check the version history of your mapping objects to be sure.

Check the name of your parameter on your operational mapping, check the binding to the message mapping of the parameter. If you were doing the RFC via a UDF, check the parameter is still labelled with the correct name/exists.

Are you using iFlows? If so and if all your configuration is correct, undeploy and redploy the iFlow which will regenerate the ICO

Share
10 |10000 characters needed characters left characters exceeded
Raghuraman S Nov 02, 2016 at 03:30 AM
0

See if the note- 1307777 helps.

Share
10 |10000 characters needed characters left characters exceeded