K_GROUP_SELECT in SAP Cloud ERP: what replaces it?

Use instead of K_GROUP_SELECT

• I_COSTCENTERHIERARCHYCDS_STOBReleased
• I_COSTCTRACTIVITYTYPEHIERARCHYCDS_STOBReleased
• I_FUNCTIONALAREAHIERARCHYCDS_STOBReleased
• I_PROFITCENTERHIERARCHYCDS_STOBReleased
• I_STSTCLKEYFIGUREHIERARCHYCDS_STOBReleased

SAP successor classification: multipleObjects

Migration steps

1. List every place your custom code reads or writes K_GROUP_SELECT; the ABAP Test Cockpit cloud-readiness checks report these usages.
2. Replace each access with one of I_COSTCENTERHIERARCHY, I_COSTCTRACTIVITYTYPEHIERARCHY, I_FUNCTIONALAREAHIERARCHY, I_PROFITCENTERHIERARCHY, I_STSTCLKEYFIGUREHIERARCHY; 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 K_GROUP_SELECT 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_COSTCENTERGROUP_GETDETAILFUNC
• BAPI_PROFITCENTERGRP_GETLISTFUNC
• G_SET_ENCRYPT_SETIDFUNC
• G_SET_FETCHFUNC
• G_SET_GET_ID_FROM_NAMEFUNC
• G_SET_TREE_IMPORTFUNC
• SETHEADERTABL
• SETHEADERTTABL

Terms used on this page

• Released API
• Successor
• ABAP Cloud
• Cloudification Repository