RFC call failed at Receiver channel

[former_member436332]

Hi All,

We have a RFC to check the validity of WBS. RFC works fine in ECC. Import parameter is 11 characters (WBS). If we trigger the RFC from PI with 11 characters WBS, getting an error as shown below.

If we try with 8 digit WBS, RFC is getting triggered and correct output is coming. There are some WBS with length 11 digits. So in that case also this needs to be triggered. But getting the error as above. External debugger in ECC is also not working in this case.

Can anyone tell us why 'To many digits' error is coming & it fails at Receiver channel ?

I would appreciate every comment on this.

[former_member193386 · Accepted solution]

You  try to send integer number with eleven digits, int on sap support only 10 digits

[former_member436332 · Accepted solution]

Thanks for your response.

In SAP ,import parameter is declared as CHAR11

[former_member184720 · Accepted solution]

Is it a change? If so re-import the RFC and send the message again(don't resend from RWB).

What is the type you see in PI?

[former_member182412 · Accepted solution]

Hi Veena,

May be the problem with function module metadata cache, refresh the cache and send the message again.

The cache is cleared when any of the following happen:

- The corresponding RFC channel is restarted

- The RFC channel is changed in the Integration Directory

- The RFC adapter service is restarted

- The Dependent J2EE services are restarted (MessagingSystem,

CPACache, and so on)

- The J2EE server is restarted

Regards,

Praveen.

[former_member436332 · Accepted solution]

Hi Hareesh,

Some changes were made in the RFC. and then RFC were re imported in PI . Still getting same error.

[former_member182412 · Accepted solution]

Hi Veena,

If you import the RFC the changes will not automatically update in meta data cache, you need to manually refresh the cache as mention before. Please check below RFC FAQ note.

SAP Note 730870 - FAQ RFC Adapter

Q 29: When a function module is changed in the backend, are the

changes published to the runtime at real-time?

A: No, an update made to a function module in the backend is not

informed to the runtime. This is because the function module metadata

is cached by the system during the first invocation of the module. All

the subsequent references to this function module are directed to the

cache. Any update made to the function module in the backend will not

be notified to the runtime, unless the cache is cleared.

Regards,

Praveen.

[former_member193386 · Accepted solution]

SAP PI always have a problem with changes in RFC, You can try to do this steps to refresh cache:

1) Do a complete cache refresh using CPA full Cache refresh

2) In dual stack: go to sxi_cache->Go To-> Adapter Engine Cache, remove line on grid.

3) In dua stack: go to sxi_cache->Run Time Cache->Start full cache refresh in background

[former_member436332 · Accepted solution]

Hi Praveen,

We have tried clearing Cache. But still no luck.

[former_member184720 · Accepted solution]

I hope you are sending the new message, instead of resending the failed message.

If the cache refresh doesn't help, try restarting the service "XPI Adapter: RFC" in NWA. That should help.

[former_member193386 · Accepted solution]

Some times, for RFC object be uodated is necessary stop and start from abap service and java service. Because this I´m preffer user ABAP PROXY interface

[iaki_vila]

Hi Veena,

Has you change the RFC metadata in the ECC?. Try to do a dummy change like to change the description and/or to refresh the CPA cache.

Check st22 transaction in the ECC endpoint.

Regards.

[former_member436332]

No errors are there in ST22