Skip to content
FAST SAP SOLUTIONS®Discuss a project

START HERE · NO PRIOR TOPIC KNOWLEDGE NEEDED

What it is. Why it matters.

Transactional RFC, or tRFC, manages relevant remote function deliveries. SM58 displays pending or failed units, which need to be matched to their destination and business operation.

Completely new to SAP?

Manufacturers use SAP to connect work such as buying components, recording inventory, planning production, shipping equipment and accounting for costs. SAP S/4HANA is an enterprise resource planning system: it connects these activities through shared business data.

SAP Business Technology Platform, or BTP, provides cloud services for applications, data and integration. A connection needs a route, an identity and permission to perform the intended task.

A transaction code, or t-code, is a shortcut to a task in classic SAP GUI. Fiori apps provide another way to work. Names and screens depend on the product and release; you do not need a live system to learn the concepts in this guide.

Original editorial vector illustration for SAP SM58 tRFC failure: Why a successful manual retry is not the whole answer
Original FSS editorial vector illustration. Conceptual artwork, not an SAP interface or customer-system evidence.
Scope and source-review notes

Scope and evidence

Source review by FAST SAP SOLUTIONS® editorial. This badge describes our editorial review; it does not represent SAP certification or independent endorsement.

Classic ABAP transactional RFC monitoring. The intermittent application-server example is a specific SAP support scenario, not a diagnosis of every SM58 error.

Documentation review on 14 November 2026 using official SAP sources and indexed official excerpts where full Help text was unavailable. Scope and service or release differences are explained in the lesson. All datasets, requests and checks are illustrative; no customer SAP runtime execution or measured results are claimed.

A MANUFACTURING EXAMPLE

Trace a factory integration from the actual sender

Track the remote unit

Remote unit: Relevant transaction identity. Destination: Confirm exact receiver. Current evidence: Pending or failed delivery. Business outcome: Check receiver processing
What to notice: A failed connection and a missing or already-processed business document require separate evidence.Original annotated example with illustrative values. This is not an SAP screen or a result from a customer system.
Read the example values
Remote unit
Relevant transaction identity
Destination
Confirm exact receiver
Current evidence
Pending or failed delivery
Business outcome
Check receiver processing
Words you’ll meet in this guide
Backend
The service or system doing the work behind an interface.
Destination
Named connection settings for another service.
Credential
Access information used to prove an identity.
Subaccount
A BTP scope for applications, services and access settings.
ABAP
SAP’s programming language for business applications.
IDoc
A structured SAP document format used to exchange business data.
RFC
Remote Function Call: a way for one system to call functions in another.
LUW
Logical unit of work: a group of related changes considered together by the relevant transaction model.
Preview the practical steps

SEE THE CONNECTION

See it in a simple example.

A small example to make the idea concrete.

Remote unit → Destination and error → Verified delivery outcome. Conceptual diagram for SAP SM58 tRFC failure: Why a successful manual retry is not the whole answer.
Apply the idea: A manufacturer's transactional RFC processing fails from one application server even though a different connection test succeeds.An illustrative example, not a live SAP screen. The connections show how to think about the topic; they are not instructions to change a system.
  1. Trace a factory integration from the actual sender

    A manufacturer's transactional RFC processing fails from one application server even though a different connection test succeeds.

  2. A successful manual retry proves one execution path, not a permanent repair

    SM58 displays classic transactional RFC units that were unsuccessful or scheduled for later handling.

  3. Understand the transaction boundary and identity

    Classic tRFC groups relevant calls to the same destination within the sender’s commit interval into a logical unit of work.

  4. Worked case: one sender application server cannot reach the receiver

    Imagine destination ERP_TARGET used by a scheduler group containing application servers APP_A and APP_B.

Reading map · FSS editorial. The sections below explain each part in detail.

Found this useful?

Share this guide with your network, or leave a like.

LinkedIn WhatsApp

Your like is saved in this browser.

Explore Knowledge Hub

Discuss Your SAP Project

Your enquiry is sent through this website and used only to respond to your request.