Skip to content
ERP Preflight

FUNCfunction module· BC-SRV-NUM

NUMBER_GET_NEXT in SAP Cloud ERP: what replaces it?

Custom code that reads or writes NUMBER_GET_NEXT (FUNC) has to move to a released successor before it runs on SAP Cloud ERP or in ABAP Cloud. SAP names one successor: CL_NUMBERRANGE_RUNTIME.

Last verified:
Data source
Knowledge snapshot #3 · 33e0865dc811
Analyse your code for freeLook up another object
Cite:r/SAPINXHN

Use instead of NUMBER_GET_NEXT

SAP successor classification: oneObject

Migration steps

  1. List every place your custom code reads or writes NUMBER_GET_NEXT; the ABAP Test Cockpit cloud-readiness checks report these usages.
  2. Replace each access with CL_NUMBERRANGE_RUNTIME (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 NUMBER_GET_NEXT 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.

Release history and evidence

12 release states from 13 official sources, last verified October 12, 2026.

Full release history and evidence

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