Journals / Bilişim Teknolojileri Dergisi / 2026 / Cilt: 19 Sayı: 3

A Configuration-Driven Dynamic REST/RFC Gateway for ABAP-Based ERP Systems

ABAP Tabanlı ERP Sistemleri İçin Yapılandırma Odaklı Dinamik Bir REST/RFC Ağ Geçidi

Mustafa Öztürk(İSTANBUL ÜNİVERSİTESİ-CERRAHPAŞA, LİSANSÜSTÜ EĞİTİM ENSTİTÜSÜ, BİLGİSAYAR MÜHENDİSLİĞİ (YL) (TEZLİ))0009-0000-7515-3923
Şükrü Okul(TÜBİTAK BİLGEM, Informatics and Information Security Research Center)0000-0001-6645-7933
Muhammed Ali Aydın(ISTANBUL UNIVERSITY-CERRAHPASA, FACULTY OF ENGINEERING, DEPARTMENT OF COMPUTER ENGINEERING)0000-0002-1846-6090
Pages
331–352
Publication Date
2026-07-31
🏛️Bibliographic metadata and full text access for this article are provided via DergiPark.
DergiPark Record ↗
✨

AI Summary & Key Takeaways

AI Insight
⚡ TL;DR(Too Long; Didn't Read)

Results indicate that, although the proposed model does not achieve the lowest latency in every scenario, it reduces scenario-specific technical artifacts while providing competitive runtime performance and compact payloads.

📌 3 Key Takeaways

🎯
Objective & Hypothesis:Remote function call (RFC) interfaces widely used in ABAP-based enterprise resource planning (ERP) systems are not naturally aligned with modern HTTP/JSON integration requirements.
📊
Key Findings & Data:Evaluation metrics included p90, p95, and p99 response times, payload size, success rate, limited concurrency, and throughput.
💡
Conclusion & Impact:Results indicate that, although the proposed model does not achieve the lowest latency in every scenario, it reduces scenario-specific technical artifacts while providing competitive runtime performance and compact payloads.
🔬Design:Modeling & Simulation
📍Scope:Comprehensive Sample
⚙️Variables:abap · erp entegrasyonu · rest api

Abstract

Remote function call (RFC) interfaces widely used in ABAP-based enterprise resource planning (ERP) systems are not naturally aligned with modern HTTP/JSON integration requirements. Consequently, organizations often develop scenario-specific SOAP services, SAP Gateway/OData services, or custom REST wrappers, increasing maintenance effort and integration complexity. This study proposes a configuration-driven dynamic REST/RFC gateway that exposes existing RFC functions through a single HTTP entry point. The gateway resolves requests through configuration records, discovers interface metadata at runtime using RTTS/RTTI, performs generic JSON-to-ABAP and ABAP-to-JSON transformations, and provides centralized logging and endpoint-level authorization. The model was evaluated in a production ERP environment across three read-oriented scenarios against REST/RFC gateway, SOAP, and SAP Gateway/OData alternatives. Evaluation metrics included p90, p95, and p99 response times, payload size, success rate, limited concurrency, and throughput. Results indicate that, although the proposed model does not achieve the lowest latency in every scenario, it reduces scenario-specific technical artifacts while providing competitive runtime performance and compact payloads. The proposed approach offers a practical modernization model for RFC-centric integrations through configuration-driven exposure, reusability, and centralized governance.

Özet

ABAP tabanlı kurumsal kaynak planlama (ERP) sistemlerinde yaygın kullanılan uzak fonksiyon çağrısı (RFC) arayüzleri, güncel HTTP/JSON tabanlı entegrasyon gereksinimleriyle doğal olarak uyumlu değildir. Bu durum, senaryoya özgü SOAP servisleri, SAP Gateway/OData servisleri veya özel REST sarmalayıcıları geliştirilmesini gerektirerek bakım yükünü ve entegrasyon karmaşıklığını artırmaktadır. Bu çalışmada, mevcut RFC işlevlerini tek bir HTTP giriş noktası üzerinden dışa açan yapılandırma odaklı dinamik bir REST/RFC ağ geçidi modeli önerilmektedir. Model, istekleri yapılandırma kayıtlarıyla çözümlemekte, RTTS/RTTI ile arayüz meta verilerini çalışma anında keşfetmekte, genel JSON–ABAP dönüşümleri gerçekleştirmekte, merkezi loglama ve endpoint düzeyinde yetkilendirme sağlamaktadır. Model, üretim ERP ortamında üç okuma odaklı senaryoda REST/RFC gateway, SOAP ve SAP Gateway/OData yaklaşımlarıyla karşılaştırılmıştır. Değerlendirmede p90, p95 ve p99 yanıt süreleri, veri yükü boyutu, başarı oranı, sınırlı eşzamanlılık ve verimlilik metrikleri kullanılmıştır. Bulgular, modelin her senaryoda en düşük gecikmeyi sağlamasa da teknik nesne üretimini azaltırken rekabetçi çalışma zamanı ve kompakt yanıt yükleri sunduğunu göstermektedir. Sonuç olarak önerilen yaklaşım, RFC tabanlı entegrasyonlar için yeniden kullanılabilir ve merkezi yönetişim sağlayan pratik bir modernizasyon modeli sunmaktadır.

🔖

Cite This Article

Öztürk, M., Okul, Ş., Aydın, M. A. (2026). A Configuration-Driven Dynamic REST/RFC Gateway for ABAP-Based ERP Systems. Bilişim Teknolojileri Dergisi, Cilt: 19 Sayı: 3, 331–352. https://doi.org/10.17671/gazibtd.1905143

📄 Full Text PDF Viewer

📄

PDF görüntüleyici hazırlanıyor...

References (19)

  1. V. Botta-Genoulaz, P.-A. Millet, and B. Grabot, “A survey on the recent research literature on ERP systems,” Computers in Industry, vol. 56, no. 6, pp. 510–522, 2005.
  2. Y. B. Moon, “Enterprise resource planning (ERP): A review of the literature,” International Journal of Management and Enterprise Development, vol. 4, no. 3, pp. 235–264, 2007.
  3. V. A. Mabert, A. Soni, and M. A. Venkataramanan, “Enterprise resource planning: Managing the implementation process,” European Journal of Operational Research, vol. 146, no. 2, pp. 302–314, 2003.
  4. R. Malhotra and C. Temponi, “Critical decisions for ERP integration: Small business issues,” International Journal of Information Management, vol. 30, no. 1, pp. 28–37, 2010.
  5. H. S. Aguirre-Mayorga, J. E. Carreño-Vargas, C. A. Vega-Mejía, J. S. Castellanos-Arias, and Y. P. Hernanaez-Martinez, “Evaluation of integration approaches between ERP and BPM systems,” Ingeniería y Universidad, vol. 16, no. 2, pp. 415–431, 2012.
  6. R. T. Fielding, Architectural Styles and the Design of Network-based Software Architectures. Doctoral dissertation, University of California, Irvine, 2000.
  7. M. P. Papazoglou and W. J. A. M. van den Heuvel, “Service oriented architectures: Approaches, technologies and research issues,” The VLDB Journal, vol. 16, no. 3, pp. 389–415, 2007.
  8. C. Pautasso, O. Zimmermann, and F. Leymann, “RESTful Web Services vs. ‘Big’ Web Services: Making the Right Architectural Decision,” in Proceedings of the 17th International World Wide Web Conference, 2008, pp. 805–814.
  9. L. Richardson and M. Amundsen, RESTful Web APIs. Sebastopol, CA, USA: O’Reilly Media, 2013.
  10. C. Bönnen, V. Drees, A. Fischer, L. Heinz, and K. Strothmann, SAP Gateway and OData, 3rd ed. Bonn, Germany: Rheinwerk Publishing, 2018.
  11. J. Andersen, “ABAP reflection – Part one (The RTTS and type introspection),” Nocture, 2012. [Online]. Available: https://www.nocture.dk/2012/11/01/abap-reflection-part-one-the-rtts-and-type-introspection/
  12. SAP SE, “ABAP JSON serializer and deserializer (abap-to-json),” GitHub repository. [Online]. Available: https://github.com/SAP/abap-to-json
  13. A. R. Hevner, S. T. March, J. Park, and S. Ram, “Design science in information systems research,” MIS Quarterly, vol. 28, no. 1, pp. 75–105, 2004.
  14. K. Peffers, T. Tuunanen, M. A. Rothenberger, and S. Chatterjee, “A design science research methodology for information systems research,” Journal of Management Information Systems, vol. 24, no. 3, pp. 45–77, 2007.
  15. C. M. Garcia and R. Abilio, “Systems integration using web services, REST and SOAP: A practical report,” Revista de Sistemas de Informação da FSMA, no. 19, pp. 34–41, 2017.
  16. M. Arslan, “Serialize JSON in ABAP,” Medium, 2020. [Online]. Available: https://xmarslan.medium.com/serialize-json-in-abap-d2d44ce0d771
  17. K. Duran, L. V. Cakir, Y. Yigit, K. Huseynov, S. R. Kusu, M. A. Ertürk, and B. Canberk, “Toward Digital Twin-as-a-Service (DTaaS) Platforms: A Survey on Architecture, Design Requirements, and Performance Metrics,” IEEE Communications Surveys & Tutorials, vol. 28, pp. 1845–1878, 2025.
  18. OpenAPI Initiative, “OpenAPI Specification,” Linux Foundation, 2024. [Online]. Available: https://spec.openapis.org/oas/latest.html
  19. JSON Lines, “JSON Lines text format.” [Online]. Available: https://jsonlines.org/