Example of an End Point (RFC
Adapter) 
The end point is used in a Business Scenario in which the availability of flights is checked by using a function module call.
SAP system TAG (travel agency) checks the availability in SAP system AIR (airline) by calling the module CHECK_FLIGHT_AVAILABILITY_IN.
Header Data
|
Field |
Value |
|
Receiver business system |
AIR |
|
Receiver interface name |
CHECK_FLIGHTAVAILABILITY_IN |
|
Receiver interface namespace |
urn:sap-com:document:sap:rfc:functions |
|
Description |
Check Flight Availability |
The calls are made to system AIR by using load balancing. The radio button Load Balancing Activated is selected correspondingly.
Attributes
|
Attribute |
Value |
|
Message Server |
airmain |
|
Message Server Service |
3642 |
|
System ID |
AIR |
|
Logon Group |
PUBLIC |
All RFC calls from system TAG arrive at the receiver with the same SNC logon data.
Header Data
|
Field |
Value |
|
Sender business system |
TAG |
|
Sender interface name |
* |
|
Sender interface namespace |
* |
|
Receiver business system |
AIR |
|
Receiver interface name |
* |
|
Receiver interface namespace |
* |
|
Description |
* |
Logon Data
|
Field |
Value |
|
Authentication Procedure |
Secure Network Connection for RFC |
|
User Name |
FLIGHTCHK |
|
SAP Client |
100 |
|
Logon Language |
English |
|
Security Level |
Level 4 – “Maximum Protection of IS” |
|
Partner Name |
TAG |
Also see:
· For more information about using placeholders (for example here, when defining logon data), see Default Procedure.