💖 "A Remote Call to the Heart" — A Story of Two ABAPers

In the quiet hum of the SAP system landscape, two developers worked side by side—Minu, curious and bright, and Arnav, wise with years and experience. Their connection grew like clean code—structured, meaningful, and waiting to be executed.

Minu admired Arnav’s calm, his mastery over Function Modules, the way he debugged life’s problems like he debugged programs. She wanted to say something. To tell him that in the huge data table of her heart, he was the primary key. But feelings, unlike ABAP, don’t always follow syntax.

She opened SE37 and created a Function Module called Z_EXPRESS_FEELINGS. But she hesitated—she didn’t know if it would compile in the real world. What if it raised an exception called REJECTION_NOT_HANDLED?

So, she saved it but didn’t execute.

Arnav, sensing something in her silences, decided to take the first step. He marked his own heart as remote-enabled. He believed love, like RFCs, could travel across time, age, and fear—as long as the destination was trusted.

One afternoon, he sent an emotional RFC call:

CALL FUNCTION 'Z_EXPRESS_FEELINGS'
  DESTINATION 'Minu_Heart'
  EXPORTING
    Emotion = 'Respect, Care, and Love'
  EXCEPTIONS
    Heart_Closed = 1
    OTHERS       = 2.

To his relief, the connection was successful. Minu’s heart, though unsure, returned a gentle response: SY-SUBRC = 0.

Still unsure how to say it aloud, Minu turned to SAP’s own way of expressing emotions—BAPIs. She called:

CALL FUNCTION 'BAPI_RELATIONSHIP_CREATE'
  EXPORTING
    Partner1 = 'Minu'
    Partner2 = 'Arnav'
    RelationshipType = 'TrustAndLove'.

No dump. No error. Just a commit work… and a smile across the monitor.

From then on, their code merged—not just in the system, but in life. She learned from him, and he found new joy in her curiosity. Together, they built modules not just for SAP, but for love, stitched with debugging sessions, long walks, and shared dreams.

💌 Moral:

Sometimes, love needs a remote-enabled function—a little courage sent across distance or hesitation. And sometimes, the perfect expression is not spoken, but coded... with heart.


Here’s a concise yet detailed explanation of each with definitions, differences, and interview-ready pointers:

📌 1. Function Module (FM)

Definition:
A Function Module in ABAP is a reusable procedure that encapsulates a set of related statements. It is stored in the Function Library (via transaction SE37) and can be called from any ABAP program.

Key Features:

  • Has Import, Export, Changing, and Tables parameters.

  • Can raise exceptions.

  • Grouped under Function Groups.

  • Used for modularizing code.

Example:

CALL FUNCTION 'DATE_COMPUTE_DAY'
  EXPORTING date = '20250527'
  IMPORTING day = lv_day.

📌 2. Remote Function Call (RFC)

Definition:
RFC is a mechanism that allows communication between different SAP systems (or between SAP and external systems) via Function Modules marked as remote-enabled.

Types of RFC:

  • sRFC (Synchronous)

  • aRFC (Asynchronous)

  • tRFC (Transactional)

  • qRFC (Queued)

Key Requirements:

  • The FM must be flagged as Remote-Enabled Module in SE37.

  • You must define a destination via transaction SM59.

Example:

CALL FUNCTION 'Z_REMOTE_FM'
  DESTINATION 'TARGET_SYSTEM'
  EXPORTING param1 = 'value1'.

📌 3. BAPI (Business Application Programming Interface)

Definition:
BAPI is a standardized, officially released Remote-Enabled Function Module provided by SAP for business object operations (like creating a sales order, retrieving material data, etc.).

Key Features:

  • Always remote-enabled.

  • Part of the Business Object Repository (BOR).

  • Can be explored using transactions: BAPI, SWO1, SE37.

  • Designed for stable external access to business data.

Example:

CALL FUNCTION 'BAPI_CUSTOMER_CREATEFROMDATA1'
  EXPORTING customerdata = ls_customer
  IMPORTING customerno   = lv_customerno.

🔍 Differences Summary:

Feature Function Module RFC BAPI
Scope Local modular function Cross-system or client calls Standard SAP business API
Remote-enabled Optional Required Always remote-enabled
Standardization Custom or SAP-defined Any remote call Strictly standardized by SAP
Use Case Internal reuse Integration across systems Business-level operations (e.g. Sales)
Access via BOR No No Yes (Business Object Repository)
Example DATE_COMPUTE_DAY Z_REMOTE_FM BAPI_SALESORDER_CREATEFROMDAT2

✅ Interview Tips:

  • Always mention that BAPIs are a subset of RFC-enabled Function Modules.

  • Emphasize real-world examples (e.g., using BAPI to create a customer).

  • Know how to check or create a remote-enabled function module.

  • Be ready to explain commit handling after BAPI calls (use of BAPI_TRANSACTION_COMMIT).

🧠 Final Wrap:

F-R-B → "Friendly Remote Business"

Mnemonic PartConceptKeyword Reminder
F – FriendlyFunction ModuleReusable, Internal
R – RemoteRFCRemote-enabled FM
B – BusinessBAPIOfficial API from SAP

Comments

Post a Comment

Popular posts from this blog

SQVI Query using "Alias"

Image
Can we use a table again in SQVI Transaction code? What is “Alias” in SQVI Transaction Code? One of my colleague came to me and said I don't know if we can use a table multiple times in SQVI query. I thought there should be something which can help us. We searched and find “Alias” functionality in SQVI. Let's create a SQVI Query using “Alias”. Objective : Create a query to display Purchase Requisition Number with service details   Step 1: Execute transaction code SQVI and Enter. Step 2: Enter Query Name (Start with Z/Y) in selection Screen in Text Box in front of Label Quick View and Click Create Button Step 3:  Enter Title, Comments and select data Source as Table Join from dropdown and keep checked Basis mode radio button and press Enter. Step 4:  Now It will open the Screen where you can insert tables and create join between them. Purchase requisition data exist in EBAN table and Service Data Exists in ESLL table. As there are more other tables as well which are linked...
Read more

Automated Note Search & Customer Code Detection Tool

Image
Introduction Many times we need to find out correct customer code or space where we can add our code to enhance functionality of standard application. Sometimes we got through experience, by google, search at sap blogs and sometimes we debug. But did you heard about “ Automated Note Search & Customer Code Detection Tool ”.  Automated Note Search & Customer Code Detection Tool or you may Say T-Code ANST, which is used to find existing customer code space in standard code flow. Steps:    1. Type Transaction code ANST 2.  Execute Transaction code Now you have different options in selection screen which you may use as per your requirement and business use case. As Example, I want to know the custom code space for ME52N transaction code. 3. Enter Transaction Code and tick customer Code Only check box. 4. Execute the report after putting parameters. As I put ME52N so it will execute the ME52N. 5. Modify some values in transaction and click “ Save ” button. 6. Progr...
Read more