Skip to content
ERP Preflight

BADI_DEFbadi· FI-LOC-SRF-RUN

ES_SRF_TAX_CALENDAR in SAP Cloud ERP: what replaces it?

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

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

Use instead of ES_SRF_TAX_CALENDAR

SAP successor classification: oneObject

Migration steps

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

  • SAP Cloud ERP Private:Deprecatedas of SAP Cloud ERP Private — latest release · released since SAP S/4HANA 2022 · deprecated since SAP S/4HANA 2023 FPS03
  • SAP Cloud ERP:Deprecatedas of SAP Cloud ERP — current release · deprecated since SAP Cloud ERP — current release

Release history and evidence

11 release states from 11 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.

ES_SRF_TAX_CALENDAR successor for SAP Cloud ERP migration: ES_SRF_TAX_CALENDAR_V2