SAP AS ABAP Administration · RFC, CPI-C & Network Connectivity

A type-3 RFC destination to another SAP system suddenly fails to log on after a routine password rotation on the target. What design fact explains this, and what user type should have been used?

Answer locked. Get the free KnowCard app to reveal it — plus spaced-repetition review so it actually sticks.

This is one card from the KnowCard library — thousands more across SAP, Linux, Python and more. In the app you get the answer, AI explanations, and cards that come back right before you would forget them. Free to start on iOS, Android or the web.

More in RFC, CPI-C & Network Connectivity

An RFC destination left with no logon credentials tests fine interactively but breaks the moment a background job uses it. Why?

You need to add RFC/gateway capacity to a landscape but the host has no spare resources for dialog work processes. What kind of instance can you install, and what does it deliberately lack?

For an HTTP RFC destination, single sign-on with the same SAP user and trusted-RFC logon are offered for one connection type but not the other. Which type gets them, and why?

Unlike tRFC/qRFC where the source system pushes data to the target, how does the Local Data Queue (LDQ) deliver data, and what scenario is it built for?

You need to protect the network links between SAP system components with your organization's own security product rather than SAP's built-in mechanisms. Which interface makes that possible?

A WAN link works fine between the SAP GUI frontends and the application servers, so the team wants to stretch the same WAN between the application server and the database server. Why is that a mistake?

Start learning today

Free to start — download the app or use it in your browser.