Keep abap learning

Consume SAP CPI HTTP API in ABAP Using SM59

2026-04-02T18:17:00.003+05:30

Consume SAP CPI HTTP API in ABAP Using SM59 (With `/http` Prefix & Client ID/Secret)

This guide shows a clean and reusable approach to call SAP CPI APIs from ABAP with:

✅ SM59 RFC Destination
✅ Prefix /http maintained in SM59
✅ Dynamic endpoint handling
✅ Client ID & Secret (Basic Authentication)
✅ Custom configuration table (no hardcoding)

📌 Scenario Design

🔹 Key Concept

SM59: Maintain host + /http prefix
Table: Maintain only remaining endpoint
ABAP: Combines both dynamically

Example:

Component	Value
SM59 Host	`dev-cpi-xxxx.cfapps.ap11.hana.ondemand.com`
SM59 Prefix	`/http`
Table Endpoint	`/transaction`
Final URL	`/http/transaction`

🔧 Step 1: Create RFC Destination (SM59)

Go to SM59
Create destination:
- Type: G (HTTP Connection)

Maintain:

Technical Settings:

Target Host: dev-cpi-xxxx.cfapps.ap11.hana.ondemand.com
Service No: 443
Path Prefix: /http ✅ (Important)

👉 Now /http is fixed and reusable.

🗂️ Step 2: Create Custom Config Table

Create a table: ZCPI_CONFIG

Suggested Structure:

FIELD NAME	DESCRIPTION
PROCESS	Key (DEST / API / AUTH)
VALUE	Stores destination or endpoint
CLIENT_ID	Client ID
CLIENT_SECRET	Client Secret

Sample Entries:

PROCESS	VALUE	CLIENT_ID	CLIENT_SECRET
DEST	ZCPI_DEST	-	-
API	/transaction	-	-
AUTH	-	CPI_CLIENT	CPI_SECRET

💻 Step 3: ABAP Code (With Comments)

DATA: lo_http_client TYPE REF TO if_http_client,
      lv_json        TYPE string,
      lv_response    TYPE string,
      lv_endpoint    TYPE string,
      lv_client      TYPE string,
      lv_secret      TYPE string.

DATA: ls_dest TYPE zcpi_config,
      ls_api  TYPE zcpi_config,
      ls_auth TYPE zcpi_config.

" 1. Read RFC Destination
SELECT SINGLE * INTO ls_dest FROM zcpi_config WHERE process = 'DEST'.

" 2. Read API Endpoint (only /transaction)
SELECT SINGLE * INTO ls_api FROM zcpi_config WHERE process = 'API'.
lv_endpoint = ls_api-value.

IF ls_dest-value IS INITIAL.
  WRITE: 'Maintain RFC destination in ZCPI_CONFIG'.
  EXIT.
ENDIF.

IF lv_endpoint IS INITIAL.
  WRITE: 'Maintain API endpoint'.
  EXIT.
ENDIF.

" 3. Create HTTP Client using SM59
CALL METHOD cl_http_client=>create_by_destination
  EXPORTING
    destination = ls_dest-value
  IMPORTING
    client      = lo_http_client.

IF sy-subrc <> 0.
  WRITE: 'Error creating HTTP client'.
  EXIT.
ENDIF.

" 4. Append Endpoint to Prefix (/http already in SM59)
lo_http_client->request->set_header_field(
  name  = '~request_uri'
  value = lv_endpoint ).   " Only /transaction

" Final URL becomes: /http/transaction

" 5. Read Authentication Details
SELECT SINGLE * INTO ls_auth FROM zcpi_config WHERE process = 'AUTH'.

IF ls_auth-client_id IS INITIAL OR ls_auth-client_secret IS INITIAL.
  WRITE: 'Maintain Client ID & Secret'.
  EXIT.
ENDIF.

lv_client = ls_auth-client_id.
lv_secret = ls_auth-client_secret.

" 6. Set Basic Authentication
lo_http_client->authenticate(
  username = lv_client
  password = lv_secret ).

" 7. Set HTTP Method & Headers
lo_http_client->request->set_method( if_http_request=>co_request_method_post ).

lo_http_client->request->set_header_field(
  name  = 'Content-Type'
  value = 'application/json' ).

lo_http_client->request->set_header_field(
  name  = 'Accept'
  value = '*/*' ).

" 8. Prepare JSON Payload
lv_json = '{ "id": "1001", "type": "TEST" }'.

lo_http_client->request->set_cdata( lv_json ).

" 9. Send Request
CALL METHOD lo_http_client->send
  EXPORTING timeout = 15.

" 10. Receive Response
CALL METHOD lo_http_client->receive.

" 11. Fetch Response
lv_response = lo_http_client->response->get_cdata( ).

DATA(status_code) TYPE i.
DATA(reason) TYPE string.

lo_http_client->response->get_status(
  IMPORTING
    code   = status_code
    reason = reason ).

WRITE: / 'Status:', status_code.
WRITE: / 'Response:', lv_response.

" 12. Close Connection
lo_http_client->close( ).

🎯 Key Highlights

✅ Prefix Handling (Best Practice)

/http → maintained in SM59
/transaction → maintained in table
Combined dynamically → flexible & reusable

✅ Reusable Architecture

One RFC → multiple APIs
No hardcoding
Easy maintenance

✅ Secure Authentication

Client ID & Secret stored in table
Passed using:

lo_http_client->authenticate( )

⚠️ Common Issues

Issue	Reason	Fix
404 Error	Wrong endpoint	Check `/transaction`
401 Error	Invalid credentials	Verify client ID/secret
SSL Issue	Certificate missing	Maintain in STRUST
No response	Timeout	Check network

🏁 Final Summary

This design gives you:

🔁 Reusable RFC destination
⚡ Dynamic endpoint control
🔐 Simple authentication handling
🧩 Clean separation (SM59 + Table + Code)

If you want, I can next help you build:

Reusable ABAP class (factory pattern)
CPI integration logging dashboard
Error handling + retry framework

Just let me know 👍

SAP ABAP Tutorial: How to Post F-47 Down Payment Request via BAPI BAPI_ACC_DOCUMENT_POST

2026-02-07T21:14:00.003+05:30

SAP ABAP Tutorial: How to Post F-47 Down Payment Request via BAPI BAPI_ACC_DOCUMENT_POST

Working fine..

Top SAP ABAP Interview Questions on BAPI

2026-01-13T17:18:00.004+05:30

Introduction

BAPI (Business Application Programming Interface) is one of the most frequently asked topics in SAP ABAP interviews, especially for real-time projects and integrations.
In this post, we cover important SAP ABAP BAPI interview questions with simple and practical answers, useful for freshers as well as experienced consultants.

1. What is BAPI in SAP ABAP?

Answer:
BAPI stands for Business Application Programming Interface.
It is a standard SAP-provided, remote-enabled function module used to access SAP business objects like Purchase Orders, Sales Orders, Accounting Documents, etc.

BAPIs ensure that SAP business rules, validations, and authorizations are followed.

2. Why should we use BAPI instead of direct table updates?

Answer:
Direct table updates can cause data inconsistency and system corruption.

BAPIs are preferred because:

They follow standard SAP logic
They are upgrade safe
They perform validations automatically
They maintain data integrity

3. Are all BAPIs remote-enabled?

Answer:
Yes, all BAPIs are remote-enabled function modules, which means they can be called:

From other SAP systems
From non-SAP systems
Via RFC, Web services, or APIs

4. How do you find a BAPI in SAP?

Answer:
You can find BAPIs using:

Transaction BAPI
Transaction SE37 (search with BAPI*)
SAP Object Browser (SWO1)
SAP documentation and Google

5. Which BAPI is used to post accounting documents?

Answer:


BAPI_ACC_DOCUMENT_POST

This BAPI is used to post accounting documents such as:

GL postings
Vendor invoices
Customer invoices
Tax and withholding tax postings

6. What is the use of BAPI_TRANSACTION_COMMIT?

Answer:
After calling a BAPI that creates or changes data, we must call:


BAPI_TRANSACTION_COMMIT

This ensures that the data is permanently saved in the database.

Without this, the data will not be committed.

7. What happens if we do not call BAPI_TRANSACTION_COMMIT?

Answer:
If BAPI_TRANSACTION_COMMIT is not called:

Data will not be saved
Document number will not be generated
Changes will be rolled back

8. How do you handle errors in BAPI?

Answer:
BAPIs return messages in a RETURN parameter (usually of type BAPIRET2).

We check:

TYPE = 'E' → Error
TYPE = 'A' → Abort
TYPE = 'S' → Success

If errors exist, we do not call COMMIT.

9. Can we update SAP tables directly if BAPI is not available?

Answer:
No, direct updates are not recommended.
If no BAPI exists, alternatives include:

Standard SAP transactions via BDC
Enhancement frameworks (BAdI, User Exit)
Custom function modules using standard logic

10. What is the difference between BAPI and RFC?