MARC_SINGLE_READ in SAP Cloud ERP: what replaces it?

Use instead of MARC_SINGLE_READ

• I_PRODUCTPLANTBASICCDS_STOBReleased
• I_PRODUCTPLANTCOSTINGCDS_STOBReleased
• I_PRODUCTPLANTFORECASTCDS_STOBReleased
• I_PRODUCTPLANTINTLTRDCDS_STOBReleased
• I_PRODUCTPLANTPROCUREMENTCDS_STOBReleased
• I_PRODUCTPLANTQTMANAGEMENTCDS_STOBReleased
• I_PRODUCTPLANTSALESCDS_STOBReleased
• I_PRODUCTSUPPLYPLANNINGCDS_STOBReleased
• I_PRODUCTWORKSCHEDULINGCDS_STOBReleased

SAP successor classification: multipleObjects

Migration steps

1. List every place your custom code reads or writes MARC_SINGLE_READ; the ABAP Test Cockpit cloud-readiness checks report these usages.
2. Replace each access with one of I_PRODUCTPLANTBASIC, I_PRODUCTPLANTCOSTING, I_PRODUCTPLANTFORECAST, I_PRODUCTPLANTINTLTRD, I_PRODUCTPLANTPROCUREMENT +4; pick the successor whose fields match the usage.
3. All 9 successors are marked “Released” in the official release data, so the new code can use them in ABAP Cloud.
4. Re-run the cloud-readiness check on the changed code against your target release.

Release state of MARC_SINGLE_READ per edition

• 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.

• BAPI_MATERIAL_GET_ALLFUNC
• BAPI_MATERIAL_GETALLFUNC
• BAPI_MATERIAL_GET_DETAILFUNC
• BAPI_MATERIAL_GETLISTFUNC
• MARCTABL
• MATERIAL_READFUNC
• MD_READ_MATERIAL_SIMPLEFUNC
• STANDARDMATERIAL_GET_DATABADI_DEF

Terms used on this page

• Released API
• Successor
• ABAP Cloud
• Cloudification Repository