on 2024 Feb 04 11:00 PM
Hi,
After setting the parameter rfc/callback_security_method with Value 3, we have noticed few runtime dumps in our Development system. These runtime dumps corresponds to the RFC callback Rejection.
To fix the issue we have maintained the RFC callback whitelist in SM59 for the particular RFC for which we got dumps.
We are expecting, similar dumps in UAT and production system for different other RFCs.
Hence requesting your assistance to check how can we maintain called function module and callback function module for every RFC in order to avoid RFC callback rejections?
Thanks.
Request clarification before answering.
Hello,
The rfc/callback_security_method parameter with value 3 means the highest of security per KBA 3349924 - Impacts of the parameter rfc/callback_security_method.
It is recommended to run it with value 2 (simulation mode) for some days to capture the SM59 destinations that needs adjustments, per KBA 1971118 - No RFC callback check.
Then, you may maintain the collected entries also per guided in the above KBA.
Best regards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
65 | |
7 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.