The Error That Sends You the Wrong Way
You call a function module from an external program. SAP answers:
Incompatible Call Rejected, see note 2295840;
Called Incompatible Function :CSAP_MAT_BOM_READ
The word "Incompatible" starts a search. Many results blame your client library. They point at the SAP Connector version (NCo) or the NW RFC SDK, and they recommend an upgrade.
I followed that path. I recorded the wrong conclusion in my own notes, and I looked at library versions for a problem that has nothing to do with them.
What the Error Actually Means
An S/4HANA system blocks a set of RFC function modules. The block is a system setting, not a client setting.
SAP supplies the list for a reason. In S/4HANA, some RFC function modules changed their signature, compared with the same modules in ERP. An external program that still uses the old signature can write inconsistent data. SAP Note 2259818 describes the risk. The affected modules land on an RFC blacklist, and a check rejects the call.
Two SAP documents describe the mechanism.
| Note | Title |
|---|---|
| 2259818 | RFC enabled Function Modules with incompatible signature change compared to its version in ERP are blocked from external access |
| 2295840 | Outbound / Inbound calls from external to RFC FM are blocked when the FM is blocklisted and the UCON-Check is active |
SAP Help Portal carries both notes, together with the removal procedure, on the page How to deal with error "Incompatible Call Rejected, see note 2295840".
The error text states its own cause. "Called Incompatible Function" refers to the function signature. It does not refer to your library.
Read One Table
The blacklist lives in a table called RFC_BL_SERVER. Read the table, and you have the answer before you write any code.
sap-vc-cli read-table RFC_BL_SERVER \
--where "RFM_NAME LIKE 'CSAP_MAT_BOM%'" \
--fields RFM_NAME,BLOCKED --system S4H
Three fields matter.
| Field | Meaning |
|---|---|
RFM_NAME |
Function module name |
BLOCKED |
X means the check rejects the call |
BLPACKAGE |
The SAP package that supplies the entry |
A function on the list fails every time. Do not test it. A function absent from the list can run.
What One S/4HANA System Contains
I read the full table on an S/4HANA system (client 200) on 2026-09-20.
| Item | Value |
|---|---|
| Rows in the table | 9,010 |
| Unique function modules | 3,174 |
Blocked CSAP_MAT_BOM modules |
6 of 6 |
Blocked CSAP_ modules |
16 |
Blocked CAMA_ modules |
14 |
Blocked CARD_ modules |
9 |
Blocked BAPI_ modules |
180 |
Read these numbers as one snapshot. SAP changes the list with kernel and support package updates. Check your own system.
The Boundary Is the Function Family
A common assumption says that read functions stay open and write functions close. That assumption is wrong on this system.
The whole CSAP_MAT_BOM family carries a block, and the family covers both directions.
CSAP_MAT_BOM_ALLOC_CREATE BLOCKED=X
CSAP_MAT_BOM_CREATE BLOCKED=X
CSAP_MAT_BOM_DELETE BLOCKED=X
CSAP_MAT_BOM_MAINTAIN BLOCKED=X
CSAP_MAT_BOM_OPEN BLOCKED=X
CSAP_MAT_BOM_READ BLOCKED=X
I called CSAP_MAT_BOM_READ on the same system with real data. SAP rejected the call with the note 2295840 message. A read function fails in the same way as a write function.
The split also runs inside a single family. CARD_CLASS_READ carries a block. CARD_DEPENDENCY_READ does not. A name prefix tells you nothing. Read the table.
What the Blacklist Leaves Open
Most Variant Configuration functions stayed off the list. I checked each name against the same table.
| Function | Use |
|---|---|
BAPI_CHARACT_CREATE |
Create a characteristic |
BAPI_CHARACT_CHANGE |
Change a characteristic |
BAPI_CLASS_CREATE |
Create a class |
BAPI_OBJCL_CREATE |
Assign an object to a class |
BAPI_UI_CREATE |
Create a UI design |
CAMA_TABLE_MAINTAIN_STRUCTURE |
Create a variant table structure |
CAMA_TABLE_MAINTAIN_ENTRIES |
Write variant table entries |
CAMA_DEPENDENCY_MAINTAIN |
Create a dependency |
CAMA_CONSTRAINT_NET_MAINTAIN |
Create a constraint net |
CAMA_CON_PROFILE_MAINTAIN |
Write a configuration profile |
BAPI_MATERIAL_SAVEDATA |
Create a material |
RFC_READ_TABLE |
Read any table |
CARD_DEPENDENCY_READ |
Verify a dependency |
Note the shape of the list. SAP blocks the BOM service functions and leaves the configuration functions open. I do not know SAP's reason.
The practical result matters more. A BOM has a second write path through the dialog transactions CS01 and CS02. GUI scripting can use that path. Configuration objects have no equivalent bulk dialog, so the table above covers that work.
A BOM read follows RFC_READ_TABLE instead. Read the tables STPO, STAS, STKO, and MAST.
For a BOM read, use STLTY and STLNR in the WHERE condition. The STPO and STAS tables have no STLAN field, and a query with STLAN returns OPTION_NOT_VALID.
Removing an Entry
SAP documents a removal path. The procedure needs a BASIS decision, and the risk belongs to the person who removes the entry.
- Check the table with transaction SE16N
- Remove an entry with the report
RS_RFC_BLACKLIST_CUSTOM. SAP Note 2298711 describes the report - The UCON check controls enforcement, as the title of Note 2295840 states. Community reports give the switch as parameter
ucon/rfc/check_blacklist(reported)
Read Note 2259818 before you remove anything. SAP added each entry to protect data integrity. A removed entry lets an outdated signature write to your database, and SAP does not support the result.
I do not recommend this path for a normal migration. Change the channel, not the guard rail. The functions in the table above cover most of the work.
Check Before You Build
Test the interface before you write a program around it. Two steps, in this order.
- Read
RFC_BL_SERVERfor the function name. An entry ends the discussion. - Call the function once with real data in a test client.
The first step takes one minute. The second step catches the problems that the table does not show, such as a missing parameter or a wrong LUW.
I learned this order the hard way. I checked the function interfaces for four BOM modules, saw complete parameter lists, and built the plan. Every call failed.
RFC_GET_FUNCTION_INTERFACE reports that a function exists. It says nothing about the blacklist.