SETLEAF in SAP Cloud ERP: what replaces it?

Use instead of SETLEAF

• I_COSTCENTERHIERARCHYNODECDS_STOBReleased
• I_COSTCTRACTIVITYTYPEHIERNODECDS_STOBReleased
• I_FUNCTIONALAREAHIERNODECDS_STOBReleased
• I_PROFITCENTERHIERARCHYNODECDS_STOBReleased
• I_STSTCLKEYFIGUREHIERNODECDS_STOBReleased

SAP successor classification: multipleObjects

Migration steps

1. List every place your custom code reads or writes SETLEAF; the ABAP Test Cockpit cloud-readiness checks report these usages.
2. Replace each access with one of I_COSTCENTERHIERARCHYNODE, I_COSTCTRACTIVITYTYPEHIERNODE, I_FUNCTIONALAREAHIERNODE, I_PROFITCENTERHIERARCHYNODE, I_STSTCLKEYFIGUREHIERNODE; pick the successor whose fields match the usage.
3. All 5 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 SETLEAF 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.

• G_SET_FETCHFUNC
• G_SET_GET_ALL_VALUESFUNC
• G_SET_TREE_IMPORTFUNC
• SETNODETABL

Terms used on this page

• Released API
• Successor
• ABAP Cloud
• Cloudification Repository