In order to record outbound RFC calls, there are a number of pre-requisite steps that must be performed prior to turning on the recording.
The process for recording is:
Analysis and stub creation
Run analysis program, ST03 usage data is retrieved and analyzed to understand outbound RFC calls, through which RFC destinations and the “stubs” are created if needed. This is a one-off activity. If changes to outbound RFC’s or RFC destinations, then re-run
Review Analysis Output
Review RFC destinations to see which ones can / should be “re-pointed”. Stub must already exist (or have been created) and no parameter mis-matches
Generates outbound RFC wrappers (which also handle inbound RFC as well). Need to check if changes and whether to re-do this or not
Activate the Inbound / Outbound enhancement point.
Re-point RFC destinations
Creates a back-up RFC destination, unique user, and starts redirecting outbound calls
Check that no short-dumps are being caused in production (recording is off at this point but the outbound RFC’s will be going through the wrappers – stubs have no code in them)
Turn on recording
Inputs and outputs captured and stored against current business transaction. Check SHM monitoring.
Turn off recording
Review outbound RFC linkages