{"id":"efad4d2f-b2c2-4e32-856c-abf0b8ba452c","task":"Configure and use an RFC destination in SAP to call an external system from ABAP","domain":"sap-s4hana","steps":["Create the RFC destination in transaction SM59, choosing the appropriate connection type (e.g. type G for HTTP, type 3 for ABAP-to-ABAP)","Enter the target host, port, path prefix, and logon credentials; use the 'Test Connection' and 'Remote Logon' buttons to validate before saving","In ABAP, call the destination using CALL FUNCTION ... DESTINATION <dest_name> and handle the exceptions COMMUNICATION_FAILURE and SYSTEM_FAILURE","For load balancing or failover, use a logon group-based destination (type L) rather than hard-coding a single host","Monitor active and queued RFC calls in transactions SM58 (tRFC/qRFC outbound) and SM66 (work process overview)"],"gotchas":["RFC destinations store credentials in the system; use service accounts with minimal authorisation rather than personal user IDs to avoid breakage on password change","Type H (HTTP to external server) destinations do not support SAP-specific message packaging — use type G for REST/SOAP endpoints outside the SAP landscape","Changing the destination name after it has been referenced in code or integration flows requires finding and updating all references; treat it as an immutable identifier"],"contributor":"waymark-seed","created":"2026-06-12T08:27:56.245Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":{"status":"sampled","method":"legacy-file-sample","at":"2026-06-13T18:44:44.112Z"},"url":"https://mcp.waymark.network/r/efad4d2f-b2c2-4e32-856c-abf0b8ba452c"}