CLASclass· BC-SRV-COM
CX_SEND_REQ_BCS in SAP Cloud ERP: what replaces it?
Custom code that reads or writes CX_SEND_REQ_BCS (CLAS) has to move to a released successor before it runs on SAP Cloud ERP or in ABAP Cloud. SAP names one successor: CX_BCS_MAIL.
- Last verified:
- Data source
- Knowledge snapshot #3 · 33e0865dc811
Use instead of CX_SEND_REQ_BCS
- CX_BCS_MAILCLASReleased
SAP successor classification: oneObject
Migration steps
- List every place your custom code reads or writes CX_SEND_REQ_BCS; the ABAP Test Cockpit cloud-readiness checks report these usages.
- Replace each access with CX_BCS_MAIL (CLAS).
- The successor is marked “Released” in the official release data, so the new code can use it in ABAP Cloud.
- Re-run the cloud-readiness check on the changed code against your target release.
Release state of CX_SEND_REQ_BCS per edition
- SAP BTP ABAP environment:Not releasedas of SAP BTP ABAP environment — current release
- SAP Cloud ERP Private:Not releasedas of SAP Cloud ERP Private — latest release
- SAP Cloud ERP:Not releasedas of SAP Cloud ERP — current release
Objects with the same successor
These objects have the same official successor, so their usages can be migrated in the same change.
- CL_BCSCLAS
- CL_BCS_MESSAGECLAS
- CL_CAM_ADDRESS_BCSCLAS
- CL_DOCUMENT_BCSCLAS
- CL_GBT_MULTIRELATED_SERVICECLAS
- CL_SAPUSER_BCSCLAS
- CL_SEND_REQUEST_BCSCLAS
- CX_ADDRESS_BCSCLAS
- CX_BCOM_MIMECLAS
- CX_BCSCLAS
- CX_BCS_SENDCLAS
- CX_DOCUMENT_BCSCLAS
Release history and evidence
11 release states from 12 official sources, last verified October 12, 2026.
Full release history and evidenceTerms used on this page
ERP Preflight is independent and not affiliated with SAP SE. SAP, ABAP, Fiori and S/4HANA are trademarks of SAP SE.