Skip to main content
Apragya AIFree quotation builderQuotation builderQuote builderno signup
Integration

SAP RFC ERP Integration: Read ECC Tables and Test BAPIs Safely

For IT and migration teams working with SAP ECC or S/4 systems that have no OData services: read live data and test postings without transports.

Two engineers looking at a folder beside a server rack

A SAP RFC ERP integration reaches the systems OData cannot. Many ECC landscapes expose no Gateway services at all, but every SAP system speaks RFC, the protocol SAP's own tools use.

Apragya's RFC connector can ping a system and read its release details, describe a table's fields from the data dictionary, list tables, read table data in pages, and call any RFC-enabled function module, including BAPIs.

It needs the SAP NW RFC SDK, so it usually runs through a Tenant Runner inside your network, which connects out without an inbound firewall rule.

What reading ECC the old way costs

Spreadsheet extracts

Someone runs a report and emails the file.

Transport requests

Custom Z modules wait weeks for change control.

Risky test postings

Trying a BAPI in production is not an option.

Stale snapshots

Decisions rest on last month's extract.

An example: a Jamshedpur engineering group

Take an illustrative engineering group moving a business unit off ECC. The team needed live vendor and material data, and proof that migrated records would pass SAP's own checks.

Two weeks of reading ECC live

  1. Day 1

    Ping confirms the system and its release.
  2. Day 2

    Field catalogues read for vendor and material tables.
  3. Days 3 to 6

    Tables read in pages, wide rows split safely.
  4. Days 7 to 10

    Records mapped and cleaned in Apragya.
  5. Days 11 to 14

    BAPI dry runs validate every record.
The dry runs let SAP judge each record without saving any of them.

Every record SAP rejected in the dry run came back with SAP's own message, so the team fixed it before cut-over. Basis never had to transport a custom function module.

Steel parts on cards beside a stamp and a stack of stamped sheets
Every record checked by SAP itself, and none saved until the team was ready.

How the RFC read table connector works

Step 1 of 5

Install a runner

A Tenant Runner with the RFC SDK sits inside your network.

  1. Install a runner: A Tenant Runner with the RFC SDK sits inside your network.
  2. Add the connection: Application server, system number, client and a service user.
  3. Describe tables: Read the live field catalogue before extracting.
  4. Read in pages: Wide rows are split to stay within the standard row limit.
  5. Dry-run BAPIs: SAP validates and rolls back unless a commit is asked for.

Choosing a SAP ECC integration without Z transports

The standard table reader returns each row as a fixed-width string with a size cap, which is why some tools ship a custom function module. Apragya splits wide reads into chunks within that cap, so your Basis team does not need to import anything.

Common approaches against Apragya's RFC connector

FeatureCustom Z module toolsApragya RFC connector
Transport into SAPUsually requiredNot required
Wide tablesHandled by the Z moduleSplit into chunks
BAPI testingVariesDry run by default
NetworkVariesOutbound Tenant Runner
Field catalogueVariesRead live from the dictionary

Checked against public information on 16 September 2026.

Getting started

  1. Agree a read-only service user with your Basis team.
  2. Install a Tenant Runner with the RFC SDK.
  3. Add the connection and run a ping.
  4. Describe and read one table in small pages.
  5. Dry-run a BAPI on a handful of records.

A read-only user for the first weeks keeps security reviews short.

What else helps on SAP projects

Rollback by default

Nothing is saved unless a commit is requested.

Encrypted credentials

Service user passwords stored encrypted.

Human review

Postings wait for a named approver.

AI mapping help

Suggestions for mapping SAP fields to records.

Multi-company

Company codes map to companies in Apragya.

Clear progress

What was read and validated, record by record.

For S/4HANA with Gateway, see the SAP OData integration; compare Apragya with SAP Business One or read the PostgreSQL integration for other data sources.

What it costs to start

Free
Up to 3 users
CRM, HR and Vendor Onboarding
INR 3,999
Starter, a month
Up to 10 users, CRM and HR plus a choice of apps
INR 7,999
Pro, a month
Up to 25 users and every enterprise app

SAP RFC ERP integration, answered

Does it change data in SAP?
BAPI calls are dry runs by default: SAP validates and the transaction is rolled back. A commit happens only when explicitly requested.
Do we need to transport a Z function module?
No. Wide reads are split into chunks using the standard reader.
Can it run in the cloud?
It needs the SAP NW RFC SDK, so it usually runs on a Tenant Runner inside your network.
Does it work with S/4?
Yes. RFC works with ECC and S/4 systems that allow RFC access.
What does it cost to start?
The free plan covers up to 3 users with CRM, HR and Vendor Onboarding and 1,000 AI Credits a month. Starter is INR 3,999 a month for up to 10 users, with CRM and HR plus a choice of apps such as Sales and POS, Inventory, Payroll, Purchase and Payables, Support and Manufacturing. Pro is INR 7,999 a month for up to 25 users with every enterprise app, including Finance and Accounting, plus 5,000 AI Credits, single sign-on and audit logs.

Read ECC live, without a transport

Install a runner, add an RFC connection and read your first table.