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.
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
Day 1
Ping confirms the system and its release.Day 2
Field catalogues read for vendor and material tables.Days 3 to 6
Tables read in pages, wide rows split safely.Days 7 to 10
Records mapped and cleaned in Apragya.Days 11 to 14
BAPI dry runs validate every record.
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.
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.
- Install a runner: A Tenant Runner with the RFC SDK sits inside your network.
- Add the connection: Application server, system number, client and a service user.
- Describe tables: Read the live field catalogue before extracting.
- Read in pages: Wide rows are split to stay within the standard row limit.
- 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
| Feature | Custom Z module tools | Apragya RFC connector |
|---|---|---|
| Transport into SAP | Usually required | Not required |
| Wide tables | Handled by the Z module | Split into chunks |
| BAPI testing | Varies | Dry run by default |
| Network | Varies | Outbound Tenant Runner |
| Field catalogue | Varies | Read live from the dictionary |
Checked against public information on 16 September 2026.
Getting started
- Agree a read-only service user with your Basis team.
- Install a Tenant Runner with the RFC SDK.
- Add the connection and run a ping.
- Describe and read one table in small pages.
- 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
SAP RFC ERP integration, answered
Does it change data in SAP?
Do we need to transport a Z function module?
Can it run in the cloud?
Does it work with S/4?
What does it cost to start?
Read ECC live, without a transport
Install a runner, add an RFC connection and read your first table.