CL_BCS_MESSAGE in SAP Cloud ERP: what replaces it?

Use instead of CL_BCS_MESSAGE

• CL_BCS_MAIL_MESSAGECLASReleased

SAP successor classification: oneObject

Migration steps

1. List every place your custom code reads or writes CL_BCS_MESSAGE; the ABAP Test Cockpit cloud-readiness checks report these usages.
2. Replace each access with CL_BCS_MAIL_MESSAGE (CLAS).
3. The successor is marked “Released” in the official release data, so the new code can use it in ABAP Cloud.
4. Re-run the cloud-readiness check on the changed code against your target release.

Release state of CL_BCS_MESSAGE 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_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
• CX_GBT_MIMECLAS

Terms used on this page

• Released API
• Successor
• ABAP Cloud
• Cloudification Repository